11.2.1 My Findings, -9173 error with BTD

[JFreak]

Avid has their hands full in fixing the bugs and testing, and besides it wouldn't be good making a point of what is broken. Fixed are always mentioned in the readme documentation

[Intransit]

Originally Posted by zion

This is odd! I have NI Komplete Ultimate and Ive tested them NI Massive and all with tons of plugins behind them in different orders and RTB and off line bounce both work fine here on Pro Tools 11.2.1 HD on PT HD Native PCIe. This is really strange. I've never had an issue with this on my rig. I wonder how our systems are different.

Doesn't look much different then mine. I have two service tickets open and I'm always emailing with an Avid tech. We went through every step, nothing fixed it. I'm using the 192 but I hooked up an omni and same issue.

The plugin has to come after Massive. I've only seen Sound Toys and those Avid plugs do it. Also switching to built in I/O gets rid of the CPU peaks.

[Intransit]

Originally Posted by Eric Lambert

Wait a minute... You've not been able to bounce to disk successfully under any circumstances when using 11.2.1?

Offline seems fine but I can't get through a real time in 11.2.1. I didn't install 11.2 because of the people reporting the real time issue. I was printing RT BTD daily with 11.1.3…

[Intransit]

Originally Posted by Danny Caccavo

FWIW, Avid is VERY aware of the bounce bug. They couldn't get a fix for it in time to get 11.2.1 out the door - and since 11.2.1 fixed so many OTHER things they did not want to hold it up. No need to make idea scale topics on it.

Good to know. I emailed an Avid tech friday but hadn't heard back.

[jryser]

Yes thanks Danny! I got a whole new OSX Mavs clean install out of trying, so it wasn't such a horrible ordeal. Got rid of a few other things and my computer is clean. Oddly my B rig handled the change well, and is fine. Might be something in the MBProRetinas.

[musicman691]

Originally Posted by derFunkenstein

How are you guys bouncing to disk in real-time? I just want to make sure I'm not repeating what you've already said (or maybe confirm that I'm seeing the same thing).

I'm bouncing instrument tracks to disk by

create/record the instrument track
create a new audio track
set input on the new audio track to be the instrument track
record arm the audio track
record the audio to the track

At that point, it's not crashing for me. I have a 27" Haswell iMac running 10.9.4.

Where it does crash for me is if I right-click the instrument track and delete it without setting the input on the audio track back to no input. That's frustrating.

I've been doing real time like that since I got into PT - always works; never use PT bounce to disk function. There's no need to delete the Instrument track - just right click and select 'hide and make inactive'. That takes it out of all processing. If you do that then you can easily go back and make changes if you don't like what you did.

[Eric Lambert]

Originally Posted by Intransit

Offline seems fine but I can't get through a real time in 11.2.1. I didn't install 11.2 because of the people reporting the real time issue. I was printing RT BTD daily with 11.1.3…

We'd need real time bounce as we use time-dependent outboard gear.

[musicman691]

Originally Posted by Eric Lambert

We'd need real time bounce as we use time-dependent outboard gear.

Why not just record it all to a new track in PT? Works for me.

[Cliffy_Boy]

BTD real time gives a quick and easy way to get an mp3 to try on different systems and output sources. Saves a lot of steps.

[derFunkenstein]

Originally Posted by musicman691

I've been doing real time like that since I got into PT - always works; never use PT bounce to disk function. There's no need to delete the Instrument track - just right click and select 'hide and make inactive'. That takes it out of all processing. If you do that then you can easily go back and make changes if you don't like what you did.

That is actually what I had intended to do but I whiffed with the mouse (no, really, I meant to do that! - NOT!) and that's what actually caused the crash. Hiding and making inactive didn't crash it for me.