I have the raw file but when Picasa sync with web site, it automatically converts them to jpg and strips the EXIF. I'll see if there's a way to include the EXIF.
On Wednesday, May 30, 2012 8:00:04 AM UTC-7, Jan Martin wrote: > > Is it just me, or is there really no way to get the original images with > EXIF intact? > Also I do not want to download 100 images one by one. > > Jan > > On Wed, May 30, 2012 at 4:48 PM, ecs1749 <[email protected]> wrote: > >> I set the number of CPU down to 1, still fails after 6 photos (4948 bit >> wide each). If I reduce the resolution of each photo to 1600 (268kb file >> size each), I can load 140+ pictures no sweat. At a resolution of 3200 >> bits wide and I was able to load close to 100 photos before it fails. >> >> If anybody wants to try, the pictures are located at: >> >> >> https://picasaweb.google.com/116295145477369704246/HuginTest?authkey=Gv1sRgCPeHl_-Wmci06QE >> >> >> >> On Tuesday, May 29, 2012 11:16:27 PM UTC-7, Steeve wrote: >>> >>> >>"An error happened while loading image : caught exception: bad >>> allocation" >>> Hasn't this problem already been discussed on this newsgroups? >>> >>> In summary on computers with multiple cores/processors images are >>> being loaded in parallel which consumes too much memory.. The error is >>> not coming from the memory which is currently being used, but from the >>> additional memory it wants to allocate.. You can find a better >>> explanation by search the newsgroup for "bad allocation" >>> >>> The workaround was to reduce the number of CPUs Hugin uses.. >>> >>> In Hugin look at file->preferences-> number of CPUs. On my machine >>> this was set to 4 I had to reduce it to 1. >>> >>> With 4 I'd typically get this error after 10 images (I've got a >>> smaller camera sensor) >>> With 2 I'd still occassionally got this error >>> So I end up having to reduce this to 1. >>> >>> Regards >>> Steve >>> >>> >>> >>> >>> >>> On May 30, 5:01 am, ecs1749 <[email protected]> wrote: >>> > For my case, this is the newly available 64 bit version of Hugin (w >>> new >>> > GUI), running under Windows 7, 8G of real memory, plenty of disk space >>> for >>> > temp, and the max amount of memory used by Hugin appears to be less >>> than >>> > 1.5G. The failure occurs with ramdon set of photos at widths of 4948 >>> bits >>> > each. Most cases I tried, the failure occurs after a handful of >>> pictures - >>> > around 4 to 5. The error message simply says " "An error happened >>> while >>> > loading image : >>> > caught exception: bad allocation". If I scale the pictures down to >>> 1087 >>> > bits, there is no issue. I can process over a hundred files no >>> problem. >>> > What else info can I provide to help? >>> > >>> > >>> > >>> > >>> > >>> > >>> > >>> > On Tuesday, May 29, 2012 2:53:12 PM UTC-7, Bart van Andel wrote: >>> > >>> > > It would help if you provide a *detailed* description of when things >>> go >>> > > wrong instead of just saying "Hugin crashes". Which version, which >>> OS, 32 >>> > > or 64 bit, amount of RAM, *specific error message*, all of those may >>> > > matter. Moreover, giving incorrect information (which you did, I >>> guess not >>> > > purposefully but nonetheless) can steer your fellow group members in >>> the >>> > > wrong direction. Being precise can save everyone some time - and a >>> little >>> > > frustration. Please keep that in mind. >>> > >>> > > Also, I asked which program crashed a couple replies back. Please do >>> read >>> > > answers carefully when people are offering you a hand. We are all >>> > > volunteers here. >>> > >>> > > Could you try to see which image the cp generators are crashing on >>> > > exactly? If you find it, you may want to post it somewhere so we can >>> have a >>> > > look at it. Maybe one of your images is broken which may cause all >>> kinds of >>> > > unexpected behavior. >>> > >>> > > -- >>> > > Bart >>> > >>> > > On Tuesday, May 29, 2012 6:02:36 PM UTC+2, ecs1749 wrote: >>> > >>> > >> Yes, I have done both and still fails. Incidentally, the failure >>> is not >>> > >> when loading the images. It's when detecting control points. I've >>> tried >>> > >> changing detectors and they all fail the same fashion (some sooner >>> than >>> > >> others). >>> > >>> > >> On Tuesday, May 29, 2012 12:09:06 AM UTC-7, Stefan wrote: >>> > >>> > >>> On 27.05.2012 20:28, ecs1749 wrote: >>> > >>> > I downloaded the 64 bit version for Windows 7 and tried to load >>> photos >>> > >>> > at full resolutions (width 4948) . Can only load 4 photos >>> before >>> > >>> > running into the dreadful "An error happened while loading image >>> : >>> > >>> > caught exception: bad allocation". I have plenty of free >>> memory - >>> > >>> > according to the Task Manager. >>> > >>> > >>> Have you tried to increase the image cache memory setting in the >>> Hugin >>> > >>> Preferences dialog? Are you sure you have enough free disk space >>> in your >>> > >>> TEMP directory? >>> > >>> > >>> With kind regards >>> > >>> > >>> Stefan Peter >>> > >>> > >>> -- >>> > >>> In theory there is no difference between theory and practice. In >>> > >>> practice there is. >> >> -- >> 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 >> > > -- 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
