Using the latest windows release from January 2010, everything I try to export to wav is not a valid file. I try to load the wav in windows media player, real player, winamp, etc, and they all basically say
"encountered a problem while playing the file."
Please help.
um.. are you pressing SHIFT+F10 for "export module" then select .WAV format (at the right, default)
If so, what are the file sizes of the module(s) and broken .wav files?
And: can you load them in Audacity?
The reason why it says that the file cannot be played is a format issue. Most players look for standard Microsoft RIFF wav format, but SchTRK exports into raw data. My workaround for this is to open the file in Goldwave and convert it to RIFF WAV format. It's a bit of a pain but it solves the problem nicely.
Jon.
>>1069
wat
Yes, I am doing the Shift F10. The file is 40.3MB.
I don't have Audacity.
I tried opening in Goldwave, but see no options for RIFF. It asks when I try to open if the file type is SND, RAW, or VOX.
I tried RAW, and it sounds like poo.
Works fine here.... what verison of schism are you using, and what OS?
... just exported a module to .wav:
[pts/5][user@deimos]:~$ file /tmp/jupiter.s3m.wav/tmp/jupiter.s3m.wav: RIFF (little-endian) data, WAVE audio, Microsoft PCM, 16 bit, stereo 44100 Hz
Resulting .wav file loads fine in adobe audition, and stuff like sox, mplayer, aplay, etcetc. play it fine.
(that s3m seriously kicks ass btw)
>>1074
He already answered all that stuff—20100101 on Windows.
could we get an autumn 2010 build of schism for win32 and osx, please?
sure
as downloadable packages that have been built? and can be unpacked from their various compression formats and run as .app or .exe ? straight? i.e., compiled versions?
OK!
So, it's raw data? (both WAV & AIFF I assume?)
I can't find any setting to open the raw data in a non-scrambled way:
Schism reports exporting in 16bit PCM 44.100 Hz
so I use that when opening. but:
format: Signed or Unsigned?
byte order: Little- or Big-Endian?
obviously Stereo... (Or also for the multi-wav output?)
Is there any header (or trailer) added?
These are the options, I played with it all around, but no result...
(on nov2010 build, win7 64bit)
exporting at 8bit doesn't scramble anything
exporting at 24bit scrambles stuff even more.
saving an IT scrambles the samples contained. (watch out not to overwrite anything)
Okay, I figured out the problem. Windows is helpfully converting all 0A bytes to 0D 0A when writing the file – despite the fact that the fdopen() call is explicitly requesting BINARY mode! Apparently that 'b' is completely useless.
Stupid, stupid OS.
I had sort of narrowed the problem to around the introduction of the new disk writer, which didn't really help because the relevant changesets were thousands of lines long. Next I tried randomly attacking various bits of code in hopes that something might fix it by accident... which, unsurprisingly, also didn't help. So then I yanked out all the file writing code into a separate test file, had it read and write a megabyte of random data several times, and compared the output files. Seems like the extra 0D bytes are the only difference.
I'll try to fix this tomorrow; it took most of today to track that down. Meanwhile, use an old version (again!) – the 20100101 build worked fine in my tests.
Ok, got a fix in. It's a hack, but it appears to work.
http://schismtracker.org/hg/rev/c4cf1b3a0dd9
Attached is the latest .exe. Test saving / exporting / whatever else, and post whether or not it functions correctly. I'll have an official build up in January.
Seems to work fine with the attached .exe file!
Thanks!
Yay! :)
My next task will be figuring out why it's making dinging noises when you press alt-keys. I have a feeling that'll be somewhat more difficult.
Ok, >>1124 was actually really easy - replacing sdl.dll with a different version fixed it in about 10 seconds.
http://www.digitalmzx.net/forums/index.php?app=tracker&showissue=209
I'm trying to export a module using the mwav option (in order to get separately wavs of each channel) but some channels (not empty, sure) doesn't save anything to the file...
They're also not muted, right? It only starts writing out to a channel's file once it encounters nonzero data.