Hi Ian, 2011/12/21 Ian Tindale <[email protected]>
> I downloaded last night, and ran a set that I had shot that afternoon. I > found that it did the job as per usual, except that I noticed when changing > the projection from the GL window, it sometimes exited the application when > I selected successive projections one after the other. Not always, though. > Maybe it used to do this before, I don’t know. > > When it worked, it happily blasted all eight cores of this i7-2700K > hackintosh (running my purchased Lion) (16GB ram), for the parts of the > procedure that use all eight cores that is. > > I notice that this (and prior versions) have a tendency to ‘forget’ which > state I left it in when I try out the Use GPU option (which doesn’t work in > OS X, but I seem to remember can work in Linux, but I’ve hardly used it > more than once or so in Linux, some months ago). The GPUs I’ve attempted > are the in-cpu one, the Intel HD-3000 (no-go in either OS), and the card I > am actually using right now, the Asus HD-6450 silent (which as I say, I’ve > seen Hugin use the GPU setting once in Linux). The thing is, in OS X, if I > set it to use GPU, I get an error (this is the end part): > > gpu shader program compile time = 0.025 > nona: Unsupported framebuffer format in: > /Users/Shared/development/hugin_related/hugin-2011.4.0/mac/../src/hugin_base/vigra_ext/ImageTransformsGPU.cpp:713 > gnumake: *** [PC202039-PC202076-60000.tif] Error 1 > > However, if I set it back to not using the GPU, it often doesn’t realise > this and continues giving me this error, even next time I use it. I have to > go back into the prefs a second time and click apply and OK again, and > it'll work. Once it is set to work, it continues. It’s only if I try to see > if the GPU now works, once every time I download a new one, that it > misbehaves like this for a while. > > Also, what would be useful is if the PTUbatcherGIU could be quit properly > — it cannot every be quit from by itself using cmd q, it always requires > cmd opt esc to force quit it. This has always been the case, though. It > just means that I can’t leave the computer on and have the Energy Saver > schedule turn the computer off later at night, this program stops it > because it can’t be quit from. > > > Thanks for you feedback. The gpu stuff is still experimental. We do have a track record with user experiences where you can add your hardware data and experiences, but I can't find it myself right now. W.r.t. PTBatcherGui: I can quit it using cmd-q. I never tried the energy saver schedule. I will test and probably we need to do a feature request. Harry -- You received this message because you are subscribed to the Google Groups "Hugin and other free panoramic software" group. A list of frequently asked questions is available at: http://wiki.panotools.org/Hugin_FAQ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/hugin-ptx
