Dave Fancella wrote:
>On Thursday 25 March 2004 12:27 pm, Dave Phillips wrote:
>>I use fluidsynth with three different fonts: the 8 MB set from Creative,
>>a set of fonts compatible with the Roland GS layout, and the big set
>>from Fluid. I haven't had any trouble with those sets.
>I found one that works alright, I forget what it's called though. It doesn't
>match the level of sound I get out of Timidity, though.
Well, to be precise, you're not getting any sound out of TiMidity,
you're getting it from whatever PAT or SF2 set TiMidity uses as its
default patch set.
I suggest taking a listen to the FluidR3 set. I'm not completely
satisfied with it, but its piano is outstanding, and to my ears the SF2
patches sound better than the PAT. But what appeals to you might not
float my boat, so "de gustibus.." as always.
You can find FluidR3 here :
Look for the link at the right side of the page. It's a rather large
download, I hope you have a broadband connection. :) Btw, the
uncompressed font is ~150 MB.
>>TiMidity does do soundfonts. Here's the contents of my ~/timidity.cfg :
>> soundfont /home/dlphilp/soundfonts/FluidR3_20GM.sf2
>>Works well here. Unfortunately TiMidity can be something of a CPU hog,
>>and I think fluidsynth handles patch changes better (especially during
>Timidity is a bit of a CPU hog. I don't want to trash talk FluidSynth,
>really. It just doesn't suit my needs, personally. I started midi composing
>a few weeks ago to write a game soundtrack, and the game uses SDL_mixer, so
>it uses an older version of Timidity to play midi files. Timidity is too
>much of a CPU hog for me to run it in conjunction with RoseGarden, so I use
>fluidsynth during composition. I frequently drop back to ecasound, which
>also uses Timidity to playback midi files, in order to hear the song as it
>will sound in the game. In the longer run, I think Timidity on a dedicated
>box (as much as it may sound like overkill) will better suit my personal
>studio/musical needs than FluidSynth, and Timidity on a dedicated box means
>CPU load is irrelevant.
Just out of curiosity: Why bother with ecasound's support for TiMidity,
why not just play your files via TiMidity itself ? (It is my preferred
MIDIfile player for Linux.)
TiMidity's CPU hogging is the main reason I use fluidsynth instead (my
CPU is a lowly 800 MHz Duron). And as I remarked, patch changes during
playback cause TiMidity to belch, I don't think it handles sample
caching very well.
>... If I could use Timidity's sample set with FluidSynth (and admittedly I
>haven't tried all that hard to do so), I'd probably do it. And if FluidSynth
>becomes a piece of software that will really work well in my personal studio,
>I'll happily make the switch.
AFAIK fluidsynth is designed to handle soundfonts and that's all.
>... Honestly, I haven't made a strong midi
>commitment yet, I'm still learning about the stuff. ;) But I am considering
>running Hydrogen next to Timidity on that dedicated box, so if it ever
>happens (it will happen this summer, or I'm in a lot of trouble for other
>reasons ;) ), I'll probably be looking at how to make hydrogen run headless
>as a midi slave.
I think that's a great idea. I can see running a few dedicated machines
as standalone synths, you don't need state-of-the-art CPU power for most
Linux softsynths, so building your own dedicated synth boxes could
likely be done on the cheap.
I've been corresponding with one user who has put DOSemu and Voyetra's
Sequencer Plus Gold on a Linux-powered laptop, the machine is dedicated
only to MIDI sequencing. He says he's aiming to use it in live
performance, he'll just start it up, it'll boot into a DOSemu session
running SPG, and he's ready to rock.
>... I'd hate to see Hydrogen depend on soundfonts, but having
>greater access to more file formats is always a good thing.
Well, it looks like Comix feels the same way. We'll all enjoy the
expansion of H's support for other file formats.