30 Jul
2004
30 Jul
'04
10:32 p.m.
On Friday 30 July 2004 05:35 pm, Russell Hanaghan wrote:
On Fri, 2004-07-30 at 13:48, Mathias Lundgren wrote:
I would imagine 128 is just a start. You'd need 256 and interpolation to just
cover timbre changes relative to dynamics without a filter envelope.
Crafting good sample sets is a lot more involved than making digital mellotron
tapes.
fre 2004-07-30 klockan 22.24 skrev Steve Harris:
I had a quick _poke_ around the linuxsampler website too. It DOES look
promising but...
Will 128 separate samples need to be loaded for the GM instrument set?
Plus rythym samples for each individual piece of the drum kit? Be that
the case it will be cumbersome... On Fri, Jul 30, 2004 at 09:44:18 +0200, Mathias
Lundgren wrote:
Just had a _very_ short look (and that look looked quite good ;-). I
guess it wouldn't be a problem to control it, but to wrap MESS on top,
you need to be able to get the audio output (to feed it further into
MusE). Perhaps another backend is needed for that. Didn't look that deep
though to see how tricky that would be. Ah, well. Not today.
/Mathias If linuxsampler provides the same gui/engine
separation as fluidsynth
does it wouldn't be difficult to wrap it up with M.E.S.S or DSSI and
throw it into MusE or RG, together with a bank of good drumsamples
and some preconfigured "drumkits". Not to mention all the other fun
things you would be able to do... I don't know much about
linuxsampler though, does anyone know how it will work with
LADSPA-fx, routing and midi? Will it provide send-fx that could be
controlled via midi, for different channels etc etc or? Hmm, better
check the archives...
linuxsampler does have gui/engine speration. It speaks a custom
protocol, but its wrapped in a library, so its not too much of a pain.