No I don't mean getting a bit map selection. I mean using the actual shape as a mask. FOr this you need to make a shape layer and ctrl+alt drag the shape over onto the bitmap layer, then it stays a vector. This cant be replaced by what you are suggesting. This also work on groups, but it also does auto zoom into the shape of the vector This  ... View more

I dont understand what you mean? I want to transfer a shape from a shape layer to another layer and use it as a clipping mask. Is there another way to do this? ... View more

I'm still having this issue after 21.0.2. Just make one shape layer and one regular and use alt+ctrl and add the shape layer as a mask, it will auto zoom into the shape size. I hope you don't mark this bug as fixed yet.... ... View more

It did not fix it for me, so doesn't seem fixed to me.  ... View more

I sincerely hope this will be fixed quickly, and that Adobe don't spend the length it took to add the uniform transform off option.  It was ok to wait for that one as it had a workaround - this one don't. This problem is really disrupting my workflow, especially for adding a shape to a mask with ctrl+shift+alt drag . I thought ctrl+shift worked, but that inverts the mask and makes it cumbersomme as well. And honestly, if you are used to zoom with keyboard shortcuts and a tablet, this new "auto zoom" feature is not needed at all.  ... View more

I sincerely hope this will be fixed quickly, and that Adobe spend the length it took to add the uniform transform off option, it was ok to wait for that one as it had a workaround - this one don't. This problem is really disrupting my workflow. And honestly, if you are used to zoom with keyboard shortcuts and a tablet, this new "auto zoom" feature is not needed at all.  ... View more

WHenever I make a mask from a shape in Photoshop CC 2020, the whole canvas zooms into that shape and makes it fill the entire canvas. This is really annoying when I work with a lot of shapes and want to use them as vector mask layers. I have to zoom out all the time. How can I disable this behaviour? ... View more

I agree with Andrew, don't expect much change in the years to come. Also, softwares are different, the same way anything else you do on a computer is - so one have to build the machine based on what you will use it for, which is why Puget systems are so great. And since Apple custom build the entire machine they have to pick components based on what they think their userbase wants primarily...and iMac Pro is very much based around Final Cut Pro X, which was rebuilt a few years back for modern hardware. Building a machine for AE is very different and if Apple would make a machine for that, it would feel like they are making machines that are good for the opposite of the rest of the Apple users want (since gaming and such are low priority for Apple). The only way this would ever change is if Adobe scratched AE and started over and threw away the entire program. Something that is a HUGE undertaking, also because of all the plugins people are reliant on. It would take years before it would scratch the surface of what AE can do today...So yeah, not going to happen for a very long time. If AE is your main tool, then you should return your iMac Pro and buy a regular top of the line iMac, you would get a LOT better performance for a cheaper machine. ... View more

It was but in a very crude way. Because AE used ONLY 1 core previously across the entire software, now some few plugins are using multicore (which is one of the reasons they removed this feature). But back in cc2015, when no plugin had multi core support, they could render multiple single frames per core. It would not impact the responsiveness of the program or when caching preview or working, but when you hit render button it could increase rendering speed based on core amount. So, back then you could have a ton of cores and render really fast. (it was crashing a lot though) There are plugins that does the same today, such as RenderGarden. But the main problem with slow CPU cores which makes AE slow and sluggish when working, is in my opinion more crucial than final render speed in itself. It is when you are working with the scene that speed matters - especially now when you can send a queue of renders to Adobe Media Encoder. ... View more

I've done extensive testing and made faulty investments myself and learned the hard way. But it is what it is, and I can tell you that the top of the line iMac Pro, which I assume you bought, is the slowest of all iMac Pro models in After Effects (and that's the way it will be, forever....unless Adobe start making AE from scratch in a different way). Ram has hardly anything to do with speed. The only reason why a lot of Ram is good, is that it takes longer before the machine starts scratching to disk and it can hold more preview frames in memory which will feel like a faster machine. The speed of the ram doesn't make much difference in AE either. AE prefer a machine the same way as games. Meaning few cores and fast cores. Which is the opposite of what you have bought, and in fact the cheapest option. Plugins in AE are being rewritten one by one for each update Adobe does, but they tend to make the new updates GPU dependent. If you buy a 5ghz intel CPU machine with a fast GPU, that would be the fastest option on the marked today, and it cost about 20% of your iMac Pro. Honestly, Macs are the slowest and most expensive option you can get for Adobe programs. If you really want as much speed for your bucks as possible, you need to read up on pages like pugetsystems.com and see what hardware they recommend for which softwares and then build your own machine or order it from a company (like puget). If you by any means want to stick with a Mac, then get a regular iMac with a faster CPU and as much ram as possible, it would perform a lot better than your iMac Pro in After Effects, that's just how it is, sadly. i.e. Mac Pro, the most expensive one of apples models, performs about 50% of the speed of an intel 5ghz CPU , thats approx 4X the price for HALF the performance!! (caugh, rip off) ... View more

That's really strange, I haven't encountered this problem for years now. What version of Photoshop are you using, the latest Photoshop CC? Does it happen with the mouse AND the tablet or only the tablet? Or is the problem different between the two. Mouse closing the gap and the tablet sticking ? ... View more

I don't mind getting notifications of software updates. But the daily spam of trying to make me subscribe to adobe stock photos is not ok. Though it has been more quiet lately, so I'm ok about it now - but there was a period I got multiple notifications of images I can buy, every day! ...that's not ok!! ... View more

I think if you had implemented it properly at the get go, it would have been better received. It's mainly the inconsistency that made it impossible to work with, at least for me. Particularly in Photoshop. As for someone like myself, I use shapes, text and bitmap layers and all kind of layers all the time, often on one same PSD file and all the layers are used in different ways. I don't really regard shapes in a different way than a bitmap layers. And having to learn my muscle memory to get used to them all behaving different is impossible!. F.example: first scale a bitmap layer in uniform scale, then add a vector mask and scale, and boom it behaves differently and you make mistakes. It feels like a complete mess when working.  If such a major behavior change for a tool that is used all the time should be changed, it should be a common behavior across the entire program (bitmaps, content aware scale, vector, text, etc etc....) and not least across all Adobe programs coming out at the same time - so you are forced to relearn it. Additionally, users should be able to revert to legacy behavior the same way you did with multiple undo's, inside the program preferences.  Without such an implementation, this feature will never be well received.  ... View more

It would be very nice I agree. though I have brushes in folders. It would be nice to color tag those that I use most commonly to remember where to find them. Or when working on a specific project.  ... View more

the line with circle is just something Lazy Nezumi has to show how the smoothing works.  ... View more

thank you so much 🙂  I was currently writing a new reply while you answered, trying to explain it better. (sorry I'm not a programmer, so it's not so easy to explain what is good/bad in a technical way).  But to sum up: Lazy nezumi has two behaviours. either it stops when you stop or it completes the movement until it hits the mouse pointer.  Photoshop is an inbetween, so you don't benefit from neither ways, because it doesn't stop but it slowly lurks its way to the pointer when you stop, and at that moment it's not very useful. Do you agree ?  So you understand me correctly, this is the thing I dislike with how photoshop currently does it. If you gave the user the two options lazy nezumi has, 1. stops when you stop 2. completes the movement without slowing down the instant you do so with the pointer...everything else with the photoshop smoothing is great.  thank you so much for listening, if this gets improved it would have been amazing!  ... View more

Hi yes I guess my video might show it incorrectly according to technicality, sorry bad example... 🙂 . What Lazy nezumi does makes the smoothed trail line feel natural, it catches up to the pointer in the speed it has all across the movement, while in Photoshop smoothing it does exactly like you say, the instant you stop moving, the smoothing almost stops as well, instead of catching up to the pointer. so yeah, when you paint you have to either sit and wait for the smoothing to catch up, which is very annoying and difficult to work with or you need to lift your hand from the tablet when moment you feel it has reached the point you want it to. Do you see what I mean. While the preferred behaviour would be the two selections Lazy nezumi has, either it stops completely the moment you stop the cursor or it catches up in the speed it has when you stop painting. THat would have been awesome.  ... View more

Here you see how lazy nezumi works, with catch up on/off. which is how it should work in my opinion.  catchup off: https://i.imgur.com/ToL5Ccs.gif catchup on: https://i.imgur.com/RnAlTGp.gif ... View more

None of the catch up works properly in my opinion. Because one of them stops completely but the other one which is suppose to catch up actually almost stops the instant you stop your cursor. It flows in the right speed all the way until you stop. But it should instead adopt the speed you had at that area you were drawing at the time you were painting, like a proper trail, so that it doesn't halt the instant you stop. This has nothing to do with what kind of brush you use, its just the general behavior of the feature. Lazy Nezmuni, the plugin, does it correct, though Photoshops version makes better smoothed lines, so I would really like it to work well in the end of the stroke as well.  I will show you two videos to try to explain the problem, one video is an example on how it should behave when you do the stroke based on the amount of smoothing, the other show the problem with how it is currently implemented.  ... View more

@alexandra giamanco, Yeah, and Look at what CC 2019 brought us, a rather simple color wheel (compared to coolorus), a small upgrade to the HealBrush tool and force shifting two keyboard shortcuts around (multiple undos and free transform)...If that's the rate of features on a yearly update, then one can't expect to a feature request in decades! warren@thompson, well maybe the way they solved required something from Microsoft. But I had other programs that supported both low and HiDPI monitors at the same time, so it's not something that couldn't be done. Also, they way they added it initially before it was fixed, it would have been better if they let windows do the job by scaling it instead. Which is something most were stuck with unless doing an elaborate hack. But once it got fixed, it was solved very well from Adobes part, gotta give them that 🙂  ... View more

@Alexandra Giamanco Well, the HiDPI UI fix took about 4-5 years since people started complaining. the requested brush improvements took even a LOT longer than that. There's a limit to how far one should backtrack tbh 😄 ...Either the team is too small or things take too much time to make in the Photoshop code. Nevertheless it's kind of unfortunate when a feature takes so long that its nearly obsolete when it actually comes out.  ... View more

@Alexandra Giamanco I did not quite get what you were referring to with your analogy 🙂 Was it something I said? ... View more