gmp

I'm still getting this bug in the Export window. When I open it  it defaults to my custom Eternal Encoder preset named "Wav+MP3" Which creates both a wav and mp3 in the export. Many times all I want is an mp3 so I change it to my custom "Mp3" preset. Half the time it creates both the wav and mp3 instead of only the mp3

28 minutes ago, Craig Reeves said:

I do want to be clear I still think Cakewalk is awesome and I love it. Trust me, I have FAR more scathing things to say on the Ableton forum, and they never listen to me...

Hang in there, Craig, you're in great hands in this forum. Someone will get to the bottom of this. I've been using the various incarnations of Cakewalk since 1992 an CbB is clearly the best one ever. I've had a lot of issues though the decades and some have nothing to do with CbB but other things in your computer setup.

And of course I've run across legitimate bugs, but all were fixed. Even after you get a stable system, make sure you make backups or learn how to use the rollback feature, where you can rollback to the previous version if you get a showstopper bug.

46 minutes ago, Noel Borthwick said:

It has always worked that way. Older versions didn't ever warn about the mp3 for external encoders. External encoders are as the name implies "external" so Cakewalk doesn't do any special handling.

I just used launchpad to open 2021.08  I selected some audio, chose Export, entered the song name, chose my External Encoder preset named "WAV+MP3" and exported the files.

 I then opened Export again, entered the same name in the box and right below the box, the song name. mp3 and song name.wav popped up, letting me know I already had those files and I'd be overwriting them.

 I chose "export" and got an overwrite message about the wav file and after that I got a separate overwrite message about the mp3. So the old Export window was clearly better at safeguarding us from overwriting files.

 I tend to add a number after the song name like "song name 1", "song name 2", etc. So sometimes it's hard to remember the number at the end, especially  if it's a different day, so these are very helpful reminders, so we don't accidentally overwrite files

19 minutes ago, Keni said:

Thanks Mark...

Too bad. That's a tender spot there I will have to remember to triple think before committing.

 

 I do realize why though.

 

In this case, it was actually convenient saving me from needing to give permission for both. 🙏

 

I see you have a slightly different situation. Whenever I create an mp3  and wav I move the mp3 to my internet computer mp3 folder for sending to clients. This still doesn't explain why I don't get that overwrite message when exporting only an mp3

45 minutes ago, msmcleod said:

@Keni / @gmp  -  The export dialog checks for duplicate filenames at the time you add the task.  After that, there are no more checks.

The task queue is designed to be run without any user intervention/interruption, so files will be overwritten if they already exist.

In my case I'm not using "tasks", I'm using an External Encoder. And for wav files I always get the "replace file" message, but I never get that message for mp3's. If this is the way it was intended, then it should be reconsidered, since the old export window did not do this and was better in this respect.

2 hours ago, Keni said:

I experienced something like this too.

I ran my two tasks (see previous post), I then realized an error I made and went back and re-ran the tasks recently updated.

 

Both files were over-written with no warning

This is good news for me, since you weren't using an External Encoder, which I'm sure few use. So hopefully this will be fixed since the same thing is happening when using "tasks"

Export using External Encoder still doesn't ask if you'd like to overwrite an  mp3 file.

I have my External Encoder set up to save the wav file used to create an mp3. So if I choose my Preset named wav+mp3, Both a wav and mp3 are created in the same process,

If I use my preset: wav+mp3, to create a wav and mp3 and then repeat the process. I will get a message box asking if I'd like to replace the wav file, but not a message asking to if I'd like to replace the mp3. 

 If I choose my custom External Encoder "Mp3", it also doesn't ask if I'd like to replace the file with the same name

The export window sometimes gets confused also. Sometimes if I choose my custom mp3 preset, it will create and save the wav file also

4 hours ago, Milton Sica said:

Friends, I still have audio dropouts. It had achieved success only by closing the project and reopening it. Now I can only recover audio playback if I close the daw and reopen it again.

Any tips for me to be able to do this recovery?

There are so many crazy unpredictable things that can happen with computers and a complex program like CbB. This is why I'd suggest to everyone to have a disaster recovery plan. Of course this isn't a disaster, but it's frustrating and you wonder where the problem is. You can spend a long time troubleshooting. 

The easier path is to make a clone of your boot drive when everything is working ok and put that in when things are perplexing and first see if things are ok then.

Another great thing with CbB is the rollback feature where you can rollback to a previous version and see if that fixes it. I save all the install versions of CbB in case I need to go that route. I also have scook Launchpad that enables you to save the Cakewalk Core folder which is only about 200-300 meg and go back to a previous version using that.

Since the problem could be an auto Win Update. The safest thing to do is to disable Win Updates and to enable Win Updates when you go to a new CbB version. After it's installed and all the Win Updates are up to date. Save that as an image file using the free Macrium or Acronis. 

The image is exactly like a clone of your boot drive. If you go this route you should try and keep your C drive lean - only OS and programs, no samples or data. Use other HD's for that. My C drive is about 67 gigs and the compressed  images are about 33 gigs

When things go haywire and they always do eventually, I first try a previous CbB, if that doesn't work then I'll make an image of my current C drive and revert to an earlier image when everything was working to try to determine if my OS got corrupted or what.

Troubleshooting is far easier if you have these tools - good luck.

Yes it has to be in a separate folder. Search some of my recent posts where I describe the whole process and give you some code and also a quick way of getting the lame files on my OneDrive

1 hour ago, Keni said:

I think what he's referring to is that it has the tag in the field requiring the pasting/typing the name if you wish to add/modify the name as in adding a number to the export name.

If it placed the actual name that the tag refers to only a quick edit of the number is needed.

 

I would love it that way as well.

Currently my system requires clicking the 3 dotd, navigating to the location/previous mix. Selecting this, then entering the filename box to edit the name... over and over all day...

Yes Keni, that's exactly what we'd both like

3 hours ago, msmcleod said:

FYI - {projectname} is the CWP name,  {notesname} is the song name from the notes tab.

yes, I'm aware of that - thanks for all your help and advice

55 minutes ago, msmcleod said:

You do know you can create  your own presets?  These can be in the form of:
1. Your own filename presets
2. Your own complete Mix presets, including a default filename

I suggest making sure you put the client name / song name in the notes tab for your project, and setting your default filename to:

{notesartist} {notesname}


 

I checked it out. Pretty amazing stuff. If I were to try this I'd need to open the browser, select notes and  add into the notes - artist and  name (songname).  I already have the artist name and songname in my CWP. 

So in my case it's easier to not have to type that again and just open export and paste my cwp name in there. All I have to do it delete the number at the end of the cwp and then type in a few letters or numbers. 

For them to change it so where my CWP name is in the box instead of {projectname) may foul up the current tasks, not sure. The simpler solution is when I open the Export window that the focus is on my filename, so I can easily edit it, instead of having to click in that box and then hit Paste. 

Ideally I'd prefer when I open the Export that my CWP name is already in there, not {projectname) , so I don't even have to hit Paste.

46 minutes ago, Max Arwood said:

Usually I save as Project-02 then when I export I get Project-02.wav The next time ia save as 03 and export - I get Project-03.wav. I think the Mp3 would have the same name too. Not sure about this that. I'm not sure but you might try {projectname}+02_data??? There might be secret "{???}"'s we don't know about either.  Don't know if it would work or not.  I usually put this " I usually add some of my own personal code to tell me what kind of mix it is." in the file name - Just started this practice this year, not in every file name, but just the ones that have major changes in them. When I export the info it in the .wav Hope this helps. Let us know about whether you and }+ in that data entry box/

 

I tried adding MAST at the end of the y {projectname} and it works fine for wav files, yet I got an error for the mp3. It didn't create the mp3. It's  because I’m using the External Encoder. It works fine for the regular CbB mp3

7 hours ago, Max Arwood said:

I think the new export dialogue uses the file name automatically if you leave {projectname} in the text box. No need to copy paste. 

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

27 minutes ago, Noel Borthwick said:

Next update will have a registry setting to make it auto fade out. 

That's a good solution for me

2 hours ago, Kevin Perry said:

Or like some.applications have a tickbox to say "Open export locatiom on completion".  No need for toast at all then.

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.

21 hours ago, gmp said:

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

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

16 minutes ago, Noel Borthwick said:

I'm thinking of adding a parallel export to wav for other encoders

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

39 minutes ago, Kevin Perry said:

Why not use the new features of the exporter in CbB to create multiple.files as a job?

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