Ableton Forum

Discovered this by accident and not sure if its a bug or by design but: Buffers of identical names are shared assuming they are initialised in both devices. Set up 2 tracks both containing a device. In each device place a buffer called test (or whatever). Read a file into the buffer in one device. E...

With the device I'm working on I am plagued by frequent crashes and freezes whilst editing. I've started turning off the audio engine in Live before I edit the patch and this does seem to stop the crashes. This might seem obvious but I just thought I'd point it out as it makes the beta more usable f...

[quote="Mattijs"] Unfortunately, when Loop is off, it is not possible to find out what the loop points are. When you query loop_start and loop_end in that case, they report the start and the end point of the clip instead. - can you not just temporarily create a loop between beginning of fi...

This doesn't happen all the time and haven't found a way to replicate it reliably. But my render window stops working about half the time after returning to Live environment after editing a device. Only way I've found to reactivate it is to reload my Live Project. Ironically bug reporting snapshot d...

If Live and Max crash whilst you are editing a device in Max then when you choose to restore your session on relaunch the edit button of that device is greyed out.

As the editable version doesn't exist in a max window, you have to replace the device to edit it.

Does that make sense?

I'm wondering if you could do something like: create a loop or start/end points between the very beginning of the clip and 1.1.1 (think you can do this via M4L?) Then check the length via the API and you should have the offset - at least in beats. If you need it in seconds you could try toggling war...

This seems to be fixed in the latest version of Max.

Thanks!

Two updates now and the smoothing issues haven't been resolved!
As its just taken me the best part of a day for me to carry out a minor update to my website I'm not complaining.
Just wondering what the score is with it though.
Or if there is a workaround!

Gavin

This isnt specific to 8.05b but wasnt sure where to post it.

Basically its as the title says - soloing a track has no effect on the video component ie the other video clips will still show in the video window.

Maybe this isn't a bug? Seems like one to me though.

Also wouldn't it make weird things happen when you're looping?

OK well feature request for smoothing being optional then! Here's a couple of examples where smoothing might not be desirable: i)If you're feeding M4L clip position data via a modulated parameter (if we havent got access to clip position through the API this might still turn out to be the best way) ...

Can you tell me which the bug is exactly? Is it that the modulated parameter value starts from the new value immediately ie without smoothing), or that if the control value changes significantly the parameter is smoothed? I realise that a physical controller such as a slider or dial cannot move from...

Oh God Sorry about that and thanks for looking.

I've fixed the link now.

http://www.digitalfunfair.co.uk/smoothing.zip

Trigger the first clip and the param value starts from zero straight away.
Trigger the second and it slides down towards zero.

Something like this maybe? Hit the button in the device if it isnt working. If its a looped clip start must be at beginning of loop. If not start must be a 1 1 1 I really don't know what I'm doing so sorry if it crashes horribly. <pre><code> ----------begin_max5_patcher---------- 3048.3oc6bs0iqhiD94...

If I save my M4L patch in Max then the observer objects lose contact with live.

I have to return to Live and then return back to Max to get them working again.