Kodi 19 'Matrix' alpha 1 is ready to launch

ArcticWolf

Trusted Helper
#3
Gaaaah, can't believe they'r planning to change the DB numbers for the final 19 release after running with the same DB version as Kodi 18 all this time with the alphas/nightlies :(. (At one point it was mentioned there may be some support to avoid this very issue with each new Kodi version but it looks like that all went down the crapper.)

My knowledge of MySQL (MariaDB 10) literally ended at the ultimately unnecessary & extensive research I did to get it all initially set up & running. It's all worked absolutely perfectly since just with the MySQL server itself running on one of my NAS, (no additional Trakt add-ons etc. etc.)

Migrating/exporting the DB from one version to another, however. In a word, YIKES!!!!!

I don't want tens of thousands of bloody .nfo files everywhere in with all of my media & I don't presently have any .nfo files in use with my DB at all. It's incredibly lean & clean as it us, & I'd prefer it stayed that way.

I just want to migrate it all as is with PHPMyAdmin so it seamlessly jumps from one Kodi version to the next. So far, however, I can't find anything to explain the whole process in simple terms for the complete MySQL dummies like me :(!!

It's been an awesome option to have, especially as we're constantly jumping between or testing all of the various MINIX devices which would have been a nightmare maintaining a separate library on each individual device, but Christ I hope I don't have to end up rebuilding a new MySQL library from scratch just for Kodi 19. (Not that, that is a slow process, it actually only takes a few minutes & it's all done ready to go.) It's the countless hours it would take for me to manually note all of my watched status & user ratings for all of my media which could potentially take days :(. (Not really bothered about resume points if starting a whole new library & there wouldn't be that many to bother about that anyway.). But, I have countless files with watched status/user ratings that I'd really want to preserve after all of the initial effort & growing the MySQL library since starting it all up.

With a library as large as mine, this could potentially become a serious headache for something that's actually supposed to make the whole concept easier :(
 

notrui

Trusted Helper
#4
@ArcticWolf

Do this:
1-Use trakt kodi add-on in order to keep your watched/rating library (it works very good for me trakt)
2-Use advancedsettings.xml with the same username (this way you can copy just one advancedsettings.xml to clients and use kodi18 or kodi19 and in the future kodi 20...)
3-With your whole database library syncronized with trakt:
when you migrate to kodi 19 is just syncronize your whole database library (if new installation you need to scan for new content)

Note:
there is a option in phpmyadmin to export databases (for backup) and there is another to import.
To create new database: (for kodi 19 for example)
I always use trakt (installed on kodi) and i let server (in my case mariadb5, i also have installed on my NAS mariadb10 but i am not using it) to create a new/fresh database.

If you look at my phpmyadmin you see kodi 18 and kodi 19 databases (see attached files)
And yes kodi changed database versions for kodi 19 (in my opinion it is better this way, because it is easier to understand with different database numbers)
https://kodi.wiki/view/Databases

Other notes:
Of course we can create two advancedsettings.xml with a different username but i came to a conclusion that is much easier if we use only one username and one advancedsettings.xml
I can use kodi 18 and kodi 19 (databases are syncronized and tottaly scanned)
 

Attachments

Last edited:

ArcticWolf

Trusted Helper
#5
@ArcticWolf

Do this:
1-Use trakt kodi add-on in order to keep your watched/rating library (it works very good for me trakt)
2-Use advancedsettings.xml with the same username (this way you can copy just one advancedsettings.xml to clients and use kodi18 or kodi19 and in the future kodi 20...)
3-With your whole database library syncronized with trakt:
when you migrate to kodi 19 is just syncronize your whole database library (if new installation you need to scan for new content)

Note:
there is a option in phpmyadmin to export databases and there is another to import but i always use trakt and i let phpmyadmin to create a new/fresh database.

If you look at my phpmyadmin you see kodi 18 and kodi 19 databases (see attached files)
And yes kodi changed database versions for kodi 19 (in my opinion it is better this way, because it is easier to understand with different database numbers)
https://kodi.wiki/view/Databases

Other notes:
Of course we can create two advancedsettings.xml with a different username but i came to a conclusion that is much easier if we use only one username and one advancedsettings.xml
I can use kodi 18 and kodi 19 (databases are syncronized and tottaly scanned)
Aaahh, your Kodi 18 & 19 tables are now under the same username. When we discussed this in the past you had posted up a previous screenshot of your PHPMyAdmin with a Kodi 18 DB & a second completely separate Kodi 19 DB as well.

Yes, I know there's the option to export/import in PHPMyAdmin itself, but it's unclear whether that process would create & cause thousands of .NFO files everywhere as previously mentioned above, that's the issue there's little information on.

I'd rather avoid using Trakt as that's essentially then two things doing the exact same job simultaneously at all times for a start, twice the resources to do one job too obviously. (The whole point of one is that the other essentially isn't required anymore.). I'm also not big on posting up on exactly what I had for breakfast, lunch or dinner on Facebook/Twitter/Instagram, or the precise timings of my last bowel movements as often seems to be the trend these days. The same applies to Trakt in that regard really ;).

Will ask about on the forum Kodi, best place to get definitive answers on this particular issue guess :).
 

notrui

Trusted Helper
#6
Aaahh, your Kodi 18 & 19 tables are now under the same username. When we discussed this in the past you had posted up a previous screenshot of your PHPMyAdmin with a Kodi 18 DB & a second completely separate Kodi 19 DB as well.

Yes, I know there's the option to export/import in PHPMyAdmin itself, but it's unclear whether that process would create & cause thousands of .NFO files everywhere as previously mentioned above, that's the issue there's little information on.

I'd rather avoid using Trakt as that's essentially then two things doing the exact same job simultaneously at all times for a start, twice the resources to do one job too obviously. (The whole point of one is that the other essentially isn't required anymore.). I'm also not big on posting up on exactly what I had for breakfast, lunch or dinner on Facebook/Twitter/Instagram, or the precise timings of my last bowel movements as often seems to be the trend these days. The same applies to Trakt in that regard really ;).

Will ask about on the forum Kodi, best place to get definitive answers on this particular issue guess :).
Ok. I understand 🙂.

I don't have that problem of posting/information on trakt.

Regarding social media i only have facebook and i keep things very private 🙂
 

ArcticWolf

Trusted Helper
#7
Phew, asked on the Kodi forums & they've sorted out this process for updating Kodi with MySQL :).

All being well, once a new instance of Kodi 19 is run linked to the MySQL server it automatically creates & ports entirely new DB tables under the same user/root all by itself.

Whoop :). Finger's crossed it's all automated & simple.
 

notrui

Trusted Helper
#8
Phew, asked on the Kodi forums & they've sorted out this process for updating Kodi with MySQL :).

All being well, once a new instance of Kodi 19 is run linked to the MySQL server it automatically creates & ports entirely new DB tables under the same user/root all by itself.

Whoop :). Finger's crossed it's all automated & simple.
Yes. I already tested that :)
Use only one advancedsettings.xml (i am using this now) and when you install and run kodi 19, MySQL server automaticaly creates new DB tables and ports everything.

The problem is :
If you use two different advancedsettings.xml (one for kodi 18 and another for kodi 19) MySQL server creates new Databases tables and you have to scan again your whole library.

Backup databases:
You have several options:
-Use mariadb 5 (for primary server) and mariadb 10 (for backup for example)
-Use replication (phpmyadmin, master replication and slave replication)
" MySQL replication is a process that allows you to easily maintain multiple copies of a MySQL data by having them copied automatically from a master to a slave database "
-Use export and import (phpmyadmin) - Manual

I use only kodi trakt add-on and for now it works for me very well :) (automaticaly)
 
Last edited:

ArcticWolf

Trusted Helper
#9
Yes. I already tested that :)
Use only one advancedsettings.xml (i am using this now) and when you install and run kodi 19, MySQL server automaticaly creates new DB tables and ports everything.
Lol, why didn't you say that to begin with???

The problem is :
If you use two different advancedsettings.xml (one for kodi 18 and another for kodi 19) MySQL server creates new Databases tables and you have to scan again your whole library.
Why would I use another/different advancedsettings.xml when I specifically want to keep the existing library from existing sources??? I'll drop the exact same advancedsettings & sources .XML files I always use into Kodi 19 when the time comes :)!!

Job done, (no Trakt required).
 

notrui

Trusted Helper
#10
I already tested many things:
Mariadb5, mariadb10, different advancedsettings.xml, nfs, smb, server name (instead of ip number), etc🙂...

When you migrate to kodi 19 (new installation): (i almost sure in all the tests that i made and i think it will work just fine for you)
The first time you run kodi 19 you will see database migration and you will have the whole database content also in kodi 19 (automaticaly creation of new tables).

Using kodi 18 and kodi 19: (this is true also for me)
If you are going to use for some time (just kodi 19 to test and you added more videos to your library) and don't use (in that test time) kodi 18, next time you return to kodi 18 you need to scan the new content in kodi 18 (will be outdated, less tables, as a sequence, less videos).

Using trakt:
It is useful, specially if you are going to use kodi 18 and kodi 19 and as a backup

With many setups (and tested) i made sometimes it is difficult to explain 🙂
 
Last edited:

Skynet

Administrator
#11
KODI 19 alpha 2 is out.

It's been more than a month since our last "preview" release, so it's time we boxed up something new for everyone.

The usual drill applies: this is an alpha, some things will be broken, your home is at risk if something goes wrong, it might run off with your partner, don't blame us if it eats your kittens. Otherwise, though, all should be fine.

Latest changes:

Playback

  • Music: Display album duration in info dialog. Album duration can be used in smart playlists in the same way as for songs
  • Music: Read tags and and album art from music files served from an http(s) server
  • Music: Fix list view of files containing multiple streams
  • Feature: Audio decoder addons can now pass more information on Kodi (album, year, notes ...)
  • Audio decoder addons can now pass more information to Kodi (album, year, notes ...)
Subtitles

  • ASS: Fixed timestamp overlapping overlays
Skin/Look-and-Feel

  • Improvements to both music and video library artwork
    • Better "out the box" behaviour, optionally use all image files found in media folders
    • Artwork levels - max, basic, custom, none
    • GUI settings for custom configuration of whitelists (replacing awkward editing of advancedsettings.xml)
  • Redesigned SeekBar that will auto-hide when video playback is paused
Platform Specifics

  • Apple TV
    • Fix Kodi crash on start after a manual install with dpkg -i command (jailbroken devices only)
    • Fix TopShelf feature after a manual install with dpkg -i command (jailbroken devices only except Unc0verTV devices, needs investigation)
    • Fix missing thumbs on TopShelf items
Python/Addons

  • Fix scripts/plugins not being notified of abortRequest intents on app close
  • Deprecate xbmc.translatepath in favour of xbmcvfs.translatepath towards convergence with the binary addon API
  • Broken/deprecated add-ons are now highlighted in the add-on list, and you're now prompted when you try to activate one
  • Fix: Prevent VFS addon changes (update, disable and uninstall) if in use
  • Fix: VFS addon problem, where Kodi needed a restart before showing a newly-installed version
  • Binary addon system revised to ensure higher security in data exchange between addon and Kodi (only inputstream missing)
  • Revised binary add-on system documentation for outside developers (only inputstream missing)
  • Internal binary add-on settings dialogs cleaned up, plus updated help text (audioencoder.kodi.builtin.aac, audioencoder.kodi.builtin.wma, screensaver.xbmc.builtin.dim)
If you're bold, brave (and possibly a wearing a red shirt), you can get Alpha 2 from here. Again, though, please - and adopting a more serious note - expect some breakage, and don't use this as your daily installation unless you know how to get things working again. If you do make the move and install it, however, please do share your experiences back with us so we can really get going on those bugs.
 
Top