Danjel van Tijn

So I have made a nice sequencer patch with lot's of unique features. However, for development I used a tempo object as the clock source and the sequencer output went to a vst~. Now I want to use this sequencer with Ableton Live.

Should I make the sequencer the master clock or slave it to ableton?

If I make the max patch the master, it needs to send out midi clock and start/stop commands.

If I make the max patch slave, it needs to receive these commands.

I assume either of these is straight forward to do?

So I have made a nice sequencer patch with lot's of unique features. However, for development I used a tempo object as the clock source and the sequencer output went to a vst~.  Now I want to use this sequencer with Ableton Live. 

master-or-servant

sorry guys, I should have searched the previous messages first!

Looks like the best way for me to do this is use Ableton as the master and then strip the midi clock ticks using select 248.

I can then use lnth to select the clock divisions I want and then trigger a counter to generate step numbers (e.g. 16th notes).

> sorry guys, I should have searched the previous messages first!

> Looks like the best way for me to do this is use Ableton as the master and then strip the midi clock ticks using select 248.

> I can then use lnth to select the clock divisions I want and then trigger a counter to generate step numbers (e.g. 16th notes).

Actually, I think the best way to do it is to build a pluggo from your 

patch...so it all depends on who you ask.

Danjel van Tijn skrev:
> sorry guys, I should have searched the previous messages first!
>
> Looks like the best way for me to do this is use Ableton as the master and then strip the midi clock ticks using select 248.
>
> I can then use lnth to select the clock divisions I want and then trigger a counter to generate step numbers (e.g. 16th notes).
Actually, I think the best way to do it is to build a pluggo from your 
patch...so it all depends on who you ask.

On 22 Apr 2007, at 20:33, Danjel van Tijn wrote:

> Looks like the best way for me to do this is use Ableton as the 

> master and then strip the midi clock ticks using select 248.

Alternatively: look into packaging your application as a VST and 

running it as a plug-in within Live. You then get sync features for 

> Looks like the best way for me to do this is use Ableton as the  
> master and then strip the midi clock ticks using select 248.

Alternatively: look into packaging your application as a VST and  
running it as a plug-in within Live. You then get sync features for  
free.

Nick Rothwell / Cassiel.com Limited
www.cassiel.com
www.myspace.com/cassieldotcom
www.loadbang.net


hmmm haven't tried that before. I am new to programming max/msp but in the past I did own pluggo (and technically still do). I am aware that pluggo plugins can send midi to each other. However, isn't there a limitation in Ableton with regards to plugins generating/processing midi? i.e. I don't think I could have a sequencer plugin and then have it generate note information that could be received on any channels of ableton unless I use loopback via MidiYoke.

If there is some advanatges to using the latest version of pluggo in this respect then maybe it will be worth investing in the upgrade (I have pluggo v. 2.0 )

p.s. In my previous msg I forgot to mention that I was stripping clock ticks using RTIN

that would be good if my plugin was generating audio instead of midi. Unfortunately with Live I need to keep midi generators external or linked via MidiYoke.

> I am new to programming max/msp but in the past I did own pluggo 

If you've got MaxMSP then you have what you need to build pluggos - 

> I am aware that pluggo plugins can send midi to each other. 

> However, isn't there a limitation in Ableton with regards to 

> plugins generating/processing midi? i.e. I don't think I could have 

> a sequencer plugin and then have it generate note information that 

> could be received on any channels of ableton unless I use loopback 

I don't know, to be honest. I've written pluggos for Live which take 

in MIDI and generate OSC, but haven't yet managed to get MIDI out 

working. I don't know offhand whether it'll work, or whether I'll 

> I am new to programming max/msp but in the past I did own pluggo  
> (and technically still do).

If you've got MaxMSP then you have what you need to build pluggos -  
you just need the free Pluggo runtime.

> I am aware that pluggo plugins can send midi to each other.  
> However, isn't there a limitation in Ableton with regards to  
> plugins generating/processing midi? i.e. I don't think I could have  
> a sequencer plugin and then have it generate note information that  
> could be received on any channels of ableton unless I use loopback  
> via MidiYoke.

I don't know, to be honest. I've written pluggos for Live which take  
in MIDI and generate OSC, but haven't yet managed to get MIDI out  
working. I don't know offhand whether it'll work, or whether I'll  
have to go the IAC route.

> that would be good if my plugin was generating audio instead of midi. Unfortunately with Live I need to keep midi generators external or linked via MidiYoke.

yes, unless it's just midi note info. Live handles those quite beautifully.

It's "just" cc#s and such messages that can't get routed around internally.

Danjel van Tijn skrev:
> that would be good if my plugin was generating audio instead of midi. Unfortunately with Live I need to keep midi generators external or linked via MidiYoke.
>
yes, unless it's just midi note info. Live handles those quite beautifully.
It's "just" cc#s and such messages that can't get routed around internally.

>> I am aware that pluggo plugins can send midi to each other. However, 

>> isn't there a limitation in Ableton with regards to plugins 

>> generating/processing midi? i.e. I don't think I could have a 

>> sequencer plugin and then have it generate note information that 

>> could be received on any channels of ableton unless I use loopback 

> I don't know, to be honest. I've written pluggos for Live which take 

> in MIDI and generate OSC, but haven't yet managed to get MIDI out 

> working. I don't know offhand whether it'll work, or whether I'll have 

You'll have to trust me on this one, then ;-) I've built many little 

sequencers for use in Live over the last year.

The one limitation I've heard is that although VSTs can do it, AUs can't 

output midi without using a loopback of sorts. But vsts definitely can. 

And it's easy. Use the [plugmidiout] object in the pluggo, and then 

select the pluggo as an input to whichever track you want.

Nick Rothwell skrev:
>> I am aware that pluggo plugins can send midi to each other. However, 
>> isn't there a limitation in Ableton with regards to plugins 
>> generating/processing midi? i.e. I don't think I could have a 
>> sequencer plugin and then have it generate note information that 
>> could be received on any channels of ableton unless I use loopback 
>> via MidiYoke.
>
> I don't know, to be honest. I've written pluggos for Live which take 
> in MIDI and generate OSC, but haven't yet managed to get MIDI out 
> working. I don't know offhand whether it'll work, or whether I'll have 
> to go the IAC route.
>
>
You'll have to trust me on this one, then ;-) I've built many little 
sequencers for use in Live over the last year.

The one limitation I've heard is that although VSTs can do it, AUs can't 
output midi without using a loopback of sorts. But vsts definitely can. 
And it's easy. Use the [plugmidiout] object in the pluggo, and then 
select the pluggo as an input to whichever track you want.

On 22 Apr 2007, at 21:38, Andreas Wetterberg wrote:

> Use the [plugmidiout] object in the pluggo, and then select the 

> pluggo as an input to whichever track you want.

I was getting Live crashing on me, but that's fixed now... Important 

safety tip: don't forget to put in a [plugconfig] if you have a [pp]...

> Use the [plugmidiout] object in the pluggo, and then select the  
> pluggo as an input to whichever track you want.

I was getting Live crashing on me, but that's fixed now... Important  
safety tip: don't forget to put in a [plugconfig] if you have a [pp]...

master or servant??