Notice how the file address mimicks the db3 folder actually being within the Picasa2 folder. This is why it works for Picasa — because Picasa is now able to reference the files it needs in the place it thinks it needs them. If you are struggling to set up the symbolic link, there are programs available which provide a nicer user interface than the Command Prompt.
Check the above guide for more information. So it will have to rebuild its database, and this takes time. Especially the facial recognition, which can take days or even weeks for a large library. If you have a very large library, you might want to periodically back-up your db3 folder.
A corrupted library can cause Picasa to fail completely, but it can also result in performance and stability issues. If this happens, try replacing the db3 folder with your backup of db3.
I have to admit, I thought my computer was having a blip when it showed the folder in the gigabytes. But it does actually make sense. For every file in the Picasa library, it stores thumbnails of different sizes. These thumbnails are images in themselves, and this does soon add up. But what really seems to take up space is the facial recognition. The logic is the same — for every face it recognises, it creates a thumbnail.
There is also further work to do in building up a profile for each person, so that Picasa can try to match future faces found against existing people. Picasa can allegedly function with libraries right into the millions. I would hate to see the database size for this though.
Because of the overheads of facial recognition, both in terms of storage space and processing, it has been advised that facial recognition is turned off for very large libraries.
Google have decided to drop Picasa in favour of Google Photos. While the web is great for sharing and access-anywhere, it will never replace the performance and functionality that you get with native programs. If Google also decide to stop publishing the Picasa installer, I have archived a copy here.
Of course corrected that and used J and it worked…. The J stands for Directory Junction. Hey this is great. I used it for moving many files not just picasa. I have had the same issue and beside, I wanted to use picasa from several computers while keeping all configurations elements. Possibly the database was corrupted when you moved it. If you backed up db3, you could create a copy of your backup with this and then try again.
If not, you might unfortunately have to rebuild the database. Creates a symbolic link. Default is a file symbolic link. Link Specifies the new symbolic link name. Target Specifies the path relative or absolute that the new link refers to.
The system cannot find the path specified. It might be worth trying a visual tool — howtogeek has more information. This is helpful, thank you! I expect it would be dangerous to have Picasa running on both machines at the same time, but perhaps it would work if I only use one at a time? Hm, I did this to another computer, and put the db3 file in Dropbox. Now every time I open Picasa it re-scans my picture folder. Sometimes it is messing up thumbnails, and cropping in odd ways.
Would it have been better to copy the whole Picasa2 folder into Dropbox? Or keep it out of dropbox altogether? Unless all the photos on all your computers have exactly the same address, this could be causing problems.
Well, I ended up deleting the old dB and letting it rebuild from scratch from the photo directories and. I lost the albums, but all the photo markup crop, stars, etc is there. I spent so much time tagging the face of my family and hundred of my friends and now google closes picasa?
Like many people I've been using the wonderful and free Picasa to manage my photos. One of the huge benefits of Picasa aside from its fast and friendly user interface is that it doesn't write changes to your images. Instead it stores a record of changes that are made to each original image in a Picasa. This means you can make changes to your images in Picasa, such as adjusting the contrast and brightness or cropping or marking with a star , and you don't need to worry about it overwriting your original images.
In order to keep performance reasonable it stores a cache of these adjusted thumbnails and the changes in your Local Settings directory too. I discovered a problem with Picasa's method of updating these Picasa. This means there's a record of the changes still in the old directory, but not the new one, but it doesn't seem to matter because Picasa tracks this information in the Local Settings database.
The problem comes if you lose the database, or as I did intentionally delete it. I corrected a few, but as I looked closer, many of them were wrong -- the captions and pcitures were no longer correctly associated.
After the next update, I noticed that Picasa was slower, often hanging for a while. This also included causing screen refresh problems with my other applications that were running at the same time. I just finished allowing another version 3 update, and I notice it seems to be re-building my library -- I now seem to recall it did this with the first version 3 update. I also noticed with pictures that I've added after the prior update also have incorrect captions on some of them -- I hadn't put captions on any of them, yet.
Update Jan I've re-opened Picasa, and now the thumbnails are mixed up too. Needless to say after recommending Picasa back in March of , I can no longer recommend it. Further, if you have it, but have not upgrade to version 3 -- don't. I guess it's time to find a new photo management solution. Of course this means I guess it's time to give Flickr a shot, too.
Google Picasa. TG said…. I have yet to notice any errors. However, I will be keeping a close eye it now. Thank you for the heads up on it :. Cee said…. I have had nothing but problems with Picasa 3 for a few weeks. I had loved it at first - being able to type in info right onto the pics, adding borders around them for printing, etc. It's a pain in the rear.
Pics have been scrambled and labels are not correct under them, it hangs up constantly - I am surprized that Google hasn't done a fix on this yet Christina said….
0コメント