@tiroy no not that option, the one I mentioned.
It changes the output to match the video that you’re playing, it gets rid of juddering when using sources with different frame rates.
Regardless, it’s not working for me.
@tiroy no not that option, the one I mentioned.
It changes the output to match the video that you’re playing, it gets rid of juddering when using sources with different frame rates.
Regardless, it’s not working for me.
If anyone’s wondering why the ‘adjust refresh rate’ option isn’t working, there’s a new feature in system - display called whitelist…select which refresh rates and resolutions you want supported and then the adjustment will happen when you start playback, it’s pretty cool as it switches both the resolution and refresh rate.
It works well with 24/25/60 fps content but I think there’s a slight problem with it, as when using the OSMC tvb-d stick through TVHE, it switches the refresh rate to 25 fps, but should switch to 50.
Maybe I’m missing something here.
17.8-245, 12 June 2018: Based off OSMC commit (183500893d) and newclock5 (97e11fe6)
XBMC:
inputstream.adaptive:
pvr.zattoo:
newclock5:
New commits in this build:
Commits no longer in build:
Includes latest addons:
inputstream.adaptive (27ddff1,2),inputstream.rtmp (b8e3f39), peripheral.joystick (6312745), pvr.argustv (37a3a76), pvr.demo(bcd8289), pvr.dvblink (1732e4b), pvr.dvbviewer (986b1ba), pvr.filmon (ba261c9), pvr.hdhomerun (379c62c), pvr.hts (f569808), pvr.iptvsimple (663040c), pvr.mediaportal.tvserver (01af5a0), pvr.mythtv (c18ca9e), pvr.nextpvr (fad3ca9), pvr.njoy (30743c6), pvr.octonet (1e44819), pvr.pctv (d0c7241), pvr.stalker(00f3fc4), pvr.teleboy (dfa68b0), pvr.vbox (d2e61a9), pvr.vdr.vnsi (18c7474), pvr.vuplus (bcfd34d), pvr.wmc (ce4b47a), pvr.zattoo (286ce5f, +1), vfs.libarchive(84a4876)
OK finished the movie and while scanning the library it crashed again. Another note is the IP address has changed for my Pi 3 times from 10.0.0.163 to 10.0.0.164 to 10.0.0.32 all in about hour of testing.
https://paste.osmc.tv/vofamiyazu
Some weird network issues you are having.
12 18:12:40 osmc avahi-daemon[259]: Host name conflict, retrying with osmc-3
Do you have another device with the same name? Is wifi and lan both connected at the same time?
Something is causing your IP to be knocked off the network and then your DHCP Server issues a different IP Address. The lease should be long enough that it issues the same address so have a look at your DHCP server too.
I have 4 Raspberry’s all with OSMC and the same name on the network
I’d advice you change the name of each device: like osmc1, osmc2 or something like the seven dwarfs of snowwihte. Anything that makes em uniqe.
Here is how to do it in ssh:
Ok changed everybody to a name unique to the room ! Let the testing begin ! Thanks guys !
17.8-246, 13 June 2018: Based off OSMC commit (c77366e3b) and newclock5 (a47b98b)
XBMC:
inputstream.adaptive:
pvr.zattoo:
newclock5:
Commits no longer in build:
Includes latest addons: inputstream.adaptive (4705d59, +4), inputstream.rtmp (b8e3f39), peripheral.joystick (6312745), pvr.argustv (37a3a76), pvr.demo(bcd8289), pvr.dvblink (1732e4b), pvr.dvbviewer (986b1ba), pvr.filmon (ba261c9), pvr.hdhomerun (379c62c), pvr.hts (f569808), pvr.iptvsimple (663040c), pvr.mediaportal.tvserver (01af5a0), pvr.mythtv (c18ca9e), pvr.nextpvr (fad3ca9), pvr.njoy (30743c6), pvr.octonet (1e44819), pvr.pctv (d0c7241), pvr.stalker(00f3fc4), pvr.teleboy (dfa68b0), pvr.vbox (d2e61a9), pvr.vdr.vnsi (18c7474), pvr.vuplus (bcfd34d), pvr.wmc (ce4b47a), pvr.zattoo (e72598d, +2), vfs.libarchive(84a4876)
Using the new 8-246 watching Cable TV with HDhomerun channel was using the wrong audio. It was using the handicap audio. After awhile the channel dropped off back to home screen. https://paste.osmc.tv/xosavulamu
17.8-247, 14 June 2018: Based off OSMC commit (4e5de7fd) and newclock5 (2a225662)
XBMC:
inputstream.adaptive:
Includes latest addons: inputstream.adaptive (5756133, +6), inputstream.rtmp (b8e3f39), peripheral.joystick (6312745), pvr.argustv (37a3a76), pvr.demo(bcd8289), pvr.dvblink (1732e4b), pvr.dvbviewer (986b1ba), pvr.filmon (ba261c9), pvr.hdhomerun (379c62c), pvr.hts (f569808), pvr.iptvsimple (663040c), pvr.mediaportal.tvserver (01af5a0), pvr.mythtv (c18ca9e), pvr.nextpvr (fad3ca9), pvr.njoy (30743c6), pvr.octonet (1e44819), pvr.pctv (d0c7241), pvr.stalker(00f3fc4), pvr.teleboy (dfa68b0), pvr.vbox (d2e61a9), pvr.vdr.vnsi (18c7474), pvr.vuplus (bcfd34d), pvr.wmc (ce4b47a), pvr.zattoo (e72598d, +2), vfs.libarchive(84a4876)
17.8-248, 15 June 2018: Based off OSMC commit (a3155aa4) and newclock5 (2a225662)
XBMC:
pvr.dvbviewer:
Includes latest addons: inputstream.adaptive (5756133, +6), inputstream.rtmp (b8e3f39), peripheral.joystick (6312745), pvr.argustv (37a3a76), pvr.demo (bcd8289), pvr.dvblink (1732e4b), pvr.dvbviewer (f01e52c, +19), pvr.filmon (ba261c9), pvr.hdhomerun (379c62c), pvr.hts (f569808), pvr.iptvsimple (663040c), pvr.mediaportal.tvserver (01af5a0), pvr.mythtv (c18ca9e), pvr.nextpvr (fad3ca9), pvr.njoy (30743c6), pvr.octonet (1e44819), pvr.pctv (d0c7241), pvr.stalker (00f3fc4), pvr.teleboy (dfa68b0), pvr.vbox (d2e61a9), pvr.vdr.vnsi (18c7474), pvr.vuplus (bcfd34d), pvr.wmc (ce4b47a), pvr.zattoo (e72598d, +2), vfs.libarchive (84a4876)
Jun 15 18:30:00 osmc-18test mediacenter[293]: /usr/bin/mediacenter: line 142: 358 Segmentation fault sudo -u osmc $KODI --standalone -fs --lircdev
Don’t see any reason for this, also can’t replicate on the 4k. Will try a test on the Pi.
Can you try the latest version (249). Should be up within the hour.
17.8-249, 16 June 2018: Based off OSMC commit (72de2ea3) and newclock5 (2a225662)
XBMC:
Includes latest addons: inputstream.adaptive (5756133, +6), inputstream.rtmp (b8e3f39), peripheral.joystick (6312745), pvr.argustv (37a3a76), pvr.demo (bcd8289), pvr.dvblink (1732e4b), pvr.dvbviewer (f01e52c, +19), pvr.filmon (ba261c9), pvr.hdhomerun (379c62c), pvr.hts (f569808), pvr.iptvsimple (663040c), pvr.mediaportal.tvserver (01af5a0), pvr.mythtv (c18ca9e), pvr.nextpvr (fad3ca9), pvr.njoy (30743c6), pvr.octonet (1e44819), pvr.pctv (d0c7241), pvr.stalker (00f3fc4), pvr.teleboy (dfa68b0), pvr.vbox (d2e61a9), pvr.vdr.vnsi (18c7474), pvr.vuplus (bcfd34d), pvr.wmc (ce4b47a), pvr.zattoo (e72598d, +2), vfs.libarchive (84a4876)
After closing an emulator there is a sad-face now:
https://paste.osmc.tv/javedugege
but the mgba emulator and quckNes still works, just when you close it there is a sad-face
17.8-250, 16 June 2018: Based off OSMC commit (b5eb9256) and newclock5 (2a225662)
XBMC:
pvr.dvbviewer:
Includes latest addons: inputstream.adaptive (5756133, +6), inputstream.rtmp (b8e3f39), peripheral.joystick (6312745), pvr.argustv (37a3a76), pvr.demo (bcd8289), pvr.dvblink (1732e4b), pvr.dvbviewer (d6f1629, +21), pvr.filmon(ba261c9), pvr.hdhomerun (379c62c), pvr.hts (f569808), pvr.iptvsimple (663040c), pvr.mediaportal.tvserver (01af5a0), pvr.mythtv (c18ca9e), pvr.nextpvr (fad3ca9), pvr.njoy (30743c6), pvr.octonet (1e44819), pvr.pctv (d0c7241), pvr.stalker(00f3fc4), pvr.teleboy (dfa68b0), pvr.vbox (d2e61a9), pvr.vdr.vnsi (18c7474), pvr.vuplus (bcfd34d), pvr.wmc (ce4b47a), pvr.zattoo (e72598d, +2), vfs.libarchive (84a4876)
Hello. Since today I have the problem that everytime I enable a pvr client (teleboy or iptvsimple client) I get a bootloop. When I delete the addons27.db kodi starts again but when I try to enable pvr addon bootloop is there again. Do I have a chance to rescue my system or do I need a fresh install to get pvr working again?
Here the log:
https://paste.osmc.tv/tusotetuli
Thanks in advance
Greets
is the problem only on 250? If you downgrade to 249 does it work again?