AAE error -9173 stronger than ever on PT 12.5

[jeffro]

From http://protools.ideascale.com/a/pages/instructions - "Note that while it might be helpful to vote on bugs, the severity of the bug carries more weight when Avid is prioritizing bug fixes." So I'd say more important than voting is filling out the linked form to get a better picture of the systems affected (which will ultimately lead to a fix). I added it there (and made this thready a sticky) to raise visibility and will add additional detail as it becomes available. Thanks.

[nigelpry]

Originally Posted by jeffro

From http://protools.ideascale.com/a/pages/instructions - "Note that while it might be helpful to vote on bugs, the severity of the bug carries more weight when Avid is prioritizing bug fixes." So I'd say more important than voting is filling out the linked form to get a better picture of the systems affected (which will ultimately lead to a fix). I added it there (and made this thready a sticky) to raise visibility and will add additional detail as it becomes available. Thanks.

Jeffro, no criticism of you involved, implied or intended, we appreciate your efforts and understand you have to work within the system provided.

[Wireline]

Seconded...the mods and actual tech staff here have a seemingly impossible task, and no disrespect was implied or intended with my question.

Sometimes it's rough being caught between the dawg and the fire hydrant

[TOM@METRO]

Originally Posted by Wireline

Sometimes it's rough being caught between the dawg and the fire hydrant

Thanks for that.

[mkosacek]

Damn Daniel....

UAD finally supports Windows 10 so I made a backup, wiped everything and started from scratch with a brand new Windows 10 install, with latest updates, installed the UAD 8.6, and then Pro Tools 12.5 and all my plugins. existing sessions opened but then I actually tried recording...

I had a virtually empty session - no plugins except for click II and I turned off the "blinky light" - and was trying to record about 12 tracks of drums and it kept crashing randomly. I tried with and without increasing the disk cache (I'm using pretty fast SSDs - they are MLC but even the write throughput is faster than my old 7200rpm disk). I played around with the buffer size and finally found something that sort of worked (buffer of 256 and "normal" disk cache). Finally got the drums recorded but had to edit a few stops and starts (since PT kept giving me errors). Then when editing I saw the "hang" that I had been seeing with 12.4 -- when zooming in it hangs for several seconds and then eventually usually comes back to life...

so I'm definitely going to have to go back to 12.4 AGAIN. I may try disabling hyper-threading but I think its a lost cause.

[TOM@METRO]

I'm running 12.4 (Hyperthreading disabled). For me, his has been solid enough to run with clients.

Some are better with 11.3.2, I haven't had to go back that far.

[mkosacek]

yeah, I was mostly stable on Win7 and 12.4, but silly me, with the holiday weekend thought I might have time to switch it up again... I think that when I up the disk cache to 2 or 3GB with 12.4, then I see that editing "hang" a lot less. so I will go back to that soon...

[tonepad]

You guys trying to flog the 12.5 dead horse are amazing...I admire your perseverance but take the collective Forum word for it and stay put at 12.4 which "should" be good for the most of us on W7/8/10 and Mac OS X 10.9/10.10. It is my experience running rigs with W7 and OS X 10.10 that 12.4 is solid. It's a head scratcher that some folks are having issues with the release and have to roll all the way back to 11.x. Also sad since they are missing out on some great 12.4 features. I've been in the camp that thinks Cloud Collab is vaporware and with this 12.5 debacle i feel confident in my condemnation :)}=. I'd be really happy if the day comes when that is working AND they let me run it on my own FIOS server cloud...hey a boy can dream.

The take away: forget 12.5 for another couple of dots and about our subscription value...HMMMM!!! just like Avid's stock price it's not so valuable these days.

[noiseboyuk]

Originally Posted by tonepad

You guys trying to flog the 12.5 dead horse are amazing...I admire your perseverance but take the collective Forum word for it and stay put at 12.4 which "should" be good for the most of us on W7/8/10 and Mac OS X 10.9/10.10. It is my experience running rigs with W7 and OS X 10.10 that 12.4 is solid. It's a head scratcher that some folks are having issues with the release and have to roll all the way back to 11.x. Also sad since they are missing out on some great 12.4 features. I've been in the camp that thinks Cloud Collab is vaporware and with this 12.5 debacle i feel confident in my condemnation :)}=. I'd be really happy if the day comes when that is working AND they let me run it on my own FIOS server cloud...hey a boy can dream.

The take away: forget 12.5 for another couple of dots and about our subscription value...HMMMM!!! just like Avid's stock price it's not so valuable these days.

For me 12.5 is a considerable improvement over 12.4. I think all of that is due to video engine improvements in Windows - I think they finally have it gripped in 12.5, it's the best it's been since 10. Waaaaay better than 11, waaaay better indeed than 12.4. So there's no way I'd go back. But I do have crashes and playback stall errors in 12.5 I didn't have in 12.4. I'm lucky though, in that these crashes and stalls are relatively rare. It's an occasional irritation vs is a constant irritation of video bugs.

I'm hoping the next version stabalises the bugs without introducing the new ones, obviously. I'm also DESPERATE for Field Recorder improvements - when matching only with timecode it still also matches with every file already on the project, which is a) insane and b) a colossal PITA to unpick. If they fixed the playback bugs and sorted that Field Recorder issue, I'd likely stick on that version for years.

[nigelpry]

Originally Posted by noiseboyuk

If they fixed the playback bugs and sorted that Field Recorder issue, I'd likely stick on that version for years.

Sounds like exactly the reason why someone might think it best NOT to fix too many bugs right now.