Possible Bug?

[Jake Wilganowski]

Dragon Epic, latest release build.

When selecting 6k with a timebase of 23.98, and a framerate of 50 (or others), and also enabling hdrx 2 or 3 stops, the resulting file does not play in slow motion, it plays realtime at 23.98, although the metadata shows 50fps. ALSO, the HDRx X track is the same exposure as the A track. This behavior is the same for both Redcine X and Davinci. All of the settings are selected and shown correctly in the camera GUI and menus. Can anyone else replicate this? It happened the other day on a shoot and I just replicated it at my house.

 

[David Battistella]

I don't think you can hdrx and slomotion at the same time.

Ie. 2x24p 1x track 1hdr track stream equals 48fps @6K

i think it's a processing power thing.

It might be possible at higher compression ratios though.

 

[Jake Wilganowski]

What's confusing is that it allows me to select it in camera and it shows up in the metadata but it doesn't actually record that way

 

[David Battistella]

Yup,

You should open a support ticket and upload a log file.

Battistella

 

[TheBied]

Dragon Epic, latest release build.

When selecting 6k with a timebase of 23.98, and a framerate of 50 (or others), and also enabling hdrx 2 or 3 stops, the resulting file does not play in slow motion, it plays realtime at 23.98, although the metadata shows 50fps. ALSO, the HDRx X track is the same exposure as the A track. This behavior is the same for both Redcine X and Davinci. All of the settings are selected and shown correctly in the camera GUI and menus. Can anyone else replicate this? It happened the other day on a shoot and I just replicated it at my house.

This was fixed as of 5.2.29. Previously, there was a possible issue recording the x-track when the maximum frame-rate for a format was selected.