Hi there,
this bug seems to strange that it sounds like an invention.
Selecting multiple tracks and rendering them while QLink is activated leads to the rendered tracks getting panned in erratic ways following what seems to be a Fibonacci pattern/calculation. If the rendering is undone the original tracks are panned even more extremely in what seems to be the inversion of the previous Fibonacci value.
It happens if one of the rendered tracks is panned in any way via the pan value in Cubase. Even just by 1 to the left or right. This will then be propagated across the other tracks but in increasing values Fibonacci style, according to Claude which made the claim.
Here is a video using another pan value (4) as an example which is apparently the same kind of pattern.
IMAGE OF RENDERS IF 1ST TRACK IS PANNED 4 TO RIGHT
Claude’s Fibonacci take here:
"Track: 1=R4, 2=C(0), 3=R4, 4=R4, 5=R12, 6=R32, 7=R20, 8=R8, 9=R52, 10=R84
Divide every nonzero value by the seed (4):
1, 1, 1, 3, 8, 5, 2, 13, 21
Every one of those is a Fibonacci number (1, 1, 2, 3, 5, 8, 13, 21 — just scrambled in order across the tracks). So each affected track’s pan = 4 × Fibonacci(n), for some n, distributed unpredictably across the stack rather than in sequence."
IMAGE OF ORIGINAL TRACKS AFTER UNDOING THE RENDER
Claude:
"Track: 1=R(100), 2=R96, 3=R96, 4=R92, 5=R80, 6=R48, 7=R68, 8=R88, 9=R16, 10=R84
Subtract each from 100:
0, 4, 4, 8, 20, 52, 32, 12, 84, 16
Divide by 4 again: 0, 1, 1, 2, 5, 13, 8, 3, 21, 4
Same Fibonacci set (1,1,2,3,5,8,13,21) reappears — just now expressed as 100 minus (4 × Fibonacci(n)), i.e., mirrored around the hard-right pan limit instead of centered at 0. That last “4” (track 10, giving 16) doesn’t fit — could be a rounding/clipping artifact or a second seed value leaking in, worth flagging as a minor inconsistency in the report rather than ignoring it."
I’ll also send this to support but I thought its relevant public information because it will probably take time to get solved.
Luckily it’s quite easy to workaround by not having QLink enabled during rendering.
In my case I also remove all pan information because I actually never use the panning in Cubase - it’s all done with plugins. So any panning is accidental, which means I should remove it anyway. If no track has panning the bug doesn’t seem to happen regardless of QLink.
