Dolby Vision now possible through MP4 Mux.

[scaramanga]

Apologies to Reset - I know you mentioned to use Doom forum but it's a 5 day wait after registration so trying in here first.

I've got a setup of Shield 2019 through to LG TV utilising a Plex server and it can happily play native DV rips (Dune) and standard UHD rips (Sicario) from MKV
no issue.
When I have ran Sicario through the script (3-1) the film does trigger DV on the TV but there are blocky aspects when it comes to dark colours on light background and a few frames that are obviously awry.

Just wondered if I am doing something wrong in prepping the scripts, or do I need to invest in a Nvidia GFX card or a SSD to carry out the conversion work?

Thanks

[gm23o]

Hi,

I'm experiencing raised blacks in DV with some movies.
I'm using an Oppo clone connected to a Nexigo Aurora Pro UST projector.

Full Disc Rip - BDMV

I've noticed this recently when watching :
- Mission Impossible : Dead Reckoning
- True Romance

The letterbox bars and opening credits etc are very raised to a medium grey.

When I switch from TV led to Player led it improves.

Any ideas?

Any thoughts on this guys? RESET_9999?

[jayper]

Hi,

I'm experiencing raised blacks in DV with some movies.
I'm using an Oppo clone connected to a Nexigo Aurora Pro UST projector.

Full Disc Rip - BDMV

I've noticed this recently when watching :
- Mission Impossible : Dead Reckoning
- True Romance

The letterbox bars and opening credits etc are very raised to a medium grey.

When I switch from TV led to Player led it improves.

Any ideas?

Any thoughts on this guys? RESET_9999?

please ask any further questions related to the dovi_scripts here: https://forum.doom9.org/showthread.php? ... ost1997616

thanks.

[scaramanga]

You have to wait 5 days after registering for Doom Forum so in my case I took a punt on here whilst waiting to post in there.

[croweyes1121]

Last night I watched The Lord of the Rings The Fellowship of the Ring and I was able to fast forward. I used the latest version of tsMuxer and muxed both parts to individual m2ts files.

I merged mine in a single TS file.
So if FF works for each individual part, that pretty much confirms the issue is related to the length of the movie.
thank you

Yes but that isn't enough for me

I still haven't got myself a x700 yet, but I dug out my old x800. It can't do dolby vision, but I had some time today and figured it should be close enough to see whats going on (they should be very similar internal players if not the same).

Started with the second hobbit film. The raw m2ts and the tsmuxer file both wouldn't seek. 'Operation not permitted'.

Tried cutting the file with tsmuxer to 2 hours and 45 minutes. Seek worked.

Then I went for 2 hours 50 minutes. Seek didn't work.

Something in tsmuxer caught my eye: "--cut-end=10200000ms"

To me that seemed like such a specific round number. I have now tested both hobbit 1 and 2...

If the file is 2 hours, 46 minutes and 39 seconds or shorter. The file will allow seeking.
If the file is 2 hours, 46 minutes and 40 seconds or longer. The file will not allow seeking.

Turns out in milliseconds that is:

9999000ms: Seeks
10000000ms: Does not seek

From all this, I believe that if the file is greater than (or equal to) 10 million millisconds then seeking will not work. Anything below seems to work fine.

Does this align with what you have experienced on the x700? Know any titles that might be under this 10 million ms 'limit' that don't allow seeking?

Note: For me, on the latest tsmuxer nightly, the resulting file was always 1 second less than what I put into the 'end'. So if anyone tries this, take this into account if you are trying to be precise.

Why there might be such a limit I'm not sure - maybe someone else might know that

Never seen something related to length in ms, at least 10 million...doesn't really strike me as a number that would normally cause issues in the computing world

Has anyone ever figured out a workaround for this issue that doesn't involve splitting the file (which I really would prefer not to have to do)? Surely there's some way to change a setting in tsmuxer that allows the file to be seekable...

[RESET_9999]

Has anyone ever figured out a workaround for this issue that doesn't involve splitting the file (which I really would prefer not to have to do)? Surely there's some way to change a setting in tsmuxer that allows the file to be seekable...

I dont think there's anything you can do about it except using BDMV folder and It looks like a bug with the oppo and x700 with TS DV rip because the x800m2 doesnt have this problem.

[RESET_9999]

Hi,

I'm experiencing raised blacks in DV with some movies.
I'm using an Oppo clone connected to a Nexigo Aurora Pro UST projector.

Full Disc Rip - BDMV

I've noticed this recently when watching :
- Mission Impossible : Dead Reckoning
- True Romance

The letterbox bars and opening credits etc are very raised to a medium grey.

When I switch from TV led to Player led it improves.

Any ideas?

full disc rip?? are you sure because it sounds like your video is cropped which would produce a raised letterbox...

[jayper]

I merged mine in a single TS file.
So if FF works for each individual part, that pretty much confirms the issue is related to the length of the movie.
thank you

Yes but that isn't enough for me

I still haven't got myself a x700 yet, but I dug out my old x800. It can't do dolby vision, but I had some time today and figured it should be close enough to see whats going on (they should be very similar internal players if not the same).

Started with the second hobbit film. The raw m2ts and the tsmuxer file both wouldn't seek. 'Operation not permitted'.

Tried cutting the file with tsmuxer to 2 hours and 45 minutes. Seek worked.

Then I went for 2 hours 50 minutes. Seek didn't work.

Something in tsmuxer caught my eye: "--cut-end=10200000ms"

To me that seemed like such a specific round number. I have now tested both hobbit 1 and 2...

If the file is 2 hours, 46 minutes and 39 seconds or shorter. The file will allow seeking.
If the file is 2 hours, 46 minutes and 40 seconds or longer. The file will not allow seeking.

Turns out in milliseconds that is:

9999000ms: Seeks
10000000ms: Does not seek

From all this, I believe that if the file is greater than (or equal to) 10 million millisconds then seeking will not work. Anything below seems to work fine.

Does this align with what you have experienced on the x700? Know any titles that might be under this 10 million ms 'limit' that don't allow seeking?

Note: For me, on the latest tsmuxer nightly, the resulting file was always 1 second less than what I put into the 'end'. So if anyone tries this, take this into account if you are trying to be precise.

Why there might be such a limit I'm not sure - maybe someone else might know that

Never seen something related to length in ms, at least 10 million...doesn't really strike me as a number that would normally cause issues in the computing world

Has anyone ever figured out a workaround for this issue that doesn't involve splitting the file (which I really would prefer not to have to do)? Surely there's some way to change a setting in tsmuxer that allows the file to be seekable...

If you have an x700 or x800m2, and you're trying to play back a Profile 7 file (ie a UHD with DV), use tsmuxer to create a BDMV folder output. Place the BDMV folder in the root of a USB drive.

To my knowledge, there is no workaround for the seeking issue with TS files. I believe that is a device limitation.

[croweyes1121]

I dont think there's anything you can do about it except using BDMV folder

Oh, if that works, then I'm a happy camper. I'm happy to do it this way, I just want to be able to watch a 3-hr movie without stopping it. I just assumed it still would not be seekable even if I put it on the drive that way. Trying it now!

[croweyes1121]

I dont think there's anything you can do about it except using BDMV folder

If you have an x700 or x800m2, and you're trying to play back a Profile 7 file (ie a UHD with DV), use tsmuxer to create a BDMV folder output. Place the BDMV folder in the root of a USB drive.

This is not working for me.

The standalone m2ts file plays fine (albeit without the ability to seek). When I export to a BDMV folder, the X700 sees it as an AVCHD video file (as I understand it should), but it won't play. In fact, attempting to play it just locks up the player to the point that I have to unplug it. I've tried running the original m2ts file through tsmuxer to a BDMV folder and putting it back on the USB drive multiple times, same result every time. Any suggestions?

[RESET_9999]

i dont know, it worked the last time I tried a long time ago and I don't have to bother with this anymore with the x800m2.
Maybe something changed in tsmuxer?

[Hellboy.]

i dont know, it worked the last time I tried a long time ago and I don't have to bother with this anymore with the x800m2.
Maybe something changed in tsmuxer?

If you no longer use the x800m2, what do you use for DV?

[RESET_9999]

If you no longer use the x800m2, what do you use for DV?

I meant that I don't have to deal with the TS DV rip bugs(FF/RW on long movies or green screen) because the x800m2 does not have any of those problems.

but...
I will soon stop using my x800m2 though because if you haven't heard, the old UGOOS AM6plus is now stable with FEL, supports CMV4.0, and does true TV-LED.

[bbeny123]

I will soon stop using my x800m2 though because if you haven't heard, the old UGOOS AM6plus is now stable with FEL, supports CMV4.0, and does true TV-LED.

Let's assume that Ugoos AM6B Plus is stable with FEL - will it be better in terms of image quality than x800m2?

Does the x800m2 support CMv4.0?

[RESET_9999]

Let's assume that Ugoos AM6B Plus is stable with FEL - will it be better in terms of image quality than x800m2?

Does the x800m2 support CMv4.0?

Since it supports true tv-led, for cmv2.9 content it should be the same quality. I will do a direct comparison with the Shield, AppleTV, and X800m2 once I receive my Ugoos (early April, tracking says)
For cmv4.0 content, on the other hand, the ugoos should be better because cmv2.9 hardware/content have crushed black and cmv4.0 has better tone mapping.

The talk about the stable FEL build is happening here FYI:
https://discourse.coreelec.org/t/dolby- ... /24273/707