DJI Osmo Pocket 3 timecode accuracy test
HTML-код
- Опубликовано: 31 июл 2024
- How accurate is the DJI Osmo Pocket 3 timecode when jammed to an external timecode generator? Let's check it.
The reference timecode generator is a BETSO SBOX-2RF. It has a very accurate TCXO clock chip with a maximum rated drift of 0.3 frames in a twenty-four hour period. The BETSO TCX-2 generator seen in this video was synced to it via BETSO's wireless sync protocol, which ensures zero drift between the reference and all synced receivers. The Sound Devices Scorpio used to record the external audio was directly connected to the SBOX-2RF with mode set to external timecode sync (so continuous sync, not jammed).
(The timecode tests were performed using DJI Osmo Pocket 3 firmware version 01.02.06.06.)
00:00 Intro
03:02 Consistent timecode accuracy is paramount
04:47 How to timecode jam the DJI Osmo Pocket 3
07:25 Timecode accuracy breakdown - displayed
11:33 Timecode accuract breakdown - DaVinci Resolve timeline
18:31 Conclusions 
Наука
Thanks Christopher that nice to know!
Thanks!
It did a lot better than I was expecting, but will still require checking clips. That said, in a lot of use cases a frame or two is probably acceptable (e.g., when not filming yourself talking where people will see the lipsync delta), in which case it will absolutely save time in post.
Thanks for taking the time to do the test, your pocket 3 seems more accurate than mine, when i sync using a Saramonic SR-C2001 3.5mm TRS/m to
USB-C cable and a deity TC-1, Tentacle sync Track E and my mixpre6 mkii my pocket three accelerates ahead soon after sync, all equipment on latest firmware as of 19th feb, in the uk the c21 deity cable and most deity cables are almost impossible to find, i have been in touch with a uk audio store who mentioned this to the deity rep and I'm told they'll stock some soon, not that a different cable will make any difference to the p3.
can dji tighten up the clock cycle with a firmware update or is it down to the dji lame quality control and pot luck ?
@jazzstream I doubt firmware will do it. I believe they do not have a TCXO clock in the P3, and are relying on a regular RTC chip. From observations over multiple cycles, I believe they record the RTC time when the camera goes to sleep and then when it wakes up they read the RTC again and compute the delta to update the timecode value.
FWIW, my test was done indoors in a room with relatively consistent temperature (around 78F).
@@cwichura
Hi Chris and Matt,
Today my Boya BY-K2 3.5mm to usb c cable arrived and i can confirm it syncs perfectly with the P3, one thing i have noticed is after i have synced my Track E to the Deity TC-1 i can then plug the Track E into the P3 and nothing on screen except that when i hit record on the P3 you can see a constant audio signal on the P3 audio level indicator, this i assume can only be the timecode generated by the Track E ? could it be that we can have a constant timecode with no drift, I'll put the recorded track onto prem pro or audition later on when i have time to see if the timcode signal is recorded and also if i can replicate it via the TC-1.
i just put the TC-1 into master/audio out, plugged it into the P3 and the timcode audio pulse shows on screen even when not recording, hit record and playback and it is clear and loud timecode.
too much drift in DJI.. i have a 3 camera setup and this dji Drifts way too much every 4-8 minutes i gotta do slip audio several steps to the right... in some cases almost 14 steps.
I think they just use the RTC chip to maintain their timecode. So there will be more variance, especially at different ambient temperatures.
Does anyone know how to fucking disable the time code feature so that I can get the normal time and date?
In the Timecode menu, there is a button to set the timecode to the system clock's current time. You will want to do this each time you turn on the camera.
The system clock appears to be auto-updated whenever you access the camera via the Mimo app.