jono grant

Yes, but when I analyze more than one at a time, it's all glitchy. I have to do them separate. Perhaps I need an update or something?

Hi, if I try to select multiple tracks to go into Melodyne, they seem to be glitched. If I have Melodyne analyze each one separately, they work fine.

Is it not able to analyze more than one at a time?

Thanks

Jono

On 2/2/2022 at 9:45 PM, bitflipper said:

What John was suggesting was creating a new project with NO plugins. If that closes properly - as it probably will - start adding in plugins to determine which one is causing the hang. Disabling a plugin does not unload it.

 

Thanks, yes, for sure. I'm noticing it has something to do with releasing the RAM that is loaded up. I see it still loaded in task manager after I quit a session. The RAM amount then decreases and when it's at zero I can open Cakewalk again.   

1 hour ago, John Vere said:

So to test open a project with out those plug ins and see if it closes properly. It’s always a process of elimination to troubleshoot “what or why” 

Its not Cakewalk itself, it’s almost always a plug in. 

The thing I'm noticing in task manager, is I close CW, and in task manager, it shows the amount of ram CW is using. That number goes down to zero. That's when I can re open a file. So the ram remains loaded after closing. hmmmmm

It even happens when I disable all plugins, save and then close.

I wonder if there's a way to find out what plugin is causing it?  Some kind of crash lof or something. Don't know much about that.

Thanks

JG

Hey, pretty much 100% of the time, when I close Cakewalk, it doesn't quite release the driver or something and is still open in device manager. I have to "end task" most times to open a new file.

Why is that? I do have a fair amount of UAD plugins going in most sessions, but close down should just close down I would think.

Anyone know about this?

Cheers

On 12/16/2021 at 8:29 PM, Base 57 said:

Try increasing the size of the midi buffer in Preferences. 

Thanks, ya, I had tried that and any other thing that was suggested to me in other posts, didn't make a difference.

I never had the problem with my MOTU cards, perhaps it's UAD related.

Just wondered if anyone had any insight as to why midi would perform poorly with the higher soundcard buffer size?

Does anyone know about this? Thanks

J

Hey there, I'm using 2 x UAD Apollos and an octo pcie card with cakewalk.

When I have a huge file with lots of plugins, I need to change the buffers in the UAD settings to 2048. However at this rate, the midi has unexpected errors. Missing notes mostly.

Midi seems to perform best at low buffer sizes like 128 or 256 but poorly at higher ones like 2048.

How am I supposed to deal with this??

Why does midi perform poorly at 2048 buffer size in the sound card settings??

Frustrating to say the least.

Thanks

I have a cakewalk file that had a track that I used to create a tempo map. I didn't use audio snap, I just dragged the clip onto the ruler/timeline and it created a tempo map.

I go to save it as a bundle because I want to send it to someone and it won't include the track that I used to create the tempo map. It gives me some dialog box saying it won't include audio snap files (not an audio snap file) and when I reopen the bundle, that track is replaced with audio from another track! WT actual F? I even bounce that track down first, I even mixed it out as a wave file and brought it back in. This makes zero sense. 

So many weird bugs are surfacing in these new updates. 

Any help appreciated!

If you import a video to cakewalk timeline and select "import as mono tracks" it does not do that.

Just brings in an interleaved file.

Always worked, now it's broken.

FYI

I'm using a Soundiron piano in kontakt and in cakewalk.

The sample is only about 340 megs. When I play, I can have many notes or big chords no problem but if I use a lot of sustain pedal, it's causing clicks and pops in the audio! I can hear it when I use the sustain pedal, clicking as I do it.

Anyone have a similar issue or know what could cause it? I've tried various buffer sizes on the sound card but it's the same.

Thanks

On 10/31/2021 at 11:00 PM, John Vere said:

If you do. Do you still get stuck notes? 

I'm on a laptop now with only kontakt running. No stuck notes! The piano pedal causes clicks in the audio though! Can't win...

I can just use Kontakt in standalone and use the midi keyboard to change midi channels I guess...

Thanks

On 10/29/2021 at 10:40 PM, John Vere said:

Stuck notes are normally caused by the hardware not transmitting the note off message. This can be the controller, the cable, the interface and lastly the software. 
In the old days this was often called a midi log jam because too much data was jamming up in the buffer. 
Which is one thing you can try increasing the midi buffer s 

Thanks. I'm trying all different buffer numbers in both places in preferences. Nothing seems to make a difference. Lower or higher. Anything else that could cause this? 

Hi, I have a live situation where I need to toggle between two tracks in cakewalk, so I can activate different synths that correspond to those tracks.

I use my arrow keys for this normally

During the live gig, I won't be able to reach my laptop keys very easily. 

Is there some other way I could trigger toggling through tracks in cakewalk? With a pedal or midi note or something?

Thanks

Anyone know about this? thx

I'm setting up keyboard sounds for a live show and using cakewalk to house the synths.

Is there anyone who knows how to eliminate stuck midi notes??? I can deal with it in a recording situation (even though that sucks) but live? It's gonna be ridiculous getting stuck notes during a performance. Nothing else going on in the file, no plugins or wave files etc. Just a few synths.

Anyone know why it happens/ solution?

Thanks

Jono

Don't love the new export window.. slower

What I mean is that when you expand a manufacturers plug list, it gets all melted in with the other manufacturer entries. Here's a picture (below)

*Shown here, the Antares menu is expanded, but the plug list look like they're part of the continued list on the right. They used to have graphic separators for each plug. It looks like a graphics glitch in the update is what I mean. It's confusing. 

Is no one seeing this?

Thanks

After recent cakewalk update, when I go to insert a plugin, the list is all weird looking, the menus aren't defined and it was redesigned poorly. Is this being corrected on a new update perhaps?

Annoying change...

Never mind, thanks... I found the auto scroll button down at the bottom right side. Cheers

J

Melodyne seems to have stopped scrolling in Cakewalk. Usually, if nothing is selected in the melodyne window, it scrolls with the time line. Not anymore.

Anyone else with this issue? 

Thanks

On 6/21/2021 at 9:19 AM, Tommy Byrnes said:

I've found the best way to deal with UAD plugin problems like this, and many other VST problems as well, is to make sure I only have one VST2 folder location, which for me is Cakewalk\VST Plugins. Have the VSTScan only scan that one folder. I've always used that location, no matter the DAW just because I've been doing it since the early Sonar days. VST3 defaults to its normal place (C:\Program Files\Common Files\VST3). I copy (don't cut) the dll for the plugin I own from the main UAD Powered Plugins folder and paste them into a new UAD Plugins folder in my main VST2 folder and there they stay, unaffected, unless I buy an update for one of them or there are fixes to specific plugins. This way the VST folder and their contents aren't changed and there aren't all the UAD plugins to scan, just the ones you own.

Just don't scan the normal UAD folder and you're good. Keep the UAD Powered Plugins folder intact because Console uses that location to load the plugins.  I hope this helps.

(edited for a stupid spelling error)

Sorry, I'm a little confused here. Is it something like this: Perhaps if I create a special folder for UAD plugs in my cakewalk vst folder, I can just copy the plugins I want/own from the current vst folder (x86/steinberg/powered plugins) and only have cakewalk scan that folder. Then run the newer update, copy anything I want from it to that cakewalk vst folder I made and never scan the steinberg folder where it gets installed. Then it will utilize any new console updates but cakewalk only sees the plugs in the cake vst folder? Something like that? Just wondering if the update/firmware itself might not allow me to run the older plugins. hmmmm Maybe i'm way off here... thanks! 

49 minutes ago, Tom B said:

Yes, version UAD 9.12.2 has the older Neve 33609 version. Our registry data should be the same for UAD 9.12.2 (except, maybe path names).  

The latest UAD version is 9.14.5.  I decided to update to that version about a week ago, and now have the updated Neve 33609C.  Interestingly, my Cakewalk test project was able to automatically find the 33609C. There are a few differences in registry data for UAD 9.14.5:  The dll  is now "UAD Neve 33609 C.dll",  the DosName is different, the uniqueId (i.e. plugin ID) is the same,

My test project uses  Cakewalk 2021.04 (perhaps it started one rev earlier). I'm guessing your projects started out with earlier Cakewalk versions. 

Note:  I haven't activated the 33609 plugin because it's only being used to understand this issue.  However, I don't think that matters.  For those not familiar with UAD,  the installation includes all the VSTs  whether activated or not.  I think this is done to make it easier demo and/or purchase the plugin.  An inactive plugin can be inserted, but it isn't functional.

Thanks! I'll do some more digging!

Cheers