The first firmware 4.01 test ran for 6.5 hours, losing part of a frame in 15 minutes and going over a few hours when it lost less than two frames by the end. Next test losing a slightly larger part of a frame in ten minutes and I’ll monitor this for several hours.
What’s good is that I may no longer see those chunks of a second or more lost suddenly. This gradual loss is similar to before 4.1 but doesn’t get ridiculously bad. Still losing Timecode so quickly means I can’t use it. On a real shoot, I’ll have it taking TC from the Tentacle continuously when I can...
... MixPres are calibrated to an atomic clock. I suspect that so are Tentacle's but don't know that for sure. Run the test again with both devices set to 23.98 and if you still see that level of drift, contact our tech support team to arrange a calibration check...
Paul, I set all devices to 23.976 fps; the test to jam the Tentacles from the MixPre Gen Timecode vía the stereo out port ran for 9 hours and appears to be flawless. Both Tentacle devices match the Gen clock. No need to calibrate or blame the Tentacles or MixPre for inconsistencies.
Currently running (over an hour) the test of MixPre with Gen Timecode jam synced to a Tentacle. Monitoring that via the Jam screen, there is no difference detected at 23.976 fps.
So you must be relieved as I am. I’ll let it run longer but doubt there is a problem under 4.01.
However, I still want to verify if running at 24 fps now performs properly.
I can do a low level exFAT erase/format on my Mac (Disk Utility) as requested before stress testing 6/8 tracks armed writing 192KHz 32bit Audio. All I plan to use at this time is 6 tracks and 48KHz 32bit audio but I’ll do the stress test using your own approved SD32GB card. In practice if I was really running those rates, I’d test with the Wise 128GB card I have.
Sent from my iPhone using Tapatalk