Jump to content
Our response time is longer than usual currently. We're working to answer users as quickly as possible and thank you for your continued patience.


  • Posts

  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Not a huge issue, but slightly annoying iPad Pro 2018 1TB EDIT **Not sure why I've got 2 videos here** RPReplay_Final1596633213.mp4 RPReplay_Final1596633213.mp4
  2. I still get a line and a dot unfortunately. I would rather only allow the context menu to be dismissed by pressing OK, rather than having to go back in history/erase whenever I forget. But there are bigger things to worry about!!
  3. This has regressed to prior .168 Beta with the last two versions ( and previous) In other words the line is being drawn again after tapping off the context menu.
  4. Thanks for letting us know. I think I would have preferred forcing the user to tap OK on the popup as it is easy to forget and having to correct the error blob much later is a pain.
  5. Beta .168 Partial fix to tapping away from popups Still get a dot when tapping away, no longer get a line forming it seems. The dot is the size of the previous brush size. A start I guess!
  6. This bug was, I think, first introduced in 1.7. After my limited testing 1.8 seems like a huge improvement on 1.7, so huge congratulations to the team. It seems to be back to the wonderful standards of 1.6, which is great. My main annoyance of 1.7 was the slowdown when resizing layers, this seems to be vastly improved in the new version. There are a few occasions when resizing/moving layers long slow downs occur but it's nowhere near the levels of 1.7.
  7. After changing the size of the pencil width or colour, tapping off the menu to close it with the pencil causes a straight line to be drawn. The only effective way is to tap with your finger. Clearly one should be able to tap off the menu with the pencil. *Edit* I should have stated this is on a 1TB iPad Pro 2018 RPReplay_Final1582029380.mp4
  8. Photo still cannot cope with transformations of groups, though I'm wondering whether its just shrinking the groups which causes issues (particularly shrinking smaller than their original size?) In these videos one shows that no issues occur when simply enlarging the groups, however there is significant lag when one attempts to shrink the groups (these are unadjusted sample pictures pixel dimensions 2560x1440):- This is with the latest Photo release on a 1TB iPad RPReplay_Final1566425259.mp4 RPReplay_Final1566425594.mp4
  9. As a further example, I've made a video of a document which is 10000 x 10000 pixels (equivalent to about four layers of 5000 x 5000 I guess) and performed the same scaling and translating with no lag. Surely this should be further evidence that there is something wrong with the group implementation? RPReplay_Final1565273562.mp4
  10. However, I can manipulate single layers with wild abandon, with no slowdown whatsoever. Note these videos are done at 5000 x 5000 pixels RPReplay_Final1565254091.mp4
  11. I have just been testing the latest version, and unfortunately the same problems occur. Any kind of manipulation of groups of layers is resulting in complete slowdown, and degradation of work. Leading to files being unable to be saved. I realise that I am probably coming off as a pain, but I just want Photo to be back to the glory of 1.6. When I try to manipulate groups of layers (in this case, just two), even with kid gloves, I experience horrendous slow down. Note that when the blue touch circle is on screen (and paused) the app has hung. When there is no blue circle I am giving the app every chance to recover. RPReplay_Final1565253975.mp4
  12. Thank you so much for the detailed reply. I'm glad that something has been sorted out, I'm looking forward to loving this amazing program once more. I'm not quite sure I understand the reasoning that given as I would have expected similar problems when dealing with single layers. Unless one is dealing with the group as a whole (rather than individually) and then referencing memory that has not been allocated I guess.
  13. To be honest it doesn't require much to get the app to slow down to a crawl, just manipulate a group of 3 layers or more on a reasonably large canvas for a few operations and you will experience serious slow down. If one works on individual layers then the app seems fine and smooth as it was on 1.6, however working with groups of layers is still very buggy.
  14. Just as a further example, I've performed the same operations to individual layers (i.e. not in a group) and it is far harder to get the system to slow down. RPReplay_Final1565092284.mp4
  • Create New...

Important Information

Please note there is currently a delay in replying to some post. See pinned thread in the Questions forum. These are the Terms of Use you will be asked to agree to if you join the forum. | 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.