Hi,
It seems as though all the MEGA links higher up in the thread are down/have been removed.
does anybody have a link to the most recent CPM build?
Thanks in advance.
Hi,
It seems as though all the MEGA links higher up in the thread are down/have been removed.
does anybody have a link to the most recent CPM build?
Thanks in advance.
As far as I can tell, there are no Dolby Vision changes in this version. It’s mostly to experiment with fixing the broken VC-1 decoder. However, at this point, the fix results in only 12fps output for 24fps VC-1 videos.
can’t download.
did you delete the file?
you have new version.
it sounds maybe stupid, but can you T6A again online?
i am collecting some versions
ok, it’s up again, tell me when you download it so I remove.
you can take it down. i got it.
new links for
T7 https://www.mediafire.com/file/wpvz29ycr0is3ag/CoreELEC-cpm.v-T7.Amlogic-ng.arm-21.1.1-Omega_devel_20240915045212.T7.tar/file
Apologies if this is an ignorant comment, but is there any way we could filter out specific addons, or something like that? For instance, with SDR to DV conversion enabled, YouTube trailers only play audio with a black screen. Ideally, it would be great if they could be played without conversion, but all other SDR files would be converted
I’m now running the t7. thanks again cpm for all your work and everyone else for the testing and helping… UNBELIEVABLE!!!
by far the best picture quality come from an open source hobby project!! love and peace!!
one probably stupid question. but I’m not so into technical details… my tv, lg oled, runs dv and hdr10, not 10+.
I’m now converting a hdr10 and 10+ movie (without the +meta data as described) to dv. works perfect! tv dv picture mode jumps right in.
question, is the picture quality better than with my hdr10 mode?
I’m getting the benefit with sdr of course. Will try that.
but with hdr10 if the + data is not utilized anyway, is there a benefit?
ps, I’ve not changed any peak luminance or edid data, I’m 100% sure I would destroy something. and of course let’s say my both tv picture mode settings (dv and hdr) are identical …
thanks!!
Exactly what I was looking for. Thanks of that!
T8 version
Is the VS10 engine working in reverse too?
For us Samsung HDR10+ people.
DV to HDR10+ or DV to HDR10 signal?
DV plays fine on Samsung TVs no need to convert.
Really? It works perfectly on Samsung DVs? Yet they don’t list it as DV compatible, can you explain? Maybe thanks to AM6B+? Thank You
VS10 build enables VSVDB injection where you can input a custom payload.
Allows player led DV to be sent to HDR only TVs like Samsung.
Ah … OK …The music changes, but that’s clear.
sorry for the off topic
To add a bit more colour:
It does not convert DV metadata to HDR10+ metadata (i.e. metadata as processed by the TV - because I understand that is not possible - HDR10+ cannot fully replicate what DV can do, so cannot do a reasonable conversion)
So as liquidion says, instead we can set a Dolby VSVDB Payload in the Ugoos “on behalf” of the TV (which does not have one as not a DV TV), using that Dolby VSVDB the Ugoos then does the DV processing on the player as low latency dolby vision.
DV-LL (low latency dolby vision), is just an HDR signal pre-baked with the DV applied (FEL, RPU etc.), but have a 2nd problem the Samsung would likely read that as SDR as it does not know about “DV-LL”, so instead that signal is marked as HDR - hence the name Player Led (HDR).
The key point is the video data being sent to the TV in both: Player Led (DV-LL) and Player Led (HDR) is identical (just some signal type metadata changing)
VS10 can be set to DV → HDR10 but I removed it from the UI (only option is DV → SDR) because for the Ugoos it does not work correctly, that is what sent me down the Dolby VSVDB route to get a DV → HDR10 solution working otherwise would not have done it - what we have now is a better solution with more capability.
Allows for things like:
I didnt actually know the regular build did DV so thanks haha
About | FAQ | Terms of Service | Privacy Policy | Legal Notice