Dragging audio files directly via Drag and Drop from a web page to Premiere Pro Timeline

@MyerPj 
> I don't ever drag and drop onto the timeline, always into the project.
Okay, I seed.

Did I understand you correctly: You're using Drag and Drop (sometimes) but only for files already located in a local content folder and then drop these files to your "project window" instead of "timeline window"?

I'm not agreeing with any of this. There are all kinds of paywalls and protection for files out there in wild on the web. I don't ever drag and drop onto the timeline, always into the project. No thanks.

Having been around this app for several years, I have seen numerous instances of what were thought minimalist changes wreak havoc unexpected.

Might it be easy enough to code across OS/hardware needs? And work within and augment the current file handling capabilities? Maybe.

Might be more work than it seems. Just as a possibility.

@R Neil Haugen 
> So this would also require the devs...
Unfortunately, yes - and that's why I wrote my post as an idea for an extension.

But the effort is rather low.

I can say that because I programmed a small working example in c++ by myself this week, also to check the effort involved.

So this would also require the devs to create an automated file handling and moving process. Ok.

@R Neil Haugen 
> So you still need to manually find the file, then move the file to a proper location ... right?
No, fortunately not.

Since the target application (e. g. Premiere Pro) will get informed by the OS about the temporary local "transit" location of the just dropped file (by a normal DROP event), the target application (e. g. Premiere Pro) also has every opportunity to immediately determine the next steps by itself.

This means in case of the audio file I mentioned, this file can be immediately moved, converted from 44100 to 48000, or even discarded due to incompatibility by Premiere itself.

I believe that "Drag and Drop" from "website to timeline" can speed up the workflow considerably in some cases, especially when it comes to serveral individual AI-generated voice prompts, as in my case, which have to be generated by a web service due to the very complex AI models behind that process and the variety of voices.

So you still need to manually find the file, then move the file to a proper location ... right?

@R Neil Haugen 
Ah, okay. Please think of smaller audio files (like sound fx or text to speech) rather than large video files at this point.

And btw the %Temp% folder is only needed for a short time "for transit" so that the application can get "a local path" rather than a "url" to the file during the drop action and then can take the file and MOVE the file to the project folder or your prefered location.

I must say having the OS or a browser downloading significant-sized asset files and parking them in buried locations, probably on the C drive, is not at all attractive.

As in the H*** NO! category of 'attractive'.

I would never want anything to download crap to splay it aound the C drive. So ... it would need to have some sort of option to intentionally park things, in a properly organized manner. That organization determined by individual users somehow, probably.

As we all work differently.

@R Neil Haugen 
> Premiere needs all assets to be 'local', ... , Premiere would have to download the asset to local storage first.
No, since the Webbrowser does this for you - Yes the browser will do that work for you :-).

In case of "Microsoft Edge" on Windows or "Google Chrome-Browser" on both Win and Mac will care about the async download and will place the downloaded file in a random %Temp% folder on your local hard drive (e. g. C:\Users<YOUR-USERNAME>\AppData\Local\Temp\chrome_drag<PID>_<RANDOM NUMBER>\Audio.wav in case of Windows 10/11 where \Audio.wav will become the name the website can force to be the name).

But since downloading bigger files can end in some seconds of download time, it's good practice that the JavaScript behind the source website pre-loads the file in the background (e. g. with an ajax get/pots request) and when the user start dragging the file to the os desktop or to an application like Premiere Pro, this pre-loaded file is already in client computer's memory so the Darg and Drop will only take the time of copying the BLOB data in memory to file to the %Temp% folder and within the DROP event the client app will receive the complete path to that file as a normal file drop (in case of Windows this is normaly a CF_HDROP with a filled DROPFILES structure).

As I wrote, i have both a working website to drag from and a win32 client app to drop to as a working example.