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.

Similar Messages

  • 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 CC and Media Encoder won't start

    Hey everyone,
    I have a huge problem: My Adobe Premiere CC won't start. I've tried all the solutions I've found in the internet, but nothing seems to work for me
    I am using OS X 10.9.3.
    Here is a part of my report:
    Process:         Adobe Premiere Pro CC 2014 [1153]
    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 [235]
    Responsible:     Adobe Premiere Pro CC 2014 [1153]
    User ID:         501
    Date/Time:       2014-12-10 23:51:37.341 +0100
    OS Version:      Mac OS X 10.9.3 (13D65)
    Report Version:  11
    Anonymous UUID:  5BE9B722-1F73-691F-5EEF-9775088356E8
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000001650
    VM Regions Near 0x1650:
    -->
        __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_platform.dylib       0x00007fff9195abe6 OSAtomicAdd32Barrier$VARIANT$mp + 2
    1   libclh.dylib                   0x00007fff9076859f 0x7fff90765000 + 13727
    2   libclh.dylib                   0x00007fff90875305 clhCtxCreate + 101
    3   libGPUSupportMercury.dylib     0x00007fff94e2daab gldCreateQueue + 651
    4   com.apple.opencl               0x00007fff8f68e8ad 0x7fff8f688000 + 26797
    5   com.apple.opencl               0x00007fff8f68d32b 0x7fff8f688000 + 21291
    6   com.apple.opencl               0x00007fff8f68d211 0x7fff8f688000 + 21009
    7   com.apple.opencl               0x00007fff8f6a9fbe clCreateCommandQueue + 150
    8   com.adobe.GPUFoundation.framework 0x0000000109afbeb1 GF::CreateOpenCLCommandQueue(_cl_device_id*, _cl_context*, bool) + 65
    9   com.adobe.GPUFoundation.framework 0x0000000109ad521f GF::Device::InitializeContextImpl() + 2479
    10  com.adobe.GPUFoundation.framework 0x0000000109ad76ae GF::Device::InitializeContext(bool, void*, void*) + 622
    11  com.adobe.GPUFoundation.framework 0x0000000109af141a GF::Initialize(bool, bool, bool, void*, void*) + 2154
    12  com.adobe.DisplaySurface.framework 0x0000000111bb7f84 DS::Initialize() + 228
    13  com.adobe.Mezzanine.framework 0x000000010636c3cd MZ::(anonymous namespace)::FullInitializer::FullInitializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 6173
    14  com.adobe.Mezzanine.framework 0x0000000106369874 MZ::Initializer::Initializer(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, bool, bool, bool) + 84
    15  com.adobe.Frontend.framework   0x00000001000abe97 FE::Initializer::PrivateImpl::PrivateImpl(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 1479
    16  com.adobe.Frontend.framework   0x00000001000aadc8 FE::Initializer::Initializer(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 40
    17  com.adobe.Frontend.framework   0x00000001000cdc32 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 226
    18  com.adobe.Frontend.framework   0x00000001000d4ea5 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
    19  com.adobe.AdobePremierePro     0x00000001000018ac main + 508
    20  com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

    AND Media Encoder won't start as well!!
    Process:         Adobe Media Encoder CC 2014 [1284]
    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:         8.1.0.122 (8.1.0)
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [235]
    Responsible:     Adobe Media Encoder CC 2014 [1284]
    User ID:         501
    Date/Time:       2014-12-10 23:59:55.226 +0100
    OS Version:      Mac OS X 10.9.3 (13D65)
    Report Version:  11
    Anonymous UUID:  5BE9B722-1F73-691F-5EEF-9775088356E8
    Crashed Thread:  0  Dispatch queue: com.apple.main-thread
    Exception Type:  EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000001650
    VM Regions Near 0x1650:
    -->
        __TEXT                 0000000100000000-0000000100088000 [  544K] r-x/rwx SM=COW  /Applications/Adobe Media Encoder CC 2014/Adobe Media Encoder CC 2014.app/Contents/MacOS/Adobe Media Encoder CC 2014
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   libsystem_kernel.dylib         0x00007fff93a9a292 __kill + 10
    1   com.adobe.dvacore.framework   0x00000001003a28ea (anonymous namespace)::SignalHandler(int, __siginfo*, void*) + 410
    2   libsystem_platform.dylib       0x00007fff9195b5aa _sigtramp + 26
    3   libsystem_platform.dylib       0x00007fff9195abe6 OSAtomicAdd32Barrier$VARIANT$mp + 2
    4   libclh.dylib                   0x00007fff9076859f 0x7fff90765000 + 13727
    5   libclh.dylib                   0x00007fff90875305 clhCtxCreate + 101
    6   libGPUSupportMercury.dylib     0x00007fff94e2daab gldCreateQueue + 651
    7   com.apple.opencl               0x00007fff8f68e8ad 0x7fff8f688000 + 26797
    8   com.apple.opencl               0x00007fff8f68d32b 0x7fff8f688000 + 21291
    9   com.apple.opencl               0x00007fff8f68d211 0x7fff8f688000 + 21009
    10  com.apple.opencl               0x00007fff8f6a9fbe clCreateCommandQueue + 150
    11  com.adobe.GPUFoundation.framework 0x0000000109ef7b01 GF::CreateOpenCLCommandQueue(_cl_device_id*, _cl_context*, bool) + 65
    12  com.adobe.GPUFoundation.framework 0x0000000109ed0e6f GF::Device::InitializeContextImpl() + 2479
    13  com.adobe.GPUFoundation.framework 0x0000000109ed32fe GF::Device::InitializeContext(bool, void*, void*) + 622
    14  com.adobe.GPUFoundation.framework 0x0000000109eed06a GF::Initialize(bool, bool, bool, void*, void*) + 2154
    15  com.adobe.DisplaySurface.framework 0x0000000107845f74 DS::Initialize() + 228
    16  com.adobe.ame.application     0x00000001000376e7 AME::app::MCInitializer::MCInitializer() + 12039
    17  com.adobe.ame.application     0x000000010002323a AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 250
    18  com.adobe.ame.application     0x000000010000d2ba AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 1802
    19  com.adobe.exo.framework       0x00000001057d2bd5 exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1141
    20  com.adobe.ame.application     0x00000001000167e6 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> > > >&) + 3270
    21  com.adobe.ame.application     0x0000000100047828 main + 440
    22  com.adobe.ame.application     0x00000001000032f4 start + 52

  • 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.

  • I cannot import .mov files to Premiere Pro or Adobe Media Encoder.

    I cannot import .mov files to Premiere Pro or Adobe Media Encoder.
    How do I around this problem?

    We need to know a lot more if we're going to help you.
    What happens when you try? Do you get an error message? If so, exactly what does it say?
    What version of Premiere Pro? Have you installed the recent updates? What operating system?
    Does this happen for all .mov files or just some? Has this ever worked before? What version of QuickTime do you have installed?
    Here's a page written for After Effects, but the information is relevant to Premiere Pro and AME, too:
    http://blogs.adobe.com/toddkopriva/2011/02/troubleshooting-quicktime-errors-with-after-eff ects.html

  • How can I get a copy of Premiere and Media Encoder CS6?

    I need to be able to convert a video that has an alpha channel into an FLV file for import into Captivate 8. Captivate only works with FLV and MP4, and only FLV has an alpha channel. However, FLV was removed as an option from the CC version of Premiere/Media Encoder.
    Supposedly, you can download old versions of the software from the CC desktop app, but I can't. In my CC app, there is no Old Versions option in the Filters, and there is no option to download old versions on the Install buttons, or anywhere else for that matter.
    We have the Team version of CC, and our IT dept is switching us over to Enterprise, if that has anything to do with it.
    So, is there any way to download and install CS6 versions of Premiere and Media Encoder?

    check this thread with the same question about languages!!!
    https://forums.adobe.com/message/7437370#7437370
    hahahahahahahahahahaha!!!!

  • Exporting from Prem CS6 through Media Encoder CS6 gives 'media offline' frames

    Hi
    I'm having problems with Prem and Media Encoder.
    If I 'queue' the output of a project and use AME, wherever there are graphics laid on top of HDV footage in a PP sequence, AME is adding a red frame that says 'media offline' in several languages. If I 'export' from PP without using AME, it renders fine.
    Everything looks good in the PP sequence, all files are present and work fine, so I deduce this is an issue between PP and AME.
    Is this a known problem? IS there a workaround?
    This system has successfully completed other projects recently. The overlaid graphics in this case are TIFFS, would that cause a difference?
    I'm a long time PP/AME user - but CS4 on PC until recently when I bought PP CS6 for Mac, running it on a maxed out iMac.
    OS and Adobe are fully up to date, and have tried a restart.
    Thanks

    Bump!
    Nothing from Adobe on this?
    Richard

  • Premiere Pro CS5.  Media Encoder .dll interace message.

    Out of the blue, when I am working in Premiere Pro CS5 and want to export media, I get an error message about "this software could not find the required software interface .dll.  Reinstall the software and try again..."
    This just started several days ago.  I have changed nothing.  I did do as asked and reloaded the Adobe Premiere program and that worked for about a day.  And now it is back.  Also, my Premiere CS5 is starting to crash fairly often where as before it never did.  I haven't changed anything on the computer.  No new software added.  No windows 7 updates of any kind.
    Any ideas on what to do.

    I experienced this at one point.  Searching the WEB I saw suggestions that there was a problem with a recent version of Quicktime.  (I have no idea why the quicktime player would have an impact.)  However, reverting to an earlier version of Quicktime fixed the problem.  Search this board using quicktime as a search phase.  The quicktime web site allows you to download the earlier versions.  I'm not at my editing machine, but I believe that I am at version 7.5.2.

  • Problems exporting mpeg 2 videos using Premiere Pro CS6 and Media Encoder

    Using a Mac, I'm trying to exporting an mpeg 2 video from Premiere Pro CS6 using the queue process that opens the Media Encoder but when the process begins, it freezes and doesn't end.

    Using a Mac, I'm trying to exporting an mpeg 2 video from Premiere Pro CS6 using the queue process that opens the Media Encoder but when the process begins, it freezes and doesn't end.

  • Queuing from Premiere Pro to Adobe Media Encoder no longer working? CS6

    Hi there,
    Just very recently adobe media encoder has stopped accepting que's from premiere. I choose export in premiere, setup the export details and hit que, adobe media encoder launches, but then it flashes once (like disappears reappears, very quickly) and then it just simply does nothing. No item appears in the que. I have tried opening the premiere sequence directly from adobe media encoder but it does nothing either. If I drag the premiere project directly onto a preset in adobe media encoder, it crashes every time. (though not sure if it would of done this previous to my problem arising)
    Anyway, very frustrating as I usually work on a different project whilst media encoder is rendering something out. Now i'm stuck with huge down times as I wait till the render is finished.
    Recently updated to Mac OSX 10.8.3 - I think this is when the problem began.
    Just updated the CUDA driver to 5.0.45 but this has not changed anything.
    Working on a Mac Pro 5,1, 2x2.4Ghz 24GB RAM, EVGA GTX 660 FTW,

    Some suggestions and answer at least the 16 questions at the end of the Wiki article.

  • Adobe Premiere Pro CC or media encoder MFX OP1a Bug

    Hi I'm outtputting for broadcast TV Commercial and getting a consistant audio issue with adobe premiere pro cc MFX OP1a using IMX30 pal export master. Orginial project is HD exported AVI from After effects, audio is .wav 48k. The audio has a glitch where it almost seems to drop out by a frame. I tried this over and over again with all my projects and the same issue. It's usually around 1 second in and occurs once. My projects are 30 second in length or 15 second at a time. I have ended up going back to Adobe CS6 so I can fix this issue and send to the tv station for playout (cs6 is fine). Is there any chance someone could look into this or check to see if there is an issue here?  I have tried this on all our computers here running CC and the same issue.

    Bumping this as it seems to be an update issue. I have noticed it now with premiere pro cs6 update. Works fine for 6.0.3 but the update to 6.0.5 has the same issue as above. Have reported this to Adobe however don't see any changes, this is a major problem since this is the broadcast standard for uploading to station down in NZ and the media uploaded has confirmed other cases of this issue around.

  • Premiere Pro CC and Media Cache

    Hello!
    I've read the documentation on Media Cache (http://help.adobe.com/en_US/premierepro/cs/using/WSF08BCDDB-FCD7-40a2-8290-8872EE725E6B.ht ml#WSa41b87baf39dd9b0-4a7aee25125bce32690-8000) but I didn't understandt what are exactly the formats/containers that Premiere Pro creates cache for?
    Also, am I remembering wrong, but was in Premiere Pro CS 5.5 and CS 6 the cache for the project was kept in the same folder as the project?
    Does Premiere clean the Media Cache regularly or I have to remember to do it from time to time?

    I don't think that much has changed regarding the treatment of cache files from CS5 to CS6 to CC.
    Here's how I manage the cache files:
    1) Set Premiere to store media cache and media cache database in a drive folder separate from your project files (use menu: Edit / Preferences / Media and then browse to where you want them - I use "X:\premiere_cache"). This way, when you back up projects you are not backing all of this stuff up too.
    2) They do not clean up for themselves - go to the same panel mentioned in #1 and click the "clean" button to remove all of the files. When Premiere Pro is closed, you can manually delete all of the folders created by Premiere and you will not destroy anything that is recoverable.
    The purpose of cache files is to prepare some files additional your projects and media for performance enhancing reasons.
    Regards,
    Jim

  • Exporting from Premiere Pro CS4 using Media Encoder gets stop error

    I am trying to export my timeline from Premiere Pro CS4, using the Adobe Media Encoder CS4 to export my timeline as an MPEG2 HDTV 1080 24, and it goes for about fifteen minutes then I get the blue screen and my computer restarts, telling me the program had a stop error.  Is there a way to go around this step?  Another method to get the mpeg2 without losing quality?  Anything I can do?
    Please offer any knowledge you have before I scream at my computer again.
    Thank you

    as I know Adobe products are buggy no matter what hardware you have.
    I am sorry, but my experience has been the absolute opposite of what you have heard, or experienced. I have used many, many Adobe programs for almost 2 decades (maybe even more than 2 decades?), and have never observed such. I do have to admit that over those many years, I have always had a "state of the art" computer, but have made plenty of $ using Adobe software. Even with my now aging workstation, things work great. Time to upgrade though.
    When troubleshooting issues, they shake out like this:
    1.) system
    2.) Assets
    3.) Project
    4.) OE
    5.) Bugs
    This is after troubleshooting Adobe issues from almost the time that PS hit the PC, when they were only NNTP, in what, 1985?
    Now, I am not saying that your issue IS hardware, but only that that is the most likely issue, given a BSOD. Also, system is the #1 cause of issues, so that is where I start.
    Good luck,
    Hunt

  • Premiere Pro CC 2014 & Media Encoder Crash when rendering

    Every time I try and render something out of Premiere Pro CC 2014 it will crash before it completes the render. I have no idea why. I am on a windows 8 machine running the latest version of Premiere Pro CC 2014.Any idea what is going on?
    Here is the log from Event Viewer:
    Faulting application name: Adobe Premiere Pro.exe, version: 8.0.1.21, time stamp: 0x53c7b17f
    Faulting module name: mc_enc_avc.dll, version: 9.8.11.6624, time stamp: 0x536af65d
    Exception code: 0xc0000005
    Fault offset: 0x00000000000e7f80
    Faulting process id: 0x650
    Faulting application start time: 0x01cfb99562fe469a
    Faulting application path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe
    Faulting module path: E:\Program Files\Adobe\Adobe Premiere Pro CC 2014\mc_enc_avc.dll
    Report Id: f30f38a1-2589-11e4-bf2c-bc5ff467c039
    Faulting package full name:
    Faulting package-relative application ID:
    Here is the Report.wer that windows automatically generates: http://pastebin.com/hriEegkJ
    I have also tried rendering out of media encoder and I get a crash also (Report.wer: http://pastebin.com/Dpvk6bDb):
    Faulting application name: Adobe Media Encoder.exe, version: 8.0.1.48, time stamp: 0x53c99d97
    Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
    Exception code: 0xc0000005
    Fault offset: 0x000000002c2cce3d
    Faulting process id: 0xcf8
    Faulting application start time: 0x01cfb9906060796e
    Faulting application path: E:\Program Files\Adobe\Adobe Media Encoder CC 2014\Adobe Media Encoder.exe
    Faulting module path: unknown
    Report Id: 07096c20-2584-11e4-bf29-a0f3c1153ce7
    Faulting package full name:
    Faulting package-relative application ID:

    More hardware information might help someone give you an idea
    -Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840
    or
    http://blogs.adobe.com/kevinmonahan/2014/01/13/computer-shuts-down-with-premiere-pro-or-af ter-effects/

  • Premiere Pro error saying Media Encoder is not installed (it is)

    I'm trying to export a sequence from Premiere Pro CC 2014 to Media Encoder CC. After changing all the export settings to what I want in Premiere, I go to select the Queue button and receive the message "Adobe Media Encoder is not installed. Please download and install it to use this feature. Go to https://creative.adobe.com/apps". I have Media Encoder open right now. Any idea why they aren't communicating? I'm using a Macbook Pro btw.

    You need AME 8.0.1 to match that version of Premiere. The most up to date for both is 8.2.0. Try clicking on help-updates in each program rather that using CC updater.

Maybe you are looking for