HandBrake 1.8 Discussion Thread

[s55]

viewtopic.php?p=206237

Discuss the HandBrake 1.8 release here.

[mduell]

SVT-AV1 2.1.0 (AV1 video encoding)

finally :wink:

[metricspace]

Hi, I have a quick question about Encode Settings usually embedded in the mediainfo of an encode. When I use NVENC, they are not available and I see no toggle or box to check to make them available. How do I get the Encode Settings in the mediainfo while encoding using NVENC?

[mduell]

Hi, I have a quick question about Encode Settings usually embedded in the mediainfo of an encode. When I use NVENC, they are not available and I see no toggle or box to check to make them available. How do I get the Encode Settings in the mediainfo while encoding using NVENC?

As has been answered on Reddit, they're not available for all encoders in the output file.

[metricspace]

As has been answered on Reddit, they're not available for all encoders in the output file.

They don't have to be in the mediafile for me, I just want to find them somewhere, thats what I'm getting at.

[pvanderp]

I'm having some problems with HB 1.8 transcoded Blu-ray content with Kodi 21.0 on my Android TV: There is no video.

- Happens with video material that has the DOLBY ATMOS marker.
- Same content transcoded with HB 1.73 plays fine.
- Other content without DOLBY ATMOS marker plays fine.
- All transcodes with VideoToolBox HEVC 10 bit (Mac).

I don't want to stay on 1.73, so I will try some variations with settings, e.g. without the "Passthrough common metadata" option.

I assume it is also very specific to the playback hardware. Possibly related to the H.265 decoding hardware in the TV.

regards,
Peter

[Ritsuka]

1.8 preserves the Dolby Vision metadata even when encoding with VideoToolbox, so either HandBrake is doing something wrong, or Kodi is.
Try to see if encoding with x265 10bit helps, and please post the activity log because it's so hard guessing every time.

[pvanderp]

1.8 preserves the Dolby Vision metadata even when encoding with VideoToolbox, so either HandBrake is doing something wrong, or Kodi is.
Try to see if encoding with x265 10bit helps, and please post the activity log because it's so hard guessing every time.

An attempt with the x265 10bit encoder results in a playable file on the TV. Although I forgot to set the RF value to a proper value, so the result was extremely low in quality. Running it again at RF20 just to be sure.
Kodi has no problems with the VideoToolBox encoded versions on the Mac itself.

So somehow using VideoToolBox results in something that is less compatible. Shall I run that encode again and provide the Activitylog?

Peter

[pvanderp]

Found out that other Dolby Vision content also does not play on the Android TV with Kodi 21, so this may not be related to HandBrake.
Kodi 21 has some extra Dolby options in the Player Settings which I must test first. Will report on that later.

[pvanderp]

This is not a problem with HandBrake 1.8, it was just revealed because now the Dolby Vision metadata is passed through. My TV supports some DV profiles, but not 7.6. I have to filter out the Dolby Vision metadata in Kodi 21 to enable playback of the Dolby Vision 7.6 content.

Maybe a future version of HandBrake would be able to convert some Dolby Vision profiles to HDR10, which seems to be supported by more devices.

regards,
Peter

[Rodeo314]

I suppose a toggle to discard Dolby Vision data might be useful. The base layer is likely HDR10 to begin with.

[pvanderp]

I did some more testing with Dolby Vision HDR video files with different Dolby Vision profiles. I used test files that are mentioned on the Kodi Wiki:

https://kodi.wiki/view/Samples#4K_(UltraHD)_Formats

I transcoded three Dolby Vision 5.0 test clips with 10-bit x265 and 10-bit VideoToolbox (Mac hardware encoder) and indeed the Dolby Vision profile information is retained in the output. If I add the output back to HandBrake, it reports the same profile.

However, if I transcode a Dolby Vision 7.6 profile clip (10-bit x265/VideoToolbox) and offer the output back to HandBrake, HandBrake reports that the Dolby Vision profile is now 8.1. Why is this?

regards,
Peter

tested clips:
DV 5.0: dolby-vision-amaze, dolby-vision-art, Mystery Box
DV 7.6: awaken-girl

[mduell]

However, if I transcode a Dolby Vision 7.6 profile clip (10-bit x265/VideoToolbox) and offer the output back to HandBrake, HandBrake reports that the Dolby Vision profile is now 8.1. Why is this?

Covered in the documentation:

The supported Dolby Vision profiles and cross compatibility IDs are: - 5.0 - 7.6 (base layer only, converted to 8.1) - 8.1 - 8.4

[pvanderp]

However, if I transcode a Dolby Vision 7.6 profile clip (10-bit x265/VideoToolbox) and offer the output back to HandBrake, HandBrake reports that the Dolby Vision profile is now 8.1. Why is this?

Covered in the documentation:

The supported Dolby Vision profiles and cross compatibility IDs are: - 5.0 - 7.6 (base layer only, converted to 8.1) - 8.1 - 8.4

Well, it states that, but it doesn't say why.

With the previous version of HandBrake, this was converted to HDR10. Now it's apparently partially converted to DV 8.1. Since it is partial, I think there should be a switch to retain the old way of converting to HDR10.

I will revert to HandBrake 1.73 for Dolby Vision 7.6 source material.

[mduell]

However, if I transcode a Dolby Vision 7.6 profile clip (10-bit x265/VideoToolbox) and offer the output back to HandBrake, HandBrake reports that the Dolby Vision profile is now 8.1. Why is this?

Covered in the documentation:

The supported Dolby Vision profiles and cross compatibility IDs are: - 5.0 - 7.6 (base layer only, converted to 8.1) - 8.1 - 8.4

Well, it states that, but it doesn't say why.

With the previous version of HandBrake, this was converted to HDR10. Now it's apparently partially converted to DV 8.1. Since it is partial, I think there should be a switch to retain the old way of converting to HDR10.

I will revert to HandBrake 1.73 for Dolby Vision 7.6 source material.

1.7.x didn't support DV for VTB, so you got HDR10; 1.8.0 does support DV for VTB.

[Rodeo314]

A way to discard the Dolby Vision might be useful regardless of the reason for the change.

[Gillietalls]

Sorry if I'm in the wrong thread but have a question about Dolby Vision playback on an Apple TV. I'm told the Infuse app only supports DV profiles 5 or 8. How can we use HandBrake to convert the DV profile to allow playback on an Apple TV? Thanks in advance for any assistance.

[rollin_eng]

Sorry if I'm in the wrong thread but have a question about Dolby Vision playback on an Apple TV. I'm told the Infuse app only supports DV profiles 5 or 8. How can we use HandBrake to convert the DV profile to allow playback on an Apple TV? Thanks in advance for any assistance.

https://handbrake.fr/docs/en/1.7.0/technical/hdr.html

[mduell]

Do a supported HDR/DV conversion in HB and you'll have profile 5 or 8 since that's all HB supports.

[TornaLuna]

viewtopic.php?p=206237

Discuss the HandBrake 1.8 release here.

Al instalarlo aparece un error: Can't write: C:\Program files\HandBrake. Worker.exe

¿Hay solución?
Gracia