jono grant

Anyone have any idea why midi notes might start dropping out at higher buffer sizes (2048)?

Thanks

Jono

Hi, I use UAD hardware, a pretty extensive system, I'm constantly going back and forth altering buffers to deal with tracking latency and buffers to deal with mixing and plugins. Very frustrating to begin with, but now another issue. If I have a file with a good deal of tracks and plugins, I usually need to crank the UAD buffers to 2048, so it can handle the plugins and playback smoothly. Problem is, it seems I get dropped midi notes in the higher buffer settings (AAAAAAAAUGH!) How can it be this difficult to get a DAW to play files properly?

Anyhow, is there a setting that might help the midi not drop out at this buffer size? I would think it would be easier to deal with the midi just like it is for the audio, to be using higher buffers.

Thanks

13 hours ago, msmcleod said:

We fixed an issue a while back for some plugins that were registering multiple changes in parameters either due to automation resetting when going back to zero, or on zero all controllers... but not all plugins were playing ball with this, and still register multiple changes.

My recommendation is to set the number of changes to zero, and rely on the timer instead.

Could you elaborate on what you're doing when it crashes?  We did go through a bunch of operations and postpone auto-save if it tried to do it mid-operation. Maybe one or two have been missed.

It's random, I could be altering an envelope or even just moving a clip, if it happens right when the autosave happens it can crash. Again, I go look at the time of the last autosave when it happens and it's always right when the crash was. 

59 minutes ago, jackson white said:

@jono grant   Maybe try setting it to zero and see if that changes the observed behavior. 

fwiw, my 'best practice' is a well conditioned "ctrl+s" reflex and a permanent position in the custom control module. 🙂

 

As do I save all the time but I also make 100 changes per minute and I hate losing stuff. Often it's a performance of some kind. 

I've been using Cakewalk since I had windows 98, perhaps even 95... there are issues that don't ever get fixed, it puzzles me.  

The one thing I mention above about crashes occurring at an auto-save point is an issue as well. I think it just tries to autosave at the exact same time as you make a move and it blows up...lol

Anyhow, thanks

I think my main point here is that; even with autosave set to 10 minutes/10 changes, it's autosaving each time I stop playback...like, all the time!

What is causing that??

Thanks

J

1 hour ago, jackson white said:

Preferences > File > Advanced > "Auto save every" ?

Mine is set at 0. 

Wouldn't that turn the feature off? Auto save has saved my butt so many times...I can't imagine not having it enabled.  

Is that what you meant?

Thanks

I find many files that get to a point where they have a lot going on, are auto-saving constantly, sometimes after every time I hit stop! I have the preference set to autosave every 10 minutes or 10 changes. I think I've been told in the past that recorded midi tracks that have automation etc. may be calculated as "changes" when mod wheels etc. get moved or other parameters get automated, very annoying. I don't make any change at all and it auto saves. 

I've also found that almost any time a crash happens, it's right when an autosave happens... not a coincidence I don't think, it's gets messed up because it tries to auto-save while I'm making some other change and can't handle it.

Anyone know how to make auto-save behave better? 

Thanks

J

17 minutes ago, msmcleod said:

I've not seen this, however I pretty much always apply my region fx immediately after editing.

If you have an "open" Melodyne region fx in your project and save your project, then upgrade Melodyne before you next open it, there's always a risk that Celemony have changed the file format making your region fx invalid. 

Could this be what's happened here?

Not sure.. I apply region effects immediately as well. This message just comes up after you add a melodyne region effect and it detects the pitches and you open the editor for the first time on a clip. J

Since installing the latest Cakewalk update, one thing I'm noticing is, when opening a melodyne region effect, a message pops up saying "cannot find or open file". Nothing else is wrong and I just dismiss the message but it happens every time, it's a bit annoying. It didn't do this prior to the update. 

Anyone else seeing this?

Cheers

Jono

On 12/22/2020 at 9:41 AM, Billy86 said:

Curious to know if this solved it?

Since the update I haven't noticed it hang. I haven't had too many projects open yet but so far so good!

J

1 hour ago, Gswitz said:

Look in the event viewer. You should be able to see the events recorded.

Just checked. They all say "note" E5 and F5. They have different channels, 3 for the E notes and channel 4 for the F notes.

Hi there, I have a cakewalk file that is all of a sudden recording phantom midi notes when I try to record a track. 

I don't even have to touch my keyboard, I just hit the record button and there are 16th notes recording a constant pattern.  What could be doing that?

Any help appreciated!

J

Thanks for all this info everyone! I see a new update sitting there, I'll try it out.

Cheers

J

Does anyone have the problem: Cakewalk sticks around in Task Manager after closing? 

Any reason this would happen? (quite often)

Thanks

JG

22 hours ago, William W. Saunders, Jr. said:

There's been a lot of that going around, but there is an update due in Washington next month which may get rid of some of it.  Probably not all.

I have a massive list of weird goings on lately...

I wish they would fix things rather than keep changing things...

Final update:

I deleted one track at a time and found the one track causing all the grief. I saved the track's effect bin as a preset, exported the audio dry and then created a new track with the audio and efx bin.  Everything works fine now.

There was nothing I could see causing the corruption. It was a track that I hadn't even been working on.  

Thanks

Jono

Update: saved file as a bundle, reopened, it says there's a corrupt audio region and it will be padded with silence, file opens, same issue though.

So a corrupt region on a track somewhere.

I reopened file and deleted all the tracks, add a new track and it works fine. So I guess I have to delete tracks one by one until I find the culprit! Oi

4 hours ago, twelvetone said:

Are the outputs selected in the properties page?

Not sure what you mean selected. The output says "master" on the track and in the properties section but it won't let me open the output to change it or do anything.

J

1 minute ago, John Vere said:

To me that sounds impossible.  I think you need  Cakewalk support on this one. This sounds like corruption. 

Indeed. I wonder if I can use mix recall somehow to rebuild the file in a new session?

Frustrating! 

16 hours ago, John Vere said:

What happens if you insert a new bus, Can you change the track output to that?

I tried this but it simply will not let me even open a track output!

I've never seen this in decades of using cakewalk

Hey there, I have an almost finished Cakewalk session that is all of a sudden being all crazy!

When I open it, it displays a huge list of all the tracks and says they're all set to silent hardware busses. Everything is playing and I can change inputs and bus outputs, but it will not allow me to change any track outputs! They are all set to master and play fine.

What the heck is going on? I need to change some outputs on some tracks but now I can't.

If I've ever seen a message like this in the past, I just change the master output or something simple to get it all working again.

I've never had track outputs become locked.

Please help!

Thanks

45 minutes ago, Lord Tim said:

Yeah, it's time consuming but getting the transients right first is crucial to getting good results and it does mean a bit of manual grunt work moving or deleting markers.

That said, though, if you're just playing it back while the markers are active, you'll be hearing the lower quality online stretching algorithms. If you bounce all of those tracks to clips, it locks everything and uses the better quality offline algorithms. You might find your results sound a lot better, even with rogue markers.

Cool, thanks!

JG

Hey there,

Audio snap is truly fantastic! I had a question though.

I enabled it across a drum multi-track, It does a great job especially when rendered using the Advanced Radius algorithm.

My question is, is will occasionally create a transient during a long cymbal decay or something, and you get a really odd glitch. 

Is there a way to prevent that or do you just have to go through each transient marker and disable the bad ones?

Thanks

Jono

16 hours ago, msmcleod said:

%APPDATA%\Cakewalk\Cakewalk Core
 

Thanks, I was searching but it wasn't coming up. Went manually and found it. Appreciate the help!

J

I can't seem to locate the TTSseq.ini file.

I need to change it so my keyboard local control doesn't keep changing.

Where might it be?

I searched all cakewalk folders and also just updated.

??

Thanks

Jono