Hi there,
Tried both dithering options (i.e. with "Enabled" and "Disabled") through
File > Save As > Convert Sample Type > Bit Depth > Advanced > Dithering.
But the saved output file with the 'Dithering' option looks like working in the opposite way (i.e. dithering is disabled when "Enabled" is selected and vice versa).
Notice that I’m currently using Adobe Audition ‘Build 14.2.0.34’ (the previous versions look the same though) and tried 48KHz/16-bit generated tone with extremely small gain (-90 dB) just to see the effects of dithering more clearly.
Additionally,
Close/Reopen the file is required to check out the changes only when Dithering is “Disabled” (but actually dithered). No need to reopen it if “Enabled”.
And the last setting is gone (indicating "Disabled" always) when I revisit the menu again (just to make sure which option I've selected, right before saving it finally) which is not pretty intuitive and confusing.
Hope the GUI get revised, if applicable.

Thanks,
HP Lee

Hello adobe

Inquiry about premiere and audition

-Softube's plug-in VST3 is not applied (no sound)

(VST works very, very, very well)

-Only Audition 2020 and Premier 2020 do not work

(The 2019 version works very, very, very well. Setup and rooting are the same)

-Of course I did cross-validation.
Both intel and amd cannot work

-Of course, other companies' VST3 plugins work very, very, very well.

I tried clean install ->

Doesn't work

Of course, Softube's plug-in is the latest version.

softube is a promising plug-in company

Today, the quality of video and sound is increasing, so many people will use external plug-ins as well.
I ask you to review this

(There is a free plugin provided by softube. Likewise, vst works, but vst3 does not)

Hello there! I’ve been an Audition user for years and years now.

Having made some presets for the effect rack (single file and multitrack) I encountered the problem, that for some time now the presets do not work correctly. Maybe it happened in a recent update?

All the effects get loaded into the rack, but with most of them, their respective settings are set to defaults when I load the rack preset.
I have some speech processing chains which I update regularly to make them fit my needs. But there, lot’s of the effects in that preset have gotten reset. Especially Singleband and multiband compression show that problem. Sometimes the effects rack preset saves the internal settings, and sometimes they seem to get lost.
That’s a real problem, I cannot check all effects in all my presets all the time. I have to be sure, that they work and do not reset themselves.

Does anyone else have that problem?I’m using 13.0.5.36

Importing user preferences and effects does not happen. This is the fourth time I have experienced this issue and with the latest update (13.0.1.35) it is happened again.

When I chose to update Audition from 13.0 to 13.0.1, I made sure the "import preferences" option box was checked, along with the other option box (I can't remember know, "save something/or other") option box and as well. The 13.0 preference folder was in it's correct file path and I expected it to be used for the upgrade.

However, at the end of the installation process, a dialogue box popped up saying the "preference folder 12.0 has been found. Do you want to import these preferences?"

No, of course not, I wanted it to import from the newer 13.0 preference folder, so I clicked "No".

No additional preference folders were offered and Audition opened and all of my preferences, workspaces, etc., were lost. (Just to be clear, when I updated from 12.?? to 13.0, I chose "Yes" when asked if I wanted to use the 12.0 preference folder and those preferences were not transferred over. I called and left a report with the help desk, ticket #ADB-9791065-X0H8.

Since the earliest days, I always keep a backup of my preference folder and update it before I upgrade, so I was able to restore my preferences and effects.

However, this begs the question, why are the updates pulling preferences from the wrong folder? I stated above, this is the fourth time this error has happened. It happened when I updated from 11 to 12.0 to 12.1, and the next iteration, and again from 12.? to 13.0. The upgrade finds the "Oldest" preference folder (in my case 11 and 12.0) and uses that as the reference file. Please check into this.

Thanks,

Rhett