Quantcast
Channel: Adobe Community : Popular Discussions - Premiere Pro SDK
Viewing all 53010 articles
Browse latest View live

Bin targeting for import in 11.1 is broken?

$
0
0

Hi All

 

I have an extension which creates media on disk, creates a bin in the current project, and then imports the media to that  bin ... nothing fancy.

But since the 11.1 update it no longer imports the media to the targeted bin, instead it it imports it to the root level of the project.

My code for bin creation & targeting (below) is pretty much taken from the PProPanel importFiles : function sample.

 

var targetBin = app.project.rootItem.createBin(binName);

targetBin.select();

 

This worked without issue until the recent 11.1 update.

 

I've grabbed the latest version of the PProPanel sample from Github and have noted the addition to the code in that function:

 

// New in 11.1; you can determine which bin will be targeted, before importing.

 

var currentTargetBin = app.project.getInsertionBin();

if (currentTargetBin.nodeId === app.project.rootItem.nodeId){

  // If we're here, then the target bin is the root of the project.

  }

 

If I'm understanding that correctly the I can use that new functionality to find out where (Premiere thinks) the files will be added, with:

 

$.writeln(targetBin.nodeId);

$.writeln(app.project.getInsertionBin().nodeId);

 

And sure enough, the nodeId returned for my "targetBin" is the same as the nodeId returned for app.project.getInsertionBin().

 

Nonetheless, since 11.1, my files are always imported to the root folder and not the targeted bin.

 

So I've just tested the "Import Files" function directly from the PProPanel extension ... and, on my system at least, it's exhibiting the exact same behaviour as my own panel i.e. it's importing the selected files to the project root, not targeting the "'Targeted by PProPanel import" import bin.

 

Bugger.

 

Is this an issue with the sample code itself, or do you think it might be due to the possible bug in 11.1 noted below

 

Re: Importing video files into a BIN no longer works in CC 2017 Spring Edition

 

Cheers

Andy


How can I open a local folder view by clicking on a link

$
0
0

Hello All,

 

Is there any way to open a local folder (file explorer not a file chooser) from a link in a premiere pro panel? Is this possible using cep API?

 

Premiere Pro version: 11.1.0

Extension Type: Panel

 


Thanks & Regards,
Meet Tank

AE fails to load PRM plugin

$
0
0

I build an Exporter plugin for Premiere as a dot PRM file.  Zal Lam says I need to put it into C:\Program Files\Adobe\Common\Plug-ins\CS5.5\MediaCore folder so the render will be seen in the queue and access MediaCore libraries. 

 

After Effects is trying to load my Premiere Exporter plug-in and giving a failed to load warning. 

 

How do I make my Premiere plug-in only be seen by Premiere and not also by After Effects?

How can I access HTTP services via Extendscript from PPro CC

$
0
0

I attempting to build an HTML5 panel for Premiere Pro that retrieves assets from a third party REST API but there seems to be no support for Socket or XMLHttpRequest objects in this application which there is for others. (I get Error: Socket does not have a constructor)

 

How would I go about making these requests in Extendscript?

Premiere Pro is not recognizing my plugin

$
0
0

Hi,

 

  I am developing One Adobe Premiere Pro Exporter Plugin. Working version: Adobe Premiere Pro 2014.

 

As per the Premiere Pro SDK document, I installed MSVC & Adobe Premiere Pro 2014 in One machine. I set all the environment variables and started my Exporter plugin development.

 

My Final output has,

Exporteri265.prm, + 2 x DLL files. In the PC where I developed the exporter, I copied Exporteri265.prm to C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Plug-ins\Common

and 2 x DLL files to C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\

In My development PC(where it has MSVC + Premiere Pro 2014), all works fine. Premiere Pro is able to load the plugin.

 

Recently we purchased one more license and installed in a Test PC (Only Premiere Pro, No MSVC). In this machine I copied the executable in the same way. But Premiere Pro is not loading my plugin.

It gives one loading error (Log File).


Loading C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Plug-ins\Common\Exporteri265.prm

Invalid registry entry found so the plugin will be loaded from disk.

Loading from disk...

The library could not be loaded.

 

The same technique works fine in my development PC. But not in Test PC.

 

I checked all the registry settings. HKEY_LOCAL_MACHINE. I also moved my .prm to C:\Program Files\Adobe\Common\Plug-ins\7.0\MediaCore. Not working.

 

Can somebody help me?? What is missing in my approach??

 

Regards,

Subash

ExtendScripts JSON object is suddenly undefined?

$
0
0

I've been passing data pretty fluently back and forth between a custom HTML5 panel and ExtendScript, making use of JSON.stringify

 

All of a sudden, today the JSON object is coming up as undefined in the ExtendScript context.

I know it has worked, and now it doesn't.  Why on earth?!

Getting Display Name Of Clip In Sequence?

$
0
0

Does anyone know if there is a way to access the name of a clip in a specific sequence? I'm looking for the name that is displayed, not necessarily the projectItem name.

 

In Premiere you can right click on a clip in a sequence and rename the instance of that clip, but not have that actually rename the source item's name in the project.

I'm looking for a way to view the renamed clip's name (and potentially modify it)

 

I know I can get the source name of a clip with something like this:

app.project.activeSequence.videoTracks[0].clips[0].projectItem.name;

 

But that won't give me the renamed name.

 

Has anyone come across this before? Any help is appreciated!

Thanks!

[Adobe Premiere Pro] Installed Extensions not Showing in Adobe Premiere

$
0
0

[Adobe Premiere Pro] Installed Extensions not Showing in Adobe Premiere

 

Hi all,

 

Complete Adobe-Development noob here -- so apologies in advanced for any confusion on my part.

 

I have a requirement for work to update an extension that someone else (who is no longer available) created for Adobe Premiere Pro.

 

To the limit of my knowledge, it was hosted on Adobe Exchange and ceased to work due to new released Premiere Pro versions. I am tasked with updating the extension to make it compatible with the newest Premiere Pro release (and hopefully just all versions if possible). The extension is just essentially an iFrame redirect to our web application, housed in an Adobe Premiere Pro panel. I plan to just update the versions and submit a "Patch" on Adobe Exchange with the new ZXP Package.

 

Issue:

  1. I cannot see my "installed" extension in Adobe Premiere Pro when testing my ZXP changes -- the extension menu is grayed out / disabled.

 

Attempted Fix Process (learning to repackage the original ZXP file has been an epic journey):

  • I stripped the original ZXP package of the "mimetype" file and "META-INF" directory after learning those are generated after signing the package.

          ZXP Package Files.png

  • I edited the CSXS --> manifest.xml to provide (what I thought was) the minimum version supported (which I hoped would then just be compatible with all new versions)

               Manifest XML File - Updated.PNG

  • I signed the folder with ZXPSignCmd.exe -- this creates the new, signed ZXP file

 

  • I install the new ZXP package with ExManCmd.exe
    • Command: ExManCmd.exe /install com.MyExtension.zxp

 

  • I receive a successful extension installation result:

          Successful CMD Line Install of Extension.PNG

 

  • Unfortunately, I still do not see the installed extension (or any extensions) in Adobe Premiere Pro version: 11.1.2

          Adobe Premiere Pro - No Extension Showing.png

 

Question:

  1. Can anyone tell me what I'm missing or what I'm doing wrong? Ha I feel like I've exhausted all my options / internet-hunting / knowledge power here.

 

 

EDIT:

  • When installing the extension with ExManCmd.exe, the "com.MyExtension" extension folder is being placed in the following path:
    • C:\Program Files (x86)\Common Files\Adobe\CEP\extensions

Is it possible to read a UTF-16 encoded file text file using cep.fs.readFile?

$
0
0

Hi All

 

I'm on a Mac, trying to read a UTF-16 encoded xml/text file from my HTML5 extension panel in Premiere Pro CC2017.

My javascript statement, result = window.cep.fs.readFile(myFilePath);  returns without error, but result.data is empty.

If I open the target file in a text editor application (e.g. TextEdit) and resave it with UTF-8 encoding then everything works fine.

 

Is there any alternative to window.cep.fs.readFilethat I can use from my HTML5 extension panel that would allow me to successfully read/convert a UTF-16 encoded file?

 

Many thanks in advance

Andy

Run .exe File in PR via ExtendScript

$
0
0

Hi,

I'm trying to run a .exe File via ExtendScript. We're doing the same in AE which works fine using "system.callSystem(xyz.exe)" but "system" is unknown to Premiere.

Any ideas how to solve this?

 

Thanks,

Mathias

Premiere, Extendscript,

$
0
0

Hi guys!

 

I am experimenting with a script for premiere that imports new versions of vfx shots into the project.

 

It all works fine unless the media is coming from a mounted volume or from within the user's home folder.

The only error I get it that the media may be corrupted.

 

I'm using something like the following to bring the found files in:

app.project.importFiles(vidFilesToImport, 1, targetBin, 0);

 

I'm thinking it may be to do with the file paths having spaces or irregular characters

 

Any ideas?

 

Thanks!

 

Adam

Retrieve name of Track-local Clip name (not ProjectItem name)?

$
0
0

I'm looking for a way to access the possibly renamed "name" of a clip (TrackItem) in Track. Specifically, I'm not interested in the (clip as TrackItem).projectItem.name.

 

Searching the forums returned some old questions. One used the QE DOM, which does not appear to be accessible anymore. Another suggested exporting the project as FCP XML and parsing the information from the exported XML. This seems exceptionally kludgy and prone to mistakes. The "correct" implementation would probably include using the os.tmpdir API from io.js and passing that to ExtendScript, where you would then export the Project or Sequence and then parse the XML. This seems as though it could get pretty heavy, pretty quickly with complex projects. How performant are the XML export functions?

 

Also, has a better way to do this appeared? This seems like an oft-requested and (theoretically) simple-to-implement feature...

Creating a Sequence by Linking to Preset -- Filepath issue

$
0
0

I am trying to create a sequence from a variety of presets. These presets work well when I am directly linking to the .sqpreset in a drive on my computer, however I would like to package these links within the panel directory so they can work anywhere.

 

When I run the following code it works great if running directly from Extendscript, but when I load it in a panel I have no luck.

 

           var scriptLocation = File($.fileName).fsName

           sliceOne = scriptLocation.lastIndexOf("/");

           var filePlacement = scriptLocation.slice(0, sliceOne+1)

 

             var preset1360 = filePlacement + "Presets/1360x768_30FPS.sqpreset";

             var preset720 = filePlacement + "Presets/1280x720_30FPS.sqpreset";

             var preset1080 = filePlacement + "Presets/1920x1080_30FPS.sqpreset";

 

app.enableQE();

          

        if (seqPreset == "1080"){

                desiredPreset = preset1080

            }

        if (seqPreset == "720"){

                desiredPreset = preset720

            }

        if (seqPreset == "1360"){

                desiredPreset = preset1360

            }

            

  if (seqPreset == "1080" || seqPreset == "720" || seqPreset == "1360" ) {

                qe.project.newSequence(seqName, desiredPreset);

  }else{

                   alert("Please try again." + "\r" + "\r" + "Enter a valid resolution")

            }

       

        }

 

Any help would be great. Making sequences is essential but if I can't package the preset, that'd be a shame.

Opencv and Premier Pro

$
0
0

Hello,

 

I have designed a new process in Opencv.

 

Where do i start in creating a new plugin?

 

There is a wealth of information on using various Adobe applications, however, i cannot see much on creating a plugin from C++ source code. I'd like to get a proof of concept before signing up to and paying for a partner program.

 

Let's say we want to create a plugin that will alter a frame and apply an effect on each consecutive

 

Are there any tutorials?

 

Third-party plug-ins for Premiere Pro CC

Partner with Adobe

Technology Partners

 

Kind regards,

 

Daniel

Node Enabled by Default in 2017.1?

$
0
0

We've begun to take advantage of the Node integration in a Premiere Pro Panel. Based on the documentation, it seems as though CEP 7 supports the following two flags for the CEFCommandLine:

 

  1. --enable-nodejs - According to the documentation, this is disabled by default.
    • [Side Note: the CEP Cookbook PDF contains this Adobe-internal link for "Customize CEF Command Line Parameters".]
  2. --mixed-context - According to the documentation, this is disabled by default.

 

Before attempting to use any Node APIs, I enabled both of those in the manifest.xml for our panel and restarted Premiere Pro (2017.1). Everything worked great.

 

The documentation does not specify if the above two flags are interdependent or not. To test, I decided to remove both flags to ensure that I would get an "undefined" or some other error in our console output. Instead, I was surprised to find that the APIs worked without issue! It appears as though I'm currently able to use the Node integration without specifying any special CEFCommandLine flags!

 

What am I missing here?


Finding a bin with Project.findItemsMatchingMediaPath()?

$
0
0

I'm trying to figure out how to locate a known bin by name. I see that there's a Project.findItemsMatchingMediaPath() API. I've been able to use it to locate Clips but attempts to locate Bins have been unsuccessful.

 

What's the expected way for us to traverse the bin hierarchy? What's the best way to locate a specific bin within the project?

Premiere ExtendScript API Requests

$
0
0

I have a few API requests.

 

  • ProjectItem.isSelected() - Theoretically a ticket for this one already exists. Please add my vote.
  • Project.getSelectedItems() - This would return an array of ProjectItems (ProjectItem[]). This API would allow us to quickly access and loop over the set of items selected by the user, regardless of their location within the Project hierarchy. Perhaps an optional filter ProjectItemType parameter (or array?) could be specified to pre-filter returned values to those of a specified type.
    • This could, of course, be implemented by the user provided ProjectItem.isSelected() was added. Would prefer an official API as it would theoretically be more performant and would cut down on boilerplate code/reimplementation across projects.

 

Thanks.

Duplicate command is not working for custom importer

$
0
0

Hi All,

 

I am working on a custom importer plugin. Basic features are working fine, but, I'm facing an issue with Duplicate functionality.

 

I added a new custom importer clip to project and created a duplicate of that clip (by right clicking the clip in Project window and selecting Duplicate from pop-up menu). Then I added both clip instances to timeline. Now, if I change properties of one clip instance it reflects in both clips. I noticed that both ClipIds are same and they are referring to same media path. I also observed the same behavior in SDK_Custom_importer sample. But, built in 'Color Matte' and 'Title' clips works fine.

 

As per my understanding, Duplicate command should create a new clip from existing clip and new clip should be independent of original clip after creation.

 

How to fix this issue? Is there any selector that I should handle to support Duplicate functionality?

 

Thanks & Regards,

Chandan

Can you do that with the SDK?

$
0
0

I have a question concerning the SDK. In a project, we want to automate some Editing-Functions and the "Premiere_SDK_Guide.pdf" leaves some questions:

 

1) Is it possible to write a plugin, that read pathes from ressources (for example Images and Audio from an XML-file) and put these at specific places on the timeline?

2) With video- and audio-transitions?

 

Even if the above is not possible, than can you automatically:

3) Set Chapter-Markers?

4) Export to Encore or directly as a DVD?

 

Thanks in advance,

Hans

How do you find "App installation path"

$
0
0

 

According to the SDK doc page 117 on presets, you're supposed to install to "App installation path" but I can't find a reliable registry entry that indicates what it is.

 

Premiere Pro presets

...

[App installation path]\MediaIO\systempresets\[exporter subfolder]

 

...

 

I did find...

HKEY_CURRENT_USER\Software\Adobe\Adobe Media Encoder\[version]\AMECodecCache\64\en_US\AppRoot

and..

HKEY_CURRENT_USER\Software\Adobe\Premiere Pro\[version]\AMECodecCache\64\en_US\Default\AppRoot

and...

HKEY_CURRENT_USER\Software\Adobe\CommonFiles\Usage\Agent

 

What is the correct way to detect the installation path?

What if the user has CS5 and CS6 installed?

What if the user doesn't have en_US installed as the language?

 

Is it really a common preset system for CS5 and CS6 as the doc suggests or do you have to put it in both PPro and AME?

 

thx

 

Rallymax

Viewing all 53010 articles
Browse latest View live


<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>