Revenir à Adobe Media Encoder 2013 ?

Bonjour,
j'ai constaté avec dépit que Adobe Media Encoder 2014 ne permet plus l'exportation aux formats FLV & F4V. Pourquoi ?
c'est tout simplement absurde, les régies de diffusion de campagnes de publicité demandent encore massivement ces formats dans leurs specs.
Adobe dans sa note de Maj recommande de revenir à une ancienne version pour exporter en FLV. J'ai donc du résintaller la version 5.5 à partir d'un vieux DVD, ce qui n'est pas très satisfaisant vu que cette version est moins intuitive et performante que la CC.
Bref. Quelle est la solution pour revenir à Adobe Media Encoder 2013 car dans Creative Cloud, je ne peux revenir qu'à la version précédente de Adobe Media Encoder 2014 ce qui ne résout pas mon problème.
merci pour votre réponse
Sébastien

Bonjour Seb,
Je viens de lire ton message et malheureusement, je ne puis te donner de solution.
Je suis assez ahuri et consterné qu'adobe puisse recommander de revenir à une ancienne version pour utiliser un de ses propres formats. Je le suis d'autant plus, que mon site est entièrement construit en flash (CS4 ou 5 ) et les vidéos sont au format FLV et je continue donc à utiliser ce format.
Je n'ai plus ouvert flash depuis la création du site, je viens de l'ouvrir et essayé d'importer une vidéo ....impossible d'ouvrir un AVI, un MTS, un WMV et même un MOV !!!!
Je n'ai réussi qu'avec un MP4 et j'ai fermé car je ne tiens pas à me replonger dans Flash actuellement.
Reste, les convertisseurs sur le net.....tout cela est assez étonnant. Ce n'est pas parce que ce format à comme inconvénient d'être dépendant de la bande passante et si c'est évident que sa mort est programmée qu'il faut que ce soit Adobe lui-même qui enfonce l'estocade. Adobe, le matador du FLV, c'est fort!!!! .
Encore, FLV...quelle sera la prochaine surprise qu'Adobe nous prépare????
Andres

Similar Messages

Adobe Media Encoder Unknown Error

I'm trying to export an Adobe Premier Pro file on Adobe Media Encoder. Each time I try, it gets about halfway through, then this error message comes up:
- Source File: /Users/A25/Library/Caches/TemporaryItems/Incubus Trailer Rough Cut.prproj
- Output File: /Users/A25/Desktop/Odyne Theatrical Trailer.mp4
- Preset Used: HDTV 1080p 25 High Quality
- Video: PAL, 1920x1080, 25 [fps], Progressive
- Audio: AAC, 160 [kbps], 48 kHz, Stereo
- Bitrate: VBR, 1 Pass, Target 32.00, Max 40.00 [Mbps]
- Encoding Time: 00:07:07
Mon Apr 15 12:48:21 2013 : Encoding Failed
Error compiling movie.
Unknown error.
I've tried different video presets (1440x1080, 1920x1080 etc), but this message has appeard every time. Any ideas how to export it?
Thanks

Please read here:
"Error compiling movie" when rendering or exporting with Premiere Pro CS3, CS4, CS5, CS5.5, CS6
and here:
Adobe Forums: FAQ: What information should I provide when asking a question on this forum?
Jeff

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 7.2.0.43 still crashes after beginning of encoding - bugs for months now!

Adobe Media Encoder CC 7.2.0.43 is still crashing after beginning of encoding! In my case this bug exists for months now and Adobe is not able to get rid of its own programming faults! The user pays a lot of money for the license and doesn't get a functioning software! I spent days to get a solution now, but NOTHING of your suggested help works!
This is my 'support' history beginning in AUGUST (!):
Sent: Thursday, August 15, 2013 ...
Subject: Bug Report
Product: Adobe Media Encoder
Product Version: CC
Operating System : Windows 7
OS version: Service P1
Concise problem statement: Steps to reproduce bug:
1. Go to Premiere Media Export
2. Stating Media Export Parameters for ME
3. Starting ME
4. Define video title and path
5. Start Media Encoder CC rendering
6. ME states 'Preview not available'
7. Rendering aborts after about 15 sec.
8. Media Encoder CC crashes, no matter which kind of video! Every time.
9. Direct 'Export' from Premiere CC is possible with all the same parameters, but CC AME crashes!
10. Also installed Premiere CS 6 Media Encoder WORKS without any problems, but not the CC Media Encoder!!
Expected results: Media Encoder CC WORKING. This is still my expected result as a paying customer!
My steps to solve these problems (with Adobe's help) were / are:
- Cleant every suggested media cashes.
- Tried to render the sequences also without audio.
- Tried to render as one pass.
- Even if I try just to export ONE simple standard SONY PMW EX1 mp4 file which should never cause problems it chrashes, also without audio.
- Also if I clean all preferences and caches before, EVERY file type crashes, no matter if I try to export a video or a still picture.
- This is not happening in Adobe AME CS6 with the same files, but in CC!! CS6 still renders reliably with preview, but CC crashes without being able to show any preview.
- Held the Shift key down while starting AME. This should reset preferences and so on...
- Deleted suggested "7.0" directories as described in other forum posts concerning this topic.
- Logged out of my CC account.
- Deinstalled and reinstalled PPro, After Effects, InDesign, Flash, using Adobe Creative Cloud Cleaner Tool. All is the newest version 7.2.
- Set GPU renderer to "Software Only". Some video cards have issues when GPU is set to "OpenCL" or "CUDA".
- Checked updates available for video driver. Latest is installed.
- Turned off "Enable Native Premiere Pro sequence import" in AME prefs.
- AMEEncodingErrorLog.txt doesn't have any content, not a single line.
NOTHING WORKED OR HELPED!
Windows Crash log: WER3A92.tmp.WERInternalMetadata.xml:
<?xml version="1.0" encoding="UTF-16"?>
<WERReportMetadata>
    <OSVersionInformation>
        <WindowsNTVersion>6.1</WindowsNTVersion>
        <Build>7601 Service Pack 1</Build>
        <Product>(0x3): Windows 7 Home Premium</Product>
        <Edition>HomePremium</Edition>
        <BuildString>7601.18247.amd64fre.win7sp1_ ... private data erased here ...</BuildString>
        <Revision>1130</Revision>
        <Flavor>Multiprocessor Free</Flavor>
        <Architecture>X64</Architecture>
        <LCID>1031</LCID>
    </OSVersionInformation>
    <ParentProcessInformation>
        <ParentProcessId>9168</ParentProcessId>
        <ParentProcessPath>C:\Program Files\Adobe\Adobe Media Encoder CC\32\dynamiclinkmanager.exe</ParentProcessPath>
        <ParentProcessCmdLine>"C:\Program Files\Adobe\Adobe Media Encoder CC\32\dynamiclinkmanager.exe"</ParentProcessCmdLine>
    </ParentProcessInformation>
    <ProblemSignatures>
        <EventType>APPCRASH</EventType>
        <Parameter0>Adobe Media Encoder.exe</Parameter0>
        <Parameter1>7.2.0.43</Parameter1>
        <Parameter2>52a18991</Parameter2>
        <Parameter3>libmmd.dll</Parameter3>
        <Parameter4>12.0.12.2</Parameter4>
        <Parameter5>5073ba44</Parameter5>
        <Parameter6>c0000005</Parameter6>
        <Parameter7>00000000000bfd76</Parameter7>
    </ProblemSignatures>
    <DynamicSignatures>
        <Parameter1>6.1.7601.2.1.0.768.3</Parameter1>
        <Parameter2>1031</Parameter2>
        <Parameter22>4c50</Parameter22>
        <Parameter23>4c50fbaed87d7d2a6adc173c5da6a755</Parameter23>
        <Parameter24>28b8</Parameter24>
        <Parameter25>28b834131666732fe13a476b5fa8febe</Parameter25>
    </DynamicSignatures>
    <SystemInformation>
        <MID> ... private data erased here ... </MID>
        <MarkerFile>1043_ASUSTEK_G74SX_V20_WIN7</MarkerFile>
        <SystemManufacturer>ASUSTeK Computer Inc.</SystemManufacturer>
        <SystemProductName>G74Sx</SystemProductName>
        <BIOSVersion>G74Sx.203</BIOSVersion>
    </SystemInformation>
</WERReportMetadata>
Adobe team, I'm at my wits' end now and don't know how to continue. Can you help me?

https://www.youtube.com/watch?v=oJ0hz9JkLgM

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 CC (7.0.1) Update

Hi all,
The Adobe Media Encoder CC (7.0.1) update is now available.
See this post for details, including how to install the update:
http://blogs.adobe.com/aftereffects/2013/07/adobe-media-encoder-cc-7-0-1-update-available- several-bug-fixes-for-closed-captions-h-264-exports-and-more.html
Kevin

Does the AME not support CUDA like Premiere Pro?
It used to in CS6. It does not in CC7.
Direct export may be the better way to go.

Adobe Media Encoder CC が起動しない

Adobe Media Encoder CC についてです。
Media Encoder CC を起動させたいのですがエラーが出て起動しません。
Premiereで単体の書き出しはできるのですが
複数のシーケンスデータを個々に書き出しをしたいので
どうしてもMedia Encoder CC にキューを出してまとめて処理をしたいので
どなたか解決策を知っている方どうかご教授願います。
OS:windows8
プロセッサ：Intel(R)Core(TM)i7-3770 CPU @3.40Ghz 3.40Ghz
メモリ：16.0GB
システムの種類：64ビットオペレーティングシステム、x64 ベースプロセッサ
Adobe Media Encoder CC 起動時のエラーメッセージ：
「 Adobe Media Encoder CC は動作を停止しましたプログラムは閉じられ、
解決策がある場合はWindowsから通知されます。」
windowsから通知なんて来ません；
アンインストールをしても状態は変わりませんでした。
あとなにか必要な情報がありましたら可能な限り追記します。
よろしくお願い致します。

ご投稿ありがとうございます。
こちらの件に関しまして、先日リリースされた7.2アップデートでの修正点となっております。
是非一度お試しいただければと存じます。
アップデートは、製品のヘルプメニューからアップデート　を選択・実行いただくか、
Creative Cloud　デスクトップアプリケーションのアップデートボタンから実行できます。
（Premiere Pro CCのアップデートを実行すると、AdobeMediaEncoder CC側も同時にアップデートされます）
Premiere Pro CC の 2013 年12月リリースについて
http://helpx.adobe.com/jp/premiere-pro/kb/cq12162025.html
Adobe Media Encoder CC (7.2): what’s new and changed in this December 2013 update(英文）
http://blogs.adobe.com/aftereffects/2013/12/adobe-media-encoder-cc-7-2-december-2013-updat e.html

Adobe Media Encoder CS5 doesn't work anymore (WHY? WHAT's WRONG?)

The system I use is Adobe Production Premium CS5.
I have often used Adobe Media Encoder CS5 started from the export of a film sequence in Adobe Premiere Pro CS5.
On the 31st of December 2013 my computer crashed and dumped more or less at the end of a process of Adobe Media Encoder CS5. There was no complete output.
Since then this program Adobe Media Encoder CS5 cannot start up anymore.
It stops at the start-up saying that the program does not work anymore and that there will be looked for a solution. But then it finishes saying that it will be reported if a solution becomes available in the future.
I have tried the following:
- Run Adobe Media Encoder CS5 (exe) from directory C:\Program Files\Adobe\Adobe Media Encoder CS5 => same problem.
- Stop security control AVG while not online with internet => run Adobe Media Encoder CS5 => same problem.
- Reinstalled complete Production Premium CS5 suite => same problem.
- Removed complete directory C:\Program Files\Adobe\Adobe Media Encoder CS5 and then reinstalled Adobe Premiere Pro CS5 => the full directory C:\Program Files\Adobe\Adobe Media Encoder CS5 with contents was there after the install, but subsequent running of Adobe Media Encoder CS5 => same problem.
- Removed complete contents of D:\mediacache\database\Media Cache and D:\mediacache\Media Cache Files => same problem.
What more can I do ??????
I would be very grateful for a solution.
Regards, Arie de Jong, Rotterdam

Hi Jim,
Thank you very much for the suggestions for a solution. First I considered
re-installing Win 7 Pro, because I did not have a fall-back point
predefined. So I could not try to reload a previous system environment. But
for your information the following.
Yesterday my son suggested that there could be some corruption in a control
file of Adobe Media Encoder, because re-installing that program did not
give a solution. Obviously that then would have to be a file which is not
affected by a program re-install.
What he then did for me is to remove directory
Users\owner\ AppData\Roaming\Adobe\Adobe Media Encoder (he actually
renamed it to hide that directory for Media Encoder).
Thereafter we ran program Media Encoder from Premiere. The result was that
a new directory ......\ Roaming\Adobe\Adobe Media Encoder with proper
control files was automatically generated and the problem was solved.
Regards from Arie de Jong

Both After Effects & Adobe Media Encode CC giving are not letting me export.

Dear All,
Both After Effects & Adobe Media Encode CC giving are not letting me export movies.
Some times they will, but after one file both programs give me the following error messages.
After effects:
“[file path and name].mov. An output module failed. The file may be damaged or corrupted. (-1610153464)"
AME:
"Can't read from source."
I've went through the forum and found threads & pages discussing the problem.
E.g.
http://blogs.adobe.com/aftereffects/2013/08/solutions-for-problems-with-quicktime-files-in -after-effects-cc-12-0-because-of-conflict-with-dvcprohdvideoout-quicktime-component.html
http://forums.adobe.com/thread/1252092
After following all the tips and suggestions (from deinstalling quicktime components & audio components to completely reinstalling CC) I'm still experiencing the problems.
Which leaves me in a bit of a squeeze. I need to export over 144 movies in the coming 2 days and the only way to do this is to quit and open media encoder (or AE) after each single export.
Not really an option.
Both problems have the process Adobe QT sever in common, I took this from the console:
9/26/13 1:02:44.517 PM com.apple.launchd.peruser.501[171]: ([0x0-0x42042].com.adobe.Adobe QT32 Server.application[331]) Job appears to have crashed: Segmentation fault: 11
9/26/13 1:02:44.672 PM ReportCrash[354]: Saved crash report for Adobe QT32 Server[331] version 7.0.1 (7.0.1.0) to /Users/martijn/Library/Logs/DiagnosticReports/Adobe QT32 Server_2013-09-26-130244_martijns-MacBook-Pro-2.crash
System information:
Retina MacBook Pro (Mid 2012) (16gb ram)
Mac OS X 10.8.5 (12F37)
Running Adobe CC (for teams), all apps are up-to-date.
I don't no why Adobe puts out such a buggy piece of software (I know it has to with Apple's poor 32bit quicktime implimentation, but hey, this was known information no?).
Upgrading to CC has given our office nothing but problems.
Hope someone can help to find a work around until Adobe realeases a proper update and solves this problem once and for all.
All help is much appreciated.
Kind regards,
Martijn

Hello Tim,
Thanks for the really quick response!
Regarding the crash log: it doesn't reference com.apple.audio.CoreAudio (though it did before, so I followed all the steps in your blog post before I posted to this forum).
I've uploaded the crashlog to:
http://martijnlambada.com/TMP/AdobeQT32servercrash.zip
If you want to inspect it. It mentions the DXV codec (which I also uninstalled), but the crash keeps occuring. Also I need to export to DXV since it's the only codec the d3 media
server accepts (http://d3technologies.com).
I followed all the steps in the troubleshooting steps.
Codecs used: I've tried everything from animation to Apple ProRes (including: h264/motion jpeg/uncompressed). With all codecs the Adobe QT32 server keeps crashing (though I can't always reproduce).
Export destination: Internal SSD (same as where the OS is installed on) + External raid (via firewire & thunderbolt) + external HD via usb 3.0 (tried everything).
When does the problem start: Really hard to specify, sometimes a day without crashes, sometimes every export for days on end. Sometime after restarting (tried logging out, restarting, switching off and on the computer). With other programs running and with out. Now checking every process active when exporting, and comparing log files.
Can you export to other formats: See question 1, sometimes I can, sometimes not.
When you launch AE and/or AME, is QT32 Server running? At what point does it stop running? Still runing when I open the program. It crashes when exporting (ofter after finishing the first export).
What component files are in your Library/QuickTime folder?: Currently the folowing:
AppleAVCIntraCodec
AppleHDVCodec.component
AppleIntermediateCodec.component
AppleMPEG2Codec.component
AppleProResCodec.component
DesktopVideoOut.component
DVCPROHDCodec.component
DVCPROHDMuxer.component
DVCPROHDVideoDigitizer.component
DVCPROHDVideoOutput.component
DVCPROHDVideoOutputClock.component
FCP Uncompressed 422.component
iChatTheaterPreview.component
IMXCodec.component
LiveType.component
Hope this helps.
Cheers,
Martijn

Adobe Media Encoder Export like source size

Hey,
i´m trying to set up a custom export setting based upon HD BlueRay Mpeg setting.
My source is a custom size (1400 x 1050 px), but i am not able to change to "size as source".
Any Ideas how to change that?
THX
MArco

Marco,
You can use AME to encode a 1400x1050 M2V file.
You need to use the generic MPEG2 format (not Blu-ray or DVD) and change the Level to High. (High 1440 will also work, but it is designed for specific applications.) You will also need to set the Profile to Main or High.
The most important factor is what type of MPEG2 streams your playback device will support. That will be important for setting the Profile and Level values, which constrain the bitrate and therefore the frame size/frame rate of the MPEG2 stream. (This is what Mylenium was referring to.)
Read this for more technical detail about different Profiles and Levels:
http://en.wikipedia.org/wiki/H.262/MPEG-2_Part_2#Video_profiles_and_levels
You cannot transfer encoding presets between After Effects and AME. However, remember than you can encode an After Effects comp directly from AME without rendering an intermediate comp first. Either drag and drop the comp from AE's Project panel into the AME queue, or simply import the AE project into AME, and choose the comp you wish to render. In the next version of After Effects, this process will be much easier with the introduction of a new Add To Adobe Media Encoder command from within After Effects.
http://blogs.adobe.com/aftereffects/2013/04/whats-new-changed-after-effects-next.html
If you want to contact in-person support for AME, visit the following page and choose After Effects as the product (there is no AME option because AME is not sold separately).
http://helpx.adobe.com/contact.html

AME Adobe Media Encoder Cuda GPU Acceleration not activated, How do I activate it

Mac Pro Early 2009 4.1, Processor 2.93 GHz Quad-Core Intel Xeon, Memory 16 GB 1066 MHz DDR3 ECC, Graphics NVIDIA GeForce GTX 680 2048 MB, Software OS X 10.9.2 (13C64)
Adobe CS6 suite up to date all programs as of 3-18-14
NVidia Cuda Driver 5.5.47 installed, Open CL and GL capable
I read this article http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-mercury-playback-engi ne-in-the-macbook-pro-retina/. it shows GPU acceleration through AME (see below). In my AME que window I do not see this

Todd:
(edit)
Just reread - sorry, CS6 vs CC.
What about AME CC?
http://blogs.adobe.com/kevinmonahan/2013/09/13/enabling-cuda-for-the-m ercury-playback-engine-in-the-macbook-pro-retina/
So, CUDA acceleration in AME and OpenCL is supported. Anyway to monitor this? I get FAILED when I try either (on a box with nVidia, or a box with AMD).
Found this: http://helpx.adobe.com/media-encoder/using/whats-new-media-encoder-7-1.html#gpu-accelerati on
GPU acceleration
Adobe Media Encoder now takes advantage of GPU for rendering purposes. Both CUDA and OpenCL are supported. The latest release of AME uses the GPU for the following renders:
Scaling (HD to SD; SD to HD)
Timecode filter
Pixel format conversions
Deinterlacing
Aspect ratio changes
All effects in the Effects tab
GPU accelerated effects in Premiere Pro
If you are rendering a Premiere Pro sequence, Adobe Media Encoder will use the GPU render preference you have set for the project. All GPU rendering capabilities of Premiere Pro are utilized.The limited set of GPU renderable tasks in Adobe Media Encoder is only for renders that originate in Adobe Media Encoder.
If you are rendering a sequence with native sequence support, the GPU setting in AME is used and the project setting is ignored. In this case, all GPU rendering capabilities of Premiere Pro are utilized directly in AME.
If your project uses 3rd party VSTs (Virtual Studio plugins), the GPU setting in the project is used. The sequence is encoded through headless Premiere Pro just as in earlier versions of Adobe Media Encoder. If Enable Native Premiere Pro Sequence Import option is unchecked, headless Premiere Pro will always be used and the GPU setting is used.

Adobe Media Encoder CS5 の SideBySideエラー

win7 64bit　にて　CS5マスコレをインストールしていますが、
Adobe Media Encoder CS5 の起動時にイベントビューワーにて以下の　SideBySideエラーが必ず出ます。
知人のwin8.1 64bitでも同じような状態です。
ログの名前:         Application
ソース:           SideBySide
日付:            2013/12/22 0:38:12
イベント ID:       75
タスクのカテゴリ:      なし
レベル:           エラー
キーワード:         クラシック
ユーザー:          N/A
コンピューター:       asrock-z68
説明:
"C:\Program Files\Adobe\Adobe Media Encoder CS5\PhotoshopServer.exe" のアクティブ化コンテキストの生成に失敗しました。マニフェストまたはポリシーファイル "C:\Program Files\Adobe\Adobe Media Encoder CS5\PhotoshopServer.exe" 行 2 のエラーです。マニフェストで複数の requestedPrivileges 要素を使用することはできません。
イベント XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="SideBySide" />
    <EventID Qualifiers="49409">75</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2013-12-21T15:38:12.000000000Z" />
    <EventRecordID>14166</EventRecordID>
    <Channel>Application</Channel>
使用に差し支えはありませんが、（あまり使っていないので気がついてないだけかもしれませんが）
このエラーの解消法についてご存じの方おられますか？それとも放っておいても良い物でしょうか？

PhotoshopServer.exe　の削除でとりあえずエラーは出なくなりました。

Adobe Media Encoder CS 5.5.

What has Adobe Media Encoder CS 5.5, got to do with Exporting iMovies? It is now stopping the Export of a 5 hour .Mov = 40 hours of wasted time, sofar!
Never experienced it before - before Lion. There is a queue of 6 attempts which I didn't see till now, because the Menu came up behind the iMovie screen.
Everything is either Waiting or Failed.
How do I dump this twit idea?
Ted

The time came up and then the normal 20 hours extra message - that came down to 2 hours in about 2 minutes, Still says 2 hours but counting. In the mean time I've found the Encoder in my Applications and deposited it in the Trash till after this game is finished.
BUT something VERY strange came up. To take up some of the time I opened a regular Joke file that comes to me. Knew the joke so opened my Star Sign, this is what it said:
Aquarius
Sunday, February 24, 2013
You can rely on powerful allies to lead you in the right direction today. However, don't expect others to sugarcoat what they tell you. If you have to swallow a bitter pill of reality, then do it as gracefully as possible. There's no need to make anything look better than it actually is now, since whatever isn't working should just be set aside. Instead of wasting energy on an outdated plan, consider creating a brilliant new one, altogether.
Isn't that exactly the right philosophy for the Support Community?
Thank you 'powerful allies'.
Ted

Adobe media encoder error in photoshop

Hi everyone!This morning i have tried to render a video timelapse in photoshop but it showed to me an error which says:''Could not complete the render video command because of a problem with Adobe Media Encoder''.Could anyone tell me how can i fix this error?

Nobody can tell you anything without proper system info or other technical details like exact versions, render settings, details about the source files and so on.
Mylenium

Adobe media encoder cc has encountered an error

can anyone help me about some problems with adobe media encoder cc ??
adobe media encoder cc has encountered an error
command.cpp-3302
THIS IS NEW CRASH WHEN I TRY TO EXPORT MPEG2 VIDEO

FAQ: What information should I provide when asking a question on this forum?

Revenir à Adobe Media Encoder 2013 ?

Similar Messages

Maybe you are looking for