SilkTone

Ryan Munnis [Cakewalk]

I'm not sure where you're drawing your conclusions from. Didn't I just list three significant fixes? There were a few fixes in X3c and now some more in X3d. I just dug up the internal report on the third bug fix that I mentioned above. These are the exact details from the report:
 
------
Based on this video:
http://www.youtube.com/watch?v=73Pf1b6bTk8&feature=c4-overview&list=UUu9stuavxCp5UtC7c4fmfWg

Thread also realted:
http://forum.cakewalk.com/enable-midi-out-soft-synth-confusion-now-with-video-comparison-to-studio-one_-m2807089.aspx

 
I'm making conclusions based on the fact that CWBRN-22142 is not mentioned as being fixed in the release notes, the fact that Foster Mansfield confirmed that what looks su****iously like the same bug has not been fixed, and the fact that I didn't see anything in the release notes that seems to imply that it has been fixed.
 
I would really like to test X3d myself and see once and for all if it has been fixed, but I really don't want to pay for yet another update and then find out it hasn't been fixed.
 
Ryan, so how about this... Since you are sure X3d fixed the MIDI crosstalk issue, if I pay for the X3d upgrade but the issue still reproduces, can I get a refund? It seems fair to me.
 
EDIT: LOL, apparently s u s p i c i o u s l y is a bad word.

I'm assuming CWBRN-22142 was left open because it's not fully resolved in that scenario. Keep in mind we still have some stuff open with high priorities for fixing next.


Anyhow, the set up in that report is a MIDI track receiving MIDI from a VSTi Out and another MIDI track recording input from a hardware MIDI device. If you have the hardware MIDI input set to Omni, the confidence preview recording clip indicates that there will be MIDI recorded from Catanya's VSTi MIDI Out. When you stop recording, however, it only records the MIDI that came in from the keyboard. So the preview misleads you from what eventually gets written to the track.
 
Maybe you can help me narrow down the scope of this report? Here's what we have currently:
 
--- Details from CWBRN-22142--- 

 Summary: MIDI crosstalk when a VSTi has "Enable MIDI Output" turned on 

 Description: 
    * Insert any VSTi that can send MIDI events out, like Catanya

    * Ensure "Enable MIDI Output" is turned on for the plugin

    * Ensure the plugin has MIDI content it will play back

    * Set up a completely unrelated track to record from an external MIDI keyboard

    * Record MIDI from the keyboard


 Expected Results: MIDI events from the VSTi should not bleed into the track that is recording the external MIDI keyboard. 

 Actual Results: The VSTi MIDI events are incorrectly being recorded on the keyboard track.

Note that this is NOT the same as the so-called crosstalk bug that was fixed when recording from multiple MIDI keyboards.

For this issue, note that choosing a specific MIDI channel on the keyboard track (as opposed to OMNI), will make the problem less severe, however the VSTi events will still interfere with the keyboard events by causing stuck/hung/missing notes if they happen to occur at the same time.

While the X3b/c release notes claim this issue has been fixed, there have been confirmations that this issue has NOT been fixed.

This same issue was reported almost 5 years ago as CWBRN-1336, however Ryan Munnis has recently erroneously closed that report as fixed while the problem still persists. So this report is to track when this issue *really* gets fixed.

This MIDI crosstalk bug and crashing bug with multiple VSTi plugins sending MIDI events out have been preventing me from using Sonar for a few years now, and I'd like to know when these issues are *actually* fixed. Therefore I will really appreciate it this time around if no-one closes this report as fixed when it really hasn't been fixed. IOW, please understand the actual problem before closing as fixed. Thanks!
------

Ryan, as you say I think I should create a new thread for this specific issue. I will do so and provide some more detailed info there.

I hope for SilkTone sanity this gets resolved.
Glad you still want to stick it out.
 

I just did a test with 3 instances of Reaktor (Spiral, Nod-e, Automata) each outputting midi on a different channel. Each was routed to a VSTi for output.  I recorded the 3 output VSTis for 10 minutes (got around 12,000 notes) and each midi track recorded only contained notes from the correct midi channel.  It seems like the cross talk issue is fixed.  I'll do some more testing when I have time.
Jim
 
 

Shawke
I just did a test with 3 instances of Reaktor (Spiral, Nod-e, Automata) each outputting midi on a different channel. Each was routed to a VSTi for output.  I recorded the 3 output VSTis for 10 minutes (got around 12,000 notes) and each midi track recorded only contained notes from the correct midi channel.  It seems like the cross talk issue is fixed.  I'll do some more testing when I have time.
Jim

Sounds promising. Keeping fingers crossed. Thanks for checking these out. I also added some steps that can be used to verify whether it has been fixed here.
 
EDIT: What happens when you select the VST port - OMNI for each MIDI track input? The way you have it configured, you will only get cut off notes, not bleed into other channels. You might not be able to notice the cut off notes unless you specifically look for them.
 
EDIT EDIT: With your original configuration, can you also add a MIDI track and configure it to record from an external keyboard? Try to play some of the same notes as what the VSTis are sending out and hold them for a bar of two. Are the MIDI notes being recorded from the external keyboard being cut off?

Silk Tone,
I followed your suggestion and changed the inputs to omni, and recorded.  Everything worked correctly.  I added a 4th VSTi with an external keyboard input set to omni (the external keyboard is transmitting on a different midi channel), and recorded all 4, no problems again.  I realize I haven't followed your steps to reproduce the problem exactly, at least these basic scenarios work.
Jim
 

Com'on this thread here please for the MIDI issue, this is just a general X3D bugs summary thread :) Cheers

 
(Hate doing large letters, hate it )... 

Any more issues found with X3D other than MIDI please summarise here and create a new thread to discuss if you have to (assuming this thread hasn't been killed off already)...

Okay, Alex, have a look at "ProChannel fx chain label text is out of alignment after X3d update".

Something that may be helpful to you (and us) in this venture is to edit the OP to highlight things as they are called/confirmed. This way we can all refer to the same post more quickly. Bullet list preferred.