krbo

Members
  • Content count

    13
  • Joined

  • Last visited

About krbo

  • Rank
    Newbie
  • Birthday 05/22/1962

Profile Information

  • Gender
    Male
  • Location
    Croatia
  • Interests
    tennis, books, photo & video

Recent Profile Visitors

75 profile views
  1. I always download these fine tutorials from Vimeo for an easier later usage. Usually in a 1080p resolution and have a question: why there are very often two files of the same resolution but different sizes?? (usually on higher resolutions 1080,2K) For example latest "Uplift Epic skies" in 1080p have two files: one 112,393Mb and other 103,971Mb Which one to use?
  2. Vignetting correction couldn't work you as it never worked and it will never work until someone make calibration and updates database. APhoto uses this database: http://lensfun.sourceforge.net/lenslist/ Last column is vignette correction and it is "no" - no auto correction for our camera! But Adobe also does not have vignetting correction for FZ1000 You have to use manual lens correction for FZ1000 wide angle shots
  3. what exactly does not work for you? if you expected vignetting correction it never worked as it is not part of a lens database used (I also have a FZ1000)
  4. Just a few hours ago 1.5 crashed with well known and reported HDR merge (denoise, deghosting..., error 05 without log) Right now tested this latest (88) beta with the same photo set - a least several times faster merging, denoise and tone mapping - no crash!!! this subject requires more testing but so far - excellent! thanks to a whole team!
  5. This problem is at least several months old, found this: but I have to test it on my other Win10 PC config (previous report was for Win7)
  6. it's here: I had to remember testing latest HDR crash on another PC with Win10
  7. I already reported that. It's random and picture dependable. It's not just denoise, sometimes you can go away with correct HDR if you switch off denoising but other times it produces picture with heavy artifacts (lines, blocks - usually black) and sometimes it plain simple crahes with error 5 and no log.
  8. I will confirm this behaviour - once closed Sources window - goodbye sources no matter of clone tool. (1.52.69) Latest beta ("81") is a little better - sources can be populated again by selecting a clone tool but only in a current session - if a work in progress is saved, Photo closed and then started and continued later - again no sources in a source window.
  9. downloaded, installed and tested with previous example: yes, it is fixed - thanks! but one more small thing - this exif info shows wrong picture size for my camera (Lumix FZ1000) or my camera has it on the wrong place? it says on "Summary" mode that size iz 1920x1080 pixels readed from exif:PixelXDimension param (and "Y" also), real dimension is 4823x3617 pixels which can be found in tiff:ImageWidth (and Lenght) params. test jpg with that data is made from raw picture format (with same exif) jpgs direct from camera have correct dimensions in exif but raw and exported jpgs after editing has wrong one (just tested it with Lumix TZ70 - same thing.)
  10. Hi, there is a one small bug with EXIF reading. If I use picture folder with some of my language specific accented letters in it's name, EXIF becomes empty (letters are ŠĐŽĆČ) For now I don't have exact rule as it is variable, in some combination of letters Photo reads EXIF in other don't - it took me a while to pinpoint a problem which can be easily avoided by using pure ASCII for folder names. Free ExifTool shows exactly the same behavior. example: folder named "Đ" (unicode U+0110 as Character Map says) - Photo can't read EXIF in any file in it
  11. great, it's always a question of reproducing an error (i'm 30 yrs in computer maintenance so know a drill), now I'm sure it will be solved. thanks!
  12. hi Sean, certainly - all 3 of them are there.
  13. hi, I have a problem with frequent Affinity win crashing during HDR merge with tone mapping. It's interesting it is not a general problem but a picture specific one - can't detect what triggers it but some shots goes like a charm through the process, some crashing app. Scenario: - usually using 3 RAW bracketed shots from Panasonic FZ1000 - 20Mpix each (12Mpix from other camera never produced such thing on powerfull PC configs) - bringing a HDR merge and choosing: it's my usual start params - Affinity then works OK aligning and merging but starting denoise brings: of course crash reporter is useless: if I deselect denoise (and ghosting sometimes) process can finish but with random errors in picture: (these two vertical lines are error in processing) This is a brand new PC, not so weak: I5-7500 (internal GPU) 16Gb RAM and SSD with Win10 x64 Pro (this set of 3 shots always produces the same error so if you need them for analysis please PM me)