Noel Borthwick

Mix recall is fully confiigurable and you can save snapshots of the faders and recall them at will. If all you need is A/Bing two different mix settings this is the ideal feature to use and switching scenes should be very fast if you do not choose to recall the FX settings.

@jsg we’ll investigate this thanks.

This thread is for issues specific to the latest release. Please make a different thread for other issues. Thanks..

Its about 5-10 gb on disk depending on what components you install. I would start by installing just the program using the web installer from here. That way you don't need to install BandLab Assistant. Just install the basic program without any addons to start. Let us know how it goes.

Hi @Jerico Sicat we're aware of this. It is a new problem caused by Google who are now blocking google authorization from our webview. It caught us by surprise because they changed it before schedule. We are working on a different mechanism to bypass this issue and will release a new update with the fix soon. If you sign in using your bandlab credentials instead of using google auth it should work however.

The new plugin menu's do not use Windows common controls any more. We have plans of extending them further as we go along and an embedded search filter was also discussed. I don't have a timeline for when this will happen since there are other higher priority features in the pipeline before that.

Yeah I'd like to know how he gets it to consume 100% on his machine. Maybe he knows something I don't lol.

@CeaYou cant be sure of the cause until we look at it. Please send the project file and also follow instructions to get a crash dump. Under preferences | Initialization file you can set the ExceptionHandlingSeverity to 7 and it will capture more errors if you don't get a crash dialog.

Sure as I said if you want to control energy use then you can do that. Turning off the engine manually could also help. Additionally if you enable the "suspend audio engine when cakewalk is not if focus" feature it will automatically stop background engine activity when you switch focus away from Cakewalk.

Im not sure why the cpu use is a concern when not playing, unless you are trying to conserve battery power. Using the CPU doesnt cause any harm. In fact irrespective of this setting when you start the transport it will use the plugins.

Not at all. Export is SUPPOSED to try and max the CPU by design. This is how it can do it as fast as possible. There will be zero artifacts due to this because the audio driver is not involved. In practice it almost never hits 100% because there are other factors that gate performance such as the hard drive speed. Disabling stream audio through FX will not utilize the effects unless the track is streaming audio through the effect. Its not on by default because tempo based effects will not respond to changes in transport position unless the transport is rolling. Among other things.

Yes that is the option. Regarding exporting why are you concerned with the CPU meter? Its normal for Cakewalk to use as much CPU as possible when exporting because its doing the export faster than realtime.

By default cakewalk is streaming audio to plugins even when the transport is not running (there is a setting in preferences) VST3 has a setting for telling the plugin that its a zero buffer but its up to plugins to implement it. You can find out which plugin is consuming cpu by bypassing them one by one in the fx rack.

Lol we used to do work with them at one point. You can tell them that the bloke said that since the crash is completely within the plugin there is nothing actionable from our side until one of their developers investigates the reason for it crashing by looking at the dump. I don't have magical powers to analyze their code unfortunately

You don't even need a foot switch. Use midi shift key bindings and assign a special key to start recording.

Good to know. Were the outputs not visible in the port list earlier on? Was the issue specific to VST3 or VST2? There were quite a lot of improvements in the 06 release for multi out instruments mainly for VST3.

That is strange. apparently the resource strings got confused and displayed the wrong text. Let me know if that recurs.

2021.06 Update 2 has been released.

If I were to make a calculated guess I would think Air might be a potential cause. We've had issues in the past with some Air plugins. If you get a hang again use task manager to capture the dump and that should show the stack where the hang occurred.

Thanks for taking the time to test it, appreciated. I expect that you ran into a hang that was unrelated to the EA2. This is a relief since there isn't any code in EA2 that I can imagine would cause a hang. In fact I fixed a hang with one VST instrument. Please keep an eye out and report back if you see anything untoward.

@Base 57 Can you please provide more information? There is nothing we can go on with just a report of a hang. As far as we know there are no changes that could cause a hang so this could be an independent issue. If you can't repro the hang please capture a dump and send it asap so we can investigate. What plugins are being used here?

Two people in this thread have pointed you to an updated installer. Have you tried that? BandLab assistant as a means of installing will soon be deprecated.

Well not in general. The PPQ concept itself is still valid though its an old term - its a measure of accuracy or sub divisions of a quarter note. In the old MIDI days, the highest subdivision was 960 PPQ before computers could keep up. Since then most DAW's can handle far greater accuracy so the subdivisions are much more. Rather than get rid of the PPQ setting, concept we retained it such that the setting controls the display and editing resolution of MIDI. For example in the UI where you enter values in MBT we convert from our internal high resolution time to MBT using the display PPQ. That's one example where you will see the impact of that setting. Its also used when exporting MIDI files - i.e. internal timestamps of notes will be quantized to the display PPQ. So the PPQ also affects outgoing data. Another way to explain this is that our internal representation of MIDI uses high resolution timestamps but when its used in the UI, or in editing operations its quantized to the display PPQ. Hope I haven't confused you further Its a bit confusing I agree and could probably be documented better.

Right

Not quite. Our internal "PPQ" if you could call it that is 2 to the power of 27 (134,217,728) This is our high res subdivision of a quarter note.