Jump to content

AlainP

Members
  • Posts

    1,167
  • Joined

Everything posted by AlainP

  1. I calibrate my monitor with Spyder5 Pro and use the calibrated profile. If I setup AP to use my Datacolor Color profile there is no more pink in the clipped highlight areas. It only shows with the default sRGB color profile. But this is not a problem in AP 1.5.2.69.
  2. If that can help... An Exposure adjustment as low as "-.2" fixes it. The pink completely disapears. The loss of exposure can then be brought back with "Brightness and Contrast". An easy workaround untill the next version.
  3. Thanks to all team members for your good work ! I don't know if it's a bug or particular to my system... each photo I open (JPG or afphoto) shows pink around the clipped white area on the picture. These pink spots don't appear in the exported JPG. It also disappears If I click on "Auto White Balance", but not on very clipped areas. It looks like some "left over" clipped area indicator.
  4. Just made the test... same issue in 1.6.0.72 but no problem is 1.5.3
  5. No issue with the color picker tool on a curve layer... Win 10, i3, Integrated Intel HD graphics.
  6. On my side, switching from panel to panel is as quick in Light mode as it is in Dark mode, no differrence at all...
  7. Confirmed ... AP and AD
  8. In Develop and Tone Maping personas the "Apply" and "Cancel" text is missing in the buttons. The small square buttons are there but nothing in it. And Tone Maping has never been so slow to finish loading.
  9. Both programs installed perfectly (both .69 betas had been uninstalled before, everything runs fine, except this: Once "Stabiliser" has been enabled, the cursors disappears when it gets over any panel, left, right or top. Even if Stabiliser is disabled the cursor doesn't come back. It happens with my Wacom Tablet or just the mouse with tablet disabled. If Stabiliser is never used there is no problem with the cursor.
  10. Quick startup here too, 11 secs. Download of the file took 20 seconds here in Canada (120 MB Download speed)
  11. Installed smoothly, no problem so far. Wacom tablets works very well (worked well also in .66)
  12. Installed smoothly, no problem so far. Wacom tablets works very well (worked well also in .66)
  13. Just tried it and I don't have this problem. I had the same problem a while ago but it was fixed in one of the Beta. WIndows 10, basic Intel Graphics.
  14. Just made the test... The "brush preview area" stays there when you get out of quick mask, with marching ants, but it's not selected. Only the original selection stays selected. It looks more like a video redraw problem.
  15. Confirmed, Windows 10 Creators, Wacom CTH-470. Resizing Artbord is really weird, you put your pen on your desk and the artboard keeps up resizing and flickering.
  16. Windows 10 Creators update, i3 with Intel Graphics, 6 Gb memory, and Wacom Bamboo CTH-470, quite a basic system. Everything works very well and quite speedy for the configuration I have. I can reproduce what Stuart_R mentionned, moving handles of a closed object made with curves, makes the fill running behind to catchup with the move. But, to see that lag, I have to move the handles extremely quickly, something I never did and will never do. It also have to be a large file at high resolution. At 192 dpi I don't see anything. So, I wouldn't say that's a problem on my side. But I can understand that when your computer is a "monster" this is probably something that you don't expect.
  17. I repeated these steps and I don't have any problem at all... Windows 10 Creators update, Wacom Bamboo CTH-470, Intel I3 with Intel Graphics
  18. Works perfectly so far. Wacom tablet works very well, and no mouse scrolling problem.
  19. Why latest beta .63 wouldn't become the new "official release" while waiting for a new beta, I didn't have any problem with it. This way, we could keep working for one, and we would have all our imported brushes, styles and other "imports". I can't work with the .54 release as it shuts down by itself all of a sudden and I loose all my work... and then.. my blood pressure goes up.....
  20. As nobody from the Developper Team is rushing to give us an answer, I like to think that they are working very hard to come up today with a new Beta, or even an official release, that is very much improved, blazing fast, with all we asked for..... and please... don't wake me up..... . . . Just kidding.... I'm sure that they are really working very hard, and we are like kids on Christmas Eve....
  21. Photo Beta expired, same for Designer Beta.... quite frustrating.... this should not exist for owners of the full versions. I use them both almost every day for my work and having to go back to the "official release" and to the bugs that were fixed in the beta.... I hate that. I appreciate very much your software... but I have to say that you missed this one.
  22. I just customized the toolbar moving the assistant icon to the extreme right and everything went fine, no problem on my side. (1.5.2.63 cb on WIndows 10)
  23. Whining for 50$ ... that's what we call "real" professionnals.... I can't believe what I read her....
  24. I made a similar test. Loading a CR2 file in AP latest beta took 18 seconds. Opening the same file in AD latest beta took 8 seconds. But in AD there is not much I can do with this RAW file.
  25. I am quite sure that CMYK color works as it should in AD. You will never get the same colors for RGB to CMYK and vice versa. I worked many years with Photoshop and a CMYK 100% Black is never a "pure deep black", it renders exactly as AD does. A "true Black" is something like " C75 M68 Y67 K90", but there are many "recipies". C0 M0 Y0 K100 is usually used for text printing over a background. There is a short article on Blurp site that explains this: https://support.blurb.com/hc/en-us/articles/207792816-CMYK-black-values and if you can also "google" for "true black CMYK in PS".
×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.