PS. Looks like it happens even with only one instance of Looperator. Turnado also seems to have the problem to a certain degree although the value range is not as extreme it does exhibit it.
@Audiogus said:
PS. Looks like it happens even with only one instance of Looperator. Turnado also seems to have the problem to a certain degree although the value range is not as extreme it does exhibit it.
@Audiogus said:
PS. Looks like it happens even with only one instance of Looperator. Turnado also seems to have the problem to a certain degree although the value range is not as extreme it does exhibit it.
@Audiogus said:
I don’t see how that adds up to ‘Probably not’ though. I mean, part of me agrees ‘probably not’ but not for technical reasons.
Likely 'technical reasons'.
It was tested extensively with many AUs by several users. A ticket was created with simple steps to recreate the issue, with videos (including yours) attached. The dev was notified. No acknowledgement from the dev.
@Audiogus said:
I don’t see how that adds up to ‘Probably not’ though. I mean, part of me agrees ‘probably not’ but not for technical reasons.
Likely 'technical reasons'.
It was tested extensively with many AUs by several users. A ticket was created with simple steps to recreate the issue, with videos (including yours) attached. The dev was notified. No acknowledgement from the dev.
Hmmm, OK. Thought it was more elusive. I don’t think I made a video with specific repro steps for this before (maybe? Did I?) , although I do recall showing other automation bugs.
I can’t actually see the Trello links you sent. I don’t think I was ever logged on there.
For the benefit of @Audiogus here are the 2 trello bug reports that @Sequencer1 posted above (only beta testers were given access to the bug report Trello)
Comments
PS. Looks like it happens even with only one instance of Looperator. Turnado also seems to have the problem to a certain degree although the value range is not as extreme it does exhibit it.
Think this will ever get fixed?
Probably not.
https://forum.audiob.us/discussion/comment/698656/#Comment_698656
Most AUs use the 0-127 range, not 0-1, so automation in most AUs will eventually get fubared.
BM3's macros use the 0-1 (%) range too.
I don’t see how that adds up to ‘Probably not’ though. I mean, part of me agrees ‘probably not’ but not for technical reasons.
Likely 'technical reasons'.
It was tested extensively with many AUs by several users. A ticket was created with simple steps to recreate the issue, with videos (including yours) attached. The dev was notified. No acknowledgement from the dev.
Here it is again:
https://trello.com/c/XVD8lg40/12-auv3-parameter-automation-scaling-issue
And another related one that you initially reported:
https://trello.com/c/P1b9kjDm/13-pattern-automation-bugs-via-audiogus
Hmmm, OK. Thought it was more elusive. I don’t think I made a video with specific repro steps for this before (maybe? Did I?) , although I do recall showing other automation bugs.
I can’t actually see the Trello links you sent. I don’t think I was ever logged on there.
For the benefit of @Audiogus here are the 2 trello bug reports that @Sequencer1 posted above (only beta testers were given access to the bug report Trello)
@tk32
Thanks for the inside peak!
^