[Confirmed] Timestamp issues

Hello Timo,

Thanks again for the response. I will attempt to help where possible.

Timestamp repro -

Set up identical Nuendo Live and Nuendo 5 systems fed from the same source, we use Madi.
Set up to chase LTC.
Do a test recording on both chasing code.
Import N5 and NL files into any workstation spotted to timestamps.
NLive files are offset significantly, a few frames.
Change buffer settings, record again.
NLive files are still offset but by a different amount.
Change MTC sync devices if you are able.
NLive files are still offset but by a different amount than the N5 files.
Change preRecord amount.
NLive files are still offset but by a different amount than the N5 files.

  • To eliminate variables we simultaneously tested with NLive, N5, PTHD, Cinedeck, EVS, SonyHR, KiPro, and MetaCorder. They all were as close as could be expected except NLive which was a few frames off.

Dropped samples repro -
This one is more difficult because it’s not consistent.

Set up identical Nuendo Live and Nuendo 5 systems fed from the same source, we use Madi.
Set up to chase LTC.
Do a long test recording on both chasing code, we used 3 hours.
Import N5 and NL files into any workstation spotted to timestamps.
Move NLive files so that an audio hit at the beginning lines up with N5 files.
Examine a hit near the end of the files, look to see if they’re exactly lined up.

You may need to do this a number of times, it took us 5 tries before we found one that dropped samples. On the other hand Tom had it happen on quite a few recordings, there does not appear to be a pattern. The only thing we can guarantee is that all systems have been set up correctly and clocked correctly; we used identical hardware for our NL/N5 tests and we’re very good at clocking and synchronization issues.

  • To eliminate variables we simultaneously tested with NLive, N5, PTHD, Cinedeck, EVS, SonyHR, KiPro, and MetaCorder. All the audio hits lined up exactly except for the instances where NLive dropped samples.

Sincerely,
Hugh