Problem Exporting from multitrack - error code 0000000B

Forum|Forum|6 years ago
May 22, 2020
2 replies
1716 views

Hi,

I'm having severe issues exporting a multitrack project from Audition CC2019 v 12.1.2.3

I receive a "severe error" warning, code 0000000B, and cannot export from the timeline. Neither can I bounce individual tracks, it seems.

I'm aware of people saying this can be connected to use of 3rd party plugins - I am using 3 in this session, which are Waves, Eventide and a Kilohearts "Tape Stop" plugin. I am going through removing/ disabling plugins temporarily to see if this resolves the plugin, but so far no luck.

I have to deliver an hour-long radio doc this afternoon, a lot of hours have gone into it, and at the moment it is stuck in my timeline.

Are there any solutions anyone is aware of? An update that will work? Anything? This is so frustrating

This topic has been closed for replies.

T

TrevLun

Participating Frequently

I've just turned all of the effects off (Audition and 3rd party) and still the same error.

SteveG_AudioMasters_

Community Expert

Don't know what's actually happening, but there are definitely issues with the current release and Multitrack saves. The inmediate solution is to replace your current version with the beta version available using the CC tool, which apparently fixes the problems. The only real difference with the beta versions compared to the release versions is that usage is logged.

T

TrevLun

Participating Frequently

Cheers Steve, appreciated.

E

elkalamarAuthor

Inspiring

So, it's taken some time (because I missed a track when disabling plugins) but it turns out to the Kilohearts Tape Stop plugin that causes the error. This is a bit of a nightmare as the plugin is used throughout 8 x 1 hour radio docs which were sent to me by a video editor to mix (very strange that he is working in Premiere Pro and the same plugin doesn't cause any issues there)

Hey ho. Another serious glitch to add to the long list of issues which make Audition completely unreliable...

SteveG_AudioMasters_

Community Expert

Audition has a long history of being very fussy about poorly-written VST effects - several manufacturers (including Waves) have had to rewrite VSTs so that they follow the specification and don't take short-cuts. Now you can blame Audition for that if you like, but personally I think it's a good thing. Haven't heard so much about it lately though - most VST providers have upped their game. Maybe this is one that hasn't?

E

elkalamarAuthor

Inspiring

hey Steve,
I'm no programmer and I'm sure you know what you say when you describe plugs that don't follow specifications, but at the same time Adobe could up their game and make sure the software is more resilient - I don't have these issue in other DAWs, but ALWAYS come up against issues when I have to work in Adobe Audition it is incredibly buggy (I'm not necessarily saying the issue doesn't lie with the VST in this case, respect your knowledge. Also frustrating is the inconsistency that the offending plug-in in this case does not cause issues in Premiere Pro, but does in Audition.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded