Analogue-sequencer

@ midihooker:

that should have been Korg Electribe!

Live does not receive MTC just BPM tempo better known as midi clock.

I use Live as a patch bay / recorder.  By using hardware as the midi clock
source and then sending that clock information to Live and back out to all
other hardware (P3 included) and all copies of Live - everything stays in
sync.

I agree that hardware is far more tactile and exspressive - I do not use the
software with a keyboard and mouse - but via my hardware controllers
including a Jazzmutant Lemur.

@ headznmuzik:

I have not noticed any deviation or timing issues.
Mind you - the clock is hardware controlled via the Electribe and is just
passing through the software.
I do use ASIO cards on all pc's.

The VST instruments I use have no problems adapting to the tempo, and even
my hybrid synths TI Snow stays in step.

This may very well be because the tempo information is not being generated
by the computer but via hardware and then passed to all the other gear.

I have created a step sequencer on the Lemur as well - but it too is running
on it's own dedicated hardware - works great...

I guess a VST version of the P3 would have to rely on the hosts ability to
keep accurate tempo, and this is where the problem would come in.


[Non-text portions of this message have been removed]

On 21 Nov 2008, at 16:46, Robin wrote:

> By using hardware as the midi clock
> source and then sending that clock information to Live and back out  
> to all
> other hardware (P3 included) and all copies of Live - everything  
> stays in
> sync.

Actually, when the software is heavily loaded (say, when Live is  
running alongside Max via ReWire, with Max running a sequencer in Java  
driving a monome via OSC, and running a Pluggo-based VST at the same  
time) it will actually drop beats relative to the P3 as master, but  
everything works OK when the software is master and the P3 is slave.

	-- N.


Nick Rothwell / Cassiel.com Limited
www.cassiel.com
www.myspace.com/cassieldotcom
www.last.fm/music/cassiel
www.reverbnation.com/cassiel
www.linkedin.com/in/cassiel
www.loadbang.net

Nick Rothwell wrote:

> Actually, when the software is heavily loaded (say, when Live is  
> running alongside Max via ReWire, with Max running a sequencer in Java  
> driving a monome via OSC, and running a Pluggo-based VST at the same  
> time) it will actually drop beats relative to the P3 as master, but  
> everything works OK when the software is master and the P3 is slave.

Are you running from a standard MIDI out or the sync out? So far, for 
me, Live has been spot on as slave - but I probably haven't pushed it 
terribly hard.

-- 
Paul
---
http://www.SmokyFrog.com
http://www.JointIntelligenceCommittee.com

On 22 Nov 2008, at 21:21, Softroom wrote:

> Are you running from a standard MIDI out or the sync out?

Sync out.

> So far, for
> me, Live has been spot on as slave - but I probably haven't pushed it
> terribly hard.

I suspect that Live, MaxMSP (two instances, one for Pluggo), a Java  
VM, a Python interpreter and OSC-to-USB bridging for the monome  
qualify as "terribly hard."

	-- N.


Nick Rothwell / Cassiel.com Limited
www.cassiel.com
www.myspace.com/cassieldotcom
www.last.fm/music/cassiel
www.reverbnation.com/cassiel
www.linkedin.com/in/cassiel
www.loadbang.net

Nick Rothwell wrote:

> Sync out.

Sync out has been known to drop a pulse or two here also.

> I suspect that Live, MaxMSP (two instances, one for Pluggo), a Java  
> VM, a Python interpreter and OSC-to-USB bridging for the monome  
> qualify as "terribly hard."

Qualifies here. I'm imagining a cheekful of tattooed tears, a pitbull on 
a string and regimental black shellsuits.

-- 
Paul
---
http://www.SmokyFrog.com
http://www.JointIntelligenceCommittee.com