• SONAR
  • No midi events arriving at sonar platinum
2015/12/12 10:26:15
steffens.matthias
Hi there,
 
I am using the actual sonar platinum version (Kingston) and an Axiom 49 midi keyboard (usb). This works fine for month but since yesterday no midi event is arriving at sonar.
The Axiom midi device is found by sonar and correctly inserted in the routing (so midi device is set and channel/instrument is using the Axiom as input device. I even tried to use "ANY" input device Omni). So the systems behave as always (unplugging = system asks me to delete this device, plugging the keyboard = sonar ask me if it should be used and correctly changes the input device visible at the instrument channel).
 
Anything else works fine. I can playback my songs and use the onscreen keyboards to play sounds but nothing happens when I use my midi keyboard.
I tested with standalone applications of some synths like Tone2 Nemesis or the ZTA3+ 2 and there I can use my midi keyboard without any problem. Even Windows is showing me that midi data is arriving but when using sonar = no input :-(
Maybe someone has an idea?
 
Thanks in advance
 
Matt
2015/12/12 10:37:50
Anderton
There's a chance you could be on the borderline of the Windows MIDI port limitation. Probably not, but it's easy enough to check.
2015/12/12 10:57:43
steffens.matthias
Hello Anderton,
 
thanks for this idea. Unfortunately this seems not to be the problem point. I have 6 Midi Devices (2 High Definition Audio devices, M-Audio Axiom 49, NVidia High Definition, Plantronics Wireless Audo and Scarlett 2i2 and all of them are marked as "working/available" indicated through a small speaker). I unplugged my Scarlett 2i2 und so only 5 audio/midi devices left. I opened sonar but nothing changed at all. Everything looks perfectly (Axiom Midi device is visible und midi devices and can be used for an instrument). Even windows shows "midi activity" indicated by a small icon within the systray. Very strange. I have opened a case for this and will post solution in this thread.
 
Anyway thanks for trying to help me.
 
Matt
2015/12/12 11:09:28
brundlefly
I think you need to verify the problem is input and not output from the track. MIDI track meters are always metering output (even when the track is armed to record). Just because the track shows no live input being echoed out, does not mean it's not receiving MIDI. So, using separate MIDI and synth tracks, the first question is:
 
- Can you record MIDI?
- Is Input Echo enabled on the MIDI track, either by being forced on, or by having 'Always Echo Current MIDI Track' enabled in Preferences?
2015/12/12 11:18:36
steffens.matthias
Hello Brundlefly,
 
you were right. When recording, sonar received midi data and after manual enabling midi echo = I could hear and see that I am playing. I maybe was wondering about this stupid self-mistake as this happended to all songs. So it seems that the general midi-echo enforcement maybe was disbaled by myself. So ashes on my head.
 
EDIT: I found out why I have disabled "midi echo" ! When enabling input midi-echo then the record has all notes twice! But this seems to be solved by another settings as disabling the input echo is not allowed!
Sonar is recording notes twice if I am using "Axiom 49 Omni". If I am using the dedicated midi channel 1, sonar is recording correctly. As I am sure I have always used the "Omni" settings, something else must cause this issue. But i will find out.
 
Thank you for help find out.
 
Best Regards to all for such quick help.
 
Matt
2015/12/12 11:45:06
brundlefly
Glad to hear you got the input echo problem sorted. For the note-doubling problem, that might be because you still have the track Input set to Axiom - Omni, or All Inputs - Omni, and the keyboard is transmitting on more than one channel or is connected by both USB and MIDI DIN cables.
 
Check the Event List of a recorded track to see if duplicate events are on different channels, or have slightly different start times. In any case, setting the Input to a specific port and channel should eliminate the problem whatever the root cause, and is usually a best practice.
© 2026 APG vNext Commercial Version 5.1

Use My Existing Forum Account

Use My Social Media Account