Dear Fredo,
It makes no difference here whether I shut down the machine in between or just reload the project.
Hi,
I saw the different position of the āPostfaderslotpositionlineā 
in your screenshots.
I tried myself and could narrow it down a little further I think.
I now have a Project with two multichannel groups.
Group1
-Post fader insert line between Insert 15 and 16
-Insert1 stereo plugin L/R
-Insert 16 stereo plugin on last two channels
Group2
-Post fader insert line between Insert 1 and 2
-Insert1 stereo plugin L/R
-Insert 3 stereo plugin on last two channels
Group 1 is always recalled correct,
group 2 is always recalled wrong.
This might explain different results, when different people tried to reproduce.
I did not dig in deeper, whether it is the Insert position or the post fader insert line position, or a combination of both.
Cheers,
Dirx
1 Like
Huh! 
Thanks for pointing out that small, but remarkable difference, @Dirx ! Iāll give it a try myself ASAP.
BINGO!!! @Fredo 
@Dirx has given the hint to the crucial variable! I can confirm that the error described in my messages and tests is indeed and reliably dependent on the position of the plug-in in respect to the fader. Multi-track routing for post-fader plug-ins is recalled correctly only in slots 11 and 12. In all other slots, the routing is reset to default in a post-fader position, regardless of where the fader is placed.
ā¦ to make things even more complicated, even pre-fade multi-track routing is NOT recalled properly in slot 11 as soon as the fader is moved to the position between slots 11 and 12.
Here is a simple test project that show-cases the issue:
NU11Routing Test4.npr (452.8 KB)
@Steinberg: Please fix.
Will bugbase this.
Fredo
Thanks a lot. Iāll give it a bump, every now an then. 
As I just run into this in a clientās project on a system with an older installation of Nuendo: Let me confirm that this bug has been solved with Nuendo 12.
4 Likes