Previous Page | Next Page

by hcs at 7:51 AM EDT on March 16, 2008
Well, yes, "test > test.txt" will result in a blank file. I meant "test blah.adx > test.txt".
by javispedro at 8:12 AM EDT on March 16, 2008

Another thing I've noticed: in most Brawl songs (esp F05.brstm), it doesn't play the first samples at all (it skips them). You can hear them however using in_cube. It seems to happen with Galaxy's ast too.

The gstreamer plugin I've been doing is nearly usable -- It can already play & N-loop brstm, adx using Rhythmbox or Totem -- no infinite loop, no seeks yet. I might clean it up a little and release it.
by Bugger at 8:48 AM EDT on March 16, 2008
And there is no way around?
Just say "yes" or "no"...
by Bugger at 5:52 PM EDT on March 16, 2008
... Say, what is the new -x option good for?
Can you give me an example, it confuses me really...
And I wonder, you take all my requests so far, thanks very much hcs.

Edit: What is the output line when decoding with -x for? What is that?

edited 5:56 PM EDT March 16, 2008
by hcs at 9:19 PM EDT on March 16, 2008
@javispedro: Hum, that's bizarre, I'm not really sure what you mean. How many samples are skipped?

@Bugger: The -x option outputs a command line for the ADX encoder, so that you can then reencode the output to ADX with the correct loop points.
uf jumps aboard the vgmstream bandwagon by unknownfile at 11:09 PM EDT on March 16, 2008
i am now doing some tweaking to the code on svn with winamp and visual c in mind. don't expect anything major from me though as i suck with code ports (and in_cube is a mess anyway).
by javispedro at 6:24 AM EDT on March 17, 2008
Oops. I noticed that even vgm-generated dump.wav plays fine in Winamp, so it must be that I borked my sound system somehow. Sorry.

Indeed, switching to pulseaudio fixed the problem. Rhythmbox's working now. Going to test seeking...

EDIT: First release of the gstreamer plugin is up!
vgmgstream- (source file)
Includes patched vgmstream-r53, so all you need is "./configure --prefix=/usr && make && make install".

It is both my first gstreamer plugin and my first autoconf project, so there may be lots of bugs.

Currently, it can only play brstm & ast files, but it is very easy to add support for more extensions -- next release will have them all (TM). Seeking does not work yet.

If anyone is interested in it, tell me if it works for you.

edited 9:37 AM EDT March 17, 2008
by Mouser X at 4:09 AM EDT on March 23, 2008
I didn't see this brought up in this thread (I probably brought it up in #usf), so I thought I'd put it here. When the VGMstream Winamp plugin gets some settings, I would suggest that there be multiple options. Specifically, some ADXs have data after the loop point. In its current iteration, this data is never heard. For the settings, I would like to see not only "Loop [x] times" and "Fade [x] length" but also "If data exists past the loop point, use that instead of using "Fade Length.'"

I'm not sure how to make that into a menu entry (I don't know how to shorten it), but I figured I'd let you know that a feature like that would b pretty cool. Basically a "If data exists past the end loop, play it. Else use FadeLength."

Anyway, I've been using VGMstream instead of in_cube for a few days now, and I haven't run into any problems. That is, excluding the noticeable decrease in available formats. Nice job! I look forward to more releases/formats. Your work is appreciated. Mouser X over and out.
by JILost at 5:05 AM EDT on March 23, 2008
My take on the "data past the loop end point" situation is to have it so that if fade delay and fade length are set to 0 while loop count is NOT set to 0, the data after the loop point is heard rather than having an abrupt stop at the loop point after x loops. That seems the easiest and most logical to me...but that might just be me.
by Mouser X at 5:40 AM EDT on March 23, 2008
What about when ADXs don't have any data past the end loop point? If you have fade and fade delay set to 0, and it's not looping infinitely, you're going to end up with an abrupt end. Not all ADXs have data after the end loop. A few do, but definitely not all. With the options as I said, if there's data after the end loop, then the fade delay and fade time are ignored. If there *isn't* data after the end loop, it falls back on the fade delay and fade time.

However, if someone wants an abrupt end (for whatever reason), then leave fade delay and fade time empty/0, and turn off "play data past the end loop." With that option off, you'll essentially have in_cube as it now stands. With that option on, you're afforded more abilities. I don't see how your method improves things, most because not every file contains data past the end loop. I think that most *don't* contain data past the end loop, but I'm not certain. I haven't looked at a ton of files to find out. But if that's correct (that most don't have data past the end loop) then I would think that with your method, you'd end up with an abrupt end more often than not, which is something I'd prefer to avoid.

Besides, what's the harm in providing an extra option? I'd rather be able to set it specifically, than have to do some oddball combination thing (set both fade delay and fade length to 0) to get it to play past the end loop (which would then often result in abrupt ends for files that don't have data past the end loop).

Anyway, it's HCS's work, not mine. I only provided the info. as I thought it would be useful. Mouser X over and out.

Previous Page | Next Page
Go to Page 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207

Search this thread

Show all threads

Reply to this thread:

User Name Tags:

bold: [b]bold[/b]
italics: [i]italics[/i]
emphasis: [em]emphasis[/em]
underline: [u]underline[/u]
small: [small]small[/small]
Link: [url=]Link[/url]


HCS Forum Index
Halley's Comet Software
forum source
Generated in 0.018s;