Jump to content

IPv6

Members
  • Content count

    57
  • Joined

  • Last visited

About IPv6

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. 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 //
  2. 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.
  3. 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
  4. 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)
  5. 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
  6. 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 //
  7. 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
  8. 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 //
  9. 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
  10. 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
  11. Please, add "Affine filter" as live filter
  12. 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.
  13. Funny enough, but seems this crash has to do nothing with new clipboard manager. Its not present on my system at all - my settings app even dont not have such entry. Here is the screen (russian is mine, english is screenshot from the article, describing this clipboard manager). Anyway, i do a lot of copy-paste for layers. In common this works well and layer copy with all inners and styles is really great feature (photoshop lacks this, for exaple). Its just this two layers can be copied... i suspect because there is no layers with pixels inside them. But this should not crash app for sure, imho
  14. Thanks for advice, now get it, will try. Anyway, AP should not crash... win10 is popular enough to make AP to adapt to clipboard manager requirements, imho
  15. Sorry, didn`t get it, i do not use any clipboard managers. Or you mean windows internals flags for something specific (hard to tell from your screenshot)? Anyway, it definitely should work on plain fresh system (i never enable fancy stuff manually). and it working with other layers without problems
×