Upgraded to CC 2014 and Media Encoder doesn't work now.

Using a mac with mavericks, all updated. Upgraded to Premiere Pro CC 2014 and Media Encoder CC 2014. But when I want to launch it... it won't open.
Help?

JUST FOR MAC USERS - Some 10.9.3 links
-next link says After Effects, but check YOUR permissions !!!
-http://blogs.adobe.com/aftereffects/2014/06/permissions-mac-os-start-adobe-applications.ht ml
-Mac 10.9.3 workaround https://forums.adobe.com/thread/1489922
-more Mac 10.9.3 https://forums.adobe.com/thread/1491469
-Enable Mac Root User https://forums.adobe.com/thread/1156604
-more Root User http://forums.adobe.com/thread/879931
-and more root user http://forums.adobe.com/thread/940869?tstart=0
-Mac 10.9.3 and CS6 https://forums.adobe.com/thread/1480238

Similar Messages

Premiere Pro CC 2014 and Media Encoder CC 2014 Crashing constantly

Running out of options and ideas...
Symptom: Every time I work on any project in Premiere Pro CC 2014 or try to render out in Premiere Pro CC 2014 or Media Encoder CC 2014, the software crashes after 2-3 minutes of use/rendering when the GPU is enabled in Premiere/Media Encoder, or after 5-10 minutes of use/rendering in software only mode. The crash is a software crash, Windows continues to run fine.
I have tried all the standard list of steps that adobe reps post on threads like these - clearing media cache, software only on render, new project, etc. https://helpx.adobe.com/x-productkb/global/troubleshoot-system-errors-freezes-windows.html
Windows event is not that helpful to me:
Faulting application name: Adobe Premiere Pro.exe, version: 8.2.0.65, time stamp: 0x5486db4a
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00007ff5ecb4de40
Faulting process id: 0x1dc8
Faulting application start time: 0x01d04a503cd82df2
Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
Faulting module path: unknown
Report Id: cacdfbab-b717-11e4-826d-8863dfc268bc
Faulting package full name:
Faulting package-relative application ID:
I have wiped adobe off the machine and reinstalled - same problem. I have tried projects that crash the machine on other machines and it works fine.
The machine is new, clean install and runs everything else great - 3ds max, high res games, scientific computing - max memory use, etc.
Spec:
5K iMac running bootcamp and Windows 8.1
Intel Core i7-4790K @ 4.0 GHz
32 GB ram
1TB SSD
AMD Radeon R9 M295X 4GB GDDR5
I have used this bootcamp/imac configuration for 5+ years on 3-4 machines and everything has always just worked great. Guess it was my time for a problem, but I'm open to new ideas to try...
Finally - I hope someone from Adobe reads this. I have spent 2 nights on the phone with support. The first night I got an over confident answer that it's a gpu driver issue, just go with software only (no luck - same crashes and different drivers aren't solving the problem). Tonight I was hung up on "by accident" as the agent looked up my video card after waiting 15 minutes to talk to someone, only to be hung up on a second time while on hold after calling back and waiting 20 minutes (because I assume the Adobe call center closed). No message to say so, just hung up on. An overall very disappointing experience.
Thanks in advance to anyone with ideas on things to try,
Cheers!

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

Premire Pro CC 2014 and Media Encoder Crash During Launch

Premire Pro and Media Encoder crash during startup and are unusable. I am using Windows 7 Ultimate and already tried reinstalling Adobe Creative Cloud from scratch and it's still happening. I also tried following Adobes KB articles directions to rename the Adobe folder in my documents and appdata to no avail. When I try to launch either application, I get a generic windows crash message "Adobe Premire Pro CC 2014.0 has stopped working" and when I click problem details, it lists this:
Problem signature:
Problem Event Name: APPCRASH
Application Name: Adobe Premiere Pro.exe
Application Version: 8.0.0.169
Application Timestamp: 536f4f89
Fault Module Name: ImageRenderer.dll
Fault Module Version: 8.0.0.169
Fault Module Timestamp: 536f2c18
Exception Code: c000001d
Exception Offset: 00000000001f5382
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
Additional Information 1: 0b2d
Additional Information 2: 0b2df4702c3fc6489bf922fb8e966350
Additional Information 3: fa9f
Additional Information 4: fa9f59f642d335ee71c6667e52000d39

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

Premiere Pro CC 2014 and Media Encoder CC 2014 not completing encode.

This is a project that I have been successfully encoding in short segments until now. Now when encoding, session runs about 10-15 minutes and then ends without error messages.
Removing effects and changing to Mercury PB Engine SW did not help.
Also tried disabling metadata as suggested in another forum.
When CUDA used, logged as "Encoding failed." When Mercury SW used, logged as "File Successfully Encoded" even though video file is only 6 KB with no content.
Premiere Pro Build 8.1.0 (81)
Media Encoder Build 8.1.0.122
Windows 7 Professional
Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz
8 GB RAM
NVIDIA GeForce GT 610 (9.18.13.3788)

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

Apps and media library doesn't work after software...

Hey guys!
Few days ago I updated my C3-00's software and my apps (Opera Mini and Facebook) doesn't work anymore. I tried reinstalling Opera but when I try to open it it says Opening Application and immediately after that Closing application (same with Facebook client).
My second problem is that my media library is messing with me because it maps the song artist and titles (484 songs) and only the few ones within a folder is played over and over. E.g. I try to play Queen - I want it all but Pendulum is played besides that.
Thank for helping

Read
http://support.apple.com/kb/ht1808

I have just upgraded to Firefox 5 and google toolbar doesn't work anymore. How can I go back?

What details?
''locking - asked & answered multiple time - moderator''

Thats because the old installed version of googletoolbar has a file named install.rdf that declares the max supported version of firefox to be 4.0.
To fix this ,just open the install.rdf file with notepad and change maxVersion from 4.0.* to 6.* (see the image i've also uploaded)
Now, in order to find the correct install.rdf file do the following:
Go to folder : C:\Users\[your user name here]\AppData\Roaming\Mozilla\Firefox\Profiles\[sometext].default and search for the install.rdf file (im using windows 7)
Windows search will find many install.rdf files (one for each addon you have installed on firefox) so make sure that you find the install.rdf that has the line
Google Toolbar for Firefox
in it. For this install.rdf file just rename the max version as stated above , restart firefox..and vuala! Google toolbar is back!

Premiere Pro CC 2014 update and Media Encoder update fail to install

Hi -
I've been updating my CC applications. But PP CC 2014 and media Encoder say: "UPDATE FAILED". Naturally I cannot get through to Abobe. Does anyone have a suggestion?
Harry

Hi Harry,
Sorry, chat and phone support are closed on weekends for the video queue. We only have general support open on weekends. It's been this way for years. Sorry if that caused some inconvenience.
I hope you have solved your issue. If on Mac, you can update NVIDIA drivers in the NVIDIA control panel in System Preferences. AMD GPUs are merely updated when you update OS X.
Also, please check out the doc that was recommended: Installation failed. Error U44M1P7 | Updates
If you are still having trouble, contact us Monday through Friday 7AM-7PM PST here: Contact Customer Care
If you can't get your issue solved, send me a PM and I'll try and help.
BTW, I am not sure why your post is marked as correct. I do have that ability but did not do that. Sorry for that.
Thanks,
Kevin

Media Encoder CS6 not working with Premiere

Hi
I have been merrily editing a lager job in Adobe Premiere CS6 and then queuing the time lines to export in media encoder CS6 done the entire job everything rendered fine then Bam all of a sudden when I try and render I get all the audio a couple of frames of video then just black!!
I have tried different codecs same result, I have tried different timelines same result, When I export directly out of Premiere without going through Media encoder all works fine, when I try encoding a file directly in media encoder works ok, It just seems to be the link between Premiere and Media encoder that not working as it should
Anyone got any ideas?
Hi Folks
Has no one had an issue exporting to Media encoder from Adobe Premiere CS6?

Any chance this gets fixed soon? I'm shooting with an AF-100, and at this point I'm still using Final Cut to transcode my footage so I can have audio. I've also noticed the video jumps around even when it does have audio. Prelude has been extremely problematic for me, and it doesn't have a way to bring in clips that returned errors upon importing, I have to write down the clip numbers and bring them in individually. I've also tried just dropping the file structure from the card straight to the hard drive. It's a huge problem, and is keeping me from making the switch fully from FCP 7.

AME CC 2014: "Adobe Media Encoder has encountered an unexpected error and cannot continue."

Adobe Media Encoder CC 2014 on MacPro "mid-2012" (MacPro5,1) running OSX 10.9.3 and getting this error when trying to launch Adobe Media Encoder CC 2014:
Adobe Media Encoder Error
Adobe Media Encoder has encountered an unexpected error and cannot continue.
Have uninstalled, reinstalled. Checked and fixed permissions numerous times. Tried removing all plugins and that didn't fix. Also tried editing the text listings within the .app for OpenGL and CUDA to remove all cards listed - that didn't fix anything either.
At this point it's uninstalled and "hopefully" everything will point to CC (non-2014 version). Adobe Media Encoder CC works fine. Adobe Media Encoder CS6 works fine.
Cannot find any other reports of this issue.

Progress in trying to fix. This workaround was NOT successful on previous attempts, but now appears to be working. Seems like the trick was to have AME CC 2014 started and open BEFORE doing any of this? As always, make sure all of your permissions are set properly - had done that numerous times previously. My issue was NOT directly permission related.
Navigate to the following folder:
You may see a file SHORTCUT that is invalid called "Presets":
Remove/delete this file. It's a broken shortcut.
Move a folder of .EPR files into the "8.0" folder. Call it anything except "Presets". Go to AME CC 2014 and quit. (I was greeted with another crash message.)
Open AME CC 2014 again. Your presets will not be loaded yet, but you should see an XML file that was created in your new folder like this:
Delete this file.
You should see a new folder also created by AME called "Presets". Move your .EPR files into this folder and delete the original folder. Quit AME CC 2014. (I was greeted with ANOTHER crash message.)
Open AME CC 2014. Your preset files should be there at the top under the preset browser:
Probably a good idea to keep a copy of those .EPR files elsewhere

Premiere Pro and Media Encoder crash while rendering H.264

Very recently, a problem's popped up where Premiere Pro and Media Encoder (CC) will crash while rendering H.264.
It's only while rendering H.264 - other formats seem to work fine.
And I don't mean that it returns an error, I mean it hard crashes with a Windows "Adobe Premiere Pro CC has stopped working" popup.
It doesn't crash at a consistent time during the render, even on the same project. Occasionally, it won't crash at all, but this is usually not the case.
I've tried disabling CUDA and my overclock to no avail. Please help!

On the topic of opening a project on the exact same version of Premiere Pro CC 2014 (yes it is definitely up to date, and the 2014 version), to overcome this export crash problem that ZachHinchy has brought up - you can't. Technically speaking, one should easily be able to open a Premiere Pro CC 2014 project from one system on another system running the exact same up to date, legitimate version of Premiere Pro CC 2014 without any kind of error. But for some reason, this has been disallowed(?) by Adobe. It has facepalm written all over it. Does anyone agree that this is at least a little bit silly?
I have tried exporting a Final Cut Pro XML from my project to try and open the sequence at uni on a Mac, so I can render my project when I finish my edit. It half works - the clips are there, but the sequence is gone - i.e. 12 hours of painstaking sequencing and micro-edits that had me at several points in time wanting to insert my hand through my monitor with enough force to make a large hole. I really cannot afford redo this sequence, as my assignment is due tomorrow, and I have to work at 6 oclock in the morning, so I also cannot afford to stay up till the early hours of tomorrow morning. Wish me luck that some miraculous event has taken place overnight that will somehow allow me to just open my project, on the same version of Premiere, on a Mac, without hassle. (Apple OS is not friendly to anything but its own selfish nature, so I am having doubts).
Adobe please, if you can do anything at all to help, you will save my assignment, and my faith will be restored. Otherwise, I'll just get my money back and buy Final Cut instead.
I cant even
If I find a way to fix either of these problems, I will post straight away.

Premiere pro and media encoder CC problem

Hi guys,
I hope some of you can help me, I installed new version of premiere pro and media encoder CC and now none of them works, I can edit in premiere but as soon as I press export message apears ''sorry a serious error has occurred that requires adobe premiere to shut down'' when I try to open encoder it shut down on startup.
I'm using old IMac 2.4ghz intel core duo, 2gb 667 mhz ddr2 sdram, ATI Radeon HD 2600 Pro 256 MB, OS X 10.8.5.
This is the error report, please help:
Process:
Adobe Media Encoder CC [946]
Path:
/Applications/Adobe Media Encoder 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 [136]
User ID:
501
Date/Time:
2014-02-10 08:44:28.001 +0100
OS Version:
Mac OS X 10.8.5 (12F45)
Report Version: 10
Interval Since Last Report:
1264 sec
Crashes Since Last Report:
1
Per-App Interval Since Last Report: 24 sec
Per-App Crashes Since Last Report:   1
Anonymous UUID:
7E711766-8C55-00D3-811F-852F73421407
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminate called throwing an exception
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib
0x00007fff9483c212 __pthread_kill + 10
1   libsystem_c.dylib
0x00007fff8d74ab24 pthread_kill + 90
2   libsystem_c.dylib
0x00007fff8d78ef61 abort + 143
3   libc++abi.dylib
0x00007fff96ff79eb abort_message + 257
4   libc++abi.dylib
0x00007fff96ff539a default_terminate() + 28
5   libobjc.A.dylib
0x00007fff8f49d887 _objc_terminate() + 111
6   libc++abi.dylib
0x00007fff96ff53c9 safe_handler_caller(void (*)()) + 8
7   libc++abi.dylib
0x00007fff96ff5424 std::terminate() + 16
8   libc++abi.dylib
0x00007fff96ff658b __cxa_throw + 111
9   com.adobe.dvacore.framework
0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
10 com.adobe.AMEAppFoundation.framework
0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
11 com.adobe.Batch.framework
0x0000000105c0a842 AMEBatch::Initialize() + 2194
12 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
13 com.adobe.ame.application
0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
14 com.adobe.exo.framework
0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
15 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
16 com.adobe.ame.application
0x0000000100056a38 main + 424
17 com.adobe.ame.application
0x0000000100003f74 start + 52
==========================
Edited by moderator to trim the crash report down to the essentials. Since these forums do not support attaching file (due to legal and security issues), we recommend uploading files using Acrobat.com’s Sendnow (https://sendnow.acrobat.com) or similar services (YouSendit.com, etc.)

Hi mawe81,
Thanks for posting on Adobe forums,
Please follow this document http://adobe.ly/1f2EHCg
and let us know if this fix your issue or not.
Regards,
Sandeep

Using Premiere CC and Media Encoder CC at the same time

Is this possible? Doesn't seem to be. Media Encoder bails on every job as soon as you try to render anything in Premiere. I guess they don't play nice together, which is surprising. I was hoping that Media Encoder would pause and wait for Premiere to finish a render. Instead it dies on every render job, creating 0 size video files... while making a sheep bleating sound.
Is this a GPU issue? I have 2 nVidia cards, a 770GTX and 560GTX. (Windows 8.1, 16gb RAM, 3770k CPU)

As soon as I initiate a render in Premiere, Media Encoder bleats, and all subsequent render jobs bleat and produce 0 size video output files... even if I quit the Premiere render before Media Encoder reaches some of those render jobs.
I suspect this is a GPU sharing issue.... but can't be certain.
What do you mean by new install? Did I install it (AME or Premiere) recently? No. I've had Creative Cloud on my machine for almost a year, and both Premiere and Media Encoder have been updated periodically.
To my knowledge they have never worked together, but I only started using the queue feature within Premiere recently, so I haven't used AME until recently.

Premier Pro CC and Media Encoder crashing on long file export.

Please forgive the length of this inquiry. But it is complicated and has a lot of variables.
I have an hour long mixed format timeline both Red 3K footage and Black Magic ProRes 1080P footage that I want to make a DVD from and it takes forever and crashes half way through. I have tried doing it every way possible and the only way I was able to get even a partial export was using the "MPEG 2 DVD" export option in Premier CC. It goes fast at first telling me it will take about 2 hours but even though it starts quickly doing about 15 fps it slows down to less than 1 fps and finally just stops and crashes my Cuda Core enabled Macbook Pro Laptop.
I really don't know who to ask about this since there are so many different variables. I never had a problem like this on my MBP with PP6 on a 4K timeline exporting to DVD or Blue Ray or to H-264 or Even Prores. But I wasn't mixing formats either. But on this project the first 20-30 minutes of footage goes through fine in a couple of hours but something seems to be bogging down the system on longer projects. My work around was to break the project up into multiple exports and combining them on the DVD timeline but I can't do this on every project. I thought maybe it was a corrupted clip somewhere in the timeline but when I broke the timeline up into several parts I had no problems.
I did notice a dramatic variance in the time it took to export footage based on the sequence settings. A one minute timeline comprised Red 3K footage and ProRes 1080P footage Here are some sample export results:
From a Red raw 3K timeline 2880x1620 with 1080P Prores footage upscaled 150%)
to .m2v Mpeg 2 720x480 format    1:48 Minutes ***
to .mov Prores 422HQ 1080P                         22 Minutes
to .mov H.264 1080P                    22 Minutes
to .m2v Mpeg 2 1080P                                                22 Minutes
From a 1080P timeline Prores footage at 100% (Red footage downscaled to 67%)
to .m2v Mpeg 2 720x480 format                         13 Minutes
to .mov Prores 422HQ 1080P                             13 Minutes
to .mov H.264 1080P                                                             14 Minutes
to .m2v Mpeg 2 1080P                                                            14 Minutes
Since I am going to DVD, I chose the fastest option Red to m2v Mpeg 2 720x480 format which only took 1:48 per minute. Why? I have no idea. Maybe someone here knows the answer. But again these numbers are for a ONE MINUTE clip when I tried to convert the whole hour timeline to the 720x480.m2v DVD File the Red timeline froze my computer after several hours even though I had set sleep mode to “Never” and turned the display off manually and I had to convert it in multiple chunks. In 20-30 minute chunks it did go fast about 1:48 per minute like the test indicated. But I would like to be able to convert the whole hour and not to have to try to stitch the clips together in my DVD authoring program.
I don’t want to have to avoid using multiple formats on the same timeline or waste time transcoding everything to the same format.
Can anyone give me any suggestions as to why the computer is crashing or bogging down in long exports and what timeline settings I should be using?
I have plenty of room on my Scratch Disk and 8 Gig of RAM and according to my Activity Monitor during the export process have about 800 Meg of System Memory during export but the CPU Usage is 98% and in my Activity Monitor I see under “Process Name” ImporterRedServer flashing up at the top of the list about every second during export.
Why .720x480 mpeg DVD setting is so much faster than all the other export codecs?
And if there are any other settings I can use to get higher speed exports in HD? 14x1 seems a little slow especially since every time it crashes I have to start over.

Hi,
Since a long time I did not encounter the crash of Media encoder with
long file export.
But I take care of a lot of details before the export :
- clean up Media cache and Media Cache Files within PP CS6 and/or CC,
- delete all render files with Preview Files,
- rendering of sequences until the rendering is completed,
- PP CS6 and/or Pp CC opened during export to AME and/or Encore CS6,
I guessed to leave Adobe but this company remains the last with a
serious authoring software (Encore CS 6).
I tested :
- Avid Media Composer, Final Cut Pro X, both are very good software but
no really authoring software for these video editing softs.
Th only way is to "flood" Adobe with "bug reports" and "wish forms"
which are not very easy to use.
And also to call the Adobe support day by day until they send they
escalate the bug.
Le 16/05/2014 16:51, alainmaiki a écrit :
>
      Premier Pro CC and Media Encoder crashing on long file export.
created by alainmaiki <https://forums.adobe.com/people/alainmaiki> in
/Premiere Pro/ - View the full discussion
<https://forums.adobe.com/message/6384665#6384665>

Premiere Pro CS6 and Media Encoder CS6 Color shift on export

Hello,
I am working on an early 2008 Mac Pro with 2 X 3.2 GHz Quad Core Intel Xeon Processors 32 GB of RAM a NVIDIA GeForce 8800 GT 512 MB Graphics Card and I am running OS X 10.8.2.
I have the updated Version of Adobe Premiere Pro CS6 and Media Encoder CS6 through the awesome Subscription program that Adobe has started.
My footage is shot with the Canon 1D Mark IV shot 1920X1080 at 24 FPS
I am importing the camera files and then exporting them after I cut them up in to Quicktime Pro Res 422 HQ files
With the technical explination out of the way here is my problem. I have color right from the camera files that I like. and with out doing any thing to change the color I export the footage and get a dramatic color shift. The exported file looks desaturated and slightly green.
I have tried using Media Encoder CS6 to export my footage and that has the same result.
I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
I have attached three screen shots that show the color shift exactly. Now what I need is a solution. What I am not seeing is color settings for Premiere. I am totally open to any suggestions on what I might be doing incorrectly.
Ben

Benjamin Peterson wrote:
I started my career as a photographic retoucher and use photoshop and light room constantly so I am pretty confident that i know color. I also calibrate my Lacie 526 and Lacie 324i montiors monthly as well as have a sensor that will slightly shift the profile depending on the time of day.
I've been doing this for a few years now, and have come to some conclusions. Basically, the difference between still photography and video is like the difference between playing the trumpet and the sax. What you bring to the sax from playing trumpet is your ability to read music, what you know about composition, blending while playint with others, ect. But playing trumpet tells you nothing about how to physically play a sax. So it is with still photography and video.
For starters, your carefully calibrated computer monitor is just that, a computer monitor. It doesn't display the correct working space for video. What you need for WYSIWYG in video is a monitor that can show you the Rec.709 working space. Rec.709 has a different gamut, a different gamma, probably a different white point (D65), different phosphor colors, etc., etc., etc. Enought differences that it's difficult to make a computer monitor that can successfully display Rec.709. Yet there are a couple of computer monitors that can do this (a few Eizos, one HP). The vast majority of people doing serious color correction work in video use a production monitor for just this reason.
But a production monitor isn't enough. You also have to make sure that the signals you're sending the production monitor are correct. There's a sub-industry making signal converters for signals from NLE video cards (usually RGB based) -> signals for production monitors (usually YUV based).
That said, it is certainly possible to get a very good match between your NLE suite and a DVD / BD as displayed on an HDTV. But it's not as simple or easy as a calibrtated computer monitor for still photography use.
This is probably part of your problem. But Quicktime is probably the root of it. Quicktime is, well, I guess the polite way of saying it is that Quicktime is problematic. It gives all kinds of problems. Most people have abandoned it. You should too.

Premiere and Media Encoder will will no longer export my edit to any file format.

This is on a Windows 8.1 PC.
The edit exported fine until I made one big mistake.
I created a Nested Edit to make a quick alteration.
Since then the following is now the case and I cannot go back to an earlier edit to fix this.
Premiere and Media Encoder will will no longer export my edit to any file format. Using either the Export Option or Media Encoder. Get a dialog that says "Unknown Error Compiling Movie"
There is nothing wrong with my footage. This edit worked fine and I export through Media Encoder many times until I made a Nested Edit within the Premiere Project.
I have tried all sorts of searches on the net for a fix to this but nothing seems to be current or indeed works.
Any help would be appreciated as this is a show stopper.

Thanks for the reply Mark, appreciated.
I have found a work around but it still leaves a long term issue for Adobe to fix.
As to your first solution:
1). The nested edit is already in its own timeline panel. It will not export or encode via media encoder. This is the problem.
2). I will try the KEM roll feature but I have a work around see following.
3). No I do not have a nested edit within a nested edit.
I did a lot of research on the net on this issue as it happened to a colleague of mine on his machine about two weeks ago. It took me six hours to get a fix and in his case there were six video clip that had read errors. When I overwrote those clips from the original backup master it fixed the problem. However I was never able to use Media Encoder again to export his project without it failing. I could only use the Export feature. Again he had used a nested edit in his project.
I my case I do not have any nested edits within a nested edit. All I did was drag my main edit onto the New Sequence icon at the bottom of the Project Bin. This of course created a nested edit in a new Timeline Panel which is what I wanted. I then slid the entire nested edit to the right in the timeline by two seconds as all a wanted to do was add two seconds of black at the head of the edit. That was it. From that point of creating the nested edit Media Encoder and the Export option failed every time with the fore mentioned error.
The final work around was one of those I found previous mention of during my research. I created a new clean Premiere Pro CC 2014 project, I then used the import option under the file menu. I imported only the original main edit which brought in that edit along with all the required footage. This would then export to disk using the Export feature. However, Media Encoder will still not encode this new edit, it fails the same way every time, 'Unknown Error Compiling Movie'.
As a test I loaded the old corrupt edit project back up and deleted the nested edit sequence completely and re-saved it. This had no effect and did not fix the problem. This particular project file will no longer export directly or via media encoder at all no matter what I do.
This seems pretty serious to me. I worked on this edit for a whole month without issue, encoding out roughs as a went without any issue, it was only yesterday after I made the nested edit that the project file is now useless as it will not encode out at all. Yes I have a work around and was able to salvage my project and get it rendered in time for my deadline but the fact I have a partially working Project that Media Encoder will not touch does not instill me with confidence for long term use of Premiere Pro if this is going to happen again.
Is there some place I can send this project file to Adobe to see if they can find out what is wrong with it? I am not the only person having this issue I have seen other post going all the way back through CS6 it seems.

Upgraded to CC 2014 and Media Encoder doesn't work now.

Similar Messages

Maybe you are looking for