Miles Davies

I have this M4L sequencer that starts and stops with each note placed in the live clip. The sequencer timing is from ticks from the transport object. I am getting variable number counts each note on/off. Is there a better way to implement this?

comment

loadmess

button

number

counter

toggle

unpack

midiselect

midiout

midiin

live.button

live.numbox

live.dial

noteout

makenote

metro

transport

live.grid

message

change

scale

I have this M4L sequencer that starts and stops with each note placed in the live clip. The sequencer timing is from ticks from the transpor

trying-to-start-sequencer-with-note-onoff

Pink Fluffy Bunnies! (i ran from facebook around election time, as a result deleted my insta as well, miss seeing your stuff there... maybe i'll join up again someday)

i wanted to see your patch work so i attached a metro sending alternating '64' and '0' where needed and it never jitters within the same patch for me(must be some jitter in the midi-event routing between live and the device)... and i am not very Live savvy, in fact, i'm not sure it's safe for me here in the Max4Live part of the forums 👀 ...🤫...they might shoot me in the DAW if they heard i didn't use Live, myself... but i think you should grab the absolute duration from the midi clip itself somehow since it's already available there, and when i search through the LOM, i get a good feeling about the 'Clip' page:

https://docs.cycling74.com/max8/vignettes/live_object_model#Clip

(somehow maybe you could select the current note, then use something like "get_notes" or "get_selected_notes" which could tell you the 'duration'...?)

ok, i better haul ass before they find me, keep up the good fight for betterer and bettererer sequencing! 🦾

i wanted to see your patch work so i attached a metro sending alternating '64' and '0' where needed and it never jitters within the same patch for me(must be some jitter in the midi-event routing between live and the device)... and i am not very Live savvy, in fact, i'm not sure it's safe for me here in the Max4Live part of the forums 👀 ...🤫...they might shoot me in the DAW if they heard i didn't use Live, myself... but i think you should grab the absolute duration from the midi clip itself somehow since it's already available there, and when i search through the LOM, i get a good feeling about the 'Clip' page:
https://docs.cycling74.com/max8/vignettes/live_object_model#Clip
(somehow maybe you could select the current note, then use something like "get_notes" or "get_selected_notes" which could tell you the 'duration'...?)

ok, i better haul ass before they find me, keep up the good fight for betterer and bettererer sequencing! 🦾
🏃🏼‍♂️💨

Haha Raja. Don't blame you. Insta misses you though. All the politics seems to have calmed down again, so quite safe to return if you feel inclined.

Yeah, I thought it might be Live causing the jitter. I had searched for an object to find the duration of note, but note on note off seemed the only option.

I've had a look at the M4L.api.GetSelectedNotes, but it's not very intuitive since its all new to me. Seems quite complicated and convoluted just to get note duration. And there is no clear example. But I will persevere with it. Thanks for the pointing it out.

Yeah, I thought it might be Live causing the jitter. I had searched for an object to find the duration of note, but note on note off seemed the only option. 

I've had a look at the M4L.api.GetSelectedNotes, but it's not very intuitive since its all new to me. Seems quite complicated and convoluted just to get note duration. And there is no clear example. But I will persevere with it. Thanks for the pointing it out. 

Still can't work out why ticks from transport are jittering from a single note looping in Live. Can anyone show me what is wrong here?

Okay, so another test with alternative objects show the fluctuation in duration from Live into Max.

It seems every 4th report has a fluctuation.

Trying to start sequencer with note on/off