Screen sharing causing 9173 errors

[dankin]

I've been using screen sharing for years when I'm tracking by myself with very few issues other than it being a little laggy. Since upgrading to 11 and now with 12, I get 9173 errors every time I track if I'm using screen sharing. It's strange in that I can count on it happening on the first pass every time, with out fail. But after that it may or may not happen again. I've had it happen on 2 different machines. Just curious if any body else uses screen sharing and has this issue? I would just use the new iPad app if they allowed you to change playlist.

[Darryl Ramm]

Just out of curiosity have you tried disabling/toggling dynamic plugin processing?

Checked all your plugins are up to date? Tried to temporarily remove plugin files to find any bad plugins?

What plugins (especially VIs) are instantiated in these sessions?

What make/model/spec disk drive are you recording to?

What IO buffer size are you operating at? Does increasing that make the problem go away? What session sample rate? How large a session? Are your computers fully optimized?

What changed with Pro Tools 11 was every plugin you had been running before (to AAX-64) and the whole new audio engine was introduced. So maybe more than usual the first thing to suspect is plugins. And of course, depending on what you are trying to do, screen sharing might just be a bit too much overhead for reliable operation on many systems, and you were just more lucky before.

[dankin]

Originally Posted by Darryl Ramm

Just out of curiosity have you tried disabling/toggling dynamic plugin processing?

Checked all your plugins are up to date? Tried to temporarily remove plugin files to find any bad plugins?

What plugins (especially VIs) are instantiated in these sessions?

What make/model/spec disk drive are you recording to?

What IO buffer size are you operating at? Does increasing that make the problem go away? What session sample rate? How large a session? Are your computers fully optimized?

What changed with Pro Tools 11 was every plugin you had been running before (to AAX-64) and the whole new audio engine was introduced. So maybe more than usual the first thing to suspect is plugins. And of course, depending on what you are trying to do, screen sharing might just be a bit too much overhead for reliable operation on many systems, and you were just more lucky before.

I have tried removing plugins. Also it doesn't matter what combination of plugins are in the session. Over all CPU usage is generally around 10-15%. Current machine is a 12core Macpro 5.1. Tracking to Hitachi Ultrastar drives. Buffer is at 128 on my SSL Madi card when tracking. Never had this issue before PT11, even on my old 4core Mac Pro. I keep dynamic plugin processing off. No VI's are in the session. The amount of tracks I'm recording could vary between 8 to up to 24. Doesn't have any affect on it.

I've been using screen sharing to control protools while I'm behind the drumset for around 7 years now with out issues until PT11/12. The only problem I've ever had, was it lagging behind some. Fortunately I don't have to do it everyday. But it still sucks when it stops recording in the middle of a take. I may end up putting a separate monitor, keyboard and mouse by the kit. The only reason I haven't, is the cable run would be around 50ft.