Page 1 of 1
Gui unusable again
Posted: Wed Feb 24, 2016 1:56 pm
by R Green
I am giving up soon. The jamstix gui yet again is not fitting in the Reaper fx box so I am unable to close it once it is open (when it eventually decides to display).
Latest version of Reaper, (either official release or latest pre have been tried). Latest version of el capitan. Dual monitors.
This is no fun.
Gui unusable again
Posted: Thu Feb 25, 2016 5:45 am
by Bagatell_
El Capitan is more likely the culprit than Jamstix. I'm having problems with Firefox screen captures with EC that were fine before the upgrade.
Gui unusable again
Posted: Thu Feb 25, 2016 12:08 pm
by Ralph @ Rayzoon
We'll check that out as soon as possible. Sorry for the inconvenience but, unlike Microsoft, Apple is quite aggressive with API changes that are not backwards-compatible etc. so various issues can crop up with OSX upgrades across many apps.
Gui unusable again
Posted: Thu Feb 25, 2016 1:41 pm
by R Green
Right, I've calmed down and remembered that with El Capitan (no r) you have to reboot the mac with the second monitor disconnected. I then played around with jamstix, which was now ok and then powered off.
I then connected the second monitor, booted up, turned the second monitor on, and the Jamstix gui is pretty much behaving itself. So I then drag it to the second screen and have it open all the time. If I close it, I still sometimes get the infamous jamstix white gui; but dragging the reaper fx window to my primary monitor and back again forces the gui to reappear.
So next time this happens (because things were working ok in El Capitan for a while) I know what to do and am sharing this should anyone have the same problem.
I was having this problem in Yosemite too btw. I think this is a combination of things. But thank you Bagatell for you suggestion. Ralph please concentrate on JS4. Those interested can see a screenshot of my problem on the Macosx Reaper forum until it drifts down the pages.
Gui unusable again
Posted: Sun Mar 06, 2016 3:54 am
by R Green
Since my last post the problem has resurfaced twice. Rebooted with one monitor connected again then reboot with both connected fixed.