Ableton Forum

delete

I am also experiencing this issue.

I wrote to the tech support, let's see what they say.

I wonder how many more people are experiencing that..

Loop turned on in arrangement?

That was the issue for them: viewtopic.php?f=55&t=199591

Because789 wrote:Loop turned on in arrangement?

That was the issue for them: viewtopic.php?f=55&t=199591

It is turned on. But I never had that issue prior to updating the Push's firmware to 1.13

5blackcats wrote:It is turned on. But I never had that issue prior to updating the Push's firmware to 1.13

Not the firmware, but the Push remote script is responsible for this issue.

I guess to add the ability to edit a segment of a loop (introduced with 9.1) they had to implement major changes to the playhead behaviour and in this process the conflict with the arrangement loop occured. Since they mention it in the playhead article it looks like it's not that easy to get rid of this conflict. But that's just speculation...

same here

Ok just got a reply from tech support, they are working on a fix and in the mean time we need to turn off the loop in the arrangement view.

Is "extreme" beta testing proving to be unnecessary when a new release is out with obvious broken features?
Truly, not trying to be a wise arse, but really. I'm constantly feeling like I'm running a beta version and seriously getting tired of it. Personally I'd much rather not have a new version that is broken and going months again with workarounds. Keep it until it works and then set it loose. Jmo and sorry for the rant.

i dont care about this bug. it doesnt decrease my creativity nor efficiency

Timbeaux wrote:i dont care about this bug. it doesnt decrease my creativity nor efficiency

thanks for your input, that was very helpful and much needed

5blackcats wrote:

Timbeaux wrote:i dont care about this bug. it doesnt decrease my creativity nor efficiency

thanks for your input, that was very helpful and much needed

and this:

lyovino wrote:Is "extreme" beta testing proving to be unnecessary when a new release is out with obvious broken features?
Truly, not trying to be a wise arse, but really. I'm constantly feeling like I'm running a beta version and seriously getting tired of it. Personally I'd much rather not have a new version that is broken and going months again with workarounds. Keep it until it works and then set it loose. Jmo and sorry for the rant.

helped u and was needed, too?

Timbeaux wrote:

5blackcats wrote:

Timbeaux wrote:i dont care about this bug. it doesnt decrease my creativity nor efficiency

thanks for your input, that was very helpful and much needed

and this:

lyovino wrote:Is "extreme" beta testing proving to be unnecessary when a new release is out with obvious broken features?
Truly, not trying to be a wise arse, but really. I'm constantly feeling like I'm running a beta version and seriously getting tired of it. Personally I'd much rather not have a new version that is broken and going months again with workarounds. Keep it until it works and then set it loose. Jmo and sorry for the rant.

helped u and was needed, too?

The whole point of the topic is to discuss the deficiency of the firmware update and attract developers' attention, and not about how you don't care about the bug.

And because i dont have ur oppinion i dont have the right to write it here in an open forum? sry for that

anyway, if u want to attract the developers attention just write to support... (what u already did ofc)