jeff s

Thank you Jonesey! Since I don't use Loops, Stem separation, audio stretching, BL Studio etc. a subscription would only bring back POW-r and Plugin Oversampling & my custom workspace layout (no biggie) to my workflow. I plan to jump on the $49 for the first year special to try it out but to say I'm skeptical is an understatement.

I could never figure out how this works... I assumed you could cue up multiple tasks to be exported and the launch them all at once and return later when it completed. If so, that would be very helpful and time saving.

Ok - that's good that they didn't remove the PCs. Since my custom workspace didn't migrate, I wasn't seeing the PCs where I left them Is there a list of what things from CbB are now only in the subscription version? I see all the added content that the subscription offers (loops, instruments, track manager etc) but I mainly use it as a tape recorder and only do minimal MIDI stuff as I record live bands for the most part. I do use POW-r dither all the time for my exports, so I'm wondering what else I might be missing from my usual workflow. thanks jeff

Long time Cakewalk user back to the Pro Audio days... I downloaded the free SONAR to give it a spin. I see now that POW-r dithering is only available at the subscription level and it looks like all the ProChannel modules are removed and my custom workspace didn't get migrated.... Is there a list that spells out what been removed from CbB in the free SONAR by chance? I have no problem paying for continued updates/support - I can't even remember how many times I bought this software over the years. I always stayed up to date. Any info would be appreciated. thanks jeff

Thanks for the replies I upgraded to Melodyne 5 Studio last June 2021 (not Editor as I previously stated) and this " error" *just* started showing up recently. Since that upgrade, I have added a few new plug-ins which is why I suspected a potential conflict. I may try to reinstall Melodyne and see if that helps. Currently, I do what Treesha said ("close it and move on") but it's kinda of unprofessional when a client is sitting next to you during a session using Melodyne and keeps seeing the error. As John mentioned, I do use short clips and render afterwards most of the time but this "error" occurs when I insert it on a clip and after I render it, so it's 2x per use. So you can imaging how many times it can occur during a vocal tuning session... I opened a service ticket with Celemony and will follow up if we make any progress... here's their initial reply: Dear Jeff, This is Rob at the Celemony Technical Support for Melodyne. Thanks for reaching out! when I insert Melodyne on a region Do you use Melodyne as an ARA or as a Transfer plug-in? Cakewalk error "Cannot find or open file". Yes, this is a Cakewalk Error message, not from Melodyne. Have you heard of this or have any suggestions on how I can fix this? We have never heard about such an issue, so we can't say anything yet. As our regular tests with CbB also do not show such issues, it would be helpful to send us one session in question so that we can investigate on the session itself. It would help us to nail down your issue better if you could send the files via Dropbox, Wetransfer or Google Drive and send the link where we can download the files as a reply to this e-mail. Please remember that for a requested session all files incl. audio files of the project are needed. Best, Rob -- Robert Schröder Celemony Technical Support

I started getting the error message when using Melodyne. It always appears when making a new region with Melodyne. When I click OK, the error message goes away and the files are present and work as usual. It also started popping up when opening a project that has Melodyne employed but not rendered. It's more of an annoyance than anything. I'm suspecting that another plug-in might be conflicting with it but that's just a guess. I have the latest CbB version and use Melodyne 5 Editor .......Any thoughts would be appreciated.

Thank you for the reply. I will give that a try. I recall having an issue when I upgraded my DAW hardware and did a rebuild for Win10x64. I had a heck of a time getting my second controller (Tranzport - USB) to work properly with my Mackie Controllers (via RME midi ports) - I think I understand what you are saying: Delete RME midi ports add new midi interface (MOTU Fastlane) reinstall RME ports for controllers I'm not familiar with the azlow driver but I have seen that mentioned in other threads when I have been researching my issue. I will look into that also. I'm sure there is a way to have them all working, I just need to get the right method of installation sequence (?). I am surprised that it's that finicky .... Thank you again!

I've recently decided to get back into recording MIDI tracks and incorporating some drum machines and vintage synths. Over the years, I have mostly used SONAR (and CW ProAudio) as a tape machine as I tend to record full bands ensemble in the live room - that's more my thing as I came from the pre-digital/MIDI world. My last significant MIDI experiences were back when everything was trying to sound like Miami Vice and very machine-like.... but I digress. I am currently still running Platinum on a Win10x64 PC (but I continue to install the latest version of CW by BL, but I'm just more comfortable in Platinum) . This is a commercial studio so change is slow or avoided when things just work as is. I use RME HDSP 9652 as my interface and am utilizing the 2 MIDI ports to control my 2 (original) Mackie Control surfaces along with a Frontier Tranzport (USB). It's been bullet proof :) So now I try to add an external MIDI interface (MOTU USB Fastlane or an Arturia USB interface via DrumBrute) and when I attempt to use them, they work but disable my control surfaces. I really need to use the control surfaces... any thoughts or suggestions on where to start trouble shooting? I'm sure they can both co-exist but darned if I know ;) Thanks! jeff