In 17.1 recordings database characters coding issue
#1
After update to 17.1 in mysql library the recordings state (seen etc.) is gone. Windows and Libreelec on rpi as well.

In updateted database the earlier played file is in files table strFilename:

"Doktor House House, M.D. orvos-sorozat , TV (PRIME), 20170404_120000.pvr"

In database all new played recordings general new row, and the strFilename characters coding problematic:

"Doktor%20House%20House%2c%20M.D.%20orvos-sorozat%20, TV%20(PRIME), 20170524_232500, 38266017.pvr"

Similar problem with vdr: http://forum.kodi.tv/showthread.php?tid=307817
Reply
#2
Just confirm that you updated to 17.1 on all your devices
My Signature
Links to : Official:Forum rules (wiki) | Official:Forum rules/Banned add-ons (wiki) | Debug Log (wiki)
Links to : HOW-TO:Create Music Library (wiki) | HOW-TO:Create_Video_Library (wiki)  ||  Artwork (wiki) | Basic controls (wiki) | Import-export library (wiki) | Movie sets (wiki) | Movie universe (wiki) | NFO files (wiki) | Quick start guide (wiki)
Reply
#3
No.

My system:
X86 Ubuntu 16.04 machine with tuners, mysql and tvheadend, without Kodi
Raspberry Pi2 Libreelec 8.01 (Kodi 17.1)
Raspberry Pi2 Openelec 7.0.1 (Kodi 16.1)
Desktop Windows 10 computer Kodi 17.1

Raspi with openelec perfect work but this use the database Myvideos99 (Kodi 16.1) http://kodi.wiki/view/database_versions

Kodi 17.1 work when I played a video, the state is change (seen) but by 16.1 migrated state is lost.

The problem is only in recordings, in the video files everything is fine.
Reply
#4
(2017-05-25, 14:01)korcsi Wrote: No.

My system:
X86 Ubuntu 16.04 machine with tuners, mysql and tvheadend, without Kodi
Raspberry Pi2 Libreelec 8.01 (Kodi 17.1)
Raspberry Pi2 Openelec 7.0.1 (Kodi 16.1)
Desktop Windows 10 computer Kodi 17.1

Raspi with openelec perfect work but this use the database Myvideos99 (Kodi 16.1) http://kodi.wiki/view/database_versions

Kodi 17.1 work when I played a video, the state is change (seen) but by 16.1 migrated state is lost.

The problem is only in recordings, in the video files everything is fine.


You will have to live with this. Introducing proper encoding for recordings was an important bug fix. You will have to go once thru your recordings and restore the watched state manually. Sorry for the inconvenience.

BTW: this change did not happen from 17.0 to 17.1 In assume you updated from some version less than 17.0 to 17.1
Reply
#5
Thanks for the reply!
Reply

Logout Mark Read Team Forum Stats Members Help
In 17.1 recordings database characters coding issue0