dazarz

I have done quite a lot of testing recently, unfortunately my theory about the relationship between the number of monitors connected and the ability to enable DirectMusic has not been confirmed. It was a coincidence then. I currently enable DirectMusic every time. But I cannot change the MIDI port, then an error occurs. I will continue testing.

After dozens of attempts, I managed to enable DirectMusic in Steem. The DM initiation time while turning on in my case is about 45 seconds.... That's also how long I have to wait when starting Steem. So far, I have been launching Steem when Windows has two monitors on. The successful attempt was with the second monitor disconnected. Tests in Cubase -> MIDI Out look encouraging, timing is much better, connected instruments are now not reporting errors. But I've noticed long delays in MIDI In -> Cubase....

Thank you for the clarification. I've tried all the settings, still no good. I also can't turn on DirectMusic because soon after clicking the option - Steem first freezes for a few minutes and then displays an error window: "MS Visual C++ Runtime Library - Runtime Error! This app has requested the Runtime to terminate it in an unusual way." I'm curious if the cause is a problem with the VC++ library or if it's that I have about 20 MIDI (IN/OUT) ports on my system.

I have a question about MIDI in Steem since version 4.0.x - Which settings are critical when it comes to using Steem in a MIDI environment? I've been using Steem for many years and the last version that I manage to configure correctly for MIDI is 3.9.4. Since version 4.0 MIDI behaves less well when it comes to playing more complex sequences. It's not just a matter of uneven timing, but often messages are displayed on instruments connected to Steem indicating that some bytes are being lost. Does anyone...

I have just installed the version 4. Unfortunately in Options -> I/O Ports -> MIDI Ports - I can't find any of my midi outputs... only the "None" appeares... But all midi inputs are available. What's the problem?

Tim Conrardy passed away on Feb 28, 2009 - but his website has many helpful articles so I suggest replace the dead link with the archived link: http://tamw.atari-users.net/ -> https://web.archive.org/web/20100504085054/http://tamw.atari-users.net/index.htm and this one: http://dev-docs.atariforge.org/ -> https://web.archive.org/web/20171016150036/http://dev-docs.atariforge.org/ This is a must! The same way the others (although not a must): http://aicq.atari-users.net/ -> https://web.archive.org/web/20160503205108/http://aicq.atari-users.net/...