1621
SCI Development Tools / Re: Script issues with Companion
« on: June 02, 2007, 02:01:39 AM »
Ah, many thanks! Didn't even know that file existed. Yeah, automatic would be nice. Thanks for the help.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Well, that goes quite beyond my capabilities at the moment. Why the need for a custom General MIDI driver? Why not just use the gm.drv and then everyone knows which instruments are which? You said General MIDI was no good for some reason?
That may very well be. The Adlib and Yamaha sound fine. How do I fix it?I wouldn't say it's something that needs fixing. I assume you're using Sierra games to test the sound previewing, right? I don't think there's any way to translate Sierra game stuff to General MIDI since every Sierra game has a completely different instrument patch list and sometimes have instruments or sound effects that you just can't find a General MIDI alternative for. Even if you succeeded for one game it wouldn't work for another. What the program at the top of this thread has is a drop down list where you can select whichever format you want (Yamaha, MT32, General MIDI which SCI0 games don't have unless a General MIDI patch and driver is created for fangames, Digital also which SCI0 doesn't have, and adlib/sound blaster) and then you pick the MIDI output in the program settings and it just puts whatever you've selected in the output you've selected. I say keep it that way. Don't try to translate into General MIDI because it's impossible for every game. Go the route of making a custom General MIDI driver and patch specifically for fangames. But don't let the program translate anything.
Not sure what you're asking here... a way to make custom patches?
SMF 2.0.19 |
SMF © 2021, Simple Machines
Simple Audio Video Embedder
Page created in 0.103 seconds with 21 queries.