I’ve had my Wi-Fi Expander set to the same IP address since I got it and have never had any trouble.
After updating to 2.0.2, the expander failed to connect when I tried to send patches from VCV. I investigated and discovered that for some reason the Meta Hub in VCV had a completely different address set. I reset the address and sent my patch via wi-fi as usual.
Five minutes later I tried to send a new version of the patch, and the address had changed back to the same incorrect address!
Hmm… well, the Hub module saves the wifi URL in the patch file and also in plugin-wide settings (which is in a file called settings.json in your rack user folder).
When you add a Hub module to a patch, it sets the URL to the one from the settings. But if you open a patch file that had a different URL set, it will use the one that’s saved in the patch file. And if the timing is wrong, Rack might save the wrong URL to the plugin-wide settings, which would mean that will become the new default.
I think I can fix this easily, just by not saving or loading the URL from the patch file. It doesn’t make sense to do that anyways with sharing patch files.
Oh right, I must have grabbed the wifi address from the x0x patch that your colleagues shared. Yeah, it doesn’t really make sense for that to be stored at the patch level.
Ok, I think I have this working better, I’ll test some more and it’ll be part of the v2.0.15 release.
Probably a dumb question but why 2.0.15 when the current version is 2.0.3?
Oh, the wifi url stuff all happens in the 4ms VCV plugin, which is at 2.0.14 right now
See, I knew it was a dumb question. Thanks.