Jump to content
You must now use your email address to sign in [click for more info] ×

hisuku

Members
 View Profile  See their activity

  • Posts

    30

  • Joined

  • Last visited

 Content Type 

Everything posted by hisuku

  1. hisuku
    So we have the big version 2 now and Serif staff still thinks its not necessary to keep metadata in all exported slices
  2. hisuku
    Its hilarious, honestly. I currently am forced to use a dedicated metadata management software and copy every set of data over manually for the slices. Its even more funny if you consider that they managed to add an entire dialogue telling you if or if not the data will be included after leaving the mark checked.
  3. hisuku
    Yes, as I said, its hard to replicate. Sometimes it happens often sometimes not at all. I have a feeling (really just a feeling) that it happens more often if you zoom on detail like in the example and often drag the image around to work on it. Combined with spamming the program with retouching.
  4. hisuku
    Sorry, I know this took quite the time. It does appear at random so most attempts failed when I tried to recreate the situation. I finally managed to get the bug recorded. Even though there is nothing to see. Just me encircling stuff like a maniac. What the video doesn't show is my pen movement: I encircle the area meant to retouch and drag to any destination place but nothing happens. I don't change anything else and it always appears when I do a lot of retouching mid doing so. Like I do 20-30 small changes with the tool and suddenly nothing happens anymore. I have to leave the project and enter again for it to work again. RPReplay_Final1618500473.MP4
  5. hisuku
    I have noticed that you can set the marker to include metadata in the export options field an it even saves that state. But it still doesnt include the data for slices but leaves a small info-button telling you if the data will be included in your chosen slice or not (the text is different for the main slice where you get your meta). How programmers can take the energy to lay this path instead of actually using the user selection as it is and writing that little information beyond my understanding...
  6. hisuku
    Yes, it does still happen. Not very much details I could provide at this point. Just open up a dozen files or two and try closing them without applying changes. It will not crash but at some point it will start taking small eternitys for closing a file without applying changes (i went the patient path out of curiosity: closing a file may take between 2 to 5 minutes) If you aren't patient enough and force quit the program it will of course start up again with all files opening again and you are at square zero again. the only path out of that loop is that with each restart it may open one or two files less than before.
  7. hisuku
    Yes, that is what I meant. Well then we have to change the topic in 'retouching sometimes wont be applied' because thats what happens. But sadly I do not have an recipe to recreate a problem. I thought it would be because of the locked layers but if that is not the case, it has to be something else.
  8. hisuku
    Hi there, In the Export persona, is there a way to include a specific layer for one slice only (between various other slices)? So far I know I can exclude a specific layer/group of layers for all slices by unchecking the eye mark. But I want to do like the opposite. For example: I have a usual project file with the original image, various changes in multiple layers and groups. On top of that is a soft-proof profile placed as well as some smaller tweaks for printing. Now if I export those image I want copys for the digital media without those printing tweaks, so I simply uncheck those. But for printing I want a dedicated filename_print.tiff with those printing tweaks applied on top. I know I can go the long road and do two exports but that somewhat defies the logic behind the export persona. And if I try to create a slice from a selection of layers it creates one slice per layer which obviously also isn't what I want.
  9. hisuku
    I appreciate it, thank you
  10. hisuku
    Hi there, I just noticed that the ipad version doesn't stop the user from retouching protected layers immediately (repair, clone etc tools). It takes a few seconds after opening a project until the protection starts working and changes wont be applied anymore. I have neither tested if the same happens on the desktop version or if other types of changes like painting on the layer would work as well.
  11. hisuku
    Yes, that is absolutely logical and from that point of view it makes sense. But I noticed the battery drain before I started using the liquify layer. Since you asked I mentioned the liquify live layer but honestly I just mentioned that one because you asked and I knew nothing else. Can we just forget the mentioning of the layer at all? Of course it makes sense that the liquify layer will use more energy (but honestly: 1% per minute would still be insane if it only were that!). As mentioned its hard to exactly replicate. But using the same project files still left on the device its using more battery than before. I havent benchmarked that before and after so its hard to put the finger on hard numbers and I can only tell what I think have experienced from my subjective point of view.
  12. hisuku
    Please dont close this since its not (only) about the live liquify layer but general sluggish behavior and battery drain. So could you please de-duplicate this? Do you have any idea that it may be tied to certain functions like filters? I wasnt able to replicate the problem exactly. Sometimes it drains a lot of the battery (30% in half an hour which would be around the same you experienced), sometimes its very little. Could you please try a very basic project in comparison (like 1 layer and only simple pixel edits)? But even then we could argue that more complicated features need more calculating power and thus more energy. But 1% per minute is insane! Oh and welcome to the forum! I am still new here myself but the people are very friendly and helpfull. We are in good hands!
  13. hisuku
    Since 1.9.1 is out I did test again. No changes so far with export taking 2:07 minutes for my example file.
  14. hisuku
    Thank you. I am looking forward to your results. If there is anything else I can provide: Please let me know.
  15. hisuku
    Hi there, Affinity Photo freezes almost every time when I close an file without making a change. You would expect it to close the file smoothly but even without having to safe anything or even loading another file it often produces just freezes. I am using a rather old iMac 2011 with High Sierra. Can someone confirm the situation? I also included a copy of the problem report the system creates for sending to apple. Maybe there is something useful in there. freeze report.txt
  16. hisuku
    Has there been anything happening since then? I am still guessing its more on the side of logi to implement it in their driver but either way it would require communication between both sides.
  17. hisuku
    Where do I have to go to then, if I was hoping for feedback and discussion over a suggestion?
  18. hisuku
    a forum isn't really that useful if a topic dies in fresh without being seen...
  19. hisuku
    its mostly with liquify layers involved (I have an separate topic ongoing about that with an example file included). For exporting an image (to take the example from the other topic) its 2:30min with an liquify mask applied on my iMac while it takes only 4 seconds without it. Yes, my iMac is old (2011) and I do expect a slight decrease in performance with every update but thats just incredible. I have worked a lot with live masks before and never had any issues but the liquify live mask is on a whole different stage.
  20. hisuku
    Rasterizing left my iMac running for 2:30min (which left even me surprised and I was prepared!) and took 80 to 90% of the total CPU during that time (simply all it can get). Exporting does take the same time (actually like 15 seconds less when I stopped the time, but the processor may just didnt have anything else to do at that moment). Without the liquify mask its around 3-4 seconds. On my MacBook its 27 seconds to rasterize, around 20 seconds to export and again around 3 seconds to export without the mask applied.
  21. hisuku
    I want to suggest making it possible to keep the original files exif/metadata in ALL slices set. As far as I understood only the very first slice which is automatically set (not really a slice, but just the whole thing called by the projects name) keeps that data since it works with the same engine as the default export function (the one you can use over Data>Export from everywhere, which you can set to delete all exif data if you want). All other manually set slices will always loose their exif data and there is no option to change that! I imagine it to be not that hard to implement it that way that you have the ability to write exif in slices as well (since its only very little data to copy after the file creation), probably even by default. You can always set the options to ditch the exif if you want, just like with the normal export function. Yes, you can currently workaround by cropping multiple times in the normal Photo Persona and its nondestructive as well. But that defies the whole sense behind the existence of the export persona! If I change even the slightest thing in the image I have to redo every crop and pray to the crop gods that it is somewhat cropped the same as before.
  22. hisuku
    Since there is a dedicated option to exclude the metadata at will, wouldn't it be the most logical thing to assume you can also include them at will in anything. I think the whole sense behind the export persona (which I love to use) is that you don't have to change your crops multiple times. If I want to change my picture even the slightest and also want to export an uncrossed version I have to go back, export, crop and export again. And pray to the cropping gods that my new crop is close to the previous one. What I am pointing at is, that it is very inconvenient to offer an advantage while taking something else people want. And including metadata from the file isn't really that hard, c`mon.
  23. hisuku
    can confirm as well. macOS 10.13.6
  24. hisuku
    Hi there, I noticed an overall drop of performance with the newest version. Especially when liquify masks are involved (but not necessarily bound to the use of liquify masks). It will often react with huge lags even with only using the GUI (selecting tools, opening menus, switching personas etc but not doing anything to the file itself). Can someone else confirm? Update: Its not only sluggish but also a first grade battery consumer. 30% in half an hour. My device is an iPad Pro 2nd Gen 10.5" with the latest OS installed (14.4 as today).
  25. hisuku
    Hi there, is there a way to increase the thumbnail size in the .afphoto file so one can judge his documents with the macOS preview (hitting the space bar)? Natively it seems to be in a size of something around 342x512. PSD documents in comparison seem to include larger thumbnails you can "zoom" in. Sincerely, me
×
×
  • 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.

 Accept Cookies  Reject Cookies