Lemur editor and Daemon don't work on OSX 14.7 (multiple screens)

[earmade]

Hello,
I'm a old Lemur user (still have the real one...). I was happy to hear that the app have just renewed from his aches. So I took a look at the editor before considering paying an annual subscription to the IOS app. But, unfortunately, I still encounter the same problems I had before. I have a 3 screens set on my Mac M1 (osx 14) and whenever I open the lemur editor It get stuck on the screen and it is impossible to do anything, even move the window. As for Daemon, clicking on "set up daemon" will do nothing. I'm really disapointed to see that the same problems occur again and have not been resolved. Is anyone having the same issue ?

[midikinetics]

Hi,

Thanks for the report. Indeed this issue was looked at and it seemed to have been resolved on the various setups that were tested, so I am very sorry to hear that it is still happening

The Lemur Daemon issue is likely the same issue as the Editor--- it is showing something but potentially off screen so you can't see it. Can you please post below your monitor and computer specs below? Can you also please try disconnecting all your external displays except one and then trying again. Once you do, please try to set the monitor display resolution to its native resolution.

Thanks

[earmade]

Hi,

Thanks for your answer. I tried with one monitor and it works (1920x1080) . Even with the second one (1920x1080)
The 3rd one is older and has a lower definition (1680x1050). Actually the older one was "above" the two others (in the monitor configuration window) so I put it on the far right, and the monitors are now (virtually) side by side. Now It works.
I will make further experiments but obviously there's an issue with the mixing of different resolutions..

[midikinetics]

Awesome! I'm glad it worked.

Ugh, I completely understand how frustrating this bug can be, and believe me when I say your frustration is shared. I worked hard on fixing that one and It’s been a tough one to tackle because it’s so dependent on specific setups—mixing resolutions, monitor arrangements, and configurations all seem to play a part in its unpredictable behavior. While I know exactly where the issue stems from in the codebase, reliably reproducing it has been almost impossible.

Please do let me know if it happens again or if you discover any other quirks during your experiments. Every bit of feedback helps me zero in on these tricky edge cases. Thank you!