mrmrshoes

I'm having a problem with live.step. I've put together a patch which saves one bar sequences from live step and then recalls them. I'm using the command interval and n_steps in order to use different interval timed steps. The problem i've got comes from updating the duration of a step. if i set the interval to 8nt with durations of 8nt and send this to live step using the duration message and a list of ticks values, it sets the duration values to 4nt. the same thing happens with 32n timing. interval 32n duration 32n = a duration of 64n.

I'm not sure what i'm doing wrong. The patch i'm working on has become quite involed and apart from the duration values everything else seem's to be working. if anyone could help me out that would be a buzz coz this is starting to do ma head in.

here is a test patch to show whats happening.

live-step-duration-problem

sorry i didn't put together the last example patch very well.

Would someone be able to comfrim this behavior for me. I not sure if i'm doing something wrong or if its a problem with live step?

sorry i didn't put together the last example patch very well.
Would someone be able to comfrim this behavior for me. I not sure if i'm doing something wrong or if its a problem with live step?

Looks like a serious bug, probably not detected so far because live.step is commonly used with drums where durations don't matter.

I can confirm this behavior.
Looks like a serious bug, probably not detected so far because live.step is commonly used with drums where durations don't matter.


Cheers broc for the confirmation. I was going half insane while debuging my patch. I did think it could be something to do with live step. just wanted to be sure that others got the same results.

Cheers broc for the confirmation. I was going half insane while debuging my patch. I did think it could be something to do with live step. just wanted to be sure that others got the same results.
thanks again


Thanks for the clear report, will take a closer look.

I thought the answer was right in a the live.step reference, under the description of the "step" message: the duration attribute only recognizes eight precise values. Which makes the live.step extremely limited. You either have to accept their eight preset durations, manually translate them to eight of your own, or use one of the extra parameters to devise your own duration coding. Boooooo.

I suppose it was designed with ease of mouse interaction in mind.

I thought the answer was right in a the live.step reference, under the description of the "step" message: the duration attribute only recognizes eight precise values.  Which makes the live.step extremely limited.  You either have to accept their eight preset durations, manually translate them to eight of your own, or use one of the extra parameters to devise your own duration coding.  Boooooo.

I suppose it was designed with ease of mouse interaction in mind.


You are right about the reference. Only 8 suported duration value 64n 32n 16n 8n 4n 2n 1n 2.0.0

but live step does set the triplet duration values when you change the step interval and outputs those values in ticks. but it doesn't like some of them when you recall the values with the duration message. try it out with, get duration and duration 1, messages

live step duration problem