Hi all, i've just recently updated Sonar to X3d, previously from X3c. i noticed 2 issues which i may have not noticed before.
 
1. REMOVED: to be started in another thread
EDITED: New thread
http://forum.cakewalk.com/PC-FX-Chain-led-not-lighted-m2963930.aspx#2963930
 
2. VST Midi out
 
recently there were some posts going on about this. though i have done this many times before in X1d and also X3b & X3c, i am not sure if this is normal behaviour and i really cannot remember if this was working before for the Korg Legacy Collection.
 

1. loaded Kontakt and necessary instrument - split into Instrument and Audio Track
2. enabled MIDI out from Synth Browser
3. placed MIDI noted on Kontact MIDI track
4. test play - all ok
5. inserted a new MIDI channel
6. hit Echo and Record on new Midi Track
7. hit record, midi notes, events, Midi CC...etc, all is well.... (i am doing this because at times i need to convert Controller Automation to Midi CC)
8. however,

if i changed the instrument to any from the Korg Legacy Series (ie M1 or Wavestation) following the original steps from above there would not be any thing recorded onto the new Midi track. The input led on the Midi track is not even flashing as if there is no input signal.
 
could it be that there are some instruments that will only enable Midi out? i also noticed from the Help file that certain VST instruments do not have this Midi out feature and thus the Enable Midi Out will be greyed out from within the Synth Browser. The strange thing is that on every Korg Legacy plugin, within the Synth Browser, the Enable Midi out is clickable.
 
could others kindly advice...??? many thanks all... 

Bump...
 
hi all, any advice on this...  many thanks again.

I can't talk to your exact issue but I can say that there are still some bugs related to MIDI routing within Sonar. For one thing, just because a MIDI track's input shows that it is set to some source doesn't actually mean that it is. What I found is that you have to cycle the input selection to some other input and then back to the input you want it to be on. Only then will it more or less do what you want.
 
I say "more or less" because you will find that as you navigate through different tracks while Sonar is playing back, it will randomly stop routing MIDI even for tracks that have specific inputs selected (and have Echo=ON). In addition, as you navigate through the tracks, you will often briefly hear MIDI events bleeding into unrelated tracks.
 
X3d is a big step forward in fixing MIDI routing, where in previous versions some of the above was impossible to do at all, but there are still some bugs that need to be sorted out.
 
My suggestion to you is to cycle the MIDI tracks' inputs and see if it helps.

SilkTone
X3d is a big step forward in fixing MIDI routing, where in previous versions some of the above was impossible to do at all, but there are still some bugs that need to be sorted out.

I don't have anything documented nor have I seen any issues since X3D, if there are still outstanding bugs please create a thread (don't want to hijack this thread) with specific steps to reproduce and we can attempt to reproduce it.

CakeAlexS

SilkTone
X3d is a big step forward in fixing MIDI routing, where in previous versions some of the above was impossible to do at all, but there are still some bugs that need to be sorted out.

I don't have anything documented nor have I seen any issues since X3D, if there are still outstanding bugs please create a thread (don't want to hijack this thread) with specific steps to reproduce and we can attempt to reproduce it.

Alex, I did create a thread (which was mostly ignored), here. I run into these issues daily so I believe them to be real bugs related to MIDI routing.

Thanks that went under the radar. I'll post there.

guys thanks for the replies... i'll report back on the issues and solutions as mentioned a little later as i'm not at my desk now.
 
@SilkTone - thanks for your steps, i'll try to reproduce them with the instruments i have. for what i know Kontakt 5 is working well with regard to Midi out but not for the Korg Legacy Systems. However, i have not tried the cycling thru of the Midi channels. - will report back here and also your other thread.
 
@CakeAlexS - thanks also, if you could perhaps may try to reproduce this along with the steps @SilkTone mentioned. 

1) The FX Chain issue I suggest posting on a new thread to keep things clear, maybe even a screenshot. Then rename this thread and edit it out of your first post. Otherwise we will all get confused.
 
2) Please check post #11 from http://forum.cakewalk.com/Still-some-issues-with-MIDI-crosstalk-but-now-there-is-an-easy-workaround-m2954622.aspx#2954622 . It looks like the same issue? If not please copy/paste his steps and alter it so it's like your steps. Please be as specific with the steps as possible. I only have Komplete BTW.

Hi Alex, thanks again for your reply.
 
sounds good. i'll make the necessary edits. however, i will not be able to post the PC FX Chain issue with screenshot at the moment. i'll do it later in the day as a new topic.
 
cheers!!!

SilkTone
 
My suggestion to you is to cycle the MIDI tracks' inputs and see if it helps.

Hi @SilkTone, i have tried this suggestion. Unfortunately it is still not working for me. 
 
i guess the work around, at this point in time, is to use a dummy track on Kontakt to send the midi information to any other track(s) i need.
 
many thanks again...Cheers!!!