verysame

Neil, Hope your request will be taken into consideration! There are some other few things about PS brushes in AP which are not still working. Anyway, just wanted to add my +1 :)

As far as I know, not yet.

Thank you, Frankentoon!

The rental model is something didn't exist before as originally the consumer who bought the software had an actual copy of it and unless the hardware/OS would become obsolete, the user could keep using that copy virtually forever. Water, gas, it's a different situation. It is a service being provided vs a product being purchased. When you step into a shop to buy something, you keep what you buy. If you rent say a car then, of course, you're not keeping the product. As for the locking file problem, it is actually an issue because I'm not supposed to rely on third-party solutions in order to use Adobe's native files.

Same issue here, and it's been like this since the very first beta I tried. This persisted in the final release and new betas as well. I can't find a way to reproduce it. It only happens randomly. As Maxen suggested, the only way to temporary fix it is by closing and re-opening the document. I didn't notice if it is strictly related to large images only, I'll see if that's the case. It could be, as when the issue happens I tend to create a new 1920x1080 document to check if the brush is working at all and in the new document it does.

The default behavior is the one you look for, the new layer is added on top of the selected layer, not on top of the stack. I don't even think the Assistant gives that option. I'm not sure why that's happening on your end :/

+ 1!

Thanks for the new beta, downloading right now.

Despite I'd love to see an AE alternative coming from Serif, we have to be realistic. I kind of agree with DarkClown here regarding what we can expect. Don't get me wrong, I think Serif is doing a terrific job with Photo and Designer. Bugs have to be expected, but the status of both apps is already great. If they keep improving them as they are doing, they both are going to be killer apps. That said, an AE alternative is a tough one for a few reasons. The habits of AE users are hard to beat, perhaps even more than PS users AE's interface and workflow, after all these years, are set in stone: for someone who works in the motion graphics industry is very hard to move to a different application (Hitfilm tried already and I think with no much luck) If a Photoshop alternative may sound reasonable, an AE alternative is less Let me expand on the last point. When it comes to rendering a still image, to a certain extent is not so crucial what program has been used. After all, worst case scenario as long as the layers are readable from both sides, everything is fine. For a motion graphics piece is different. Studios, from small to big, have invested in their pipelines, plugins, scripts, and so on. Now, sharing some still renders is one thing, working on an animated project involves more steps. I don't see a studio embracing an alternative considered that, from that point on, they will feel like a drop in the ocean. Chances that someone, from the casual user who wants to mess around with some pictures, to a professional who wants to try something different or who is tired of the Adobe monopoly, will end up using Photo or Designer are definitely good. Working with bitmaps and vectors it's sort of a closed loop, worst case scenario an EPS will do. On the other hand, I don't see a casual user investing time in learning a complex application for motion graphics (and I'm already reading posts from frustrated users considering AP too complex!). Professionals? Why should they? What the benefits? The market has already its parading. Why should someone learn an unknown program, with an unknown future when there's next to zero chances to share the work with any other professionals out there? Even if figuring out a partial communication with AE via an XML or something (I'm not a dev, just guessing), I hardly see a serious, robust way to go back & forth with AE. It's been a nightmare for years for 3d users, and only now we can finally share files via Alembic and OpenVDB (and is not 100% there yet). Last but not least, there are free or quasi-free solutions on the market already: Fusion (wich comes with a free version) and Nuke (with a non-commercial version). Considered how the industry pushed the limits, it also makes sense to invest time and energy in learning, say, Nuke rather than an unknown AE-alternative. Plus, Nuke and Fusion means competing not only with a 20 years old corporation like Adobe but also with two other well-known, solid compositing softwares (I know, they are not specifically mograph-oriented apps, but still...) As Timo said, better to focus on AP and AD.

Here:

Hi there, As pointed out in a few previous posts, in the latest beta (1.5.1.51) the default behavior for a new adjustment layer is being added as a child layer. I'm not sure whether this is a bug or an intentional choice. Unless there's a specific reason for that, I hope you would consider reverting the situation to the previous releases. Most of the time, the need is to have an adjustment layer on top of the selected layer, not as a child and I'm pretty sure this is a quite common workflow shared by other users as well. Although it is possible to change this option from the Assistant, it also true that changing options in the Assistant it is a session related tweak and changes are not stored globally to the application.

Harrym, On WeTransfer you get 2gb file transfer: https://wetransfer.com/

Totally agree, something is off and it shouldn't happen.

Hey DarkClown, I've had a similar issue a few days ago. Some adjustment layers were deselected although their effect was still visible. I've had to restart AP in order to get rid of the issue. It looks like a video card related bug, the problem is I can't reproduce it. edit: I wonder if a Purge Cache command as in PS would help in situations like this.

I'm loading it in 1.5.1.51. Hope some moderators will chime in! :)

Oops, Yes, it seems you've got an issue with your build. I always see the moderators asking for the crash log... Sorry, wish I could help more :/

Oh totally, Hope didn't sound I was reacting to your explanation :)

Let me try... Hm... it's working fine here. This is what I get: I'm on the 1.5.51 as well.

I can't open your file. Is it an Affinity Photo file?

Too many functions, meaning...? Not flexible, meaning? Plugins: it's been stated several times already, plugins' support is not 100% there yet. Editing an existing mask, no success: again, what's the issue? Editing masks can indeed feels different from what people is used to. That said, there are other similar posts on this very forum already solved. It only takes a minute to understand how it works, then it's a matter of habit. The more you use it, the better you get (as for everything, right?). Not intuitive. You should expand on this topic because it really opens a can of worms. What is intuitive for you, could be totally counter-intuitive for someone else. Also, what you find intuitive could be only your habit to something you are used to, which surely took some time to get used to. So, perhaps, your definition of intuitive is better interpreted as "X doesn't work as Y", which is not the meaning of intuitive. I agree with PaulAffinity: it's the era of the apps. Which is totally fine, no one forces anyone to use one particular program. But then, people should also be either more descriptive about the issues they find, or more honest and admit they are not willing to give up on their habits. But that has nothing to do with a program being ready for new users. Perhaps I went through too many programs to know that a learning curve is always needed. That learning curve, though, is what gives me new ways to explore things I take for granted. If I want to stay in the comfort zone, why wander in other territories in the first place?

Thanks for the explanation. I can understand the efficiency workaround, that said most of the time the adjustment layers are meant to affect what's under them, not just one layer. In my experience, most likely I'm creating an adjustment to affect the whole comp than just one single layer. That doesn't mean I don't add adjustment to single layers, but that's exactly where the nesting comes into play. In other words, if it's been done because of an efficiency issue I only hope it's temporary as the efficiency has to be fixed first, not worked around.

OT: KiboOst, this is your photography stuff? http://www.nicolasgenette.com/us/Fovea It's really beautiful! And what is this? http://www.nicolasgenette.com/photos/Fovea/2016/Noirceur-8.jpg Stunning! It almost looks like 3d particles as seen in Houdini and in other generative graphic.

I probably should start another thread, but since we are here... Changing the settings in the Assistant Manager did the trick, only now it doesn't store the new setting. In other words, every time I open Photo I have to change the setting again. Is there another setting somewhere, or is this a bug?

KiboOst, on 07 Jan 2017 - 01:54 AM, said: Same here! It took me a while to get used to it. Now I must admit I think I prefer it over the PS method. For instance, I like it that CTRL+M creates and adjustment right away, rather than a curve baked into the layer as in PS. KiboOst, on 07 Jan 2017 - 01:54 AM, said: Yep! I know it's a bummer, but I'm positive about Affinity's improvements. Soon or later this will be added. After all, AP it's still version 1.5 ;)

Awesome! Thank you, MarvinR. I always forget to check the assistant.