Re: how to made plugin using flex3 application

Zac Lam · ‎Jun 06, 2011

Hi there, You'll want to display any UI during the esSetup call into the transition plug-in. This selector will be sent when the user chooses the Custom setup button for the transition in the Effect Controls Panel. The SDK transition sample already displays a MessageBox() here. Regards, Zac

Zac Lam · ‎May 25, 2011

Hi there, For Flex questions, I would suggest posting in the Flex forums here: http://forums.adobe.com/community/flex Regards, Zac

Zac Lam · ‎May 20, 2011

Would the scripting command for File > Save As > Save a Copy be what you're looking for? Not sure if that is right for your needs, because it does show UI, so it wouldn't run in the background. But if that's what you're looking for, I could dig up the command ID. Zac

Zac Lam · ‎May 13, 2011

Hi there, Unfortunately the formatting didn't make it through in your post, so I'm not sure which part of the function you had the question about. In general, this function is called in response to the esExecute selector, and handles the actual rendering for the transition. Regards, Zac

Zac Lam · ‎May 12, 2011

Hi Dylin, Yes, you can create a Comp marker with the AEGP API. Creating markers on layers is demonstrated in the Easy Cheese sample. The only difference is that you’ll need to use AEGP_GetNewCompMarkerStream() to get the stream for the markers in the Comp. Here’s an example by modifying the Easy Cheese sample, in the main CommandHook() function: if (!err && num_keyframesL) { /* err = suites.StreamSuite2()->AEGP_GetNewLayerStream( S_my_id, current_layerH, AEGP_LayerStream_MARKER, &marker_streamH); */ suites.CompSuite7()->AEGP_GetNewCompMarkerStream(S_my_id, current_compH, &marker_streamH); // Added for (A_long indexL = 0; (!err && indexL < num_keyframesL) ; indexL++){ err = suites.KeyframeSuite3()->AEGP_GetKeyframeTime(position_streamH, indexL, AEGP_LTimeMode_LayerTime, &key_timeT); ERR(GetCheesyWithIt(&position_streamH, &indexL, &value_dimsS)); if (!err && marker_streamH) { err = MessWithMarkers(&current_layerH, &marker_streamH, &key_timeT); } } ERR2(suites.StreamSuite2()->AEGP_DisposeStream(marker_streamH)); } The code I’ve removed is just commented out, and I just added the one line after it. Notice that I’m using CompSuite7, since CompSuite8 doesn’t seem to be hooked up into the AEGP_SuiteHandler in CS5. I get the marker stream for the composition using AEGP_GetNewCompMarkerStream. The key_timeT in this case comes from the keyframes I’m looking at in the position stream, so I just put markers at the same time as the position keyframes. In MessWithMarkers(), the markers are added using AEGP_InsertKeyframe(). Zac

Zac Lam · ‎Apr 29, 2011

Let's use your other post here: http://forums.adobe.com/thread/844486?tstart=0. I just posted an answer there. Cheers, Zac

Zac Lam · ‎Apr 29, 2011

Sure, you can use AEGP_CreateCameraInComp(), which is in AEGP_CompSuite. Regards, Zac

Zac Lam · ‎Apr 26, 2011

Just wanted to provide an update this thread - the exporter has been brought forward to CS5, thanks to some coordination between interested users that were willing to pool their donations together and pay for a developer. Very nice to see this project taken care of! Zac

Zac Lam · ‎Apr 26, 2011

Hi Christian, Try using command ID 2038 for New Solid. Cheers, Zac

Zac Lam · ‎Apr 19, 2011

Hi there, Starting with CS4 and later, the way to check if the user has cancelled the export is to call exportProgressSuite->UpdateProgressPercent(), and check the return value. If the return value is exportReturn_Abort, then the export has been cancelled. Note that the exporter can still continue to ask for video frames and audio samples after a cancel has been received, which is useful in certain circumstances, such as if an exporter needs a few more frames to complete an MPEG GOP, or if it wants to include the audio for the video exported up to the point of cancel. This allows the exporter to generate well-formed output files, even in the case of a cancel. The SDK exporter sample currently only demonstrates the pause case by checking for suiteError_ExporterSuspended, so I am adding support for exportReturn_Abort to the exporter sample for the next SDK release. Regards, Zac

Zac Lam · ‎Apr 15, 2011

Hi Chris, Using a custom pixel format with only an importer and exporter could be problematic because you wouldn't be able to view the video in the Monitor, since the player wouldn't understand the pixel format. You'd have to provide a player to display the custom pixel format in the Monitor. That is a huge undertaking and probably more trouble than it's worth in this case. I would suggest filing a feature request to add API support for this. http://www.adobe.com/go/wish Zac

Zac Lam · ‎Mar 24, 2011

I just tried this using the SDK exporter sample from the CS5 SDK with AME CS4. v2 works for me. Here's the code: PrSDKMemoryManagerSuiteV2 *memorySuite; SPBasicSuite *spBasic = stdParmsP->getSPBasicSuite(); if (spBasic != NULL) { spError = spBasic->AcquireSuite( kPrSDKMemoryManagerSuite, kPrSDKMemoryManagerSuiteVersion2, const_cast<const void**>(reinterpret_cast<void**>(&memorySuite))); } As mentioned before, v3 isn't going to work because it didn't exist yet in CS4. I'm curious why v2 isn't working for you though. But it doesn't seem to be a problem with the CS5 SDK itself. What exact version of AME CS4 do you happen to be testing with?

Zac Lam · ‎Mar 23, 2011

Hi Rallymax, exSDKPostProcessing is more for providing localized strings for the parameter UI. It sounds safe enough to skip respecifying the range if you are not experiencing problems. A drop-down list could default to the first entry if it doesn't understand the default value. But if I recall, the defaults set in exSelGenerateDefaultParams for drop-down parameters such as frame rate are correctly initialized in the SDK Exporter sample. For parameter caching in AME, there's the Placeholder Preset.epr, there's the queued up items in AME, and after deleting all this and relaunching AME, the SDK Guide recommends going into the Export Settings dialog and switching to a different Format and then back to yours. Regards, Zac

Zac Lam · ‎Mar 18, 2011

Hi Benoit, There is no sample code that demonstrates how to display the preview in the Capture panel, but you are on the right track. If you save off the window information during recmod_SetDisp, you can draw your preview there during recmod_Idle. Regards, Zac

Zac Lam · ‎Mar 07, 2011

If you're interested in 32 bpc processing in Premiere Pro too, then try the SDK Noise sample. Cheers, Zac

Zac Lam · ‎Mar 07, 2011

Basically, Premiere Elements has a recorder plug-in that acts as a host for WDM capture drivers. This looks to be the correct MSDN reference for developing a WDM video capture filter: http://msdn.microsoft.com/en-us/library/dd373406%28v=VS.85%29.aspx Looking at our WDM support code, it appears that for the video display in the capture window, the WDM host code creates a capture preview graph. Here's a reference: http://msdn.microsoft.com/en-us/library/dd377468%28v=vs.85%29.aspx Premiere doesn't provide generic libraries for decoding compressed frames - that's exactly what the plug-in architecture is for. The plug-in needs to provide the support for the hardware and video formats. Whether you support H.264 decompression directly, or through other 3rd party libraries, is your choice. As Rallymax pointed out, Windows 7 32-bit seems to already have that support built-in. Regards, Zac

Zac Lam · ‎Mar 07, 2011

Hi there, In that case, it sounds like you would want to write a standard importer plug-in. You could start with the SDK File Importer plug-in sample as your guide. Since your plug-in will be working with another process to perform file handling, you'll want to set canOpen. This will tell Premiere Pro that you want your plug-in to receive the imOpenFile8 and imQuietFile calls, which is where you should open / close any file handles. Regards, Zac

Zac Lam · ‎Mar 03, 2011

Hi hanniblek, For Premiere Elements to support capture using your hardware, you'll need to either provide a recorder plug-in built using the Premiere Pro SDK, or a WDM capture driver. If you provide a recorder plug-in, you will need to provide your own code to decode the video for display in the Capture panel. Ideally, you would capture directly to files already supported by Premiere Elements. That way there would be no need to provide a separate importer plug-in. Regards, Zac

Zac Lam · ‎Mar 02, 2011

Hi E, I'll add some notes to the documentation to explain more about suite versioning. The checkbox issue is fixed in CS5. My suggestion was to try creating the presets in CS5, and use them in CS4, to see if that by any chance helps in CS4. But looking at the code, I don't think that will work for CS4. Sorry. Regards, Zac

Zac Lam · ‎Feb 28, 2011

Hi there, In this case, the Memory Manager Suite was revised for CS5, and the version number was bumped to 3. kPrSDKMemoryManagerSuiteVersion is defined as 3, so when you try to acquire the suite using that version, it will succeed in CS5, but fail in CS4 because it didn't exist yet. Version 2 should still be supported, so and exporter running in either CS4 or CS5 can acquire version 2, and use the PrSDKMemoryManagerSuiteV2 struct definitions instead. Regards, Zac

Zac Lam · ‎Feb 23, 2011

Hi Rallymax, The slider + checkbox behavior was a problem with the first version of the exporter API in CS4, but in CS5 it has been fixed. The problem was in how the exporter host layer interpreted the parameters specified via the Export Param Suite. So when making presets for your exporter, it would make sense to use CS5, since CS4 has the problematic behavior. I haven't tried this, but bringing those presets from CS5 back to CS4 may solve the problem in CS4. So far we haven't had any need or request for two editable fields side-by-side. Sure, I can add that detail to the docs. Regards, Zac

Zac Lam · ‎Feb 08, 2011

I'm late in coming back to this thread, but for anyone who is wondering where 32 bpc effect rendering stands in Premiere Pro, I wanted to clarify what's going on. As mentioned further up, Premiere Pro does contain a considerable number of effects that are 32-bit capable. This 32-bit rendering has been available since Premiere Pro 2.0. CS5 now provides badges in the Effects panel so that an editor can distinguish between which effects are 32-bit capable, which ones can process YUV natively, and which ones are limited to 8-bit or RGB. The limitation RE:VisionFX is referring to here is in a specific function (PF_CHECKOUT_PARAM) in Premiere Pro's support for the After Effects API. That function provides a way for an effect plug-in to get frames at times other than the input frame. Most effects like color correction, displacement effects, and light effects, and dissolves don't need to get frames at other times. But plug-ins that provide time remapping or motion blur do need this function. This limitation is bug 1516663, and we planning on addressing it in a future version. Regards, Zac

Zac Lam · ‎Feb 08, 2011

Hi Roy, There’s no command line / scripting interface for Premiere Pro. You could generate a sequence programmatically and save it as a FCP XML file, which can then be imported into Premiere Pro. After Effects supports scripting, if you’re interested - http://www.adobe.com/devnet/aftereffects.html Regards, Zac

Zac Lam · ‎Jan 24, 2011

Hi there, Premiere Pro does support 32-bit per channel floating point video throughout the pipeline. I'm sure Todd was making reference to some certain capability AE has that isn't in PPro, but without seeing the original post, I'm not sure what he was referring to. However, Premiere Pro has supported 32-bit floating point rendering since version 2.0. Premiere Pro renders in various pixel formats and depths depending on the input formats, but as a user you can always force 32-bit floating point rendering by checking the Maximum Bit Depth checkbox in the render / export settings. New in CS5, the Effects panel has various badges to show the capabilities of each effect, so if 32-bit rendering is important to you, you should stick with the effects that have the 32-bit badges. Regards, Zac

Zac Lam · ‎Jan 18, 2011

Hi there, Almost every sequence involves more than one clip, and effects, frame rate conversions, compositing, etc require extra rendering so that the source clips are not something that can just be fed directly to the exporter plug-in. Since the case of sending a single clip to the output is relatively rare in a user workflow, there's no simple callback to get that information. Rather, a basic exporter should use the Sequence Render Suite to call into Premiere Pro to get rendered frames, and then encode those frames into the final file. Regards, Zac

Zac Lam · ‎Jan 04, 2011

Hi, These custom controls are implemented using custom ECW UI, using the After Effects API. You can download the AE SDK here: http://www.adobe.com/devnet/aftereffects.html Check out the Custom ECW UI sample plug-in in that SDK. It has basic compatibility in Premiere Pro. For questions about the AE SDK, please use the After Effects SDK forum: http://forums.adobe.com/community/aftereffects_general_discussion/aftereffects_sdk Regards, Zac

Zac Lam · ‎Jan 04, 2011

Hi Annabella, There currently is no way to create custom audio transitions for Premiere Pro. Feel free to submit a feature request, either for a cosine audio transition, or for an audio transition API in general, or both: http://www.adobe.com/go/wish Regards, Zac

Zac Lam · ‎Dec 24, 2010

Thanks for posting back the steps that worked for you. That is very much appreciated. And I'll add a link in the SDK Guide that connects the "Guidelines for Exporters in Premiere Elements" section to the "Creating Presets" section. Cheers, Zac

Zac Lam · ‎Dec 23, 2010

Hi there, The es_ES subfolder is the right subfolder for a Spanish language installation. But on Windows, it is best to refer to this registry key: HKEY_LOCAL_MACHINE/Software/Adobe/Premiere Elements/CurrentVersion/Plug-InsDir In reading the SDK Guide, did you see the "Guidelines for Exporters in Premiere Elements" section, towards the end of the Exporters chapter? There is describes that the new export option should appear here: b. Goto the “Share” tab c. Under that choose “Personal Computer” d. You should see the “Others – 3rd Party Plug-ins” in the list of formats. Select this. e. Your preset should be seen in the drop-down. Also, using the Premiere Pro CS5 SDK, you'll want to make sure to build a 32-bit binary for Premiere Elements, since it is a 32-bit application. That setting is the Solution Platforms drop-down in Microsoft Visual Studio. Since the SDK is primarily for Premiere Pro, it defaults to building 64-bit binaries, so make sure to change this setting. Regards, Zac

Zac Lam · ‎Dec 15, 2010

Would you be able to just use the version that ships with Premiere Pro? Or is there new functionality that you depend on in the newer version?

Adobe Community

Zac Lam

Zac Lam

Activity

Re: how to made plugin using flex3 application

Re: what is meaning of following code

Re: Save as "Copy"

Re: what is meaning of following code

Re: problem when creating a marker

Re: Plugin - insert camera

Re: Plugin - how to insert camera in code

Re: Any exporter developers interested in an open ...

Re: Using app.executeCommand() for New Solid Dialo...

Re: RenderVideoFrame doesnot return abort

Re: Importer => Exporter limit

Re: CS5 SDK + AME CS4 = Crash from bad memorySuite

Re: Exporter API - neccesary re-init?

Re: Preview in recorder

Re: Is there a 32bpc example?

Re: Capture card plug-in

Re: Importer - basic question

Re: Capture card plug-in

Re: CS5 SDK + AME CS4 = Crash from bad memorySuite

Re: CS5 SDK + AME CS4 = Crash from bad memorySuite

Re: CS4|5 Exporter - how to make slider with no ch...

Re: Does PPRO deserve a complete 32bpc color pipli...

Re: Editing movie from script (API)

Re: Does PPRO deserve a complete 32bpc color pipli...

Re: How to get source clip file Path within SDK ex...

Re: Implementing Bezier-type controls in a Premier...

Re: Audio Transitions

Re: Starting up with SDK for CS5 (premiere)

Re: Starting up with SDK for CS5 (premiere)

Re: QtCore4.dll and QtGui4.dll