Jump to content

Atomos Ninja V - Problem with Input Gamma?


Matt Perks
 Share

Recommended Posts

19 hours ago, androidlad said:

It's a known unresolved issue for many years, Atomos applies a forced data range to video range scale regardless of the actual range of the source, clipping highlights and crushing blacks, making the images look more contrasty. Fortunately the range can be mapped back in post, as demonstrated in previous posts.

I wonder why they do that? That's what it looks like to me, blacks are crushed but can be drawn out later and still, it's where I'd have taken the log footage anyway. Does this mean it doesn't really record log footage? It's pretty confusing..

 

Link to comment
Share on other sites

EOSHD Pro Color 5 for Sony cameras EOSHD Z LOG for Nikon CamerasEOSHD C-LOG and Film Profiles for All Canon DSLRs
20 hours ago, androidlad said:

It's a known unresolved issue for many years, Atomos applies a forced data range to video range scale regardless of the actual range of the source, clipping highlights and crushing blacks, making the images look more contrasty. Fortunately the range can be mapped back in post, as demonstrated in previous posts.

Are you really sure that it's an issue with Atomos? My X-T2 recorded in-camera F-Log as data range, but when I used it with the Blackmagic Video Assist 4K, it recorded in video range, levels went up to 109% IRE. It's also worth noting that Prores is assumed to be video levels, except for Prores4444 RGB. As long as the data is there just mapped differently, I wouldn't worry. In Resolve it's just a few clicks to map it back to data levels, in other NLE's or on the recorder itself you can use a LUT for that. I can create such a LUT if anyone's interested.

Link to comment
Share on other sites

3 hours ago, Attila Bakos said:

Are you really sure that it's an issue with Atomos? My X-T2 recorded in-camera F-Log as data range, but when I used it with the Blackmagic Video Assist 4K, it recorded in video range, levels went up to 109% IRE. It's also worth noting that Prores is assumed to be video levels, except for Prores4444 RGB. As long as the data is there just mapped differently, I wouldn't worry. In Resolve it's just a few clicks to map it back to data levels, in other NLE's or on the recorder itself you can use a LUT for that. I can create such a LUT if anyone's interested.

On the regular 5in Video Assist, there's a "HDMI Range" setting that allows you to specify the range of input signal. It's very simple for Atomos to implement this, instead of treating all input signal as video range.

ProRes can contain either full or video range data, it just need to be specified in the metadata header.

2144469718_Screenshot_2018-11-20Video_Assist_Manualpdf.png.d151cb7ae4c5c87d154d680c06df7726.png

Link to comment
Share on other sites

38 minutes ago, androidlad said:

On the regular 5in Video Assist, there's a "HDMI Range" setting that allows you to specify the range of input signal. It's very simple for Atomos to implement this, instead of treating all input signal as video range.

ProRes can contain either full or video range data, it just need to be specified in the metadata header.

Well, the 4K version doesn't have that. And I graded X-T2 F-Log files coming from the BM Video Assist 4K, one of the Atomos recorders, and the Convergent Design Odyssey 7Q+, they were all video range. It's really not a problem of Atomos, altough I imagine it would be fairly easy to implement what BM did on the smaller Video Assist.
I'm not sure if Prores has flags for full or video levels. I've never seen a full range Prores 422 for example. I'm on Windows so I could only try ffmpeg, but the Prores implementation ignored my level scaling parameters.

Link to comment
Share on other sites

  • 1 month later...
4 hours ago, dia3olik said:

hey guys! any news about this? maybe someone is still in contact with Atomos about a new firmware with this fix?

Thanks!

A few months ago (after raising this twice with Atomos) they said they would refer it to their development team......

I also think it's the responsibility of the camera manufacturers to allow users to select data or video range as the HDMI output. Having said that I don't believe it's simply a data vs Video range issue as I observed that the scopes were accurate but the issue was with the zebras. Someone from BM in an old thread said the zebras in the P4k are driven from the Luma (Y) channel which is fair enough in a YCbCr codec like ProRes but the scopes are in RGB and NLE grade controls work in RGB so there is obviously some problem with the YCbCr - RGB translation. Other external device manufacturers seem to be able to do it right though so I advise people to keep on telling Atomos they need to fix this.

Link to comment
Share on other sites

One thing I noticed on the ninja v with the zebras is that they are measured at the last stage in the image processing instead of in the first.

If you try for example to add a LUT the zebra value will change, because is measures the zebra after the LUT is applied.

For me it would be much better if the zebras are measured directly from the input signal before any processing so that I know my source footage is correctly exposed.

Link to comment
Share on other sites

  • 4 weeks later...
  • 4 months later...
On 10/24/2018 at 7:44 PM, Robert John said:

Put your .cube files onto the Atomos SSD  load the drive into the Ninja V. Make sure monitor is highlighted, tap the far right icon, go into the LUT's menu, tap on the numbered box where you want the LUT to go. It will then be highlighted. Then tap the folder icon and double tap the LUT you want. 

Only one problem... So I copied a handful of LUTs onto the SSD that I use on the Ninja V. Loaded them into the Ninja, and they worked perfectly. HOWEVER, when I finished recording video, I uploaded the files into Final Cut, then put the SSD back in the Ninja and formatted. Next time I go to use the Ninja, my LUTs are gone. For some reason, I was thinking the Ninja had a small amount of memory internal so that once I uploaded the LUTs from my SSD, they would STAY installed in the Ninja. Instead, it seems that every time I format the SSD in Ninja, I then have to remove, hook back up to my Mac, and copy the LUTs over again, then re-upload them again into the Ninja. This doesn't seem right. Am I missing something?

Link to comment
Share on other sites

  • 6 months later...
On 12/25/2019 at 8:13 PM, Danylo said:

Hi. I have a problem with Ninja V. The colors look different than on pc or in camera monitor. They are too warm. When turning on the monochrome mode on ninja V it looks like sepia. Did anyone else have the same issue?

What makes you think you PC monitor and camera monitor have accurate color? ?

Ninja V does have a slighter warmer factory calibration, around 6000K instead of standard D65. If it really bothers you, you can calibrate the screen with i1 Display Pro.

Link to comment
Share on other sites

  • 3 weeks later...
On 12/28/2019 at 2:55 AM, androidlad said:

What makes you think you PC monitor and camera monitor have accurate color? ?

Ninja V does have a slighter warmer factory calibration, around 6000K instead of standard D65. If it really bothers you, you can calibrate the screen with i1 Display Pro.

Hi everyone, 

 

Maybe @Androidlad you ll be able to answer.

I have the Sony A7III and the Atomos Ninja V.

I made a test this afternoon and I can't figure out what it's happening.

 I set my Sony in hlg3 picture profile.

I record first internally, then I record with the Atomos ( Atomos without matching camera and hlg) and get the same result.

Then I switch the Atomos in HDR input and switch CAMERA OUTPUT to the correct brand Sony the Correct Gamma HLG and correct gamut BT2020.

I let the monitoring gamma to native and the record was the same as the 2 first record.

I tried with the monitoring gamma on rec709, HLG and PQ and you can see on screenshot that the highlights are blown out.

The camera setting never change and the EV was set to 0.0.

All the screenshots are from my timeline in premiere pro.

I'd like to know what I'm doing wrong??

PS: I'm unable to put the screenshoots in the right order. The 3 pictures with blown out highlights are those with monitoring gamma set to rec709, HLG and PQ

 

Hope to read you soon

 

Sony HLG internal.jpg

 

 

 

 

Sony HLG Atomos Record.jpg

 

Atomos HDR Native.jpg

Atomos HDR REC709.jpg

Atomos HDR HLG.jpg

Atomos HDR PQ.jpg

Link to comment
Share on other sites

12 hours ago, Mindwide said:

Hi everyone, 

 

Maybe @Androidlad you ll be able to answer.

I have the Sony A7III and the Atomos Ninja V.

I made a test this afternoon and I can't figure out what it's happening.

 I set my Sony in hlg3 picture profile.

I record first internally, then I record with the Atomos ( Atomos without matching camera and hlg) and get the same result.

Then I switch the Atomos in HDR input and switch CAMERA OUTPUT to the correct brand Sony the Correct Gamma HLG and correct gamut BT2020.

I let the monitoring gamma to native and the record was the same as the 2 first record.

I tried with the monitoring gamma on rec709, HLG and PQ and you can see on screenshot that the highlights are blown out.

The camera setting never change and the EV was set to 0.0.

All the screenshots are from my timeline in premiere pro.

I'd like to know what I'm doing wrong??

PS: I'm unable to put the screenshoots in the right order. The 3 pictures with blown out highlights are those with monitoring gamma set to rec709, HLG and PQ

Hope to read you soon

It's a Premiere Pro issue, in the third clip with blown out highlights, Premiere Pro sees the PQ/HLG metadata and display the HDR clips as is, without tone-mapping, it assumes you working on an HDR monitor.

The highlights aren't actually blown out, if you check the scope, it can be brought back to SDR range with exposure tools.

The workaround is record the clips without the HDR metadata.

Link to comment
Share on other sites

2 hours ago, androidlad said:

It's a Premiere Pro issue, in the third clip with blown out highlights, Premiere Pro sees the PQ/HLG metadata and display the HDR clips as is, without tone-mapping, it assumes you working on an HDR monitor.

The highlights aren't actually blown out, if you check the scope, it can be brought back to SDR range with exposure tools.

The workaround is record the clips without the HDR metadata.

First thanks a lot for answering!

Do you mean record the cilps without HDR metadata on the Atomos or in premiere?

If it s premiere how do you change that?

In Fcpx it s easy but can't find the right way to do it in premiere.

 

Link to comment
Share on other sites

3 hours ago, Mindwide said:

First thanks a lot for answering!

Do you mean record the cilps without HDR metadata on the Atomos or in premiere?

If it s premiere how do you change that?

In Fcpx it s easy but can't find the right way to do it in premiere.

 

Record on the Ninja V.

There's no way to change that in Premiere at the moment.

BTW you're hot.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

  • EOSHD Pro Color 5 for All Sony cameras
    EOSHD C-LOG and Film Profiles for All Canon DSLRs
    EOSHD Dynamic Range Enhancer for H.264/H.265
×
×
  • Create New...