• SONAR
  • MIDI input lost after Professional upgrade
2017/01/30 20:56:48
guyshomenet
I've been using a Lexicon Omega as my only I/O for years. Used it for audio and MIDI without significant problems under Sonar X2.
 
I upgraded to Sonar Professional and MIDI input from the Omega cannot be had (output is fine ... using Omega through to the reference monitors). I checked the obvious Preferences sections, and all seems to be well there.
 
I suspect I'm missing something either new or obvious with Professional. Any ideas and tutorials for debugging would be helpful and welcome. Especially any tools to prove the signal/note path (like validating that other software can get the midi notes from the ASIO interface).
 
(purely frustrating that every time I think I can get some work done, one or another Sonar quirk knocks that into the trench).
2017/01/31 02:48:12
brundlefly
guyshomenet
MIDI input from the Omega cannot be had



What does this mean exactly in terms of routing and symptoms? 
2017/01/31 07:25:37
mudgel
I'm with brundlefly, I don't quite know what you mean but if it will help, google MIDI-OX. It's a great utility for debugging MIDI pathways and has a variety of uses that might help you explain what you mean in a more understandable way.
2017/01/31 09:20:30
Keith Albright [Cakewalk]
Does it still work in X2?  The MIDI ports usually can be used by one program at a time.
MIDI-OX will open the MIDI port the same way SONAR does.  It can show whether or not anything is coming through.
 
2017/01/31 10:57:50
guyshomenet
Thanks for all the help. I'll grab MIDI-OX ASAP.
 
For clarification sake, a MIDI track which had previously received notes via the Omega was no longer receiving them. In fact, a new test track with input set to omni received nothing as well.
 
That being said, it is for the moment fixed. During a mad attempt to isolate the problem, I switched from ASIO to a different driver, exited out of Sonar, switched back to ASIO (and a few other stunts) and the midi notes returned.
2017/01/31 11:35:41
brundlefly
The only way to know whether MIDI is 'received' at the track is to record it or echo it to some output. That's why I was asking for clarification of what exactly isn't working. Is it that nothing gets recorded or that there's no MIDI track meter activity when echoing to output or the synth (software or hardware?) doesn't respond, or all three?
2017/01/31 13:58:08
guyshomenet
brundlefly
The only way to know whether MIDI is 'received' at the track is to record it or echo it to some output. That's why I was asking for clarification of what exactly isn't working. Is it that nothing gets recorded or that there's no MIDI track meter activity when echoing to output or the synth (software or hardware?) doesn't respond, or all three?



Thanks, and right on. But there might be a situation where the interface is faithfully delivering notes to the OS/driver, but the OPS drops it. Another situation (and this was the case) is that the OS/driver delivers it to the DAW software, but the DAW does not process it.
 
This was why I was looking for a tool that would show the path from interface to DAW, to see where in the chain the notes were being lost. As it is, I'm betting Sonar quit listening to the driver, but for reasons I don't know.
2017/01/31 14:48:19
brundlefly
guyshomenet
During a mad attempt to isolate the problem, I switched from ASIO to a different driver, exited out of Sonar, switched back to ASIO (and a few other stunts) and the midi notes returned.



Ah, okay, I overlooked this part of your previous post.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account