krbo

Members
  • Content count

    23
  • 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

195 profile views
  1. thanks - I asked because it was written in your sample photo "M-42 or no lens" so I thought maybe some vintage lens with nice picture
  2. Hi, just tested your file - arround 2 minutes to export here and yes, I also didn't realise high-pass is a choking until this thread. High-pass is my favored sharpen filter, almost in every of my post processing so that's why I noticed general slowness in work path And I'm sure it was not like that before, but in what version can't pinpoint. btw what lens you used for a photo?
  3. Of course, here you are: Wrapped.afphoto
  4. For now couldn't point a problem - started beta with CTRL - reset everything, loaded my aphoto with 4 filters and tried to measure a time before calculated export size is shown as by included picture. Times were: - no filter activated - 2-3sec - first Defringe 7sec - second Defringe 21sec - Clarity 66sec - High Pass 370sec (over 6 minutes) after that tested production version 1.6.1.93 with full filters - arround 7 minutes and results are consistent between two PCS with different GPU and win versions
  5. Since maybe 2-3 last versions export to jpg becomes more and more slowly. Now latest beta goes to something very, very slow, up to a 10 minutes to do a step. From a picture with a task manager you can see I'm not on an old, slow hardware (Win drive is SSD) but AP makes it crawl during an export. Also you can see only 4 filters used (pixel layer is a tone mapped HDR made from 3 exp. bracketed shots) First stage - calculating an export size lasts 8 minutes topping a 4 core CPU to 100% and after that actual export took another 10 minutes. During that PC is almost dead hardly responding to anything (but response to "Cancel" button of export dialog was OK) "96" was slow, "98" looks even slower - first impression with new beta. just to inform you, nothing dramatic as this is beta in the end
  6. Another vote for hot pixel filter as I just stumbled on them. It was mentioned a year ago here: hope Serif stuff didn't gave up from it.
  7. Hi Chris, catched the time to test deadly shots set on another PC (Win7 x64, Radeon 5760) Version 1.6.0.89 was installed and I tried same thing twice - all went well - no crash, no UI errors Then I made an upgrade to latest production - "93" Frist trial and crash - unhadled exception without "phone home" dialog UI crashed as I already wrote above, screenshots attached. (crash, dead Tone Map menu and Crop menu without presets)
  8. can you try your files on a beta 1.6.1.93 ??
  9. Hi Chris, I've had it exactly the same before on "59" production level but on another PC (Win7 x64, different graphics) Will certainly try that particular set of photos also over there, maybe tomorrow and will report here.
  10. Hello, Installed latest Photo and tried my usual way of merging 3 exposure bracketed photos into a HDR Full compliment of dangerous settings - denoise and tone map Photo crashed in a usual way (unhandled exception blah,blah...) entering a denoise part but this time successfully "phoned home" with an incident report. All of this is known for a long time and not yet solved yet but interesting is behaviour later: - I immediately used same photos with same settings into a beta 93 - no crash, went smooth. - Again fired in a production build 93 - this time no crash even there but UI is destroyed, after a crash Photo leaves some garbage somewhere - going into a Tone Map persona there is no more presets menu choices on the left (Natural, Detailed...) and no previews - just an empty grey area where they should be. - Crop mode dialog is also destroyed, not a single saved preset just main "Unconstrained, Original, Custom, Absolute" text - One of my open tabs in Opera browser was blanked and frozen. This looks like some collision with Aero/Desktop Manager. PC must be restarted - Photo is OK after reboot . Windows 10 x64, i5 with internal VGA, SSD, 16Gb RAM
  11. 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?
  12. 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
  13. 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)
  14. 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!
  15. 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)