User talk:Ozone Grif

Revision as of 08:20, 27 April 2009

Hello, I understand the effort for checking for duplicates which differ due to rotation.

But maybe as an option you could add the 90 degree check. Due to different import programs of digital cameras sometime the picture is transfered as it is and sometimes using the ETIF information if the camera was rotated. This information is applied to the photo during import and rotated as well.

Therefore I have quite some duplicated which differ "just" by 90 degree but are not detected by the program.

I would be a great help if you could add this feature.

Kind Regards,

Sven

• Hello Sven, That option can be done in the next version. It shouldn't be too difficult to implement. I will write a "To Do" page in the Wiki to follow possible evolutions. Yours, --Ozone Grif 02:48, 1 January 2008 (CET)

Why can't I see the "discussions" page ?

I always got a: "You've followed a link to a page that doesn't exist yet. To create the page, start typing in the box below (see the help page for more info). If you are here by mistake, just click your browser's back button. "

Please email answer to my email adresss *****@*****.ca

I want to contact the authors for some questions and bugs but found no email address

Thank you Peter

Is there a limit on how many pics can be compared?

I am running Windows XP Pro SP2 on a system with an Intel Pentium 4 and a 3.60GHz chip and 1GB of memory. I have tried to scan a directory with about 206,000 images. Visipics scan about 200,000 files before it freezes. I've tried running in several times but it just stops and when I check the running applications under the Windows Task Manager it say's the application has stopped responding. It's frustrating because it takes more than 5 hours to scan.

I'm curious to know if there is a limit to how many pictures Visipics can check? I know I need to add more memory because it uses all available physical memory as well as cache memory. My dilema is that I have roughly 1,000,000 pics that need to be compared across multiple directories and this has become an issue.

Thanks for your assistance.

Michael (hawk72758) 1/8/2009 8:43pm

Hello Michael, try to check the option "Thread Sync". It helps preventing freezes. There is no theorical limit to the number of pictures you can load, but your memory. With 1gb you can indeed scan around 200,000 pictures before reaching the maximum cap. For 1,000,000 you will require 4gb of memory and a dual core to speed up the scanning process. I suggest you manually scan folders after folders to not overload your computer. You can also scan one folder, then save the projet to reuse it later when you get new photos. Yours --Ozone Grif 23:58, 14 January 2009 (UTC)

Thanks Ozone, I'll try the sync thing. I am adding 3 more gigs of memory next week. Unfortunately my motherboard can handle 8gigs but Windows XP only see's 4gigs unless I use 64bit XP. Also, is it possible to filter out the folder settings directory globally? I have to tell it to ignore pages and pages of pics that aren't duplicates.

Michael (hawk72758) 1/24/2009 9:22pm

It is not possible to set folder names filters to prevent them from loading. But you can ignore a whole folder and subfolders with the button "Ignore folder". --Ozone Grif 18:11, 26 January 2009 (UTC)

I have the same file count and/or memory limitation as well. I cannot process much more than 200,000 images without the application hanging. I did try turning off the "Threads Sync" option and it made no difference. I have 3GB of RAM on Windows Vista 32-bit. This is the only issue I have with this great product. :)

Richard

Just wanted to let everyone know that after bringing my system up to 4gb of memory I am still limited to 238,518 files before it crashes even with the thread sync checked. I'm wondering if it has to do with the fact that it loads ignored files. I would think that they should not be visable on subsequent scans unless it finds a new match. I have 98,000 lines in my ignore file. I'm not a programmer but it's just a thought. Also, it never utilizes more than 2gb of the 4gb of memory which i guess is good?

Michael (hawk72758) 3/28/09 22:11

loading limits

I see a couple of loading limits for 1Gb and 4Gb- can you give a figure for 2Gb- the maximum my computer can address. Thanks

It all depends on your system : Windows XP / Vista / Linux, how much memory you have, how the swap is configured, what type of pictures / photos you load, etc.

If you read above, we find Michael who can load 200,000 pictures with 1gb on XP ; and Richard can load 200,000 pictures with 3gb on Vista. I heard of a user who loaded 500,000 pictures with 2gb on Linux.

My best guess is "Somewhere between 200,000 and 500,000 pictures". It is hard to get finer.

I take a note in the RoadMap to try to increase this capacity in a future version.

Yours, --Ozone Grif 10:57, 17 February 2009 (UTC)

Thanks. I had originally set it working with close to 1,000,000 and it started repeated error boxes pinging away. It just succesfully completed 100,000 so I'll build the number up- it seems like a guess thing. Is there anyway you could set up a way to catch it before it crashes- say when memory drops to a preset amount? Alan (sorry name missing from earlier message, I kind of expected it to automatically be entered).

1.3 slower for me than 1.25

Hello, I've been using Visipics for a long time. After replacing my hard drive and reinstalling WinXP, while reinstalling all my programs, I upgraded Visipics from 1.25 to 1.3. I soon went back to 1.25 because 1.3 takes more than 3 hours to do what 1.25 does in 2 hours. 1.3 loads pix in about the same amount of time, but is slow in comparing them. I also noticed that 1.3's filter slider does not stay in one place while running a job. I'll start a job with it on Basic and when I check back later, it'll be in another random spot

Hello Cloudchaser,

I understand your remark. It is mostly a configuration problem which can be solved with the following steps.

First make sure about those options are not checked :

• Scan for 90° rotations
• Slower VisiPics
• Thread Sync (except if you have observed freezes on your computer)
• Loosen filter automatically

Then go into the "Loader Tab", next to the "Filter Tab", and make sure you don't have any filter activated :

• Bigger than "None"
• Smaller than "None"

Try again, VisiPics 1.3 should be way faster, and the slider won't move after an empty scan ! --Ozone Grif 15:26, 15 April 2009 (UTC)

To let you and anyone who sees this know, that took care of the problem! Thanx for your help! I made a note of that so I'll remember it in the future the next time Visipics updates.

It was a little faster, 10 minuites faster on a job that took 1.25 124 minuites, but I was loading a lot of image heavy pages in my browser at the same time, so that probably slowed visipics down.

1.3 not saving jobs properly

I hate to bug you again, but 1.3 seems to not be saving projects properly. Steps I take to recreate and attempt to solve this problem are as follows.

1. Visipics scans my storage folder.

2. I tell Visipics to file/save project and I save the .vps to the same folder that my storage folder is in (as I always did with 1.25).

3. I close Visipics and restart my system and reopen visipics (or just close and reopen Visipics).

4. I load the project, hit the green arrow start button and wait for all the pictures to be loaded.

5. I put the folder that I initially save pix to in the list of folders to be scanned.

6. I hit the green arrow start button and Visipics seems to scan that folder, but duplicates aren't detected.

7. Even when I deliberately planted duplicates from the storage folder to the folder I initially save pix to, duplicates weren't detected.

8. I also tried closing/reopening Visipics and repeating step 4 with the folder that I initially save pix to already in the list of folders to be scanned before hitting the green arrow start button and that didn't work either.

9. If I have Visipics to scan my storage folder from scratch and then scan the folder that I initially save pix to, duplicates are found, it just doesn't work if I load a previously saved job and then scan another folder.