Export filename doesnt use the file name I say it has to use

Hi Julian,

Sorry. I apologize if your workflow performed well in the past and does not work now. Thanks for writing your bug report and for the information you have provided. Knowing more details can help us troubleshoot for you. This problem might be a bug already fixed in the current version. If you can give more info on the version of Premiere Pro, your system, media, and workflow, kindly leave it in a post in this format: How do I write a bug report? 

I hope the team can restore the feature, or we can help find a fix for you soon. Have a good weekend.

Thank You,

Kevin

Google drive, OneDrive, DropBox, WeTransfer ... they all treat files as if they're documents/spreadsheets. And therein lies a major problem for online video post work. Ann's right, those are all designed for backup situations, not 'live' working situations.

You might get one to seemingly work for a while, but eventually it will bite your backside, and badly. I work for/with/teach pro colorists. They normally worked on projects linked to other facilities, typically with physical file transfers, and did "client attended sessions", that suddenly had to go online during Covid. And tried everything available, including the above listed things. With mostly ... problems.

So if you can work with that, more power to you. But those programs all do things to mod file headers for internal use. Things like added material, copy up next cycle, is one typical sign of some kind added to the file header. This tends to cause issues for file verification in NLEs, grading apps, audio apps ... as something about the header ain't quite right no more.

Plus while a copy/write/delete cycle is going, they will sweep through folders locking a few files at a time. Yea, that's a pain thing too.

So there are some things ... some cost more than others, and may or may not actually work ... that can help with this.

My partner in Cape Town and I in western Oregon use Amazon S3 servers in London, and LucidLink's magical file transfer service. He'll call me to say he's uploading a folder of media for me to edit ... within seconds, the folder appears on my "virtual" LucidLink drive. Another few seconds, I'm seeing the files.

I head over to Premiere, and start importing files. Making a new sequence ... and many of those files haven't even finished uploading from Cape Town to London!

LL somehow knows how to parse file segments as video post apps need to use them ... not as a document app would. And it makes a huge difference. I could work with sequences with files up to around 60Mbps on a 140-160Mpbs ISP speed if latency kept high. Changed to a full gig, and it's pretty solid a lot higher now.

This is a heavily used process in video post at this time. A lot of facilities use it. Even Adobe's "Hollywood" hotshots, Dave Helmly and Karl Soule both have been suggesting it as the probably best such service at this time.

Neil

Write a bugreport.

How do I write a bug report? - Adobe Support Community - 13361863

but no ideas? it always worked before, since the 23.0 update it does this 

 We never had any issues while exporting or doing any file management from windows to google drive.

Yes that is windows, this is Premiere.

Hi, we do all on google drive, except for loading the footage from it.

We never had any issues while exporting or doing any file management from windows to google drive.

If we had to save locally first and then have to upload later, then we'd have to download again if there is any feeback, that's constant downloading. And for someone who is hectic, that doesn't sound great.

I downloaded it and tried again, but it still gives the issue.

Google Drive is fine for backup etc. but not for editing.

Save file first to local drive, then upload.