Jump to content

Eric5

Members
  • Content count

    90
  • Joined

  • Last visited


Reputation Activity

  1. Like
    Eric5 got a reaction from Snapseed in Please Lightroom Replacement!   
    I was just researching this myself and came across this thread.  I ditched all Photoshop stuff six months ago.  Although I seldom ever used Lightroom (I don't take enough photos), it did come in handy once or twice for some huge astronomical panoramas I created (mainly just for quick processing of each photo, but I used the excellent MS ICE for the composite).   Anyway, what about Darktable?  Never used it, but free and supposedly updated, also works on multiple platforms.  The info I could find on it shows that it supports many Lightroom functions.     
  2. Like
    Eric5 got a reaction from studio97 in duplicate document   
    I have several paid Photoshop actions that I am trying to manually transfer to Affinity Photo using Affinity's macro format.  The problem is that many of the actions had duplicate document as one of the steps and Affinity does not have this feature.  Unfortunately, I have not found a workaround therefore I am requesting that duplicate document be added.  Thank you.
  3. Like
    Eric5 got a reaction from firstdefence in need larger than 4096 brush size, how to do?   
    Thanks, guys.  I got around it by warping.  AP didn't like that and eventually crashed, but got the job done. 
  4. Like
    Eric5 got a reaction from firstdefence in need larger than 4096 brush size, how to do?   
    Thanks, guys.  I got around it by warping.  AP didn't like that and eventually crashed, but got the job done. 
  5. Like
    Eric5 got a reaction from walt.farrell in need larger than 4096 brush size, how to do?   
    I'm trying to make a series of concentric rings with an oval shape relating to the size of the original oval that is approximately 5000px.  I could do this I suppose by warping the dual brush I had planned on using, but this is going to be a lot more work.  I could also resample the original image down to the max of the brush, but I didn't really want to do that. 
  6. Like
    Eric5 got a reaction from John Rostron in copying a layer to use as a layer mask and adjust mask?   
    Yes, I got your part, John... and thanks for also listing the steps.  I'm going to have to make a note and keep it handy for a while until I get used to the process.  The part I'm having trouble with is setting adjustments (to alpha?) in order to then apply adjustments directly to the mask. 
  7. Like
    Eric5 got a reaction from Chris B in convert format/ ICC profile crash   
    You're welcome, Chris.  I hadn't tried the "simplified version" method (using a new doc from scratch), but I was able to cause the same crash as long as the doc was large enough to start with (roughly equivalent to the 12 MB DNG RAW I had been using).  Smaller docs wouldn't crash and converted. 
  8. Like
    Eric5 got a reaction from Rick G in convert format/ ICC profile crash   
    Immediate crash, latest beta while trying to convert multilayered RGB/32 (HDR) to RGB/16  under Document> Convert Format/ ICC Profile
    105be6b9-ad3c-4eca-b5f3-6e3139b7f7d5.dmp
  9. Like
    Eric5 got a reaction from studio97 in duplicate document   
    I have several paid Photoshop actions that I am trying to manually transfer to Affinity Photo using Affinity's macro format.  The problem is that many of the actions had duplicate document as one of the steps and Affinity does not have this feature.  Unfortunately, I have not found a workaround therefore I am requesting that duplicate document be added.  Thank you.
  10. Like
    Eric5 got a reaction from firstdefence in why image files on Facebook are not looking the same as in AP?   
    Well, essentially I did as firstdefence first said, went back and redid all portraits this time with a surplus of lighting. That did the trick since I did not have to artificially darken any backgrounds with gradients or try cutting out my hair for any reason. I still stuck with a black backdrop, but it was lit up enough that there ended up being no issues.

    The lesson learned here is definitely to use more lighting and more strategically.

    Thanks again all for the suggestions.
  11. Like
    Eric5 got a reaction from Extended in displace filter additions   
    Would be nice to have adjustable x and y sizes for displacement map as well as what to do with extra or not enough pixels (wrap around, etc). 
  12. Like
    Eric5 got a reaction from Extended in displace filter additions   
    Would be nice to have adjustable x and y sizes for displacement map as well as what to do with extra or not enough pixels (wrap around, etc). 
  13. Like
    Eric5 got a reaction from Extended in displace filter additions   
    Would be nice to have adjustable x and y sizes for displacement map as well as what to do with extra or not enough pixels (wrap around, etc). 
  14. Like
    Eric5 got a reaction from PaulAffinity in AP beta crash today Win 10 clean boot mode   
    New behavior in Win 10 today.  I was having the same black screen issues with an existing file I've been working on and closed Affinity.  Upon reopening and rebooting, the file had been autosaved, and I proceeded to open the autosaved version.  Screen flashes black, the file opens.  Crash report created in Win and I am attaching along with other report.
    WATCHDOG-20181213-1019.dmp
    reliabilityreport.txt
  15. Like
    Eric5 got a reaction from Mark Ingram in AP beta crash today Win 10 clean boot mode   
    @Mark Ingramtoday I decided to start Furmark's "CPU burner" before launching AP beta.  This program runs, or attempts to run, the CPU at near the maximum until I tell it to stop.  Affinity was then launched and I opened a file I've been working on.  I proceeded to perform operations (add layers, refine, adjustment layers, etc) in order to keep CPU at or near 100% over the course of 45 min and no black screening.  Unfortunately, I ran out of time and had to leave, but I don't think the CPU is the issue.  
    @PaulAffinity true about ICE.  I have found nothing better for huge panoramas.  Even Photoshop can't compare. 
  16. Like
    Eric5 got a reaction from Mark Ingram in AP beta crash today Win 10 clean boot mode   
    @Mark Ingramtoday I decided to start Furmark's "CPU burner" before launching AP beta.  This program runs, or attempts to run, the CPU at near the maximum until I tell it to stop.  Affinity was then launched and I opened a file I've been working on.  I proceeded to perform operations (add layers, refine, adjustment layers, etc) in order to keep CPU at or near 100% over the course of 45 min and no black screening.  Unfortunately, I ran out of time and had to leave, but I don't think the CPU is the issue.  
    @PaulAffinity true about ICE.  I have found nothing better for huge panoramas.  Even Photoshop can't compare. 
  17. Like
    Eric5 got a reaction from PaulAffinity in AP beta crash today Win 10 clean boot mode   
    Mark, no offense, but from what I am reading, it seems like everyone is taking guesses as to what could be wrong.  All I know is that for weeks, Affinity is the only program where I have this black screen issue.  If it were only exception errors, I could just close and restart the program and, with any luck, autosave will have saved most of my work.  However, with this issue and happening with no warning (other than the most recent behavior of Affinity becoming non-responsive for 15 min before the black screen... and unable to shut down Affinity with task manager), is making me seriously question whether I want to continue trying to use Affinity.  
    You mention CPU, but I have used test programs to stress CPU to the max (even with the fans greatly increasing in speed); test programs for both memory and GPU (also both stressed to the max).... none of these stresses have caused any black screens or crashes.  
    I have used the desktop in question to compose huge 1 GB panoramas, oftentimes consisting of 100 separate images or more, with Image Composite Editor.  Even Photoshop struggles with such sizes on this computer and I will admit will crash with no black screen, but ICE handles it well, quickly, and no crashes.   So this desktop has handled heavy duty work without fail..   
    I'll continue trying to work on this for a while longer, but even my patience has a limit.  Are there any other programs I could try to help diagnose the problem?  Is there any way to conveniently record task manager or other relevant loggers since what I provided didn't seem to help?  Any other suggestions? 
    Just looking for answers.  I really don't want to give up on Affinity unless I have no choice.  And budget at the current time just doesn't warrant the cost of a new desktop.    
  18. Like
    Eric5 got a reaction from PaulAffinity in AP beta crash today Win 10 clean boot mode   
    Ok, ran Affinity again today and, as expected, black screen occurred after about an hour.  This time, I tried watching the task manager and also ran a logging program called GPUZ for my video card.  Unfortunately, no crash reports generated from Affinity, but I did get two "hardware error" crash reports in Win after reboot (they are attached).  Note that Win acted a bit differently upon reboot this time with my screen going black for a couple of seconds twice just a few seconds apart, thus the reports Win generated.  Not sure if related, but attaching.  I am also attaching the logging text file for my video card.  I don't think the card itself has issues from the data I see in the log, which appeared to keep logging right on through the black screening.  Finally, I am attaching the error report generated at moment of black screen from Win reliability. 
    Before running Affinity beta today, I ran a video card test using a program called FurMark.  I ran both burn in and extended graphics tests for at least 15 min.  I didn't see anything unusual with the card's performance.  
    Today, I decided to see if there was any way to regain something of my screen after it went black.  I first unplugged the monitor cable from the card and then reattached.  This time, my mouse pointer was in the center of the black screen, rapidly flashing.  I could move it somewhat if I moved the mouse, but it always went back center screen with rapid flashing.  I then proceeded to try going into sleep mode, just backing off from manual shut down.  I turned the monitor off and back on.  Surprisingly, I now had a white screen with task manager on the foreground, with what looked like Affinity and the logging program at the bottom of screen.  I tried to maximize either program, but no response.  I then went over to Win menu to try a shut down.  I was able to access the menu and tried to shut down several times, but no response.   I finally shut down manually.  Upon reboot in Win 10, the screen blacked out quickly twice and as described in the first paragraph above.  
    I noticed something new with Affinity today too.  About 10 min before the black screen, Affinity became non-responsive.  I could move the mouse pointer and whatever tool I was using at the time's characteristics took the place of the pointer, but despite all efforts the program was frozen.  I kept an eye on the task manager.  Sometimes CPU would go to 90% but back down fairly quickly.  Hard drive hardly varied from 0%.  Only memory seemed to gradually increase and after I could regain task manager visibility, the reading was 75%.  
    i don't know what to make of all this.  I've dealt with computers for years, but I'm still not sure what this issue could be.  Only happens with Affinity.  From the report on the video card, I would say that it's not at fault.  I have a suspicion, but I will reserve it until I see the response I get from the crash reports I'm attaching along with the other data.    
     
    GPU-Z Sensor Log.txt
    momentofblackscreen.txt
    WATCHDOG-20181208-1755.dmp
    WATCHDOG-20181208-1755 (2).dmp
  19. Like
    Eric5 got a reaction from PaulAffinity in AP beta crash today Win 10 clean boot mode   
    Ok, ran Affinity again today and, as expected, black screen occurred after about an hour.  This time, I tried watching the task manager and also ran a logging program called GPUZ for my video card.  Unfortunately, no crash reports generated from Affinity, but I did get two "hardware error" crash reports in Win after reboot (they are attached).  Note that Win acted a bit differently upon reboot this time with my screen going black for a couple of seconds twice just a few seconds apart, thus the reports Win generated.  Not sure if related, but attaching.  I am also attaching the logging text file for my video card.  I don't think the card itself has issues from the data I see in the log, which appeared to keep logging right on through the black screening.  Finally, I am attaching the error report generated at moment of black screen from Win reliability. 
    Before running Affinity beta today, I ran a video card test using a program called FurMark.  I ran both burn in and extended graphics tests for at least 15 min.  I didn't see anything unusual with the card's performance.  
    Today, I decided to see if there was any way to regain something of my screen after it went black.  I first unplugged the monitor cable from the card and then reattached.  This time, my mouse pointer was in the center of the black screen, rapidly flashing.  I could move it somewhat if I moved the mouse, but it always went back center screen with rapid flashing.  I then proceeded to try going into sleep mode, just backing off from manual shut down.  I turned the monitor off and back on.  Surprisingly, I now had a white screen with task manager on the foreground, with what looked like Affinity and the logging program at the bottom of screen.  I tried to maximize either program, but no response.  I then went over to Win menu to try a shut down.  I was able to access the menu and tried to shut down several times, but no response.   I finally shut down manually.  Upon reboot in Win 10, the screen blacked out quickly twice and as described in the first paragraph above.  
    I noticed something new with Affinity today too.  About 10 min before the black screen, Affinity became non-responsive.  I could move the mouse pointer and whatever tool I was using at the time's characteristics took the place of the pointer, but despite all efforts the program was frozen.  I kept an eye on the task manager.  Sometimes CPU would go to 90% but back down fairly quickly.  Hard drive hardly varied from 0%.  Only memory seemed to gradually increase and after I could regain task manager visibility, the reading was 75%.  
    i don't know what to make of all this.  I've dealt with computers for years, but I'm still not sure what this issue could be.  Only happens with Affinity.  From the report on the video card, I would say that it's not at fault.  I have a suspicion, but I will reserve it until I see the response I get from the crash reports I'm attaching along with the other data.    
     
    GPU-Z Sensor Log.txt
    momentofblackscreen.txt
    WATCHDOG-20181208-1755.dmp
    WATCHDOG-20181208-1755 (2).dmp
  20. Like
    Eric5 got a reaction from midnightlightning in Do Annie's Astro Actions (PS) Work in Affinity Photo?   
    To the OP, the current answer seems to be that the "astronomy" actions originally designed for Photoshop will not work in Affinity.  I actually contacted the author of  Noel's (Noel Carboni) actions about possible development for Affinity and he has no interest, trying to instead encourage me to sign up with Photoshop. 
    As others have pointed out, macros have a long way to go before they reach the level of actions: I started trying to use a trial of Photoshop CS6 with both Annie's and Noel's installed and displaying each action step while trying to emulate in Affinity.  With Noel's, almost immediately stopped since Affinity lacks a duplicate document function which is often the first step of Noel's actions.  It's going to take a lot longer than the 30 day trial period to try and emulate the actions with the macro's current state!   Unfortunately, there is no way to convert Photoshop actions directly to macro format either as they appear to be different in nature.   
  21. Like
    Eric5 got a reaction from PaulAffinity in latest AP beta crashing video card + occasional exception errors   
    I haven't had time to fully revisit this, but I did find logs using Windows "reliability" search and they are attached. 
    blackscreen_beta.txt
    exceptionerror_beta.txt
  22. Like
    Eric5 got a reaction from studio97 in duplicate document   
    I have several paid Photoshop actions that I am trying to manually transfer to Affinity Photo using Affinity's macro format.  The problem is that many of the actions had duplicate document as one of the steps and Affinity does not have this feature.  Unfortunately, I have not found a workaround therefore I am requesting that duplicate document be added.  Thank you.
×