Is there someone else experiencing slightly raised blacks when playing DV content? For me, whenever i play DV from my AM6+ on my LG C7 and lets say on cuts, where all gets black, the picture isn´t completely black, it even seems there are some minor elevated spots which aren´t complete black. Very weird, but it´s in all DV related content i´ve watched so far. Latest nightly build, nothing changed but relevant settings for playing DV and have installed another skin (thx jurialmonkey for great skins).
Deep color on TV is activated
TV shows DV on playback
TV-led enabled in options
AVR just passthrough´s the image
on playback information´s screen its shows:
EOTF and colorspace / pixel format:
8 bit, RGB unknown DV. Std BT.709
This should be normal as it just “sees” the wrapper in which DV info is embedded?
It’s a known issue with LG TVs and Dolby Vision. Try the white-balance RGB trick: -1 / –1 / –1 (or even more if needed). You can usethis file to test the adjustments.
My old C8 needed –3, and the C2 needed –1. The G5 is my first OLED TV with proper blacks in DV without any adjustments.
Just asking out of curiosity, what do you watch on LG G5 to take advantage of it’s high brightness? I know that it has highest LG OLED brightness today, but most movies coming out last couple of years, even blockbusters, are mastered with (very) low nits 200-300 only. So what to watch with such an expencive TV to take advantage of its high nits posibilities, old movies?
Also, bright TVs benefit the most from FEL DV Blu-rays, which can restore 4000+ nits of brightness, whereas the HDR10 base layer is capped at 600 or 1000 nits.
Does anyone else have problems playing DV MP4 files? They just hang immediately for me. If I extend video cache to crazy numbers I can delay it for a few minutes but it still inevitably hangs. MKV never had any issues.
You can download the coreelec-no general installer or the coreelec-no nightly installer and search the archive for the required .dtb file for your device. If it’s there, installation is possible.
I’m sorry if this is a dumb Q. but I’ve heard a few people mention they have installed this latest build on their Ugoo AM6B+. Does the new Piers Beta build include DV FEL for AM6B+? Or is still a case of using the old Omega 2.x.x setup? If so, I understand that is no longer supported on here, so I guess I’m asking is there any kind of new update or alternative available for my AM6B+ whilst retaining FEL DV playback please? I’ve been searching the net. for hours and haven’t been able to find a clear answer, so I thought I’d just ask here. Many thanks to anyone who knows.
fresh install + dovi.ko from the linked thread, no weird stuff
if it doesn’t work “out of the box” then just make sure dovi is installed correctly
maybe browse settings but i don’t recall anything specific
i just installed it and the dovi.ko then it worked
So, I put all the files correctly on a USB stick, reset the device, it went into ‘upgrade mode’, everything looked good. I set all my settings, turned off the box, removed the USB stick, and it reloaded in the old Coreelec build. I put the USB back in and reset it and it started again with the new build.
I thought the upgrade would automatically install the new firmware to the box’s internal HD, but it has not, it runs it from the USB. I want to install the new build over my old one on the HD. I even went back to the old SSH method, but eemc came back with this error.
Please choose one option? [1/2/3/4/5/6/7]: 1
Free space of ‘partition CE_FLASH’: 512MB
Warning: Could not find ‘dto’ partition!
Could not find ‘CE_STORAGE’ partition!
Failed to read size of partition ‘CE_STORAGE’!
Failed to create new partition table!
I read this could be a USB size issue, but I used to flash tool and it automatically partitioned the USB stick to be small (just enough for the programme) as suggested in various guides, and this method has worked for me before. Can someone please point me in the right direction?
Thanks for the help guys. I figured it out. In case anyone else is struggling with this - I had to boot up using the new firmware via USB, then I had to SSH into the drive (found ip address via angry ip scanner), then used putty to log in, THEN I had the full options menu, selected 7 to remove existing dual boot, then selected 1 to install the new dual boot, and… it works! Many thanks for the help again
Can I just do it as a fresh install and use it as is, or do I need to tweak/add anything else, like a custom .tar via ssh, etc?