Helpful ReplyThere is STILL MIDI crosstalk in Sonar

Page: < 123 Showing page 3 of 3
Author
sharke
Max Output Level: 0 dBFS
  • Total Posts : 13933
  • Joined: 2012/08/03 00:13:00
  • Location: NYC
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/17 14:42:11 (permalink)
abacab
I think one answer was to avoid leaving any midi track inputs set to Omni, except those you want to listen.
 
Apparently NONE defaults to Omni, so set MIDI track inputs to Virtual Controller, or something, unless you are actually using them.




I wish avoiding omni was the answer. Unfortunately, it's not. I currently have a project in which an instance of MIDI-generating plugin Cthulhu is sending MIDI data to a synth bass track. Therefore, the synth bass track's MIDI input is set to Cthulhu, not omni. I also have an instance of Geist in the project, another MIDI outputting plugin. During playback, if I click on the Geist track, it routes Geist's MIDI output to the synth bass track despite the fact that its input is set to Cthulhu. You can imagine the resulting cacophony of drum MIDI being sent to a synth bass. 
 
There are definitely issues of MIDI leakage within Sonar which need addressing. It's not just the issue outlined above - I was working in a project the other day in which so much as toggling mute on a track would trigger a kick drum on a completely unrelated track. There are many oddities like this in Sonar which distract from the whole music making experience. 

James
Windows 10, Sonar SPlat (64-bit), Intel i7-4930K, 32GB RAM, RME Babyface, AKAI MPK Mini, Roland A-800 Pro, Focusrite VRM Box, Komplete 10 Ultimate, 2012 American Telecaster!
#61
auto_da_fe
Max Output Level: -56.5 dBFS
  • Total Posts : 1866
  • Joined: 2004/08/04 21:32:18
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/17 15:20:24 (permalink)
Not sure if this has been mentioned as it is a very long thread.
 
None as an input does not mean none  (always shows omni)...not sure why.   But when I want 'none' i select the virtual keyboard, ch 1 (which is not active and therefore supplies no midi)   
 
I still think enable midi out is a mess and very unpredictable how inputs from vstis trigger other vstis.   I have even had enable midi out not trigger during mixdown, but plays great when mixing.
 
I have come to a personal work flow that works around all the uncertainty and weirdness but if I was new to this DAW I would be very frustrated.
 
JR 

HP DV6T - 2670QM, 8 GB RAM,
Sonar Platypus,  Octa Capture, BFD2 & Jamstix3, Komplete 10 and Komplete Kontrol
Win 10 64 
SLS PS8R Monitors and KRK Ergo
https://soundcloud.com/airportface
#62
abacab
Max Output Level: -30.5 dBFS
  • Total Posts : 4464
  • Joined: 2014/12/31 19:34:07
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/17 18:56:11 (permalink)
sharke
 
I wish avoiding omni was the answer. Unfortunately, it's not. I currently have a project in which an instance of MIDI-generating plugin Cthulhu is sending MIDI data to a synth bass track. Therefore, the synth bass track's MIDI input is set to Cthulhu, not omni. I also have an instance of Geist in the project, another MIDI outputting plugin. During playback, if I click on the Geist track, it routes Geist's MIDI output to the synth bass track despite the fact that its input is set to Cthulhu. You can imagine the resulting cacophony of drum MIDI being sent to a synth bass.




Yup, that sounds worthy of a bug report!

DAW: CbB; Sonar Platinum, and others ... 
#63
SquireBum
Max Output Level: -84 dBFS
  • Total Posts : 347
  • Joined: 2013/06/26 13:23:55
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/17 19:58:19 (permalink)
sharke
 
I wish avoiding omni was the answer. Unfortunately, it's not. I currently have a project in which an instance of MIDI-generating plugin Cthulhu is sending MIDI data to a synth bass track. Therefore, the synth bass track's MIDI input is set to Cthulhu, not omni. I also have an instance of Geist in the project, another MIDI outputting plugin. During playback, if I click on the Geist track, it routes Geist's MIDI output to the synth bass track despite the fact that its input is set to Cthulhu. You can imagine the resulting cacophony of drum MIDI being sent to a synth bass. 
 

 
What was the MIDI Input for the Cthulhu track and was Input Monitoring enabled on the Cthulhu track?
 
Just a theory, since I don't own Cthulhu or Geist:
 
Since Cthulhu is attached to the Bass Synth track, Cthulhu passes any MIDI data that is entering the Cthulhu track when Input Monitoring is enabled.  If the MIDI Input to Cthulhu is acting as an Omni port, then any data that is generated by Geist will reach Cthulhu and be passed to the Synth Bass.
 
On my system, if I select None after I enable Input Monitoring, the port does not pass MIDI.  The problem is that if I turn Input Monitoring off and back on, the MIDI Input goes back Omni and I have to select None again.
 
Hope this helps,
-- Ron
 

Cakewalk by Bandlab, Sonar Platinum x64 2017.10, X3E, X2a, X1d, 8.5
Windows 10 x64
AMD Phenom II X4 955 3.20 GHz
8 GB Ram
Nvidia GeForce 9500 GT
Echo Gina 3G
#64
mettelus
Max Output Level: -22 dBFS
  • Total Posts : 5321
  • Joined: 2005/08/05 03:19:25
  • Location: Maryland, USA
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/17 20:22:52 (permalink)
The only fail-safe work around is to record the audio out to take the MIDI offline. WRT Geist, MIDI fires off discrete (and unalterable) channels, so using any other channels within SONAR with Geist using those (up to 11 of them) is not possible. If routing were beefed up so that SONAR isolated "Geist MIDI Channel 1" to then be used as an input discretely where you want it to go would be nice, but I often get into the issue of all Channel 1 commands get heard by everything monitoring Channel 1. Internal to SONAR this should be manageable with very defined MIDI routing (visually mapped highly preferred); but if it exists, I haven't found it yet. AFAICT MIDI Channel 1 from any synth with MIDI output enabled appears the same as any other Channel 1.
 
Since Geist is a DAW in essence, I have taken to moving samples into it and recording the audio outputs (or even monitoring those outputs), but to drive other synths (like AD2) was hit or miss due to a few reasons.
 
I have not tried external routings like Loopbe30, so not sure if they are viable (but may very well be).

ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
#65
gustabo
Max Output Level: -49.5 dBFS
  • Total Posts : 2591
  • Joined: 2009/01/05 17:32:38
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/17 21:03:16 (permalink)
For absolutely no midi input, I created a midi input preset that selects channel 16 on a midisport that is plugged in but not being used.
No chance of "bleed" that way for me.
 


Cakewalk by Bandlab - Win10 Pro x64 - StudioCat Platinum Studio DAW - 32 GB Ram - MOTU UltraLite-mk3
M-Audio Keystation 88ES - Akai MPD26 (hot-rodded) - Alesis DM10 - a few guitars, a few amps
Novation Launch Control - Korg nanoKONTROL2 - PreSonus FaderPort - DAW Remote HD on iPad
Adam A7X - Behritone C50A
PreSonus Monitor Station v2 (controlling the mons)
https://www.facebook.com/groups/sonarusergroup/

#66
robert_e_bone
Moderator
  • Total Posts : 8968
  • Joined: 2007/12/26 22:09:28
  • Location: Palatine, IL
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/17 21:13:30 (permalink)
I almost always set the midi input for midi tracks to midi Omni for a specific controller, and I don't seem to have any of these issues.
 
So, I hover on one of my midi controllers, and then when the channels list opens, I usually then select the Midi Omni from there, and it just works for me.
 
Bob Bone
 

Wisdom is a giant accumulation of "DOH!"
 
Sonar: Platinum (x64), X3 (x64) 
Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22
Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64
Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others
MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es
Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms  
#67
mettelus
Max Output Level: -22 dBFS
  • Total Posts : 5321
  • Joined: 2005/08/05 03:19:25
  • Location: Maryland, USA
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/18 05:34:51 (permalink)
The issue with Geist in particular is that the MIDI output is truly an output rather than a "MIDI thru" scenario. There is a clear distinction here, so the MIDI input selection to Geist is no solution pathway. If running Geist, either MIDI output must be off, or all channels it is firing must be known. There is no visual indicator to readily know these situations to that detail in SONAR, let alone discreetly path them.

ASUS ROG Maximus X Hero (Wi-Fi AC), i7-8700k, 16GB RAM, GTX-1070Ti, Win 10 Pro, Saffire PRO 24 DSP, A-300 PRO, plus numerous gadgets and gizmos that make or manipulate sound in some way.
#68
pwalpwal
Max Output Level: -43 dBFS
  • Total Posts : 3249
  • Joined: 2015/01/17 03:52:50
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/18 08:20:24 (permalink)
sharke
 if I click on the Geist track, it routes Geist's MIDI output to the synth bass track despite the fact that its input is set to Cthulhu.

 
that sounds like a bug in the "monitor input on selected track" (or "focused"? i'm still not sure of the difference)

just a sec

#69
pwalpwal
Max Output Level: -43 dBFS
  • Total Posts : 3249
  • Joined: 2015/01/17 03:52:50
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/18 08:22:05 (permalink)
gustabo

No chance of "bleed" that way for me.
 




well, the bleed is still there, but there's no data to cause trouble!

just a sec

#70
AdamGrossmanLG
Max Output Level: -62 dBFS
  • Total Posts : 1436
  • Joined: 2014/07/13 03:40:34
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/18 10:18:12 (permalink)
sharke
A little OT but I still don't understand why "none" doesn't just mean "none." 
 
Sometimes you don't want ANY MIDI reaching a track and it's ridiculous that you should have to be selecting anything but "none" to do this. 
 
Every time I insert Jamstix into a project and use its MIDI-out I encounter the familiar annoyance of having Jamstix playing a freaking crazy-ass bass line on another track until I set that track's MIDI input to my keyboard. Sort this out Cakewalk!




BINGO!
#71
AdamGrossmanLG
Max Output Level: -62 dBFS
  • Total Posts : 1436
  • Joined: 2014/07/13 03:40:34
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/18 10:19:25 (permalink)
Anderton
I'd be happy to test this but don't know if I have any plug-ins that generate MIDI out. Do any of SONAR's built-in plugs have it, or any common ones from NI, Arturia, etc.?




Dimension Pro!
#72
AdamGrossmanLG
Max Output Level: -62 dBFS
  • Total Posts : 1436
  • Joined: 2014/07/13 03:40:34
  • Status: offline
Re: There is STILL MIDI crosstalk in Sonar 2017/01/18 10:22:58 (permalink)
I made a whole post about this "None" option a week or two ago:

http://forum.cakewalk.com/MIDI-Input-of-None-Actually-Means-ALL-m3540426.aspx
 
and here is a youtube video i made to go along with it:

https://www.youtube.com/watch?v=M9z1Lr2P5rQ&t=157s
 
but I am being told "nothing is wrong, this is by design LOL".  
#73
Page: < 123 Showing page 3 of 3
Jump to:
© 2025 APG vNext Commercial Version 5.1