AWS Thinkbox Discussion Forums

Adobe Premiere Submission Script

Does anybody has an Adobe Premiere script for the submission scripts? I basically copy the scripts for MediaEncoder submission and added to the submit processing submission.

Mmm… Do you mean something that runs in the Monitor or something that runs within Media Encoder?

I think if it’s for the Monitor, that’s not a bad idea. Technically Premier support through Adobe Media Encoder isn’t great so we don’t advertise it well.

Well, I’m trying to add Adobe Premiere for the submit plugins menu. I see AfterEffects and MediaEncoder but I’d like to add Adobe Premiere for encoding for proxies frames.

There are backing plugins for both of those options and because Premier Pro is difficult to control we don’t support it out of the box. Or, it was when we checked it out last time.

You can try sending your Premier Pro project through the Media Encoder submitter. The downside is that it will only render the first output. You’ll also need to make sure Media Encoder is installed on the machines you are running Deadline Slave.

The Media Encoder plugin is using an unsupported API so we’re at the mercy of Adobe there and we can’t make it much better than it is now.

Ok, I’ll try that and let you know. Thanks.

By the way, when you say “it will only render the first output”, does that mean it cannot render all the files inside the folder?

It will only be able to run one prproj file at a time, but I believe also only the first element from the render queue.

I’m getting an error when I submit a MediaEncoder job.

Logs:
Ticks = 703 <3568> <5> Time = 0.0474581second
Ticks = 1282 <3568> <5> GPUSniffer launching with test mask 254
Ticks = 8532 <3568> <0> Time taken to load MediaCore plugins: 3547.13 milliseconds.
Ticks = 9407 <3568> <1> Entering RunEventLoop
Ticks = 12782 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 12782 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 12782 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 12782 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 12782 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 12782 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 12782 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 13125 <15984> <5> Page ID
Ticks = 13141 <15984> <5> Page ID
Ticks = 13141 <15580> <5> QuickTime smart rendering disabled.
Ticks = 13141 <15580> <5> The video codec fourcc of 1634755439 is not installed.
Ticks = 13141 <15580> ExporterHost::BeginThreadExport <5> Exporter finished in : 0.00405405 seconds. Result code: 27 Destination:R:\Mov_Files\Test_encode_.mov
Ticks = 13157 <3568> MF::ErrorReport <1> Summary:
Ticks = 13157 <3568> MF::ErrorReport <1> * errorTitle=Export Error
Ticks = 13157 <3568> MF::ErrorReport <1> * errorDescription=Exporter returned bad result.
Ticks = 13157 <3568> MF::ErrorReport <1> * componentName=QuickTime
Ticks = 13157 <3568> MF::ErrorReport <1> * componentSelector=9
Ticks = 13157 <3568> MF::ErrorReport <1> * componentType=$$$/ErrorReport/ComponentTypeExporter=Exporter
Ticks = 13157 <3568> MF::ErrorReport <1> * errorCode=27
Ticks = 13157 <3568> MF::ErrorReport <1> * exporter=QuickTime
Ticks = 13157 <3568> MF::ErrorReport <1> * moduleFilePath=ExporterPluginModule.cpp
Ticks = 13157 <3568> MF::ErrorReport <1> * moduleFunction=ML::ReportExportError
Ticks = 13157 <3568> MF::ErrorReport <1> * moduleLine=111
Ticks = 13157 <3568> MF::ErrorReport <1> * outputFilePath=Test_encode_.mov
Ticks = 13157 <3568> MF::ErrorReport <1> * outputFileType=1299148630
Ticks = 13157 <3568> MF::ErrorReport <1> * timecode=14:14:07:07
Ticks = 13172 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 13172 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 13172 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 13172 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 13172 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 13172 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient
Ticks = 13172 <3568> <5> ProxyProcessor::DestroyVulcanClient resetting mVulcanClient

I have installed the latest Quicktime and updates and still getting the above error.

That’s a new one for me, though I don’t have much experience with AME. Do you see a similar issue when running that project in AME on the same machine as this error? I know often times things will work fine on a workstation but fail on the farm due to hardware or software (usually plugin or version) differences.

I expect that this should hit on the station as well.

I’m also assuming “Vulcan” is referring to the OpenGL replacement. Usually GPU-related work can fail when things are running as a service. Is the Slave running as a service? You’ll be able to tell from the job report.

I’m able to run the job without any issue from Adobe Premiere to MediaEncoder.

Using the same machine.

Here’s another log from the render node for MediaEncoder:

  • Encoding Time: 00:00:00
    11/20/2018 11:37:24 AM : Encoding Failed

Export Error
Incompatible Video Codec found in the preset. Preset load failed.

Exporter returned bad result.

Writing with exporter: QuickTime
Writing to file: R:\Encode Mov\A001C012_181015_R5NR_1.mov
Around timecode: 15:41:21:03

This is challenging. Would you be willing to have a call? You can either send a private message or e-mail to support@thinkboxsoftware.com and we’ll set something up.

Ok, just confirmed with our media tech guy here and he was using a different preset for Mediaencoder for windows platform.

The tests were successful, but as you said the Premiere only takes one video item even though the Premiere proj has multiple videos selected.

It’s certainly not ideal, that’s for sure. If you have good access to the right contacts at Adobe, we’d really like to support Premier Pro properly one day. :slight_smile:

Please check this topic:

2 Likes
Privacy | Site terms | Cookie preferences