CS5 Media Encoder fails to start.

Hi All,
Two days ago whilst encoding an AVI file my Display driver failed then recovered halting AME. l needed to reboot to start again, and the Display driver failed again but recovered. I have since been able to encode the file but fear the graphics card may be on the way out. My problem now is l want to encode another AVI but AME fails to start after the logo apears a message says that AME  has stopped working.  I seem to remember a forum member in PPro giving advise on deleting the Pref file as it may have been corrupted, but l can't find any reference to it anywhere. I'm working with Windows 7 64 with Adobe Production Premium. l hope it's just a matter of deleting these files. Can any one help please. All updates have been installed to these programs.
Thank you
Simon Allan

Here's the page about preferences, which describes how to reset them.
You can also reset preferences by deleting the preferences files.
Preferences are stored in files in the following locations:
(Mac OS) <drive>/Users/<username>/Library/Preferences/Adobe/
(Windows) <drive>\Users\<username>\AppData\Roaming\Adobe\

Similar Messages

  • Adobe Media Encoder Fails to start

    I recently upgraded to CS5, fully 64-bit, but because a lot of my plugins and etc are still 32-bit, I installed the 32-bit support so I could have premiere & after effects CS4 and CS5 on the same system. But this seems to have created a but with media encoder, When I do a render que in media encoder, it doesn't start at all, just hangs there saying contacting dynamic link manager. The only way to render out of Premiere CS5 is to use the export feature within it. I also get a problem with whenever I say export media, it says there is an update for the media encoder, when there is one for CS4 media encoder not CS5 media encoder. And all the processmanagers and mediaimporter are running in 32-bit for some reason.

    I recommend getting the suite.  Mixing and matching CS5 and CS4 not a good idea.  I took the plunge and so far I don't regret it even though I have run into some bugs that are slowly getting fixed.  CS4 engine not the same as CS5.
    Rob

  • Why does Adobe Media Encoder fail to export Quicktime Files?

    I'm using Adobe Media Encoder CC 2014 on a Windows 7 Pro 64 bit PC.
    While exporting the Quicktime variant of H.264 for ATSC television broadcast files, Adobe Media Encoder fails.  Non-Quicktime H.264's render correctly, but some television stations require quicktime.
    Troubleshooting reveals the problem only occurs when attempting to make a 1920x1080 H.264 QuickTime file.
    Using the same original file (1920x1080), Adobe Media Encoder WILL export a 720x480/486 H.264 MOV file.
    More interesting still, it will ALSO export at 1280x720.
    Testing this information to it's limits, I found that the cutoff for a successful render is between a frame size of 1610x906 and 1609x905.
    Useless, random sizes, I know... but that's the breaking point for Adobe Media Encoder CS6 (6.0.3.1 to be precise) and H.264 Quicktime files.
    Others are having a similar problem:
    http://forums.creativecow.net/thread/3/934721#953485
    This information did not correct the problem:
    http://helpx.adobe.com/premiere-pro/kb/error-compiling-movie-warning-or.html
    Any help or ideas are greatly appreciated.
    OS:  Windows 7 Professional 64-bit SP1
    CPU: 41.6GHz (dual octo-core Intel Xeon E5-2670 @ 2.60GHz)
    RAM: 64GB
    GPU: NVIDIA Quadro 5000 v334.95 (2.5Gb GDDR5 RAM)
    VID: Blackmagic Design DeckLink HD Extreme 3D+/Desktop Video v10.1.1
    DRV: Facilis TerraBlock 16TB RAID/ATTO ExpressSAS R680 v2.19
    NLE: Adobe Premiere Pro CC 2014
    James Brady
    Senior Editor
    Results Video, Inc.
    El Paso, Texas
    http://www.resultsvideo.com

    I'm trying to make a file with the extension ".MOV" using AME's "HD 1080i 29.97, H.264, AAC 48kHz" preset.  AME fails every time with the following message:
    "Encoding Failed
    Export Error
    Error compiling movie.
    Unknown error."
    Any other file extension (MP4, M4V, etc.) renders fine.  The issue seems only to happen when attempting to make an MOV file.  It doesn't seem to matter whether I use AME's built-in preset, or customize my own render settings--the problem always happens with any MOV larger than the size I mentioned above.
    All of this used to work just fine on the same machine 2 years back with Adobe CS5, previous version of windows and QuicTime.  I've been all through the Adobe and Windows possibilities, so I'm grabbing at straws here with QuickTime maybe having something to do with it.
    Interesting.
    Would you happen to know if Adobe has made any changes to its manner of muxing long-address MPEG-4 AVC data to the MOV file container? Since the MP4 and M4V files encode properly, have you tried opening these files in a media player and simply using the "Save As..." option to move the date to an MOV file container without transcoding audio or video data? I.e., is there any obvious relationship between the size of the MOV file encode (less than/greater than 4 GB) as a function of the resolution "break point" previously discovered?

  • Media Encoder Fails to Launch (Mac)

    I sent three sequences to media encoder (5.5) from Premiere then looked for the Media Encoder window to start the batch (as usual) and it failed to come up.    I quit Premiere Pro, still no Media Encoder Window.
    Rebooted the Mac and tried to launch Media Encoder from the Dock.   It loads the flash screen, tells me about loading the filters then appears to access something in the project folder (the path is too long for me to see what), hides the flash screen and ..... nothing.   Media Encoder is not responding.
    I've tried reboot / restart several times and can't get past this.
    How can I delete what ever job is keeping it from starting up?

    Fixed it.  For those searching in the future, hold down CMD+ALT_Shift while clicking on Media Encoder and it will delete preferences and allow Media Encoder to start up.   Phew!

  • 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

  • Have CS4 use CS5 Media Encoder

    I have CS5 Master Collection installed, but because I'm running XP x64 I'm having to continue using Premiere CS4. That's all well and good, but is there a way for me to set preferences so that when I export from Premiere CS4 it uses the CS5 Media Encoder rather than the CS4 one which it currently defaults to?

    You're implying that by my saying "Shame" I am criticising Adobe. Absolutely not.
    That's not my implication at all. As a matter of fact, I encourage criticizing Adobe for things that don't work as they should--most of my own posts are usually in this vein. However, this is not a case of something not working as it should, which is what I was pointing out: you can't be disappointed (or at least you shouldn't) in something that was never said to work in the first place. That was my point.
    Anyway, glad you're considering Windows 7. I think that, after an adjustment period (particularly since it appears you skipped Vista--not a bad idea), you'll find Win7 to be a pretty great advancement for the Windows platform. As an added benefit, you'll get to play with all the toys we get to play with

  • Media Encoder failing with AVCHD

    There's been a few discussions about AVCHD but I haven't been able to find any that were resolved. In using AVCHD footage from my Canon C100 I've found that media encoder fails if CUDA hardware acceleration is enabled for the project. Having acceleration disabled slows down my system a lot so I wondered if anybody found a solution?
    I'm using 6.2 on the Mac with a Quadro 4000 GPU.

    Hi Ann
    Good point, I assumed it was the AVCHD footage as I've not had a problem exporting with MPE turned on until using this footage but I just tested some Canon MXF footage from the C300 and AME failed with that too.

  • Adobe Media Encoder fails on launch

    Every time I go to render media, when Adobe Media Encoder launches, the file fails. I get a non-descript dialog that says "Installation error: Please ensure this product has been installed properly." This happens immediately after I start the AME queue and it begins to load the .prproj file (which is already open in Premiere Pro, since that's where I exported from in the first place).
    I ran Adobe Updater and got the newest version of everything, except for the latest CS4 "Services Update" which fails to install properly. I've tried that update numerous times (after restart, after repairing permissions) and it seems to fail every time. I didn't think this was relevant but thought I'd mention it anyway.
    I'm on a Quad-Core Xenon Intel 2x2.5 Ghz tower, with 12GB RAM and 78+ GB free disk space. I'm trying to render a portion of a project, this segment is about a min and a half long. I'm on Mac OS 10.6.7 (latest update), using Premiere Pro CS4.2.1 (003 MC: 166418) and Adobe Media Encoder 4.2.0.006.
    Any help is greatly appreciated!

    If you have done a complete reinstall, and ran the Adobe CleanScript CS5 (that is the latest), then a Repair Install should not be needed - it would do nothing.
    For info, to do a Repair Install, one would insert the installation disc. When the installer module has loaded, it will survey one's system. If it finds the Adobe program(s), it will ask if you wish to Uninstall, or Repair Install. When one chooses Repair Install, it surveys the system again, for that program, and will replace, or correct any issues. This is usually MUCH faster, than doing an uninstall/reinstall.
    Good luck, and not sure what else could be the cause.
    Hunt

  • Premiere Pro CS5 - Media Encoder Crash when Exporting to MPEG-2

    System:
    Core i7 920 @ 3.8 Ghz
    Gigabyte X58A-UD3R
    12GB DDR3 1600
    External Sound Card - M-Audio ProFire 610
    OS Drive - 2x300GB WD Raptors - Raid 0
    Project Drives - 3x300 WD Raptor - Raid 0
    Video Card - Geforce GTX 285 1GB
    Adobe Premiere Pro CS5 and Media Encoder CS5 continually crashes or hangs every time I try to export to MPEG-2.  I can successfully render to every other codec without any issue, but need the MPEG-2 for an Adobe Encore Project.
    The project is approximately 38 minutes long and contains AVI and MP4 files, all of which were ripped from DVDs as I'm producing a reel for a producer who provided his DVDs for me to rip and use as content.
    Possible issues:
    1.   Currently have Magic DVD Ripper and DVD Fab installed (codec conflicts?)
    2.   Originally ripped the DVDs at 630x360 (my mistake - hadn't really worked with a DVD ripper before and was the largest avi pre-set) and I'm exporting to MPEG-2 standard 720x480 Widescreen)  (I know I should've just ripped them as the original lossless MPEG-2 files - I'm a tool)
    2.   Blank space in the timline (there are a number of these)
    I would like to get some input before I try to export to MPEG-2 again as I blew a capacitor on my old mother board (Gigabyte x58-ud3r) after I had gotten my computer to start rendering a MPEG-2 after about 50 tries to export/launch media encoder set on MPEG-2.  I just installed my new motherboard to replace it.  Clearly MPEG-2 taxes the system more so than any other codec (from what I can tell).  However, I thought the issue with the blank space/no media in the timeline was fixed with CS5.  I saw in a previous post that someone thought that ffdshow was conflicting with AME.  I don't have ffdshow, but I believe that's a ripper program like Magic and DVDFab.

    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.

  • Adobe Media Encoder Fail - need help please

    I keep getting a failed error when trying to use Adobe Media Encoder. 
    I open up my premiere project and select the comp I want.  I switch the format to Quicktime, select h.264 from preset.  Hit the start button and I get the failed sound/icon.
    2 questions:
    1. My comp is 1920x1080 but when I go in it automatically has it as 720... why is it not recognizing the comp size?
    2. Is there a way to fix this error?  It seems to export occassionally to my C drive (which is not raid) but it fails to my F drive (Raid 10).  But usually if I export as a wmv or something smaller it exports fine to F.

    Sorry it took so long to get back to you I had to go out of town.  Error message doesn't say anything to me... maybe to you.  I'm not really sure what to set for "Field Type" so I just leave it at Lower.  Not sure if I should set it to higher or progressive instead.
    - Source File: F:\master_project\Fetterman\Premiere\Fetterman_Actos.prproj
    - Output File: F:\master_project\Fetterman\Premiere\Fetterman-Actos.mov
    - Preset Used: Custom
    - Video: 1920x1080, 29.97 fps, Lower, Quality 100
    - Audio: 48000 Hz, Stereo, 16 bit
    - Bitrate: H.264
    - Encoding Time: 00:00:00
    03/15/2012 04:05:21 PM : Encoding Failed

  • CS6-Media Encoder Fails on long (1hr +) H.264 render

    Windows 7 - 64 Bit. 8 GBs RAM
    Adobe Pr and other programs on C: internal Plenty of hard disk space left 300+GBs
    External high speed 7200 RPM RAID 1 where the media is stored.
    External high speed 7200 RPM Non RAID drive for rendering to be written to.
    Both drives are eSata.
    CS6 Pr and Media Encoder 6.0.0.382 (OP update: It appears that has been an update to this version, I am going to download the updates and see if that fixes this.)
    FOLLOW UP: It appears that the update did fix the problem. I have multiple workstations and was under the impression I had updated them all. I have not fully tested this yet, but for now, I consider it fixed.
    Footage is a single capture of a lecture. 1 hr. 20 minutes.
    Shot on Canon xf105 in MXF format at 1280x720 23.976p (US)
    Footage goes together fine (many multiple file clips 'chained' or butted up against one another, as is done when you shoot a continuous take)
    The footage plays fine in Pr in final form for export.
    No special effects. one dissolve (intro title slide to lecture)
    Reproduceable problem:
    i export to Media Encoder.
    I choose H.264 and Vimeo Wide Screen SD 23.976
    The file exports about 2/3rds of the way, not the same place each time, and fails with no definitive error message. The log shows, "Export Error: Error compiling movie. Unknown error."
    Rendered file to external drive (have more than one, have tried it on two, with same results)
    All drives have plenty of disk space on them.
    I tried cleaning the Media Encoder Media Cache. Same result.
    I tried moving the cache files to an almost empty external disk. No change.
    I broke the video into a 10 minute segment, it rendered just fine with the same settings.
    This seems to be a bug in Media Encoder. Is there a fix for this? A workaround? My client would like a single long file of the presentation.
    Could the 8 GBs of RAM be an issue? Not sure why it would. Or is this a known bug for Media Encoder?
    I also had a second job today, similar in that I needed to take 6 multiple takes of the same person, drop them onto a timeline and render it to Vimeo for them to review. same issue. Got 13'05" into the compile and it failed.  So something is odd. I have compiled much longer footage before, that was done with this camera.

    If you have done a complete reinstall, and ran the Adobe CleanScript CS5 (that is the latest), then a Repair Install should not be needed - it would do nothing.
    For info, to do a Repair Install, one would insert the installation disc. When the installer module has loaded, it will survey one's system. If it finds the Adobe program(s), it will ask if you wish to Uninstall, or Repair Install. When one chooses Repair Install, it surveys the system again, for that program, and will replace, or correct any issues. This is usually MUCH faster, than doing an uninstall/reinstall.
    Good luck, and not sure what else could be the cause.
    Hunt

  • Encore CS5/Media Encoder CS5 freeze when transcoding

    I'm trying to encode avi files for DVD. I have tried building my project in Encore & doing "build disc". Note: I am creating a Disc image, not actually burning any disc. It starts by transcoding; it gets through the video pass, and when it gets to the very end of the audio pass, it freezes. I have tried this 4-5 times with the same result. Oddly enough, I also had it work twice. Go figure.
    Since I had 3-4 files to transcode for DVDs, I thought I might be able to save time (and try another approach) by using the Adobe Media Encoder. Same deal. It got about 99% done with the first file and FROZE.
    What I've done:
    1. Verified no DLA is running (at least, no Roxio or Nero software)
    2. Verified the PhHlap64.dll is the latest (3.0.90.2 or whatever it's supposed to be)
    3. Installed latest Windows 7 (64bit) and CS5 updates
    4. tried different user accounts (both administrator accounts)
    Here is what we do have installed on this machine:
    Firefly
    MediaShout 4.5
    Quicktime 7.6.6
    Symantec Endpoint Protection 11 (mr5)
    Itunes
    That's all I can really think of. I just ran the apple updater and see there is a new (7.6.8) verison of quicktime. I'll update that and see if it makes a difference. Any and all help is appreciated!
    Computer Specs:
    Q9300 Quad core
    4GB Ram
    1GB HD4670
    320GB+1TB HDDs

    Thomas Nord wrote:
    Update: We have discovered an issue where you can get this behavior if the source is a Premeire Pro sequence whose sample rate doesn't match that of the clips in that sequence. The solution is to match the sample rate of your sequence to that of your clips. Please let me know if this does not resolve your issue.
    Thanks,
    Tom
    I had some 96/16 audio from an H4n recorder. AME just sat there. Also had the same problem exporting directly from PPro without using AME. Just sat there, no error, just nothing.
    Changed the final sequence samples to 96kHz sampling and problem solved. That's a real bummer, since Adobe definitely pushes the sort of "edit anything" mantra a lot, and having to tailor sequence settings to a recently added audio clip is a step in the wrong direction. Glad to know it CAN be fixed, since these renders need to happen, but need that one patched up.

  • Adobe Media Encoder Fails Export from Premiere

    AME will not start the render qeue. I have tried Clip notes and different output types. I have embedded After Effects comps in my Premiere timeline. Could that be a cause? This is my first time working with Premiere and AE together.
    Error log below:
    - Source File: C:\Users\Alex\AppData\Local\Temp\Cosmetics Working_2.prproj
    - Output File: F:\Premiere Projects\20090803 Shapiro Cosmetics\From Prem Timeline\Working Copy.pdf
    - Preset Used: Custom
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 18:16:01
    9/17/2009 3:37:39 PM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    - Source File: C:\Users\Alex\AppData\Local\Temp\Cosmetics Working_3.prproj
    - Output File: F:\Premiere Projects\20090803 Shapiro Cosmetics\From Prem Timeline\New Pierre Video.avi
    - Preset Used: NTSC DV
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 18:19:04
    9/17/2009 3:40:43 PM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    - Source File: C:\Users\Alex\AppData\Local\Temp\Cosmetics Working_4.prproj
    - Output File: F:\Premiere Projects\20090803 Shapiro Cosmetics\From Prem Timeline\Working Copy.wmv
    - Preset Used: NTSC Source to Download 512kbps
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 18:22:58
    9/17/2009 3:44:37 PM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    - Source File: C:\Users\Alex\AppData\Local\Temp\Cosmetics Working_5.prproj
    - Output File: F:\Premiere Projects\20090803 Shapiro Cosmetics\From Prem Timeline\Working Copy.avi
    - Preset Used: NTSC DV
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 18:26:09
    9/17/2009 3:47:48 PM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    - Source File: C:\Users\Alex\AppData\Local\Temp\Cosmetics Working_6.prproj
    - Output File: F:\Premiere Projects\20090803 Shapiro Cosmetics\From Prem Timeline\Working Copy.avi
    - Preset Used: Custom
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 18:34:14
    9/17/2009 3:55:52 PM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    - Source File: C:\Users\Alex\AppData\Local\Temp\Cosmetics Working_7.prproj
    - Output File: F:\Premiere Projects\20090803 Shapiro Cosmetics\From Prem Timeline\Working Copy.pdf
    - Preset Used: NTSC Source to 512kbps
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 18:36:22
    9/17/2009 3:58:00 PM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.

    Hello, this is terrible problem, which i found in CS 6 softwares ...
    solution i found only working, is uninstall and reinstall full package.. but it is not all,
    you need to do BRAND NEW admin account in windows, and install it there.
    that means, i could not export after repair from encoder in my original account never more (!!)   .. this is really terrible way how to repair this issue, because :
    1.by reinstalling of software, client WASTE HIS TIME
    2.by necessity to begin work in another windows profile you again WASTE YOUR TIME because of learning and migrating all other profile modifications, which i see really unaccpetable. Adobe means, this solution of repair is ok, and they did not do till today any steps of creating some "clever" solution.
    I ask everybody, who will meet this issue in future, guys, please, complain about this situation, give "BUG Report" to them, and write "feature request" to them , in the way of creating some repair tool, which check actual  "broken" connections between encoder and premiere, which refuses to "take material" from it and encode, and REPAIR it automatically..  
       I am not IT, but ..does it seems so hard to create this ? Adobe IT developers should know their systems, and should create such utility tool really easy.
    Steps to reproduce bug:
    1. i export anything by button "queue" from premiere to Encoder
    2. Encoder will start encoding
    3. Encoder does not show the window of media encoding (down left )
    Results: sound of sheep occur,
    in encoding error file is this reason of canceling the encoding :
    01/02/2014 10:10:48 AM : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    History of this problem and detailed description, HOW i did "repair" this. With wasting of app 2,5 days of my working time :
    1. after repairing "error 5" problem , i solved it by reinstalling the suite from the new admin user profile (profile B) . 
    I continued my work on my normal working windows profile . (profile A)
    Every cooperation (AE+Pr, export media via "queue" to Encoder) was working fine . . .
    2. suddenly it stop working (without knowing any possible reason - i did not do installations )
    and showed in error export log file :
    "Could not read from the source. Please check if it has moved or been deleted."
    3.repair via procedure(procedure "a"):
    i did this procedure on the profile B (profile from last time installation of repairing problem error 5)
    I did these steps :
    a-uninstall master coll suite
    b-i used Adobe cleaner tool (remove ALL)
    c-removed raw directories in locations
    •C:\Program Files\Adobe
    •C:\Program Files(x86)\Adobe
    •C:\Program Files\Common Files\Adobe
    •C:\Program Files(x86)\Common Files\Adobe
    •C:\ProgramData\Adobe
    d-removed these links from registry file
    •HKEY_LOCAL_MACHINE\SOFTWARE\Adobe
    •HKEY_CURRENT_USER\Software\Adobe
    •HKEY_LOCAL_MACH INE\SOFTWARE\Wow6432Node\Adobe
    •HKEY_CURRENT_USER \Software\Wow6432Node\Adobe
    e-restarted the PC
    f- newly installed the Master Coll CS6
    g-update the software
    result of repair of "3" : problem still exists
    4.Ok i find out after coordination with support, it should have been created  ANOTHER NEW admin account.
    4a:so i did the same procedure (uninstalling) in profile B
    4b: and then i created brand new admin profile (profile C)for INSTALLATION of software
    4c: restarted the pc (and did not updated it yet)
    result :
    ==exporting of any sequence/raw/AE link video material from premiere via "queue" (Encoder) (profile C) : export WORKS
    ==exporting of any sequence/raw/AE link video material from premiere via "queue" (Encoder) (profile B) : export WORKS
    ==exporting of any sequence/raw/AE link video material from premiere via "queue" (Encoder) (profile A) : export DOES NOT WORK ! ! !
    (in profile A, is possible to export some raw video material in encoder which is imported to it via "drag and drop)
    problem i see:, i have my basic profile A, which i am interested to work, because of all my directory modifications are in there..
    this issue should be some "broken" connections between encoder and premiere, which refuses to "take material" from it and encode.
    what i expect :
    to get from Adobe some repair tool, which automatically checks these connections and repair if necessary, without necessity of founding the new profile and reinstallation of whole software.. this is madness !
    what i do NOT expect from Adobe:
    to get from Adobe advice of kind : you have to reinstall full software in new admin profile. sorry , we do not know the solution, because we do not know, how do behave our software.

  • Media Encoder CC not starting

    Windows7 64 bit
    Media Encoder CC (7.0.1)
    AME worked a while. I exported a couple of jobs to it's queue. All good. Tried to cancel the jobs and it seemed to hang. Had to kill the application from task manager.
    Since then AME will not run. It crashes on startup. No splash screen.. nothing. Appears briefly in task manager then dissapears.
    I have deleted all files from C:\Users\login\AppData\Roaming\Adobe\Adobe Media Encoder\7.0
    Have reinstalled PremierProCC after uninstalling and using the cleanup tool.
    Still no luck. Is there a queue file anywhere that should be deleted?  A registry entry maybe?

    Tried everything....Reinstalled...twice..
    Cleaned everything using REVO uninstaller..
    This Frustration made me Format my PC too..and made a fresh install
    no Response yet
    1. Media Encoder worked fine since last 4 weeks..
    2. suddenly..today it isn't working fine.
    3. It Just starts for the first time and closes.
    Please help me to resolve this Issue..
    I almost..cant render anything..:(
    AME i need u badly..:(

  • Exporting in Adobe Media Encoder fails in CS4 after CS3 is removed.

    There's an issue with Adobe Media Encoder in CS4 where encoding will fail after CS3 is uninstalled.
    If you never had CS3 installed on your machine - no problem.
    If you never had CS3 and CS4 installed at the same time - no problem.
    If you had CS3 and CS4 installed concurrently, then uninstalled CS3 - Houston, you have a problem.
    You will need to uninstall CS4 and then reinstall CS4.
    The error message is:
    Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.
    One more thing I forgot to mention, this is a Win-only issue.

    >Does anyone understand this?
    Simple:
    1. Open a Windows Explorer window and navigate to the folder that contains "dynamiclinkmanager.exe"
    2. Open a
    second Windows Explorer window and navigate to the folder that contains "Premiere.exe"
    3. Arrange the windows side by side.
    4. Right-click on "Premiere.exe" and drag to the first explorer window, targeting between the files so as to avoid any specific file.
    5. Release the right-hand mouse button.
    6. Select "create shortcut here" from the pop-up menu.
    Cheers
    Eddie
    PremiereProPedia   (
    RSS feed)
    - Over 300 frequently answered questions
    - Over 250 free tutorials
    - Maintained by editors like
    you
    Forum FAQ

Maybe you are looking for