Hi Ken Check that your project is set to use GPU acceleration (not Software Only). In the File menu > Project Settings window > General tab choose Video Rendering and Playback : Renderer > Mercury Playback Engine GPU Acceleration. Hope it helps Andy ... View more

I didn't have the master files to make proxies from. The masters were in Kashmir,  whereas I am in Kuala Lumpur... bit tricky ingesting from there myself because the hard drive cable wasn't quite long enough.    ... View more

Hey Fran If you're willing to slum it and use the Legacy Title format then what you want to do is possible via an ExtendScript based panel extension...  but there would be hoops to jump through. For example,  you can't save a Legacy Title Template with the CC 2017 release,  so you'd have to also install an earlier build (eg CC2015)  in order to  set up your templates. If that's something you'd want to try then (Legacy) Title Templates (.PRTL) files are XML files that can be easily manipulated programmatically. Basic process would be to a) read in the Legacy Title Template file and the Excel Spreadsheet, b) for each title instance (from spreadsheet) write a modified copy of the Legacy Title Template file to disk, c) import the generated Title files, d) insert the imported Titles into the sequence accordingly. I think pretty much everything needed for the above is covered in the various sample panel scripts, especially the PProPanel sample. GitHub - Adobe-CEP/Samples: Samples for Adobe Common Extensibility Platform (CEP) Cheers Andy ... View more

Hi Jonathan Suggest you re-ask your question in the Premiere Pro SDK subforum... this may well be possible with a bit of scripting,  just not sure Adobe have added scripting support for the new Title format yet. For what it's worth tho',  with the help of the folks on the SDK forum,  I built and now use a custom extension to generate (Legacy Title based) subtitles for my programmes from a plain text file... saves me hours of work. Cheers Andy ... View more

https://forums.adobe.com/people/Trent+Happel  wrote Proxy does not currently fully support Interpret Footage. Hi Trent Is this still an issue / unsupported in the latest Premiere CC version? Thanks Andy ... View more

Hey Bernard If you're sure its a CC2017 issue then I'd strongly suggest you reinstall CC2015.4, just for compatibility with those older projects. For what its worth though, old (Legacy) Titles are still accessible on my own Windows 10 / CC2017 system... last time I checked I can open and edit old projects with Titles intact. I can work with template (PRTL) files (although to do that I now use the Media Browser panel rather than the Titles > Templates menu). The only thing I can't do is export new template (PRTL) files. Cheers Andy ... View more

sberic  wrote For instance, if the time specified for overwriteClip is in the middle of another clip on the Track, does the entire clip get erased and the current clip inserted at the specified location, or is the existing clip get truncated at the point specified before insertion? Hey sberic, am I right in guessing you are not a video editor? In NLE terms, an insert operation adds new media, starting at the specified frame, and retains all existing media by moving it after the newly inserted media. An overwrite operation adds new media, starting at the specified frame, and replaces (overwrites) any existing media that previously occupied that space. So with respect to your question, the existing clip gets truncated at the point specified, as will any following clips that also intersect in whole or in part with the new media added to that track. Hope that helps Andy ... View more

Unfortunately, that code only partially solves the problem. The function would be more aptly named "searchForBinWithNameInProjectRoot". It does not help if you have a path that goes beyond the root bin. You're absolutely right ... I assumed it was recursive without actually checking. Apologies for the misdirection. ... View more

The only current option is to install a earlier version of Premiere e.g. CC2015 ... I believe you should be able to install this alongside your current version?  If you need to build and export a PRTL file you would then create it and export it from CC2015. Appreciate that Adobe wants us to move forward with EGP/Title Tool, but they seem to have forgotten about the larger 3rd party ecosystem in their hurry for us to do so. A bit of a misstep, but perhaps not insurmountable if you keep an older version of Premiere installed specifically for that purpose. ... View more

I suspect your assumption is already correct steric, and the best I can do is personally is tell you what I believe it to be : the 'rootItem' is the project's index as an object...  in the sense of the UI, I think of the 'rootItem' as being the Project Panel, whereby the children of that root item are the items displayed in the project panel. Thats my interpretation anyway. Hope it helps Andy [Edited for clarity] ... View more

Hey sberic, there's a function in Bruce's PProPanel Premiere.jsx script that specifically addresses this : searchForBinWithName Samples/Premiere.jsx at master · Adobe-CEP/Samples · GitHub ... View more

Unfortunately, I don't think this issue was addressed yet... or at least, it wasn't working for me yesterday, on my 2017.1.1 Windows box. ... View more

Hey Dogminder XDCAM HD422 is a 50Mb/s codec... that's a data rate of 50000Kb/s. Cheers Andy ... View more

Hey Nehru, As has been explained, there is no "JavaScript API" there is an ExtendScript API for interacting programmatically with Premiere, and the functionality for getting and setting keyframe values within Effect components is demonstrated in the PProPanel sample Javascript API to change Premiere Pro Lumetri color Basically, you have to navigate through the active sequence to select the target clip, within the clip to select the target component (eg Lumetri Effect), and within the component to select the target property (eg Exposure etc) so a particular property (eg Exposure, Contrast, Highlights ect) would be referenced using something like: myEffectProperty = app.project.activeSequence.videoTracks.clips .components .properties where 'i' is the target track's index number (within the sequence) where 'j' is the target clip's index number (within the track) where 'k' is the component (effect) index number (within the clip) where 'l' is the property index number (within the effect) A quick scan of a targetted clip (using code derived directly from the PProPanel sample) reveals the following parameters (properties) for a Lumetri Color effect. var clipComponents = clip.components; if (clipComponents){       for (var cc = 0; cc < clipComponents.numItems; ++cc) {             $.writeln('component ' + cc + ' = ' + clipComponents[cc].matchName + ' : ' + clipComponents[cc].displayName);             var componentProperties = clipComponents[cc].properties;             for (var cp = 0; cp < componentProperties.numItems; ++cp){                   $.writeln('param ' + cp + ' = ' + componentProperties[cp].displayName);             }       } } component 2 = AE.ADBE Lumetri : Lumetri Color param 0 = Blob param 1 =  param 2 = Basic Correction param 3 =  param 4 =  param 5 =  param 6 = Input LUT param 7 = HDR White param 8 = White Balance param 9 = WB Selector param 10 = Temperature param 11 = Tint param 12 = param 13 = Tone param 14 = Exposure param 15 = Contrast param 16 = Highlights param 17 = Shadows param 18 = Whites param 19 = Blacks param 20 = HDR Specular param 21 =  param 22 =  param 23 = param 24 = Saturation param 25 = param 26 = Creative param 27 =  param 28 =  param 29 =  param 30 = Look param 31 = Intensity param 32 = Adjustments param 33 = Faded Film param 34 = Sharpen param 35 = Vibrance param 36 = Saturation param 37 = param 38 = Tint Balance param 39 = param 40 = param 41 = Curves param 42 =  param 43 = RGB Curves param 44 = HDR Range param 45 =  param 46 = param 47 = Hue Saturation Curves param 48 =  param 49 = param 50 = param 51 = Color Wheels param 52 =  param 53 = HDR White param 54 =  param 55 = param 56 = HSL Secondary param 57 =  param 58 = Key param 59 = Set color param 60 = Add color param 61 = Remove color param 62 =  param 63 =  param 64 =  param 65 =  param 66 =  param 67 =  param 68 =  param 69 = Refine param 70 = Denoise param 71 = Blur param 72 = Blur param 73 = Correction param 74 =  param 75 =  param 76 = Temperature param 77 = Tint param 78 = Contrast param 79 = Sharpen param 80 = Saturation param 81 = Saturation param 82 = param 83 = Vignette param 84 =  param 85 = Amount param 86 = Midpoint param 87 = Roundness param 88 = Feather param 89 = param 90 = SpeedGrade Custom param 91 = Custom Layer param 92 = unused param 93 = unused param 94 =  param 95 = param 96 = param 97 = Embedded LUTs Cheers Andy ... View more

Well, you could just put your stereo audio clip in a mono audio track... but as Meg The Dog says,  more info would likely lead to the best solution. ... View more

Hey Jacob I have a (Mac) plug in called Elastic Aspect which I (re) made for the folks at GoPro that does a horizontal anamorphic like stretch on an image. It's not designed to be a technically accurate lens distortion removal tool (it's more a creative tool for redistributing pixels on a horizontal axis)... still,  if its of any use you can access it via FxFactory in their 'Free'  section. Elastic Aspect | Life through the Canvas Window Cheers Andy ... View more

Hi Peter The toggle proxy button is used to toggle proxy use on/off in the timeline... but regardless of that setting, Premiere will always use the full res on export if it's available. Cheers Andy Aljazeera International (M) Sdn Bhd (704385<tel:704385>-V) ... View more

Nope, it seems like a no-brainer, but that little checkbox of joy has yet to appear... one day maybe, or maybe not. 😕 ... View more

I hate to say it,  but have you tried turning it off and on again? In similar situations (stuck renders/exports)  I find restarting my PC fixes the issue. ... View more

Hi amyh, apologies for any confusion, what I'm noting here is not the exact same issue that you are reporting, I'm simply offering a similar experience (an issue with the application of a Lumetri effects in the Export Settings dialog/process) as support to the fact that such issues do exist ... and giving you the workaround for my issue, as it may be possible that it will work for you. So to answer your question: From the Lumetri Look/LUT >> Applied: popup menu in the Export Settings dialog I set up all my required export settings in the Export Settings dialog, including selecting my Lumetri Effect (from the Lumetri>Applied popup menu), and then save those combined settings as an export preset so that I can reuse that settings combination quickly and easily whenever necessary. But when I apply my export preset (with the Lumetri Effect applied as part of the preset) the effect does not get processed in the export, nor is it visible in the Export Settings >> Output tab. My workaround is that whenever I apply that preset, I then also re-apply the desired Lumetri Effect in the export dialog (again from the Lumetri>Applied popup menu) before I press the Export/Queue button... and that seems to work. After reapplying the Look/LUT I can preview the effect in the Export Settings >> Output tab and the exported file does have the effect applied.  I have no idea why it doesn't work directly from the preset, it always used to, but at some point a couple of versions or so ago it stopped. Hope it helps Andy ... View more

If the primary issue you're facing is due to format support then one solution would be to make use of Premiere's "Ingest" functionality to transcode the media you import into Premiere into a common format (ie one that's supported by Resolve). ... View more

I've seen a similar issue amyh, with a custom export presets that includes a Lumetri  Effect (a strict broadcast legaliser) ... if I simply choose the export preset and export then the Lumetri Effect doesn't work, if I choose the export preset and then manually re-select the effect (even tho it's already selected) then it works just fine. ... View more

Premiopolis  wrote selects all timeline clips whose name matches MOGRT you're working with (requires an reliable naming convention to work) and automatically selects only the items you intend to replace.  Custom built panels are certainly a lot of fun, but assuming you're already following a reliable naming convention, couldn't you select the target items by just using the built-in Find command? ... View more

https://forums.adobe.com/people/R+Neil+Haugen  wrote You can at times install the first build of a series ... and update it incrementally. If done ... carefully. Stopping at the increment you want. Now ... project files ... never go backwards. Neil True... but that's not because they "couldn't" , its because Adobe chooses not to support such workflows. (As you know) to some extent, a simple change to the version number in the header of the project file xml is enough to enable an earlier version to at least attempt to open a newer project. ... View more