[linux-audio-user] TiMidity++ and FluidSynth

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Greetings:

  For all purposes these days TiMidity == TiMidity++. The original app 
is no longer developed by its original coder, nor has it been developed 
for years. There's no practical reason to go calling it TiMidity++. But 
if it makes you happy... ;)

Best regards,

== dp


Joerg Anders wrote:

>On Wed, 26 Nov 2003, Dave Phillips wrote:
>
>  
>
>>  TiMidity can be configured to use soundfonts. Here's the contents of 
>>my ~/timidity.cfg file :
>>
>>    
>>
>
>I would use TiMidity++. The problem is: In contrast to FluidSynth
>TiMidity loads the instruments not until they are really needed.
>
>That is: If the clarinet keeps silent for - say - 20 measures
>the clarinet waves are not loaded. In measure 20 TiMidity
>starts loading the clarinet. This requires processor time
>and leads to a short gap. (Also with my 2.4 GHz Intel)
>
>Does anybody know how to change this behaviour?
>
>And: Does anybody know how to recorord the FluidSynth
>aoutput into a WAV file ?
>
>  
>



[Index of Archives]     [Linux Sound]     [ALSA Users]     [Pulse Audio]     [ALSA Devel]     [Sox Users]     [Linux Media]     [Kernel]     [Photo Sharing]     [Gimp]     [Yosemite News]     [Linux Media]

  Powered by Linux