February 28, 2022 at 6:01 AM #9843
Screenshot (IMGBB): https://ibb.co/M6MJ71p
PCM 5.1 Upmixed from isolated tracks from the textless split.
ProRes 422 HQ, (MEGA): https://mega.nz/file/9eA2kT5K#VdD7FxeMqRE9pUh36hcMjINNDbrzIrbCyR87cAE8iFIMarch 2, 2022 at 8:01 PM #9852
I already tinkered with this and got a nice 4GB H265 with DTS-HD MA 5.1 working on my Oppo-203.
Not that you encoder guys tell anyone what player your encoding for. But for the rest of the public, now you know.March 17, 2022 at 7:49 PM #9898
An OPPO-203 shouldn’t have issues playing this file back unless they’re picky about encode parameters, although, I’m unsure what hardware the 203 uses to decode 4K Blu-ray.
Do you mind sharing what settings you used to encode this 4GB file?
Also, I encode with mostly HTPCs in mind. I don’t tune my encodes to play the best on any specific hardware player, however, a 50mbps, 1080p, HEVC stream should be a walk in the park for media players that can decode 4K Blu-ray considering that 4K Blu-ray uses a higher resolution and bit-rate unless it is running into the issue.
What issue are you having?March 19, 2022 at 9:04 PM #9910
if my memory is correct….?
Using the ProRes 422 HQ file:
I used Handbrake 1.4.2 on my Mac mini M1 (2020) Arm on MacOS 11.6.3.
I might not recall the exact settings in handbrake….?
I did two high bit rate encodes. 1 at Average bite rate 80000kbps and one over that, maybe at 1000000kbps.
I kept the higher bite rate one which is variblae at 100-210Mbps. Plays fine on my Oppo-203 as an mkv container.
I used eac3toGUI to demux the 5.1 PCM into 6 mono wave files and ran it in DTS-HD Master Audio Suite 2.60.22 for Blu-ray spec DTS-HD MA 5.1.
My Oppo-203 reports back with a pop-up “File is not supported” for:
Remuxing JurassicWorldDominion_T1_TXTD_H.265.mkv in MKVToolNix with no compression on the video and audio tracks gives me a corrupted video track and no audio and a possible freeze of my Oppo-203. It looks like the end credits to Blade Runner 2049. Doing the same for the ProRes still gives me the pop up “File not supported”.
Ive seen two encoders here and on movie-list also put out trailers with similar issues along with the LPCM SL24 xxx something on the audio tracks of the trailers and that comes out as static sound on my Oppo-203. I would guess that’s not up to Blu-ray/4K UHD Blu-ray White papers spec.
If you guys are using the DCP packages, you have to unwrap/extract and or convert the video or audio tracks. Unless DCP packages and its DCI and Interop and SMTPE, showvault and so on has change dramatically since I left back in 2015 from the theatrical exhibition of Digital Cinemas. BTW, I started in the early days of a theatre going from 35mm to Digital in 2009. I hope this helps.April 14, 2022 at 7:20 PM #9969
I believe I’ve found the issues, although, I do not own an OPPO-203 to test my encodes.
I think the source of the problems is that since I left the extra compression setting in MKVToolNix to “Determine
automatically” last time I think it chose to add extra compression, therefore, giving the “File is not supported” message that you’ve described.
I’ve also repackaged the stereo PCM data into a .wav file and then muxed that with the video tracks because previously
I was muxing the PCM track directly from the ProRes master that comes from the studio for the press. I believe that the
format that it was in was causing the white noise like audio on the stereo track which I was also able to recreate through my media player hence ruling this out as an issue specifically with the OPPO-203. The OPPO should have no problem decoding PCM because the OPPO supports standard Blu-ray which also supports PCM.
The ProRes mux contains the original ProRes track that I sourced from the electronic press kit site EPK TV.
This means that I did not encode this track because it was encoded by the studio, therefore, the problem is not that the video encoding is bad, it’s that
the OPPO doesn’t support data compression or at least that’s why I’ve hypothesized because I cannot find information on whether the OPPO supports data compression or not.
My next post will have the things I’ve mentioned fixed.
I hope this fixes the issues with the 203 and other players that may have a similar issue.
I will also factor in hardware that can’t decode HEVC by providing an AVC encode for 1080p trailers.April 20, 2022 at 7:05 PM #10005
huh.. took weeks to reply.. ok. smh.
same BS goes for Tap Gun maverick Trailer C 4k HEVC. Maybe you guys should at least own a Blu-ray standalone player.April 21, 2022 at 9:23 AM #10007dragonmcmxModerator
@axledentaldj There’s no need for this kind of attitude. Not all of us have the time, ability or resources to tailor every single upload to your specific needs. So instead of making unrealistic demands, you could be grateful that these materials are freely available at all, and if they don’t work for you, you’re welcome to take our files and re-encode them yourself to whatever format best suits your needs.April 21, 2022 at 7:46 PM #10011
Oh, I’m just being honest. Yes, it was a little rude. But I’m tired of some of the BS. I think I know who tapped me on movie-list forum to pick my brain for help. I gave it and I saw nothing. Take it or leave and yes, if I have to, I’ll re-encode it myself. Specific needs or not. Im just using a manufactured Oppo-203 Universal Blu-ray player. Sure its got the Free RU JB. I might even been doing this before you.
- You must be logged in to reply to this topic.