Quick Question on MIDI Signal Behavior

Author
SonicExplorer
Max Output Level: -75 dBFS
  • Total Posts : 775
  • Joined: 2004/02/26 16:44:40
  • Status: offline
2017/10/29 21:22:32 (permalink)

Quick Question on MIDI Signal Behavior

Hi,
 
I had always used an SBLive card strictly for MIDI purposes (onboard synth, etc) but now I've removed it and am relying on just my RME (with DXi synth replacing the SBLive).  For some reason though the MIDI activity light is constantly flashing on the face of the RME, even when not playing anything on the keyboard.  I am no MIDI expert so if somebody could please explain what that handshaking is about and how to make it stop, or control it, I'd really appreciate it.  First off, I'm not sure if it is even normal to be happening, and secondly it's super annoying to have that blinking light out of the corner of my eye when I'm trying to program/tap in drums.
 
Thanks,
 
       Sonic
#1

8 Replies Related Threads

    yapweiliang
    Max Output Level: -87 dBFS
    • Total Posts : 173
    • Joined: 2003/12/06 07:03:18
    • Location: UK
    • Status: offline
    Re: Quick Question on MIDI Signal Behavior 2017/10/29 23:52:42 (permalink)
    Midi clock signal? MIDI-OX software might be helpful to investigate
    #2
    gswitz
    Max Output Level: -18.5 dBFS
    • Total Posts : 5694
    • Joined: 2007/06/16 07:17:14
    • Location: Richmond Virginia USA
    • Status: offline
    Re: Quick Question on MIDI Signal Behavior 2017/10/30 03:29:47 (permalink)
    Mine blinks an awful lot too. I only look at it to ensure it is working.

    You can record it then go to the midi event viewer to see what is coming across the wire.

    StudioCat > I use Windows 10 and Sonar Platinum. I have a touch screen.
    I make some videos. This one shows how to do a physical loopback on the RME UCX to get many more equalizer nodes.
    #3
    Jeff Evans
    Max Output Level: -24 dBFS
    • Total Posts : 5139
    • Joined: 2009/04/13 18:20:16
    • Location: Ballarat, Australia
    • Status: offline
    Re: Quick Question on MIDI Signal Behavior 2017/10/30 04:40:54 (permalink)
    More information required about the controller you are using.  Some of them send a continuous handshake type message.  It is not an issue really.  It is more than likely the Active Sense message:
     
    Active Sense:  OxFE
     
    An optional "keep alive" message that, when implemented, can be used to detect if a transmitter has been accidentally unplugged. A transmitter sends them every 300 milliseconds. If the messages stop flowing, the recipient times out, and cleans up by stopping sequences and turning off notes that would otherwise be stuck on.
     
    Other controllers don't do this so you must have one that is sending that message. My Kurzweil PC3K for example does not. You may be able to set that not sure. But is usual for some controllers to do it and others to not.
     
    Just don't look out the corner of your eye and concentrate on doing the parts instead!
     
    I doubt it is a midi clock. Controllers don't often send it unless it is more of a workstation type controller and in most cases it defaults to off and you have to tell it to send. Midi clocks are ore often coming from your DAW to receiving devices that can utilise them and sync to them.
     

    Specs i5-2500K 3.5 Ghz - 8 Gb RAM - Win 7 64 bit - ATI Radeon HD6900 Series - RME PCI HDSP9632 - Steinberg Midex 8 Midi interface - Faderport 8- Studio One V4 - iMac 2.5Ghz Core i5 - Sierra 10.12.6 - Focusrite Clarett thunderbolt interface 
     
    Poor minds talk about people, average minds talk about events, great minds talk about ideas -Eleanor Roosevelt
    #4
    SonicExplorer
    Max Output Level: -75 dBFS
    • Total Posts : 775
    • Joined: 2004/02/26 16:44:40
    • Status: offline
    Re: Quick Question on MIDI Signal Behavior 2017/10/30 05:44:45 (permalink)
    This happens with an older M-Audio Keystation keyboard.  I'll have to drag out the instructions and see if it says anything about Active Sense messaging.... 
     
    *** Update ***
     
    The manual doesn't indicate any way to turn Active Sensing off.  So, I guess it will just have to stay as-is.

    Sonic
    post edited by SonicExplorer - 2017/10/30 08:01:08
    #5
    gswitz
    Max Output Level: -18.5 dBFS
    • Total Posts : 5694
    • Joined: 2007/06/16 07:17:14
    • Location: Richmond Virginia USA
    • Status: offline
    Re: Quick Question on MIDI Signal Behavior 2017/10/30 13:26:23 (permalink)
    Did you try recording it and checking the events to see what they are?

    StudioCat > I use Windows 10 and Sonar Platinum. I have a touch screen.
    I make some videos. This one shows how to do a physical loopback on the RME UCX to get many more equalizer nodes.
    #6
    yapweiliang
    Max Output Level: -87 dBFS
    • Total Posts : 173
    • Joined: 2003/12/06 07:03:18
    • Location: UK
    • Status: offline
    Re: Quick Question on MIDI Signal Behavior 2017/10/30 20:39:22 (permalink)
    Activr Sense won't be recorded and Jeff is probably right. I don't think midi clock will be recorded either. Never tried. If SonicExplorer is curious enough to learn exactly what it is then something like MIDI Ox can help. Otherwise take it as a way of confirming that the keyboard is alive 🙂
    #7
    tlw
    Max Output Level: -49.5 dBFS
    • Total Posts : 2567
    • Joined: 2008/10/11 22:06:32
    • Location: West Midlands, UK
    • Status: offline
    Re: Quick Question on MIDI Signal Behavior 2017/10/30 21:58:22 (permalink)
    The RME could be indicating a number of things, none of which are problematic.

    Firstly, MIDI clock, Active Sense, Start/Stop/Continue/Song Position Pointer messages that are sent when Sonar’s sequencer engine enters play mode don’t get recorded to tracks. They are however important for keeping MIDI-controlled stuff synchronised. I don’t think the RME will indicate any of those, at least I don’t remember seeing mine ever do it. MIDI sync/clock and what Sonar does with it is a per-project preferences setting. All that stuff is somewhere between essential and harmless depending on your MIDI hardware setup.

    What might be happening is that MIDI data is being sent to the RME because it’s being sent out of Sonar on all ports. The RME will indicate it’s receiving MIDI, though only the stuff set to the right channel will respond to it. What the LEDs do confirm is that you’re enabled the RME MIDI ports in Sonar’s preferences.

    MIDIoX is a really useful - essential if you have MIDI hardware - free application that will show you what’s being sent to what. It’s usually a good idea with any MIDI analysing tool to tell it to not show you Active Sense and clock messages as they can fill the screen pretty quickly. Unless that’s what you are looking for, of course.

    With most things MIDI, if it works then it’s often best left alone. The clock and sense related date takes up so little bandwith they’re not worth worrying about even if you have no MIDI hardware.

    Sonar Platinum 64bit, Windows 8.1 Pro 64bit, I7 3770K Ivybridge, 16GB Ram, Gigabyte Z77-D3H m/board,
    ATI 7750 graphics+ 1GB RAM, 2xIntel 520 series 220GB SSDs, 1 TB Samsung F3 + 1 TB WD HDDs, Seasonic fanless 460W psu, RME Fireface UFX, Focusrite Octopre.
    Assorted real synths, guitars, mandolins, diatonic accordions, percussion, fx and other stuff.
    #8
    SonicExplorer
    Max Output Level: -75 dBFS
    • Total Posts : 775
    • Joined: 2004/02/26 16:44:40
    • Status: offline
    Re: Quick Question on MIDI Signal Behavior 2017/10/31 05:21:12 (permalink)
    Directly from RME:  "Your keyboard sends Active Sensing messages. That is fully normal."
     
    Sonic
    #9
    Jump to:
    © 2024 APG vNext Commercial Version 5.1