Jump to content

IPv6

Members
  • Content count

    67
  • Joined

  • Last visited

Everything posted by IPv6

  1. There is a problem with "Apply Image" filter when metal is enabled and when not enabled. It produce different results. see screenshots. Right result when metal is NOT enabled (screenshot 1-filter/1-opts), when metal is "on" - result too much white (screenshot 2-filter/2-opts). In other cases it looks like like filter with Metal "on" try to make channel value above 1, clamping colors
  2. Curves and Channel mixer are ok, though, in beta... i was under impressions they suffer from same problem but in beta they are not. So only apply image affected
  3. Yes, the same problem exist in latest beta as well. Metal-powered execution of "Apply Image" filter in LAB mode is completely wrong // Looks like LAB values are offsetted, making everything "whitish" and causing clamping where it should not (i use this filter in macros for LAB transformations and difference is big)
  4. There is a problem with using brush tool on some layers in deep groupings. As soon as i choose BRUSH tool and move mouse over canvas (ready to draw) - all background pixels became transparent, and stay transparent as mouse is moved. Only layers in current group are visible. Note - this is NOT isolated editing, just plain editing of layers inside hierarchy. So all background should be here. Although when canvas is scrolled - border tiles seems to be refreshed for a bit. After checking conditions i can see this happens when Median Blur filter (see screenshot, at the bottom) is enabled and probably caused by brush preview... when this filter is not visible - everything is fine. See screenshots and attached file 1111.afphoto.zip
  5. See attached afphoto file, AP (latestbeta) crashes when copying layer (group of layers). Win10, no external clipboard managers used, windows clipboard manager also disabled crash-on-copy.zip
  6. I am using PSD format for exchanging images and with latest beta found a bug in PSD export: In resulted PSD all layers, that are HIDDEN in original AP file - all of them are completely empty. They are here, they are named properly and stay on right hierarchy place - but fully transparent, no pixels in them. Layer, that was visible in original AP file are exported as usual, with all pixels This happens with all 3 PSD export presets
  7. Problem still exist in latest beta (367) As well as on latest beta on Mac
  8. Procedural textures is a greate thing, but currently it is limited to channels of current document. Please, add ability to set "color mode" to add operations over other channels - especially LAB channels (in RGB document)
  9. Congrats for GM, this release really superior to 1.6! In some areas it clearly better than Photoshop now, which is big archivement imho It`s a pity though, that PSD export still has problems with hidden layers (just checked with GM)... they are exported completely empty (no pixels in layer in PSD). Which is kinda looks like a bug - exporting hidden layer did not mean destroying its content (but this what really happen upon PSD export). 1.6 didn`t has such problems, all layers were properly exported "as is" with content, even hidden. Hoping this will be fixed later
  10. Seems like a bug... but have to note there is simplier way to get Lab-Light layer: just use "Apply Image" filter -> Equations in Lab mode and set "SL" for all channels You`ll get lightness in white and black much faster
  11. Since there is no "destructive crop" bringing document size to proper dimensions can be very tricky. Thanksfully there is "Rasterize and trim" option for Pixel layer. But MASK layers can be bigger then document too! And currrently there is simply NO way to change its size to fit document bounds. In whole application. Which is sad // Suggestion: Please, make option "Rasterize and trim" work on masks too so they are trimmed (rasterize part ignored). Or, add additional action to layers - Trim. Which wok on layer of any kind and do DESTRUCTIVE trimming. Because frequently this is exactly what is really needed.
  12. i have different "template" files of different sizes and frequently moving layers from template files (bigger) to production files (smaller). Then i position bigger layer in document and trim it. This is greatly speeding up my workflow. And for this workflow layers (including masks) of "non document" size are frequently annoying, since when i add different effects (like blur, meadian, etc) - bigger layers frequently "leak" color (usual layers)/transparency (mask layers) from the outside of the document bounds. Layers can be instanlty trimmed but with masks only cut&paste works - and in deep hierachy its a pain to shuffle this stuff after paste. Would be best to have destructive crop, in fact... i have no idea why devs so resist to just do real usual crop for all invisible parts //
  13. I`m using AP both on Windows and Mac, always latest betas and it was ok until latest Mac beta. Now file (afphoto) created in mac beta 122 gets immetiade crash in windows beta 293, when opened. Tried several files (created in latest mac beta 122), same result. Once i get a message "file corrupted" without a crash - but in other cases AP Win-293 crashes when opening Max-122 afphoto file. Files created with previous betas work as usual (no crash, opened normally in both Max/Win)
  14. IPv6

    Win-Mac afphoto interability

    you probably right, but any such changes was always marked as "file created in old version" message before, no crash, no cryptic "file corrupted" messages. so this still may be a sign of missed/unwanted change. file format change should not just crash app, even beta, imho
  15. I have a file with size of 5760*1080. it hase a lost of adjustments, that cover whole area of document. And after rasterizing (flattening) file - adjustments on part of the document are lost completely // See screenshot and a file attached. Expecially third frame before and after rasterization Really critical... Is there is a size limit after which AP gets unreliable? // bad_raster.afphoto
  16. There is something strange regarding primary/secondary colors management in AP. This really confusing and very common reason of redoing things... and this NEVER happen in Photoshop. Specifically some tools randomly change primary and secondary colors. 1) For example IF you select color in "COLOR" panel (just picking on gradients) and then select brush tool - your primary color... will be changed/swapped. Why? Who knows... Looks like a bug, there is no reason for changing primary color, specifically selected a second earlier 2) Same with selection. select brush tool, pick color, do some strokes. Primary color is the one you just picked. Then select area and choose "Fill with primary color" from menu... boom! You primary color changed and layer filled with something completely different because selection "SELECTION" tool switched colors! WTF, is this made specifically to ruin the work? )) First screen before activating select tool. Second - after. Made in latest beta.
  17. i`m aware of rendering issue, that`s why screenshots in low zoom made - there is flickering, etc in case of higher zoom. In this case it`s NOT rendering. after rasterization lost adjustments can be seen on any zoom level.they just lost on 1/3 of the document. Adjustments work before rasterization. And partially lost (not applied) after rasterization. With big document - such "partial rasterization" can easily go unnoticed... and thats sad
  18. Please, add "Smooth tool" to liquify persona. Photoshop already has it and sometimes this is invaluable to fix "messy" areas. Smoothign should just mix current state with original (under cursor) with very low divider/percentage
  19. Even if this is just memory-related issue - though 5000*1000 quite NOT a big size this days - and i have decent comp/memory - its still expected that AP will warn about issues IN ADVANCE, so user would be able to split up the work. It`s not always clear to see that rasterization just "forget" about part of adjustments stack... finding this after several steps down the pipeline can be disastrous //
  20. i see... yep, in terms of mixing with original value. But turns out i was wrong about photoshop smoothing - its working not like that, not like i described... something more sophisticated Smoothing adjust messed part of the grid to be on line (on grid with some regularity) to the outer grid - which can be already rotated, shifted, etc. it`s not "original" positions. it`s "current" positions, just not under brush tip. smoothing align mesh under brush tip to the grid out of brush tip. recornstruct targets on original position regardless to the state of the outer part of the mesh... so behaviour is not the same, unfortunately //
  21. Current way much more usable then previous... in my case most of the time gradient used to tune masks - and one click to change "final" color/optionally first is the fastest way to make thing done. less clicks, no need to target precisely into small buttons like in previous design, etc. So current UI is better than previous, imho
  22. Please, add "Affine filter" as live filter
  23. There is a "Displacement live filter" and in its current state it is almost useless // Please, add a direction to allow displace work on it or add separate sliders for X and Y displacement.
  24. Open attached afphoto file, select two layers as on screenshot and press Ctrl-C. On my system (Win10) this crashes Affinity photo immediately // 111.zip
×