previously, it janked with a second of lag, made some popups, and left the display on eternal blank hang. when an image file fails to render in the media viewer, it now draws a bordered box with a brief 'failed to render' note.I fleshed out the logic and fixed several bugs in the migration code, mostly to do with the new max size stuff and distributing weights appropriately in various situations.the 'edit num bytes' widget now supports terabytes (TB).updated the 'database migration' help to talk about this and added a new migration example.I hope to have automatic background rebalancing in the near future right now, the only way files move between locations is through the 'move files now' button on the dialog, so if you have a location that is full up according to its max size rule and then spend a month importing many files, it will go over its limit until and unless you revisit 'migrate database' and move files again.

also, please note that this will not automatically rebalance yet.

it is not super precise (and it isn't healthy to fill drives up to 98% anyway), so make sure you leave some padding if you have a 500GB drive you want to store some stuff on, you no longer have to balance the weights in your head-just set a max size of 450GB and hydrus will figure it out for you.

the migrate database dialog now allows you to set a 'max size' for all but one of your media locations.

it seems many large programs are dropping support for Win 7 this year, so while I will continue to support it for a reasonable while longer, I think the train may be running out of track bros

unfortunately, Windows 7 users (or anyone else running from source on Python 3.7) cannot get the fix! it needs Pillow 10.0.1, which is >=Python 3.8.

note, if you use the advanced setup, that there is a new question about Pillow

if you run from source, rebuild your venv at your earliest convenience, and you'll get the new version of Pillow and be good.

the builds today have the fix, so if you use them, update as normal and you are good.

there were apparently exploits for this floating around I'm not sure how vulnerable hydrus ever was, since we are usually jank about how we do anything, but best to be safe about these things. we use the same thing via the Pillow library, which also rolled out a fix.

you probably noticed your chrome/firefox updated this week, which was fixing this. the main webp library (libwebp) that many programs use for webp support had a remote execution (very bad) vulnerability.

Download Hydrus Network 535 free