rpaul

Insert imogi of hand palm bouncing off forehead. Thanks Walt, for covering the initial bases. I've been working with first generation of Apple pencil since 2017 and haven't had much time with the new setup. Guess I need to read some more. incidentally, another thing that kinda threw me off was that double-tapping on the screen does work for the View tool.

So, I just got a new iPad M4 and it's pencil. I wanted the double tap feature to toggle between paintbrush and eraser. However, the double-tap feature doesn't seem to work with the paintbrush. I did change the paintbrush menu option to eraser in the Pencil Setup screen, but when I go back to my project, double-tapping just lays down a couple faint paint marks on the pixel layer. Double-tapping does work in View mode, however, zooming it to full screen by default. I tried it on my old iPad pro, and it didn't work there, either. I'm kind of thinking that it was disabled or made harder to implement because it would interfere with the actual painting process too much. But I did want to try it, at least. I did find out that the new pencil can be squeezed. That feature currently brings up the menu at center screen. Maybe there's a way to utilize it differently? Any advise helpful. Paul

So, maybe I didn't search hard enough but, I didn't see a reference to anything like this. I have Affinity Photo 2.x running on my Windows 11 tablet. I'm wanting to undock it from it's keyboard and take it outside for some fresh air and use it like I used my older iPad. One thing that I liked on Affinity for the iPad was the ease in which I could hide most of the tools and open up the screen for actual image manipulation. With the keyboard attached, I could just hit the tab key. Without it I have to go to "view" menu and drag down to "toggle UI", which seems cumbersome to me. I realize that if there was a customizable option placed on the toolbar, it would go away when "toggle UI" was enabled. Is there anything I can do to make this option more tablet friendly?

I've been experimenting with the Deform filter a lot recently. Although its a bit buggy, it seems to have some versatility that I've never been able to achieve with Liquify or Mesh Warp. First, as with the Mesh warp, you can go back and re-edit a deformation arbitrarily, which you can't really do with Liquify. But it also seems to be a bit more targeted than the Mesh warp. So, I feel it works best when I am trying to re-map an image on to another with precision and with fewer steps in the long run.

Five years later, I agree. This is a very useful tool for many situations. It would be nice to see it polished up and maybe reimagined to some degree. The above video is only a crude example of what can be done with it.

I second these two

It's been a while since I've posted anything here. Just curious what the status is for address this particular bug. Reinstalling didn't last long before the problem came back for me. Thanks

I managed to get it to work. Can't remember what I did but since it involved making a very large selection, I think I broke the process down somehow.

Okay I understand this, thanks. But it was my understanding that the beta had "expired", which is what it says if I try to launch it. So, is there a way that I can reanimate my copy of 1.9? Continuing to use 1.9 would be perfectly fine.

Is there a planned release date for 1.9 retail for iOS? I'm hoping to open the files I saved in the beta version

I'm looking for version 1.8.5 of AP for iOS. Is there a way that I can get it? I read that I can open files that were saved from the 1.9 beta in this version.

Um, is it actually possible to revert to a previous version of Photo in iOS? I guess I'm looking for 1.8.4 or 1.8.5.

I would say that I'm am an inexperienced beta tester. So, I'm just looking for some advice on the testing process. I did read the bold disclaimer on doing 'real work' before I downloaded the new beta. However, the only way that I am going to put the new beta through its paces is to do 'real work' with it. And I have. My iPad says that I logged an average of 6 hours and 20 mins daily on this app, which I assume includes weekends too. I have reported some issues through testflight messaging. I'm assuming (and maybe this isn't so), that any crash that I experience gets logged and adds to some data set. I see my voluntary test of this application as a contribution to the development of a very important and unique resource for the iPad. And I am happy to do this but I'm never really sure that my contribution is that helpful since I don't really get any feedback when I do report something or if the application self-reports when an error occurs. Also, I've been continuing to use the 1.9 beta until yesterday since keeping it in the app history allowed it to be accessible. But, I somehow lost the link last night. So now, foolishly, I am in the same predicament as some of the other users who posted here, not able to open many of my .aphoto files. Fortunately, no contracts are riding on this since I'm just a hobbyist. I will see if I can reinstall 1.8.5 or wait for the 1.9 retail release. So, in the future, I may leave the beta testing to the more experienced professionals and just complain when I have an issue with the retail version Thanks

I realize the beta phase is over but I'm still using 1.9.0.199 since my files don't seem to open in my non-beta version. I'm having trouble selecting a sharp precision rectangle out of an image without it pasting it on a new layer with a feathered edge. (See video) Also, when I use the transform studio to alter the marque I have to select the arrow tool and then go back to the marque tool in order for it to work. Not in the video, I rasterized the image before making the selection. Paul Tompkins FullSizeRender.mov

Actually, it still doesn't work the way that I expected. I was under the impression that raising the low end of the alpha curve would allow any virtually invisible pixel would show up. Instead it just brightens the rgb values. Right?

Hi, I'm happy to see that the alpha channel control in the curves tool works better now. However, shouldn't it work whether or not it is located above the bitmap vs nested within the bitmap? It seems that when nested it has no influence on the graphic. Thanks

Im not a professional, but have spent several months on AP. What seens to work best for me is to find a way to break the project down into separate files, do a merge-visible and assemble the merged images into a final version.

So, I've had similar issues with lag and occasional crash using some of the simplest tools. But I figured out that it seems to happen on layers that have been resized, and if I rasterize the layer it works better.

I still would like to know what resources are taken up when keeping documents loaded in the main menu. Do they take up RAM? Are they stored as some kind of virtual memory?

I figured. Thanks.

Thank you Callum. I will see if I can find something reproducible. I did realize finally that I wasn't clearing the history which makes a BIG difference in file size. It would be good to have a better understanding of how some of the actions, which may be simple to use, have an impact on computer resources. I guess a lot of them are standard algorithms which I can research somewhere. Not sure how much I care yet. I just see that the more sophisticated I get with CG, the more my file sizes balloon and computer bogs down. So, I would think some understanding of this would help me parse my workflow.

So, I'm just wondering if its a more efficient use of computer resources to create separate smaller AP files and embed them into a into a master file. I was hoping to find some kind of option where files could be 'linked" and therefore reducing file sizes. But I'd like to know if embedding has advantages other than organizational. Thanks for any feedback.

I'm not sure if this question is answerable, but I'm trying to get a sense of when I'm reaching the memory/complexity limits of editing an AP file on my ipad. I have a 2nd gen 12.9" model with 64gb drive(only 17gb available)/4gb ram. I'm working on a 422mb file that is 5000x5000 8 bit resolution and at least 100 layers. I just started having troubles with the program crashing and I'm not sure if it's a bug that I can address or I'm just reaching the limits of what I can do on this system. So my main question is: Is there an idea of how much ram or disk space I should have available to work on a file of a certain size? I have to do more troubleshooting, but wanted to see if anyone has any ideas around this. Associated with this question is how much overhead does it take to use certain features in AP? For instance: - Does grouping small layers of bitmaps add to the file size/computational complexity much? Or should I just rasterize/flatten into larger bitmaps more often? - Using certain adjustments versus rasterizing those into the pixel layers? I know that using live filters takes more overhead. - Does the number of files loaded onto the home menu influence the editing of a single open file? I noticed that they open pretty quickly from the home screen versus opening the file directly from another location. So, I'm assuming that anything on the home screen is also loaded into memory to some degree. I'm not going to be able to upgrade for a while, so need to make the best optimal use of what I have. Thanks

Has hiding the selection line been asked about before? I used this a lot in PS and it was very helpful when tweaking/aligning the image portion to see behind the marching ants. Also, even though I'm impressed with the image adjustment tools, some buttons for moving a single pixel at a time would be useful as well. Thanks

I'm thinking it would be nice if there were more instances of the message: "Do you want to commit these changes",before one can move on, as there is for transitioning from some of the other personas. I tend to make the same repetative mistake of not pushing the check.