Aahhh… Thank you. 
Testing on a vero4k…looks like the LiveTV issues i was previously having are back:
Did not have these problems with the gmc builds. Will update that thread with logs etc.
Just updated my 4K no serious issues to report,
Aside from the 'stuttering on the PVR feed (already noted elsewhere).
Interestingly this only manifests its self on the TVHeadend feed. There is no stuttering when using the PVR feed from my Enigma 2 Satellite receiver.
Many thanks for all the hard work.
Me too for the moment it looks pretty solid. Almost disappointing !!!
I only had few errors that i think will not be part of normal use. Using my script to detect advert using comskip the CPU climbs to 100% and I found my TV waking up on its own.
And on installed the build defaulted to a low resolution. I could still go through menus to return to normal resolution.
Hoping to get emulators soon!!!
Yes, it does. This should improve with the next testing release.
So far so good on my Vero 2.
Resolution was normal on first boot.
No issues so far.
Seems more responsive ?
Look like the wait was worth it. (NO SURPRISE THERE)
Hurry up with that ATV Release ! Hehe 
A BIG Thanks to Sam and the rest of the OSMC team.
EDIT: I installed the Amazon VOD addon, and after widevine download/install. I had to manually install libnss3.so, libnssutil3.so, libnspr4.so.
I have been out of the loop for a long time, so I a,m not sure if the plan is to include those libraries in this version or the stable one, but I though you may want to know.
Just updated my RPi 3 to the release candidate. No issues with the update process. Testing out a few things to check everything still works as before.
Thanks Sam and the OSMC team.
Those dependencies are for libwidvine and were part of gmc’s nightlys, but wasn’t on 18.2-rc1, should be in rc2.
1 Like
Just updated the Pi again, the missing audio option to include LFE in the downmix is now there, but the center channel boost option is still missing. Is that on the to-do list for the official release?
I couldn’t switch to estuary skin
kodi .log:
http://paste.osmc.tv/ujinidewib
2019-04-20 12:58:33.352 T:1351443168 DEBUG: script.skinshortcuts: Failed to write menu
2019-04-20 12:58:33.352 T:1351443168 ERROR: Traceback (most recent call last):
2019-04-20 12:58:33.353 T:1351443168 ERROR: File “/home/osmc/.kodi/addons/script.skinshortcuts/resources/lib/xmlfunctions.py”, line 97, in buildMenu
2019-04-20 12:58:33.353 T:1351443168 ERROR: self.writexml( profilelist, mainmenuID, groups, numLevels, buildMode, progress, options, minitems )
2019-04-20 12:58:33.353 T:1351443168 ERROR: File “/home/osmc/.kodi/addons/script.skinshortcuts/resources/lib/xmlfunctions.py”, line 680, in writexml
2019-04-20 12:58:33.353 T:1351443168 ERROR: tree.write( path, encoding=“UTF-8” )
2019-04-20 12:58:33.353 T:1351443168 ERROR: File “/usr/lib/python2.7/xml/etree/ElementTree.py”, line 802, in write
2019-04-20 12:58:33.353 T:1351443168 ERROR: file = open(file_or_filename, “wb”)
2019-04-20 12:58:33.353 T:1351443168 ERROR: IOError: [Errno 13] Permission denied: u’/usr/share/kodi/addons/skin.estuary/xml/script-skinshortcuts-includes.xml’
After I created the script-skinshortcuts-includes.xml file, it worked…
sudo touch usr/share/kodi/addons/skin.estuary/xml/script-skinshortcuts-includes.xml
sudo chmod 777 /usr/share/kodi/addons/skin.estuary/xml/script-skinshortcuts-includes.xml
I’ve pushed update builds. See original post for a changelog.
I had a video I was playing back suddenly stop, followed by a sad face. After which the resolution was no longer 1080p. When I went into settings to fix that, the resolution changed several times, and each time, asked me if I wanted to keep the new resolution. (I had not even seen the system settings page I was trying to access at this point). After declining all the offers to keep the new resolution, the display settings page was finally shown, but resolution entry was dimmed out. I chose to reboot, and was happily back to normal - my TV’s OSD confirmed 1080p 30bit when the OSMC GUI came up.
Other than that (and the resolution being skew-whiff immediately after upgrade) I have experienced no problems not associated with add-ons.
Thanks for your efforts with this.
What device are you using?
Can you please send us a debug log if this happens again?
So I had this:
deb Index of /osmc/osmc/download/dev/gmc-19/public gmc-19 main
in sources.list but when I look in system, it was still saying 18.2
I commented the above out and added deb http://apt.osmc.tv stretch-devel main and did an update in OSMC and it has now updated OSMC from the December build to April 1 build.
executing: dpkg -l | grep mediacenter-osmc | awk ‘{ print $3 }’
returns: 18.8-23
Am I now back on ‘official releases’ again? Is there anything else I need do? I only went on nightlies because a streaming app required Kodi Leia.
osmc@osmc_vero4:~$ grep Kodi .kodi/temp/kodi.log | head -3
2019-04-21 16:37:03.823 T:4067614720 NOTICE: Starting Kodi (18.2-RC1). Platform: Linux ARM (Thumb) 32-bit
2019-04-21 16:37:03.823 T:4067614720 NOTICE: Using Release Kodi x32 build (version for Vero)
2019-04-21 16:37:03.823 T:4067614720 NOTICE: Kodi compiled 2019-04-11 by GCC 6.3.0 for Linux ARM (Thumb) 32-bit version 4.9.110 (264558)
osmc@osmc_vero4:~$ grep VERSION_ID /etc/os-release
VERSION_ID=“2019.04-1”
osmc@osmc_vero4:~$
Just another thing I just stumbled across (not sure if this is actually a bug or intended behaviour):
I whitelisted 720p (max I get from IPTV over here) resolutions only but set Kodi output resolution to 1080p60. When watching a movie Vero sets output to 1080p60 as well - should this not be 720p at max? I think it used to - but not sure. Is there some kind of auto-whitelisting happening?
You are pointing to the nightly builds so you are on a higher version now than Sam’s release builds.
returns: 18.8-23
Is the nightly 18.2RC1 version
The latest “official” test build from Sam is 18.2.0-4 (As you are 18.8.x you will not automatically get these)
To go back to the official releases comment out the gmc-19 line in the sources.list and run a
sudo apt-get update
You will then need to force a downgrade
sudo apt-get install vero3-mediacenter-osmc=18.2.0-4
When the stable release is released you can then upgrade:
sudo apt-get update && sudo apt-get dist-upgrade
Of course you will need to be on “stretch-devel main” branch otherwise you will not be able to install the test release. (Otherwise if you stay on “stretch main” then you will need to downgrade to the stable when its released.
Have you enabled “Adjust Refresh Rate”?
I just tried it with a 576p video and it worked.
Still on for release today 3pm ET? will schedule a backup right before the upgrade 
There is a huge amount of music-related improvements in Leia that I’ve been looking forward to for a very long time for my RPi/OSMC-based music server. Thanks Sam & team for the years supporting kodi 17
1 Like
Just double checked it and yes, Adjust Refresh Rate is (and was) enabled
Kodi v18 has now been released: OSMC's Easter update is here with Kodi v18 (Leia) - OSMC
Thanks for those that tested either these builds or @gmc builds.
Sam