Core i7 system locking up in Adobe Media Encoder

Here's my system:
Core i7 920
6GB Corsair XMS3 (Running at 1600)
Asus P6T V2
2x PNY 9800GTX+
Vista Ultimate with CS4
Any time I try to encode somthing in AME, no matter the format, source, or application using it, my system will completely lock up. It doesn't even give me a blue screen, just a complete system halt. It did work one time (just once) when I encoded a short flash video. I know my system is stable, temps are fine and it still locks up when I bring the RAM down to normal speeds. I have the latest adobe and windows updates and latest drivers for my hardware. Any ideas would be appreciated.

Some Encore notes... including a critical update to the Roxio component
Encore Roxio component problem http://forums.adobe.com/thread/400484?tstart=0
More on Encore and Roxio http://forums.adobe.com/thread/528582?tstart=0 or direct to
http://kb.roxio.com/search.aspx?URL=/content/kb/General%20Information/000070GN&PARAMS
Long File Names Cause Crashing http://forums.adobe.com/thread/588273
Encore Tutorial http://www.precomposed.com/blog/2009/05/encore-tutorial/

Similar Messages

  • Adobe Media Encoder crashing system

    I  am experiencing crashes whenever I use Adobe Media Encoder for a file 2  min. or more.  It seems no matter what format I save in flv, quicktime,  etc. or size – NTSC, Custom, 1080p the same results..  Please advise as  I cannot use program until fixing this problem.
    I am using Premiere CS4 on Windows Vista, quad core 3.2 AMD processor, 16 gb RAM
    Don
    Also; earlier this year when I had this similar problem, I  needed to upgrade my power supply and it completely fixed the problem.   Since it has started again, I;ve upgraded the power supply  substantially, but this time no change.

    When a system crashes, there is often a breadcrumb trail left behind. This ARTICLE will give you tips on finding clues in that trail.
    This ARTICLE will give you tips on setting up your computer for an editing session.
    Good luck, and hope that helps,
    Hunt

  • Adobe MEdia Encoder Crashes with big files inputed

    Hello,
    There isn't a forum for the Adobe Media Encoder, so I thought this would be a good spot. I am an after effects and Premiere user who likes the idea Adobe seems to have of using the media encoder to cover all my encoding needs.
    My typical workflow, especially since these days I'm doing more shorter form animations, is to render out to a Quicktime Animation codec file as my main archive file. From there, output all the various different web versions, flv, etc from that core archive file. Since my projects usually aren't running more than 5 minutes, this leaves me with a nice 3 - 7gig file.
    Problem: I'm running CS4 and the media encoder crashes when I input files that are in this file size range. The program locks up when I push start que, and then eventually crashes. Works fine with smaller size files that are about under a gig.
    I can run a render out of after effects, which seems to be more stable. But I'd love to be able to use this great new tool.
    Here's my machine specs if it helps:
    PC
    Intel Quad Core Q9550 @ 2.83 ghz
    4gB RAM
    Windows Vista 64 bit ultimate
    All updates current for CS4 apps as of 01/30/08
    Running Adobe Media Encoder V 4.01.078
    Hard drives are nothing special. 7200 rpm western digital internal and external. I've tried all sorts of hard drive configurations, where the input is coming from, where it's going, etc. No difference.
    I have been experimenting with using Lossless AVI's as my "uncompressed" archive file. Works well, but same crashing with the Media Encoder.
    Also tried experimenting with frame size alterations during encoding, no difference there. Also, whatever the output codec is, be it FLV, H264, etc. no difference.
    Anyone have any thoughts or have experienced similar issues? I hope all my MAC friends aren't right, seems like all my attempts to streamline my workflow with this CS4 and beefy PC combo are crashing and burning.
    Anyone else feeling this pain, or have recommendations?
    Thanks,

    Thomas, thanks for your suggestions on Vista optimization. That Sheer Codec looks nice, but hard justify the cost when I've been working for years with essentially uncompressed codecs that work well. Will play more though to see if the cost would actually pay off in the long run though.
    In general I made a decision that it was too early to throw in the towel on my old uncompressed codecs. The Quicktime animation codec has always been for me the safest, most universally accepted, and most reliable "uncompressed" codec. It's always worked in the past, not gonna give up just cuz media Encoder CS4 has troubles.
    Mylenium, thanks for the reminder about the silly platform wars. I've always felt the same as you, but when I'm stressing sometimes the silly propaganda can get to me. Makes me forget that no matter what system ya got, it never works perfect!
    Here's an update. I have trying my best to learn more about the bug and have come to some interesting realizations. The AME does work with larger files, just not the larger files that I had been using at the current moment. Older files of mine as big as 20GB can be inputed into AME with fine results.
    This being said, it scratches out most of the RAM overload thoughts with AME.
    The difference with my current files that were causing AME crashes: larger than a few GB, came from AE, had the 1.21 pixel aspect ratio metadata.
    When I re-interpreted the file in AE into a square pixel aspect ratio, exported it, it was then successfully inputed into AME.
    I have read just now that there were changes in After Effects widescreen pixel aspect ratio interpretation in CS4. Can this change be causing problems in my AME. Not positive, but I'm now thinking after many days of testing that the bug could have its roots somewhere in this ball park.
    If anyone from Adobe is reading this, I would love any ideas you might have on this issue. In general, there is really no support for the Adobe Media Encoder itself. This is not good, considering how it is so necessary for AE and Premiere users like myself.
    Thanks,

  • Maximum file size with Adobe Media Encoder?

    I seem to be having a problem when converting files in AME.
    I'm converting .m2v files into quicktimes files, using the DVCPRO HD 1080i50 codec. No sound is being exported with the audio.
    Dimensions are 1440 x 1080, frame rate, field type and aspect are locked at 25, Upper First and HD Anamorphic 1080 (1.333) respectivly.
    I've encoded about eleven other files of the same type without fail, however this certain file is at 1.7gig compared, where as every other file I wanted to encode is under 1gig.
    I'm using an Asus N53SV with 16gig of ram, so I'm sure my laptop can handle whatever is thrown at it. I'm using a 64bit operating system on Windows 7 home premium Service pack one.
    Processor: Intel Core i7 - 2630QM CPU @ 2.00Ghz
    RAM Memory: 16gig
    Graphics card: Nvidia Geforce FT 540M
    Progam: Adobe Media Encoder CS5.5 ver. 5.5.1.12
    The error log reads:
    - Source File: G:\Digital Postcard\To convert\Untitled-6.m2v
    - Output File: G:\Digital Postcard\To convert\Untitled-6_2.mov
    - Preset Used: Custom
    - Video: 1440x1080, 25 fps, Upper, Quality 100
    - Audio:
    - Bitrate: DVCPRO HD 1080i50
    - Encoding Time: 00:09:50
    04/19/2012 03:19:30 AM : Encoding Failed
    File size that I want to encode is 1.7gig
    I'm assuming either the file is corrupt or I don't have sufficient specs to handle the large file.
    Any help will be great,
    Thanks.

    There are no file size limits to the software beyond what would be imposed by the operating system itself and the file format of the drive.
    So...assuming you have enough drive space, something else is going on.

  • Adobe Media Encoder error when encoding: winfile.cpp-759

    Mods: Please move this to the appropriate thread wasn't sure to move it to Premiere or Flash
    I receive this error when trying to encode AVI to H.264 using Adobe Media Encoder CS5 (64bit):
    When searching through the forums, several suggestions for CS4 and current releases that I have tried are:
    clearing the media cache through AME, and the folder location in %APPDATA%\Adobe\Common\
    installing K-Lite Codec pack
    changing the media cache files folder to a separate disk entirely
    updating to the latest version (at the time of post ver 5.0.1.0)
    uninstalling and re-installing AME (as an error might have occurred during updates)
    verifying that the CPU has SSE support and is enabled
    I expanded my search to google which gave similar errors (winfile.cpp-754, winfile.cpp-758, etc.) and a few responses were uninstalling any Nero products (don't have any burning programs on this computer - unless you count Windows)
    The system that I have is:
    MS Windows 7 64-bit
    Intel Core 2 Quad Q6600 @ 2.40GHz
    2x 1.0GB Dual-Channel DDR2 @ 800MHz
    512MB GeForce 9600 GHz
    2x 250GB HDD Mirrored
    External USB 500GB HDD
    Any ideas as to what the cause of this is?
    LK.

    The information about installing codecs packs is true. It usually does more damage to your codecs already present with software already installed on your computer, and the registry settings even after removing it. That is why it is in good practice to do full image back ups monthy, saving the latest 3 for when I utilize last resort methods such as codec packs.
    Adobe CS5 software has been working fine on my computer ever since its installation July. I forgot to mention that I have successfully used Premiere Pro CS5 for editing a dozen files ranging from SD small res to HD 1080i. This also includes just using AME CS5 itself for transcoding files for supported playback on different devices. I notice a greater difference in speed when using a more up to date machine that uses a GTX 285 card for GPU playback - a lot faster and smoother.
    I have a 2nd, slightly older computer, that houses an extra drive I put in there to use as a scratch disk. I occasionally add that disk to the computer that has CS5 currently installed as a scratch disk for editing video. The external USB drive is used to store the final product and my backups.
    This error has only come up 1 time out of the 49 files I have encoded that usually run 10 minutes to 1.5 hours. I had 9 AVI files in the encoding queue and it always stopped at this 1 particular file. I skipped the file and encoded the rest successfully, but I want to know why it causes an error in AME because this has never happened before. I have even used it on a more up-to-date machine spec wise, thinking that there is a 1% possibility that it doesn't like my computer. The same error was produced. The 9 files that I did encode are roughly the same video and audio format - just this one is the error.
    I gave the file to my friend who was supposed to analyze before I got home - I usually assist them in PC problems and built his better-than-mine PC.
    Any other suggestions for this error and/or a solution?
    Lk

  • Adobe Media Encoder won't start

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

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

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

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

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

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

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

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

  • Adobe Media Encoder CS6 Random Crashing Mid-Render

    Hello -
    I've been dealing with this issue for enough months and across enough computers to finally seek out some advise here, hope it works out...
    Basically I've got a 2 hour long film that I've been trying to export using Adobe Media Encoder CS6. It's never made it all the way through. I can usually skim through the generated quicktime file up to the point where the crash occurred. I've tried using that as a reference to check out my sequence in Premiere but there is never anything suspicious going on there. Most frustratingly the crash occurs randomly. Sometimes it will go through 10 minutes of the film; sometimes an hour. Regardless I get a crash with a report that has no specific information.
    Footage:
    r3d - Various resolutions, all being cut in a 2048x1152 sequence.
    Quicktime mov - ProRes4444 for the most part.
    Machine(s):
    I had been attempting to render this for the past few months with a Macbook Pro running OSX 10.8.4 w/ 16GB RAM, 2.7 GHz Intel i7, NVIDIA GeForce GT 650M 1024MB - never made it through a render longer than 50 minutes of the 2 hours.
    We recently got one of the new 2013 Mac Pro systems running OSX 10.9 w/ 16GB RAM, 3.5 GHz 6-Core Intel Xeon E5, AMD FirePro D500 3072 MB
    The hope was that this new powerful machine would overcome the issues we were running into with these renders. Since I'm posting this now you can probably figure out that it didn't really work out that way...
    Software:
    AME- 6.0.2.81
    Premiere - 6.0
    I know there are updates to be used here, but whenever I update Premiere from just 6.0, the project itself becomes a buggy mess, crashing constantly. I also run Creative Cloud and have tried to just jump over to Premiere CC hoping all my problems would vanish, but instead, I again get a buggy project that constantly crashes. The only version of Premiere that seems to work with this project is 6.0, so general updates have not been useful (and instead damaging, I've wasted several days trying everything I possibly can to make the project work in the updates).
    Any help appreciated. Thanks.

    Thanks for the reply MMeguro.
    Last night I was able to get my first full render through by doing a combination of things (so I'm not sure what did the trick in the end).
    To answer some questions first, never attempted to do the FULL render directly out of Premiere, always switched over to AME for that, so that potentially could work too. Smaller renders have worked directly out of Premiere Pro, but they've also worked out of AME.
    The initial render attempts that had been failing for the last few months were on the MBP which did not support GPU accleration due to an incompatible graphics card. I assumed the issue must be tied to something else because of this and was using it on the renders with the new 2013 Mac Pro. Using the workflow of Pr6.0, AME 6.0 and GPU rendering turned ON, I was failing to render to both Quicktime h264 and ProRes 422.
    What worked for last night's render:
    1. Convert Pr6.0 project to PrCC project (when I've done actual editing in CC after converting this project it tends to crash, but I figured just generating the project itself without doing any editing in it might satisfy what I was attempting to do).
    2. Open AME CC and import PrCC Sequence. Used custom ProRes 422 setting.
    3. Turned OFF GPU acceleration.
    So as long as I the PrCC project I create stays stable long enough to save it (without crashing, which has been a problem with that Pr6.0 to PrCC conversion) then it seems like this will work. Kind of an annoying couple extra steps but I'm just out of my mind glad that I can actually render this thing finally. We're still in the rough stages so being able to turn around a review version within a day is very important.
    Wish I could do more tests to figure out exactly which combination actually made this work for the benefit of others, but can't afford to do multiple 10 hour+ renders with random crash times.
    Anyway, thanks again for the reply MMeguro much appreciated.

  • Adobe Media Encoder CS4 Causing Jerky Playback with Speed Changes

    Here is an Matrox AVI that was captured in Adobe Premiere Pro CS4. Watching the edited clip with a speed change of 600% looked fine when played in Premiere Pro CS4.
    When I export the clip using Adobe Media Encoder CS4 as MPEG2 Blu-ray with a preset of 1440 x 1080i High Quality playback is very jerky. An export of the same clip with normal speed looks great??
    Any suggestions would be greatly appreciated
    Thanks
    Type: Matrox AVI
    File Size: 119.9 MB
    Image Size: 1440 x 1080
    Pixel Depth: 24
    Frame Rate: 29.97
    Source Audio Format: 48000 Hz - 16 bit - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Total Duration: 00;00;36;27
    Average Data Rate: 3.2 MB / second
    Pixel Aspect Ratio: 1.3333
    Codec Type: MPEG-2 IBP
    Bit Depth: 8
    Scan Mode: Interlaced - Upper Field First
    Actual Image Size: 1440 x 1080
    Here are the specs on my workstation
    Case: Coolmaster-830
    Op System: Vista Ultima 64 Bit
    Edit Suite: Adobe Creative Suite 4 Production Premium Line Upgrade
    Adobe Premiere Pro CS 4.0.1 update before installing RT.X2 Card and 4.0 tools
    Performed updates on all Adobe Production Premium Products as of 03/09/2009
    Matrox RTX2 4.0 Tools
    Main Display: Dell 3007 30"
    DVI Monitor: Dell 2408WFP 24"
    MB: ASUS P5E3 Deluxe/WiFi-AP LGA 775 Intel X38
    Display Card: SAPPHIRE Radeon HD 4870 512MB GDDR5 Toxic ver.
    PS: Corsair|CMPSU-1000HX 1000W
    CPU: INTEL Quad Core Q9650 3G
    MEM: 2Gx4|Corsair TW3X4G1333C9DHXR DDR3 (8 Gigs Total)
    1 Sys Drive: Seagate Barracuda 7200.11 500GB 7200 RPM 32MB
    Cache SATA 3.0Gb/s
    2 Raid 0: Seagate Barracuda 7200.11 500GB 7200 RPM 32MB Cache SATA 3.0Gb/s Using Intel's integrared Raid Controller on MB

    Have you ever upgraded Adobe Premiere Pro in the middle of a project?
    By the way I captured the same clip in Adobe software only mode using HDV as a capture settings.  The editing mode is Adobe HDV 1080i, 29.97 frames. The results are also jerky. When I render the clip captured it is also very grainy??
    Type: MPEG Movie
    File Size: 196.4 MB
    Image Size: 1440 x 1080
    Pixel Depth: 32
    Frame Rate: 29.97
    Source Audio Format: 48000 Hz - compressed - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Average Data Rate: 3.2 MB / second
    Pixel Aspect Ratio: 1.3333
    Thanks for responding so quickly!

  • Adobe Media Encoder CS5 hangs when adding files of varying HD resolutions.

    I've seen questions similar to this related to CS4 but never explained very well, and my CS4 for mac worked fine.  I am unsure if this is a new problem or a windows specific problem but here is the situation, if you need more information I will gladly provide it.
    For the past week or so I have been encoding 1920x1080i mov files (h.264/aac) to 1280x720p (vp6/mp3) flvs.  When I stick to that single HD format in the AMC processing que everything works great. However, when I add older HD content into the AMC que, content with non-standard presets, the program hangs.  I tried to import about 15 files last night and the program just sat there all night in a '...NOT RESPONDING' state.  The video's have different audio and video settings and it's little difficult to pinpoint exactly what they were.  Some are 1440x1080, some are 1280x900, some have PCM audio some of mp3. 
    Now I temporarily resolved this issue by simply using cs4 master on my mac pro which worked great.  However I have noticed a huge speed increase in CS5 64bit AMC.  It takes 2-3 hours to encode 1 flash video on my mac pro (dual quad core xeon 2.9Ghz/32GB ram) with CS4.  It takes ~20 minutes on my windows 7 station (single core 2 quad 3Ghz/8GB ram) with CS5.
    How to replicate:
    If I drop a single file into the AMC CS5 que, regardless of the resolution, frame rate, or sound codec; it will import.  If I then add another file with a different resolution AMC will hang and become non-responsive.  It never crashed but I can't wait 12+ hours to see if it accepted a job or not.  As I said before this problem was not observed on CS4 for mac - it worked flawlessly, albeit a little slow. 
    Software used:
    Adobe Media Encoder CS5 windows 64bit
    Adobe Media Encoder CS4 mac 32bit
    System specs:
    Windows 7 home:
    Core 2 quad 3Ghz
    8GB ram
    80GB SSD x25-m
    nVidia Quadro 580
    OSX 10.6.3:
    Dual Xeon 2.99Ghz
    32GB ram
    4 7200 disks in 4TB raid 0
    Radeon HD 2600
    Matrox MAX h.264 compressor card
    Any advice on this situation would be greatly appreciated.  Thank you for your time
    -Michael Emanuel

    Hi Michael,
    Sorry to hear you're having problems with Adobe Media Encoder.  I'd like to get some more information about the problem so I can better understand your workflow, and potentially try to recreate the problem.  For what it's worth, I often import files of different resolutions without any problem, so I want to find out what's different about how you're using AME.
    Apologies for the long list of questions; the small details can be important.
    -- After you import the first file, what else do you do in AME?  Change the preset?  Change the settings?  Change the output destination?
    -- What are the properties of the files that are causing the problem?  You said it happens on "non-standard" files, but can you describe the specifications for one or more files that cause the problem?  Please include file type, length, frame rate, frame dimensions, field order (if applicable), alpha mode (if applicable), and audio type and rate.  If you know more the bitrate, both video and audio, that would be nice, too.
    -- If any of the files are small enough, could you post a couple online that I could try on my machine?
    -- How were these files generated?  What application created them?
    -- Where are the files stored? A local drive, a network drive, a removeable drive (USB or Firewire), etc.?
    -- Which Adobe application or suite do you have installed?  AME a limited set of options if you're using Flash or Web Premium compared to Master Collection, Production Premium, Premiere Pro, or After Effects.
    -=TimK
    -=Adobe Media Encoder QE

  • Since new update - Adobe Media Encoder and CUDA not working

    CUDA not launching - Premier CC says that only software will work. Media encoder crashes on launch. Re-installed both.
    Nvidia 670 GTX

    What version of Premiere Pro? Include the minor version number (e.g., Premiere Pro CS5.5 with the 5.5.2 update).
    Premier Version 7.2.2 (33)
    Have you installed the recent updates? (If not, you should. They fix a lot of problems.)
    Problem started after I installed the software updated
    What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac".
    Windows 7 Ultimate - SP1
    What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. For example, "H.264 in a .mov container", not just "QuickTime".
    REDCODE .r3d from R1 - RedCode 28
    If you are getting error message(s), what is the full text of the error message(s)?
    Adobe Media Encoder Has Crashed - please contact your system administrator. This graphics card is not supported, CUDA disabled.
    What were you doing when the problem occurred?
    Booting premier pro, opening a new project, when trying to render using the encoder
    Has this ever worked before?
    Yes worked fine before 7.2.2 update
    What other software are you running?
    Chrome, Media Player
    Do you have any third-party effects or codecs installed?
    RED Giant Universe is installed
    Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU).
    i7 3930k 12 Core, Nvidia 670 GTX 4GB, 32GB Corsair 1866 RAM, RAID HDD
    Are you using Mercury Playback Engine GPU Acceleration?
    YES - Nvidia 670GTX video card
    Does the problem only happen with your final output, with previews, or both?
    Problem Occurs when rendering the final output for the Medi Encoder and the GPU issue when I open a new project that used to use Mercury
    I also cannot seem to find the file within Premier Pro for "supported Cards" - I had this issue before and I just added my card to this list, this list seems to be missing.
    Thank you.

  • Adobe Media Encoder CS5 - 5.0.1 update

    When I try to update AME CS5 using Adobe Updater, I get this error message:
    The following updates were unable to install. If you wish to install these updates, please fix the problems below and retry:
    Adobe Media Encoder CS5 5.0.1
    Adobe Media Encoder CS5 has been moved or deleted improperly. Please launch or reinstall the application to update the location and try again. To remove the product from the system, please uninstall product using the aliases under "/Applications/Utilities/Adobe Installers"
    A few problems with this - there isn’t an AME uninstaller alias. Also there isn't an installer on the retail DVD, so I wouldn't be able to reinstall anyway. This is further complicated by the fact that the 5.0.1 update is not available online for download. Maybe I'm missing something here, and this is just a stupid mistake on my part.
    I have launched and used AME as well as checking that it is installed correctly (correct location) in my current configuration – still no luck with the auto update.
    Is there a way to tell Adobe (or Adobe Updater) the location of AME, so this install will complete successfully?
    Has anybody else seen this issue?
    Has anybody else resolved this issue?
    Any help is appreciated -
    Jeremiah
    System Config:
    MacBook Pro 5,1 (15-in, late 2008)
    OS 10.6.4
    2.53 GHz Core 2 Duo
    4GB 1067 MHz DDR3 RAM
    NVIDIA GeForce 9600M GT 512 MB (and GeForce 9400M 256 MB)
    Adobe CS5 Master Collection (all current release except AME)
    AME 5.0.0.402 (64bit)

    I did install the Adobe Support Advisor before posting. ASA was a little quirky on the Mac as well, but I finally got it to work; however, it reported no issues. Thanks for the suggestion though.
    What I ended up doing was moving the AME directory to the root level on the system - and then back to it's original location in the Applications folder (same location it has been in). This must have updated something on the OS side because once I ran the updater again - all updates installed successfully.
    I'm not sure how the issue came about, but it appears that the OS or Adobe had some incorrect information in a config or installer log file somewhere and by moving the folder out and then back it was resolved/updated.
    thanks -
    j

  • Adobe Media Encoder not launching when I clicked queue in Export Media

    Hi guys,
    I have been trying for about 3 weeks now trying to render my work using Adobe Media Encoder but it just won't launch as mentioend in my subject line. Upon clicking on queue, the animation showing "preparing data for export" and "exporting data" appeared and disappeared and then nothing happens. Resuming to work on my project in Premiere Pro becomes impossible and a semi-transparent white screen appears over Premiere Pro and it hangs with a message from Windows 7 appearing saying that Premiere Pro has stopped responding.
    Here are a few things that I have tried:
    Updating all of my softwares included in the Production Premium Suite CS5.5
    Deleting all files in the folder C:\Users\User\AppData\Roaming\Adobe\Adobe Media Encoder\5.5
    Pressing Ctrl + Alt +Shift and launching Premiere Pro
    Pressing Ctrl + Alt +Shift and launching Adobe Media Encoder
    Opening sequence in Adobe Media Encoder to try to render
    Called up Adobe Asia Pacific only to be told that I will charged something like USD$39 if they were to help me
    Disabling Mercury Engine Playback capability
    The only work around I'm doing now is to copy the files to another computer and rendering from there.
    Can anyone else suggest another way or point me in the right direction please?
    My com's specs are as follow:
    Windows 7 Premium 64-bit Operating System
    16Gb RAM
    Intel Core i7 CPU [email protected]
    System type: 64-bit Operating System
    Display Adapter: nVidia GeForce GTX560Ti
    Many thanks people.

    The X58 platform uses triple channel memory mode if you use 3 or 6 memory sticks, but if you use 4 slots, memory will only be used in single or dual channel mode, depending on which slots are occupied. Amount of memory has more impact than the mode used, but you may get better performance from 24 GB (6 x 4 GB).
    However, I don't think that will solve your issue. Having only two disks is minimum. Adding a disk can certainly help, see Adobe Forums: Generic Guideline for Disk Setup
    Have you turned of indexing and compression on both disks, have you uninstalled the sidebar, MSN and games? Have you disabled unneeded services, etc.?
    It says Vista but also applies to Win7: Adobe Forums: Guide for installing and tuning a Vista...
    DSLR material is usually HD, but .VOB files are SD, so there is a lot of scaling going on when exporting. Make sure you have enabled hardware MPE. Also have a look at Adobe Forums: System requirements for CS5

  • Crash upon opening Adobe Media Encoder

    Hello,
    I just built a new computer and installed Adobe CS3 Production Premium, with all the updates (Premiere Pro 3.2).
    I'm editing a project with DVCPRO HD 720p clips.
    When I try to open the Adobe Media Encoder, Premiere freezes, and I'm forced to restart the whole computer. (The task manager doesn't help.)
    It seems to be random too- sometimes it'll open, sometimes not. But mostly not.
    Any ideas? Thank you in advance!
    Windows XP Pro SP3
    EVGA nForce 750i mobo
    Core 2 Quad Q9300 2.5GHz
    4GB ram (3gb usable, sigh)
    GeForce 9800 GT
    X-Fi
    500GB system drive and two 500GB media drives (all with plenty of free space)

    Hi Jeff,
    Yes, I can export to movie without crashing.
    I ran Sherlock and it found a few broken codecs:
    "MainConcept (Adobe2) AAC Decoder"
    "MainConcept (Adobe2) H.264/AVC Decoder"
    "MainConcept (Adobe2) H.264/AVC Video Encoder"
    "MainConcept (Adobe2) MPEG Audio Encoder"
    "MainConcept (Adobe2) MPEG Video Encoder"
    You can see the full txt report from Sherlock here:
    http://greatmindspro.com/documents/Codecs.txt
    Is there a way to repair these? I don't have any extra third party software installed, except for Magic Bullet Looks, but it's only an effects-based plug-in- nothing to do with exporting.
    How could I repair these broken codecs?

Maybe you are looking for