Premiere Pro CC 2014.1 - end of media indicators different in source and program monitors???

Here are two screen grabs showing the right edges of the source and program monitors in PPCC 2014.1. Does anyone know why the end of media indicators are so different? Left is source monitor, right is program monitor.

Those are actually different indicators. The one on the left is the end of media indicator, which lets you know there are no more frames in the source clip. The one on the right is commonly known as the end of sequence indicator, which can also get to in the Source Monitor if you play a clip to the end and then hit Right Arrow.
Both indicators are controlled by the same option in the Overlay Settings dialog: End of Media/Sequence Indicators.

Similar Messages

  • Why are Adobe Premiere Pro CS6 source and program monitors playing each others footage?

    Why are Adobe Premiere Pro CS6 source and program monitors playing each others footage? I import my footage into the project like normal. I drag it to the source monitor on the left hand side to set in and out points then I drag it to the time line. The footage drops into the time line with no problem but when I go to play the footage in the time line it plays back on the source monitor and not on the program monitor like it is suppose to. Other times ill drag the clip to the time line and trim it there and it will be fine and show up on the program monitor.  Then ill go try to set a clip to have in and out points (which is suppose to show up in the source monitor) but it shows up in the program monitor. The clip is not even in the time line it should not be on that monitor! I have updated the program to the late update. I have re installed the program numerous times and I have even ran the Adobe Clean up program. Couldn't find much on this problem. Please help thank you! I have a PC. My computer is also way over the recommended minimum specifications to have the program installed on.

    Definitive Answer (I believe): It's all about this setting, "Write XMP ID To Files On Import" - which confirms that Adobe Premiere Pro is deliberately modifying the .mov file: http://helpx.adobe.com/premiere-pro/using/preferences.html#WSE3BD4A43-7022-4fe6-97F5-95313 935347B
    These posts give some background as to why having this setting enabled would be beneficial: one benefit being to be able to skip conforming files by matching the conformed file with the original using the embedded XMP tag :-
    http://helpx.adobe.com/premiere-pro/using/preferences.html#WSE3BD4A43-7022-4fe6-97F5-95313 935347B
    http://www.dvinfo.net/forum/adobe-creative-suite/498627-why-premiere-modifying-video-files .html
    https://forums.creativecow.net/thread/205/876064
    (Found using Google search term "adobe premiere pro date modified")

  • Source and Program Monitor not working after October CC 2014 Update

    I updated to the October 2014 Replace of Premiere Pro and since then I have had major issues with the Source and Program monitors. 
    I can select a clip from the media browser and have it appear in the source monitor - click play.  The clip will play for a bit and the picture will stop, but the audio will keep going. After a few seconds the source monitor will just display a red screen and the audio will keep going.   The same things happens in the program monitor  (different clips that worked before the October 2014 update) will start displaying the yellow media pending screen - and then go to red after a few seconds.  Again - this is a mutli-camera sequence that worked before the October 2014 update. 
    I am pretty much dead in the water at this point.  And yes, I have rebooted, changed the Mercury play back engine from hardware to software.  Nothing seems to correct the issue. 

    I have had similar problems. In fact playback is so sluggish it is unworkable.
    In addition Audio in nested sequences doesn't play back, and when it does it is intermittent. Totally unworkable!

  • When clicking an audio clip on the timeline in Premiere Pro CC 2014, it duplicates it on a different track and makes it impossible to work.

    I'm experiencing a disturbing issue as it actually prevents me to do the work in Premiere. I will put as much info as possible:
    1) Project started on a different computer (the editor), PC with Premiere Pro CC,
    2) Now opened on my Imac with Premiere Pro CC 2014,
    3) I am not editing, simply trying to move audio clips on different tracks to export audio tracks only,
    THE ISSUE:
    1) Here is my timeline:
    2) When I select an audio clip to highlight it, Premiere creates a duplicate on a different track:
    Note that the clip highlighted in the previous screen cap is the duplicate and I didn't click it, Premiere highlights it as soon as it is duplicated.
    3) When I click out of the timeline or scroll up or down on the timeline, the duplicates disappear. However, when I try to move the original clips, it doesn't do anything, they are stuck in place.
    ANTICIPATED ANSWERS:
    1) You work on 2 different computers with 2 different versions of Premiere Pro CC, what do you expect? --> The amazing thing about Adobe CC is that it shouldn't be an issue and now I have to deal with it in this way,
    2) Try and save an updated version of your project from your computer. --> Already done that.
    Thank you for your help. I usually use the customer support chat but I am on the other side of the globe and it is now closed. This issue prevents me to work so I need to solve it quickly.
    Kind regards,
    Aurelien

    This sounds to me like it could be a graphics related problem are you on the latest driver. Something else you could try, start a new project and import the one from the PC into that rather than directly opening it in the MAC

  • Premiere Pro CC 2014 gets stuck on Media Pending.

    Hi there,
    I've been having a bit of trouble with PPCC 2014 opening projects then getting stuck with all my footage and assets and after effects comps just displaying with 'Media Pending'. The program still works, opens, and I can save and click around so it's not crashing but nothing loads unless I force it to relink which obviously isn't great when I'm having to edit multiple large projects. These projects still open just fine on regular old Premiere Pro CC so I will continue using that for the time being.
    Media Encoder is also having an issue with After Effects comps that are in Premiere Pro timelines and only display as 'Media Pending'.
    Fortunately all these issues go away if I reboot my machine and try again straight away, but having to reboot my mac just to open a project or do a export isn't exactly preferable.
    I have a Mac Pro (late 2013) with 10.9.4 with 16gb Ram and a AMD D500 3GB card.
    I'm just wondering if anyone has been suffering with the same issues and has come across any fixes.
    Thanks in advance.

    Here is my post from another thread concerning the same issue:
    I got through Adobe to connect to me remotely to solve this problem twice. They cleaned the cache and preferences and renamed my Adobe folder under applications (don't exactly know how thy did it.) The problem disappeared only to come back after a little while. No video playback, unresponsive buttons - but playable audio, and media pending for all clips. I told them to report this to tech support. This was about a month ago but no updates still..I know I hadn't had this issue neither with CS6 nor with CC.
    I am currently rendering my project after changing the sequence's editing mode to Quicktime ProRes Proxy to see if it will help. Preview is still preview but as you said maybe the issue is to be with preview settings set to i-frame mpeg. I have read about the mpeg importer plugin to be an issue in previous versions of premiere pro concerning issues with media pending but i might be wrong.
    After changing the sequence settings to Prores Proxy (or if you don't have these codecs installed you may try another codec or google "Prores codec install" and have them installed) the problem cleared away. I have looped the timeline and played it over and over for a couple of hours without the issue surfacing.
    For Adobe support and for others to know here is a wiki concerning the issue in CS5. FAQ:Why does my clip show as "media pending"? - Adobe Premiere Pro

  • Premiere pro cc 2014 black screen or "media offline"

    Almost impossible to do much work in Premiere CC 2014. I use 3 machines in business and Premiere doesn't work with any of them for long. I can be editing fine for about an hour then suddenly my program monitor goes black or says media offline. The only way I can get it back is to reboot about 4-5 times before the project will load again. This happens regardless of where the media is stored, what version of Mac OS is used, or what plugins are used. Anybody else experiencing this?

    Hey John! Thanks for the help! So far I've encountered the issue on three different macs. Two are stock iMacs so some AMD chip. The third and least problematic is a desktop running a GTX 780 with CUDA 6.0.46. I will have to check on the two iMacs on Monday... I'm updating the Cuda for the desktop to see if that changes anything.

  • Media showing pending in project folder and source and program monitor

    I have Premier Pro CC and Premier Pro CC 2014 and I now have an issue with some imported files showing in the project window as pending. If I open them in the source monitor or program monitor I get the same message. Some of the files are green until you hover over them then they go to the gold screen with text showing Media Pending. Any ideas what's going on? I'm on a PC with 32G memory and nvidia GTX680 GPU and I was not experiencing this issues before.

    On the slight chance you're using that awful, notoriously bug-laden plug-in Magic Bullet Looks, it's causing this same problem, and you are guaranteed that by disabling it, your problem is solved.  It was a nightmare for me, because my whole project was color-corrected based upon that plug-in, so I had to downgrade to an earlier version from last year since Red Giant are totally stagnant in fixing its bugs.

  • Source and program monitors in Premiere are Pure Grey, no video, no frame for video

    I can load a clip into the source monitor; it has the name on top ("Source: [clipname.MOV"], but there's no video there, not even a frame where video would go.  Let me be clear: this is not a black video frame situation.  The Source monitor is the gray background color edge to edge.  If I play the clip, the position indicator moves and I hear  sound.
    The same situation for the program monitor.  Timeline is open, video and audio are there -- and the V1 track is enabled.  Play it and there's sound, the position indicator in the timeline and the program monitor track perfectly, but all there is in the program monitor is the grey background color edge to edge. The timeline that's open holds a amall edited piece that used to show up quite fine in the Program monitor.
    When I go into the setting of the source and program monitors, I see that "composite video" is selected...
    Ah, now the plot thickens.  If I choose something else, let's say "Vectorscope", when I select "Composite Video" again, it STAYS as a Vecotorscope.  In the dropdown Composite Video is checked (dotted, really), but the Vectorscope remains.  It's almost as if the video is not redrawing itself.
    I would think there's some easy solution to this, that this must be a newbie kind of problem, and perhaps I am not phrasing the question right when I search the forums or google the problem, but I've been unable to find the answer on my own, so I appreciate the help in advance.
    Claudia

    More information needed for someone to help... please click below and provide the requested information
    -PPro Information FAQ http://forums.adobe.com/message/4200840
    MOV is a wrapper, what is inside your wrapper?
    Codec & Format information, read both links in reply #1 http://forums.adobe.com/thread/1270588
    Report back with the codec details of your file, use the programs below... A screen shot works well to SHOW people what you are doing
    http://forums.adobe.com/thread/592070?tstart=30 for screen shot instructions
    Free programs to get file information for PC/Mac http://mediaarea.net/en/MediaInfo/Download
    What is your exact brand/model graphics adapter (ATI or nVidia or ???)
    What is your exact graphics adapter driver version?
    Have you gone to the vendor web site to check for a newer driver?
    For Windows, do NOT rely on Windows Update to have current driver information
    -you need to go direct to the vendor web site and check updates for yourself
    ATI Driver Autodetect http://support.amd.com/en-us/download/auto-detect-tool
    nVidia Driver Downloads http://www.nvidia.com/Download/index.aspx?lang=en-us

  • Premiere Pro CC 2014 Startup Crash "Quit Unexpectedly"

    This morning, I take a look at Creative Cloud and there was 2 updates called "Adobe Premiere Pro CC 2014" and "Adobe Photoshop CC 2014". So, I figured, "Sure. Why not?" I updated them. So far, Photoshop still works. After Effects works too. But when I open Premiere Pro CC 2014, I get the pop-up screen, loading stuff and it just quit unexpectedly. I cleaned all of the Adobe products with the Cleaner Tool, uninstalled it, reinstalled it, opened it and it still happens. This is where it stops loading every time and quits. Also, love the artwork.
    After that, it quits unexpectedly. Here is an image of that error.
    I'm using a MacBook Pro. I don't know what to do. I really need help, guys.

    Solution:
    My graphics card did not supported the "Mercury Playback Engine GPU Acceleration (Open CL)". You can change it into "Mercury Playback Engine Software Only" in your Project Settings.
    But this is in the wrong place in my opinion. Why not in "Edit/Preferences"? I could've changed it by myself but I did not find the menu.
    Thanks Michaela from the Adobe Support Chat!

  • Premiere Pro CC 2014 keeps crashing on startup.

    So, I just had a fresh Windows 7 install because for the last 3 days I've been having a problem with Premiere Pro CC 2014 and this was my last resort, even so, it didn't work.
    Everytime I try to start Premiere Pro CC 2014 this happens:
    I know this has been a problem to a lot of people, but I've tried every solution I've seen so far: tried the Premiere Pro CC version, reinstalled Premiere Pro CC 2014, updated Intel Graphic card, disabled Intel Graphic card, renamed Adobe's AppData folder, tried running in compability mode, reinstalled Quicktime, unistalled Quicktime. And I just formatted my computer, so I really don't know what else can I do.
    I'm running Windows 7 Ultimate with a Intel Core i3-4330 CPU @ 3.50GHz, Sapphire Radeon R7 260x, 8GB RAM.
    My Event Viewer logs:
    "Faulting application name: Adobe QT32 Server.exe, version: 8.0.1.21, time stamp: 0x53c7afcc Faulting module name: ImageRenderer.dll, version: 8.0.1.21, time stamp: 0x53c76485 Exception code: 0xc000001d Fault offset: 0x001e5353 Faulting process id: 0x114c Faulting application start time: 0x01cfbfc08ce68291 Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\32\Adobe QT32 Server.exe Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\32\ImageRenderer.dll Report Id: cb4f1cdb-2bb3-11e4-82a4-97822361737e"
    "Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Adobe QT32 Server CC 2014.0 because of this error.
    Program: Adobe QT32 Server CC 2014.0" "Faulting application name: Adobe Premiere Pro.exe, version: 8.0.1.21, time stamp: 0x53c7b17f Faulting module name: ImageRenderer.dll, version: 8.0.1.21, time stamp: 0x53c7659e Exception code: 0xc000001d Fault offset: 0x00000000001f5382 Faulting process id: 0xc70 Faulting application start time: 0x01cfbfc086d5619d Faulting application path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\Adobe Premiere Pro.exe Faulting module path: C:\Program Files\Adobe\Adobe Premiere Pro CC 2014\ImageRenderer.dll Report Id: cb4a3ac9-2bb3-11e4-82a4-97822361737e"
    "Windows cannot access the file  for one of the following reasons: there is a problem with the network connection, the disk that the file is stored on, or the storage drivers installed on this computer; or the disk is missing. Windows closed the program Adobe Premiere Pro CC 2014.0 because of this error. Program: Adobe Premiere Pro CC 2014.0"
    Thank you.

    Hi zerebelo,
    Please install Windows 7 Serivce Pack 1 and that should fix it.
    Let me know if that helped.
    Thanks!!!
    Rameez

  • Can no longer view video in Premiere Pro CC 2014

    I am running a Mac 10.8.5.
    Video files (various formats:mp4, mov, avi, wmv) only play the audio portion of the video when brought into the source monitor or the program monitor. Videos can be made into sequences and exported, but even they don't show video within Premiere -- only hear the audio.
    I have uninstalled Premiere and reinstalled without saving Preferences. Same result.
    Fortunately I have Premiere Adobe Premiere Pro CC (NOT the 2014version) still installed and I have been able to use that one.
    Is this a bug? a system incompatibility? software conflict?
    Thanks

    Hi Anne,
    Regarding the "audio only" in Source and Program Monitor
    What kind of files are these?
    Did you copy the entire folder from the Camera's SD card to your Media Drive?
    Did you ingest the files in Premiere Pro via the Media Browser or File > Import?
    Are your tracks patched to audio and video correctly in the Timeline?
    Regarding the crashing
    Have you tried adding clips to a brand new project?
    Have you tried trashing preference files?
    If none of these things work, please contact our support agents here (ask for the "video queue"): Contact Customer Care
    Thanks,
    Kevin

  • Premiere Pro CC 2014.2 often crashes (Windows)

    Hi...i'm on windows 8.1 and using premiere pro cc 2014.2.... there have been bugs and really need help as this problem has affected my workflow and i even can't get a solution of this.....
    1. There are times my files will be offline and have to reconnect them one by one....and sometimes i have to restart the software or computer to reconnect them back....there are also times when i reconnect them and get a "files are corrupted" error but they can be opened in redcine x...
    2. I also get error when trying to reconnect audio files stating a "header error....
    3. If i mark in and out and try to copy paste from one sequence to another, the computer will not respond and freeze....
    I'm using a asus g750jm, i7 2.4ghz, with 24gb of ram.....
    The sequence that i use to edit these red raw files are just 1024x540....
    Need serious help here...thank you...

    Hi Nazim,
    You´re not alone! It looks like the whole world of Mac users crashes when inside Premiere Pro CC 2014.
    I´ve tried back peddling to early version (8.0) same problem.
    So this is for Kevin (who probably will tell me to stay with the Mac-probelm-users-thread):
    Here is my latest crash report (out of hundred):
    Process:               Adobe Premiere Pro CC 2014 [717]
    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.0.0 (8.0.0)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Adobe Premiere Pro CC 2014 [717]
    User ID:               501
    Date/Time:             2015-04-03 14:55:56.729 +0900
    OS Version:            Mac OS X 10.10.2 (14C1514)
    Report Version:        11
    Anonymous UUID:        3C4BE865-15A1-83C0-2A8F-247384EECB0D
    Time Awake Since Boot: 19000 seconds
    Crashed Thread:        0  Dispatch queue: com.apple.main-thread
    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000000000c0
    VM Regions Near 0xc0:
    -->
        __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   com.apple.CoreText             0x00007fff8c98db95 TLine::~TLine() + 243
    1   com.apple.CoreFoundation       0x00007fff9105ca9e CFRelease + 526
    2   com.apple.HIToolbox           0x00007fff8d5a0944 TCoreTextLineInfo::~TCoreTextLineInfo() + 34
    3   com.apple.HIToolbox           0x00007fff8d5a0913 TLayoutInfo::Clear() + 51
    4   com.apple.HIToolbox           0x00007fff8d5a078f TCoreTextEngine::Invalidate() + 49
    5   com.apple.HIToolbox           0x00007fff8d59d0a8 TCoreTextEngine::Init(void const*, THIThemeTextInfo const*) + 92
    6   com.apple.HIToolbox           0x00007fff8d59cf00 TThemeTextCache::Create(void const*, THIThemeTextInfo const*) + 460
    7   com.apple.HIToolbox           0x00007fff8d59c8bf DataEngine::GetTextDimensions(void const*, double, HIThemeTextInfo*, double*, double*, double*) + 259
    8   com.apple.HIToolbox           0x00007fff8d59c785 HIThemeGetTextDimensions + 185
    9   com.apple.HIToolbox           0x00007fff8d5e124e HIStandardMenuView::MeasureItemTextWidth(__CFString const*, TextLayout*, __CTFont const*) + 122
    10  com.apple.HIToolbox           0x00007fff8d5e0a3f HIStandardMenuView::GetItemWidth(float, TextLayout*, unsigned char*) + 719
    11  com.apple.HIToolbox           0x00007fff8d5dde02 HIStandardMenuView::GetOptimalSizeSelf(CGSize*, float*) + 878
    12  com.apple.HIToolbox           0x00007fff8d5dda1c HIView::SendGetOptimalBounds(CGRect*, float*, CGSize*) + 416
    13  com.apple.HIToolbox           0x00007fff8d5dd84f HIView::GetOptimalSize(CGSize*, float*, CGSize*) + 45
    14  com.apple.HIToolbox           0x00007fff8d5dd755 HandleCalculateMenuSize(OpaqueEventRef*) + 154
    15  com.apple.HIToolbox           0x00007fff8d58213a MenuData::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 358
    16  com.apple.HIToolbox           0x00007fff8d58098c DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1260
    17  com.apple.HIToolbox           0x00007fff8d57fdce SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 386
    18  com.apple.HIToolbox           0x00007fff8d57fc42 SendEventToEventTargetWithOptions + 43
    19  com.apple.HIToolbox           0x00007fff8d5dd4e4 _CalcMenuSizeOnDevice(MenuData*, unsigned short, unsigned int, CGRect const*, unsigned int) + 763
    20  com.apple.HIToolbox           0x00007fff8d5e1bad GetInitialMenuRect(MenuSelectData*, MenuData*, unsigned char, Point, unsigned short, Rect*, unsigned int*, CGPoint*) + 261
    21  com.apple.HIToolbox           0x00007fff8d5f6f32 GetCurrentMenuRect(MenuSelectData*, unsigned int*, CGPoint*) + 110
    22  com.apple.HIToolbox           0x00007fff8d605890 DrawTheMenu(MenuSelectData*, __CFArray**, unsigned char, unsigned char*) + 582
    23  com.apple.HIToolbox           0x00007fff8d60548c MenuChanged(MenuSelectData*, unsigned char, unsigned char) + 356
    24  com.apple.HIToolbox           0x00007fff8d5f1e36 TrackMenuCommon(MenuSelectData&, unsigned char*) + 1211
    25  com.apple.HIToolbox           0x00007fff8d604fb1 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 510
    26  com.apple.HIToolbox           0x00007fff8d604c5e _HandleMenuSelection2 + 446
    27  com.apple.AppKit               0x00007fff9191b8be _NSHandleCarbonMenuEvent + 277
    28  com.apple.AppKit               0x00007fff917b72f0 _DPSNextEvent + 1843
    29  com.apple.AppKit               0x00007fff917b6730 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
    30  com.apple.AppKit               0x00007fff917aa593 -[NSApplication run] + 594
    31  com.adobe.Frontend.framework   0x00000001000c948d FE::MacApplication::RunSelf() + 45
    32  com.adobe.Frontend.framework   0x0000000100047cca FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
    33  com.adobe.Frontend.framework   0x00000001000cad44 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*) + 276
    34  com.adobe.Frontend.framework   0x00000001000d1f25 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
    35  com.adobe.AdobePremierePro     0x00000001000018ac main + 508
    36  com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

  • PPBM7 on Premiere Pro CC 2014 Flies!

    I just downloaded the trial Premiere Pro CC 2014 and as Eric's test of the new i7-4790K data shows the new Premiere Pro CC 2014 really has major improvements in the H.264 and 4K areas.  My first test on this laptop where exporting the timeline in the previous version exported our very complex H.264 timeline took about 355 seconds, it is now almost twice as fast completing the export in 185 seconds.  I do not know if I will be able to continue the PPBM7 testing, that will be up to Adobe.
    P.S.  If anyone else runs that PPBM7 test the statistics file does not identify the correct Premiere version number, or it might throw an error message if you do not have Premiere Pro CC installed.  The new version number of Premiere Pro CC 2014 is "Premiere Version:, 8.0.0.169".  Quite a jump from "Premiere Version:, 7.2.1.4" and a wonderful performance enhancer.

    hello,
    for me : h264 test (ppbm7 /i7-4770k/gtx 770 sli)... 238 sec premiere pro cc 7.2.1.....and 88 sec with premiere pro cc 2014 !!! (mpeg2 test and disk test: no change with cuda, mpeg2 test with mercury software a little slower)

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

  • Exporting to Media Encoder crashes Premiere Pro CC 2014

    Greetings,
    I am experiencing a problem with premiere off and on. Right now it is an on problem. When I am exporting from Premiere Pro CC (and CC 2014) it will intermittently crash Premiere. I have tried this with several different audio and video formats (AVI [Lagarith and uncompressed], WAV, H.264, MPG2, AAC, etc). At the moment, every time I go to export to queue it locks up and hangs on the "Preparing data for export..." Media Encoder Launches and then it just freezes. I get "Problem Even Name: AppHangB1" over and over. Sometimes a full restart will fix this temporarily and sometimes it goes away for a long while. I managed to get a few sequences exported and then it just kept freezing on every PP CC restart.
    Here are my system specs:
    Premiere Pro CC (up to date)
    Win 7 64bit (up to date)
    i7 970
    24GB Ram
    NVIDIA 470GTX (driver up to date)
    3 x 1.5TB internal
    4TB internal
    3TB internal
    12TB RAID 5 via USB 3.0
    USB 2.0 and 3.0 drives
    FireWire audio device (M-AUDIO FireWire1814)... although, I am not using it for playback. It is connected.
    Footage is from C100 H.264 .MTS, H.264.mov from 7D, and H.264 .MOV from iPhone.
    All stock video plugins with a few third party audio plugs.
    This problem happens with and without third party plugs, but it happens that this project uses them.
    I have chatted with Adobe help twice about the matter and nothing has come of it. Log out, log in = same. Restart = same (sometimes), create new user account = same, and so on. The only thing I haven't done is completely re-install premiere, which seems a bit overkill. One of the reps said he would get back to me in a few days after he watched the issue via screen share. Never heard back.
    I get the sense that this has something to do with PProHeadless.exe not launching or not running properly. When the crash happens on a fresh restart of PP CC 2014 PProHeadless is not running. I can start PProHeadless and it will send sequence to media encoder. When I try to export another sequence from the same project it crashes and I see another instance of PProHeadless launched.
    Also, once the projects are exported to Media Encoder, I can encode them to any format with no problem. The problem is getting the sequences there!
    Is there anything that I am overlooking here?
    Thanks for the help!

    Hi
    Premiere pro cc 2014  8.0.1 (21) build
    Encoder CC 2014 8.0.1.48
    I use CC for Teams so it updates all the time.
    Again when I tried to use it today by letting premiere open it by sending an output into Queue it crashed both Encoder and Premiere.
    In order to shut down Encoder and Premiere I had to go into Task Manager and "End Process Tree" on everything adobe I could find because just ending Encoder did not work it would not close. I remembered that years ago when Premiere would crash we had to end a photoshop process. I found photoshop open even though it was not "alive" on my task bar. I had used it yesterday but had closed it. I also had to close dynamiclinkmanager.exe *32 as well as one of the three Adobe CDF Helper.exe*32. They popped back on but Encode closed and then I got a message that Premiere needed to close and did when I clicked the button to let it close.
    After all this I re-opened Encoder by itself and checked the Preferences finding that Import Sequences Natively option was again checked.
    By the way for me, "Launch AME manually, then drag the sequence from PPro's Project panel to AME's Queue (or to a preset in the Preset Browser). That uses a different code path than the File>Export>Media workflow." won't work most of the time because I do live events of panel interviews that may run 2 or more hours. I need to break them down to chapters for the web
    Also I know this isn't part of this problem but I and many others would still love dynamiclink to work to Encore because the DVD is not dead yet. The current work path is a drag.
    Looks like some programers and engineers have some work to do.
    Thanks
    Dennis
    My computer:
    Self built PC windows 7 Professional 64 bit Build 7601 SP 1 I use auto update so it is up to date.
    ASUS P6x58D Premium Motherboard
    Intel (R) Core i7 930 @ 2.80 Ghz
    Installed Memory  12 GB
    NVIDIA GeForce 9500 GT
    NVIDIA GeForce GTX 580
    2 Apple Monitors and a HP full HD Monitor
    With a BlackMagic Intensity Pro Capture Card

Maybe you are looking for