Is there a reason that loop_start/end target depend on the loop status

[Angstrom]

I'm not sure if this has ever been explained anywhere. I had a search around and didn't find anything.

Why is there no way to set the clip loop braces while the Looping status is 0 ? And even worse - the properties are re-targetted to completely unrelated destinations if the clip loop flag is false.

In the Ableton Live GUI we can freely move the clip loop braces when the clip loop status is "off", but if we try to do that via the LOM it will move the clip start and end markers (which already have named properties of their own). It's weird. Such a core aspect of Ableton Live (clip loops) but never really worked correctly via the LOM.

Surely many users want to set loop start and end points, and THEN turn the loop on. EG: playhead is advancing from 5.0.0. and we decide to set a 4 bar loop starting at 17.0.0. Yet unless I've totally misunderstood it - we can't do that?

Code: Select all

loop_start
Typedouble
Accessget, set, observe
Description

For looped clips: loop start.
For unlooped clips: clip start.

loop_start and loop_end are in absolute clip beat time if clip is MIDI or warped. The 1.1.1 position has beat time 0. If the clip is unwarped audio, they are given in seconds, 0 is the time of the first sample in the audio material.

[S4racen]

I've never found a reason, but it's a pain in the arse...

Making a DJ Style Clip Looper is way more complex than it needs to be....

Cheers
D

[Angstrom]

I've never found a reason, but it's a pain in the arse...

Making a DJ Style Clip Looper is way more complex than it needs to be....

Cheers
D

Yep. A DJ style clip looper is exactly what I was doing.

[S4racen]

You have to plan the timing as well as you can't move the start after the end etc.

Cheers
D

[chapelier fou]

I definitely agree, the API calls could be so much easier