High server load
The inquirer has just posted a very nice article about gpuViewer and, as a result, our server is being hit my many visitors. Hopefully, we have enough bandwidth available, but in case anyone experiences difficulties downloading our tech preview, well, I hope you’ll have the patience to retry at a later time.
Please, don’t hesitate to send feedback, even if it feels obvious to you. There is also a bunch of new features coming up so, subscribe to the feed and stay tuned…
PS: Having just relocated from London to Paris, I’m actually not looking at moving to the USofA 
Posts RSS
September 27th, 2007 at 3:42 pm
Hi guys - i tried the GPU-Viewer and i really like it!!
A fantastic way of browsing through your pictures and locating lost pictures
Here’s some suggestions (in case you cant think of any yourselves
)
- do not index small pictures (like thumbnails)
- is it possible to also display the first frame of videos (avi/mpg) - i also record small movies with my photocamera
- make it possible to include various folders into 1 collection
Keep up the good work!!
September 27th, 2007 at 6:30 pm
Odd error on install - detects my 1900xt as not supporting shader2 when it’s really a shader3 card.
September 27th, 2007 at 10:46 pm
Great tool!! Very handy to look for a mass of photo in harddisk!!
However, it crashed and now everytime I open gpuviewer there is a “buffer overrun” message and it closes itself after the message. Any idea to solve this problem?
September 27th, 2007 at 11:55 pm
The crash is still not identified, it most presumably comes from a file that gpuViewer fails to parse and add to the database. When restarting, gpuViewer skips over the files already indexed and committed, hence it crashes earlier… I hope to find a way to identify which files aren’t understood soon, and once I can see the files, should find a way to make them not crash. Ahhh, if only it would crash on one of muy machines !!!
September 28th, 2007 at 10:54 am
Loving gpuViewer!
I’d like to make a suggestion for an alternate method of sorting/viewing pictures. The calendar view works well, but I have thousands of photos without EXIF data. If you could use the calendar interface to display pictures in folders with or without EXIF data that would be great!
Like instead of the top level being years of photos, have each folder represented. Then zooming in on each folder, instead of individual months and days we see increasing depth of subfolders.
September 28th, 2007 at 12:55 pm
I was excited by the product, however it goes into an infinite loop and eats 100% CPU on launch - this is on two differently configured machines. Does it have to be installed as admin?
September 28th, 2007 at 12:57 pm
Three people have reported 100% CPU use on launch (actually, 100% use of just one core). I am still not sure what can cause this, but as for the crash case, I’m preparing to put out a version that should help identifying what exactly is happening.
September 28th, 2007 at 12:59 pm
Folder view is in the plan, but I have some more interesting views to complete first… Stay tuned
September 28th, 2007 at 1:03 pm
I’ll help you debug the problem if you like - as long as it doesn’t trash my system … too much =)
October 1st, 2007 at 10:31 am
i had the 100% as well on 2 machines - it is caused by the config-survey trying to send its results back to the server. (maybe because of a firewall / proxy??)
This is reproducable - it happens each time i run the config survey and hit the “OK” button
just kill the process and then start gpuViwer manually as you would normally
the first time it might show a corrupted screen - dont let that bother you, select file->open catalog and you’re in business
hope this helps / costa
October 1st, 2007 at 10:40 am
hi, every thing all done, survey OK , but i cannot see any Thumbs ? i cannot see any thing actully ! no pictures in the view panel !! a little help Please
October 1st, 2007 at 2:46 pm
@Kashif Riaz
yes, i’ve seen this happen as well
It usually happens when you switch between collections without quitting gpuViwer.
Hit [tab] and look at the CPU-utilization. Once that gets down to zero (0) it means gpuViewer is done indexing the new collection.
If you don’t see any thumbs then quit and restart gpuViewer - this fixed the problem for me.
check that there’s a “index.vg” file in the root of the directory where you started browsing.
There should be enough space for this file to be created