I wasn't having Crashes related to memory leaking in Melodyne, my problem, that was being responded to in that email was Melodyne/Antares/Gtr rig/ Waves timcode/tempo based plugins not Fastbouncing as of X1d specially due to Cakewalk coding changes. Started emailing about this issue in March, Not due to melodyne memory crashes. "You aren't getting these crashes from what I gather" Again, why would a Cakewalk representative tell me to 'Stay tuned, because it looks like an update is in the works' IF he knew this was NOT my problem in Melodyne, but IN FACT a Cakewalk MISTAKE (called X1d) that affected multiple plugins across multiple plugin vendors. Fastbouncing/Clip Bouncing Worked in X1c fine with melodyne/antares/waves (aside from lacking VST3 sidechaining) I had been told by Phone Support as well that I Wasn't the only one experiencing the Fastbouncing/Clip bouncing issues and that an update to address the issue was in the works. I like the email where I'm told to stay with 8.5 in the meantime. Regarding same issue [In speaking with my manager, we are investigating another issue (possible bug perhaps) regarding very similar circumstances with another customer, so it looks like you may not be alone. I appreciate your patience and as soon as we come across some type of working solution I'd be more than happy to let you know. In the meantime, I would suggest staying with 8.5 for this specifically.] This WAS/STILL IS a Cakewalk issue in X1D. This should have been a quick fix!!! In regards to the channels to complain about customer support, I've written in in the past, In fact, you Personally wrote me back this September 5, 2011: I'm sorry to hear that you've been having a poor experience with our support team. I located your call record and it does look like you've been a long time supporter and have called about a variety of things (some of them simple and installation related, and some of them being faults in the application that you needed help with). It's hard for me to get the whole picture by just glances at the notes in the follow up emails that were sent to you unfortunately. If a customer does report an issue that is an error in the application, our support staff is not supposed to "re-direct" the customer towards filling out the problem report form. I will personally let a customer know about this form in case they run into such issues in the future, but I personally always follow up internally with our testers and developers. The rest of our staff should be doing the same. I will say, however, that the benefit to you as the customer filling out this form is that you will get notifications as to its status if things are updated and resolved. I agree with you when you say that our support staff show "own" at this, and I'm not sure who mistakenly said that we do not follow up internally regarding customer concerns. I will make a point to follow up with our team and your personal concerns in regards to our escalation process internally. For what it is worth, we are in the process of migrating systems internally that will make it easier for all of our support representatives to escalate issues they cannot resolve. I know this doesn't say much for the experience you have had up until this point, but moving forward our support team has a much better path for comparing and merging cases with the data coming in from our problem reporter and testers. In regards to standing issues in X1c, customer support has no control over resolving errors in the application. We can report the issues and express our concerns over the severity of them and how they are effecting our customers, but ultimately resolution to the problems lie outside our support staff's ability to control. I apologize if you are still experience problems of this nature. If you would like to let me know what bugs you are being affected by I will be more than happy to check the status of such issues. In regards to a support representative hanging up, do you recall who you were speaking with and what day/time the call took place? I can pull the call up if you have a rough estimate of the time. Best regards, Ryan Munnis Product Support Manager Cakewalk, Inc.

Swiller


Back to topic...

Another one for the petition, please fix, driving me insane. Back to reaper for me I think in the mean time, despite me warming to x2 .

Maschine rocks mahoosive style. The wise money is on the old kit. 159 for mikro is an absolute steal, with massive and 1.8 included. It is as important as the 909, 303 IMHO. A true modern classic. 

As a customer that has spent nigh on a grand on cakewalk products in 12 months I have a very basic question...

Is a fix coming, and if so when? No timeline means there won't be a fix to me. So at least have the decency to let us know so us die hard machinists can choose between x2 and something else. I think that is very reasonable.

This is an annoying issue for sure, but I certainly would not use this as a reason not to pick Sonar... there are two simple workarounds
 
a) use a count in of zero ( i dont like this, but some are fine with it)
b) use a count in but use a midi metronome instead of audio metronome 
  i. in preferences>midi>devices; enable your sound card midi synth (or microsoft gs wavetable synth)..count from top to determine port number
  ii. in preferences>project>metronome; select midi metronome, set port # to that above, and in the case of the gs synth try notes E6 for down beat and F6 for others
 
hope that helps

soundsubs


Maschine is getting to be unusable for me with X2 sp1.
Every time I instantiate Maschine or add it to a project its locking up when opening it or trying to save.
It wasnt this bad in X1.

Can anyone report similar findings with Maschine and X2?

nope, for me it opens fine... i instantiate with all audio outs, and midi in..
 
as a thought, if you are running win7/64 make sure you are launching 64bit vst

I have Machine 1.8 and Sonar X1 Producer expanded and over the week end I was experiencing the very samee issues as everyone else here. 
 
So please add my name to the list of intrested users wanting a fix or at least looking forward to a fix.
 
As fas as customer support goes, well cake you have always been good to me. Now that is not to say we did not always get it fixed, but, were you there for me when I called or emailed??? yes....email is a little slow, and you can only expect customer service during normal business hours.....
 
But nothing in life is perfect..............and I feel at least you guys sincerly try to help so thank you ......look at how fast you got that Rapture installation issue with DimPro resolved.....Perfect for everyone?.....No......But you at least jumped on it and did it.........so good job...
 
Would I like to see other things fixed? yep....but let's just work on one at a time......so please, let's get Machine working with sonar!
 
Clifford

yorolpal


As I stated in a previous thread my issue with X2/X1 and Maschine is similar but not the same.  My problem is that on certain (I can't ascertain why only certain ones and not others do this) "scenes" and/or "patterns" the first play through is fine but when it loops anything on the first beat doesn't sound.  As this is happening in a major project I simply reverted to dragging and dropping as audio into Sonar as a workaround.  Of course, for the time being, this just renders me a stereo track.  I'd like to have multitrack audio ported out to Sonar.  I just got groove3's Maschine tutorials and, hopefully, that will show me how to better workaround this weird anomaly.  I'm also on Maschine 1.8 64bit.

I saw that post.. if there is any value in a second look pm me and i will give you my email addr... see if its the same here..

Will do.

yorolpal


As I stated in a previous thread my issue with X2/X1 and Maschine is similar but not the same.  My problem is that on certain (I can't ascertain why only certain ones and not others do this) "scenes" and/or "patterns" the first play through is fine but when it loops anything on the first beat doesn't sound.  As this is happening in a major project I simply reverted to dragging and dropping as audio into Sonar as a workaround.  Of course, for the time being, this just renders me a stereo track.  I'd like to have multitrack audio ported out to Sonar.  I just got groove3's Maschine tutorials and, hopefully, that will show me how to better workaround this weird anomaly.  I'm also on Maschine 1.8 64bit.

This sounds extremely similar to another issue with lower MIDI Playback Buffers. Give this a try:  Go to Preferences > MIDI > Playback and Recording.  Under "Playback," make sure you have "Prepare Using 500 Millisecond Buffers.  With some systems/instruments, the lower default value of 250 results in dropped notes.  The only drawback to increasing this is an additional quarter-second when you hit the play button before the transport starts rolling.  Please let us know if this improves things for you.  Thanks.

bigboi


any word on when an update may come out Bill? we getting close?

Honestly,  I can't share planned dates without getting fired :).  But I can say that we're currently working on a patch for all flavors of X2.  There's quite a bit we're trying to tackle, in addition to the count-in offset that's been discussed here.  So we'll need some time address as much as we can and to make sure it's thoroughly tested and solid.  We sincerely appreciate your patience.  It won't be too long.

forgot about that adjustment. I have had mine set at 350 and found that solved the problem on my system.

Thanks Bill....I will try it ASAP.  My studio is currently being rewired, so I am down for around 2 weeks.  Killing me....but adding the Switchcraft 9625 is going to really uncomplicate my life I think. 

WHen I am back up, I will check it out.  Hopefully, you guys are still working on the patching it or fixing it with the next update.

Thanks for staying on top of it for us.

Frank

not sure what issue the workaround is supposed to address, but I just tried it and it does not resolve the count-in delay.

Sorry.  I should have been clear.  The work-around I posted should resolve the count-in issue.  In my tests, it resolves the problem.  If you have Maschine listed in both "Cakewalk VST" and "Cakewalk VST X64" be sure to set numInputs for both.  Also, for good measure, change "maxUsedInputs" (which is found in the same list) to a value of 2.

Regarding the missing first note issue:  Not everyone's experiencing this.  I'm confident that it can be fixed by tweaking the MIDI buffer size to a larger value, as I suggested earlier.

Wow.......it aaaaaaaalmost works! Changing maxUsedInputs was necessary to see the change on my system. So far I am seeing no visual delay from Maschines sequencer and audio stops as it should HOWEVER the first beat will not play. I can see it being triggered/lit up as soon as I hit R, but there is no audio from it after the count-in. This is still a definite improvement, but not 100% yet. Am about to open up a fresh session and report back. Thanks Bill - huge help!

I'm still stuck with the first beat not playing.  Dern.

Are their any negative side effects to setting the max inputs to 2?  What is this setting used  for anyhow?