Experiencing weird rearrangement issues with modules in patch

If you have the “neat & tidy looking patch - OCD thing” like me,
opening your patch to see it all scrambled is somewhat like this:
:scream::woozy_face: :cold_face: :scream: :hot_face: :face_with_spiral_eyes: :scream:

Oh well ok… it might not be that dramatic :joy:


Oh, but it would be exactly like that if I saw my patch do that!

1 Like

trust me, my reaction was much more severe than yours, as I couldn’t quite work out how it had been until opening a previous version in 2.0.6 which luckily loaded fine (and all have since), but any attempt to go 2.1.0 results in same serious reaction of pulling mostly non-existing hair out :wink:

1 Like

Is this limited to a particular OS platform?

not sure what @Eurikon is using, mine is MacOS 12.3.1

Mac OS 12.3.1 (M1)

OK, that confirms it appears a Mac only issue. Kicker is that I had Rack2 2.1.0 running mostly fine under 12.3.1 since the day the update dropped. The only thing I updated since then and between things working fine and not fine was XCode latest and it’s updated commandline tools. That should have exactly zero impact on things…

Hi all, trying to track this one down. Can anyone share a patch file where this issue has occurred with me?

FG_R2_58_11_GranularNoisePlethoraResonatorGranular_Fun.vcv (21.6 KB)

This patch needs the Southpole plugins. It tends to crash on Start of Rack2 if it’s in autosave, but it always opens fine if I tell Rack2 on next start not to clear patch but load the one that crashed anyhow. Never fails and works fine.

I know this one opens fine in 2.0.6 in it’s 4 rows, but 2.1.0 makes a 3 row jumbled mess out of it, Never saved that mess so don’t have one lying about that shows issue and failed to take a screenshot. Sorry, but can’t update to 2.1.0 again as it drives me up the wall in a few seconds… Looks like you need an M1 original machine (Mini or MBP) that was since updated to 12.3.1 from 11.6.x to see this happen in all of it’s heart-crushing glory :wink:

Oh, one other note, after it does rearrange your 4 row patch, if that is in autosave (likely yes if autosave interval is at default), then it becomes a 2 row even more jumbled heap of mess. Not tried if subsequent start with that in autosave would make it a.one row never to be put into logical flow again patch, but that seems likely…

@Eurikon : Did 2.1.0 ever work fine on your M1 with 12.3.1 or did it take a week (or so) before this started? If it started a few days after OS update, what did change system-wise on your Mac since then? I know mine (and I am sure that was the only one) was XCode and command line tools update, after that Rack 2.1.0 was unusable visually speaking. 2,0,6 is fine with same updates…

I had this problem before Mac OS 12.3.1 and since 2.1 VCV

That sounds real… interesting. I wonder if @dlphillips or @synthi are seing the same?

I’m still on 11.6 I can’t see that behaviour

1 Like

I had this issue, coupled with new modules drag and drop rearrangement behaviour, it was too much… I decided to stay on 2.0 release for a while. Old habits die hard. (compiled from src, on macos 10.15.x)

Just got a mail saying they are working on this, so guess must have found the issue, luckily. So here’s hoping it all gets sorted out soon.

1 Like

It’s not just on M1. I’ve now seen it and I don’t have an M1 Mac.

1 Like

So what might have happened between it working fine and then all of the sudden starting to freak out? As stated, only updates prior to issue starting here was latest XCode and it’s comman line tools update… Nothing was recompiled or otherwise changed. So mystery abounds, guess you mean on Mac in general instead of M1 only?

Yep that. Admittedly I saw it in a patch created on M1 I believe, but I saw it on a non-M1 Mac yes.

1 Like

Changing floor() to round() here fixes this problem. @Vortico

IMHO, this behaviour feels like too much smart from UX POV

And I would like to have back old showe behaviour while holding RACK_MOD_CTRL


ping @pgatt