Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - Greatly Perturbed

Pages: [1]
1
ThumbsPlus v7-v9 Questions / Changing the Drive letter
« on: 2014-03-08 20:45:11 »
I want to move my files to a different drive. The file structure will be the same but the Drive letter will be different and ideally also the partition label. Is it possible to keep the database and change either the partition letter and/or label. Thanks.

2
A happy ending! I tried what you suggested in your last post again. But this time I removed about 25% of the thumbnails before trying compression. I then remade the thumbnails I had removed. I'm happy to report that I now have a database with 120 by 120 pixels, 80 quality and size around 1.53 GB. Thanks Daan for all your help.

3
> But I still don't understand why you couldn't jpg-compress the thumbnails in your existing database. It would be great if you could get that to work because that would preserve all your searches, user fields, etc.

I don't think it works. I removed around 6% of the thumbnails, ran compact and repair, did the compress and this was the result:

The database compact and repair process succeeded.
  Old size: 1,973,600,256 bytes
  New size: 1,973,600,256 bytes
  Compressed by: 0.0 %


Changing the thumbnail size as per your second suggestion just quickly expands the size to where it won't remake any new thumbnails. It seems pretty hopeless.

4
> Maybe, as an experiment, you could make a new database with 120x120 JPG Q88 thumbnails and let TP9 run overnight to thumbnail all those 300K+ files. Then see how big the database has become. I think it will be just a 1/4th or so of what you have now.
>    

I've recreated the database with 120x120 jpeg Q80. The size is smaller but still 1.95 GB. I'd like to use it but is there any way to transfer my saved searches, galleries and user fields?

5
Thanks for your continuing help. I guess the compression option is broken.

> Maybe, as an experiment, you could make a new database with 120x120 JPG Q88 thumbnails and let TP9 run overnight to thumbnail all those 300K+ files. Then see how big the database has become. I think it will be just a 1/4th or so of what you have now.
I'm pretty sure I tried that and it maxed out long before completing the tree. I'm beginning to think that the number of keywords automatically generated is also greatly impacting on the size.
 
> Oh wait! I think I know what the problem is. I think you're only referring to their display size, which is expressed as a percentage and which you can access from the bar above the thumbnail listing. But that has no bearing on how large the actual thumbnails in your database are. In Options | Preferences | Thumbnails you can define the width and height at which your (new or remade) thumbnails will actually be generated and stored in the database.

Yes, that's the setting I have used and reused and anything over 120 gets cropped. I've tried different display settings as well but that hasn't made a difference regarding whether the image shows up cropped or not.

6
> Have you tried Database | Jpeg Compress? (of course, keeping a backup of your current database). For now, that would seem like the best solution to me. It should greatly reduce the database size.

Thanks, but Jpeg Compress is useless. Compressing to 50% saves around 1 MB:

The database compact and repair process succeeded.
  Old size: 2,147,483,648 bytes
  New size: 2,146,553,856 bytes
  Compressed by: 0.0 %


> Also, are you sure that simply starting a new database is no option? I see that you have a lot of keywords and if those were painstakenly entered by hand, I can see how you don't want to lose them. But if they were auto-generated maybe you can just start a new database (in SQLite 3 format if you wish).

Most of the keywords were auto generated but I don't want to lose my user-generated fields, keywords, galleries and searches. I did try starting to create a new database in SQLite 3 format but gave up because of the slow time to create thumbnails.

Regarding Thumbnail size regardless of whether it is a new database or I rebuild thumbnails any size over 120 is cropped. I've no idea how you can make good large thumbnails.

7
Thanks for the reply I did as you suggested and reduced the file size by 1.2% so that it now stands at 2,071,532 KB. Other statistics are as follows:

Disk volumes defined: 9
Folder paths defined: 2,637
Thumbnail Records: 316,627
keywords defined: 68,130
keyword references: 1,804,477
User field defined: 3
User field references 47

Every time I've tried to use compression or remake the thumbnails after changing the preferences there has been an error and the size of the database ends up bigger than when I started.

This is another topic but how did you make thumbnails that big? Every time I've experimented with thumbnails over 120x120 pixels they start to become cropped. The bigger the thumbnail the more the more cropping.

Anything else I can do to save my database?

8
My database is hitting the jet 2GB limit. What are my options?

1. Is there a way to convert the database to Sqlite3 format?
2. How to get the thumbnails out of the database and into separate files?

I found the solitary python script in the undernourished Help files, but of course no instructions in how to actually use it. I mean, what's the point of having that search box on the mainscreen when the help files are so meagre? Grrr!  

My thumbnail options are currently 96 by 96, 24 bit color, no compression. Please don't suggest changing the format to jpg or using a different color depth. I've tried for several days doing that on copies of the database and it always ends up bigger!

My final goal is to have my thumbnails at 120 by 120 size. I need about 5% wiggle room as this database won't grow very quickly.

I rally hope someone out there can help me. Thanks for reading.

Pages: [1]