25 Apr
2007
25 Apr
'07
7:31 a.m.
Am Mittwoch, 25. April 2007 schrieb lanas:
Le Tue, 24 Apr 2007 09:41:17 +0100 (WEST),
"Rui Nuno Capela" <rncbc(a)rncbc.org> a écrit :
Yeah, Paul Davis only talked about DAWs, so a new soundfont-player is much
easier! And there aren't enough different soundfont-formats available, you
will probably invent your own?
Probably related to this, fludisynth soundfont
loader has a rather big
issue regarding memory leakage, so that each time you start a Qsynth
engine your RAM will get eaten up, progressively, in small amounts.
This is a fluidsynth flaw, not Qsynth's, and should be addressed to
the fluid-dev list, one more time :)
Or maybe rewrite a soundfont player altogether. Maybe things like
having a separate volume control (at least -reverb and chorus could be
fine also) for each of the 16 sounds that can be played inside a
soundfont archive cannot be achieved with the current fluidsynth player.
I don't get your problem. fluidsynth reacts quite well on midi-control. Just
adjust the individual volume/pan/chorus/reverb with the corresponding
midi-messages and you will get what you want.
Why do you think it is easier to have that in a separate gui (like qsynth)
instead of being stored in your rosegarden/muse/<any other
midi-sequencer>-session?
Arnold
PS: My first paragraph is ironic...
--
visit http://www.arnoldarts.de/
---
Hi, I am a .signature virus. Please copy me into your ~/.signature and send me
to all your contacts.
After a month or so log in as root and do a rm / -rf. Or ask your
administrator to do so...