@JerryK132
I don't use Timeshift so an interesting learning period! So this is my understanding of how it works and as a result the attachment.
Most of the code developed for Timeshift dates from 2013 and as such is basically same on most images like OpenATV and their clones (as they took the OpenViX code).
The major change during that time has been python 3 and Unicode, which expect all sources to use utf-8 (thanks to the American developers - who expect you to know all your sources and make sure its utf-8) - Unfortunately there are other coding variations and languages in this world. ... and Kodi and Windows doesn't help.
So running Timeshift uses the timeshift folder until you stop or decide to continue as a recording, at which point 2 files are created in the Movie folder (for the "Movie" recording and one for the timeshift part recording).
When you stop the recording, Timeshift will merge the 2 files creating one "Movie" file and delete the other.....so at this stage one Movie folder.
Works fine EXCEPT that when you stop and it goes to merge, it processes ALL files in the /media/HDD/Movie directory, looking for a Timeshift Movie/Timeshift pair...... which is indicated by a pointer in the Movie meta file.
So not an issue, except if that Movie folder contains files with non utf-8 file names - such as from Kodi.
The attachment, tries to handle that by looking at the most likely encodings (utf-8, latin-1) and if not, assume its not involved in Timeshift.
So try the attachment - works fine on my test box
I don't use Timeshift so an interesting learning period! So this is my understanding of how it works and as a result the attachment.
Most of the code developed for Timeshift dates from 2013 and as such is basically same on most images like OpenATV and their clones (as they took the OpenViX code).
The major change during that time has been python 3 and Unicode, which expect all sources to use utf-8 (thanks to the American developers - who expect you to know all your sources and make sure its utf-8) - Unfortunately there are other coding variations and languages in this world. ... and Kodi and Windows doesn't help.
So running Timeshift uses the timeshift folder until you stop or decide to continue as a recording, at which point 2 files are created in the Movie folder (for the "Movie" recording and one for the timeshift part recording).
When you stop the recording, Timeshift will merge the 2 files creating one "Movie" file and delete the other.....so at this stage one Movie folder.
Works fine EXCEPT that when you stop and it goes to merge, it processes ALL files in the /media/HDD/Movie directory, looking for a Timeshift Movie/Timeshift pair...... which is indicated by a pointer in the Movie meta file.
So not an issue, except if that Movie folder contains files with non utf-8 file names - such as from Kodi.
The attachment, tries to handle that by looking at the most likely encodings (utf-8, latin-1) and if not, assume its not involved in Timeshift.
So try the attachment - works fine on my test box
