Download the file first, then import. PPro needs footage to be from either:      + a local path      + mapped network drive (Windows)      + mounted network volume (Mac)      + UNC path ... View more

Sure; change the sequence's zeroPoint. var startTimeOffset  = activeSequence.zeroPoint; ... View more

You'll need to export the title (from the project, to a .prtl file) first. https://helpx.adobe.com/premiere-pro/using/creating-editing-titles.html ... View more

There is no way to access the Premiere Pro clipboard, in the manner you described. What do you want to DO, with those items you'd like to copy? Perhaps there's another way. ... View more

There is no way to add clips to a timeline, through the supported, public API. ... View more

There is no concept of 'selection', in the PPro APIs. You can create sequences from a preset (.sqpreset file), and there are ways to add a given projectItem to an existent sequence... If you can provide more details of the workflows you'd like to support [write me directly; b b b at adobe dot com], we can provide better guidance. ... View more

From JavaScript? Yes; search the CEP_HTML_Test_Extension‌ you're already referencing, for 'requestOpenExtension'. What would you like to do in your dialogs? ... View more

PPro offers no APIs for keyboard shortcut creation or manipulation. ... View more

ScriptUI dialog components aren't supported, but if you need a value in ExtendScript, this works: var coolestNerds = prompt ('What application has the coolest API Engineering support?', 'Premiere Pro, of course.', 'Big Decision'); alert(coolestNerds); ... View more

Namespacing exists to allow for differentiation between different schemae. Your custom schema and the default Dynamic Media schema could both have fields named 'tapename'. More info than you could EVER want on XMP: http://www.adobe.com/products/xmp.html ... View more

What is QE? Short for Quality Engineering. The QE DOM was created for internal automation and testing use. Still, as you noted, it provides loads of interesting and useful functions. You also mentioned the QE DOM's Achilles heel: its project model refreshing is unreliable. Thus, the QE DOM remains officially unsupported, and not recommended. Since CC (2013), we've been gradually moving compelling and safe functions from the QE DOM to the 'paved road' regular DOM. No dates, but we realize that sequence element manipulation [intelligent re-timing of clips, clip insertion, setting opacity...] is a pretty compelling area for panel developers, and it is appropriately prioritized in the PPro API backlog. I'll add your vote. why is there no documentation on not just QE, but the rest of everything within Premiere's capabilities of extendscript? In a former Adobe life, I wrote the After Effects C++ plug-in SDK's 350-page .pdf, in FrameMaker; indexed, cross-referenced and hyperlinked, which documented every param of every function, noting changes across versions...which almost no one ever read*, before simply asking me their question. Now, I spend less time in FrameMaker's print dialog inserting hand-coded DSC comments into the PostScript stream for Acrobat Distiller, so that my function suite headers remained clickable in the .pdf it eventually produced... ...and more time working with customers, writing sample code, and answering developer questions. [On that note—we'd be happy to discuss whatever integration you'd like to create, and provide whatever help and guidance we can.] The quick-start guide, the sample, and our help have been sufficient to get ~140 panels in the field; hopefully, we can get you going as well. Hope [above] helps; feel free to ask me anything [here, or direct; b b b at adobe dot com] -bbb Bruce Bullis Integration Engineering Manager Adobe Pro Video bbb@adobe.com * I'm reasonably sure Brendan Bolles @ Fnordware, Pete & Pierre @ RE:VisionFX, and Paul @ Profound Effects, read it. Also, Zac's current AE API documentation is much better than mine was, and is now built in InDesign. ... View more