I have a random MIDI signal that's started coming into my DAW every second or so. I think I've narrowed down the device as when I unplug the USB, the signal trigger stops. However, I'm wondering if it's possible to detect in some way what button, rotary, or fader on the device is sending the signal so I can have a look at whether it needs a clean on that component at all.

 

ReaControlMIDI can log MIDI events - it's part of ReaPlugs (free).

https://www.reaper.fm/reaplugs/

(not sure how different it is from Reaper's own ReaControlMIDI)

 

The 'event' or 'list' editor (or however it's called in your DAW) should be able to show you what's incoming in realtime.
But finding out what exactly was the trigger is hardly possible this way. For this you'd need to move all controllers separately and see which of them has the same 'ID'.

 

Nevermind. Found this free tool and worked perfectly for my purpose: https://hautetechnique.com/midi/midiview/

It seems like the original PreSonus Faderport is sending a C2 note at velocity 127 every 6 or 7 seconds. I've looked into this, and can only find a single reference or two to someone having the same issue, and they suggest this is standard and the device reporting it's alive and present to the computer (second post here: PreSonus Forums | Faderport 1 - any reason NOT to use one? | FaderPort Classic - General Discussion)

Anyone know if it's possible to stop this, or the easiest way to prevent this as whenever I load a MIDI instrument, it sends this MIDI trigger that sets the instrument off???

 

As this device is a track controller, NOT instrument controller, it should not be a problem.
Because it will be declared as track controller in your DAW, NOT instrument playing any note.
Mackie Control send notes too. And other track controllers too.

So i don't understand what is your REAL problem ?
Thousand ppl use it without any trouble, even with this note trigger.

You can filter MIDI with Midi OX and virtual MIDI cable MIDI Yoke
http://www.midiox.com/index.htm?http://www.midiox.com/myoke.htm

But to me, it is better to configure your DAW the right way, by NOT declaring FaderPort as instrument BUT only as track controller.
So this "note" will do nothing.

 

according to the manual that is the midi that is sent every time the arm led flashes
https://files.bbystatic.com/kTFBOB5s9vgICdqoY7ipPw==/a8c7b53c-fa23-4333-8585-47eda8e2831e.pdf

 

This is the manual for the newer Fadeport, mine is the Classic version, as in the OG v1.

 

I set up the device as per PreSonus instruction on how to set up with Cubase and this note is triggering instrument notes on MIDI instruments when I load them.

 

Try Midiox
http://www.midiox.com/
+
Loopmidi
https://www.tobias-erichsen.de/software/loopmidi.html

This is one way around but a proper way, in my opinion assuming u dont need that specific signal anymore.
I dont know what daw u r using, but evey Daw has a feature to enable and disable midi from hardware unit.
So first disable it, so u don't revive midi from that hardware.

install both midiox and loopmidi virtual port, if u dont have if u have any other midi virtual ports use it anything works with MidiOx

Open Midiox, u c a toolbar on top, few icons next to comb click "select midi devices" select ur input device, Select Input as Faderport (In the mean time open loopmidi and create a dedicated vitual output port).

Now click the comb icon to filter input, isolate the port sending the signal and block it.
Select output to Loopmidi port u just created.

Open ur Daw Enable the virtual midi u created that receives the filtered signal.

If u r using this method, just make midiox to open during startup.

Or
u could just use Daw cc filter to block the signal.

 

Last edited: May 24, 2023

To be clear, this only triggers notes on midi instruments in Cubase?
It causes no problem in other DAWs?

 

Nope. Also in Ableton and Pro Tools, but not in Studio One. But I think it's fixed now.

 

The first step here fixed it when I did some digging. There was already a Faderport dll file in Cubase's Shared Components folder. However, I removed that and downloaded the one from the first link here and placed it is the Steinberg Shared Components within Program Files\Common Files instead. It then seems to work properly without sending this C-2 trigger to every instrument!

Thanks for the link @ItsFine which prompted me to do some digging in this direction and I eventually found a random post saying to put the dll in Common Files instead!

 

Last edited: May 25, 2023

Great to hear it's fixed.
You might change the title to reflect that ( maybe change "--how to fix?" to "-[FIXED!]")

 

Happy you found a fix !
It way help other ppl too

 

Almost, [solved] is better because it would be included in search results.