A question about Live 12 - Return channel automation scrolling

[Angstrom]

Hey folks,
in Live 12, have they fixed the lack of scrolling of automation envelopes ? It's pretty much a bug that has stayed there forever.

In live 1 to 11 if you have a bunch of automation on a return channel it's not possible to edit them.

Reproduce (in Live 11).

• Add a lot of devices to a return channel so that you have around 40 dials (of any kind)
• Start recording an arrangement and just randomly twiddle each of the dials on the devices, so that you should have 40 lanes of automation
• On the arrangement return track header choose "add lane for each adjusted envelope"
• Try to scroll that view vertically.
• realise you can't get out of it

Is this fixed in Live 12?

I don't have the beta, so no centercode to ask.

EXAMPLE : (edit, replaced link) https://youtu.be/P4pp3P_n5vQ

[Angstrom]

I'll take that as a "no"

[[jur]]

Wow, I wasn't aware of this horrible bug!
I just checked in L12... horrible bug.

Did you ever report it?

[Angstrom]

Wow, I wasn't aware of this horrible bug!
I just checked in L12... horrible bug.

Did you ever report it?

Oh yeah, I think I reported it during L8, or if it wasn't me it was one of the old beta testers / campers . I certainly reported it in L9, which was the first of the Alpha/Betas to move over to centercode from here. Then again in L10 beta although I dimly recall that halfway through the L10 beta, just before it went public beta there was an update to centrecode and the prior discussions on bugs all got wiped. And then flagged as "closed" for some reason I forget now. The intention was apparently to re-open any which were closed in error. I thought I reported it again for L11, but I wasn't on the private beta / dev builds for that one and looking at centercode it says I submitted 0 bugs. Which is odd.

I can no longer see L9, L10 on centercode so I can't search back the bugs on those projects

Obviously I can't submit it for L12, someone else will have to do that

[[jur]]

All right, I'm forwarding.

[Angstrom]

Now I'm on the beta I can see, and remember, why this got punted into the void the last two times. It's this:

If you discover a bug in the Live 12 Beta, please countercheck it in the latest release version of Live 11.
If you can confirm the bug in the Live 11 release version as well, please report the issue to our Tech Support.
If you can confirm that the bug exclusively appears in the latest Live 12 Beta, please report it here.

so what happens is: if a bug is found in the Beta but also in the Release version, it gets closed on Centercode as "in the release" and we get asked to send it to Tech Support .
Which when done ... well, you know. It's a letter to Santa at that point!

And that's how this bug keeps on rocking up in new versions

[[jur]]

Sure, the way it works can feel annoying/absurd from the user/beta tester POV.
But:
- tickets need to high level of organization. I'm sure you know how it works with various builds being worked on simultaneously, branches (is that the correct word?) and so on...
- reports sent to Support are not thrown into the thrash

You could report it again to Support since it seems the last time you did it was a long time ago.
And I'm not forgetting to forward it on my end.

[H20nly]

you know. It's a letter to Santa at that point!

[Synthbuilder]

reports sent to Support are not thrown into the thrash

I can confirm this. The issue I had with Live 11 resetting the tempo to 20bpm in full screen mode on MacOS Sonoma was answered with a friendly e-mail within an hour of me reporting it to support.