2024-05-14, 06:57 PM
(This post was last modified: 2024-05-14, 07:02 PM by Efficient_Good_5784. Edited 3 times in total.)
(2024-05-14, 06:25 PM)TheDreadPirate Wrote: Mine grew from 4.5GB to 17GB.Almost the same here. My config folder went from 400MB to 17GB after my BIF files were converted to trickplay files. Do you have other things enabled on your libraries like chapter image extraction?
(2024-05-14, 06:15 PM)bitmap Wrote: Holy crap I never even looked at this... I have been running 10.9 for weeks now using the unstable build (just swapped to stable for 10.9.1) and have Trickplay running at 8 AM (bad choice) with a limit of 5 hours. I'm only at 27%. Granted, I have a decent library, but I'd say at this rate it's likely that the process probably will take several days... EDIT: At 27%, my config folder has ballooned to 54 GB...Back when Jellyscrub came out, I personally wanted to use the CPU to create my BIF files since it resulted with smaller BIF files (like some tens of KBs smaller) when compared to using HWA. It took the 5600G in my server at the time 3.5 days non-stop to go through all my media. If I remember right, I had about 2.5TB worth of shows and a few movies. It would take like 1.5 minutes per 24min show and like 4-5min per movie to generate their BIF files.
What I ended up doing is making a task that would run twice weekly at 2am with no time limit to generate the BIF files for new media. I disabled everything else that would generate them as I only wanted the scheduled task to do it. Worked well for me. I wish I could turn off the current trickplay's implentation of regenerating the trickplay files when you rescan and replace the images of your media. I have everything else disabled that would do so except the new scheduled task for them, and that's the only thing I can't turn off.
Also, @playserver, the trickplay files are located at "config/metadata/library". If you look around, they're all .jpg files named in order with numbers (starting at 0, ex: 0.jpg).