You quoted my post where I reported I'm not having this problem.  I'm not claiming that exonerates Adobe, but it's also possible that it's a Catalina security issue.  Did you try a new Admin User as I suggested?  Perhaps you could try uninstalling the CC apps, log in as a fresh Admin User, reinstall, OK every security challenge, and see if that helps. From the OP:  "It will load fine upon the first few tries, but having the same error after the laptop has been switched on for a while." That gives me an idea that may be connected to Sleep and Energy Settings.  Check into your Energy Settings and try the never sleep disks option, and maybe the require log-in after sleep set to the maximum: 8 hours.  That's the only thing that seems connected to an issue popping up after the computer has been on for a while.  That, or something heat related. ... View more

Yes, there are "performance problems" with Pr 2020, but it sounds like you're confusing RAM with disk storage.  Frame size on export isn't the only variable.  Higher bit-rates generally require more disk space (storage) than lower ones, as higher frame dimensions require more space than smaller ones given the same bit-rate.  The export window estimates your exported file size at the bottom right of the window.  You must have at least that much free space on your destination drive to avoid the error you are seeing. ... View more

New MacPro here, too.  I did a clean install of all my apps and only migrated my Documents from my prior system.  I can work with Pr 2020, but with issues I can't tolerate (I've posted on this forum about it.).  Back to 2019, which works better.  There are several Project downgrader solutions around.  The only feature in 2020 that interests me anyway is the expanded options for speed changes.  I can work around that as I have before.    Adobe has a lot of gall to put out such a buggy release, and call it an "upgrade," IMO.  But then, most of their Pr x.0 releases have been imperfect. That said, the new "security" features of Catalina are onerous, and it appears the only way to get some apps to operate properly, you have to open the door to access to your file system - to make your computer insecure.  If you want a color picker to work, you have to allow the app to "record your screen."  I've kept the security pane open upon installation to verify that every third party plug in is safe, and I have dozens of them.  It's been quite a chore making the transition to Catalina - two full work days.    Sorry that I can't offer a solution, but rather an anecdote that the combo of new MacPro, Catalina, and Pr 2019 and 2020 work more or less OK on my system - or well beyond the splash screen.  My surmise is that your issue may be related to permissions (security) of a folder the app is trying to access.  Maybe try adding a new User / Admin, and see if that helps. ... View more

Downgrade your project and use 2019 until Pr 2020 is up to 14.5, unless you LIKE being a beta tester.   Search this forum or the web for info on downgrading projects. ... View more

I have a similar new MacPro, and I did a clean install  of everything except my User documents that I migrated with Migration Assistant.  So far, I've concluded that Catalina and Pr 2020 aren't ready for pro use.  I suggest you use 2019 and stay away from 2020 until it's been debugged.  There are posts here on downgrading Pr projects, or just do a web search for "premiere project downgrade." ... View more

So, Neil... You seem to be the only person interested in my thread,   I decided to give 2020 another try, and worked a whole day without issues.  Then, yesterday, a client comes to my office to work with me, and whaddya' know, Transmit decides to stop working again almost as soon as he darkens the door.  After multiple attemps to get it to work by switching Transmit on and off several times, I take a few minutes to downgrade my project with Digital Rebellion's Project Repair, and I'm back on 2019 in about four minutes with reliable Transmit functionality again. So, I'm back to considering 2020 is not ready for prime time.  Fool me twice, shame on me. ... View more

Here's another on-line downgrader I haven't used yet: http://downgrader.elements.tv/ ... View more

UNCHECK Automatically Refresh Growing Files in the Media Preferences.  It's on by default, and shouldn't be, IMO. If you have a backup system that only backs up changes since the last backup, it will rewrite all your media that's been "grown" (modified) since the last backup.  Normally, you wouldn't want to do that because of the unnecesarry amount of time it would take rewriting files that have already been written.  As Neil said, that option is changing the modification date (not the media), and that's what tells your backup app to rewrite a changed file.   There are situations where your media actually is growing in size, such as during a Capture from tape or a live feed, when you would want that option checked to make sure the updated media is backed up on your subsequent backup session. ... View more

And, here's a tip:  Locate that containing folder that contains the extra Media Cache and PTX folder, and create an alias of it on your Desktop, so that when you intend to delete all your caches, you can easily get to that folder and delete them.  You can delete the folders, not just the contents, because Pr is going to recreate the folders next time you launch the app. ... View more

Going back several versions, and persisting up to Pr 2020, the app creates Media Cache folders in the User>Library>Application Support>Adobe>Common without regard and in addition to your having chosen a Media Cache folder elsewhere, or kept the default location in your User>Documents>Adobe folder.  This is on OSX. So, what can happen, unknown to most users, is that their boot disk gets bloated with files they can't delete unless they know about this extra folder AND they delete the contents or the Cache and PTX folders manually.   Since trashing Media Caches is a oft-advised troubleshooting (and housekeeping) step, this can easily be overlooked by the uniformed.   Doing a boot disk search for anything with "adobe" in it can reveal files and folders in places you might not think to look.  I learned way back when I worked for Avid is that the installer puts inscrutably named files in inscrutably named folders, too, for license keys.  I think that's fairly typical for apps and plug-ins. ... View more

Neil, I downloaded the Cleaner Tool, which suggests uninstalling Pr before running the cleaner.  I did that, and subsequently, Pr 14.0 didn't show up in the Cleaner menu.  Does that mean the unistaller was so thorough that there's nothing to clean?   Do you know if there's a list somewhere of what files and components that the Cleaner removes?  I wouldn't mind deleting them manually if I knew they were Pr 2020-specific.   Anyway... I un and re-installed for a second time, and Transmit is working again, for now. ... View more

Thanks for the reply, Neil.  I did uninstall and reinstall, which didn't help, but didn't run the Cleaner tool.  That seems unnecessary since I did a totally clean install of all my apps on this new Mac.  But, since I have lots of experience with Premiere corrupting itself, I'll give that a try.  The three "major" new features in 2020 are a joke to me anyway, except for the time remapping increase.  We're all probably better off on 13.1.5, since that indicates five attemps at getting CC 2019 right, and CC 2020 is still a virgin .0 bug fest, as all versions of Premier have been in my experience since CS5.5.  That was about the time many FCP7 users transitioned over.   If anybody else wants to suffer 2020, I did figure out a way to fool Pr into playing on my second display:  Undock the Program pane and drag it over to the second display, click the ` key, and presto, it starts working.  Of course, you lose seeing the Program pane in the main interface, which is why this is a half-ass workaround.   I suspect some issues could also be Catalina related since Apple also puts out crap OSX releases before they get up to 10.x.5 as well.  I tried installing Mojave on the new Mac Pro, but it wouldn't take it.  I'm stuck with Catalina or my old Mac Pro 5,1, High Sierra, and Pr 2018 for a more reliable experience.    But, I've been working on Pr 2019 for a full day now, and it's been pretty solid.  So far.   Thanks for your patience.  I know my frustration is not even remotely concealed. ... View more

Turns out that 2020 is just another garbage release from Adobe.  I installed Pr 2019 and Transmit works properly. ... View more

There's a Pr project downgrader in Digital Rebellion's Project Repair app, and there's a free on-line project downgrader at: http://joshcluderay.com/downgrade-premiere-project-converter/ It has a 5 MB file size limit, though.  Very useful, since Adobe keeps putting out buggy software. ... View more

Kevin, the new 2020 doesn't drop frames so far.  Just goes to show the issue was a shortcoming in the Pr application, and that my system is perfectly fine. ... View more

I just downloaded Resolve, and my clips are playing smooth as butter. This proves that a capable, competent NLE should be able to play raw HD footage without dropping frames, even on older hardware. ... View more

I just got an automated inquiry whether this conversation solved my issue. It did not. Since the last message, I got a request from a client to cut down a 1280 x 720 H264 video. I started a new project, and Pr CC18 wouldn't even play a Sequence made from the video without dropping frames. At this point, I suspect it won't even play standard def clips. I've consulted with the company that mofidied the Titan to see if there's a test to see if it's failing or underperforming, and I've gotten some guidance, but I'm waiting to hear whether he tests I've run suggest an issue there. ... View more

Hi Kevin. I started a new project in CC18, imported a ProResHQ movie, dropped it in to a new Sequence, and played it. The Dropped Frame Indicator turned yellow within a half second. I don't believe that this can be considered acceptable performance or behavior for any NLE. I did the same thing in Pr CS6, and it played the Sequence with the same ProResHQ clip without dropping frames. I use iStat Menus, and I can keep an eye on my RAM usage, and CPU and GPU load.  At no time do my CPU meters go above around 70%, nor am I running out of RAM.  My GPU meter occassionally peaks at 100%, but only momentarily.  It's not being consistently over-driven or stressed much.  You say my system is too puny to handle my work, but the facts seem to indicate otherwise. ... View more

Kevin, I don't believe my hardware is outdated for playing ProRes in a timeline without having it drop frames. If you had read my thread, you'd have learned that this issue seems to be related to my current project, and is something I only recently noticed after about two years of working in Pr CC2018. I'm still investigating what has changed recently that might have caused this new behavior. I've given up on Pr CC2019. I only tried opening my project in it in a process of elimination. I have a separate RAID that connects via USB-C via a USB-C PCIe card in my MacPro, and the issue persists, which rules out my primary RAID. It's not a disk io issue. Looks to be related to the GPU, but I've since learned that frames are dropping in Software Only mode, but less frequently. I imported a ProResHQ clip in to Pr CS6, and it plays there without any dropped frames. ... View more

I tried that CUDA driver, trashed my caches, and re-installed the GPU driver. Tried a new project, imported the old one. No luck. Created a new squence and pasted the old on into the new one. No luck. Created a new project and imported one ProRes422 HQ master, and dropped that into a new sequence, and it's still dropping frames with the CUDA renderer. This is really odd. The previous project I was working on has all kinds of 4K mxf and no frame dropping. This is a real head scratcher. Thanks for trying to help. ... View more

I've been getting remarkably better real-time performance with this card and CUDA enabled in Pr. I'd only noticed this frame dropping recently. It hasn't been happening all along.   I just opened the last project I did and the light is staying green with the CUDA renderer. OK, I might have a corrupted project. I will do the routine on that and report back. ... View more

Yes, CUDA 418.163. And, Nvidia does supply the driver for the Titan, although it might just be the 10.13.6 driver for all their Quadro line. 387.10.10.10.40.130 is the latest version. ... View more

https://helpx.adobe.com/premiere-pro/system-requirements/earlier-versions.html ... View more

Note the Nvidia cards recommended for CC18. The Titan isn't there, because a third party flashed Windows compatible cards to work with OSX, and it was the GPU with the best performance. ... View more

There are no Nvidia GPU or CUDA cards on that list. And yet, CUDA is still supported on OSX in Pr CC18 and 19 in the Rendering options, and my system passes the Compatibility test in CC19. Also, that list is for CC19, and I have the same issue on CC18. ... View more