Copy link to clipboard
Copied
Hi,
We have a project coming in that was aready started in Premiere Pro 2025.1. The editor was having big problems with Drawbot Errors and Long Relinking Times. The media is about 40TB and the project about 300GB. Searching the forums and I can see others are having similar frustrations.
I have read Disabling Hardware-Accelerated GPU scheduling can help, aswel as keeping the project files unnested in folders. Is it just accepted that this is how Premiere works?
Is there any other good advice on how to minimize this? TIA
Rory
Copy link to clipboard
Copied
Might want to split the project up in smaller projects.
Need more info:
Copy link to clipboard
Copied
Yes, we've to wait until it arrives but my understanding is that is is a "A year in the life" type show and each month is a project under a master production. But they will obviously be needed to be intercut with each other.
Copy link to clipboard
Copied
This drawbot error was still present in 25.1 (on Windows), and for some conditions, there was a workaround.
We need to know your OS.
@Peter_Antal True? Any thoughts about the relinking times?
Stan
Copy link to clipboard
Copied
Hi Stan,
THank you for the reply. I am not sure where the project has come from but we will be working on Win11 with the media on an EditShare. Is the fix for the drawbot to turn off to "GPU accelerated UI renderering" from General Preferences?
As we are working in a production, would I be correct in saying that the project files cannot be unnested like other on the internet are suggesting?
We are currently copying the media up to shared storage. In a avid world we would generally keep the Project (Production) on a seperete workspace to the media. And the hires and proxy media on different workspaces also. Is this best practice for Premiere or does it matter as much?
I have see some proxyies in a folder labeled "proxies" alongside the HiRes media. Is this an ok workflow or should they be seperated?
Thanks again for any assistance,
Rory
Copy link to clipboard
Copied
Sorry; by OS I just meant operating system. The error I was pointing to is Windows only.
I only dealt with an oddity where having the Progress Dashboard open caused the problem.
Someone else is better to comment on the files issues.
Stan
Copy link to clipboard
Copied
I would recommend using the Productions mode for that. Which would make it vastly easier to both work in and add to over time.
Productions has an overall Productions folder (including on disc) that Premiere creates. And a Production file. Inside that folder in the Production, you create subfolders for sections of the project ... maybe Media Storage, Working Sequences, Finishing, whatever fits.
Then inside those folders you create projects ... in the Media storage, you may make one project, or ... you might make subfolders based on the time/segement of the project. Such as Month 1 or whatever. And in those folders you make projects to store the appropriate media.
In the Working Sequences subfolder, you create projects for your sequences ... simply drag/drop media to them from the Media folder/projects. It doesn't create any duplicate media ... just tracks the media from the media projects to the sequence projects.
But the whole thing is easy to organize, stays clean, works faster than the old single project file with everything in it, and doesn't ever bog down.
Premiere Pro Productions Introduction
Using Productions in Premiere Pro
Adobe Long-form and Episodic Best Practices Guide
Jarle’s blog expansion of the pdf Multicam section: Premiere Pro Multicam
Copy link to clipboard
Copied
Hi Neil,
Thank you for the information. I think the info I was working on with projects behaving better when outside of nested folders is outdated, pre productions. The main issue was the editor complaining about long production opening times (saying relinking) and the drawbot error. The assistant is going though everthing now and try to reorganize it best , I am trying to preempt similar prolems happening here.
Thanks,
Rory
Find more inspiration, events, and resources on the new Adobe Community
Explore Now