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!

> always, if people are experiencing problems the best bet is to start a new thread and list as many details as possible.
 
This is just to gauge the outstanding issues right now for the next few days, I would hope people to start their own threads as well and link to this (in fact that's what I've already been asking), or better still link to thread where a discussion has already started.
 
Cheers..
 
Alex
 

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

Step sequencing still an issue it seems (CWBRN-20128):
http://forum.cakewalk.com...iably-m2903727-p2.aspx

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?

Thanks!

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.

Trenillo
This is a issue that I have addressed since Sonar 4, and it's still not taken care of. Why doesn't Sonar have a true Write Animation button in X3. The so called Write button it has is really a Touch record, and not a true anitmation over write. This becomes a big problem when your working with a bunch of tracks and you perform the Write function on a few tracks. If you won't to record over the animation you have to physically touch the fader with you mouse, or delete the nodes, because there's no true animation over write function. And once you release the mouse from the fader the old animation information kicks in. This is so fustrating!!!! Protools have always had a Over Write,  Touch, and a Read. Is this something to hard for you guys over at Cakewalk? This should have been taken care of since Sonar 3,4,5,6,7,8 and even up to the X. What the heck Cakewalk! I love your product and the dream of what it might can do, but this need to be taken care of like yesterday.

I'm not sure what your issue is, Sonar has overwrite, touch and latch?
http://www.cakewalk.com/Documentation/default.aspx?Doc=SONAR%20X2&Lang=EN&Req=Automation.04.html
 
If you wish to debate this I suggest a new thread... thanks... 

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.

Demo coming soon as you know Steven :) I'm looking for reproducible X3D please....thanks.