MIDI Signalflow

[Glenn Stanton]

is the issue that you have multiple MIDI devices sending DAW control signals? in my setup, i have one device which (in addtion to all the other MIDI info) is the controller of DAW commands (Start, stop, etc) and the other simply provides note, velocity, modulation etc and volume information. i guess technically i could use the non-controller to send commands as well but i just don't). if it's things like program changes, presumably that is based on the channel rather than the controller MIDI.

[Bass Guitar]

58 minutes ago, Astraios said:

For example, if you start triggering two different plugins with two hardware MIDI controllers, the Sonar remote control function can't distinguish between ports, so overlaps occur very quickly, and you suddenly control two things with a single command

I explained how to prevent this by using midi channels. As I said I used Sonar Live and had no problem playing the synth I needed. I see no issue with using 2 controllers either. You just choose the channel you want to use. To here the sound input Echo has to be on and you can set it to be Globally on for all instruments. 

I don't know how many people have explained what input echo is for but somehow your not understanding that. Its a simple matter of not desiring how you think it should work it's a matter of understanding how it does work and learn that so you can take control. 

[Wookiee]

@Astraios are you sure you have set the tracks sending to these devices to receive on specific MIDI ports & channels. If you are using omni then it will receive on all channels. 

[Amberwolf]

8 hours ago, Astraios said:

 But if you could block individual inputs, then Sonar wouldn't even need to distinguish what's coming in. So there's no way to temporarily exclude a device from the MIDI flow? That means Sonar lets all MIDI data in unfiltered at once, unless you deactivate the device in Preferences --> MIDI Devices. So "All Devices In" is actually it's nature.

If you set a specific input port and channel on a track, only data from that should end up recorded on that track.   If something else is happening, I'd call that a bug.  

If you require more than one device input to a track, the only way I am aware of is to set it to All-Inputs (either picking a specific channel or leaving it at Omni)

If doing that, then without using some form of external filtering before it reaches Sonar), everyting on all the ports (and channel (s) chosen) would be recorded on that track. 

External hardware-input filtering could be accomplished by using MIDI Loopback type drivers, and passing all MIDI ports via those into a separate program that either does this filtering as a primary function built in, or hosts VST / MFX that can then do the desired filtering.  I don't have any list of such hosts, but there should be some out there.   (even other DAWs could be used for that purpose alone if they support the necessary functions and routing). 

 

 

2 hours ago, Astraios said:

Based on my intuition, without understanding the programming aspect, it should be the case that when Echo is off, no more MIDI data is active from the MIDI device. I don't know if that's even technically possible...? 

All Echo does is Echo the input directly from the input selection to the output selection, for that track, regardless of playback or record states. It changes nothing about what is or isn't recorded to the track, or played back from the track.

For instance, if you don't have the track armed for recording, everything will still be echoed from the input port/channel to the output port/channel, and will pass thru any track FX on the way.

Even if you don't have the transport running, so that no track data is being output, Echo should still do it's job.  (I think it will stop if the audio engine is not running, however).

When echo is not on, the data cannot reach the output until it first is recorded onto the track, and then subsequent playback of those regions will output that data to the output port/channel. 

 

This is true of audio or MIDI. 

 

 

2 hours ago, Astraios said:

Just to clarify again: The whole problem only becomes apparent with extensive remote control projects. For example, if you start triggering two different plugins with two hardware MIDI controllers, the Sonar remote control function can't distinguish between ports,

I have a feeling that is a separate issue from the track input selections and filtering.  I don't have a way to test this here ATM, but you've already likely done enough testing to determine:

 

If a synth (whcih is using MIDI Learn / remote control on it's fucntions) has been inserted on a track that is itself set to only receive from a single port still receives data from multiple ports, then that means the remote control is not using the track input selections at all, and a completely separate port setup and filtering system would have to be coded and built into Sonar to correct this issue--there would be no external way to deal with this without also blocking data from reaching the actual tracks themselves as well, becuase all ports are combined into the Remote control / Learned control system.

If that synth does only receive data from that track's selected input port then all of the filtering options previously specified would work--but I expect from your issues that this is not the case. 

Same for track controls using Remote Control.

 

If the former is the case, the only way I know of to fix this issue is for the bakers to recode Sonar itself to have a tool within it to allow the user to choose which ports and channels are used for each thing that is receiving or sending remote control information (the most versatile method), or for it to obey it's host track's port configuration (which would be problematic for some remote control usages), or some global configuration that all RC things use (extremely limiting and problematic, I suspect).  

 

[Amberwolf]

BTW, for all the readers of the thread, there are, AFAICT, two separate  MIDI routing systems within Sonar.  

 

If this is incorrect, please specify where I've misunderstood or gone wrong.

 

The first is at the MIDI tracks themselves, and obeys all the track controls, etc.  

 

The second is the Remote Control system, which AFAICT without being able to test ATM, does not have any control over which ports or channels are received by or sent from a widget (on a track or inside a synth, etc), it globally recieves or sends this data on all ports. (possilby restricted to hardware ports vs synth's virtual ports internal to Sonar), restricted only by the channel selection when assigning a remote control.  (which cannot be set to send or receive on more than one channel, AFAIK, no Omni option for instance; not sure if there is any reason to be able to have that ability). 

This system is used even if there are NO MIDI tracks at all, as you can use this system to assign RC to audio track controls, for instance, and that is almost certainly why this second system even exists.  

 

This second system is the one Astraios is having issues with, in trying to do external control of assorted things within his projects. 

 

 

Edited 5 hours ago by Amberwolf

[Astraios]

5 hours ago, Bass Guitar said:

Its a simple matter of not desiring how you think it should work it's a matter of understanding how it does work and learn that so you can take control. 

As for my whole life, Eckhart Tolle couldn't have put it better. I'm sorry, but you're right, I've had ADHD my whole life. It's a bit complicated. Thanks anyway.😇

Edited 2 hours ago by Astraios

[Astraios]

Okay, so here I'm controlling a Z3TA+2 with about 240 CCs (without MIDI Learn) About the SetUp: best watch from minute 8:00 onwards.

 

Edited 2 hours ago by Astraios

[Astraios]

4 hours ago, Bass Guitar said:

I explained how to prevent this by using midi channels. As I said I used Sonar Live and had no problem playing the synth I needed. I see no issue with using 2 controllers either. You just choose the channel you want to use. To here the sound input Echo has to be on and you can set it to be Globally on for all instruments. 

 

You're right. The sonar remote control window can actually process 119 x 16 = 1904 commands. 119 CCs across 16 channels. That should be enough! If you also had the 16 ports, it would be a spectacular 30,464, and nobody would ever need that many... 🫣

 

Unfortunately, you can't save the project-specific assignments to a transferable preset.

Edited 2 hours ago by Astraios

[Astraios]

4 hours ago, Wookiee said:

@Astraios are you sure you have set the tracks sending to these devices to receive on specific MIDI ports & channels. If you are using omni then it will receive on all channels. 

Hey Wookie, I'm tinkering with this so much right now that I sometimes get things mixed up and everything gets a bit blurry. Sorry for the confusion, but I see things more clearly now.

It's great that so many people responded and took the time to help me.