X2 Midi CrossTalk going from controller to VST

Author
Post
Essentials Only Full Version
MrMan
Max Output Level: -90 dBFS
  • Total Posts : 15
  • Joined: 2008/07/25 03:45:14
  • Location: Hertfordshire England
  • Status: offline
2014/01/07 08:26:48 (permalink)

X2 Midi CrossTalk going from controller to VST

I am getting a few problems with Midi Crosstalk in Sonar X2. I have recorded some midi data that controls Rapture, I then set the Rapture Midid input to None (Which switches on OMNI (which is also annoying) or to a unused midi chanell on one of my serveral ports)) and play the events. When I then set my controller to play a patch on Dimensions Pro, My controller plays the Dimensions patch AND the Rapture patch. whatever I do with the midi input setting on Rapture I cannot stop the controller from playing it. I use 4 x midi Ports and 2 x USB Midi ports and have several synths hooked up to these. I experienced this problem in X1 but it seam to still be present in X2. This has occurred in various combinations and not necessarily just VST Plugings, 
 
Does anyone have any experience with this behaviour and any clues how to stop it from happening ?
 
Happy new year !

Sonar X2 Producer
Dell XPS 420, Intel Q6600 Quad Coreâ„¢ (2.40GHz, 1066Mhz FSB, 8MB cache) 3GB RAM 2 x 320GB (7200RPM sata) Windows 7 (32) 
EMU Tracker Pre USB Audio interface
M-Audio 4 x 4 USB midi interface
Roland Fantom G7 & V-Synth GT,  Korg Z1 & MS2K, Novation UltraNova, Akai MPC1000
#1

1 Reply Related Threads
    SilkTone
    Max Output Level: -59.5 dBFS
    • Total Posts : 1566
    • Joined: 2003/11/10 17:41:28
    • Status: offline
    Re: X2 Midi CrossTalk going from controller to VST 2014/01/07 15:10:16 (permalink)
    Sonar has had some very long-standing MIDI routing issues. The most serious of these have finally been fixed in X3d, however some still remain, see here.
     
    You might not be able to work around this issue unless you upgrade to X3d, although there are some things you can try that may or may not work:
     
    • Make sure not to set Echo=ON on the Rapture MIDI track.
    • Make sure not to select the Rapture MIDI track while playing on the controller.
    • Make sure Dimension Pro has "Enable MIDI Output" turned off (right-click on it in the synth rack and make sure the option isn't checked). This is often the root of all evil when you have MIDI crosstalk/crashes in Sonar. For that matter, unless you really really need to route MIDI events out of a VSTi into another plugin (in which case you can only do it with one VSTi or else Sonar will crash), make sure they ALL have this option unchecked.
    Hope you get it sorted out.
     
    EDIT: I really don't know what the issue is with Sonar insisting on switching to Omni whenever you select None as input to a MIDI track. This is tied to the "Always Echo Current MIDI Track" option, however I really wish there was a true "None" setting for MIDI track input when the "Always Echo Current MIDI Track" is checked as the behavior is confusing and it isn't clear what this Omni is referring to.
     
    A workaround for this is to use one of your unused MIDI input ports (I use the unused MIDI port on the back of my controller), and rename the port to "No Input" or similar. I then select that input when I want to truly have no input going into one or more MIDI tracks.
    post edited by SilkTone - 2014/01/07 15:16:29

    Windows 10 Pro x64, SONAR Platinum 64-bit
    Focusrite Scarlett 18i8 USB, ASRock Z97 Pro4, Haswell 4790k @ 4.4GHz
    32GB DDR3/1600, 500GB SSD (OS) + 256 GB SSD + 3TB MD
    NVIDIA GTX-1070, 40" 4K Monitor + 1 Monitor in ISO booth
    #2
    Jump to:
    © 2025 APG vNext Commercial Version 5.1