Beta 26.0 windows I get unsupported format or damaged file warning  (they import into resolve)   edit: re-installing helped for one session, next time I restarted the beta, it went back to not recognising the files grrr     ... View more

I use masks a lot. Ai masks - great. What you've done to the rest of them - hard facepalm Previously: I have an effect on a clip and I want to mask it. Generally I'm already in the effects panel, I click on the mask icon and adjust the mask. Yes adjusting each point is a pain in the bum, this could be improved.  Beta 25.6.0: I mouse to the tools pallete, click and wait for the dropdown,  select the rectange draw the mask mouse back to the effects pallete drag the unasigned mask to the effect Adjust the mask whilst trying to see what effect its having through the "helpful" red mist Someone is going to tell me I can assign a shortcut to it.  Can I get a shortcut to drag the unnasigned mask to effect? What If I have a lumetri effect open?  WIll I have to drag it past all that to the effect I want?  Or will I have to close all the effects before I can drag it to the one I want.   Putting the mask in an unasigned item is one of the clunkiest user interface cluges I've seen in a long time.  Being able to draw the mask - great. Removing the expand control from the on screen mask?  why???  ... View more

Just thought I'd mention it again because it blows my mind that something would work so well and then just stop. Was it removed?  It used to be fantastic for smoothing out time remapping where there is a small ramp say 400-100.  or very long ramps.       ... View more

 i have identical projects on 24 and 25 is it the inclusion of colour management that has borked the performance in PP 25?   In 24 I was able to work with 8k h.265 files with 2 lots of lumetri effects and 3 adjustment layers in the timeline and it would play back.  There is no chance with 25.  Ditto 5K dji h.265s.   Its so bad that grading is almost impossible - I will change a value in a lumetri effect and it will not update in the preview window, I'll have to move the playhead to see the effect.   windows 11 24H2 PPro 25.2.1 (25.3 had a showstopping render bug I had to roll back). ... View more

After an update the gradient tool reverted to its new implementation I spent a few weeks trying to use it - I gave it a shot. This is why it doesnt work for me: I use it on masks. Thats pretty much it, but I use it a lot.  I rarely use just one, by default I have it set to screen, I create a black mask and add gradients to it.   I failed to find a graceful way to add more than one gradient to a mask with the new tool.  If there is a way, it is not at all obvious or intuitive.   The problem isn't just with this tool though, its with the overwhelming feeling of total pointlessness I feel in writing this, and the culture that creates in the community.  How many people just give up trying to give feedback.  There's only so many years you can try to point things out, report bugs that go unresolved (one for premiere is now 7 or 8 years old).  Do you have people testing this stuff that have been using photoshop for 30 years? I'm pretty sure that I wouldnt be the only photographer that will be using masks in this way. All of us waiting for deprecated features like the old gradient tool to be removed completely.  Do you listen to these testers?  The software feels more and more like it is insular, and designed by engineers.  Lightroom's recent implementation of the healing/remove tools is a fantastic example. (You paint a section to be replaced,  find you're on the wrong tool, and have to repaint it).   Something else will come along and those of us that have been yelling into the void for literally decades will leave in droves.  I dont see any sign that the culture in Adobe is even open to taking a look at itself.       ... View more

This issue cant just be related to text over png.  I have a project that wont render with the same error code. I thought this was only happening in the most recent version, but after rolling back to 25.1 - where I had no problems - and then forward to 25.2.1 i'm getting the error again).  I have manged to successfully export once - by rendering previews (sequence set to quicktime 422HQ) and then rendering using previews to the same settings - and then using ME to encode to h.264.  What a faff.  WHen the render fails it appears to take the graphics pathway with it, because I need to restart premiere to get any playback. THings I tried 1.The sequence contains text over a mogrt, which I nested and still got the error. 2. removing all those nests: sequence rendrered OK 3. Nesting the nests -still failed (at a timecode that didnt appear to have a title?!) 4. tried again to export without the sequences (recreated the sequence-free timeline): rendered ok (wasnt a fluke) 5. Removed all but the few around where the render failed:  still failed 6. Cleaned up the nested sequences so the end of the clips were at the same point (I also set one of the clips to 50% speed instead of the 49.95 that it had somehow been set to previously): success! So not sure if this helps you isoloate the issue, after and before screengrabs below.  ... View more

why is it still so clunky to crop an image to remove all transparent pixels in ps, when lightroom has a checkbox.   The crop too snaps to the image bounds which is fine most of the time, but when you have a 3 or 4 pixels of transparency - and not in a perfect rectangle (so you cant use the trim or crop command), its hopeless. I just cludged an action to do it, but i'm guessing it could be done in about 10 lines of code as a script ... View more