Just ordered my Vero V and I’m very excited. A bit ignorantly, I began transcoding my entire library into AV1 a week or so ago, DV files included, to save on space without checking if any device I own can actually play Profile 10. (They cannot)
I saw the Vero V supports Profile 10 playback and jumped at the opportunity to grab one. My sole question is am I going to have to update it to a beta/test firmware for profile 10 support, or is it going to be supported by the current stable OSMC firmware?
Either way, awesome stuff to cover that base when practically no one else out there does right now.
DV profile 10 is supported. But I’m wondering what you ended up with transcoding Profile 5 or Profile 7 into AV1. Profile 10 is a single-layer format so the beta isn’t relevant and so far we haven’t come across any AV1 files with compatibility ID 0 (as used in P5).
I suppose I’ll just have to test them out after I receive the Vero V and see if it works. Worst case I still have the original files and a nice new media player.
I used rigaya’s QSVEnc with a couple of Arc A380s and have ran more than a few files through them. All Dolby Vision files have retained their relevant DV and HDR metadata after conversion to AV1 and on paper everything looks right. The only device I have right now that would work with real-world test methods is a Windows laptop that can’t seem to trigger DV on my TV regardless of the content I’m testing it with.
Edit: DV Profile 10.1 on all transcoded files I can find. Doesn’t seem like I have any with compatibility ID 0.
Ran a test on profile 5 since it naturally has no HDR fallback. Judging by metadata alone QSVEnc properly tone-maps and converts profile 5 to profile 10.1 to give it the HDR compatibility layer. I’ll have to see how the test goes on that tonight to ensure the file at least plays HDR correctly but results from QSVEnc are very promising. I’ll update again when I find out if my converted DV files play properly on the V in case anyone else is curious.