Jul 23, 2010 ZDoom configuration file, it should already point to your G/ZDoom folder, otherwise modify it to point to Timidity.exe. Open G/ZDoom, go into the sound options, and change the midi device to Timidity, then select 'Restart Sound'. Well, if it were me the first thing i would do is do a search for the timidity config file to see where it actually DID put it: find / -name timidity.cfg if that brings up nothing, then try and see where the program installed itself to after it was compiled and link it.
![Timidity Timidity](http://i.imgur.com/v0OaGKA.jpg)
- I use Timidity++ with the soundfonts CrisisGeneralMidi3.01.sf2 and SGM-V2.01.sf2, midi files never sounds so good before. Well, other programs like XMPlay supports soundfonts as well, but Timidity++ allows to disable a channel while playing (using the Tracer Window), which other players can't do. Great to disable the voice channel. This version (TiMidity++-2.14.0-w32-160604-1900) runs better on Windows 10 than older versions (Tracer Window looks better and refreshes more often).
- This is probably the best MIDI to WAV converter I've used - and I've used all of them.
- I used to work with an ancient TiMidity version I found someplace some years ago. Nothing creates a better sound when converting MIDI to wav and/or mp3. I'm really happy to find it here at sourceforge now and with this project a long lifespan! * Installation went flawlessly. No configuration needed. * Switing to my beloved eawpats (instead of freepats) needed changing just one line in timpp32g.ini. (This should be documented!)
- Really nice project! Thanks for your job!
Thank you.
With further reading I now have an improved understanding about MIDI. MIDI files basically are wrappers containing data how to play a sound file. Another mystery unveiled is that playing MIDI files requires a synthesizer for output. The synthesizer interprets the wrapper data to provide audio output.
Based upon this additional research, I asked the mods to move this thread to the Slackware forum because now I think the problems I am experiencing are Slackware related. This thread seems to have provide similar information (my apologies for not finding the thread when I posted ).
Additional information:
I can play MIDI files in my old NT4 box with Windows Media Player (WMP) 6.4. I have no problems playing MIDI files in NT4 with Winamp 2.95. Because both are universal Windows players, I suspect the software tools are using a software synthesizer.
That NT4 box is dual boot with Slackware 12.1. The box contains a Creative Soundblaster AWE64 sound card. My understanding is the AWE64 contains a hardware synthesizer.
Therefore, when I boot into Slackware 12.1 on that dual boot box, I should be able to play MIDI files but I am not.
Running aplaymidi -l on that dual boot box reveals many ports not available on my new box. In the dual boot box alsamixer shows a Synth volume option set to 90%. That leads me to believe I likely have ALSA configured correctly on that box. Therefore something else is not configured correctly.
My new box uses an on-board sound chip. The command line reports show a MPU-401 UART installed. Yet a UART is not a built-in synthesizer, just an interface. Additionally, based upon the command line outputs as shown in my original post, and my alsamixer output not showing a Synth volume setting, I have neither a hardware nor software synthesizer installed in the new box.
I prefer a global installation approach despite my dual boot box containing the AWE64 card. That is, any solution should support any of my computers regardless of the sound card (I have two more old boxes).
Although I prefer a global solution, I suspect in the dual boot box minimally I need only install and configure soundfonts. In my new box I need to install soundfonts and a software synthesizer. Please correct me if I am wrong.
I appreciate any help. Thanks.
With further reading I now have an improved understanding about MIDI. MIDI files basically are wrappers containing data how to play a sound file. Another mystery unveiled is that playing MIDI files requires a synthesizer for output. The synthesizer interprets the wrapper data to provide audio output.
Based upon this additional research, I asked the mods to move this thread to the Slackware forum because now I think the problems I am experiencing are Slackware related. This thread seems to have provide similar information (my apologies for not finding the thread when I posted ).
Additional information:
I can play MIDI files in my old NT4 box with Windows Media Player (WMP) 6.4. I have no problems playing MIDI files in NT4 with Winamp 2.95. Because both are universal Windows players, I suspect the software tools are using a software synthesizer.
That NT4 box is dual boot with Slackware 12.1. The box contains a Creative Soundblaster AWE64 sound card. My understanding is the AWE64 contains a hardware synthesizer.
Therefore, when I boot into Slackware 12.1 on that dual boot box, I should be able to play MIDI files but I am not.
Running aplaymidi -l on that dual boot box reveals many ports not available on my new box. In the dual boot box alsamixer shows a Synth volume option set to 90%. That leads me to believe I likely have ALSA configured correctly on that box. Therefore something else is not configured correctly.
My new box uses an on-board sound chip. The command line reports show a MPU-401 UART installed. Yet a UART is not a built-in synthesizer, just an interface. Additionally, based upon the command line outputs as shown in my original post, and my alsamixer output not showing a Synth volume setting, I have neither a hardware nor software synthesizer installed in the new box.
I prefer a global installation approach despite my dual boot box containing the AWE64 card. That is, any solution should support any of my computers regardless of the sound card (I have two more old boxes).
Although I prefer a global solution, I suspect in the dual boot box minimally I need only install and configure soundfonts. In my new box I need to install soundfonts and a software synthesizer. Please correct me if I am wrong.
I appreciate any help. Thanks.