Unfortunately AME isn't scriptable at this time.  Have you checked out the documentation on watch folders in AME?  That might provide the functionality you're looking for: http://help.adobe.com/en_US/mediaencoder/cs/using/WS09F8D71D-2393-42c2-950A-764C9CD16025.html ... View more

Hi Agam, Yes, your summary is correct. The CS4 SDK sample code uses mFloat64 because it was written during the development of CS4.  At that time, I requested that we change the time value returned by GetExportSourceInfo(kExportInfo_VideoFrameRate) to be a PrTime rather than a float, since it simplifies the code in most cases.  This change to GetExportSourceInfo() wasn't made until 4.0.1, and I didn't update the SDK sample code until after releasing the CS4 SDK. So go ahead and use the mInt64 member, and make sure the plug-in is running in 4.0.1 or later, not 4.0.  You can check this by looking in exportStdParms.interfaceVer.  If that value is prExportVersion100, that means it is PPro 4.0.  On exSelStartup, you could just display a message that the user should update to 4.0.1 or later. Regards, Zac ... View more

Hi Agam, In the SDK Exporter code, you can see in the exSelBeginInstance selector handler, it calls spBasic->AcquireSuite() on every suite needed.  Then in the exSelEndInstance handler, it calls spBasic->ReleaseSuite().  Just add any new suites following the pattern of the existing suites, and you should be all set! Zac ... View more

Hi Agam, If you have any other questions, let's start a different thread to keep the issues separate and easy to digest for any others who may come to the forum with the same question. This particular ExportSettings struct is defined by the exporter  plug-in, and you can modify it to add any members you wish.  So you can  just add a pointer to the PrSDKSequenceAudioSuite, and make sure to  acquire and release it along with the other suites. Hope this helps, Zac ... View more

Hey Rallymax, CS5 provides icons in the Effects panel that let you filter the effects to see which ones support YUV, or 32-bit, or both.  For earlier versions, I don't have a comprehensive list, but here’s a list of the built-in effects (not including transitions) that I’m aware of, and there may be more: ColorFast ColorRGBCorrector ColorThreeWay Crop GarbageMatte4/8/16 GaussianBlur LumaCorrector LumaCurve LumaKey ProcAmp RGBCurves Timecode TrackMatte VideoLimiter AlphaAdjust AntiAlias BlackAndWhite HorizontalFlip BGRA_8u is no longer a required pixel format starting in CS4 and later.  If a quirky filter only supports 8-bit, then there's really not much we can do to preserve the full range of 10-bit data.  After all, the user has decided to use the 8-bit filter.  But yes, it's important for the user to make an educated decision, and the new effects badging was implemented with that in mind. If there are any effects or other plug-ins that are end-of-life but still sorely needed, that would be a great thread for this forum.  The active developer community would be really interested to hear if there's a development opportunity. Cheers, Zac ... View more

Hi John, There's no way to disable the Media Cache.  Are you calling PPixDispose() on the PPixHand returned from getPreviewFrameEx()? Zac ... View more

Hi Agam, RenderVideoFrame() may return various pixel formats, depending on what's requested, and how the video segment is composed.  You can provide your own list of requested pixel formats for  RenderVideoFrame().  After calling RenderVideoFrame(), the SDK Exporter calls GetPixelFormat() on the returned frame, to check the pixel format of the returned frame, whether it's BGRA_4444_8u or VUYA_4444_32f. In CS5, the Image Processing Suite exposes the conversion functions built-in to Premiere Pro, but in CS4 that suite is not available, which is what the ConvertFrom...() functions are for in the sample.  This allows the exporter to request several different pixel formats, and gracefully handle any format that is returned. To view the resultant video frames in a video player, you'd need to write these frames to a file and generate a proper file header, so that the video player will know how to parse it and interpret the video data. Regards, Zac ... View more

Hi Nigel, Right, the SDK wouldn't be involved for any of this type of development.  Unless you could find a cross-platform way to handle some things like the drag-and-drop, then you'd need to provide two different helper apps, one for each platform. Currently there's no scripting call or public API to send files such as FCP XMLs to be opened by Premiere Pro.  I'm not sure if Flex offers a way to do this.  A good question for the Flex Forums! We'll be interested to hear what method you decide on! ... View more

Below is the definition of the return values in Premiere Elements 8. The red values are unique to Premiere Elements 8, and shifted the subsequent return values 2 values higher than their definition in the Premiere Pro SDK. enum {       exportReturn_ErrNone = 0,                 // no error       exportReturn_Abort,                             // User aborted the compile       exportReturn_Done,                              // Export finished normally       exportReturn_InternalError,       exportReturn_OutputFormatAccept,                // The output format is valid       exportReturn_OutputFormatDecline,               // The compile module cannot compile to the output format       exportReturn_OutOfDiskSpace,        // Out of disk space error       exportReturn_BufferFull,                  // The offset into the audio buffer would overflow it       exportReturn_ErrOther,                    //       exportReturn_ErrMemory,                   // ran out of memory       exportReturn_ErrFileNotFound,       // File not found       exportReturn_ErrTooManyOpenFiles,   // Too many open files       exportReturn_ErrPermErr,                  // Permission violation       exportReturn_ErrOpenErr,                  // Unable to open the file       exportReturn_ErrInvalidDrive,       // Drive isn't valid.       exportReturn_ErrDupFile,                  // Duplicate Filename       exportReturn_ErrIo,                             // File io error       exportReturn_ErrInUse,                    // File is in use       exportReturn_IterateExporter,       // Return value from exSelStartup to request Exporter iteration       exportReturn_IterateExporterDone,   // Return value from exSelStartup to indicate there are no more Exporters       exportReturn_InternalErrorSilent,   /*    Silent error code; host application will not display an error message on screen.                                                                   Exporters can return this error code from compDoCompile if they wish to                                                                   put their own customized error message on screen just before returning                                                                   control.  */       exportReturn_ErrCodecBadInput,            // a video codec refused the input format       exportReturn_ErrLastErrorSet,       // the Exporter had an error and set a display string for it using the PrSDKErrorSuite.       exportReturn_ErrLastWarningSet,           // the Exporter had an warning and set a display string for it using the PrSDKErrorSuite.       exportReturn_ErrLastInfoSet,        // the Exporter has an info string to display and set it using the PrSDKErrorSuite.       exportReturn_ErrExceedsMaxFormatDuration, // the Exporter (or the host) has deemed the duration of the compile to be too large       exportReturn_VideoCodecNeedsActivation,         // the current video codec is not activated and cannot be used.       exportReturn_AudioCodecNeedsActivation,         // the current audio codec is not activated and cannot be used.       exportReturn_IncompatibleAudioChannelType,      // the requested audio channels are not compatible with the source audio       exportReturn_Unsupported = -100           // Unsupported selector }; Obviously, this wasn't the right way to add these new return values. ... View more

Our CUDA support in our accelerated renderer has been built to play well with others.  We have considered providing a suite to allow exporters, when running in the same process as our accelerated render (i.e. when doing a direct export rather than queue up an encode to Adobe Media Encoder), to be able to access the rendered CUDA frames directly on the card, to avoid readback to memory.  If you're interested in something like this, contact me offline using my email in the PPro SDK for the latest status. ... View more

Hi Kazuhiro-san, We currently do not plan to  publicize the Premiere Export Private Standard Param Suite.  Hopefully  the public suite should be sufficient for your needs. Also,  I can confirm that bug 1925419 has been fixed in CS5.  So slider parameters defined by your exporter should behave as expected in the upcoming CS5 release. ... View more