nope, writes to rest of Rack dir just fine, so not that issue as far as I can tell. I have given it access to files and documents, as should be, but I tried even full access for Rack and it still happens, ONLY on autosave/modules folder, not autosave itself. so no app should have full access unless it needs to do a low level backup of all. But given that does not fix it I discount it is MacOS security that causes this, as otherwise I would see it in the whole Rack folder as it is in Documents folder. Does not compute
For what itās worth, I had this exact problem last night on my Linux system. Something somewhere decided to remove write permissions on the autosave folder. And of course I donāt have any antivirus or anything like that running. I have no evidence, but the most likely cause is VCV Rack itself, or the unzipper it uses for .vcvplugin files. Instead of deleting the whole folder, I did this:
chmod -R +w /home/don/.Rack2/autosave
Then I started Rack again and everything worked fine. And this isnāt the first time Iāve had to do this.
1 Like
Yeah, must be a bug in the archiver then, or how Andrew is using it in Rack. It wouldnāt be the first one.
Hey everyone, check out this commit to VCV Rackās source code, in particular lines 581ā¦592. This appears to fix the Unarchiver problem. Looks like it will be part of the next release after 2.2.3.
2 Likes
So VCV has reported to me a while back (stated in another thread about this one perhaps) as I had filed a bug on this after I ended up fighting it first few times and narrowed it down to Rack or one of itās components. Hopefully that will fix it and fix will arrive soon, as I, if I am in a mood to work on some older patches, hit this regularly enough to be annoying and disruptive to any creative endeavor.
1 Like
Yup, looks like it. Strange he has waited so long. Also strange that not everyone suffers from it. Maybe itās the combo of macOS protection on Documents + this archiver bug.
I encountered it most recently when I downloaded a patch someone else made. My best guess is when someone creates a patch on one operating system, then sends it to someone on another operating system, there is some mixup about the permission flags. When the file is unzipped, it removes write permission, but no bad behavior is apparent at that time. Then the next time you try to do something in the directory, you hit the bug. If this theory is correct, the reason itās so hard to pinpoint is the bug doesnāt do anything immediately noticeable. It might be hours or days later when you open VCV Rack again that the problem manifests.
1 Like
Itās an interesting theory. Maybe it mostly bit people who use a lot of other peopleās patches.
I donāt think thatās it, because I got the error on one of my own patches ā¦ Iāve proved to my own satisfaction that this is a permissions issue on Mac OS, relating solely to the Autosave folder. How it happens, IDK lol
And that patch started on your own machine and never left that specific machine?
yep
Maybe there are multiple bugs. Last year on Windows, I had a case where I had downloaded a patch from a well known blogger and could only resolve my problem by deleting the autosave folder contents. I mentioned that at some point here.
I have also seen it both with my patches (but only a few and no pattern to find what may trigger it) and other folkās patches I check for interesting ideasā¦ So hopefully the fix done covers both scenarios if it really is only one bug after all.
1 Like
The directory write bit? The some de-archivers play it safe by making it read only is a reasonable theory. Also a rack crash with a file open might lock writes ā¦ ummm.
It appears to me that the Rack V2.3.0 may have addressed this issue based on the change-log.
2 Likes
so far so good with 2.3.0, not yet hit any further unurchiver errorsā¦
2 Likes
FWIW ā I have no idea if this is connected to the issue at hand, but the comments about using patches from other peopleās machines brings this to mind.
In Windows, when downloading a zip file from the internet (or email), it is flagged with the āMark of the Webā, which often wreaks havoc on being able to use the for anything until you remove it.
To do so, select the file in File Explorer and open itās properties (Alt+Enter or right click > properties) and find this:
.
Make sure to check the Unblock box and hit Apply or Ok.
YMMV
1 Like
Hello, yesterday I was using an old patch of mine and now it wonāt open it has come up with the following tab :
This due to the current v2.4.0 upgrade? I have not upgraded to that yet. Is it still not functioning properly?
If you search the forums, youāll find a number of instances of this symptom, some that go way back, so unlikely to be related to Rack 2.4 specifically.
Some antivirus software can interfere with files in a way that creates this problem. When this is the case, it usually goes away without intervention.
Thanks, Iāll see what happens. I have Norton 360 see if that is causing it.