gmp

I name my projects like this: client name song name 1 So instead of {projectname} in that box where you can't make any changes to the name. It would be better to have it place my project name in the box where I could make little changes to it. For instance I always delete the number after the project name, which could be 1 or higher numbers. Since I always add a higher number when I make changes to a project, so I can revert back to an earlier version easily. In addition to deleting the number after the project name I usually add some of my own personal code to tell me what kind of mix it is. So it seems it would be an easy fix to put the real project name without the cwp in that box instead of the {projectname} which can't be edited. Also I do many times make a wav and mp3 at the same time using the External Encoder for a custom mp3 with variable bit rate.

I'm not sure if anyone has addressed this yet, but every time before I hit the Export window, I choose "Save as" and copy the song name. I then open Export and immediately hit Control-V to paste the song name and of course nothing happens. But in the old Export window when you open the window, the focus is on the file name, so when you hit "Paste" the name goes in the box. It sure would be nice if when you open the Export window that the focus is on the file name, so we can quickly paste the name in the box

That's a good solution for me

That sounds like a good solution. I thought at first it would be best to have the check box under notifications in Preferences, but your idea is better. Most of the time I don't want it to open, but on occasion I would. I think adding that box near the Export button would be convenient,

It was released on 10/5. Personally I'm going to wait until the smoke clears, and I hear what others think about it.

You can do this if you configure it in the External Encoder. Once you do that your 320 mp3 shows up in the Export list. I have mine setup to default to VBR4, which is a variable bit rate. It processes at 320, yet in areas that 320 is of no benefit, it reduces the bit rate lower. This way your ending file is smaller.

I did some more testing and found that if you choose the regular mp3 as the export and you have the same name it does ask you if you'd lek to overwrite it. But if I choose to export only my custom External Encoder mp3 and not the mp3+wav files, it doesn't ask me if I'd like to overwrite the file, it just overwrites it. So this seems to only affect mp3's and not wavs when using the External Encoder

The External Encoder is now fixed, but when I run my custom External Encoder Preset called "Mp3+wav", it does created both files. Yet if the file name is exactly the same as one previously used, I do get a message about whether to replace the wav file with the same name with the new wav file. Yet that doesn't happen with the Mp3, it simply replaces the older mp3 with the new one. With the old export window it asked if I wanted to replace for both wav and MP3. I'm using build 145

External encoder works great with the mp3+wav files - thanks

In the export window it would be nice to have a check box for "save wav file" for anyone saving to mp3 or other format, since the wav file in most cases is created first and then deleted after creating the mp3

Before you choose to Export, select all the tracks and make sure the selection starts at 15 sec or so, instead of at 0 sec

I saw that. So with this I could create a wav file and mp3 at the same time? Have you tried this feature?

Glad to hear it's on the fix list - thanks msmcleod. What I really like about using the External Encoder is I can create an mp3 and a wav file at the same time. Just go to Utilities/ External Encoder Configuration utility and put these values in the boxes. MP3 VBR4 + Wav - file name Extension - mp3 keep source file - checked PATH: C:\Program Files\Cakewalk\Shared Utilities COMMAND LINE: lame -V4 --vbr-new -m j %I %O You do need to put 3 Lame files to the 64 bit folder C:\Program Files\Cakewalk\Shared Utilities. The 3 files in the Shared Folder are lame.css lame.exe lame.dll If anyone ever needs these I can put them in my MS Onedrive for anyone to retrieve. About 15 years ago when I set this up, I visited this specialized mp3 forum, where these gurus who were on the cutting edge of mp3 improvements. They gave me the Command Line. I found that the VBR 4 was a good compromise between quality and size and was better than even the 192. With variable bit rate the encoder will examine the file and determine which parts need the 320 and which parts are fine with 128 or less. Once you do all this when you export you'll see your file name you used in the Encoder Configuration in the drop down list. I have 2 configs - mp3 only and mp3 + wav file

I've been using the External Encoder in Sonar and CbB for about 15 years. Worked perfect every time, except with the new version of CbB 2021.09 I haven't gotten any response in the 2021.09 Feedback post, so I wanted to know if anyone else uses it. I've been creating VBR 4 mp3's which is the variable rate encoding and produces a very high quality mp3. But actually the most important use of the external Encoder is that I can create a wav file and then right away it creates an mp3 - all in one process. Quite a convenience and time saver. I hope they can fix the bug in 2021.09, but in the mean time, I'd appreciate anyone who's uses that External Encoder to at least chime in and let me know if you're having problems too

I tried the command line with quotes and it still didn't work. What do you mean by Spaces in your filename. The output mp3 file created does always have spaces and that's never been a problem. For an experiment I tried a simple output mp3 file name with no spaces and got the same error message. Keep in mind I've been using the same mp3 External Encoder presets for about 15 years with perfect results until this new 2021.09 version.

Thanks, I also prefer it in the FX bin so I can see it easier. I never like leaving the Inspector open, I like seeing as much Track Pane and Clips Pane as I can even with a big monitor. I'll go back to using CA2A

It appears both were patterned off the same analog compressor. If anyone has an opinion on which one is better as far as it's strength as a compressor, please chime in I like having the CA2A in the FX bin of my vocal tracks. For me it's easier than having it in Inspector/Pro Channel.

The External Encoder configuration utility is not working right in 2021.09 new export window. I have the External Encoder setup to create an mp3 or an mp3 and also a wav file at the same time. The mp3 is a variable rate mp3 called VBR 4. In the Export window under Format/File Type I can see my custom choices - VBR 4 and also VBR 4 + Wav. Sometimes I can get the VBR 4 to export correctly, other times I get an error message: Warning the External Encoder returned an error code and the file may have encoded properly With this error no file is created. If I choose VBR 4 + Wav under format/file, no wav file is created, once an mp3 did get created, other times I got the error code. Here are the settings for creating an mp3 and a wav file at the same time. I put this in the External Encoder configuration utility window MP3 VBR4 + Wav - file name Extension - mp3 keep source file - checked PATH: C:\Program Files (x86)\Cakewalk\Shared Utilities COMMAND LINE: lame -V4 --vbr-new -m j %I %O I also copied the 3 Lame files to the 64 bit folder C:\Program Files\Cakewalk\Shared Utilities and used that as the Path. That didn't work either. The 3 files in the Shared Folder are lame.css lame.exe lame.dll All this has worked for about 10-15 years just fine

Through this process I found another nice feature. Once you set a track's height, you can simply double click the waveform icon in the Track pane for that track and it will maximize the track, but when you double click on it again it returns to the exact size you left it. This doesn't require you to check"Lock Height"

More handy tricks - thanks. For us long time users, many times we can miss little improvements with the newer releases and get locked into our old way of doing things. It's nice to find new better ways to do things

The controls are exactly the same in the compressors CA2A and PC2A. In fact, even the graphics are almost exact. Is there really a difference in quality and sound? Curious to know other's opinions

Here's my post from the other thread I think this will solve my problem. I went ahead and changed my template so that Lock Height is already selected on tracks I want it. You can still change the height of a track and then that's the new locked height. When you lock the height of a track, its height does not change when you use a Zoom or Fit command and those are the commands that was affecting my work flow.

I think this will solve my problem. I went ahead and changed my template so that Lock Height is already selected on tracks I want it. You can still change the height of a track and then that's the new locked height. When you lock the height of a track, its height does not change when you use a Zoom or Fit command and those are the commands that was affecting my work flow. Thanks for the help,

Very good suggestion. I'll check this out. I'm not sure if screensets and workspace will even be needed, if I do this for the main vocal track.

So then if I so all this and want to maximize a vocal track and zoom in to delete a noise. Do I have to turn off "Lock track height"? And then turn it back on? Does "Lock track height" affect all my tracks with the same height?