16 Feb
2011
16 Feb
'11
4:30 a.m.
On Wed, Feb 16, 2011 at 03:19:16AM +0000, Gwenhwyfaer wrote:
On 15/02/2011, Ken Restivo <ken(a)restivo.org>
wrote:
Great idea, thanks!
Or I could just use my faster machine for sequencing work, which is what I've been
doing over the past few days.
Or, I could just run a minimal softsynth or two for some kinds of sequencing work, and do
the heavy lifting on the laptop.
By the way, I worked two gigs this weekend, using aseqnet, with great results!
I have a donated Asus tablet (Atom 1Ghz, 1GB), which I used for that huge Pedulla bass in
LinuxSampler. The rest of the synths I ran on my EEE, and I just connected the two with
aseqnet. Worked well. I noticed a bit of a lag when playing really busy bass parts, but I
think that might get solved by bumping the RT priority of the aseqnet instances.
-ken
OK, after working on this a bit, I have the
following to report:
1) The problem isn't really the sequencer. It is running the sequencer
*along with all of my softsynths* (which are of course using RT priority)
that causes even seq24 to slow to an unusable crawl.
Would it be worth simply using a different machine for seq24 than for
your softsynths, with aseqnet as intermediary?