Ok Sam, I will be attentive to updates.
If you have a PC, use madVR for 4K HDR to SDR tone mapping.
I don´t have madVR, i use Nvidia Shield.
Chatter about this seems to have died down, does that mean most of the issues have been resolved or the initial cusp of space monkeys are on the moon now?
I think I speak for nearly everyone when I say “huh?”
Hey, also you can contribute in testing and you should if you have testing kernel installed, otherwise you can go with stable 3.14 kernel. Thats my two cents
Space monkeys were one of the first living creatures to be literally shot into space as pioneers to test whether it was viable to then send humans
I’ll be damned. I thought Laika was the first animal in space but you’re right, the US sent monkeys in to space several years before.
Back to the topic: there are still a lot of issues in 4.9 that prevent it from being ready for prime time. The more testers the merrier though. Take a backup via My OSMC. If things don’t work well for you, a reinstall won’t take too long.
Yeah that’s what I meant, there seemed to be less talk so less issues so I was more likely to rebuild my Vero4k as new with this and help out
Thanks for the effort on this upgrade .
Some feedback -
I have tested this extensively with High Res Music files up to 192khz and Flac 5.1 music files and I am please to say that everything is working well . I did have one instance where gapless playback stopped working but a reboot sorted this out …this happened occasionally with the current 3.14 as well though.
I am having one issue where the interface is sometimes only showing 1280 * 720 as an available resolution , a reboot is fixing this and displaying all available resolutions . Also lock HDMI HPD is defaulting to on even after turning it on and rebooting - is this normal ?
My setup is VERO connected to Integra AVR connected to Sony OLED .
What logs / files do I need to check to diagnose what is going on with the resolution issue ?
Hi there… Anyone know what I’m doing wrong regarding updating - i.e. sudo apt-get update ?
This worked the other day, now all of a sudden not working (unless this is a temporary server issue):
Get:1 http://security.debian.org buster/updates InRelease [65.4 kB]
Hit:2 Index of /debian buster InRelease
Get:5 Index of /debian buster-updates InRelease [51.9 kB]
Hit:3 Index of /osmc/osmc/apt buster InRelease
Hit:4 Index of /osmc/osmc/apt videoimprovevero49 InRelease
Reading package lists… Done
E: Release file for http://security.debian.org/dists/buster/updates/InRelease is not valid yet (invalid for another 2860d 7h 26min 19s). Updates for this repository will not be applied.
E: Release file for http://ftp.debian.org/debian/dists/buster/InRelease is not valid yet (invalid for another 2823d 23h 59min 20s). Updates for this repository will not be applied.
E: Release file for http://ftp.debian.org/debian/dists/buster-updates/InRelease is not valid yet (invalid for another 2861d 10h 38min 24s). Updates for this repository will not be applied.
E: Release file for http://apt.osmc.tv/dists/buster/InRelease is not valid yet (invalid for another 2847d 5h 1min 50s). Updates for this repository will not be applied.
E: Release file for http://apt.osmc.tv/dists/videoimprovevero49/InRelease is not valid yet (invalid for another 2845d 14h 18min 12s). Updates for this repository will not be applied.
Thanks in advance!
Note, sources are per those given on thread 1.
Hi,
have you checked the date and time on the device, looks like it may be quite a bit out? Have you tried rebooting, as long as you have internet the http-time service should correct the time and date.
Thanks Tom.
It’s a bug in tzdata, manually correct your date and time then the update will run and a new version of tzdata will be installed
@Tom_Doyle @spl147 - Thanks guys!
Did a reboot, and update ran fine (…slapping my head moment!)
Cheers,
Jez
None of my devices running Debian Buster have had such an error.
Can you point us to the bug report?
Anyone else experiencing an occasional green screen after seeking with HDR material?
Yes, several other people including myself posted about this. Please take a look at this post how to report this to the developers.
After the decoder gets into this state only a reboot can get it back to normal again.