spaced wrote: ↑Sat Oct 03, 2020 11:40 pm
Great new release, seems to run a bit smoother on some discs I was having trouble with as well as a bit faster I think? Ford v Ferarri currently ripping @ 3.3x on WH14NS40 modded 1.04 firmware in a Mercury Pro bay direct connect to Mobo. Before I was lucky to get 2ish
So I understand, this new version still won't magically make DV/Atmos Mkvs read DV in plex via shield pro 2019 because that's still on Plex? I will continue to use tsmuxer 04.06 to get that to work?
Maybe this will fix the issue I was having on a few DV movies that were stubborn and wouldn't apply DV/Atmos with the above method. For me the troubled ones were Spectre, Skyfall, Braveheart which I read up a bunch on the forums that these were problematic for others to get DV to recognize on Plex/Shield Pro 2019 after doing the proper steps.
Also, first post, so hello to all fellow ripping nerds, I am still fairly new to this wild west of tech, I do come from a fairly technical background, just not this specifically. Been using MakeMKV for about a year now, purchased a key after it did so much for me and my UHDs.
Hey there fellow new ripper! Did anyone ever respond to you on this? I'm in the same boat; my previous and currently working workflow is MakeMKV 1.15.2 --> eac3to to extract ac3+thd --> tsmuxer to mux the MKV and extracted Audio into a .ts. Then the .ts plays in DV+Atmos streaming from Plex server to Nvidia Shield TV 2019 hooked up to Sony A8G (DV profile 5 only). Wondering if anyone can help with these questions:
1. Does my workflow change with the 1.15.3 update? If the end goal is DV+Atmos through Nvidia Shield TV Plex?
2. Are there pros/cons of having a library full of .ts vs .mkv saves? The .ts method seems to be working, so ya know if it ain't broke, why convert everything to .mkv?
3. What's going on with the DV profiles? I've been hearing that Sony Bravia is only compatible with DV Profile 5 but I have several .ts that show up as
Dolby Vision, Version 1.0, dvhe.04.06, BL+EL+RPU, Blu-ray compatible from the aforementioned workflow that trigger DV through Plex. So first question is: is my intuition right that "dvhe.04.06" means DV Profile 4 and/or Profile 6 (i.e not Profile 5)? And if so, how does it work nonetheless in my setup? The Shield is doing something to ensure compatibility between the source file Profile and the output Profile?