RE: [Linuxsampler-devel] Hi - Very quiet list - my first post

[Mark K. <mk...@co...>]

>
>
> > The problem of GS is that it is a
> [...]
>
> So, in short, GS is a Windows specific performance hack, while Halion
> is a plugin sampler Done Right - only on the wrong OS.
>
>
Ah, but GS has the library that the other's wish they had. (And that I've
already invested a couple grand in, so let's not get religious and go some
other direction! There would be huge value in being able to load GSt
libraries into ANYTHING we do.

GSt crashes all the time when running on a PC with other apps. It's actually
pretty stable on it's own machine.



> > MIDI sequencing and a sampler/synth engine on the same box is not a
> > problem since sequencing only takes a fraction of the available
> > resources. If you add HD recording to the equation, then the
> > workload increases significantly but nothing speaks against of
> > runnning both the HDR and the sampler software in the same box.
>
> Except that they need separate disks, unless they share the disk
> butler, I think... Just adding another disk would probably be
> acceptable to most serious users, though.
>

There's a lot going on these days on the sequencer side with notation. I
expect that I will run 2-3 computers to really do what I want to do, but
that's me.

I can already bring my disks to their knees just running Ardour. I doubt my
current, sub-2GHz Athlon XP would run this sampler at the level I push GSt,
which is 10-15 stereo libraries and maybe 100 voices sustained over time.
Hans Zimmer, doing movie scores, has talked of pushing multiple copies of
GSt to the level of 300-500 voices sustained. Those guys are using arrays of
SCSI drives. It can be a lot bigger than just another drive.