Drifting Video offset

[smurfyou]

Originally Posted by Schottlandru

Just an update on interesting findings:
I think it may be linked to processor Speed Stepping (EIST for Intel i.e.).
These I usually have disabled (re DAW OS optimization), but it seems that when they are enabled while loading PT or a PT Session, they throw off the internal latency calculation.
Have to delve deeper into this but I have been pretty consistent with offset values for this one session now over the last week - always making sure I have my right CPU profile loaded when opening PT/session.
Other things I have done also: changed PhysX away from NVIDIA GPU to the CPU and disabled some of NVIDIAs "auto" choice on which GPU does what etc.
Might have been a combination of things.

Hope it helps the OP or others...

I have that disabled on Windows systems I use.

Interesting about the NVidia settings.

[Schottlandru]

How do you have it disabled - BIOS only or are you also using ThrottleStop (I can let ThrottleStop re-enable stuff, indepent of the BIOS, so Windows system power settings might be messing with stuff still)...

[smurfyou]

BIOS setting.

[HDXSound]

Hi,

Got the Sync HD and and Aja Gen 10 in the mail today.
Just to get the connections right:

Aja GEN out > AJA Express IO Video REF in
Aja GEN out > Sync HD Video REF in
Sync HD > HD IO Loop sync in?
Do i need a video bnc terminator on the HD IO?

In Protools i set the Clock source to video ref?


Thanks guys!

[originalscottyg]

You need a 75ohm terminator on the unused Video Ref connector on the Sync HD.

Loop Sync needs to be connected in a loop:
Sync HD Loop Sync Out > HD I/O Loop Sync In
HD I/O Loop Sync Out > Sync HD Loop Sync In

In Pro Tools, set the clock source to Video Ref with the setting that matches your project's frame rate and resolution.
And make sure the dip switches on the Aja GEN10 match the project specs as well.

Hope that helps!!

[HDXSound]

Thanks a lot Scott!
Love this community!!!

[Schottlandru]

Just a quick update after some time, and some further research (PT 12.8 this is):

It might be linked to "Dynamic Plugin Processing" (Playback Engine Prefs).
Disabling this seems to have worked in a first overnight test...
Maybe worth a try, should you be struck by this.