BUG: looper automation only available when transport is on

[ring (Simon Slowik)]

Dear friends!

I was trying to control the looper by M4L. Looper has the device parameter named "State" with the values [stop, record, play and overdub]. Gerenally it works but there is one problem:

The looper automation only works when transport is on.
(For example if I send "record" with transport off, nothing will happen. When I now turn on tranport, it will start to record.)

WHY?
Is there a work around?!

Thank you,
ring

[pid]

this behavior of looper is optional / dependent on other looper settings. read the manual entry for it.

[ring (Simon Slowik)]

No, I don't think so. I neither depends on the "song control" nor the "tempo control" nor the "quantization" settings.
The problem is not that it works different when transport is off - the problem is, that it doesn't work at all!

[pid]

my bad / misunderstanding sorry. apologies i cannot help further...

[ring (Simon Slowik)]

OK, to me it seems like a bug. Maybe you guys from ableton could have a look at this?!

And if so: Maybe you could also implement the complex warp mode to the loopers buffer?! That would be awesome!

Thanks,
ring

[ring (Simon Slowik)]

For shure: If you start recording a midi or audio clip the transport turns on because that what's a sequencer does.


But for the looper it's different: if you set the quantization, transport and tempo settings of the looper to "none" then the looper should be completely independent from the global transport. That's makes conceptionally sense and that's also what the manual says.

You can map the buttons of the looper to MIDI and start/stop recroding when transport is off. I simply want to have the same functionality via M4L!

All other device parameters response no matter the transport is on or off.

I honestly don't see the point why that should be design!

[S4racen]

Dear friends!

I was trying to control the looper by M4L. Looper has the device parameter named "State" with the values [stop, record, play and overdub]. Gerenally it works but there is one problem:

The looper automation only works when transport is on.
(For example if I send "record" with transport off, nothing will happen. When I now turn on tranport, it will start to record.)

WHY?
Is there a work around?!

Thank you,
ring

This is excellent news!!

Can your workaround start with checking is transport is on? if so then a simple record begins if not it would trigger the transport and then record....

How did you find the state parameter??

It's a pity i imagine as i want to use the looper in a rack on a return track so i imagine i'll not be able to get at it.....

Cheers
D

[ring (Simon Slowik)]

here you can see what I mean:

http://www.youtube.com/watch?v=QOYmQkTexRU