No midi input on new X3 project?

Author
Post
Essentials Only Full Version
boosifier
Max Output Level: -90 dBFS
  • Total Posts : 3
  • Joined: 2013/12/29 16:13:55
  • Location: Long Island, NY
  • Status: offline
2013/12/29 16:59:24 (permalink)

No midi input on new X3 project?

I just upgraded from Sonar 8.5 to X3 and midi input does not work on new projects. Midi output works fine but if I want the input from my keyboard to work I have to open an old project. The midi input assignments are the same on the new project as the old one: either OMNI or Ch1 will work (because the data is coming in on channel 1) and I tried different "input echo" options but I still get no input light on the little MIDI activity indicator. I've seen many similar posts to this but no solution so far. Again, if I open an old project, TruPianos, BFD and Dimension Pro all trigger flawlessly from my keyboard.
Any ideas would be greatly appreciated :-)
#1

4 Replies Related Threads
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: No midi input on new X3 project? 2013/12/29 20:01:48 (permalink)
    boosifier
    I still get no input light on the little MIDI activity indicator.



    Do you mean the MIDI I/O activity indicator in the Windows System Tray, or the MIDI activity indicator at the top of the MIDI track meter? The latter is an output indicator only, and will only show activity if MIDI is being received and echoed (or played back from an existing clip)
     
    If old projects are working, it should just be a matter of having the the track's Input set correctly, and having Input Echo enabled, either by Always Echo Current MIDI Track in Preferences, or by deliberately enabling it. A screenshot might be helpful.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #2
    boosifier
    Max Output Level: -90 dBFS
    • Total Posts : 3
    • Joined: 2013/12/29 16:13:55
    • Location: Long Island, NY
    • Status: offline
    Re: No midi input on new X3 project? 2013/12/30 09:26:24 (permalink)
    Thank you for the response, brundlefly.
    Yes, the MIDI I/O indicator in the system tray shows no input activity with new projects although if I manually enter MIDI data in that track I can redirect it's output to flash the 'output LED' on the system tray indicator.
    I guess I figured that the MIDI echo could be fully controlled from the button on the track but I will double-check the Always Echo Current MIDI Track in Preferences, as you suggested when I get home today.
    #3
    brundlefly
    Max Output Level: 0 dBFS
    • Total Posts : 14250
    • Joined: 2007/09/14 14:57:59
    • Location: Manitou Spgs, Colorado
    • Status: offline
    Re: No midi input on new X3 project? 2013/12/30 11:24:42 (permalink)
    If the System Tray activity indicator isn't flashing, that's a little weird because that would usually indicate that MIDI devices aren't enabled in Preferences; but then no project would work. You don't even have to have a project open for the System tray indicator to show MIDI input.
     
    I would double-check that the keyboard is powered up before booting (assuming it's connected by USB) and showing a check mark in Preferences > MIDI > Devices > Input.
     
    If you're using a standard MIDI DIN input, tell us more about what hardware you're using.

    SONAR Platinum x64, 2x MOTU 2408/PCIe-424  (24-bit, 48kHz)
    Win10, I7-6700K @ 4.0GHz, 24GB DDR4, 2TB HDD, 32GB SSD Cache, GeForce GTX 750Ti, 2x 24" 16:10 IPS Monitors
    #4
    boosifier
    Max Output Level: -90 dBFS
    • Total Posts : 3
    • Joined: 2013/12/29 16:13:55
    • Location: Long Island, NY
    • Status: offline
    Re: No midi input on new X3 project? 2013/12/30 19:08:00 (permalink)
    Okay, problem solved! It turned out that the old projects were set to sampling rate 88.2kHz and my default for new projects was now 192kHz. Believe it or not I can enable or disable the MIDI input by simply exceeding 96kHz as a sampling frequency. The FW-410 window acknowledges each change of frequency so it's not a communication problem between the two systems. My guess is that the FW-410 engine simply has a problem supporting the MIDI functions while sampling at that rate. I have the latest driver for the FW-410 which I think M-Audio has stopped developing further. I think that for now, 96kHz will be fine and at least I can continue working.
    Thanks again brundlefly for your help.
    #5
    Jump to:
    © 2025 APG vNext Commercial Version 5.1