Jump to content

Taluyaq

Members
  • Content count

    24
  • Joined

  • Last visited

Everything posted by Taluyaq

  1. The adjustments gallery is a nice gimmick and some of the shortcuts are even quite handy. But for some tools there are no previews because of their complex nature and for others the previews carry no useful information at all. No serious photographer takes on photo editing by tapping together random modifications by thumbnails. The gallery approach also sacrifices swiftness by focusing on misguiding optical stimuli. It took me ages to find the tool for selective colour correction (“HSL adjust”, which lacks orange and purple, by the way) from that messy gallery because the thumbnail did not nearly look like something I would like to do with the image in question. But maybe it's just me. Any thougths on that?
  2. I am sure you guys at Serif have some sort of roadmap for the further development of AP. But with any new software there pop up feature requests from users that you deemed not a priority right now or you even might not have thought of at all. At the moment the forums start clogging with requests, some new threads doubling old ones, and, of course, some quite outlandish demands. What about setting up a poll where we may vote for most needed features to implement? That would clear up things a bit and you would not need to plow through this thread jungle to keep up.
  3. Taluyaq

    Modifier Keys

    Modifier keys are a standard for every serious graphic/photo editing software for decades and they will not be gone any time soon. There is yet no sophisticated method to replace them and if so this would introduce a steep learning curve and break compatibility with professional user's skills as well as with Serif's very own desktop apps. AP's approach of tapping back and forth shows that they also have no breakthrough on this up their sleeves. But that's totally unnecessary, anyway—just add modifier keys to speed up workflow and made it more familiar to pros who are used to use them. I attached a thumbnail how this is implemented in ProtoSketch, just for inspiration.
  4. If areas outside the canvas are not intended to be seen they should not show up in the layer thumbnails as they did for me. See another thread for details: https://forum.affinity.serif.com/index.php?/topic/42088-layer-thumbnails-produce-irritating-ghost-artifacts/
  5. During construction of a transparent-vignetted picture I stumbled upon misleading depictions of the layer thumbnails. They show border artifacts which aren't really there (white lines along the borders). At least I cannot detect any pixel leftovers while examining the image on another background. And if they were there this would be a bug because I inverted a selection to get rid of the outer rim and the border pixels should have been fully included by this operation. See attachment for clarification.
  6. Hi Sean, thanks a lot for getting that sorted for me. Now that I know it seems so obvious and I should have realized it—sorry for bothering you.
  7. While not exactly being a bug the interface behavior perhaps could be adjusted: In many cases the keyboard covers parts of the interface, e. g. buttons, form fields, or other stuff. Of course you can always shut down the keyboard to reveal the whole thing but it would be a lot more convenient if the interface or parts of it either move up to reveal simple ok/cancel buttons or at least being scrollable while the keyboard is active to speed up the workflow.
  8. It's done. Thanks for getting back to me on that issue and sorry for the delay. I am only able to check the forum every couple of days …
  9. After using the development persona on a rather large image (about 9,800 × 3,900 px) AP presented a grayed-out screen with a spinning wheel that lasted for about five minutes. That reminded me strongly of the nineties where I used to wait several minutes for Photoshop to get some blending done ;) But this is not my complaint. I recognize that it may take some time to apply changes to a large image file. Though, you should not leave the user with just a spinning wheel on a gray screen. Please consider adding a progress bar so one can determine whether AP is still working or already crashed (what might not be that outlandish, given the many crash reports around here).
  10. I am aware of Photogene and its abilities and I would most appreciate those features making their way into AP. But I also believe this could be quite a feat to accomplish because of the necessary workarounds. It is not impossible, of course, but the simpler goal might be enabling transparent back-writing of changes to an image file on the device's Camera Roll first and then heading for batch processing.
  11. Andy, thanks for the clarification. I have now a better understanding of the gallery. Your preview of the changes is exciting and should make this feature enjoyable for everyone. Maybe you could consider switching on and off thumbnails on an item by item basis since some of the more frequent used presets would be nice to have as visual cues while others can go without … Yay!
  12. It seems there is no simple way to delete a selected area at once. Am I supposed to use the Eraser Tool for simple cleaning operations? I worked around that issue by using the cut-to-pasteboard command in a multi layer image. But trying to apply another cut of the same selected area on more than one layer resulted in deleting the whole layer. That is clearly a bug. Edit: Re-opening the image made the problem disappear. I can now repetitiously cut a selected area from different layers to the pasteboard and delete them in this manner. Also: Please consider offering a command to convert a current selection to a cropping frame.
  13. As far as I am aware the file contains only pixel layers but I am not sure what to make of an “image layer”. Could not find it in the documentation. Maybe I could get a hint on that?
  14. Why is not possible to adjust a cropping frame in Transform Studio? Why does a cropping frame not snap to layer borders? Would really appreciate if you could make that happen. Also (already stated in an earlier post): Please consider an option to convert a rectangular selection into a cropping frame.
  15. Thanks for getting back to me on that topic. I am aware of the possibility of making manual adjustments to the cropping frame respectively to set it to a custom size. The problem here is that I not always know the size I need because there is no (at least no easy) way to determine the dimensions of specific layers, especially when they are partially obscured. Of course I can always zoom in, so snapping would just be a handy shortcut.
  16. While fine-tuning the position of a selection by number input in the Transform Studio I noticed that the anchor point settings only worked once and further changes would not be reflected by the input panels.
  17. It seems that selections are not “snappable” which is a good thing in general. But sometimes this is exactly what would be most helpful to spare time on calculating the right position of a selection frame. I could not find any possibilities to make selections subjects to the snapping settings, too. Is this by design or do I miss something?
  18. I totally agree. But when it comes to editing AP will need to put the changes somewhere since the Photos app does not support complex manipulations and actionable change logs as AP does. As with Pixelmator it is unavoidable for AP to create (at least a temporary) image for its own purposes. So, there is always some kind of “import”, though not noticable. It should, however, be possible to write the changes back into the same file in Photos without creating a duplicate—that feature would be highly appreciated :) As for batch processing, to my knowledge Photos does not allow writing back more than one image at a time. AP would need to implement some sort of pseudo batch processing to accomodate the restrictions of iOS. That would involve imports as well. But maybe Apple changes the way how that works in future iterations of iOS.
  19. Taluyaq

    IPTC/EXIF editing abilities

    I too would appreciate editing capabilities of at least the most important EXIF/IPTC data. But that seems to be quite a challenge since it took even Adobe ages to integrate basic meta data editing into Lightroom for iPhone. Still no signs from them of bringing that on the iPad. Even Apple's own Photos app does not allow you to change the photo description on an iOS device, let alone other parameters. Seems they do not really get what's important to pros nowadays. It would be nice to have the AP programmer's view on that topic. Maybe such a feature is not important enough from an economic standpoint for the time being?
  20. Taluyaq

    [Fixed] Editing text boxes

    I encountered the same bug today while editing a photo for a class on a iPad Pro 9.7". At the first tap on the textbox it gets covered by the keyboard. After panning the textbox back into view every hit on the keyboard moves it out of sight again. No way to see what I'm typing. Also: Why is there no support for text replacement? I can't even use the iOS two finger gesture to move the cursor or mark art text (haven't tried frame text, yet)? So there is no way to do proper editing at the moment.
  21. Just got back from checking with Pixelmator. Same thing, the image size is correct. Checked also with Photo library on my Mac—it displays the right size. Now, we need to take into account that we are both working with self-provided samples and thanks to the occlusive nature of iOS it's sometimes hard to determine what really happens. It's not even possible to properly track a file by its name because it's renamend whenever it is handed over to another app. So I cannot reproduce your issue but nevertheless I see your point. I can only come up with one alternative explanation: Is it possible that the image file you are working with got compromised along the way so that its actual size IS now indeed the screen size of your iPad? Happend to me a couple of times with some apps which were either not able to retrieve the original file or not capable of working with full-sized images in the first place. At first I didn't realize the flaws until I accidentally discovered artifacts and pixelation in the affected files while working with them later. That would account for your last point. For the record, I also checked if the files I claim to be in their original sizes ARE really preserved and not just displayed as full-sized by some info labels: looks good, zooming in did not reveal any signs of degradation. Hopefully the problem evaporates with the developers both of iAP and iOS ironing out the kinks, and thereby introducing new ones ;).
  22. I took the time and did a couple of tests with different sources of one and the same image. Here's what I got: First, I copied a photo from the Photos App on my Mac to Google Drive. Checked that it was completely downloaded to my iPad and then tried to import it to Affinity Photo for iPad (“iAP” from here). Result: inconclusive at first, since iAP failed three times retrieving the file from Google Drive as a document provider (from within the Locations sheet) with an error message. But sending it directly from Drive or Google Photos to iAP did the trick—import at full size. Same goes for import from iCloud, whereas iAP was able to access the file on its own from the Locations sheet. Second, I saved the same image from Google Photos back to the photo library on my iPad and tried to import it from there into iAP. Success! iAP imported it at full size. Third, I tried to import the original photo (which I ealier had copied to Google Drive) into iAP. Fail! Was imported only as a screen sized preview. But I doubt that iOS Photos is to blame here since other third party image editing apps work just fine with the same pic right out of the photo library (Polarr, Snapseed, Adobe). I suspect this is a problem with requesting the proper sized file version by iAP, a bug after all. Therefore I'd like to suggest to remove the “solved” mark to keep the developers aware of it.
  23. I think we are talking about two different problems here. One seems to be flawed import from an outside source to the iOS Photos app, but I cannot reproduce the issue. The second is flawed import from iOS Photos to Affinity Photo. The latter only ever imports a preview picture exactly the screen size of the device, in my case 2048x1536. Even when the full size image file resides directly on the device, importing it to Affinity Photo only get me the preview image. Photos taken within the app, on the other hand, appear in original size. Mind you, we are talking about JPEGs—this is not about the already known problem with RAW import to Affinity Photo.
×