What version of PPro are you using? The last parameter to importFiles(), a 0 or 1, tells PPro whether you want to import these items as numbered stills:
However, this is not using ExtendScript, it's importing an XML file through the File -> Import menu (see image below), which unfortunately leaves all the clips as Still Image rather than Numbered Stills. Ideally I would want to modify the XML so that Premiere would know to take the images as numbered stills rather than still images, alternately I'll have to look at using script to reinterpret all footage as numbered stills - but I don't think that is possible (except by replacing all clips maybe?).
Sorry, I presumed because we're in the SDK forum, you were already using our APIs.
Yes, you could reinterpret existing stills as sequences...
I'd be tempted to create a sequence containing a couple clips made of numbered stills, export FCP XML, and see what's what.
Hi Bruce Bullis, thanks for your replies so far.
Yes, sorry about that confusion with the posting location - I originally posted it in the "main" Premiere forum, but it attracted no answers, and anyway I suppose that this is more of a technical question rather than a Premiere usage question. Especially since I'm starting to suspect the solution will come from using the SDK.
I did try to create numbered stills clips, and exporting as FCP XML, but even if I re-import that same file it will appear as Still Image rather than numbered stills - presumably because the "numbered stills" concept isn't part of FCP XML, or at least not the version that Premiere exports (Premiere still uses FCP7/XMEML instead of FCPX/FCPXML, I believe?). I will be conducting some trials with FCP later today, just to check.
I have not seen anything in the PPro Panel code to re-interpret footage - would that be utilizing "replace media" instead?
Alternately, I might want to look into creating an interface for the editors to take in specific numbered clips based on some parameters they provide (which is basically the same thing the XML file was doing), but all done with the SDK - any pointers on where to start with checking the local filesystem - things like Directory.GetFiles() from C# ? I really would prefer not to use the standard "select file" dialog to pop up for each, since we're talking 10s or even 100s of clips.
1 person found this helpful
This is not related to the script you are trying to write (which I think sounds great), but just to share a workaround I have been using to save me lots of time importing multiple image sequences. If you have each image sequence in its own folder, you can drag and drop all of them into After Effects, and it will automatically process them as image sequences, bringing in clips of each shot. Then you can simply copy and paste that into Premiere and you will effectively batch import them as image sequences. A little bit of a workaround but it saves a lot of time
> (Premiere still uses FCP7/XMEML instead of FCPX/FCPXML, I believe?)
Thank you Mitch, while it's (unfortunately) not really practical in our workflow/pipeline, I'm sure it'll be useful for others in a similar situation who come upon this post later.
Thanks Bruce, I will look into the ExtendScript toolkit, it sounds very useful (debugging scripts is definitely a hassle otherwise!)
Final Cut Pro does indeed not have the concept of an image sequence - in their world, every image is imported separately and placed on the timeline in a, well, sequence - which of course is also what happens "behind the scenes" when you render an image sequence - but the lack of an image sequence as a distinct entity is probably why no provision for it exists in the XML format.
That would explain why there is no way to tell Premiere to import as image sequence when doing an XML import.
Would it be worth putting in a feature request for expanding the XML spec with something to support image sequence in Premiere (and any other software that utilizes the same or similar concepts), or is the XML Import feature a "closed chapter" ? I suspect it's probably the latter, since there has been no updates to the XMEML spec in years from Apple's side, and it's not likely there will be since they have long since switched to FCPXML instead.
I don't know that it's necessary to expand a spec...
PPro can successfully export, and import, an FCP XML of a sequence, containing a sequence of stills. The information is in there; I've asked where.
Well that would be very good news indeed if it turns out to be possible after all - I had just about given up hope on it, and still have my doubts.
Crossing fingers and hoping I was wrong!
To further allay doubts:
0. Launch PPro.
1. New Bars n Tone.
2. New sequence (doesn't matter what format)
3. Insert BandT into new sequence.
4. Export movie --> Targa sequence, check the import into project box.
5. In sequence, replace BandT with newly-imported image sequence.
6. Export as FCP XML.
7. New project (for testing cleanliness)
8. import FCP XML
Result: Hey look, a sequence containing a sequence of stills, via FCP XML!
Upon further consideration, it was QE tester error. I see the same results as you. Looking into it...
2017.0.2 - 11.0.2 (47) Build on windows