Looks like ffmpeg doesn't support dvh1 codec in mkv.
Try something like:
Code: Select all
ffmpeg -i dvh1.mp4 -c copy -vtag dvhe dvhe.mkv
Looks like ffmpeg doesn't support dvh1 codec in mkv.
Code: Select all
ffmpeg -i dvh1.mp4 -c copy -vtag dvhe dvhe.mkv
Try using mkvtoolnixsw5163 wrote: ↑Fri Mar 08, 2024 2:23 amLooks like ffmpeg doesn't support dvh1 codec in mkv.
Try something like:I don't know if the mkv will play proper Dolby Vision though.Code: Select all
ffmpeg -i dvh1.mp4 -c copy -vtag dvhe dvhe.mkv
This worked! I didn't realize MKVToolNix could open files other than MKV, but sure enough it can!
Hi again @RESET_9999!RESET_9999 wrote: ↑Wed Jan 24, 2024 7:47 pmNo , it sounds right but you should try DV MKV with kodi on your C2, it works great on my end (PGS and SRT).
https://kodi.wiki/view/HOW-TO:Install_Kodi_for_webOS
no ideatjreis2 wrote: ↑Sun Mar 10, 2024 12:11 am
Hi again @RESET_9999!
I followed your advice and installed Kodi in the my C2 but im having some problems regarding the resolution and refresh rate options in the app..
In the display settings, only the 1920x1080p resolution is available, and in the whitelist options it only shows 1 available (1920x1080, 0Hz). When i playback some movies, i managed to get DV but the refresh rate doesnt switch, even though i turned on that setting in the player. Using the player info, i can see that it reads correctly the video stream (4k) but the screen information says 1080p and 60hz. It doesnt seem like an error because the movie is looking a bit blurry indeed..
yesAre you able to get 4k resolution and 24hz refresh rate in your setup?
yes, im connected to an AVR too via ARCwas via webos dev manager?
Code: Select all
Summary:
Frames: 147321
Profile: 8
DM version: 1 (CM v2.9)
Scene/shot count: 1630
RPU mastering display: 0.0020/1000 nits
RPU content light level (L1): MaxCLL: 10000.00 nits, MaxFALL: 892.53 nits
L6 metadata
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 1000 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 372 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 347 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 471 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 592 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 532 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 835 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 767 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 179 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 709 nits, MaxFALL: 121 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 598 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 561 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 606 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 467 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 983 nits
Mastering display: 0.0020/1000 nits. MaxCLL: 1000 nits, MaxFALL: 400 nits
L2 trims: 1000 nits, 100 nits, 600 nits
L5: Left=0, Right=0, Top=276, Bottom=276
Any thoughts on this guys? RESET_9999?gm23o wrote: ↑Sun Mar 10, 2024 5:20 pmHi,
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?
gm23o wrote: ↑Wed Mar 13, 2024 9:20 amAny thoughts on this guys? RESET_9999?gm23o wrote: ↑Sun Mar 10, 2024 5:20 pmHi,
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?
RESET_9999 wrote: ↑Tue Feb 13, 2024 1:43 pmplease ask any further questions related to the dovi_scripts here: https://forum.doom9.org/showthread.php? ... ost1997616
thanks.
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...PlatypusW wrote: ↑Sat Dec 05, 2020 7:17 pmYes but that isn't enough for meRESET_9999 wrote: ↑Sat Dec 05, 2020 4:09 pmI 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
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
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.croweyes1121 wrote: ↑Wed Mar 20, 2024 1:37 pm
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...