Noel Borthwick

Can you screenshot what you have set in Preferences | Folder Location for Export audio files?

@James Argo As Morten said "Can you please post a screenshot of the entire project folder path in Windows Explorer?" This will help us understand what your full project name looks like in windows explorer.

Not seeing that here. Can you send across the project file that throws this error?

We tried this here and there were no issues switching driver modes. Its may be specific to your hardware. Did you try this in earlier releases? Changes should work while a project is open - there is no need to restart the app. Re WASAPI I'm not sure what devices you have on your system. Some pro audio devices don't work well with WASAPI. For example Focusrite plays poorly in WASAPI mode. This is why we default to ASIO mode when an ASIO driver is available. In any case the new driver warnings are just a suggestion to users that there are known problems with certain drivers. You can still choose to use it.

Thank you for your great support and feedback so far. A final build 137 was posted (see start of thread) containing the following fixes. If you can please test this build and report back ASAP if you find any regressions. In particular, try exporting in ASIO mode and specifying a larger bounce buffer size. Please note that some plugins are unstable with larger buffer sizes (> 50 msec) Hang exporting project with arrangements containing IK Multimedia Plugins Bounce buffer size value was not respected in ASIO mode Exporting project with mono sidechain track send could cause problems flushing effects tails Exporting tracks with sidechains doesn't work if you don't make a direct track selection File Export dialog should default to Arrangements when launched from Arrangements Inspector Add new default config variables for "BounceFlushTailsMaxDurationSec" and "BounceFlushTailsThresholdDb"

For activation please read this FAQ on Activation, especially the section on in-app activation.

@Xel Ohhthanks for the report. We'll investigate this. Act chance you can share a link to a zipped project folder where this happens?

If the message is popping up you have user edited transients in your project, perhaps inadvertantly. You can ignore that warning and save if you don't care about the edits.

This is as intended and been that way for 15 years. Bundles compact audio into a single file and it's not compatible with audio snap edits

In preferences switch to WASAPI shared mode. We cannot offer support for ASIO4All and its unnecessary to use this with onboard audio devices.

Right because right click isn't changing the current focused item. We'll log it.

Definitely not seeing that. I click on a clip and it deletes the clip not the last effect. How exactly are you selecting audio. Probably best to make a video but post that in a different thread not the EA thread.

@Milton Sica I was able to get your project with all your audio after redownloading it. However both Jon and I don't see any problem here. It loads and all tracks and buses are audible. So I'm not sure what remaining problem you are seeing with audio being silent. In build 133 its working fine.

We just updated the EA build to 134. Build 134 has a single fix to address a hang with the Realtek ASIO driver. If you have this driver installed you can update to this build to try it. We've unblocked this driver from the compatibility list for now.

Thanks we'll investigate and try and reproduce. It may be a different buffering issue with WASAPI.

Thanks for sending the project. Since there is some audio missing I substituted some alternate audio. However I am not seeing any obvious problem in the build 133. I can hear all the buses in your project. Can you please explain with steps how to reproduce the solo issue you are having? You can PM me if you like.

Some plugin may not accept a high buffer size of 350 so don't use such a large buffer. Set it to 100

This is not related to the solo issue. From the picture this looks like tails not being flushed. Have you manually changed the BounceFlushTailsMaxDurationSec variable? If that value is set to the default of 20 it may be a different non plugin related buffering issue that we can investigate.

So this is new to Build 133? Please send your any project that can reproduce this ASAP so I can investigate it.

This is with build 133? If you are having solo issues please zip and send a link to the project folder. That is the only way for us to check because it is project specific. We can’t help with JBridge problems. If you have a crash send us the dump file. Also @Milton Sica its not clear when you started seeing the bus solo problem. Is it only in build 133 or were you having this problem earlier? If you load the project and play is it silent? Did the problem only happen after doing an audio export or bounce etc?

@Matthew Simon Fletcher @chris.r @Jacques Boileau This is resolved in build 133. It should also automatically repair solo states for any projects that might have had issues in the past because I've improved the solo logic for tracks. Let me know if its working for you now.

Thanks for your feedback but please make a separate thread for it or consider the feature request forum. This thread is exclusively for Early access 2021.09 release specific features.

2021.09 Build 133 has now been posted. This is the final release candidate so please check this out as soon as possible and let us know if there are any regressions. Details in the link above. Thanks for all your support and diligence in reporting problems!

The first thing to do is stop using ASIO4All. Its known to cause incompatibilities and we don't support it. The next build will have a warning asking users with ASIO4All and some other known incompatible drivers to switch to WASAPI mode or use a different ASIO driver.

We'll there have been a million changes to the engine over the last 3 years but the one you are seeing is a change to use a higher quality zPlane elastique time stretching algorithm. This release also has improved transient detection.