Jerry Freese

I found that the automation checkbox was unchecked. That was the cause. I have "mixed down" several clips that way and they came out acceptable only because I try to keep my raw tracks as consistent as possible. When I heard that slider movement wasn't affecting anything I started investigating and found that slider positions were being ignored, and had me initially confused as why and wondered how long my default mixdown parameters were that way..  Actually the answer was right there in the manual, it just took me a bit to digest it and the terminology. I realize I could have just checked the box and tried again but I was away from home and figuring things out "on paper" instead of just trying things helps me understand the big picture and flow of software. Thank You!

Thank you for confirming, I'll bet I didn't check the box because I wasn't using automation (or so I thought) I'll find out when I get home. As I wrote, I didn't think at first I needed that check box to mix down a static slider position.

19 minutes ago, Noel Borthwick said:

No its not recorded as automation but the static gainstages are treated in the same way that automation is. i,e. there is no option to export without automation envelopes but with the static track gain. So if you uncheck the track automation checkbox then the track will be exported at unity gain and no pan.  

Sorry if its confusing. Perhaps the text for those checkboxes need to be reworded somehow.

So that being said would you confirm that if I didn't have the automation checkbox checked, that would cause the fader position to be ignored?

So now I wonder is slider position recorded as automation by default even if I did not specifically record slider automation? If so, that's why my sliders were likely ignored, as without automation box checked, the initial settings were ignored and thus defaulted to raw tracks.

7 minutes ago, Noel Borthwick said:

I think the text is a bit redundant. Its referring specifically to clip gain envelopes being ignored. Clip fades will still get rendered.

Thanks for clearing that up. I assumed that but "trim setting" could mean gain (like a trim control) or a trimmed clip. 

19 minutes ago, scook said:

When everything is going through the master bus, there should be no difference between exporting the "Master Bus" and "Entire Mix" 

And if the "Mix Enables" on the export dialog are all selected (except for mutually exclusive options Fast/Audible Bounce and 64bit Engine) the levels should not need to be adjusted any differently than playing the project.

Ultimately I am trying to figure out why the three guitar tracks that had the slider all the way down (with no sends) Still were in the exported mix. It seems the slider positions were ignored. Could it be the automation checkboxes weren't checked or does that not matter if there is no automation? As I said, if I select "what you hear" it exports the mix as I expected.   I saw this:

Track Automation. If you don’t check this option, any volume and pan automation, including initial volume and pan settings, is ignored when creating the new file(s). The amplitude of the raw data in the tracks is used, and the pan is C, or centered.

Clip Automation. If you don’t check this option, any clip automation, including any trim settings, is ignored when creating the new file(s).

I'm guessing I don't have those boxes checked. I'll check the project when I get home.  Wondering, what does it mean here by "trim settings"? Trimmed clips or gain type trimming/other?

I didn't think I had to have track automation checkbox checked as I didn't knowingly record any automation on the sliders. But if slider position is part of automation data it makes sense that the positions were ignored.

21 minutes ago, scook said:

One cause of unexpected levels on export is not using a master bus.

Make sure all the audio ultimately goes through one bus.

 

AFAIK, all the project templates provided in CbB have a master bus set up.

 

If you start projects without using one of the supplied templates create a master bus before adding any tracks to the project.

This is done by adding a bus, right-clicking on the bus header and selecting "Set as Default Bus"

The same may be done to existing project.

Then select all the audio and instrument tracks, hold down the CTRL key and select the master bus in a the track output. This will set all the tracks to the master. If track outputs are set to a bus, leave them. The bus will get routed in the next step.

Route any other bus outputs to the master bus.

Yes I have a master bus.

No, I'm not home right now. For years I have been exporting like this right to a wav or MP3 without issues. I'm guessing I have some settings wrong that make it ignore slider positions now. I'm going to look at the preset"what you hear" and see what is different than my export settings now.

OK so I am doing this:

Go to File > Export > Audio.

Select the location where you would like this file to save.

Add a file name, and choose a file type from the menu below.

Make sure the source category is set to Entire Mix, or you can choose any of a host of parameters to reflect your needs.

Click Export, and check the selected location for your final product when exporting is complete.

The guitars were louder than my mix, so to test I exported the same song again but with all the guitar sliders pulled all the way down. The export still had the guitars in there at the same volume!  From what I have read, I may need to make sure track,clip and Master automation is checked? I'm not sure if it is (not home now) but I may not have checked those as there is no automation in the track unless the slider position automatically stores as automation. I guessed that "entire mix" would mean my mix not just tracks ignoring slider positions.

When I went to the export module and selected the preset "what you hear" the sliders  when pulled down worked as expected. Is this a typical way people would mix down their track?

Being a Cake user since before V4, I never looked into the workspaces and don't understand their value. Guess I'll have to read up on them and see if I'm missing something I could use.

8 hours ago, Nigel Mackay said:

It is the Workspace you are using that has disabled it. Here it is set to Instrument and Bus. Change yours  to None and everything will be enabled.

 

THANK YOU!!!!! This was driving me nuts!!!

I haven't used piano roll since I switched to cake walk by bandlab about a year ago. When I double clicked on a midi clip it didn't pop up then I noticed it wasn't an option in the views menu, like it was wiped off the program Alt 3 doesn't work either, it's just gone. Nowhere in the program or menus reads piano roll anywhere. What happened????

Ahh a hidden folder.... It didn't read that in the instructions...  I was wondering about that but figured it would say.  Thank you very much.

So where is the  %APPDATA%\Cakewalk\Cakewalk Core folder?   I don't see any folder that root is %APPDATA%

Thank you!

When a project opens there is a toast message that gives some inspirational message like "this one's gonna be a hit" etc. I read once how to change them, but i just spent 10 min searching and searching the forum using every set of words I could think of describing what I was looking for to no avil.  Can anybody tell me the procedure or where to look?

I didn't recall seeing it in the latest update, but after it the last update,mine works perfect!

15 minutes ago, RBH said:

I'm running Win 7,   Latest release of CbB (2019-build 54).  { Melodyne (4.2.4.001 ) Studio version } and  I'm not noticing this issue. Maybe studio and essentials are operating a little differently? Just thought I'd try to add a bit to this.  I know that in the Studio version - I have to select the "blobs" in the track view properties of Melodyne when instantiating multiple tracks. I'm not too familiar with essentials version differences though.

Running Melodyne assistant here and not noticing anything bad PRE  hotfix install.

Hooray! After the latest update Heal works fine now!! ( I must have missed it or the documentation didn't say anything about this fix but I don't care because it works now!!!!)

I've tried the buffer & different drivers. To me it must be in the program itself. I have used Sonar since V4 and every rendition to platinum and never had this issue. I was using my old  platinum two weeks ago perfectly fine and the next day downloaded bandlab and instantly saw the difference in the cursor. Nothing changed on my system that was working perfectly except I downloaded cake by bandlab.  That's the only thing that has changed on my system to go from stable cursor to "double vision" like shaky. No I do not have the pause key pressed . That makes it SUPER jerky and laggy. There is no reason to believe there is anything wrong or set up wrong with my hardware. Something changed between the two programs.

2 minutes ago, David Baay said:

That would be audio bit 'depth' as opposed to data bus 'width'. I don't know for sure whether CA-2A was included in the IP package that Bandlab bought; maybe Steve does. But it doesn't appear Cakewalk are putting any energy into plugin development right now, and the return on investment of updating CA-2A to use a 64-bit signal path would likely not be very attractive.

Understood. Is there an advantage to have a 64 bit plug if it can only communicate 32?  I just wonder why Cakewalk did this.

And if anyone can get two tics with this please let me know.

1 hour ago, David Baay said:

CA-2A will using 64-bit addressing and data bus, but apparently it does not support 64-bit audio processing.

SO when the manual refers to  "plug-ins that can send and receive 64-bit data display double lines"   is that referring to the addressing and data buss or the 64 bit processing?

1 hour ago, David Baay said:

You'd have to ask the developers why not.

Cakewalk has new owners now so is it possible to contact the developers of the CA-2A?

25 minutes ago, scook said:

They have and the CA-2A is not the only example. All the "half-rack" series originally bundled with Project 5 and included with several versions of SONAR are 64bit plug-ins with 32bit data paths. Alternately, several releases of SONAR included a third party plug VC-64, a 32bit plug-in with a 64bit data path. When introduced in SONAR 5, both 32bit and 64bit versions of SONAR supported the 64bit DPE option.

 

I noticed the VC-64 has two tics as well but didn't realize it was 32 bit. I figured that's what the 64 meant! I do understand the difference between bitrate data path (tics) and the rate of the plugin are two different things.

1 hour ago, David Baay said:

You're confusing x64 memory addressing and data buses with 64-bit audio processing. If you're running x64 Cakewalk on an x64 operating system, the matching version of CA-2A will using 64-bit addressing and data bus, but apparently it does not support 64-bit audio processing. Some other high-end plugins don't either. You'd have to ask the developers why not.

Thanks, As I have said I'm just wondering if anyone has got the plug to work with two tics because I could not and I wanted to see if anybody else was able to. If anyone could,I'd know something of mine is set up wrong. If nobody else could either,I'd feel pretty safe knowing that's just the way it is.