fire midi clip "loop section problem" mouse/max differences

[phatline]

i wrote something like a APC40 firematrix&clip-editor... for my midibox BLM16x16+x Matrix Controller (

all clear so far, since i wrote my first patches for that with the first launchpads ... dont know how many years ago... so i am dinsaur in sence of M4L

whats new for me is, when i fire the clips with mouse, the looping is normal - from begin to end - forever. (very good as i want it to be like that)

when i fire the same clip with max4live (clip path > live.object > call fire) then it loops 1time normal and the 2nd time for example to half, then 1xnormal then 2nd time the half.... I dont want them to do that! i want my patch to do like it does with my mouse Action - playing the loop section begin to end forever.

whats the problem here, and how to solve it?

[chapelier fou]

First of, nice controller !

My guess is that a MIDI loop is happening somewhere. Are you sure that the the clips are not sending MIDI feedback that would retrigger them ?
Would you give some details how your M4L works ?
Or maybe your buttons send the same message when released ?

[phatline]

Live-Picture
Track 1: 5bars --- loop restarts @ 2nd Bar (the clip you see in Detail view)
Track 3: 2bars --- looping normal
Track 4: 2bars loop, with 1,88bars intro --- loop restarts @ 2bars, while loop end would be 2,33


It has to do with Quanization:
In this picture you see Track 1 (in max Track 0), it has a Quantization of 1 Bar.
And it then make a "virtual-loop-point" at the end of Bar 1 and restarts, while the clip loop points in reality is 1 and 3.

Maybe this behavior make sense in some cases, in mine not really... and have to say when FIRE the clip with MOUSE, live make it as i want it to be made...

On the controller and Max Side:
I dont have double triggers, and my patch only send 1times "call fire"
See Picture: XY List, with no Double Triggering (filtered out)


Sysex:
No Loopbacks, because sending the LED-Status via Sysexdump, which is on Controller Side not Programmed to do anything then LED Change...
Sending only Button Actions, via Note Velocitys.
Receiving only Syssex Data, with no interaction with Controller Button States


...beside i dont find a "Call ARM" command for a Track - ...maybe i am on the wrong path

[chapelier fou]

I’m traveling today so I can’t really check, sorry.
To arm a track, it’s not a function to call, it’s a property of the track. I think you need to point to live_set tracks N and “set arm 1/0”.

[phatline]

yes "set Arm 1" worked, i have to keep in mind to try also "set" in combination with live.object, instead of "property" in combination with live.observer.

[phatline]

no one?

[phatline]

still not solved!!!

[phatline]

still not solved!