You can subscribe to this list here.
2002 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2003 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
(8) |
Aug
|
Sep
(8) |
Oct
(6) |
Nov
(27) |
Dec
(5) |
2004 |
Jan
(4) |
Feb
(16) |
Mar
(22) |
Apr
(7) |
May
(5) |
Jun
(4) |
Jul
(20) |
Aug
(8) |
Sep
(8) |
Oct
(12) |
Nov
(19) |
Dec
(7) |
2005 |
Jan
(5) |
Feb
(46) |
Mar
(26) |
Apr
(18) |
May
(10) |
Jun
(22) |
Jul
(8) |
Aug
(3) |
Sep
(32) |
Oct
(9) |
Nov
(19) |
Dec
(7) |
2006 |
Jan
(20) |
Feb
(7) |
Mar
(10) |
Apr
(9) |
May
(23) |
Jun
(6) |
Jul
(6) |
Aug
(8) |
Sep
(7) |
Oct
(3) |
Nov
(8) |
Dec
(25) |
2007 |
Jan
(19) |
Feb
(9) |
Mar
(3) |
Apr
(2) |
May
(5) |
Jun
(6) |
Jul
(3) |
Aug
|
Sep
(3) |
Oct
|
Nov
(8) |
Dec
(1) |
2008 |
Jan
(7) |
Feb
|
Mar
(4) |
Apr
(34) |
May
(12) |
Jun
(1) |
Jul
(23) |
Aug
(6) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
2009 |
Jan
(17) |
Feb
(1) |
Mar
|
Apr
|
May
(2) |
Jun
(6) |
Jul
(30) |
Aug
(15) |
Sep
(7) |
Oct
|
Nov
(1) |
Dec
(7) |
2010 |
Jan
(7) |
Feb
(11) |
Mar
(6) |
Apr
(4) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
(4) |
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(12) |
Sep
(3) |
Oct
|
Nov
(1) |
Dec
|
2015 |
Jan
|
Feb
|
Mar
(3) |
Apr
|
May
(22) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2016 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
(3) |
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
(3) |
Nov
|
Dec
(2) |
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2021 |
Jan
|
Feb
(2) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2023 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Yale Z. <yzh...@gm...> - 2011-05-05 04:55:42
|
Timidity users, I have tried to install timiditydrv on Windows 7 x64 and it is copied to c:\windows\sysWOW64, but I don't see any Timidity++ synthesizer in my MIDI programs. I don't the driver listed in Device Manager. Then I tried manually installing it from Device Manager using the Have Disk option, but it refuses, saying no compatible drivers were found. The driver does install on Windows 7, 32bit. Does that mean timiditydrv doesn't support Windows x64, or can I fix it by downloading the sources and build the DLL for x64? |
From: A. Z. <and...@co...> - 2011-04-05 04:01:33
|
On Mon, 4 Apr 2011 23:26:29 -0400 "A. Zimmer" <and...@co...> wrote: > > Does anyone know where the ZSF GigaPack soundfont collection can be > obtained? This collection is 6.4 Gigabytes in size and contains > virtually all the free SF2 soundfonts that were ever made available. > After some more searching, I find that this is only a partial collection. The complete set of soundfonts is called the "ZSF Distribution" and contains 39 Gigabytes worth of free soundfonts. For anyone who may be interested, the best torrent for the ZSF Distribution seems to be here: http://isohunt.com/torrent_details/110681649/?tab=summary These soundfonts are in the public domain (no copyrights) and the download is perfectly legitimate. Again, if anyone knows of an alternate source, please let us know. Andrew Zimmer |
From: A. Z. <and...@co...> - 2011-04-05 03:26:47
|
Hello, Does anyone know where the ZSF GigaPack soundfont collection can be obtained? This collection is 6.4 Gigabytes in size and contains virtually all the free SF2 soundfonts that were ever made available. There are a few torrents for this collection, but there are almost no seeders and it would take months, if ever, to download as a torrent. I was hoping that maybe Rapidshare, Megaupload, or a similar file sharing site has the collection. This GigaPack ZSF collection would make an excellent source for TiMidity++ soundfonts. If anyone knows of a repository for it please let us know. Andrew Zimmer |
From: Matthew <cra...@ya...> - 2011-03-13 11:44:28
|
That doesn't install ttymidi though. Salvador, how far did you get? Download the file ttymidi.tar.gz. Change to the directory you downloaded it in. Then tar xvf ttymidi.tar.gz cd ttymidi more README You will see it tells you how to compile it: gcc ttymidi.c -o ttymidi -lasound And if this doesn't work, you need to install the alsa development package and try again: sudo apt-get install libasound-dev (I've added sudo to that one as you need to do it as root.) You should then end up with the executable called ttymidi. You can run that from where it is with ./ttymidi Or if you want to install it so that you can run it like any other command: sudo cp ttymidi /usr/local/bin It will then be in your path, so you won't have to point at it directly. I assume this all works under 64-bit. --- On Sun, 13/3/11, pe...@o2... <pe...@o2...> wrote: From: pe...@o2... <pe...@o2...> Subject: Re: [timidity-talk] question To: "salvador allende" <sal...@gm...> Cc: tim...@li... Date: Sunday, 13 March, 2011, 10:11 Hello, try this: $ sudo apt-get install timidity Best regards, Piotr. salvador allende pisze: > hi > > how do i install ttymidi in ubuntu 10.10 64 bit, i read instructions > but i have no idea of what are they talking about > > thanxxxxxxxxx > > -- > ´´Vale la pena morir por todo aquello sin lo cual no vale la pena > vivir, Salvador Allende´´ > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > ------------------------------------------------------------------------ > > _______________________________________________ > Timidity-talk mailing list > Tim...@li... > https://lists.sourceforge.net/lists/listinfo/timidity-talk > ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Timidity-talk mailing list Tim...@li... https://lists.sourceforge.net/lists/listinfo/timidity-talk |
From: David F. <df...@an...> - 2011-03-13 11:22:08
|
Do you want ttymidi or timidity? ttymidi allows you to use the output from a USB or RS232 midi controller/instrument to connect to the midi inputs in software like jack-connection-kit ALSA etc. timidity++ is a midi to wav converter program to use if your sound card has no built in synthesiser. Hope this helps. David On 12/03/11 15:46, salvador allende wrote: > hi > > how do i install ttymidi in ubuntu 10.10 64 bit, i read instructions > but i have no idea of what are they talking about > > thanxxxxxxxxx > > -- > ´´Vale la pena morir por todo aquello sin lo cual no vale la pena > vivir, Salvador Allende´´ > > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > > > _______________________________________________ > Timidity-talk mailing list > Tim...@li... > https://lists.sourceforge.net/lists/listinfo/timidity-talk |
From: <pe...@o2...> - 2011-03-13 10:12:19
|
Hello, try this: $ sudo apt-get install timidity Best regards, Piotr. salvador allende pisze: > hi > > how do i install ttymidi in ubuntu 10.10 64 bit, i read instructions > but i have no idea of what are they talking about > > thanxxxxxxxxx > > -- > ´´Vale la pena morir por todo aquello sin lo cual no vale la pena > vivir, Salvador Allende´´ > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------------ > Colocation vs. Managed Hosting > A question and answer guide to determining the best fit > for your organization - today and in the future. > http://p.sf.net/sfu/internap-sfd2d > ------------------------------------------------------------------------ > > _______________________________________________ > Timidity-talk mailing list > Tim...@li... > https://lists.sourceforge.net/lists/listinfo/timidity-talk > |
From: salvador a. <sal...@gm...> - 2011-03-12 15:46:57
|
hi how do i install ttymidi in ubuntu 10.10 64 bit, i read instructions but i have no idea of what are they talking about thanxxxxxxxxx -- ´´Vale la pena morir por todo aquello sin lo cual no vale la pena vivir, Salvador Allende´´ |
From: Thomas K. <tk...@gi...> - 2011-02-14 18:03:36
|
Hi! png-1.5 hides structure members from public view. For this reason, some code doesn't compile any more. The attached patch fixes this problem in TiMidity++-2.13.2. I'm not sure where else to send this, since TiMidity++ doesn't really look maintained nowadays. Cheers, Thomas |
From: Claus L. W. <cl...@ge...> - 2010-09-26 18:41:30
|
I can only find this when googling and it doesn't work on my mac. timidity/newton_tables.c is never created. Does anyone have a description for compiling timidity? I downloaded build_for_iphoneos.sh alright and made it executable. No problem. Claus ****************************** 1. cd to the extractd TiMidity++ folder 2. build_for_iphoneos simulator This will fail 3. Copy timidity/newton_tables.c somewhere safe. 4. make clean 5. build_for_iphoneos device 6. Manually edit timidity/makefile and remove all references to DAU_DARWIN and darwin_a 7. Copy newton_tables.c back into the timidity subfolder and touch it 8. make |
From: Bob v. d. P. <bo...@me...> - 2010-05-22 02:12:57
|
I'm trying to get my laptop set up for gigging so got a little USB audio device. It seems to be fine with PulseAudio and sounds much better than the built-in audio on the laptop. I can set set pulseaudio to use the USB and problems like aplay and rhythmbox use it. No problem. But, timidity (from a command line) just continues to play though the internal card. I can bypass with a command: timidity file.mid -Ow -o - | aplay and this works okay. It might be a good solution since aplay always seems to select the "correct" port. Only problem is that I do get a message (I think from timidity) "Illegal Seek: Can't make valid header". Probably save to ignore. I'm looking for a selector in timidity to pick the audio port? Oh ... just figured it out. If I use -Oa it works just fine since this sends it to the alsa port. I'll post the message anyway just in case I forget or someone else is stuck. -- **** Listen to my CD at http://www.mellowood.ca/music/cedars **** Bob van der Poel ** Wynndel, British Columbia, CANADA ** EMAIL: bo...@me... WWW: http://www.mellowood.ca |
From: SATO K. <ke...@ps...> - 2010-05-17 13:04:55
|
Thank you for the patch Eric. It's been merged to CVS. 2010/2/21 Eric Welsh <ew...@bi...>: > I have attached a diff (readmidi_xg_sysex.diff) to fix a bug with > interpreting XG SYSTEM ON SYSEX events. > > playmidi.c: Allow Device Numbers other than 0x10 for XG SYSTEM ON SYSEX events > > See comments in diff for longer explanation. All my XG midi files play > fine in server mode now. > > ----- > > I am also resubmitting an anti-popping patch I submitted a few months ago > (mix_fix_amps.diff) after a discussion on this list. > > mix.c: Fix existing anti-popping minimum volume ramps for expression, > volume, pans, etc.. Extend anti-popping minimum volume ramps to > envelope amp changes. > > > In adding the envelope volume ramps, I found that I had mis-implemented > the original "reduce popping" code in compute_mix_smoothing() many years > ago. The previous 0.5 msec comment was wrong, since the code was > effectively working over 20 msec and I only *thought* it was 0.5 msec from > my incorrectly written code. Looking at WAV output in a sample editor > confirms this. I have changed the calculation to correctly take the > control_ratio into account, and changed the comment to reflect the actual > minimum ramp time. > > I was originally hesitant to add anti-popping minimum volume ramp times to > envelope calculations, since they would add very minor delays to extremely > fast envelope rates. However, saner minds convinced me that this was a > good idea for the following reasons: > > 1) 20 msec is very short to begin with > 2) It has been used for expression, volume, and pan changes for many years > with no noticible problems. > 3) Most GUS instruments have rates longer than this anyways, so they > would not be affected at all. > 4) I think the GUS PAT loader checks for missing envelope rates and sets > them to defaults that are longer than 20 msec. > 5) This effectively adds some reasonable defaults to soundfonts if the > envelope rates are missing (which is not uncommon). > 6) Other software synthesizers and real hardware do not have popping > problems with soundfonts that are missing envelopes. They must be > adding their own volume ramps to envelope changes to avoid these pops. > Therefore TiMidity++ should too, so that it can have soundfont support > that is more compatible with other players/hardware. > 7) Enforcing minimum envelope times should avoid other unforseen popping > problems in the future. > > I fully support adding minimum volume ramp times to envelopes now. > > -Eric > ------------------------------------------------------------------------------ > 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 > Tim...@li... > https://lists.sourceforge.net/lists/listinfo/timidity-talk > > |
From: Rustom M. <rus...@gm...> - 2010-04-18 02:23:59
|
I am resending the mail I sent under subject: tuning file format Summary: tuning timidity works on linux NOT on Windows. If there is some other (gui-based) way of specifying the tuning file to timidity please let me know There are any people on the tuning list who would be interested in knowing --------------------------Earlier mail resent --------------------- Ok So heres whats (finally) worked for me: 1. In scala choose the scale you want [There are zillions of scales available in scala and all kinds of ways of making them. Ive attached ET and an exaggerated Just to see (hear) the difference 2. set synth to timidity using -Z option (option 117) Many ways of doing this eg. a. GUI way Edit -> Prefs -> Midi-tab Synth tuning options(Send) choose model 117 (it should say timidity via -Z option text file [GUI way does now seem to work in windows] b. a simpler (non gui) way is the command set synth 117 3. Click send on toolbar scala should respond with Timidity, via -Z option text file: this model exports a text file, save instead? Say yes and give the name of a tuning file say mytuning.tbl 4. [Out of scala at a shell] timidity -Z mytuning.tbl music.mid should now play the music with the new tuning NOTE: timidity works in linux not on windows; ie the timidity command line on windows sounds the same with and without the -Z option whereas it is expectedly different in linux Whereas scala gives low-level errors on linux when it tries to spawn external programs on linux not windows. In the workflow I am using above I dont need those spawn commands Files Attached cminor.midi -- for trial exaji.scl -- should be audibly different ET.scl -- should be same as untuned exaji.tbl -- scala's converted scl file to timidity tbl format For windows you may try converting it to Dos (LF -> CR LF) -- still does not work |
From: Yair K. <ce...@gm...> - 2010-04-16 05:36:22
|
On Wednesday 14 April 2010 14:02:48 Rustom Mody wrote: > Hello. > > I have been trying to tune timidity to various temperaments, just > intonation etc. For now I have been able to use the -Zpure option (for > just > intonation) and the usual (no -Z) for equal temperament. > > However the man page suggests that timidity can take an arbitrary user > specified tuning file. > but it does not say anything about that file's format. > > Any tips on how that file is to be written? > There's a gentable perl script in the timidity-tools package which can generate the tuning tables. I have attached it. Yours, Yair K. |
From: Rustom M. <rus...@gm...> - 2010-04-14 11:03:09
|
Hello. I have been trying to tune timidity to various temperaments, just intonation etc. For now I have been able to use the -Zpure option (for just intonation) and the usual (no -Z) for equal temperament. However the man page suggests that timidity can take an arbitrary user specified tuning file. but it does not say anything about that file's format. Any tips on how that file is to be written? Thanks Rustom |
From: andy_blah <and...@gm...> - 2010-03-07 10:55:58
|
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-tp24681080p27810552.html Sent from the TiMidity++ - General mailing list archive at Nabble.com. |
From: andy_blah <and...@gm...> - 2010-03-07 10:50:15
|
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. |
From: Eric W. <ew...@bi...> - 2010-03-07 10:49:18
|
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 > Tim...@li... > https://lists.sourceforge.net/lists/listinfo/timidity-talk > |
From: andy_blah <and...@gm...> - 2010-03-07 08:52:38
|
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. |
From: SATO K. <ke...@ps...> - 2010-03-07 06:41:12
|
2010/3/6 andy_blah <and...@gm...>: > I still am unable to fix this issue, is nobody able to help me with this? You should use the right syntax that TiMidity++ understands for .cfg. Regards, Kentaro Sato. |
From: andy_blah <and...@gm...> - 2010-03-06 11:29:19
|
andy_blah wrote: > > I have been trying to use Pro Patches light (a replacement .pat set for > the Gravis Ultrasound) with the Windows Timidity (the version from this > site: http://timidity.s11.xrea.com/index.en.html#down). 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. Could somebody help me > make Timidity work with those patches? Both timidity.cfg and default.cfg > contain this: > > dir C:\Games\OldGames\ULTRASND\MIDI\ > > > I have uploaded the patch set here, so you could take a look: > http://www.megaupload.com/?d=4R3CLFE1 > I still am unable to fix this issue, is nobody able to help me with this? -- View this message in context: http://old.nabble.com/Pro-Patches-light-with-Timidity-tp24681080p27803623.html Sent from the TiMidity++ - General mailing list archive at Nabble.com. |
From: Eric W. <ew...@bi...> - 2010-02-24 07:57:53
|
On Tue, 23 Feb 2010, Chuck Cochems wrote: > Notably no card that uses .sf2 seems to support portmenteau controller, > even though GS and XG standard both require it's support. > > If you wish to make a GS compliant timdity++, you must include this > controller. Sorry, I hadn't looked over that part of the src code in a while (years). It looks like there is a hell of a lot of code for portamento support in playmidi.c, readmidi.c, resample.c, and other places, as well as command line options for it. As far as I can tell, TiMidity should already have support for portamento. Could you send me an example midi file that uses portamento so that I can test it? Looking over the code, it looks like there is a lot of code already there for LFOs, low pass filters, and resonance filters too. -Eric |
From: Eric W. <ew...@bi...> - 2010-02-24 06:42:05
|
On Tue, 23 Feb 2010, Chuck Cochems wrote: > Current method is absolutely horrible. It ONLY seems to load bank 0 from > the soundfont, and ignore all others, at least in the standalone player > I tried. I'll agree that TiMidity has issues with sf2 instrument loading.... But, given the history of the program, I don't think it is too horrible. TiMidity started out around 1995 or so using GUS .pat files from the Gravis Ultrasound. The GUS used a gravis.cfg file to map individual instrument files to each midi instrument number. There were no "banks" that you could just swap in and out, it was all specified in gory detail in the gravis.cfg file. TiMidity worked the same way, since the GUS was the standard consumer grade midi card at the time. SF2 support was added much later on top of the PAT support. I look at TiMidity more as a GUS .pat file player that includes some SF2 support. Although just specifying "soundfont whatevername.sf2" in a .cfg file doesn't seem to handle the non-0 banks properly, it *IS* possible to get TiMidity to use all the drumsets and SFX banks correctly. It's just painful the way I have done it on my system. I don't know if there is a better way or not, I've always just used .pat files, I didn't really get into SF2 until I started merging FreePats with FluidR3 over the weekend via config files. You can use sf2 files in the gravis.cfg and various other .cfg files similar to how you would use .pat files. You can specify each individual bank and each individual instrument within each bank, like the following: # loads instruments 49-51 from sf2 bank 0 into timidity bank 0 bank 0 49 %font "FluidR3_GM.sf2" 0 49 # String Ensemble 2 Slow 50 %font "FluidR3_GM.sf2" 0 50 # Synth Strings 1 51 %font "FluidR3_GM.sf2" 0 51 # Synth Strings 2 # loads drums 29-30 from sf2 bank drumset 0 into timidity drumset 0 # drumset loading from sf2 files is denoted with an extra 128 before the # bank/instrument drumset 0 028 %font "FluidR3_GM.sf2" 128 0 28 pan=-21 # Slap 029 %font "FluidR3_GM.sf2" 128 0 29 pan=-19 # Scratch 1 push 030 %font "FluidR3_GM.sf2" 128 0 30 pan=-19 # Scratch 2 pull You can define other banks and drumsets as well, like GS drumsets 8, 16, 24, 25, 26, 32, 40, 48, 49, 50, etc.. You can define GS SFX drumsets 56 and 127 too. Proper XG bank support is much more complicated, but is also possible to configure given the right .cfg file syntax. Yes, it's a lot of work to specify a line for every single bank and instrument (however, extra banks only need instruments that differ from bank 0, they will automatically fall back to bank 0 if missing). But, if they are already in a single sf2 file, it's really easy to just copy/paste a bunch of lines then go down the list and change the instrument numbers one at a time to specify each instrument separately. It's a little tedious... but doable. Once you have a .cfg file for the bank you want, you can then edit your timidity.cfg file to source that .cfg file, or a different one if you want to use a different instrument configuration. This would sort of work as a "bank change". I agree that the SF2 support isn't so great.... SF2 bank loading should be fixed to handle non-0 banks more easily, so that all it takes is a single "soundfont" line to correctly load the entire set of banks. Loading behavior also needs to be fixed so that instruments loaded later properly overwrite instruments loaded earlier (including PAT files). I think most of the problems stem from the behavior of the "soundfont" directive. SF2 loading seems to behave as expected when used on a per-instrument basis with the %font directive. I suspect the code that handles the soundfont directive might be the first place to look to see where the problems might be? Thank you for bringing this problem to the developers' attention. > Also the engine should support all awe32 sysex and NRPN Mainly tis means > GS sysex for reverb and chorus, and nrpn to control the LFOs and the > resonant filter. TiMidity actually DOES support most of the GS and XG SYSEX events, including chorus and reverb levels on a per-channel basis. The chorus and reverb might not sound as good as you'd like, but the support IS there, it's just the chorus and reverb engines that need some work. You may have to enable chorus and reverb support in the preferences, I'm not sure if they default to ON or not. Special audio effects, such as reverb, chorus, variation, etc. are probably the most difficult thing to add to a midi player. Once the special effects engines are written, adding the support for the SYSEX events is easy. Since special effects are hard to implement, it just hasn't happened, or if it has, the quality may not be as good as what you've come to expect from commercial solutions. Hey, it's free software written by people in their free time as a hobby, don't be surprised if it doesn't have all the features of a Roland or Yamaha sound module.... I don't think TiMidity has any linear frequency oscillators at all. Nor do most other softsynths, or even consumer level hardware for that matter. Since pretty much nothing else currently supports this either, I don't see much of a problem with it being missing.... > You want to play some final fantasy 7 awe midi files. :) I used to have a Yamaha SW60XG ISA card. It was awesome. I bought FF7 for PC and didn't need the included Yamaha S-YXG50 softsynth (for Win95/98/ME), since I already had the real hardware that was better. FF7 sounded great. GS and XG midi sounded great. I added XG support to TiMidity and it sounded ... not too bad once all the instrument changing SYSEX events were supported and configured. I can confidently say that, apart from special audio effects such as LFO and Variation, TiMidity does a good job of supporting GS and XG instruments and instrument changing SYSEX events, enough to play back midi that sound reasonable, as opposed to playing with all the wrong instruments due to missing the SYSEX instrument and drumset change events. TiMidity sounds WAY better than my Audigy ever did, since it didn't support GS or XG at all (at least not that I could tell). It couldn't even handle 2 drum channels, much less SFX drum channels. TiMidity's support is still more GS and XG support than almost every other solution out there. If you want near-perfect GS and XG support, your best bet it to aquire an old copy of Yamaha's S-YXG50 softsynth if you are running XP. The latest version you could get from Yamaha was 4.23.14, which was a WDM driver that was supposed to work under XP (but I could never get it to work). If you are running XP, you can download the Microsoft Windows Update 1403848.cab, which includes an even newer version, WITH the 4 meg ROM instead of the standard 2 meg ROM. Extract the CAB file with WinZip or something like that, then Add New Hardware the driver. Since it doesn't have an installer to create the registry entries, you'll need to add them yourself if you didn't install 4.23.14 from Yamaha beforehand (and use Update Driver under Device Manager). See the following link for details: http://www.wiki-mirror.us/wiki/Software_synthesizer It even works as an MPU-401 device under DosBox, so that great DOS midi players such as MegaMid v1.66 work perfectly :) Lucas Arts adventure games also sound very nice with it using ScummVM. I am currently running it, and I can say that it sounds almost as good as my SW60XG did on all my XG midi. It has a few issues with the volume being set too high internally so that it over-amplifies outside the 16-bit sample range and pops/crackles every now and then with really effects-loaded midi, but overall it sounds pretty good. WAY WAY better than the default Microsoft GS softsynth. If you are running Vista, there really isn't much in the way of software GS or XG support. Yamaha is currently selling software called MidRadio, but only in Japanese, and apparently only as a file player. It uses a crippled softsynth that only supports XG-Lite (no variation effects), but has a larger (11 meg) instrument bank than the S-YXG50 (4 meg, same as the SW60XG). There is a hack to turn the demo version into a VSTi plugin that you can be used with midi software that supports VSTi plugins, something even the full commercial version can't do. I found some full instructions over the weekend for how to do that, but I can't find the link at the moment. I'm running XP, so the S-YXG50 is good enough for me for now, especially since it works as a full blown Windows MIDI driver. > Notably no card that uses .sf2 seems to support portmenteau controller, > even though GS and XG standard both require it's support. If it isn't made by Roland or Yamaha, it probably doesn't have much of any GS or XG support at all :( I can't blame Creative or other consumer sound card makers, there just isn't much demand for it. I *can* however blame Roland and Yamaha. Damn them for discontinuing their consumer-level product lines *AND* their Windows software synthesizers. > If you wish to make a GS compliant timdity++, you must include this > controller. In theory, it should be possible to implement it in TiMidity, especially since it already implements portamento in MOD files. But the MOD engine is completely separate and just emits a series of internal pitch bend events to create the portamento effect, which is a bit of a hack. I think the best solution would be to implement something similar to how instrument envelopes are currently implemented. Add a voice variable that detunes the pitch by X amount. Add a separate variable that tells it how much to increment the first variable per time slice. Add a third variable that tells it at which point to stop (once the detune value has been reached). When a portamento event is issued, calculate the increment rate and endpoint for the detuning, then pass the modified detuned frequency to the resampling functions that are already used to change sample pitch. Three new variables to add to the voice data structure, a new function to write to calculate/set them on a portamento event, some extra code to write to increment the detuning value each timeslice. Cached pre-resampled notes would also need to be disabled for notes affected by a portamento. I think I mostly know which functions and data structure would need to be edited. This sounds quite doable to me. But, I don't have time for it at the moment, and I don't know about other developers. Thank you for bringing this to our attention, though. I wasn't aware that there was much need or demand for portamento support. I'd never seen it used in a midi file before. -Eric |
From: Chuck C. <za...@td...> - 2010-02-24 02:17:49
|
Here's how it should work. I speak as an ex AWE32 owner. You can load a soundfont bank as a *main bank*, or as a *user bank*. If you load a soundfont as a main bank it will load every instrument to the bank specified. If you load it as a a USER bank, you specify a bank offset to add to all non drumkit banks. Say you have your GM bank loaded. You want to play some final fantasy 7 awe midi files. :) To play them, you load the ff7 awe soundfont (well a fixed version which includes the ROM samples) into bank 1 as a user bank, like you owuld on your real awe32. it contains banks 0 through 8, and some drumkits in bank 128. So, you would load this as "user bank 1". (the final fantasy 7 pc game does exactly this just before the game starts) This would map 0 inside this new soundfont to bank 1 in your existing setup, 1 to 2, 2 to 3, etc. overwriting any existing instruments at this point. But bank 128 would stay as bank 128, and all of the final fantasy 7 drumkits (of which there are about 10-12) will overwrite any existing drumkits. Current method is absolutely horrible. It ONLY seems to load bank 0 from the soundfont, and ignore all others, at least in the standalone player I tried. Also the engine should support all awe32 sysex and NRPN Mainly tis means GS sysex for reverb and chorus, and nrpn to control the LFOs and the resonant filter. Notably no card that uses .sf2 seems to support portmenteau controller, even though GS and XG standard both require it's support. If you wish to make a GS compliant timdity++, you must include this controller. |
From: Eric W. <ew...@bi...> - 2010-02-20 18:20:35
|
On Sat, 6 Feb 2010, / ririka_sos / wrote: > >>> XG reset event problem in server mode. Â As it is now, I'm only able to > >>> build the standard player with cygwin+mingw32. > > If you're talking about building twsyng binary, > MinGW(5.1.4/5.1.2) + Msys(1.0.11-2004.04.30-1) may help you. > # tested with TiMidityCVS080327, bit older version. > ./configure --enable-winsyn --enable-winsyng I installed MinGW + MSYS, ran configure with the appropriate options, and TWSYNTH compiled and ran fine. Big thanks! > If you set "--enable-w32gui" in addition to "--enable-winsyn --enable-winsyng", > configure passes, but built in failure. I got the Windows MIDI driver to build by using --enable-windrv instead of --enable-winsyng. It, too, needs to configure and compile all by itself, you evidently can't build TWSYNTH and the driver at the same time. Driver works great. TWSYNTH is nice for debugging, though, since I don't have to reboot every time I recompile :) Looks like my problems were all coming from trying to use cygwin to cross-compile in MinGW mode (-mno-cygwin flag). A pure MingGW build environment fixed everything. ----- I have attached a diff (readmidi_xg_sysex.diff) to fix a bug with interpreting XG SYSTEM ON SYSEX events. playmidi.c: Allow Device Numbers other than 0x10 for XG SYSTEM ON SYSEX events See comments in diff for longer explanation. All my XG midi files play fine in server mode now. ----- I am also resubmitting an anti-popping patch I submitted a few months ago (mix_fix_amps.diff) after a discussion on this list. mix.c: Fix existing anti-popping minimum volume ramps for expression, volume, pans, etc.. Extend anti-popping minimum volume ramps to envelope amp changes. In adding the envelope volume ramps, I found that I had mis-implemented the original "reduce popping" code in compute_mix_smoothing() many years ago. The previous 0.5 msec comment was wrong, since the code was effectively working over 20 msec and I only *thought* it was 0.5 msec from my incorrectly written code. Looking at WAV output in a sample editor confirms this. I have changed the calculation to correctly take the control_ratio into account, and changed the comment to reflect the actual minimum ramp time. I was originally hesitant to add anti-popping minimum volume ramp times to envelope calculations, since they would add very minor delays to extremely fast envelope rates. However, saner minds convinced me that this was a good idea for the following reasons: 1) 20 msec is very short to begin with 2) It has been used for expression, volume, and pan changes for many years with no noticible problems. 3) Most GUS instruments have rates longer than this anyways, so they would not be affected at all. 4) I think the GUS PAT loader checks for missing envelope rates and sets them to defaults that are longer than 20 msec. 5) This effectively adds some reasonable defaults to soundfonts if the envelope rates are missing (which is not uncommon). 6) Other software synthesizers and real hardware do not have popping problems with soundfonts that are missing envelopes. They must be adding their own volume ramps to envelope changes to avoid these pops. Therefore TiMidity++ should too, so that it can have soundfont support that is more compatible with other players/hardware. 7) Enforcing minimum envelope times should avoid other unforseen popping problems in the future. I fully support adding minimum volume ramp times to envelopes now. -Eric |
From: SATO K. <ke...@ps...> - 2010-02-07 06:04:11
|
2010/2/7 Eric Welsh <ew...@bi...>: > On Sat, 6 Feb 2010, / ririka_sos / wrote: > Thanks. twsyng might work for debugging purposes, but I'd like to > eventually build the timiditydrv.dll that can be installed as a system > midi device (without having to launch twsyng.exe and have it sit in the > background). Oh I too assumed twsyng, still I think VC++EE would be worth trying. Regards, Kentaro Sato. |