Page 1 of 5

tvOS Testing 2.0.0 (160309.1649)

Posted: 10 Mar 2016, 04:59
by amet
Please use this ONLY if you have downloaded 2.0.0 (160309.1649), version number can be seen in TestFlight app

please avoid posting "I would love to test" posts, lets keep this for testing only.

changes since last version:
+ bump core to match jarvis
+ added skin SIO2
+ added rar
+ added DVD iso/img playback, no VIDEO_TS yet
+ bumped all PVR addons
+ added music visualisations

Re: tvOS Testing 2.0.0 (160309.1649)

Posted: 10 Mar 2016, 06:59
by Looxoor
Hi!

I just installed it and I have a problem.

Upon first run, it created the new MyVideos99 and MyMusic56 databases and as they have the same amount of rows as the older ones, I guess they have been created as they were supposed to.

MrMC was however unable to load them afterwards.

I thought that maybe it needed a fresh reboot but same result.

My log:
http://dumptext.com/Fpjlkvvq

I'm contemplating dropping the new databases to force it to re-update them.

Any suggestions?

Re: tvOS Testing 2.0.0 (160309.1649)

Posted: 10 Mar 2016, 07:28
by Looxoor
I dropped the databases and tried again to see the log for the update process.

I found a MySQL error 1419, which meant that I needed to grant the MySQL user Kodi super privilege to create triggers.

So, I dropped them again, granted the privilege and started MrMC again.

Success!

Thought I'd reply to myself if anyone else had the same problem.

Re: tvOS Testing 2.0.0 (160309.1649)

Posted: 10 Mar 2016, 13:01
by malte1975
mysql works fine with kodi 16 and MrMC version 2.0

but with kodi 17 I have problems.
do that means that there will be compatibility problems again in kodi 17

Re: tvOS Testing 2.0.0 (160309.1649)

Posted: 10 Mar 2016, 13:13
by timstephens24
I didn't have any problems with MySQL when I upgraded, it went perfectly.
malte1975 wrote:but with kodi 17 I have problems.
do that means that there will be compatibility problems again in kodi 17
Kodi 17 is in Alpha, and uses a different number at the end of the database. It's always like this with Kodi and MySQL, you can't use the same database across different versions.

Re: tvOS Testing 2.0.0 (160309.1649)

Posted: 10 Mar 2016, 14:36
by cosmoxl
Tested NextPVR a little bit so far. I'm noticing a significant increase in the time it takes to buffer the transport stream. Has something changed in the buffer settings?

Re: tvOS Testing 2.0.0 (160309.1649)

Posted: 10 Mar 2016, 15:29
by amet
cosmoxl wrote:Tested NextPVR a little bit so far. I'm noticing a significant increase in the time it takes to buffer the transport stream. Has something changed in the buffer settings?
million things have changed I am sure :)

look under settings -> system -> internet access all buffer settings should be there

Re: tvOS Testing 2.0.0 (160309.1649)

Posted: 10 Mar 2016, 15:42
by malte1975
Kodi 17 is in Alpha, and uses a different number at the end of the database. It's always like this with Kodi and MySQL, you can't use the same database across different versions.
OK - Thanks :)

Re: tvOS Testing 2.0.0 (160309.1649)

Posted: 10 Mar 2016, 15:49
by cosmoxl
amet wrote:
cosmoxl wrote:Tested NextPVR a little bit so far. I'm noticing a significant increase in the time it takes to buffer the transport stream. Has something changed in the buffer settings?
million things have changed I am sure :)

look under settings -> system -> internet access all buffer settings should be there
I'd never edited the buffer settings. Didn't even know I could.

I think that perhaps in previous versions of MrMC and/or NextPVR buffering was setup differently for the live TV stream. The default setting is to buffer 20MB and it seems that it's now doing that for live TV. The delay makes sense because it can only buffer as fast as the transport stream is broadcast. Files that are local buffer very fast indeed.

Re: tvOS Testing 2.0.0 (160309.1649)

Posted: 10 Mar 2016, 16:40
by davilla
There might be some room for improvements in the pvr binary-addon buffering area. There are a few commits that I've not brought in yet. Want to get feedback on current behavior 1st.