Giters

benkuper / Chataigne

Artist-friendly Modular Machine for Art and Technology

Home Page:https://benjamin.kuperberg.fr/chataigne

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Temporary freeze on MacOs when screen automatically turns off

DonGuig opened this issue · comments

commented

Environment

  • OS: MacOS 13 (I don't have the sub-version, but I can get the info if necessary). Mac mini M2.
  • Version : 1.9.13

Describe the bug
I have a project with sequences containing both mapping to osc tracks and mapping to Sacn tracks. In MacOS, the screen was set to turn off after a few minutes. Whenever this happened, the playback of the sequence seemed to freeze for a few minutes. Either it unfroze by itself after that, or if you interacted in any way with chataigne/the computer (for example trigger a sensor that sends OSC messages to Chataigne, or press a key to have the computer screen turn back on) the playback resumed (or rather caught back the lost time instantly). I made it so that the computer screen never turns off automatically as a workaround. Interestingly, having another computer logged in VNC to the mac mini, and letting that VNC connection idle for some time seemed to trigger the freeze as well.

To Reproduce
Steps to reproduce the behavior:

  1. Have a sequence with mapping track play
  2. Set macos to turn the screen off after a minute
  3. See if the mapping info is still output by Chataigne when the screen turns off

Expected behavior
The output (osc messages or sacn packets) should stop during the bug

commented

Thank you for the feedback, hard to say where it comes from, I'd have to test on windows but pretty sure it's not a problem.
You could try having a sound card module and linking the sequence to it (with an audio layer). This would force the playback to use the sound card instead of a separate thread.
I suspect some interference from Mac that decides to cut down resources or "put to idle" some stuff when going to sleep.

You can also try to use the "close to tray" option in preferences an close the window. This would insure that the whole software is not relying on UI, so it wouldn't come from that.

commented

Thanks for the quick reply ! Yes, these may be workarounds I'll try if I go back to this piece (it's running permanently in a museum), for now my workaround has been to keep the screen on at all times. I just thought I'd mention it in case you'd have a good idea what's going on and how to fix it in code, but I understand it's hard to troubleshoot.

commented

And thank you for the donation !! :)