lefauxdjaber

Using "set fold_state" with an integer to live.object no longer works. I had a patch that used this function and I've never had any problems until the upgrade. For either set/get the max console outputs that 'track' object has no attribute 'fold_state'.

What can I do about this? Having that property work is integral to my live setup.

Has anyone else noticed this?
Using "set fold_state" with an integer to live.object no longer works. I had a patch that used this function and I've never had any problems until the upgrade. For either set/get the max console outputs that 'track' object has no attribute 'fold_state'.

What can I do about this? Having that property work is integral to my live setup.


fold_state-issue-with-live-9-6

I assume you are working with either group tracks, racks, or the arrangement view:

It may have changed to the is_collapsed property of the track view object. Unless I have a little more context, I can't be sure of what you mean

I can't try out is_collapsed at the moment. But it is marked as a property that can be set by bool so I don't see why that wouldn't work. Would you know why it would have changed though?

Yes I was using it for group tracks.
I can't try out is_collapsed at the moment. But it is marked as a property that can be set by bool so I don't see why that wouldn't work. Would you know why it would have changed though?


I don't work at Ableton, so I am not sure why they changed that particular property, I am sure they have their reasons. It's a shame that they don't give us a rundown of these changes so we can be a little more pro active about updating our devices.

is_collapsed is on the track_view - is_foldable/fold_state are on the track... nothing has changed here...

'Track' object has no attribute 'fold_state'...

is that a group track? fold_state only exists on group tracks...

you need to check is_foldable first to see if you can get/set fold_state - this is documented in the LOM API

Yeah it was, I checked all track types. I'm sure it was there at some point, but it doesn't seem to be in 9.6 (or the latest beta 9.6.1b2)/

Yeah it was, I checked all track types. I'm sure it was there  at some point, but it doesn't seem to be in 9.6 (or the latest beta 9.6.1b2)/


Ya a heads up would have been nice haha. I looked up while practicing and was like "what the hell is going on?" It just concerns me, what else has changed that I haven't encountered yet? Now I have to go test every damn patch to ensure I don't any weird fuck ups during performance. Thanks ableton, as per usual.

this has always been the case - nothing has changed here. fold_state has only ever been available on group tracks

also, to allay your fears, in the last 5 or so years I've been using M4L, there has never been anything that has changed moving forward through Live versions that has meant that patches have stopped working... if there ever has been the occasional problem then it's down to bugs that were introduced, but this was back when m4l was changing quite a bit - it's very stable and has few issues these days

there have never been any changes that would intentionally break any patches out there...

this has always been the case – nothing has changed here. fold_state has only ever been available on group tracks

So did you not see the other screenshot querying a group track, just to demonstrate that we are talking about group tracks?

is_foldable = 1, but fold_state is still not an attribute. Has that always been the case? Nothing has changed here?

I'm sure that they never intentionally break patches, that's not the discussion. But something changed that made the OPs device start giving these errors, when there were none before.

 this has always been the case – nothing has changed here. fold_state has only ever been available on group tracks

So did you not see the other screenshot querying a group track, just to demonstrate that we are talking about group tracks?
is_foldable = 1, but fold_state is still not an attribute. Has that always been the case? Nothing has changed here?

I'm sure that they never intentionally break patches, that's not the discussion. But something changed that made the OPs device start giving these errors, when there were none before.


apologies, i missed that image showing the error.

i would definitely say that's a bug and should be raised - there were alot of changes from 9.5 to 9.6, including changing the Python interpreter, so it's possible it got missed... if you raise it quickly it might even make it into the current beta cycle...

i would definitely say that's a bug and should be raised - there were alot of changes from 9.5 to 9.6, including changing the Python interpreter,  so it's possible it got missed... if you raise it quickly it might even make it into the current beta cycle...


I would've never found this if not for digging into this thread, I'll post it in the bug tracking/beta thing.

fold_state issue with Live 9.6