|
Welcome,
Guest
|
|
Keep only certain metadata inside the CBZ
(1 viewing) (1) Guest
Share your ideas
|
TOPIC: Keep only certain metadata inside the CBZ
Keep only certain metadata inside the CBZ 1 year, 7 months ago #8839
|
Hey cYo
Following a request i made with cbanack to prevent his script from modifying the metadata on a file very often, which leads to file hash changes, I'd like to know if you'd contemplate adding a way of selecting what information to keep inside the file and what to store just with the (big) xml library file. Things that change often like last page open, read/unread status should be kept only on the library, because storing that inside the file means that each time you open a file, just by opening it, you alter its hash value. Now, if you're just using comicrack, that isn't a big deal, but if the file is also being shared by another app, and the hash value changes, it will force either a rehash or simply make if disappear from that share. Of course, i -could- simply convert everything back to cbr and be done with it, no more changes, but that kinda defeats the purpose of having metadata with the files in the first place. A more granular control over what gets written where is my suggestion/request. Thank you for your time, fK |
|
|
Re: Keep only certain metadata inside the CBZ 1 year, 7 months ago #8841
|
From the manual
![]() ComicRack only stores comic-related metadata inside the cbz.. rest all the non-comic metadata ( last page read, current page, added, tags, rating, read percentage, opened count, added/opened date etc.) are on the library. so, if you transfer a cbz to another computer, you lose this non-comic metadata. So fK, I guess your request is already implemented ! |
Now Playing: The ComicRack Manual (Online) |
Re: Keep only certain metadata inside the CBZ 1 year, 7 months ago #8844
|
I'm having a hard time pinpointing what is changing most of the files in my library, and that leads to 12 hour rehashing sessions, which i am not particularly fond of.
Anyway, sorry for posting this then, please delete this thread. Thanks, fK |
|
|
|
Time to create page: 1.35 seconds

