Noel Borthwick

Not sure its the same. Yours was related to opening the normal template correct? That has indeed been fixed. The OP's issue is with a specific project file.

Yes please send a link so we can look at it.

@smoddelm if you have a copy of the problem project could you send us a link to download it and take a look?

Hi @David A. White I'd be surprised if the metronome had anything to do with it since many use a count in while recording. As Jon asked what happens if you have the audio metronome selected but turn off the metronome count-in on recording? Do you have a different audio interface by any chance to try? We no longer have any TASCAM gear to test with.

Send me a link to the project file and I'll see if it gets modified for me. BTW make sure you are running the latest release version since there was a bug fixed in the last release relating to this.

I think the conversion happens once per file and then stays in a memory cache. I believe we cache upto 16 previews after which it will import again. The files are created whenever the source format is not native such as a different sample rate or a non wav file such as MP3. The temp files should be destroyed when the project is closed. Regarding the sample rate conversion popups on closing, thats some unintended stuff happening when closing the preview files. We can look into preventing that.

Keep in mind that changing to offset mode itself doesn't change the existing mix in any way so there is no data loss. All it does is configure the mixer so that the gain controls now affect an "offset" gain stage on top of any existing levels you have. All offset gains starts out at unity so it will not affect your mix at all until you change something. Iow the normal gain staging and envelopes all stay intact. Offset mode is typically used to fine tune an existing mix which already has automation.

Does it really sound like it is zeroed out or do the faders just look that way? The offset mode tip is a possibility. See if the volume values have a + next to them.

That is correct

To clarify, it has nothing to do with the edit filter showing Clip Gain. The problem is the way you were selecting data. You were selecting the ENVELOPE and not the clip and that caused the issue. As long as you click on the clip to select it before bouncing it makes no difference if the edit filter is showing clip gain. The keyboard shortcut will be automatically blocked since I'm disabling the command itself when there isn't a proper selection. In the problem case its really not doing a bounce to clip so the length is the track length. The change will be in the next release...

Man you guys sure find obscure weird cases The problem only happens if you right click to select AND then choose the bounce to clip operation from the top level menu. The issue is that right click selection is selecting envelope nodes and not the clip itself. The bounce to clip operation should not be allowed in the UI under that state but it was not grayed out in the menu. When the command executes because no clip is actually selected it gets confused and ends up doing some default operation. I've fixed it so that a bounce is disallowed in this case. You should click on a clip to select it or do any kind of normal selection (not right click selection) before doing a bounce. FWIW right clicking a clip and choosing bounce to clip from the clips menu automatically selects the clip so most users would never see this issue.

For the person with the rdas1089 listed in the crash thats the Roland driver crashing and there may be a compatibility issue causing it. We don't have any way of addressing driver crashes unfortunately. If you send share a link to the minidump from the crash I may be able to see what operation is causing the crash. For Larry, are you still crashing after updating Cakewalk? If so if you share your minidump file it may throw more light on the nature of the crash or if its caused by a system related problem like what msmcleod suggested.

Correct, the metronome is disabled during all bounce operations so the only way to capture it today is by recording it via an aux track.

The first thing I would try for troubleshooting is to Restart your PC, then launch Cakewalk and create a new project with the blank template. Add a single audio track arm it and try and record. Does recording work? If not there is some instability with audio on the system. Also make sure you have ASIO selected assuming you have an ASIO driver. If you are still having issues we can certainly help troubleshoot it.

I've been working closely with Celemony to get to the bottom of some of the instability with detection not being triggered in CbB. We believe its fixed - Using a test build from them I can't repro the issue where it would hang on MIDI detection or not detect blobs after creating a region effect. I can't speak for release schedules but I believe good news is on the horizon. As to why it could appear to be fixed without any changes from us, this could be because race conditions behave in unpredictable ways. A subtle change in the timing of operations can mask the issue. This is likely why this issue has lingered on so long because it was hard to repro for some people.

Ill look into it thanks.

There is a new updated signal flowchart in there for those who need it.

A reset to defaults option may be useful in the pro channel. I'm not at my pc but there may already be a prochannel preset for this. If not you can make one and apply it to all your tracks

Did you miss the export to BandLab feature? Its been there for several months now https://www.cakewalk.com/Documentation?product=Cakewalk&language=3&help=Dialogs2.158.html In January we also added the ability to open BandLab projects. This is a feature still in preview.

Have you read the documentation on setting this up? https://www.cakewalk.com/Documentation?product=Cakewalk&language=4&help=Mixing.32.html Here is a nice video tutorial from one of our users.

The Cakewalk Mac prototype was hardly a failed experiment! It was very successful considering we got about 80% functionality with very low development cost, and it demonstrated to us what we would need to do to take the project further if we wanted to. It also helped us to make several improvements and optimizations to the SONAR codebase. Ultimately it was a budgetary decision to not pursue it. These days all cross platform apps use a framework. It makes little sense to write per platform apps from scratch due to the high cost of development.

Which VST? likely a plugin corrupting memory.

There is no extra gain staging applied when exporting to mp3 within Cakewalk. We're passing the same audio data that is written to a wave file after bit reduction since the mp3 encoder doesn't support higher floating point but depths. As CJ said mp3 encoding can create artifacts depending on the algorithm and bit rates chosen so make sure you are picking high enough settings. Also some people have found that if you have inherent phase problems in your mix encoding can make it sound different from the wave file. In any case you can eliminate any gain staging problems by importing the final wave file into a empty project and exporting just that to mp3. Then compare the two. Since we've established that this is not a problem you may want to add solved to your thread title.

start screen uses the chrome embedded framework CEF. All apps built with that including chrome behave that way because they launch child processes.

@Bruce Searl I think there is some confusion about how the bounce presets work and there has been no change in behavior. You will get the same result in any version of SONAR if you export the what you hear preset, or choose entire mix in the mix options. Cakewalk presently has no way to distinguish a headphone/cue mix from the master mix. What your see as the master bus in your project is simply a bus named *master* that came from the default template when the project was created. It could have been called main/mix/speakers or anything you want. The entire mix setting in the bounce options instructs the mixdown process to sum ALL bus outputs to a single stereo mix. This option should not be used when you have sub mixes in the project going to different outputs because it will result in a higher gain output. Instead, for this use case you should explicitly export just the bus you want which in your case would be master. Another way would be to solo the master bus before exporting with the entire mix setting enabled. In short this is not a bug. That said we could do better to warn the user when using the entire mix option if we detect that included buses are going to different hardware outputs.