A different point of view might see Kyle's 'fix' as a long-winded manual workaround to a glaring workflow design issue. I'd argue that the fix is for Adobe to add reliable 'Match Source' options for audio in the encoding presets (just like it already has for video) and allow their use for ingest presets. ... View more

> 2) I wish in the graphic styling there was a way to make the background of the text a "full width". Right now I am having to create an essential graphic layer with a rectangle to place behind the text. While the caption graphic panel allows for background it only is the width of the text line itself, with some optional padding.   This... sadly. The lack of a non-adaptive background option is really the only thing stopping me from jumping all in with the new captioning workflow. ... View more

Thanks Bruce ... just for clarity, I'm not running the ARM native (beta) versions of any of the Adobe apps. I'm currently working on an M1 Mac, yes, but I'm running only the regular (non-beta) Intel version of the apps, specifically Premiere Pro.   Understood that CEP extensions are not supported in the M1 native beta... but are they also not supported using the Intel version under emulation? ... View more

Hey Team Just downloaded and tested this in the 14.9.0 Beta (29R) ... great job. I have just one small(?) request which would greatly enhance the chances of pushing it's adoption here (for burnt-in subtitling) : could you please add an option for non-adaptive backgrounds for the subtitle instances? All our onscreen text must strictly adhere to our house style, and that style requires a static background box/strap behind our subtitle text... the text changes but the strap does not. This new captioning workflow allows me to quickly and easily import / create subs for our programmes using srt files, and the flexible positioning tools mean that I can ensure those subs fit with our house text and non-stanadrd positioniong requirements exactly ... but having done that, if I have to thereafter manually edit in a separate essential graphics background box/strap element for each subtitle instance, then sadly the otherwise clear advantage of the new workflow is, for me, lost. For reference, at present I use a custom coded extension (panel) which reads plain text/srt files, and from that creates, imports and places legacy titler instances accordingly... its super fast and works perfectly... but it would be great to be able to finally drop our dependency on the legacy titler. Cheers Andy ... View more

Did you export screeners of your edit via Media Encoder at any stage?   Did you leave those completed export jobs in the Media Encoder queue? If so, then hovering your mouse on that queue item will show you the path to the simplified (sequence only) temp project file that was created when the sequence export was queued from PPro. You can use that project file as a base for rebuilding your project ... its not everything but it's the most important bit ie your edit decisions.   Even if its not still in the queue its probably still worth checking the temp directory... if you're very, very lucky (albeit unlikely) then you may be able find something .. in the Finder, press Cmd-Shift-G to get the 'Go to Folder' window, then type /var/folders and press 'Go'.  Search that directory for any occurence of 'prproj' (Premiere Pro Project).   Unfortunately for you, OS X is very good at automatically cleaning up its temp directories. If you were on Windows its almost certain your temp project files would all still be in the temp directory. ... View more

In the Audio Track Mixer panel, use the map & pan controls to create the track separation you need, eg: map tracks A1 & A2 to output 1&2, pan A1 left (-100) A2 right (+100) map tracks A3 & A4 to output 3&4, pan A3 left (-100) A4 right (+100) ... View more

Can't help Dan, but can certainly commiserate.. it happened to me yesterday. Complete nonsense message as I was exporting a clean untexted version of a film at the time. And for good messure, the font used throughout, in the texted version, was absolutely not changed. Oh well. The 'fix' was indeed to simply restart the export ... no need to change anything as there was nothing actually wrong (other than Premiere).   Sorry it's not more helpful, but at least you know you're not the only one. Cheers Andy ... View more

Hey Christian   Can I suggest you test with a different source clip that is not Apple ProRes format ... or if you prefer you could just transcode that same clip to something like Cineform first ... and then repeat your side by side test.   Cheers Andy   ... View more

What is your Video Preview codec and what are your Export settings? ... View more

>Is Premiere Pro the only program that will allow for "masking and tracking"?    No, it isn't... but asking if you could use 'other' software is an odd question for an official Adobe support forum. 😉 That said, search online for Davinci Resolve, the free version is all you need... but, if you're a long time user of Adobe software and already familiar with its user inteface, then paying a single month's subscription would help support the software you already know, plus it might save some discomfort wrestiling a new application. ... View more

In case you haven't seen it, here's a link to that function in the Premiere Pro ExtendScript-based API docs https://premiere-scripting-guide.readthedocs.io/4%20-%20Project%20Item%20object/projectItem.html#attachproxy ... View more

I'll add something that to me seems pretty obvious ... using the EGP Browse tab for storing and applying titles (mogrts) is not the problem, what's gone missing is the means to sort/browse/filter 'timeline instances' of EGP titles.   For what its worth, I rolled my own 'Timeline Index' panel for Premiere years ago, and it works a treat for the above issue ... maybe its time Adobe played catch up and provided a properly integrated Timeline Index panel for all users.   Andy ... View more

No need to nest if you use the Video Effects > Distort > Transform effect to do the rotation. Add Transform Effect first and Crop Effect second. ... View more

Yes... you can mask effects applied to an Ajustment Layer and the masked effect applies to the multiple layers/tracks underneath.   If you want to mask and apply Motion, Scale and/or Opacity properties then add the Video effects > Distort > 'Transform' effect, and add and adjust the mask on the Transform effect as needed.   ... View more

Theres no direct method, but you can try to infer it by considering how different media types will be handled by different methods eg calling canProxy() on Video/Movie clips will return true ... but on Stills will return false. ... View more

Yep. Just tested, works perfectly. Thanks again. ... View more

Hey Bruce, I'm refering to the unsupported method, detailed above, for accessing the Source Text (object) of a basic Premiere Pro authored Text Item ie MOGRT clip instance, using: JSON.stringify(app.project.activeSequence.videoTracks[track].clips[clip].components[3].properties[0].getValue());   In 'OldWorld' that call returns a string that contains the Source Text object (which can be succesfully manipulated as directed above). In NewWorld it seems to return just a single character      ... View more

Just FYI for anyone who might stumble across this topic (like myself)... a quick test seems to suggest that this method is no longer possible with 'NewWorld' scripting enabled. Works well otherwise tho.     ... View more

Hey dpt12   I would ask, how badly to you need to force this behaviour, and potentially, at what (performance) cost?   You could, for example, consider building and displaying a basic representation of the active timeline within your panel, and then allow your panel's users to interact with that represenation ie within the panel. In that manner you might be able to detect the drag and drop events (all within the panel) and trigger the matching/ required behaviour in the actual timeline.   A possibilty for moving forward, maybe... if you're determined enough. Cheers Andy                 ... View more

Hey Bruce   Thanks for the reply and apologies for the unintended shade! I blindly assumed support for Productions in the API would be limited by it being so new ... hadn't even looked. Thats my bad.   I just had a quick browse : Production.path gets me to the production folder (so I can easily discover structure and all contained projects - and thus open those as necessary) and Production.projects returns an array of all currently open projects.  Assuming its possible to move projectItems between open projects then it looks like it could already be pretty straightforward to automate. I haven't tried it yet (as per my original post, I'm really just thinking out loud, I haven't convinvced myself I need to do it at all)  but is moving items between projects really as easy as currentProject.projectItem.moveBin(targetProject.targetBinItem)?   If so, two thumbs up for rootItems!   Thanks Andy ... View more

Hi  Zeracosaitam   If all you need to do is create a playback 'playlist' as such, from a single clip, then Premiere Pro is probably not the right software for the job... its more intended for the original creative act of assembling assorted clip fragments to create a whole (sequence), which would normally be a manual/creative/interactive process. Its not daunting, its called editing.   That said, if you really do just want or need to assemble something from a predeterined list of ins and outs, then I beleive Premiere supports importing an EDL (Edit Decision List). Might be worth investigating.   Cheers Andy ... View more

Hey Denis   I convereted my current short (30 minute) documentary project to a 'Production' recently, following the reference documentation that Neil has already linked above. It was a pretty straightforward process and my efforts were rewarded with a much snappier 'Current Edit' project... but be careful not to guzzle to Kool Aid too quickly. For my preferred workflows, I did run into a few caveats, after the fact. Not showstopping problems by any means, but I'd say that knowing those limitations, now, will certainly help guide how I set up such my 'Productions' in future.   1) Search Bins will only work at a project level, not a production level. If you're embarking on a project that will contain vast numbers of clips, and if in your workflows you use metatdata to log/tag and organise that media (through Search Bin functionality), then be aware that all of your production’s media (or all that you need to be able to search at any one time) will need to live within a single project… so, for example, don’t break the rushes down into ‘dailies’ sub-projects if you want to be able to search across multiple days. 2) Splitting sequences into different projects currently prevents the ‘Reverse Match Frame’ function from working. ie A match framed clip from a sequence in one project cannot be reverse match framed into a sequnce in a different propject. Hopefully that’s something that can be fixed, but if it’s a function you need now, you need to keep all sequences that need to interact in that manner within the same project. 3) Clip usage figures are calculated ‘per project’, not ‘per production’. If you tend to use Video Usage and/or Audio Usage metadata to track and guide media usage in your edits, you’ll need to keep the edit(s) you’re tracking in the same project as the media. 4) Nested Sequences need to live in the same project as the Master Sequence(s).   There may well be other advantages/disadvantages... everyone's workflows are different, so the process will obviously affect different users in different ways... but those are the ones that jumped out for me.   Cheers Andy ... View more

Hi Kevin I'm still using Legacy Titler because I have workflow automation tools built around it. Fast / efficient solutions for converting Plain Text into a project bin full of subtitle text items or SRT files into fully subtitled sequences. I have looked into converting those tools to use Essential Graphics but last time I checked (a few months back) importing/instantiating hundreds of MOGRT instances was painfully slow and clunky, so although the tool is prepped, I've stuck to Legacy Titles. Am also quite the fan of my title tool elements/instances having associated project items. Probably time I looked again in the following regard, but if I remember correctly, theres a disparity of support in the scripting API between After Effects built MOGRTs vs Premiere's native MOGRTs... with the former getting all the love. Cheers Andy ... View more

Thanks Matt, yep thats the process I arrived at too. Appreciate the confirmation. Will follow up with Bruce re scripting too. Cheers Andy   ... View more

Its a bug in the latest versions of Premiere CC2020. Your options are to switch your Playback/Rendering engine to Software Only, roll back to an earlier version of Premiere that doesn't have that bug (eg 14.0.4) or, if you're not doing mission critical work, you can install the latest CC2020 'Beta' version (which addresses that issue, but is just a test version for upcoming changes/fixes and may not be stable). ... View more

Lol. I actually spelt out the why in the original post Neil 🙂 Totally appreciate that not everyone may want or need to do it ... but I dare say the same could be said of any feature. For those that might need and use it, the organisation model of a Production could be replicated in a standalone project easily, effectively the same way we have been working without Productions for years, mapping Production > Project, Folder > Bin, Project > Bin, Bin > Bin. Hopefully the scripting API will eventually allow for it. ... View more

Thanks Neil Yes, I have read that but it doesn't address my post ... hence my post. Have edited the 'Subject' line to better reflect the question. Cheers Andy ... View more