Dolby Vision now possible through MP4 Mux.

[RESET_9999]

Hi @RESET_9999 !
I tried 3-1 with profile 7 mkv input on your new version 1.9.7.
The process seems to run fine but at the end I'm left with a .mkv with only an audio track (no video). There's also a .bin file and a .hevc file which according to mediainfo has only hdr and no DV.
Thanks!

Muxing is disabled for P7 input until I have more time to work on that. The script should not have muxed anything though?
Just mux the HEVC file. FYI, an hevc or h265 file never has the DV flags, its normal.

[dapope]

Hi @RESET_9999 !
I tried 3-1 with profile 7 mkv input on your new version 1.9.7.
The process seems to run fine but at the end I'm left with a .mkv with only an audio track (no video). There's also a .bin file and a .hevc file which according to mediainfo has only hdr and no DV.
Thanks!

Muxing is disabled for P7 input until I have more time to work on that. The script should not have muxed anything though?
Just mux the HEVC file. FYI, an hevc or h265 file never has the DV flags, its normal.

No problem, I guess I can use TSMuxer to mux the the .hevc into a usable P8 file. I'm assuming I don't have to worry about the .bin file.
I tested some more and the .mkv with only an audio track is created if you say yes to the "convert audio to DDP" question.

[RESET_9999]

5.1 DDP track is encoded straight to an MKV on purpose in order to preserve any delay if present.

No problem, I guess I can use TSMuxer to mux the the .hevc into a usable P8 file. I'm assuming I don't have to worry about the .bin file.
I tested some more and the .mkv with only an audio track is created if you say yes to the "convert audio to DDP" question.

[LV8HD]

Hi @RESET_9999, could it be possible to make the tools path as a personal setting by moving them in the SETTINGS.bat file? I think it'd be useful for many people to void having multiple executables for the same tool spread out over the system.

[RESET_9999]

Hi @RESET_9999, could it be possible to make the tools path as a personal setting by moving them in the SETTINGS.bat file? I think it'd be useful for many people to void having multiple executables for the same tool spread out over the system.

yes sure, check out next version.

[tjayz]

@RESET_9999 Your FireTV is circular in the borders?
Like in the picture.
https://www.amazon.com/dp/B0BP9SNVH9

nop but I'd be surprised if anything changed about DV.
I might order one and return it just to find out .

So the current dolby_vision_stuff is not current for this device? All the things that make dv suck through fire stick apply even if using Queitvoid's kodi on p7?

Separate question, converting p7 FEL to p8 MEL I understand the FEL is lost, but reading some recent pages I learned of dovi_baker tool. Can this be used to bake in the lost portion only so the conversion is lossless to p8 FEL and flags DV when played?

Edit: Forgot to ask, for DV rpus, is generation via resolve always better than cm_analyze and these other newer methods assuming their is no official release that has manual L2 trim edits available? Sorry but not rereading last 100 pages to find this out. Thanks.

[RESET_9999]

Separate question, converting p7 FEL to p8 MEL I understand the FEL is lost, but reading some recent pages I learned of dovi_baker tool. Can this be used to bake in the lost portion only so the conversion is lossless to p8 FEL and flags DV when played?

yes but it requires re-encoding.

Edit: Forgot to ask, for DV rpus, is generation via resolve always better than cm_analyze

latest Resolve and CM use the same 2023 new algo

So the current dolby_vision_stuff is not current for this device? All the things that make dv suck through fire stick apply even if using Queitvoid's kodi on p7?

I just tried the newest Fire Tv and nothing changed regarding DV. Same issues and same stuttering with high bitrate video. I also could not get DTSHD nor TrueHD passthrough to work, all I got is LPCM like the old firetv.
I noticed that PLEX added support for Profile 7 (in the first gen too).

if using Queitvoid's kodi on p7?

yes

[tjayz]

yes but it requires re-encoding.

Is there a guide buried in this thread somewhere that covers this?

latest Resolve and CM use the same 2023 new algo

To be clear, the two yield the exact same quality rpu no scene detect advantage or anything else?

Same issues and same stuttering with high bitrate video. I also could not get DTSHD nor TrueHD passthrough to work, all I got is LPCM like the old firetv.

I might order this and give it a test and return if it sucks as described, as it seems strange they boast passthrough yet you are getting lpcm which has no atmos.... If passthrough did work and one gains cmv 4.0 , and if can somehow tweak those stutters this is a very appealing device. I can't help but think those stutters are related to onboard wifi issues, maybe using AC or even N signal would be more stable than AX.

[RESET_9999]

To be clear, the two yield the exact same quality rpu no scene detect advantage or anything else?

original scene cuts in CM is better but the difference is not big.

Is there a guide buried in this thread somewhere that covers this?

if you use the dovi_scripts, it's not too complicated.

automated: workflow 8-6-2
manual (with staxrip or in cli x265.exe):
1. workflow 7-1 in manual mode.
2. edit the avs script: remove the text overlay and uncomment convertbits(10)
3. convert the rpu to p8.
4. encode the avs file just like any HDR video file(with the rpu or inject it after the encode).

I might order this and give it a test and return if it sucks as described, as it seems strange they boast passthrough yet you are getting lpcm which has no atmos.... If passthrough did work and one gains cmv 4.0 , and if can somehow tweak those stutters this is a very appealing device.

not worth it.
Not true TV-LED and no 24fps support. DV MKV works great but most of my TS/M2TS give me a green or black screen. The Shield also stopped working with DV TS.

The ATV is the best solution for DV MKV rip IMO... Plus the TS/M2TS rip works (cant be FF/RW or resumed though)
And when Infuse will (I hope) add cmv4.0 support, it will be even better.

I can't help but think those stutters are related to onboard wifi issues, maybe using AC or even N signal would be more stable than AX.

its not a wifi issue. I tried the AC ethernet adaptor and it keeps buffering with the high bitrate test file.

[tjayz]

Per device description the Ethernet would be limited to 100mbs.

Nothing would resolve the TV-LED 24fps issues though. Maybe next gen cube will get it right.

Edit: Also per device description "Audio Support Dolby Atmos, 7.1 surround sound, 2-channel stereo, and HDMI audio pass through up to 5.1" if trying to pass through 7.1 and output 7.1 I think it would force lpcm, if trying to output 5.1 though think it might work, otherwise makes 0 sense lol

[quietvoid]

Not true TV-LED and no 24fps support.

The new stick 4K Max 2nd edition (2023) does do 24 fps now.
But not much has changed otherwise, though others report all lossless passthrough to work with Kodi.

According to Plex it's supposed to support DTS too.

[RESET_9999]

good to know that it finally supports 24hz in plex/kodi

I only tried DTSHD 7.1 and TrueHD 7.1 in PLEX so as tjayz said , that might be the reason why if only 5.1 channels are supported via HDMI passthrough.

[djanvi2020]

question,

I don't know if this was asked before or not, im just getting back into reconverting with the new features of the scripts, when you convert Atmos to DD+ is there a way you can up the bitrate of the DD+ conversion in the Dolby Script?

Thanks!

[skull88]

question,

I don't know if this was asked before or not, im just getting back into reconverting with the new features of the scripts, when you convert Atmos to DD+ is there a way you can up the bitrate of the DD+ conversion in the Dolby Script?

Thanks!

I'll let RESET answer as to why this may not be possible with current script, but from my extensive research over the years into audio bitrates and codecs, any perception of difference in audio quality, as you hit diminishing returns for a codec (e.g. V0 MP3, highest compression low FLAC bitrate, 640kbps DDP, etc.) is almost entirely attributable to placebo effect and confirmation bias. This was true back in the day of DTS vs. Dolby debates and DVD media, and it's true today with nearly all cases of audio encoding. Obviously TrueHD Atmos is going to be better if you are able to play it on a suitably high-end system when compared to an AC3 core or streaming DD+ audio, but the same frequency distribution transcoded from TrueHD Atmos or DTS-HD -> DD+ will sound the same as long as it's not below 640kbps, if you did an ABX comparison (blind test), and the script encodes to 1024kbps or higher, so it's perfectly fine. That's my 2 cents.

[RESET_9999]

question,

I don't know if this was asked before or not, im just getting back into reconverting with the new features of the scripts, when you convert Atmos to DD+ is there a way you can up the bitrate of the DD+ conversion in the Dolby Script?

Thanks!

All the workflows encode @ 1024kbps for 7.1(EAE ) and 1536kbps for 5.1 (FFmpeg). You can disable 7.1 encodings (line 20) to get 1536kbps from any lossless source. If you delete the EAE folder, it's the same as setting line 20 to NO.
It's possible to encode 7-1 @ 1536kbps with an AC3 core in the DEE workflows but I find the quality quite bad. FFmpeg and EAE produce better(noticeable) quality IMO.