Re: Dolby Vision and 1.15.1
Posted: Thu Jul 23, 2020 10:13 pm
Impressive. Most impressive!
Great! If you need help with GitHub, let me know. It's really not that bad once you get the hang of it.yusesope wrote: ↑Thu Jul 23, 2020 9:16 pmHello beautiful people!
Just a small update: I revised my code (Exoplayer) after the release of version 1.15.2.
@shawnc22 has just tested (on the new Shield) an apk that i have prepared.
The mkv test file is played correctly and Dolby Vision is successfully triggered.
In the next few days I will release a test version of my apk here on the forum.
At the same time I will try to understand how the h e l l GitHub works in order to be able to review the code together with @shawnc22 and @steffenmanden and present the finished work to the Exoplayer team.
Yusecope has mentioned in the past that he thinks when the Shield decoder encounters an unsupported profile (7 in this case), it will look at the raw video stream and fallback to a similar supported profile for playback. From testing with TS files in the past, the same video stream when stored as either 4 (supported), or 6/7 (unsupported) all work without issue and produces the same image. The mkv's I've tried so far from 1.15.1 and 1.15.2 all have worked despite being labeled as profile 7, so it does seem like profile labeling is not that important as far as the Shield is concerned. Now that @RESET_9999 has found a workaround for the red push issue, the last bit of mystery is to just determine what exact the Shield is doing when playing FEL titlesSamuriHL wrote: ↑Fri Jul 24, 2020 12:51 amI have a SHIELD question. When I made all my TS files I made them profile 4. Now MakeMKV is ripping them to profile 7. Is the SHIELD going to be able to play those?
EDIT:
What I mean is this....
ts: Dolby Vision, Version 1.0, dvhe.04.06, BL+EL+RPU
mkv: Codec: MpegH HEVC Main10@L5.1 (dvhe.07.06 BL+EL+RPU FEL)
Excellent. I'm hoping FEL "accidentally works" even though we know it's not supposed to be supported. And yes, REST_9999's solution worked for me, as well, so, I'm just waiting for a player. I'm reripping a bunch of titles right now as we speak. It's very nice to have rip lock begone(tm). I got 2 NS60's going right now. Fantastic!shawnc22 wrote: ↑Fri Jul 24, 2020 1:11 am
Yusecope has mentioned in the past that he thinks when the Shield decoder encounters an unsupported profile (7 in this case), it will look at the raw video stream and fallback to a similar supported profile for playback. From testing with TS files in the past, the same video stream when stored as either 4 (supported), or 6/7 (unsupported) all work without issue and produces the same image. The mkv's I've tried so far from 1.15.1 and 1.15.2 all have worked despite being labeled as profile 7, so it does seem like profile labeling is not that important as far as the Shield is concerned. Now that @RESET_9999 has found a workaround for the red push issue, the last bit of mystery is to just determine what exact the Shield is doing when playing FEL titles
Have all my decrypted backups still so no torturing of my drives needed this time aroundSamuriHL wrote: ↑Fri Jul 24, 2020 1:15 amExcellent. I'm hoping FEL "accidentally works" even though we know it's not supposed to be supported. And yes, REST_9999's solution worked for me, as well, so, I'm just waiting for a player. I'm reripping a bunch of titles right now as we speak. It's very nice to have rip lock begone(tm). I got 2 NS60's going right now. Fantastic!
Just to be clear, and sure i'm not missing anything: RESET_9990s solution for red push involves buing a vertex right?SamuriHL wrote: ↑Fri Jul 24, 2020 1:15 amExcellent. I'm hoping FEL "accidentally works" even though we know it's not supposed to be supported. And yes, REST_9999's solution worked for me, as well, so, I'm just waiting for a player. I'm reripping a bunch of titles right now as we speak. It's very nice to have rip lock begone(tm). I got 2 NS60's going right now. Fantastic!shawnc22 wrote: ↑Fri Jul 24, 2020 1:11 am
Yusecope has mentioned in the past that he thinks when the Shield decoder encounters an unsupported profile (7 in this case), it will look at the raw video stream and fallback to a similar supported profile for playback. From testing with TS files in the past, the same video stream when stored as either 4 (supported), or 6/7 (unsupported) all work without issue and produces the same image. The mkv's I've tried so far from 1.15.1 and 1.15.2 all have worked despite being labeled as profile 7, so it does seem like profile labeling is not that important as far as the Shield is concerned. Now that @RESET_9999 has found a workaround for the red push issue, the last bit of mystery is to just determine what exact the Shield is doing when playing FEL titles
I wasn't as smart. And it IS torturing my drives. I keep forgetting these discs don't age well and every time I have to pull them off the shelf they get harder and harder to read. I just don't have the space to store them all as ISO's, even temporarily til we get the DV situation sorted out. So here I am, ripping away. LOL I had to throttle the NS60's a bit. I'm still learning where the sweet spot is with these things.
That is great news, yusesope!yusesope wrote: ↑Thu Jul 23, 2020 9:16 pmHello beautiful people!
Just a small update: I revised my code (Exoplayer) after the release of version 1.15.2.
@shawnc22 has just tested (on the new Shield) an apk that i have prepared.
The mkv test file is played correctly and Dolby Vision is successfully triggered.
In the next few days I will release a test version of my apk here on the forum.
At the same time I will try to understand how the h e l l GitHub works in order to be able to review the code together with @shawnc22 and @steffenmanden and present the finished work to the Exoplayer team.