I think I missed the start of this thread. OK, googling for "pro patches light" turned up the original July 30th 2009 email.
I see the syntax you were using then is something like: 0, 2, 1, 1, 1, acpiano 1, 2, 1, 1, 1, britepno 2, 2, 1, 1, 4, synpiano Get rid of all the extra numbers and commas so that it looks like the following: 0 acpiano 1 britepno 2 synpiano > I have tried to place a timidity.cfg and a default.cfg file in the > folder with the patches, and tried to open it with Timidity from > options, but every time I try to play a midi, nothing happens and when I > restart Timidity it just says that it can't read the configuration file. If it says it can't read the configuration file, it might not be looking for it in the right place (bad config file syntax might be a different error message?). You can use the -c command line option when you run timidity to force it to look in the directory you want it to for the timidity.cfg file. So, use the "-c C:\Games\OldGames\ULTRASND\MIDI" option (minus quotes) to tell it to look for the timidity.cfg file in that directory. Or, on a Windows install, just put the timidity.cfg file in c:\windows instead of your patch directory, since that's where it will look by default. If you ever use the softsynth system driver, or the TWSYNTH softsynth binary, those will also default to looking in c:\windows\timidity.cfg. I would recommend just putting your timidity.cfg file in c:\windows rather than another directory. Keep the default.cfg file in the directory with your patches, though. In the timidity.cfg file, include the dir line to tell it where to find the patches and the default.cfg file, and a source line to use the default.cfg file: dir C:\Games\OldGames\ULTRASND\MIDI\ source default.cfg Then in your default.cfg file, have lines such as the following to map instrument filenames to instrument banks. If you leave off the .pat at the end of the filename, it will assume .pat, so you do not have to put .pat after every name. bank 0 0 acpiano 1 britepno 2 honky drumset 0 35 kick1 36 kick2 37 stickrim Use the "bank" and "drumset" lines to tell it which instrument banks and drumset banks the next block of assignments are for. In this case, they are defining the 0 banks, which are required for all midi. Hope this helps. -Eric On Sun, 7 Mar 2010, andy_blah wrote: > > I forgot to mention that I added quotes on the dir line, but that didn't fix > anything at all. So then it must be the instrument specification. I copied > it from an ini file in the patch folder so it must not be the correct one, I > don't know how to set the instrument list and didn't do it before either, > but I know I made it work once (but lost the config file and Timidity in an > hard disk failure). Is there anybody here that can help me fix this issue? > X.X > -- > View this message in context: > http://old.nabble.com/Pro-Patches-light-with-Timidity-tp24681080p27809913.html > Sent from the TiMidity++ - General mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Timidity-talk mailing list > Timidity-talk@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/timidity-talk > ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Timidity-talk mailing list Timidity-talk@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/timidity-talk
