Hi,

I usually record in 25 fps because of the light flicker in many venues I work with.
And I use tentacle sync to provide timecode to all my devices.
Like most external timecode providers, the max fps is 30 for the tentacle sync.

I was asked to record a video in 50 fps for a customer.
I kept the the timecode to 25 fps. Since 50 is a multiple of 25, I was expecting the camera to be able to correctly extract timecode on the correct frame.

Not only it didn't wotk, but the camera fully brake in this scenario.
There is no error message.
The record button does nothing.
The lidar information disapear and the auto-focus gets manual.


What is execpted:
Camera should work properly (auto-focus, recording).
If timecode is incompatible, a warning should be displayed. Or an error if you're going to block recording.
If possible, support timecode for multiples of the framerate.


I tried re-starting the camera it was still broken. I had to re-installing the firmware.
However, 50 fps with 25fps timecode still doesn't work and might brake the camera again.

Hello, there. Sorry for the inconvenience. We will confirm your issue with our engineers first. Were there any information or any updates, we will reply to you here.

DJI Wanda Posted at 4-22 01:37
Hello, there. Sorry for the inconvenience. We will confirm your issue with our engineers first. Were there any information or any updates, we will reply to you here.

Thank you Wanda.
Let me know if there is anything I can do to help.

Deltaxel Posted at 4-22 01:48
Thank you Wanda.
Let me know if there is anything I can do to help.

Sure. Thank you for your understanding.

I experienced the same issue, but only once. I did a 4 days shooting, same config: 50fps, 25fps timecode (but with Rode Wireless PRO), and it freezed the camera once and it broke a 2h shoot file.
But after a hard reset (removing the batterie), it worked again after. But impossible to recover the 2h file.

I did more tests in the morning as I wanted to make sure everything works before today's shot.

The camera was re-installed to last version (same version that created the issue).
It now seems to accept 50fps on a 25 fps timecode.
Record seems to work and auto-focus too.
However, after a few minutes running, the lidar information disappear again.
After a couple of hour at 25fps, switching back to 50fps, timecode fails to sync again and block recording.

It looks like issues happens when running for extended amounts of time.

Thank you Chapeaublanc for the hack, will try.

Deltaxel Posted at 4-22 02:34
I did more tests in the morning as I wanted to make sure everything works before today's shot.

The camera was re-installed to last version (same version that created the issue).

Hi, our engineers would like to have the information below:
1. Firmware version
2. Video recording of the issue
3. The corresponding Logs of the issue. Please tell us the time when the issue occurred
We will escalate it to our engineers for analysis.
Thank you in advance.

Version: V01.05.0100
Issue: 20/01/2024 ~10:25PM
Logs and recording: https://www.dropbox.com/scl/fo/c ... t=rn7uwpgp&dl=0

On the dropbox you will see a low quality iPhone video recording the issue.
The video start right after the R4D was restarted. Which mean the issue happened a couple of minutes before (~10:25PM).
You can see after restart that the lidar information is still gone but the auto-focus started working again.
You cannot see on the video, but during 20-30 seconds, I'm frenetically pressing the record button without any result.
A spinner is showing next to timecode too.

Deltaxel Posted at 4-22 04:11
Version: V01.05.0100
Issue: 20/01/2024 ~10:25PM
Logs and recording: https://www.dropbox.com/scl/fo/c76jnz09or2a833xx6ahn/AMqiipWEms1fDN7hFFtwkC4?rlkey=qt18vp9f4djkwzxstw6ekerlu&st=rn7uwpgp&dl=0

Sorry for the late response. We just upload all the information to our engineers for analysis.
Note: Please click Reply button to post the threads so that we can received notifications.
If there is a result, we will get back to you.  

Deltaxel Posted at 4-22 04:11
Version: V01.05.0100
Issue: 20/01/2024 ~10:25PM
Logs and recording: https://www.dropbox.com/scl/fo/c76jnz09or2a833xx6ahn/AMqiipWEms1fDN7hFFtwkC4?rlkey=qt18vp9f4djkwzxstw6ekerlu&st=rn7uwpgp&dl=0

Hi, there. Our engineers said the log you offered was not from the main body on the DJI Ronin 4D because we can not encode it.
Could you please follow the instructions to download the logs for us?
1. Ensure that the Ronin 4D has been updated to V01.03.0200 or later versions.

2. Menu > System > Export Log in DJI High-Bright Remote Monitor and export the log to the storage media.

3. Wait for the logs exporting process to finish, connect the storage media to the computer, and you will see a Log folder.

DJI Wanda Posted at 4-26 05:23
Hi, there. Our engineers said the log you offered was not from the main body on the DJI Ronin 4D because we can not encode it.
Could you please follow the instructions to download the logs for us?
1. Ensure that the Ronin 4D has been updated to V01.03.0200 or later versions.

Hi Wanda,

Sorry about this. I though the Ronin Assistant would extract the correct logs.
I uploaded the logs directly extracted from the camera.

Here are also more details on the versions installed on the camera:
Firmware version: 01.05.0100
Camera: 10.01.01.21
Vision: 10.00.38.91
Gimbal: 01.00.19.90
Power: 02.02.05.55
Monitor: 00.02.03.82
Left grip: 00.01.03.39
Right grip: 00.04.05.87
Top handle: 00.00.03.41
Lens control: 09.17.00.20

Deltaxel Posted at 4-26 08:22
Hi Wanda,

Sorry about this. I though the Ronin Assistant would extract the correct logs.

Thank you for the information. We have forwarded it to them.