Ok very weird  - I installed indesign 2022, and now the file is usable in both.  I'd put this down to idiot user error, if I i hadn't faffed around for 10 mins (including trashing prefs) before I resintalled.   Ultimately: ¯\_(ツ)_/¯ ... View more

I wasn't talking about a particular feature, I was saying that its peak usability was even earlier and it has been going downhill ever since - implementing features but not well and then never updating them (blur gallery!), or taking something that worked, albeit in a slightly clunky way, and "improving it" but actually making the usability worse.  The worst offender for me was changing the modifier keys for transforms. Lets reprogram 20 years of muscle memory, yay!    ... View more

Sigh.  Photoshop reached its peak of usability around 1999. I cant help feeling after that that the people who were running the show, weren't using it.  They started playing fast and loose with muscle memory, and tagging things on rather than integrating them properly.  I used to rave to anyone that would listen about photoshop, now I'm more likely to be raving mad.  Except generative fill. That sh#! is immense 😋   ... View more

Sigh 🤦   I used this app on my phone for a while - a dinky music looping app.  It was really thrashing the hardware but the amount it could do was nuts.  It would crash and I'd reload and I never lost a single thing. Not a thing!   ... View more

thank you, I must admit I didn't reset the prefs.  (but yes did the workspace stuff) And thanks for the audio hardware tip, that's a new one for me 🙂   ... View more

I just installed Photo Mechanic.  The speed that it produces thumbnails is unreal.  It's like being on a new computer. I always thought bridge/lightroom's problem was that it was having to read from a hard drive and it was just the volume of data that made it slow - but no.  Apparently not.     blerg  ... View more

. ... View more

yep I've never had much luck recovering video files.  I've used windows software called r-studio.  I think there are dedicated video recovery tools out there, though.  Ones that will make bits of the video files playable rather than the whole thing being trash if a part of it is trash - but again it depends on how much you need to recover.   ... View more

have you tried the autosave files?  This won't be what you want to hear, but at least you have the working cut. You can lay it down and match cut over the top of it to recreate.  You might find it quicker than trying to rescue the corrupted prproj files.  ... View more

Unfortunately not!   But wait! I figured out the transform workaround. Another entry in the great premiere workaround encyclopedia: Nest the layer so that it is the same size as the sequence.  Even if its a few pix difference, transform doesn't like it.  This can be a massive pain in the bum of course if you're in a 1080 sequence and trying to do a zoom out from a 4k shot (which is where most of my workflow is). ... View more

Hi @Kevin-Monahan I'm happy to help provide anything you need to look into this, maybe you could ping me a message or use my adobe registered email address. I don't really want to provide stuff in a forum because it's quite time-consuming and I've been down that road before - with this bug.  I'm happy to invest the time if I know it's actually going to get looked at, and not dismissed as what my Mrs calls "idiot user error" ... View more

first and foremost bridge needs to perform its core functionality quickly and reliably.  Its not flashy. It doesn't need to be. I'd be more than happy if adobe spent it's time getting it to run quicker, with less bloat, with a more sensible caching, and ditch all the bells and whistles.  Tabs? meh! especially tabs that you have to close with a right click and that stop you give you an error when you've got too many of them.  Its facepalming stuff.  And I'm writing this in Feb 2023. The current release is still a dumpster fire.  I'd go back to the 2022 release if I wasn't reasonably sure that, from past adobe experience, it was going to remove all my collections, or fail to work with photoshop.  ... View more

I first posted about this in 2017, I've seen posts from 2016 about it. But this is a mild snafu compared to the current time-remapping bug which is stopping me using premiere 14&15. As detailed: https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/40471309-bug-time-remapping-interpreted-footage-14-2 ... View more

Part of the problem with this bug is that in all the interactions I've had with adobe staff, they have all intimated that the existing behaviour is correct: sort of "you're not holding it right", type feedback. I have listed this bug at least twice. Here is a new video demonstrating the problem. I am happy to help with this. I use remapping all the time. For the last 3 years I have been having to render interim files for nested sequences that have layers.If anything is still in anyway not clear, or if anyone thinks this behavior is still as expected, I'm all ears. https://youtu.be/CoUYqRoHXEo This is the closest I have ever got at interacting with Adobe staff. Unfortunately they failed to read my post properly, and vanished once hoops had been jumped through: https://community.adobe.com/t5/premiere-pro/nested-sequence-time-remapping-bug/td-p/9493724?page=1 ... View more

BTW, the fix for this issue is to close all of the bins except the main project bin. Then it will start working again. So if you're like me, and keep exactly the bins you need open, tough tiddies ... View more

reveal in project is borked in cc2019 in a way it was not in cc2018. When it stops working you have to reset your workspace, or sometimes restart premiere. this is such a basic fundemental part of the software I cant understand how it only has 24 votes. Do people not use this? Are people manually finding clips in bins? It would be like explorer had stopped working in windows. ... View more

Has anyone noticed that sometimes if you walk away from this crash it will recover? You have to leave it half an hour or so. But if you've not got a recent save point, and you've done something vital, it might be worth giving that a go. Go and talk a relaxing bath, and muse on the decisions in your life that led you having to take a relaxing bath because your software is so ****. PS That spreadsheet is amazing. ... View more

thanks yep it seems if you have the sequence at the start it fails, if its at the end it works! ... View more

I've had direct contact with adobe about this bug - they failed to acknowledge it as a bug (because they didn't try hard enough!) I'm so used to it now I have 2 main workarounds:  If a nested sequence includes a cut/more than one layer and you need to do a speed ramp on it in another timeline you can: 1. render it out. I now have a "bump" folder for every project for such things. Re-import it into premiere. 2. turn off cuda in prefferences, nest the ramped sequence and render that out as above I've also got used to just avoiding it: for instance for doing property boundaries instead of using paths I used lumetri plus masks to do the same thing.   The more people complain about this, the more likely it is to be addressed.  There used to be a lot of uservoice stuff about this bug, but I believe thats been deprecated or removed. I'm not sure at the mo how you even report bugs.  TBH I'm in  aholding pattern until I have the time to start using that Davinci Resolve licence I bought a year ago    Here's the uservoice page: https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/34384855-bug-report-time-remap-of-nested-sequence-results   ... View more

I came here to post the exact same issue: exceptmim not using click remover.  I am using noise reduction though, so I'll try ditching that to see if it helps. ... View more