Hi all,

New to Opusmodus here (really loving it so far!)—two questions:

1. I'm working on a project where I am sending MIDI from Opusmodus to Supercollider via an IAC port. I've noticed that the more I use Opusmodus, the slower performance becomes, particularly when playing back notated material but also when typing in the IDE and processing functions. Upon restarting Opusmodus, the issue is fixed, but it seems to need a restart every hour or two. I have been interrupting the listener and stopping audition to try to clear anything holding on in the system.

2. As I've been learning, I've been opening a lot of help files (not sure if this is connected with the issues I'm having in #1, but the issue persists even after I close the files). When I press command-D to view the documentation for a given function, it leaves the file I was working on to open the help file in the same assistant window. Then, when I press the back arrow at the top left, it doesn't take me back to the project I was working on, but whichever help file I looked at before that. Usually there's a long list of recents that I have to sift through to get to the file again. Is there a shortcut to open documentation in another tab? It's not a huge deal; I can just keep another assistant window open, but it'd be good to know if there is another way.

   
   Best,

   Jack

Yes, i have the same problem, when i'm using midi-play. When i do more then about 20 "simulations", the player makes more and more troubles and i have to restart Opumodus :-/

Yes, I can reproduce the issue, will have a look. At the moment you can always reste the MIDI with: Tools/MIDI/ Forse All Notes Off. In pratice this should help.

14 hours ago, opmo said:

Yes, I can reproduce the issue, will have a look. At the moment you can always reste the MIDI with: Tools/MIDI/ Forse All Notes Off. In pratice this should help.

Many thanks!

Best,

Jack

The progressive MIDI resource accumulation is resolved in 4.0.31960

On 7/13/2026 at 3:28 PM, opmo said:

The progressive MIDI resource accumulation is resolved in 4.0.31960

Apologies as I am just seeing this now. Thank you—I do think the issue improved somewhat after that update. Unfortunately, the issue is definitely still persisting for me even in the latest version. If you would like I could try to create a version of the issue that is repeatable sometime this week.

I believe (at least for me) this issue has been resolved in the latest version I’m using (4.0.31989).

Same problems here

7 hours ago, AM said:

Same problems here

Yeah, me too—after testing the new update for a while, it seems similar for me. I can't tell exactly what is causing the issue because it accumulates so slowly, but I can say that if I am working in a project and generating a lot of scores with command-1, performance gets worse over time.

On a related note, the midi bar doesn't seem to really follow the score very well, especially when this is happening. I've noticed a correlation where, in general, the worse the MIDI playbar is doing at following along with the playback, the more likely it is for there to be performance issues (curiously it's not completely 1-1 though; sometimes playback works fine and the playbar is skipping around a bit).

Also—unless I was just missing something earlier, my #2 request seems to have been addressed, so thank you!

On Mac Option+Command+z is your friend (reset midi)

21 hours ago, Stephane Boussuge said:

On Mac Option+Command+z is your friend (reset midi)

That plus the update did the trick for me—thanks!