OK…the overwriting a patch via wifi lockup happens 100% of the time according to my tests.
OK…is that something @jeremywen can fix?
Yeah, we’re on it. I think just a simple mis-match of SDK versions
If you want to continue testing the Wifi Issue, just use different plugins until we fix that one.
I have tried different plugins and am getting the same results. Seems to be a universal issue. I may have to revert back to stable for a while to get work done…
I’m not getting freezes when transferring with Wifi.
Can you try something:
- Power up with no disk (no USB, no SD Card)
- In VCV, make a patch using only built-in brands (4ms, Audible/Cloned, Befaco, etc – no plugins).
- In the VCV MM Hub, right-click and select to send patches to the Internal drive.
- Transfer it to the MetaModule via Wifi.
- Play the patch on the MetaModule.
- Go back to VCV and change something (again use only built-ins – no pluig-ins)
- Check and make sure the MM is still working.
- Repeat the last two steps (change the patch and re-send it).
This whole time, don’t plug a USB drive in, and don’t insert an SD Card.
Does that crash for you?
For me – it works 100%.
Now, if I insert an SD Card or USB drive, sometimes when I send a patch from VCV it will timeout and tell me that the patch transfer failed. Sometimes it does fail but sometimes it goes through and just says that it failed. But it never makes the MM freeze or crash.
Aha! I got it to crash.
I started with a built-in only patch as I described above, and then started changing it to be more like the patch you attached, until it crashed.
It looks like it crashes if the patch contains a module that’s not found. This includes the VCV Audio Interface module (which is in lots of patches).
Very strange. I built a very basic patch as you suggested (see below) and removed the card and USB, and it doesn’t crash either from internal memory. I also inserted a card and wrote to there and no crash. Interestingly, the patch DOES include the VCV audio interface. So, now I am intrigued as to what is causing the crash?
4ms BASIC.yml (2.3 KB)
I’m digging into it, and it’s actually more nuanced than just having a module which isn’t found… anyways, working on a fix now.
Okay, I autoloaded all the other modules and still running the test patch and no crash.
@danngreen OK…I went back to my standard patch and replaced the Sickozell Clocker 2 with an LFO. No crash. Then I loaded the Sickozell Clocker 2 by itself, and transferred it, and it locked up immediately. BINGO!
I found the issue, am just testing the fix for it now.
I ran out of time testing all things with it, so if it still crashes sometimes I can patch it up tomorrow.
There is still a potential issue: if you play a patch with modules that you don’t have the plugins loaded yet, and then you go and load the plugins (while the patch is still playing), it MIGHT crash. I didn’t see it crash but the bug effects this situation too, so there’s a potential of it happening.
FYI, I had just noticed a bug in 13.2 wherein if you selected New Patch, Added any module, selected it, then deleted it crashed. 13.3 appears to have rectified this.
And I will add this here as a minor UX issue noted using 13.3rc1 and 13 plugins. Using Sanguine Mutants Funes or Etsia as examples- Graphics with RH Navigation window opens & manages viewable area as you navigate as expected.
Hide the Navigation pane and it neither takes over available space nor manages viewable area leaving it permanently part off screen.
Observed in Venom NORS IQ but not all modules with large real estate. Also FYI Seaside Modular has strange text character action happening.See Raga for it in Parameters, Tala for it in module Graphics window. Sanguine Mutants module Header text was problematic in 13.2 now absent in 13.3.
Ah yes, I’ve seen this.
@etcetc do you know anything about this? Maybe a missing font?
@danngreen I am spending some time testing it with various patches and using wifi to overwrite changes and I haven’t been able to get it to crash yet. Update…just tried JW DivSeq and it still locks it up. Same thing with 8Seq and Note Seq16. These have serious problems. Perhaps you and @jeremywen can test them using the latest dev-13.0-rc.
@danngreen @jeremywen I just downloaded JWs latest compile and that fixed the lockups. Bravo!