On 7/24/07, James Paige <[EMAIL PROTECTED]> wrote: > WAV->OGG would be great. it would be no extra work compared to MP3->OGG > and would save space.
You can safely include oggenc and madplay binaries with the full Windows distribution, so when WAVs are added on import, pass them into oggenc (oggenc -q 7 -o out.ogg in.wav) -- you may have to copy them to the WORKDIR first so that the absolute location is known. And recode MP3s on import as well. I hate the idea of transcoding to work around a bug, so if it comes that using libmad is easier than expected, perhaps that's something that can be done. But, at least for now, my suggestion is transcode. Maybe it can be fixed after uberzechtzung (yeah I misspelled it). > I think MIDI->OGG would be a problem. That can be a problemenatic > conversion, which results in a much bigger file that doesn't sound as > good. I have no desire to remove midi playback functionality from GAME. > If I recall, that's exactly what Timidity++ does (well, it outputs into WAV format and not Ogg). And without proprietary soundbanks it sounds terrible. Also, someone previously said that we should transcode on play. That's a bad idea. Keep in mind the least common denominator. Say someone wants to play a game on Windows 98. Or even a slow Win2K machine. GAME shouldn't have to do any hard processing -- and transcoding from MP3 to Ogg is hard. The developer using CUSTOM has the patience to wait 10-20 seconds for a song to add to their music/sfx list. The player will get angry to have to wait for GAME to transcode before they can play the game. If it's done on an as-needed basis, when they enter the shop with MP3 music, they'll have silence and choppiness for 10-20 seconds. The best and most logical place to transcode or encode (eg. MP3->Ogg is transcoding, WAV->Ogg is encoding) is on import. I think it would work fine if we included madplay and oggenc with the Windows distribution and had them as a dependency on Linux. This makes using CUSTOM in DOS impossible, but if Ogg plays in DOS, then GAME will sitll work. That is if a DOS port is still being maintained, but I don't know. Definitely though the Ogg encode quality should be a user-configurable option in CUSTOM somewhere. -1 is terrible, 10 is best. Pass that integer on the commandline as the argument to -q. -- Keith Gable Lead Programmer / Project Leader The Ignition Project <http://www.ignition-project.com/> [Ask me how you can get a free Gmail account - Now with Google Chat!] _______________________________________________ Ohrrpgce mailing list [email protected] http://lists.motherhamster.org/listinfo.cgi/ohrrpgce-motherhamster.org
