Ok, I've clearly clicked the wrong option for the Meoldyne install, and it's reinstallled it.
 
But, now it wants me to re-register and prompts me for my serial number.
 
The serial no for Melodyne is not in my Cakewalk account. Any ideas what to do?
 
Thanks!

Bristol_Jonesey
Ok, I've clearly clicked the wrong option for the Meoldyne install, and it's reinstallled it.
 
But, now it wants me to re-register and prompts me for my serial number.
 
The serial no for Melodyne is not in my Cakewalk account. Any ideas what to do?
 
Thanks!

Start a new thread :) Ta...

Ryan Munnis [Cakewalk]

SilkTone
Noel can you clarify whether the MIDI output crosstalk into other tracks bug has been fixed? You mentioned in another thread that it was fixed but we are now seeing reports that it still reproduces in X3d.

Hi SilkTone,

The two items in this topic that I'm aware of getting resolved with X3d are the following:
 
- Resolved a crash when using two instances of Catanya sending VSTi MIDI Out to SONAR (CWBRN-22141)
- Resolved an issue where moving clips on a Simple Instrument Track would reassign the tracks MIDI input from a VSTi MIDI Output ports to all hardware MIDI ports
 
The second one on that list was actually pretty bad, since it gave the impression there was crosstalk since inputs were getting remapped behind the scenes when moving clips around.
 
The other note I'm seeing (not sure this is clearly identified in our update notes) is the fix Noel is referring to, which was a fix for the video SwampTooth uploaded, discussed in this thread: http://forum.cakewalk.com/enable-midi-out-soft-synth-confusion-now-with-video-comparison-to-studio-one_-m2807089.aspx
 
I do see a report still open in regards to potential stuck notes with MIDI VSTi Outs.
 
As always, if people are experiencing problems the best bet is to start a new thread and list as many details as possible. Master threads like this are very difficult for us to keep up with.

What I'm referring to is this comment from Noel after I mentioned the crosstalk issue:
 

Noel Borthwick [Cakewalk]

SilkTone
The short version is that if you rely on VSTi plugins that send MIDI events out, you will get crosstalk into other tracks when you record on them (say from an external MIDI controller). In addition, if you have more than 1 VSTi sending MIDI events out, Sonar will crash. There are no workarounds for these two issues. I absolutely rely on more than one VSTi sending MIDI events out, and since Sonar can't handle this I'm forced to use another DAW that can.

The crash and "crosstalk" have both been addressed in X3D along with other issues related to MIDI out VST's.
We can't guarantee that every, MIDI out issue you ran into was resolved, since that is a mile long thread and the description covers many issues. In the future if you report issues please log a single problem per bug report. It makes tracking them infinitely easier, unambiguous and minimizes the chance of the report being misinterpreted. It also greatly improves the chance of the issue being addressed in a more timely fashion, leading to less frustration for all concerned.

 
So I guess at this point it is safe to say this crosstalk bug is still not fixed. At no time while I was mentioning this bug was clips ever mentioned, so I'm not sure how the two issues can get mixed up. I thought my description of this issue was pretty easy to understand.
 
For instance check out this 4 year old thread where I describe this very same problem in great detail with clear steps to repro it in two different ways, using nothing but CW products. I'm at a loss for how more clearly I could have described this issue. That doesn't even mention the other threads and multiple problem reports filed for this issue.
 
Some guidance from you or someone else at CW for what I'm doing wrong in getting this bug to CW's attention might help me to become more effective.
 
After all that it seems CW still doesn't even understand this bug at all. Ryan, I'm asking a serious question here: How can I help CW understand this bug so that it can be addressed?

SilkTone

Ryan Munnis [Cakewalk]

SilkTone
Noel can you clarify whether the MIDI output crosstalk into other tracks bug has been fixed? You mentioned in another thread that it was fixed but we are now seeing reports that it still reproduces in X3d.

Hi SilkTone,

The two items in this topic that I'm aware of getting resolved with X3d are the following:
 
- Resolved a crash when using two instances of Catanya sending VSTi MIDI Out to SONAR (CWBRN-22141)
- Resolved an issue where moving clips on a Simple Instrument Track would reassign the tracks MIDI input from a VSTi MIDI Output ports to all hardware MIDI ports
 
The second one on that list was actually pretty bad, since it gave the impression there was crosstalk since inputs were getting remapped behind the scenes when moving clips around.
 
The other note I'm seeing (not sure this is clearly identified in our update notes) is the fix Noel is referring to, which was a fix for the video SwampTooth uploaded, discussed in this thread: http://forum.cakewalk.com/enable-midi-out-soft-synth-confusion-now-with-video-comparison-to-studio-one_-m2807089.aspx
 
I do see a report still open in regards to potential stuck notes with MIDI VSTi Outs.
 
As always, if people are experiencing problems the best bet is to start a new thread and list as many details as possible. Master threads like this are very difficult for us to keep up with.

What I'm referring to is this comment from Noel after I mentioned the crosstalk issue:
 

Noel Borthwick [Cakewalk]

SilkTone
The short version is that if you rely on VSTi plugins that send MIDI events out, you will get crosstalk into other tracks when you record on them (say from an external MIDI controller). In addition, if you have more than 1 VSTi sending MIDI events out, Sonar will crash. There are no workarounds for these two issues. I absolutely rely on more than one VSTi sending MIDI events out, and since Sonar can't handle this I'm forced to use another DAW that can.

The crash and "crosstalk" have both been addressed in X3D along with other issues related to MIDI out VST's.
We can't guarantee that every, MIDI out issue you ran into was resolved, since that is a mile long thread and the description covers many issues. In the future if you report issues please log a single problem per bug report. It makes tracking them infinitely easier, unambiguous and minimizes the chance of the report being misinterpreted. It also greatly improves the chance of the issue being addressed in a more timely fashion, leading to less frustration for all concerned.

 
So I guess at this point it is safe to say this crosstalk bug is still not fixed. At no time while I was mentioning this bug was clips ever mentioned, so I'm not sure how the two issues can get mixed up. I thought my description of this issue was pretty easy to understand.
 
For instance check out this 4 year old thread where I describe this very same problem in great detail with clear steps to repro it in two different ways, using nothing but CW products. I'm at a loss for how more clearly I could have described this issue. That doesn't even mention the other threads and multiple problem reports filed for this issue.
 
Some guidance from you or someone else at CW for what I'm doing wrong in getting this bug to CW's attention might help me to become more effective.
 
After all that it seems CW still doesn't even understand this bug at all. Ryan, I'm asking a serious question here: How can I help CW understand this bug so that it can be addressed?

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

Steps:
1) Create a project with 2 instances of Rapture to receive MIDI
2) Insert Reaktor (or another synth that can generate / send Midi out per channel) and enable MIDI Out. Inside reaktor set up to LFO's to send out on different channels
3) Route each instance of Rapture to it's own channel from the Reaktor LFO's
4) Turn On Input Echo and Record for Both Rapture tracks
5) Hit record

Expected Results: The Midi generated from Reaktor is sent separately to each instance of Rapture

Actual Results: The same midi data is recorded on both
------
 
As I mentioned previously, I'm still seeing a case regarding potential stuck notes with VSTi MIDI Outs. It seems to be like the above fixes suggest a lot of progress has been made.
 
Edit: I also see that case your own case CWBRN-22142 is open as well.

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.

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!
------

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

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?

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 )... 

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

Looks like the MIDI bug is definitely fixed - strike it off.

NEW - Pro channel text out of alignment
http://forum.cakewalk.com/ProChannel-fx-chain-label-text-is-out-of-alignment-after-X3d-update-m2951887.aspx
 

CakeAlexS

JCody
The Playlist bugs I reported 2 updates ago have still not been addressed. It's basically unusable in a live situation. I still have to use X2.

Specifics or references please.

That's kinda of weird... just the other day I made a playlist of about 30 midi's and played them through my keyboard (just because I wanted to see if it would). It worked quite well.

Oh... here is that playlist thread :) Cheers JCody:
 
PLAYLIST ISSUE DISCUSSION HERE ->

http://forum.cakewalk.com/Playlist-still-broken-m2923421.aspx#2952064
 

Here's a daft and unimportant one -
 
If you have  the Console Emulator on a track, it has no needles showing before you turn it on.  They appear when you turn it on, and stay there when you turn it off again.
 
This doesn't happen with busses.
 
I guess that some routine that paints the needle isn't being called until the CE is turned on.
 
It doesn't matter in the slightest, but just thought I'd point it out.