MIDI shout Logic

Hello, New forum member here. I'm very glad actually having discovered these MIDI capabilities of the Stream Deck. Big thanks to all involved! 
I'm in Logic and there is one problem. Even though I followed the steps for setup several times, restarted computer, DAW & the same all over again, every time I switch from an application (eg Stream Deck) back to Logic, there are all sorts of MIDI events being triggered. Result is depending on the activated plug-in either a hit, shout or hanging long notes. Please have a look at the short screen recording & the Midi Monitor file attached. Video has no sound, I spare you the noise. You can see what's happening in the MIDI monitor. Thanks!!!

Hi,

Assuming that you are using the Mackie Control functionality, this kind of problem can occur if you have not disabled the midi out ports from also being midi in ports in Logic.

Please verify that you have configured your midi ports in Logic as described in the last section of the "How do I configure Midi ports in Logic" on the FAQ Page.

If that is not the problem, please enable extended logging as described on the FAQ page, trigger the problem and send me the log file.

Hello, attached the log file. But I think I understood & it works all fine so far. Although I had turned off the Inputs in the DAW settings the In/Outs between Control surface vs StreamDeck App vs DAW weren't coherent.

Now I have: 
Control surface Out = DAW2Mackie
Control surface In = Mackie2DAW
StreamDeck CC Fader Midi Out = StreamDeck2DAW
StreamDeck CC Fader Midi IN = DAW2StreamDeck

Buses DAW2StreamDeck, DAW2Mackie & DAWTrack2StreamDeck are OFF as MIDI Inputs in Logic Preferences (or "Settings" since 10.7.5)

After enabling extended logging, you didn't do anything that affected the plugin, so the log file has no helpful content.

Do I understand you correctly that everything works as expected now?

I find it odd that you use StreamDeck2Daw/Daw2StreamDeck on the Stream Deck side and Mackie2Daw/Daw2Mackie on the Logic side. If they don't use the same set of ports, they can't communicate.

Yes, it works with no audio quirks happening whatsoever. For this set-up I assumed two things:
1) StreamDeck Out ports must go towards the DAW & MCU Output port must go from the DAW
2) I have no idea about the properties of the Mackie protocol, but I assumed it must be somehow superordinate or higher in hierarchy to the others & so it could be capable of with the others.
I based my initial configuration on the set-up video for Mac on YouTube where the instructor suggests using the Mackie ports on the DAW side (7'46"). In theory, is it required to set up a MCU Pro device for each of the three midi buses, that is DAW2StreamDeck, DAW2Mackie & DAWTrack2StreamDeck?
Another log file attached 

I'm a bit confused. You have a Mackie Control device defined in Logic (the MCU Pro), but don't use the Mackie Control buttons in Stream Deck? I suggest that you use Mackie Control all the way; that would make things so much easier for you.

The Mackie Control protocol is just ordinary Midi messages (mainly Note On/Off) redefined for remote control purposes.  The protocol is bidirectional, where the device (Stream Deck, in this case) sends remote control commands, and the daw responds with state information (fader position, LED, and display information).

Since the Mackie protocol is just regular Midi messages, it must not be routed to ordinary tracks or anything else than the Mackie Control driver in the daw. For the Mackie Control protocol, you need two ports; Mackie2Daw and Daw2Mackie. The Stream Deck (Mackie Control) buttons should send on Mackie2Daw and receive on Daw2Mackie. The MCU Pro device in Logic should send on Daw2Mackie and receive on Mackie2Daw. You must ensure that these ports do not reach tracks in Logic (I don't know if that is automagic).

If you need Stream Deck buttons that should affect the tracks (e.g., for articulation), you use StreamDeck2DawTrack/DawTrack2StreamDeck for that purpose.

If you need Stream Deck buttons for another kind of remote control (i.e., not Mackie Control and not track control), you can use StreamDeck2Daw/Daw2StreamDeck for that purpose.

All port names are only suggestions; the important thing is that Mackie Control has its own set of ports used for nothing other than the Mackie Control protocol.