Media Encoder fails with Time Remapping

There is a single 1 Minute Clip in the PR CC 2014 timeline, with some time remapping effects. Exporting with Media Encoder CC 2014 SLOWS DOWN speed of the clip after approx. 30 sec unintentionally and therefore gets out of sync with sound, and ends at a complete different frame than in the timeline.
However, exporting directly from PR CC 2014 gives correct result.
Anyway, this looks like a major "feature" of ME!?!
(MacBook Pro 2013, 15", 2,6 GHz i7, OS X 10.9.4)

source is an uncompressed HD 1080 QT .mov file rendered from AE.
sequence settings are 1920x1080, 25fps, square, progressive
export settings are QT, H.264, 1920x1080, 25fps, progr, square, 20000kbps

Similar Messages

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

  • 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 Recovery failed with error 1111

    Hi,
    on 10g R2 on Unix I have :
    Media Recovery Start
    Managed Standby Recovery not using Real Time Apply
    Fri Jun 24 10:56:52 2011
    Media Recovery failed with error 1111
    From alert.log :
    Errors in file /data01/oracle/mydb/admin/bdump/hhhh_17637.trc:
    ORA-01111: name for data file 523 is unknown - rename to correct file
    ORA-01110: data file 523: '/oracle/product/10g/db_1/dbs/UNNAMED00523'
    ORA-01157: cannot identify/lock data file 523 - see DBWR trace file
    ORA-01111: name for data file 523 is unknown - rename to correct file
    ORA-01110: data file 523: /oracle/product/10g/db_1/dbs/UNNAMED00523'
    Any idea ?
    Thanks.

    here is one test case, i ran into same issue. and reolved as below.
    When Standby_file_management is set to “MANUAL” , if any data files added on primary database, These changes certainly won’t be altered in standby database.
    After starting MRP process, it dies and terminated with the following errors.
    Errors from Alert log file:-
    Errors in file /oracle/app/oracle/admin/CC/bdump/cc_mrp0_22294.trc:
    ORA-01111: name for data file 536 is unknown - rename to correct file
    ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
    ORA-01157: cannot identify/lock data file 536 - see DBWR trace file
    ORA-01111: name for data file 536 is unknown - rename to correct file
    ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
    Errors from Trace file:-
    MRP0: Background Media Recovery terminated with error 1111
    ORA-01111: name for data file 536 is unknown - rename to correct file
    ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
    ORA-01157: cannot identify/lock data file 536 - see DBWR trace file
    ORA-01111: name for data file 536 is unknown - rename to correct file
    ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
    ORA-01111: name for data file 536 is unknown - rename to correct file
    ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
    ORA-01157: cannot identify/lock data file 536 - see DBWR trace file
    ORA-01111: name for data file 536 is unknown - rename to correct file
    ORA-01110: data file 536: '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536'
    ARCH: Connecting to console port...
    Check out from SQL, Which files need to be recovered on standby database?
    SQL> select * from v$recover_file where error like '%FILE%';
    FILE# ONLINE  ONLINE_ ERROR                   CHANGE# TIME
    +536 ONLINE ONLINE FILE MISSING 0+
    SQL>
    On Primary check out for actual naming convention:-
    SQL>  select file#,name from v$datafile where file#=536;
    FILE# NAME
    +536 DATA/c/datafile/undotbs9.595.750444337
    SQL>
    On Standby check datafile name:-
    SQL> select file#,name from v$datafile where file#=536;
    FILE# NAME
    +536 /oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536+
    SQL>
    Make sure still standby_file_management is set to “MANUAL”, After performing media recovery again can be enabled to “AUTO”.
    Rename datafile from standby database:-
    SQL> alter database create datafile '/oracle/app/oracle/product/10.2.0/db_1/dbs/UNNAMED00536' as 'DATA3/cc/datafile/undotbs9_595_750444337';+
    Database altered.
    Start the MRP Now:-
    SQL> alter database recover managed standby database disconnect from session;
    Database altered.
    After creating the file, MRP will start applying archives on standby database.

  • Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem."  Tried suggestions I've seen on the forum.

    Time Machine spends hours partially backing up and then fails with "Time Machine couldn't complete the backup due to a network problem."  I've tried various suggestions I've seen on the forum but nothing has worked.  TIme Machine worked fine for the last two years and just suddenly started having this problem every time.  The only thing that was a little different is that the computer was off for a week while on vacation and then I added a large amount (20 GB) of photos. Now the requested backup size is 82GB, which is large, and process proceeds very slowly for 2-3 hours before failing with the message mentioned.  I have more than enough available backup storage space for it.  Before failing, Time Machine has backed up no more than 12GB or so of the backup.  It fails during different files each time.
    I've turned off the computer sleep feature, and I've checked that the NAS is set to never automatically power down. I normally backup over Wi-Fi, but I've also tried connecting to Ethernet and it still has the same problem.  It's odd because I also have a MacBook Pro that is still backing up fine to the same NAS using the MacBook's Time Machine. 
    I am using an iMac with OS X 10.6.8 and an Iomega StorCenter ix2-200 NAS.
    I have system logs that I can share if helpful.  The logged messages vary a bit from run to run, but here are some messages that I've been seeing:
    I always get this message near the beginning of the backup:
    Event store UUIDs don't match for volume: Macintosh HD
    I've gotten this messsage a number of times:
    Bulk setting Spotlight attributes failed.
    One Day
    Stopping backupd to allow ejection of backup destination disk!
    Another day
    1/7/12 10:44:20 AM
    mDNSResponder[18]
    PenaltyTimeForServer: PenaltyTime negative -112916, (server penaltyTime -1132397006, timenow -1132284090) resetting the penalty
    1/7/12 10:46:37 AM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x1106be94
    1/7/12 10:46:37 AM
    kernel
    AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
    Another Day
    1/6/12 8:03:22 AM
    Google Chrome[164]
    Cannot find function pointer CMPluginInFactory for factory 3487BB5A-3E66-11D5-A64E-003065B300BC in CFBundle/CFPlugIn 0x16f99e20 </Users/smarmer/Library/Contextual Menu Items/Google Notifier Quick Add CM Plugin.plugin> (not loaded)
    1/6/12 8:04:02 AM
    com.apple.backupd[193]
    Copied 7.5 GB of 67.0 GB, 8866 of 8866 items
    1/6/12 8:06:58 AM
    /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[1013]
    No valid tickets, timing out
    1/6/12 8:29:44 AM
    mDNSResponder[19]
    PenaltyTimeForServer: PenaltyTime negative -148702, (server penaltyTime 2056822773, timenow 2056971475) resetting the penalty
    1/6/12 8:59:22 AM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa5ac380
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect started /Volumes/TimeMachine prevTrigger 0 currTrigger 1
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  doing reconnect on /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  soft mounted and hidden volume so do not notify KEA for /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  Max reconnect time: 30 secs, Connect timeout: 15 secs for /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    AFP_VFS afpfs_DoReconnect:  connect to the server /Volumes/TimeMachine
    1/6/12 8:59:22 AM
    kernel
    ASP_TCP asp_SetTCPQoS:  sock_settclassopt got error 57
    Another day
    1/5/12 3:48:55 PM
    mdworker[2128]
    CFPropertyListCreateFromXMLData(): Old-style plist parser: missing semicolon in dictionary.
    1/5/12 4:24:54 PM
    mDNSResponder[19]
    PenaltyTimeForServer: PenaltyTime negative -42698, (server penaltyTime 1148718961, timenow 1148761659) resetting the penalty
    1/5/12 4:29:58 PM
    com.apple.backupd[2074]
    Copied 586.4 MB of 67.0 GB, 9891 of 9891 items
    1/5/12 4:39:00 PM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0xa1c0380

    bokon0n wrote:
    1/11/12 8:53:30 AM
    com.apple.backupd[1169]
    Warning: Destination /Volumes/TimeMachine does not support TM Lock Stealing
    1/11/12 8:53:30 AM
    com.apple.backupd[1169]
    Warning: Destination /Volumes/TimeMachine does not support Server Reply Cache
    Those indicate that your NAS is not fully compatible with Snow Leopard. 
    1/11/12 8:53:35 AM
    kernel
    jnl: disk2s2: replay_journal: from: 67182592 to: 78680064 (joffset 0xa7b8000)
    1/11/12 8:53:39 AM
    kernel
    jnl: disk2s2: examining extra transactions starting @ 78680064 / 0x4b09000
    1/11/12 8:53:39 AM
    kernel
    jnl: disk2s2: Extra txn replay stopped @ 79056896 / 0x4b65000
    1/11/12 8:53:49 AM
    kernel
    jnl: disk2s2: journal replay done.
    1/11/12 8:53:49 AM
    fseventsd[41]
    event logs in /Volumes/Time Machine/.fseventsd out of sync with volume.  destroying old logs. (253512 14 253512)
    1/11/12 8:53:50 AM
    kernel
    hfs: Removed 1 orphaned / unlinked files and 0 directories
    That looks like a problem was found with the file system (data) on the TM disk.  I don't know the details, but OSX tried to recover it from the journal, and found extra data on the drive.    Likely a result of the incompatibility mentioned above.
    1/11/12 9:47:40 AM
    com.apple.backupd[1169]
    Bulk setting Spotlight attributes failed.
    That's a problem writing to the NAS drive.
    But the backup continued after all this.
    1/11/12 1:25:07 PM
    kernel
    ASP_TCP Disconnect: triggering reconnect by bumping reconnTrigger from curr value 0 on so 0x9d00b44
    Something caused a disconnect.  Can't tell from the log what it was.
    I doubt it's a problem with something in OSX being damaged or corrupted, but reinstalling OSX isn't a major hassle, so might be worth a try.
    To be incompatible with Snow Leopard, this NAS must be at least a couple of years old.  It may be beginning to fail.
    Contact the maker.  See if there's an update to make it compatible with Snow Leopard.  If so, that might fix it.
    If not, or if that doesn't fix it, see if they have any diagnostics that will shed any light.

  • Trying to Add Adobe Media Encoder in Creative cloud licenses but its not coming up, is media encoder bundled with another adobe product?

    Trying to Add Adobe Media Encoder in Creative cloud licenses but its not coming up, is media encoder bundled with another adobe product?

    You MUST have a 64bit computer... what is your computer?
    Adobe's MINimums http://helpx.adobe.com/premiere-pro/system-requirements.html
    -Programs won't display if they will not install on your computer
    -http://helpx.adobe.com/creative-cloud/kb/all-apps-displayed-aam.html

  • Media Recovery failed with error 368

    The following error occurs on standby database---
    ALTER DATABASE RECOVER CONTINUE DEFAULT
    Media Recovery Log x.0000008973.arc
    Recovery interrupted.
    Redo code 6 enountered during in-flux buffer recovery
    Some recovered datafiles maybe left media fuzzy
    Media recovery may continue but open resetlogs may fail
    some error occurred during recovering in-flux buffers
    Recovered data files restored to a consistent state at change 138445558.
    Media Recovery failed with error 368
    Please advice. Thanks in advance

    Here you have the complete reference for the command
    that you executed :
    http://download-west.oracle.com/docs/cd/B10501_01/server.920/a96540/statements_15a.htm#SQLRF00802
    [email protected]
    Joel P�rez

  • Media Coder Failing with MPEG2-DVD and H.264 Blu-Ray Encode

    I am useing Adobe Media Encoder CC 2014 8.0.0.173 build.
    I am a CC subscriber.
    I am importing a Premiere Pro CC 2014 timeline.
    I also have Premiere Pro CS6, Photoshop CC and CS6, Encore CS6, Lightroom 5, Indesign CC and CS6 installed.  Just updated all apps from the cloud.
    When exporting the timeline to MPEG2-DVD I get the failed status.
    In the text note section this is the result: MXF decode error in "J:\Murray-Gross Wedding\CLIPS001\AA0068\AA006802.MXF" at frame 16339. Frame 16316 was substituted.
    I had several frames substituted.
    I tried both the Mercury Playback Engine GPU acceleration and I also tried the software only version.
    The original footage is;
    MXF File details:
    Wrapper type: MXF OP1a (type: SingleItem SinglePackage MultiTrack Stream Internal)
    File generated by: CANON, XF100
    MPEG-2 422 Long-GOP
    I was able to export the timeline to an avi file from Pro CC 2014.  But P Pro told me that the export had failed.  When I checked the folder though the avi file was there.
    I am running Windows 7 home premium.
    I need to make a DVD of this footage.  And would prefer not to reformat the avi file I created.  Thanks in advance.

    Do you get encode complete with Errors or are you getting encode failed (no encoded file)?  The reason frames were substituted is because the source file had errors or other problems.  So during import, PPro and AME substitute bad frame with adjacent good frame and continue to import.  But if there are way too many bad errors and source is too corrupted, it may not be able to import it correctly and won't be able to export.  so let us know if you get exported file and you are just curious what the error message was or if you don't get encoded files going to MPEG2-DVD at all. 

  • Encoding Fails with Media Encoder

    Running Premiere Pro CS6 on a 2009 27" iMac with 3.06 Intel Core 2 Duo and 16 GB Ram running OS 10.6.8. Source video is from a Canon HF100 Camera recording live shows, usually 2 acts. No problem with editing in Premiere but when using Adobe Media Encoder the video seems to process nicely but what it come to the first act break it hangs after the fade out for a minute then FAILS! Encoding log is not very useful with the following message (ooo wait for it) "Export Error Error Compiling Movie Unknown Error. This now has happened with three videos. Getting very concerned and frustrated with this situation. Any ideas out there?

    Running Premiere Pro CS6 on a 2009 27" iMac with 3.06 Intel Core 2 Duo and 16 GB Ram running OS 10.6.8. Source video is from a Canon HF100 Camera recording live shows, usually 2 acts. No problem with editing in Premiere but when using Adobe Media Encoder the video seems to process nicely but what it come to the first act break it hangs after the fade out for a minute then FAILS! Encoding log is not very useful with the following message (ooo wait for it) "Export Error Error Compiling Movie Unknown Error. This now has happened with three videos. Getting very concerned and frustrated with this situation. Any ideas out there?

  • Premiere Pro/Media Encoder fail when exporting something with AE linked?

    Hey all, I do some video production work for a university, and we're running into some problems when trying to export all the videos from a particularly large course.  We haven't run into this issue before so I'm hoping someone might have knowledge of it and can help me out.
    Here's some background-
    I'm trying to export videos, about 20 minutes each.  Each video has an opening sequence and closing sequence that were created in After Effects and are Dynamic linked in the right spots on the timeline.
    We're encoding with Vimeo HD 720p 29.97 settings.
    Media Encoder gets through one pass seemingly just fine, and then a little after halfway through encoding it stops (doesn't crash, just stops encoding any further) and crashes when attempting to stop the queue.
    It's a pain to export from After Effects and re drag in all the sequences, so our workflow keeps all exporting Premiere -> Media Encoder.
    EDIT: Can't believe I forgot to mention this- works fine exporting directly from a timeline in Premiere, it's only when Media Encoder is used that issues arise- but it's unfeasible to export 30 videos from the timeline.
    EDIT: Done some more testing over the course of the day.  I can add After Effects files to a AME queue and encode them with the Vimeo settings and it makes it through both passes, correctly exporting the videos.  It just doesn't work when those same compositions are exported as linked compositions in a Premiere Pro timeline.
    Some things I've tried with no success:
    Exporting the After Effects files separately does not work, it hangs even if only exporting the after effects segments.(20 seconds each).
    I've turned off CUDA and done software only, still hangs.
    I've tried dragging/adding from Media Encoder/any number of different workflows to get the sequences from Premiere to After Effects.
    I've tried exporting with different settings: (e.g. non Vimeo HD 720p 29.97), still hangs (doesn't even start encoding, doesn't get halfway).
    Any ideas?

    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.

  • 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

  • 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

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

  • 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

  • Exporting widescreen DV project to Media Encoder Fails

    This is my first attempt at exporting a video using CS4's media encoder, and when I try, the encoder app seems to not be able to "find" or load the Premiere CS4 sequence.  It seems to fail after a few minutes, during which the status of the job is "Waiting" and at the bottom it says "Loading xxxxx.prproj".
    Any thoughts?  I'm on an i5 iMac with the CS4 Production suite installed.
    Here's the error it gives:
    - Source File: /Users/user/Library/Caches/TemporaryItems/Wedding.prproj
    - Output File: /Users/user/Video/Projects/Wedding/DVD/_Wedding.mpg
    - Preset Used: Export Widescreen DVD 7Mbps CBR
    - Video:
    - Audio:
    - Bitrate:
    - Encoding Time: 00:12:19
    Sun Dec 20 15:56:11 2009 : Encoding Failed
    Could not read from the source. Please check if it has moved or been deleted.

    FIXED!
    Thanks to some points in this thread, I have solved my problem.
    It was the KNOLL LIGHT FACTORY plug-in.  I removed it, and the Adobe Media Encoder now works on my system.  I assume that DYNAMIC LINKING between the CS4 apps also now works, but have yet to test that.
    This also explains why my CS4 suite works on my MacBook Pro; I never installed KLF on my laptop.
    Now I need to tell RED GIANT SOFTWARE about this problem, and either get a solution from them, or a refund.
    Thanks.  You can add this solution to your collective repertoires in case a future OSX user encounters this exact problem.

Maybe you are looking for