I have this post open about running two instances of Rack 2 on 2 different computers over an ethernet connection. I was going to work on this and tried opening Rack on my laptop but the weirdest thing - it’s like it’s open in another window / screen even though I have no other screens connected. It’s “alive” in my task bar and when I hover over it I see it but when I click on it to bring it up it doesn’t show on the screen. It’s running fine on my desktop. I have restarted the laptop, uninstalled and re-installed Rack. Any ideas on this? Ableton works fine…
In saying that about Ableton I tried to open Rack in Ableton as a troubleshoot but got a message that “This VST2 plug-in is not compatible with Live” (and holy f**k but everything seems t be fighting me - I took a screenshot on my laptop of this and emailed it to myself because the networking isn’t networking properly and though I can open and look at the jpg file on my laptop it won’t open on my desktop when I try and download it … so the attached pic is actually a pic from my phone). I tried using the VST3 version and it just crashes Ableton.
I tried your suggestion as well as a few others - cascading windows for example. It does not bring up the screen. There is a quick little visual effect of the program sliding down to the taskbar when I click on it but that’s all.
On My Desktop (and normally on my laptop) if I have software like this open and I reduce the screen, if I hover my mouse over the task bar icon I get an image of that program:
Thanks very much for the troubleshoot Richie, this has worked. I see after restarting that there is a new settings.json file. I screen grabbed this shot below prior to that restart. I do not know much about the .json files but why are the ones I have shown located here? Is this fine?
Those JSON files store settings, for Rack itself and for some of your plugins. It’s fine that those are there. They’ll typically get recreated with the default settings when you run Rack again.
Sometimes they can get corrupted, or a new version of a plugin can be confused by something stored in one of those files by an earlier version, so it’s worth trying moving them aside if things go wrong.