MWorks always uses main display
This comment was split from the discussion: voltage from port DAC0
Selection of either the Main Display or Display 2 results in the display on the Main Display (the one with the macOS Dock).
When these preferences are toggled, they are updated in the user-level file (0 for Main, 1 for Display 2), but the display used does not change, and nor does the system-level file.
Lindsey.
Keyboard shortcuts
Generic
? | Show this help |
---|---|
ESC | Blurs the current field |
Comment Form
r | Focus the comment reply box |
---|---|
^ + ↩ | Submit the comment |
You can use Command ⌘
instead of Control ^
on Mac
Support Staff 1 Posted by Christopher Sta... on 14 Oct, 2021 02:04 PM
Hi Lindsey,
(I split this in to its own discussion.)
Since it sounds like the preferences mechanism is working correctly, we need to start considering other possible causes. Some questions:
Thanks,
Chris
2 Posted by llglick on 14 Oct, 2021 06:05 PM
Hi Chris,
This issue was just on a single Mac.
It followed an upgrade from High Sierra to Catalina. We did not install a
new version of Mworks (though we later tried reinstalling to see if it
would help- it didn't) or replace/reconnect the displays (I'm not sure if
this was ever tried).
Lindsey.
Support Staff 3 Posted by Christopher Sta... on 15 Oct, 2021 06:09 PM
Hi Lindsey,
OK, that's useful info. What version of MWorks are you using on that machine?
Chris
4 Posted by llglick on 16 Oct, 2021 01:19 AM
MWorks was 0.10 (a nightly). Same as on the other computers.
Lindsey.
Support Staff 5 Posted by Christopher Sta... on 20 Oct, 2021 01:58 PM
Hi Lindsey,
I created a little command-line utility that prints out some info about all the connected displays. I'm hoping it will shed some light on what's happening here.
You can download the tool from Dropbox. After unzipping it, run it from Terminal. For example, here's what happens when I run it on my iMac:
Can you run this on your problematic machine and send me the output?
Thanks,
Chris
6 Posted by llglick on 20 Oct, 2021 02:17 PM
Hi Chris,
Here's the output:
Also- I can't test the other issue with dac_cycle until we solve this one because it's the same computer...
Lindsey.
Support Staff 7 Posted by Christopher Sta... on 20 Oct, 2021 03:50 PM
Hi Lindsey,
Thanks. Unfortunately, that all looks perfectly reasonable, so it doesn't really help us.
I don't understand. dac_cycle just runs in Terminal. How does the display issue affect it?
However, it's interesting that the same machine is exhibiting both of these weird issues. Is this a Mac mini? Is it using an external GPU?
If you don't mind, could you run the following command in Terminal on that machine and send me the output?
Thanks,
Chris
8 Posted by llglick on 20 Oct, 2021 04:00 PM
Sorry- I was wrong about not being able to test things on this Mac- I can. And dac_cycle.mwel still doesn't work.
Here's the output of that command:
9 Posted by llglick on 20 Oct, 2021 04:02 PM
Also- yes- this is a mac mini (late 2012) running 10.15.7.
There is no external GPU.
Lindsey.
Support Staff 10 Posted by Christopher Sta... on 26 Oct, 2021 02:19 PM
Hi Lindsey,
Now I'm wondering if all this weirdness is due to a mismatch between the version of MWorks I built your plugin against and the version you're running. It's really never safe to use a compiled MWorks plugin with any version of MWorks other than the one you compiled it against, but usually the failure modes are obvious (e.g. MWServer crashes), so I hadn't been thinking about it.
To test this theory, can you try installing the latest MWorks nightly build on this machine? Please do not install any version of your U6 plugin (or any other non-standard plugins). Then, try loading and running the RSVP demo experiment, which is located at
If stimuli are still displayed on the main display, regardless of which display you select in MWServer's preferences, then we can rule out this theory at least.
Thanks,
Chris
11 Posted by llglick on 27 Oct, 2021 01:56 PM
Hi Chris,
I installed the nightly and ran RSVPDemo, but the display is still on Display 1.
But this wasn't surprising since the display is fine on a bunch of other computers with the "unmatched" version of MWorks.
Lindsey.
Support Staff 12 Posted by Christopher Sta... on 27 Oct, 2021 02:13 PM
OK, thanks for checking. I'll try to think of some other test to run next.
Chris