Adobe Media Encoder Batch Processing

Greetings-
Did a preliminary search...could not find anything directly on target...here's the issue:
WIN Vista 64
PrP CS4 4.2
AME 4.2
Matrox RT.X2 LE 4.2
1. Using AME, I've got multiple files(about 50) in a Source FOLDER "A" that I want batch process out to Output FOLDER "B"
2. When I drag all the files into the queue, AME assumes that the Output Folder is the same as the Source...
3. While the "formats" and "presets" are correct, each file in the queue needs to have the "Output" destination manually changed to FOLDER "B"...
4. I've searched the AME help etc, and I'm unable to find a way to mass change the "Output" folder without individually changing each "Output" destination.
5. I've Alt>A selected then tried to mass correct, but that only changes on file "Output"
Anybody know how do a batch process in AME (as in Photoshop CS3) without having to change each "Output" location?
Btw, the AME Help, and online support is a little thin...
Many TIA
Mick

OK,,,Here's a cludggy work around:
AME>File>Create Watch Folder
1. Create and name a new folder (i.e AME Watch Folder) somewhere on the source HD by right-clicking>Rename...closer to the root the easier to monitor
2. Temporarily Copy desired BP files to the newly named Watch Folder
3. Open AME
4. AME should see the all files present with Input Folder being the Watched Folder you created.
5. The Output Folder will automatically be created by AME and should show up as ...Watched Folder>Output
6. Verify that all formats/presets are properly inherited. If not Alt>A select and click Settings etc.
7. Hit Start Que. You'll see the progress bar showing encoding etc...
8. Go to Watch Folder/Output...the BP files should be there...at this point you can Move them to wherever, then delete the Watched Folder and Output Folder contents and reuse for another BP...
Yea... I know...cludggggggy...but it beats renaming the Output destination manually for 50 or more files....
Anybody else got a workaround...I'd love to hear it...
Mick

Similar Messages

Adobe Media Encoder CC constantly crashing during batch encodes

Hello!
We just made the big switch to Premiere Pro CC for our TV shows and now that it's time to finalize our first few episodes we are having some major problems batch exporting segments of the show. Sometimes it works, sometimes it works half way through the batch list then crashes, sometimes it crashes right away. There is no consistency, other than crashes are happening all the time. Here's what is happening:
• AME 7.2.0.43 (64-bit)
• Mac OS X 10.9.1 on 2x2.66 GHx 6-Core Intel Xeon, 40 GB 1333MHz DDR3 RAM
• Startup disk is SSD w/ 4GB free space (all footage is on external storage)
• Using Premiere Pro CC to export via AME.
• All recent updates insatlled as of 3/10/14.
The source footage is ProRes 422 720p 59.94 footage from AJA KiPros. Each project has 16 segments - these are individual sequences. There are 7 tracks of audio and 4-5 tracks of video in each. In addition to the video there are targa files that include the score bug, full screen graphics, etc (this is sports). There are also some Adoby Dynamic Link After Effects elements throughout.
Editing has been fairly crashless - however when I File > Export > Media and queue it up in AME, that's when the fun starts.
I can rarely get through an entire batch list - generally within a few files the preview window at the bottom shows that it has halted and nothing further will encode. There is no way to stop or close the program without force quitting. When I have tried to encode from Premiere Pro CC directly, it works, although it is much slower and will only do the one sequence at a time.
I have been trying to encode to two different formats from within AME:
1.) ProRes 422 720 59.94 (just like the source footage) with 4 channels of audio.
2.) ProRes 422 1080i29.97 with 4 channels of audio.
We have different broadcast partners so we need to deliver in these two difference specs. I get crashes regularly on both outputs.
Possibly unrelated but also weird - I've noticed that when AME starts this crashing cycle sometimes Premiere CC won't let me save anyome. The status bar comes up like it's going to save the project but it goes nowhere. I have to quit without saving. Weird.
Can anyone help me further troubleshoot? This is bordering near deal breaker to continue using this software if I have this much trouble when trying to get my project outputted. Thank you!

Agreed, I now have a project to GET OUT, and AME crashes consistently 1/3 into the render. It appears to halt all processing after (real time) 00:02:30
Am seriously considering uninstalling CC as I am beginning to find other issues in some apps, and going back to CS6/MC just so I can get work out. Durn it Adobe this is AWFUL!!
Alright, let's try to be constructive instead of throwing rocks... but the frustration level is high, and I have material on deadline. Let's get with this, guys...
What OS Win7, 64-bit
What version of AME/PPro (Please be specific by getting the full version number in the About Adobe Media Encoder screen) 8.2.0.54 Ppro: 8.2.0 (65)
When is it crashing (Again, the more detail here about where it was in the encoding process the better) roughly 1/3 into the sequence, always on exactly the same frame - tried replacing the clip with something different to see if it was a timeline error, and NO EFFECT.
What is your source (PPro project or media file (what kind?)) PPro
If the source if a PPro project, does it work when exporting directly from PPro? NO
What format are you exporting to? H.264, QT, WM, tried everything my client can play.
Do other formats work? MPEG2, QuickTime, etc? NO
Have you tried with GPU rendering on? How about turning it off by switching to Software-only mode? Mine doesn't have any choice, it's software-only.
Have you tried disabling Native Sequence Loading? (AME Preferences: General > Enable Native Sequence Loading) No effect
Other things I tried: uninstalling/reinstalling AME, setting cache to a fast local disk.

Adobe Media Encoder CS6: Freezes after starting encoding process

Adobe Media Encoder CS6: When trying to export media I Click on the Queue tab. I then click the Start button. The program shows the first few frames in the review window and then freezes with no error codes or any other notifications. Clicking on the S
I am running Adobe Media Encoder CS66.0.3.1 on Win7 64 with Intel i7-4770K CPU 16 GB Ram.
The source file is 1920 X 1080 29.97 fps. Output file is H.264 Android Tablet 1080 P 29.97 fps
I do not see any indication what so ever of what is going wrong. I have uninstalled the program completely and re installed it with no effect.
Need some help!

Can you export directly from Premiere Pro?
Have you tried disabling GPU acceleration?

Adobe Media Encoder won't start

Not OP, but I have the same problem. AME just won't run. Double click, it's loading, I can see the process in Windows Task Manager but it just goes away again. Tried deleting that watch folder .xml but not working. Here's my spec from the FAQ:
What version of Adobe Media Encoder? Include the minor version number (e.g., Adobe Media Encoder CS6 with the 6.0.1 update).AME CC from premiere cc 7.0.1
What other Adobe applications do you have installed, and what application are you using Adobe Media Encoder with?Premiere Pro. Premiere Pro
Have you installed the recent updates? (If not, you should. They fix a lot of problems.)Used creative cloud to update to latest version
What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac".Windows 7. All update patch installed.
Are you using Adobe Media Encoder through a Creative Cloud Membership subscription?Yeah
What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. For example, "H.264 in a .mov container", not just "QuickTime".N/A. App won't launch
If you are getting error message(s), what is the full text of the error message(s)?No error message
Is the problem only occurring with a specific output format or encoding preset? If so, which one? If this is a custom preset not included with AME, then upload the preset file to a file-sharing site and provide a link.No.
What were you doing when the problem occurred?Booted up the computer. Launch AME.
Has this ever worked before?Yes.
What other software are you running?Google Chrome
Do you have any third-party codecs installed?Avid DNxHD, Cineform Studio
Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU).Regular desktop
Are you using Mercury Playback Engine GPU Acceleration in Premiere Pro?Yes.

I have a problem like this:
Anybody HELP?
Process:         Adobe Media Encoder CC [16188]
Path:            /Applications/Adobe CC/*/Adobe Media Encoder CC.app/Contents/MacOS/Adobe Media Encoder CC
Identifier:      com.adobe.ame.application
Version:         7.2.0.43 (7.2.0)
Code Type:       X86-64 (Native)
Parent Process: launchd [253]
Responsible:     Adobe Media Encoder CC [16188]
User ID:         501
Date/Time:       2014-02-05 01:15:39.418 +0100
OS Version:      Mac OS X 10.9.1 (13B3116)
Report Version: 11
Anonymous UUID: 7E5DC048-8DD8-5DA9-CFD0-539F29161D59
Sleep/Wake UUID: D2BBCDCA-68C3-4C86-B34D-57E4C884FDD8
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminating with uncaught exception of type dvacore::filesupport::dir_create_exception: $$$/dvacore/filesupport/DirCreate=The directory '@0' could not be created. Please check the parent directory protection or permission rights.
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                  0x00007fff8a1c2866 __pthread_kill + 10
1   libsystem_pthread.dylib                 0x00007fff8998835c pthread_kill + 92
2   libsystem_c.dylib                       0x00007fff8f10dbba abort + 125
3   libc++abi.dylib                         0x00007fff95124141 abort_message + 257
4   libc++abi.dylib                         0x00007fff95149aa4 default_terminate_handler() + 240
5   libobjc.A.dylib                         0x00007fff9413c322 _objc_terminate() + 124
6   libc++abi.dylib                         0x00007fff951473e1 std::__terminate(void (*)()) + 8
7   libc++abi.dylib                         0x00007fff95146e6b __cxa_throw + 124
8   com.adobe.dvacore.framework             0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
9   com.adobe.AMEAppFoundation.framework          0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
10 com.adobe.Batch.framework               0x0000000105c0a842 AMEBatch::Initialize() + 2194
11 com.adobe.ame.application               0x00000001000273cb AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 811
12 com.adobe.ame.application               0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
13 com.adobe.exo.framework                 0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
14 com.adobe.ame.application               0x00000001000141a8 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1576
15 com.adobe.ame.application               0x0000000100056a38 main + 424
16 com.adobe.ame.application               0x0000000100003f74 start + 52
Model: MacBookPro11,3, BootROM MBP112.0138.B02, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.19f3
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In, 1024 MB
Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2048 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (6.30.223.154.49)
Bluetooth: Version 4.2.1f2 12982, 3 services, 23 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM1024F, 1 TB
USB Device: Internal Memory Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1

Turning off frame blending in Adobe Media Encoder

Is there a way to turn off frame blending in Adobe Media Encoder? I have a bunch of
Flip Mino HD footage (1280x720p) which I wish to convert to P2 720p format so that
I can more easily mix and match it in the Premiere timeline with actual P2 footage
shot on an HVX200.
I successfully used Media Encoder to perform this task but there is one problem. The
Flip footage is 30fps and P2 720p is 29.97fps. So Media Encoder uses frame blending.
The frame blending sometimes creates obnoxious artifacts so I would like to turn it
off but there seems to be no way to do this (or alternatively "conform" the 30fps input
to 29.97fps so that no blending is nescessary).
After Effects CS4 would seem like an alternative since it has nice batch composition
creation and rendering features but it cannot render to the P2 format - it appears to
have a older version of Media Encoder embedded within it - predating P2 support.
I would like a solution that is easily "batchable" as I have several hunderd Flip Mino HD
clips that need to be processed.
You might also ask, why not just import the Flip clips unchanged into Premiere CS4
and mix them with the P2 clips?....I have tried this and it seems to drive Premiere crazy
introducing various crashes and other strange behaviors. The pre conversion to P2
route seems to work fine. I just want to get rid of the frame blending.

I happened upon this video just before I made my posting and it doesn't help with the
crashes/hangs. When I import more than about 20 Flip Mino HD clips it seems to trigger
some sort of memory corruption bug in Premiere. Some of the clips start to just
show as solid green in their thumbnail views in the timeline and scrubbing the timeline
eventually hangs Premiere altogether. This is reproducible on two different computers
although the exact symptoms change slightly each time it is tried. Importing only 3 or 4
clips actually seems to work, at least for a short while.
The problems happen even if the only thing imported into the project are Mino footage and
the Sequence is set to Desktop or XDCAM mode. So the crashes have nothing to do
with P2 editing mode.
The same installation of Premiere CS4 on one of these computers has been just used to
successfully edit and render out a P2 project with hundreds of clips, stills and titles so the
basic CS4 installation seems to be solid.
I'll eventually file a bug report but for now I'm more interested in getting the job done.

Can I use Flex with Adobe Media Encoder to automate encoding?

I am thinking about learning Flex assuming I can do the following.
Can I use Flex to automate the process of converting/encoding videos from many formats to FLV format?
If so, what encoder do I use for this process? Flash media encoder?
Can Flash Media Encoder interface with Flex (PHP/XML/ActionScript) to automatically with presets configuered convert/encode videos that have been uploaded and placed into a folder into FLV format?
Thanks.

Guys,
I have developed a simple script ( batch file *.bat)) that will check if encoding is still being done ( every 60+ secs ) and if the process is over, it will shutdown the PC. I tried to keep the code very very simple so that others can improve it.
For now , i have tested this on Windows 7 SP1 - 64 bits and it wokrs well.
Here is the code, copy and paste it into notepad - i named it AutoPowerOff-AdobeMediaEnCoder.bat
..........copy code below ..........
@echo off
echo.
date /t
time /t
echo.
:StartMonitoring
echo.
echo.
echo.
color 0f
echo Start monitoring Adobe Media Encoding Process
echo Check every 60 secs via KeepMonitoring
ping 127.0.0.1 -n 60 > nul
Goto Check
:KeepMonitoring
echo.
echo.
echo.
color 0f
echo Continue Monitoring Adobe Media Encoding Process - every 60s
ping 127.0.0.1 -n 60 > nul
Goto Check
:Check
echo.
echo.
echo.
color 0e
echo Checking If Encoding Process Over ?
echo.
echo.
color 0a
tasklist | find /i "PProHeadless.exe"
IF ERRORLEVEL 1 GOTO AutoPowerOFF
IF ERRORLEVEL 0 echo. && echo Encoding Still In Progress && GOTO KeepMonitoring
:AutoPowerOFF
echo.
echo.
echo.
color 0c
echo Process PProHeadless.exe does not exist anymore
echo Assume Encoding DONE
echo PC Poweroff Initiated
echo.
echo.
echo ShutDown PC After 60 sec
shutdown /s /t 60
:END
....... end of code ..............
If some of you can check it out on other platforms and report back, i can maintain this thread.
Regards,
Marco.

Adobe Media Encoder (CS5) has encountered an error (WinFile.cpp-759)

I have a 714 MB Xvid file that I want to split into smaller pieces. I have gone successfully through a similar process earlier with a larger Xvid file using the same version of Adobe Media Encoder (CS5). It appears that no matter which output video format I choose, the process crashes with the following error message shown in a new pop-up dialog:
"Adobe Media Encoder has encountered an error. [..\..\Src\Win\WinFile.cpp-759].
(Even the source program file line number 759 in the above error message is always the same, regardless of my chosen output file format.)
The only option available from this point onwards is the "Continue" button. When I click Continue the program terminates with the Windows program crash message "Adobe Media Encoder CS5 has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you if a solution is available. <Debug> / <Close program>"
My search for other similar problem reports revealed that some user(s) has/have experienced a very similar problem in CS4, but the source line number was slightly different in CS4. Both problems are probably caused by the same error in Adobe's software. The small difference in source line numbers is probably due to some (minor) and probably unrelated changes to this C++ source module (WinFile.cpp).
It might of course be the case that this particular input video file has some rare encoding or other embedded problem. However, the fact that I can view the video without problems using Windows Media Player does not support this theory.
Apart from this message board I could not find any other avenue to report this bug to Adobe (without paying for support - which I am obviously not going to do as this is clearly a programming bug in the software). Hopefully some Adobe developer responsible for Media Encoder maintenance will read this forum from time to time and would subsequently inspect the source module for any obvious defects. I could supply the source video file with which this problem can be reproduced at will.
Regards
Jouni Juntunen

CS4 Adobe Media Encoder & FMLE are two different softwares - you can post your query here:http://forums.adobe.com/community/ame

Adobe Media Encoder CS4 Encoding Error

I got an error when Adobe Media Encoder CS4 encoding which is the crash of ImporterProcessServer. It crashes the halfway of the encoding process. I restarted my comp and tried several times before but the results still the same. Sometimes ImporterProcessServer did not crash but the encoder failed compiling without any error.
Processor : Intel Core 2 Duo E4600 2.4GHZ
RAM: 2GB
OS: Win7 32bit
Graphic: Nvidia 8600 GeForce 512 mb

First thing to check is what is on the Timeline at about the 50% point. Do you have an odd Asset there?
Do you have a gap in the Video at about that point?
Then, do you have adequate defragmented free space on the destination HDD?
Good luck,
Hunt

Adobe Media Encoder CS4 Error: WinFile.cpp-754

When encoding video from one format to another (no matter what is source and what is result file format) I have an error after some time or in the begining of the process. "Adobe Media Encoder has encountered an error ..\..\Src\Win\WinFile.cpp-754"
Version of Encoder is 4.2.0.006 (updated).
I can't encode any files. What is the problem?

Any update on this?
I get WinFile.cpp-754 on CS4 and WinFile.cpp-785 on CS5 trying to encode the same AVI file.
I'm trying to load a 59.94 fps AVI file into PremierPro CS4 and need to convert it to something else (correct?)

Adobe media encoder error message - please help

I purchased adobe creative suite 4 web standard in january of 2010. I'm in the process of learning how to use all the features. I am building a website in dreamweaver and wanted to create and import a flash movie. I opened adobe media encoder from my program files. I added an avi file to the encoder, chose a medium quality for web, and clicked Start Queue. I then got the following pop up error message:
Error Message:
Adobe Media Encoder Debug Event
Adobe Media Encoder has encountered an error.
[..\..\Src\Win\WinFile.cpp-754]
Please help.
Thank You.

This forum is for "flash media live encoder". For Adobe Media Encoder related queries go to Creative Suite forums.

Adobe Media Encoder (Error compiling movie) Unknown error when writing to Isilon OneFS 6.5.5.18

Adobe Media Encoder (Error compiling movie) Unknown error when writing to Isilon OneFS 6.5.5.18 while using Adobe Premiere Pro.
Process:         Adobe Premiere Pro CC 2014
Path: /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Identifier: com.adobe.AdobePremierePro
Version:         8.1.0 (8.1.0)
Code Type: X86-64 (Native)
Parent Process: launchd [2538]
Responsible:     Adobe Premiere Pro CC 2014
Date/Time: 2015-01-06 14:04:23.500 -0700
OS Version:      Mac OS X 10.9.2 (13C64)
Report Version: 11
Crashed Thread: 55 Dispatch queue: com.apple.root.default-priority
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Customer created test export with 777 permissions and set mount parameters to the following:
mount_nfs -o vers=3,tcp,rdirplus,intr,nolocks,async,rsize=32768,wsize=32768
-- Original mount options:
     General mount flags: 0x40 async
     NFS parameters: vers=3,tcp,nolocks,rsize=32768,wsize=32768,rdirplus
-- Current mount parameters:
     General mount flags: 0x4000058 async,nodev,nosuid multilabel
     NFS parameters: vers=3,tcp,port=2049,nomntudp,hard,nointr,noresvport,negnamecache,callumnt,nolocks,quota, rsize=32768,wsize=32768,readahead=16,dsize=32768,rdirplus,nodumbtimr,timeo=10,maxgroups=16 ,acregmin=5,acregmax=60,acdirmin=5,acdirmax=60,nomutejukebox,nonfc,sec=sys
The pcap shows once the movie is created a lockup call is responded from Isilon with Error: NFS3ERR_NOENT
478         V3 CREATE Call (Reply In 479), DH: 0xea5f731c/QBRSN-0-0-1.mov Mode: UNCHECKED
479         V3 CREATE Reply (Call In 478)
484         V3 LOOKUP Call (Reply In 485), DH: 0xea5f731c/._QBRSN-0-0-1.mov
485        V3 LOOKUP Reply (Call In 484) Error: NFS3ERR_NOENT
V3 LOOKUP Reply (Call In ....) Error: NFS3ERR_NOENT -   This is by design of OneFS, we coalesce files and then flush them out to disk which is why the commit time is accurate but the file is not immediately available. however when an async option is used within the mount options this should be avoided if writing asynchronously to the cluster. Has anyone else seen this behavior lately? (current workaround is to store locally and transfer to the cluster via Finder)

That error can happen for many reasons...one of the reasons that I occassionaly get it is because I try exporting a movie to an external drive that has been formated in the old FAT32 instead of the NTSF standard. FAT32 only allows for file sizes up to 2 gigs. And as soon as it reaches that...I would get that error. I don't know if that is why you are getting that error...but it would be easy to check. 1) are you generating a file that is over 2 gigs? 2) is your drive that you are exporting to FAT 32 (just right click the drive in My Computer and select "properties" then just look for what it says next to "file system".

Long load times normal for Adobe Media Encoder from Premiere CS5?

When I export a sequence from Adobe Premiere CS5 using Adobe Media Encoder, the system freezes for several minutes before giving me the exporter screen. Then, when I've loaded my settings and clicked "export," the system again freezes for several minutes before beginning to encode. I'm using a system with an Intel I7 CPU 930 @ 2.80Ghz 2.80 Ghz., 24 GB of ram, Windows 7 Ultimate 64 bit operating system and an Nvidia quadro FX4800 graphics card.. Everything else is fast, but AME is slow. Is this normal? Should I reinstall AME?

Not sure what you mean about the process. From Premiere CS5, I click on "export" which brings up a menu. I select "media" from the menu which brings up the Adobe Media Encoder. I adjust my settings and click "export" from the bottom of the screen to immediately render the Premiere file. Clicking "Queue" would put the program into the AME Queue. Am I missing something? On the slowness issue, looks like I need to reinstall AME. I've been reluctant to do that, partially because I'm using some Matrox hardware and I'll have to reinstall the Matrox softare to populate the matrox settings into the media encoder. Looks like it may be worth it.
Thanks.

Adobe Premiere Pro Won't Export To Adobe Media Encoder?

I Work for a news company and we use Adobe for aeverything we need. But when we take a little break from doing videos while we where moving to a new office space, and suddenly we start again and It decided not to export to the Adobe Media Encoder. Usually it was a 5 second process and now it does not work at all. We have adobe premiere pro cs5.5 from the CC (We are currently not planning on upgrading to CS6 anytime soon.) We have no plugins for it and it works for everything else. When I use the Exporter it Exports in in too low of a quality for use. Help? If you need I work at better-community-news.com, Sooolutions (Seprate buisness same owner.) Glad Studios, (also same owner...all the places I work are the same guy), X.L.N.T Marketing and thats about it. Its a team of 3 guys and we would appricate any help! Thanks!
~ Better Community News

Jan 21, 2014 12:51 PM -to- Jan 21, 2014 2:24 PM
thanks nobody because nobody helped me solve this delima
You do know that this is a user to user forum, not an official Adobe support site?
Which means that there is NOT a full time group of people just waiting to answer questions
Don't you think that complaining about nobody answering in less than 2 hours is a little unreasonable?

Mac Pro restarts with kernel panic error during Adobe Premiere CS6 or Adobe Media Encoder CS6 render/encode.

Multiple times this week, my Mac Pro at work has been restarting during renders in Adobe Media Encoder CS6 and Adobe Premiere CS6. This seems to be specific on this computer only. Identical computers don't have this problem. Here is the system report after it reboots to OS X:
Interval Since Last Panic Report: 252068 sec
Panics Since Last Report:          2
Anonymous UUID:                    7DF9A04B-0693-5FC4-60CF-4BC6ABDB3C1E
Fri May 17 15:37:07 2013
panic(cpu 0 caller 0xffffff8009ab7e95): Kernel trap at 0xffffff8009e1b814, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x00000000000000b8, CR3: 0x000000000c3d3000, CR4: 0x00000000000206e0
RAX: 0x0000000000000001, RBX: 0xffffff8039ebfb98, RCX: 0xffffff800a08eb00, RDX: 0xffffff82413abde8
RSP: 0xffffff82413abde8, RBP: 0xffffff82413abe20, RSI: 0x00000000000000b8, RDI: 0x0000000000000001
R8: 0x0000000000000000, R9: 0x00000000000003ff, R10: 0xffffffffffffffff, R11: 0x00000000ffffffff
R12: 0x000000000000004a, R13: 0x0000000000000371, R14: 0xffffff8040611cb0, R15: 0xffffff80404ec008
RFL: 0x0000000000010206, RIP: 0xffffff8009e1b814, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00000000000000b8, Error code: 0x0000000000000002, Fault CPU: 0x0
Backtrace (CPU 0), Frame : Return Address
0xffffff82413aba80 : 0xffffff8009a1d626
0xffffff82413abaf0 : 0xffffff8009ab7e95
0xffffff82413abcc0 : 0xffffff8009acd4dd
0xffffff82413abce0 : 0xffffff8009e1b814
0xffffff82413abe20 : 0xffffff7f8bcf4d54
0xffffff82413abe60 : 0xffffff7f8bcf72f1
0xffffff82413abf20 : 0xffffff8009d86e2b
0xffffff82413abf60 : 0xffffff8009a3dcfe
0xffffff82413abfb0 : 0xffffff8009ab2977
      Kernel Extensions in backtrace:
         com.apple.nke.asp_tcp(7.0)[78FAA01C-ABC4-3AD3-8D9A-6187F7911E1A]@0xffffff7f8bce f000->0xffffff7f8bcfbfff
BSD process name corresponding to current thread: kernel_task
Mac OS version:
12D78
Kernel version:
Darwin Kernel Version 12.3.0: Sun Jan 6 22:37:10 PST 2013; root:xnu-2050.22.13~1/RELEASE_X86_64
Kernel UUID: 3EB7D8A7-C2D3-32EC-80F4-AB37D61492C6
Kernel slide:     0x0000000009800000
Kernel text base: 0xffffff8009a00000
System model name: MacPro5,1 (Mac-F221BEC8)
System uptime in nanoseconds: 76945023460235
Model: MacPro5,1, BootROM MP51.007F.B03, 8 processors, Quad-Core Intel Xeon, 2.4 GHz, 20 GB, SMC 1.39f11
Graphics: ATI Radeon HD 5770, ATI Radeon HD 5770, PCIe, 1024 MB
Memory Module: DIMM 1, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 2, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 3, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
Memory Module: DIMM 4, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
Memory Module: DIMM 5, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 6, 4 GB, DDR3 ECC, 1066 MHz, 0x857F, 0x463732353155363446393333334700000000
Memory Module: DIMM 7, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
Memory Module: DIMM 8, 1 GB, DDR3 ECC, 1066 MHz, 0x80CE, 0x4D33393142323837334648302D4348392020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x8E), Broadcom BCM43xx 1.0 (5.106.98.100.16)
Bluetooth: Version 4.1.3f3 11349, 2 service, 18 devices, 1 incoming serial ports
Network Service: Ethernet 1, Ethernet, en0
PCI Card: ATI Radeon HD 5770, sppci_displaycontroller, Slot-1
Serial ATA Device: HL-DT-ST DVD-RW GH41N
Serial ATA Device: WDC WD1001FALS-41Y6A1, 1 TB
USB Device: Keyboard Hub, apple_vendor_id, 0x1006, 0xfd300000 / 2
USB Device: Apple Keyboard, apple_vendor_id, 0x024f, 0xfd320000 / 3
USB Device: BRCM2046 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0x5a100000 / 2
USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8215, 0x5a110000 / 3
FireWire Device: built-in_hub, 800mbit_speed

That doesn't look like a complete panic report. Is there any more to it? Regardless, I suggest you run the extended form of the Apple Hardware Test. If it fails to identify a fault, remove the RAM upgrade and test with the original RAM.

Adobe Media Encoder CC 2014 has NEVER opened on my computer.

Can somebody please help with this?
Process:         Adobe Media Encoder CC 2014 [468]
Path:            /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
Identifier:      com.adobe.ame.application
Version:         ???
Code Type:       X86-64 (Native)
Parent Process: launchd [174]
Responsible:     Adobe Media Encoder CC 2014 [468]
User ID:         501
Date/Time:       2014-08-28 07:43:01.054 +0100
OS Version:      Mac OS X 10.9.4 (13E28)
Report Version: 11
Anonymous UUID: 50100364-D4BE-B73C-C1BB-D5ADEEFB650C
Crashed Thread: 0
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Application Specific Information:
dyld: launch, loading dependent libraries
Dyld Error Message:
Library not loaded: @executable_path/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE
Referenced from: /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
Reason: no suitable image found. Did find:
/Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE: truncated mach-o error: segment __LINKEDIT extends to 1416784 which is past end of file 1416782
/Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/../Frameworks/AdobeACE.framework/Versions/A/AdobeACE: truncated mach-o error: segment __LINKEDIT extends to 1416784 which is past end of file 1416782
Binary Images:
    0x7fff6f3ef000 -     0x7fff6f422817 dyld (239.4) <042C4CED-6FB2-3B1C-948B-CAF2EE3B9F7A> /usr/lib/dyld
    0x7fff8ff53000 -     0x7fff8ff53fff com.apple.Carbon (154 - 157) <45A9A40A-78FF-3EA0-8FAB-A4F81052FA55> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
    0x7fff92ed5000 -     0x7fff92ed5fff com.apple.Cocoa (6.8 - 20) <E90E99D7-A425-3301-A025-D9E0CD11918E> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
    0x7fff92faf000 -     0x7fff92faffff com.apple.CoreServices (59 - 59) <7A697B5E-F179-30DF-93F2-8B503CEEEFD5> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
    0x7fff92fc7000 -     0x7fff932c5fff com.apple.Foundation (6.9 - 1056.13) <2EE9AB07-3EA0-37D3-B407-4A520F2CB497> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation
    0x7fff96923000 -     0x7fff9698ffff com.apple.framework.IOKit (2.0.1 - 907.100.13) <057FDBA3-56D6-3903-8C0B-849214BF1985> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
    0x7fff97732000 -     0x7fff9798cff9 com.apple.security (7.0 - 55471.14.8) <EA03E140-2509-3A07-8440-2DC97C0D478B> /System/Library/Frameworks/Security.framework/Versions/A/Security
    0x7fff9951c000 -     0x7fff9951cfff com.apple.ApplicationServices (48 - 48) <3E3F01A8-314D-378F-835E-9CC4F8820031> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices
Model: MacBookPro8,3, BootROM MBP81.0047.B27, 4 processors, Intel Core i7, 2.2 GHz, 16 GB, SMC 1.70f6
Graphics: Intel HD Graphics 3000, Intel HD Graphics 3000, Built-In, 512 MB
Graphics: AMD Radeon HD 6750M, AMD Radeon HD 6750M, PCIe, 1024 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E4D3136
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E4D3136
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.100.22)
Bluetooth: Version 4.2.6f1 14216, 3 services, 23 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: M4-CT512M4SSD2, 512.11 GB
Serial ATA Device: MATSHITADVD-R   UJ-898
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
USB Device: Apple Internal Keyboard / Trackpad
USB Device: Hub
USB Device: IR Receiver
Thunderbolt Bus: MacBook Pro, Apple Inc., 22.1
I, of course, have no idea what any of the above means. Please help.

Looks like one component in Media Encoder is either missing or corrupted somehow.
Could you uninstall Adobe Media Encoder CC 2014 and please make sure all files are deleted after uninstall? Then, please try re-installing it.

Adobe Media Encoder Batch Processing

Similar Messages

Maybe you are looking for