Hyperion SDR-to-HDR Alpha #1

I dont know why but i tried many movies but i get 90% of all error, when change to CPU only then it shows 44 min for a 2 second preview. I have latest gpu drivers RTX 2060 MSI. Has anyone any suggestion?

curious to give a try, as i have a pretty good workflow in term of conversion using ffmpeg + Vegas Pro 21…
3h to convert a 3h movie. curious to see it VideoAi can do better…

i read badly i thought it was a HDR to SD conversion lol… so it’s useless to me :frowning:

Yes I have the correct settings colourpane, but red and orange seem to be not correct anyway Rhea in the alpha is an enourmous step forward incredible how my old 30 year VHS movie looks like actually my LG does automatically add HDR style views, but I agree with the HDR from topaz and I see the HDR sign when I play it on my TV has capabiities that if the colour settings are corrected great promises. My TV is set to BT 2020 PQ I will have to doublecheck I see that gamma is BT 1897 on My LG

can someone say what we need to fill in in edit video when we right click on the source I see telecline do we need to set BT2020 in the proprties which BT2020

Sounds awesome!
Downloaded the Win version, but doesn’t open the file I want to test it with… (no problem with standard VAI).

here is the info, mov file from Panasonic HC-X1

  Duration: 00:55:28.32, start: 0.000000, bitrate: 95268 kb/s
  Stream #0:0[0x1](ita): Video: h264 (High) (avc1 / 0x31637661), yuv420p(tv, bt709, progressive), 3840x2160 [SAR 1:1 DAR 16:9], 93728 kb/s, 25 fps, 25 tbr, 90k tbn (default)
      Metadata:
        creation_time   : 2024-06-22T15:17:15.000000Z
        vendor_id       : [0][0][0][0]
        timecode        : 09:07:58:04
  Stream #0:1[0x2](ita): Audio: pcm_s16be (twos / 0x736F7774), 48000 Hz, stereo, s16, 1536 kb/s (default)
      Metadata:
        creation_time   : 2024-06-22T15:17:15.000000Z
        vendor_id       : pana
        timecode        : 09:07:58:04
  Stream #0:2[0x3](ita): Data: none (tmcd / 0x64636D74), 0 kb/s (default)
      Metadata:
        creation_time   : 2024-06-22T15:17:15.000000Z
        timecode        : 09:07:58:04

did you download mpv.io my complaint is that the orange teint is not gamma why was bt2020 chosen lg tv do not use this they use bt 1789 for hdr gamma

1 Like

Could you please add ProRes 4444 XQ export for windows users ? So I can try to integrate this model in my working process.

1 Like

What kind of Cray has to be used to test the model in this alpha ? :thinking:
If you DO release this :

We may test this model fore sure if available, else you’d have to rent either Frontier or Fugaku to test yourself :slight_smile:

I’m also interested in this. ProRes 4444 XQ can be obtained with “classic” ffmpeg. Was it removed due to licensing, as it’s an Apple codec, and you only support it on MacOS, or is there another reason?

I did, but mpv is only a player btw… and the input is not even HDR, just a simple rec709 in H.264
tried also with an H.265 export I had lying around that I did directly with VAI, but no luck, with the Video AI Alpha, nothing gets even loaded, let alone played… and I wish It would, as I have this video I highly want to test it with :slight_smile:

Maybe will end the color correction, export, and try a couple formats before giving up ^^
unless s.one knows what codecs are supported on the Alpha version… apparently either H.264 (high) or pcm_s16be are not… or might be the data stream on the input #2 of the file…

Here a video with the same characteristics, which does not even open, if you want to try too ^^

Hyperion does not seem to work correctly with AMD. I have a ryzen 9 7900x with a RX 7900 xt . It is not possible to output in H.265 main 10 but main and high. The image result is pale, low-contrast and overexposed. It looks quite good in ProRes 244HQ. Do AMD graphics cards not support output in H.265 main10?

They do, but it looks like it does not have been implemented …
I’ve got the same problem in all gen of my AMD boards.
Only Nvidia boards deals with somehow correct result.
If you bench your 7900XT you’ll see also pathetic results …

Main 10 and High are nothing to do with comparison, don’t even understand what this figure there
Main 10 is for color depth 10 bits
High is supposed to be High profile in HEVC standards, so we should have Main 10 + High or Main 10 + Main … (or Main + High / Main + Main)
Also Tier level is missing, so you’ll have to touch with other softwares …

On the paper Main 10 / 5.1 / High profile is best choice for up to 4K 60 fps result

Nvidia rox with tensor, but if you want to play your result on any player based on Kodi they are even not supported, you must have a >= Polaris board

→ The reason why UHD BR disks are Main 10 / 5.1 / High 4:4:4 BT2020/BT709(<- shit streamed)

image
All this part is completely unundertansbale

Shortly after the butterfly is hit there is a lot of Warping in the background when the bunny moves in front of the clouds.

Found out the mystery!
It does not open the file, because it is on a Samba network drive. If copied locally it loads, but unfortunately, the VM’s drive has not enough space, and allocating a half a terabyte just for this is not really feasible… will maybe try with a FFmpeg cut before delivery, but at the moment is a great problem for me :sweat_smile:

It loads no-problem with the stable version of the software.

As the optimum setting for Hyperion varies greatly depending on the camera and the scene (usually between 300 and 500 nits), an automatic setting would be desirable. Here, image by image would have to be analysed in terms of brightness and contrast range with special consideration of faces (face recognition). To prevent flickering, this automatic setting should have a certain inertia. An integrated scene recognition function, which then determines an average value for the respective scene, would be ideal.
It would be a great help for post-processing if you could implement something like this. However, the result is already very good, especially for underexposed scenes.

Translated with DeepL.com (free version)

2 Likes

I’ll be testing it on my Star Trek: DS9 DVD’s here tonight.

2 Likes

@tony.topazlabs I uploaded a Video File of a xrite chart this may be handy tuning the sdr to hdr model.In MP4 Container Main10 Profile is being replaced With Main.

2 Likes

I get error on everything I am trying to convert on my M1 MacBook, I assume it’s just not powerful enough for this early version of the model

What video player is being used to play videos on windows?

@tony.topazlabs By looking at your application, this is same as Nvidia’s RTX Video HDR (it’s fake HDR outputting plain SDR into HDR brightness, without any real HDR depth, contrast or even real wide gamut) but with a worse output settings. NVIDIA RTX HDR is already available in other encoding applications and outputs better than this. Not sure what you are trying to accomplish in here? Real HDR is completely the opposite of what you are doing here. It’s not copy pasting the SDR transfer function in same level to the PQ HDR gamma. It requires a complete new placement of everything to fit the new space, to actually use the HDR format benefits. Otherwise, you are faking HDR by using the exact same SDR data with HDR brightness EOTF.

I have compared the same SDR scenes in SDR output when in Real HDR mode. The contrast, shadows, range is the same in your output and in the original SDR file, the color gamut is just saturated to RGB levels (like Nvidia RTX HDR, fake) and the highlights are the same details, but pushed up, again same as with Nvidia’s RTX HDR, the real range is the same as SDR. This is a waste of time at the current approach.

NVIDIA’s RTX HDR is also fake, but as they make the mid’s and contrast more washed out, it feels more “real” by pushing only the specular/highlights up (in same exact SDR levels , of course)

You are pushing everything up. Which is the most fake HDR you can ever do.

May i ask if you ever watched a real HDR film or Dolby Vision HDR mastered content?

5 Likes