Eric Welsh wrote:
>
> 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
>
Thank you very much for the reply, it finally cleared out the confusion
about timidity.cfg and default.cfg, didn't knew the first had to contain a
specification to use the latter, and that one to contain the patch list
instead. And also the Timidity issue is now cleared too! :)
For anybody that had my problem, here is what the default.cfg must contain
(for Pro Patches Light or for the standard GUS patches):
bank 0
0 acpiano
1 britepno
2 synpiano
3 honky
4 epiano1
5 epiano2
6 hrpschrd
7 clavinet
8 celeste
9 glocken
10 musicbox
11 vibes
12 marimba
13 xylophon
14 tubebell
15 santur
16 homeorg
17 percorg
18 rockorg
19 church
20 reedorg
21 accordn
22 harmonca
23 concrtna
24 nyguitar
25 acguitar
26 jazzgtr
27 cleangtr
28 mutegtr
29 odguitar
30 distgtr
31 gtrharm
32 acbass
33 fngrbass
34 pickbass
35 fretless
36 slapbas1
37 slapbas2
38 synbass1
39 synbass2
40 violin
41 viola
42 cello
43 contraba
44 tremstr
45 pizzcato
46 harp
47 timpani
48 marcato
49 slowstr
50 synstr1
51 synstr2
52 choir
53 doo
54 voices
55 orchhit
56 trumpet
57 trombone
58 tuba
59 mutetrum
60 frenchrn
61 hitbrass
62 synbras1
63 synbras2
64 sprnosax
65 altosax
66 tenorsax
67 barisax
68 oboe
69 englhorn
70 bassoon
71 clarinet
72 piccolo
73 flute
74 recorder
75 woodflut
76 bottle
77 shakazul
78 whistle
79 ocarina
80 sqrwave
81 sawwave
82 calliope
83 chiflead
84 charang
85 voxlead
86 lead5th
87 basslead
88 fantasia
89 warmpad
90 polysyn
91 ghostie
92 bowglass
93 metalpad
94 halopad
95 sweeper
96 aurora
97 soundtrk
98 crystal
99 atmosphr
100 freshair
101 unicorn
102 echovox
103 startrak
104 sitar
105 banjo
106 shamisen
107 koto
108 kalimba
109 bagpipes
110 fiddle
111 shannai
112 carillon
113 agogo
114 steeldrm
115 woodblk
116 taiko
117 toms
118 syntom
119 revcym
120 fx-fret
121 fx-blow
122 seashore
123 jungle
124 telephon
125 helicptr
126 applause
127 pistol
drumset 0
27 highq
28 slap
29 scratch1
30 scratch2
31 sticks
32 sqrclick
33 metclick
34 metbell
35 kick1
36 kick2
37 stickrim
38 snare1
39 claps
40 snare2
41 tomlo2
42 hihatcl
43 tomlo1
44 hihatpd
45 tommid2
46 hihatop
47 tommid1
48 tomhi2
49 cymcrsh1
50 tomhi1
51 cymride1
52 cymchina
53 cymbell
54 tamborin
55 cymsplsh
56 cowbell
57 cymcrsh2
58 vibslap
59 cymride2
60 bongohi
61 bongolo
62 congahi1
63 congahi2
64 congalo
65 timbaleh
66 timbalel
67 agogohi
68 agogolo
69 cabasa
70 maracas
71 whistle1
72 whistle2
73 guiro1
74 guiro2
75 clave
76 woodblk1
77 woodblk2
78 cuica1
79 cuica2
80 triangl1
81 triangl2
82 shaker
83 jingles
84 belltree
85 castinet
86 surdo1
87 surdo2
--
View this message in context:
http://old.nabble.com/Pro-Patches-light-with-Timidity-tp24681080p27810522.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
