sean72

I might be missing something but I don't see anything there. Saving the audio export settings as a Cakewalk preset is done in the window before the MP3 render setting window appears, so you can't integrate the MP3 render settings to a saved preset that way.

Looks like that's already been done. Thanks!

Thanks I will try that. EDIT: I didn't have to try that, I shut Cake walk down and reopened it after I had right clicked on all of the audio clips and gone into Associated audio files and recomputed pictures. All of the graphics that had not loaded the first time I did that loaded up on relaunch..

My audio device lost sync and Cakewalk hanged amd computer had to be rebooted. When Cakewalk was relaunched all recorded wav data from the last session (about 4 tracks worth) show just a flat line in the audio track where the wavform graphic should be. Even though I had saved prior to the crash and Cakewalk should have saved a record of those tracks waveform data but apparently it did not. All other tracks in the project recorded prior to the last session still have their waveform data showing. The tracks that do not have any audio waveform graphic still contain audio though. I tried right clicking Associated audio files recompute pictures but that only seems to be working on a couple of the tracks other ones are still showing a flat line even after I do recompute pictures multiple times on them.

Is there any way I can stop Cakewalk from defaulting to 256kbps and making me change the settings every time I export to an MP3?

Thanks, hopefully CbB will give us the option to link the two functions together, so I won't have to click input echo every time I arm or disarm a track.

??

Doh! I figured out what the problem was, nullsoft (Winamp) output setting was not set to my audio interfaces main outputs. If anybody else out there is ever having the same problem open Winamp go to preferences scroll down under plugins and select output then select nullsoft wave output dll and click configure, then select your audio interface main outputs from the device drop down menu click okay and you're done. For some reason Windows was not automatically selecting that as the primary audio device even though it's the only one installed on my machine.

Yeah the master is set at 0.0 . So that's not the issue. When brought the wave file that I exported from Cakewalk back into Cakewalk the levels on that were exactly what I was hearing at mixdown in the main project, but when I play it back in something like Winamp the levels are way lower. Other audio files don't have this issue in Winamp and I suspect the file won't play nice with other playback solutions, YouTube uploader, etc. It's like Sonar exported files that only it can read properly. Weird...

Cakewalk is reducing the volume of my mixes on export. It's not at the same level I hear in Cakewalk. What do I need to set to export with the same volume levels that I'm getting in the master output bus inside cakewalk? The audio interface master volume is set at max. I've never had a problem like this before whenever I exported anything from sonar it was always the same level as what I was hearing inside the DAW mix. Files are probably around 50% volume after export. Audio interface is Presonus Q2626 and it has no mixing software to set up so it should not be lowering the volume in any way since the main out is all the way up. I also tried exporting as a wave and reimporting and slapping a limiter on there and cranking it up and the results were the same volume level is a lot lower on the file that is exported.

Yeah I haven't been able to get it working either. If it's not a feature yet hopefully it could be added to a future version of CbB. When I do a lot of recording guitar clips and jump around multiple tracks sometimes I forget to turn input echo on or off before or after recording. Would be much easier to manage if the record arm/disarm also enabled or disabled the input echo. Thanks for trying it!

The new implementation is actually much faster. Here is what you might have missed as I did at first.. Make sure you have the "Smart Tool" selected from the tool menu. Press "T" to open tools menu if it's not already visible on the control bar at the top of the screen.. The smart tool is the one all the way to the left in the tools menu. I'm not sure if the use of this tool is 100% necessary but that's how I got it to work. Then hover the pointer over the audio clip you want to boost or cut the gain on, While hovering, hold down CTRL then Left-Click-Hold and Drag. You will see the clip gain line appear and move in real time as you move the mouse up or down. You should also see the clip amplitude graphic getting larger or smaller as you drag it up or down. Not only is this much faster to adjust clip volume but the scaling of the amplitude graphic makes it much easier to match clip levels visually.

Thank you! As 57Gregy also asked, is there a way to set the save location of the backup versions? It would be safer to save across two drives in case of drive failure.

I don't meam autosave, I mean being able to save a copy whenever I manually save a project. I don't want to be interrupted by autosaves but I would like it to save a backup every time I choose to save the main project. If possible.

For the dialogue under clips, Fade Clips where you input a fade in and out time in milliseconds is there a way to set Cakewalk to automatically do that every time you record a new clip?

This page doesn't offer the solution: https://www.cakewalk.com/Documentation?product=Cakewalk&language=4&help=Recording.21.html There is a global setting to disable input monitoring during playback but it does not turn the input echo on when I arm a track to record. What I'm trying to do is simply have a track automatically turn input echo on when I arm it to record and when it is not armed for record I want input echo to be off. Is this possible? Thank you

Thanks!

It used to be so easy, right click a clip, add envelope, select gain or pan, done. That option is gone, no more right click on a clip to add an envelope (Why Spongebob, Why??) I tried clicking a clip then pressing T to bring up the tools menu, then selected clip envelope>gain, but it's drawing the gain envelope line across all individual clips in the track. Basically like a track envelope instead of a clip envelope . Also when I click to raise or lower the envelope it draws from the click point to create a peak or valley (adds an envelope control point) rather than raising or lowering the entire level of the clip linearly like it used to. Is there an easy way to add a linear gain envelope to a single clip?

"Well, when you do things in non-standard ways it should not come as a surprise to you when you get non-standard results." It wasn't non-standard when I started making music. I'd like to thank everyone for their help, I inserted SD3 as a soft synth and the problem went away. Nonetheless, it only glitched on one of two identical projects so it's still a hit or miss thing. Thank you!

Hey, thanks for the link. As for the stabbing around in the dark comment, I've been using Sonar since around version 5 so I am hardly a novice. I've also been using Toontrack drums since the original Drumkit From Hell nearly 20 years ago. My problems have not been with basic functionality they have been with errors like a crashed audio engine and now this, where I have two identical projects where one works properly and one doesn't. I know SD3 is an instrument but you can load it and others like EW Orchestra, Omnisphere or whatever by inserting them as a soft synth into the FX bin of an audio track. You can also point as many MIDI tracks to that soft synth instance as you like. Doing it that way or inserting on the synth rack are basically two methods of accomplishing the same thing. Both are just routing MIDI data to the plug-in to fetch audio samples and play them back. There are many different ways to accomplish the same things in Sonar/Cakewalk. Sorry if I am taking that comment as a slight, I do appreciate you linking the manual and assuming I haven't read it already though. ? I will try to adapt to using the soft synth rack and see if that makes any difference.

Interesting I did not know that was a problem with these latest versions of code, I will try to adapt to using the synth rack instead and see if it makes any difference.

A few days ago I made a post about creating a project in Cakewalk and how the audio engine crashed irrecoverably. I wiped out all audio, MIDI and plug-ins from the project and it still refused to initiate the audio engine. It wouldn't play back even one audio track or MIDI track without the engine crashing no matter what the buffer size was. The solution was to abandon the project and start again. I was also not the only person to experience this behavior according to a reply in that thread. So abandon the project I did and I started over with a new test track, slowly inserting plug-ins and audio tracks just to make sure the engine wasn't going to crash on me again. To my delight, it did not crash. So being optimistic I spent the last day creating a custom project template. After I had the project template built I dragged a MIDI drum track in and set it to play back through Superior Drummer 3. I noticed that the track level meters would stay lit up, frozen in position when the track was stopped and no audio was going through it. The level meters stayed lit up through the entire audio output chain, from track to bus, to master to hardware out meter, all of them stayed lit up. It was also lighting up the MIDI track levels as if it were an audio track (not sure if that part is normal or not?) The only tracks in the project are one MIDI drum track and one audio track with Superior Drummer 3 inserted into the FX bin. So there wouldn't be any audio signal passed through when the playback was stopped.. but the level meters stayed lit up anyway. This problem persisted even after I deleted the superior drummer instance and re-inserted it, and deleted the MIDI track and re-inserted it, and shut the program down and re-launched it... and cycled the audio interface power. So I went back to the blank project template I had created and re-inserted the MIDI track and saved it again under a new name. This time the level meters did not stay lit up when the track was stopped, which is how it's supposed to be. So now I have two projects with identical content, the only difference is the project name. One works correctly and one doesn't. The one that doesn't work correctly is irrecoverable, as if some hidden value is being saved within the project data that I can't change from the user interface. The only option I have to resume normal program behavior is to abandon that buggy save and move on with another one. Ordinarily I'd shrug and move on but coupled with the problems I had earlier this week I am losing confidence in this platform and am afraid at some point I will have a large project with weeks worth of time invested and the program will pull some random glitch and destroy it. I've never seen nor heard of behavior like this before as the issues are not repeatable even on the same hardware. I did save both files so Cakewalk can take a look if they want. Maybe they can find some strange write-state being saved that is beyond the reach of the end user? In the grand scheme of things the level meters staying pegged when stopped is nothing, but it's indicative of a larger problem when projects can just break in random ways. If a project gets too large and I miss something, even if I am interleaving saves with a double-save strategy, who knows what I might miss that will come back to bite me later. I REALLY don't want to have to take a broken project in the future and export every audio and MIDI track and re-import all of them into a new project and then go back and re-insert dozens of plug-ins and duplicate all of the settings (if I could even remember them). This is a nightmare, LOL it really is. I just want to get back to making music and I've spent the last week troubleshooting this program.

OK I tried again tonight amd thr problem has not returmed. I was able to do a test run w 9 neural amp instances and 1 superior drummer 3 midi track(18GB kit all bleeds on) and no issues with latency or delayed start at 128 buffer size. Engine doesn't seem to he breaking a sweat. Engine load about 18% over 33% and all core meters are just barely dancing into the visible area of the level meters in the Performance widget. I don't know WTF happened with that other track last night but looks like I'm good for now. Thank you everyone,

Hi Noel, thanks for replying. I already did what you suggested as my first suspicion was that a plugin or soft synth was to blame. But as I mentiomed the engine was still crashing even with ALL plugins and soft synths deleted and the program and audio interface restarted. Also happened regardless if buffer size was seto to 128 or 4096 or anything in between. Once the file was broken there was no recovering it no matter what I did, I will take another look tonight to see if I can uncover anything else. It likely was a plugin conflict initially but it's a lingering effect that remains even after the offending plugins have been removed from the program, that's the strange part.

Hey Mark, thanks for confirming I'm not the only one out there running into this. Could be disastrous if it happened to a mature project. I'd have to resort to carefully saving every project along the way and also making backup saves to make sure I had a safety net. Auto save would actually be more dangerous because the project could save in a broken state before I even realized what had happened. I'd be happy to share what little there is of the project I created with Cakewalk, although as mentioned all plugins and soft synths were removed and the project still kills the audio engine every time it loads... I'm wondering if Cakewalk techs would even be able to recreate the problem on their end with different hardware? Might be able to uncover something at least. This should definitely be at the top of their list of bug fixes. Now I'm seriously contemplating just switching DAWs outright because some of my projects are massive and take months to complete. If I ever lost one of those I'd probably have second thoughts about ever touching a DAW again or even picking up an instrument, LOL ?