MEDIE ENCODER, TARGAS & ÜBERWACHTE ORDNER

Tacchen Adobe Community,
ich bin derzeit auf der Suche nach einem Weg, mit Hilfe der überwachten Ordner des Media Encoders, Targa Sequenzen direkt nach Abschluß des Renderings aus 3Ds MAX in h264 (MP4) umzuwandeln.
Würde gerne anstatt der 9000px x 900px großen Targas, MP4s mit 1/4 auflösung als Preview und Stellvertreter Dateien verwenden.
Ist der Media Encoder in der Lage ein abgeschloßenes Rendering einer Sequenz zu erkennen?
Gibt es im Media Encoder einen Weg .IFL (Wird von 3DSMAX erstellt und enthält meines Wissens Informationen über Dimension, Status etc. der Sequenz) Dateien zu importieren?
Bin auch für alle anderen Zeitsparenden Wege dieser Konvertierung offen!
LG
MH

IFL ist tot. Die letzte Premiere Pro/ After Effects Version, die das unterstützt hat, war CS2/ AE7. Ansonsten fällt mir zu dem Thema nur "Nööööh" ein - AME ist einfach zu dämlich und kann nicht zeitgesteuert sowas überprüfen.
Mylenium

Similar Messages

Premiere Pro CC 2014 and Medie Encoder CC 2014 problem

Hello there,
Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing problems with the New Mac Pro. Is that true? Or is there other issue?
Thank you and looking forward to hear back,
Maruf

I am having a similar problem.
Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
My timeline is 2K, 58 minutes in 23.976
Only effects applied are Lumetri LUTs - no third party.
I've exported as recently as a week ago without issue.
Running OSX 9.5 on an X99 board
3.75 GHz 8-core
64GB 2400 MHz RAM
EVGA Titan Black 6GB
Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
Thanks Adobe, for checking this out.

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.

Encoding options

Hello,
I am working in Premiere 5.5 on some content that is headed for the web.
Currently, in order to produce a video that works on all platforms and mobile devices - I have to take the video rendered from Premiere thru meda encoder and run it thru the program HandBrake to get it to play across the board.
I am wondering if there is a preset in the H.264 format that will allow me to make a video for all platforms and mobile devices without using Handbrake - essentially eliminating this extra step.
Also - is there a suggested frame size for mobile devices? web pages?
Thanks!
Ted

Have you tried the Media Encoder H.264 presets? It does really good job of setting the correct Level and Profile for devices. (Although it uses Baseline level for iPhone, which is clearly capable of playing Main)
Also, Quicktime X Player "Save for Web…" automatically makes three h264 movies for iPhone WiFi, iPhone 3G, and Computer. As well as the HTML code to embed it into your website and to play back the correct version according to how the device is accessing your movie.

Problem mit der weitergabe einer Sequenz von Permiere an den Media Encoder

Wenn ich in Premiere Pro CC 2014 eine mov-Datei mit HD 1440*1080, prog. Pixelseitenverhältnis 1,333 importiere und in eine dementsprechende Sequenz einfüge, diese dann als h.264 exportiere ist alles in Ordnung, ich erhalte das gewünschte Ergebnis. Gebe ich diese Sequenz jedoch an die Warteliste des Media Encoders weiter erhalte ich eine Datei die rechts und links schwarze Balken aufweist. Wenn ich vor der Weitergabe an die Warteliste das importierte File mit Filmmaterial interpretieren bearbeite und dort, obwohl mit dem automatisch HD Anamorpisch 1080 (1,333) als zu verwenden ausgewählt, wähle, erfolgt das gleiche falsche Ergebnis mit den Balken rechts und links. Wähle ich jedoch händisch, Angleichen an HD Anamorpisch 1080 (1,333), dann funktioniert die Weitergabe an den Medi Encoder und ich bekomme das gleich Ergebnis wie beim Export aus Premiere. Handelt es sich hier um einen Bug oder mache ich etwas verkehrt. Die Logik will es mir nicht erklären aber vieleicht habt ihr ja einen Vorschlag wie ich diesen lästigen Zwischenschritt umgehen kann. Zumal man erst erkennt das was nicht stimmt wenn der Media Encoder mit der Wandlung fertig ist.
Manuel

Logik? Seit wann haben Adobe-Programme was mit Logik zu tun? *lol* Ja, vermutlich wieder irgendein beknackter Bug. Solange dein Workaround funktioniert, ist ja lles in Ordnung.
Mylenium

HDV export to H.264 jittery within Media Encoder

I'm rendering out a 50 minute documentary shot and edited in HDV 60i. I did it within Premeire Pro CS4 using Adobe Media Encoder CS4. First I exported it as a Quicktime H.264 1920x1080 29.97 progressive video. The video looks PERFECT, and is 31GB.
Trying to get the video file to less than 4.7 gb to burn onto a dvd as a image file, I then exported both the PP timeline and the QT H.264 file in Meda Encoder to the MP4 H.264 1920x1080 29.97 progressive and it came out to 4.5 GB. The image quality looks good, but scences that have a lot of movement the video is noticably jittery. The reason I want this encode to work is because I would like to be able to burn the HD image file to DVD to distribute along with the regular SD DVD. Does anybody know why it's jittery? Is there a setting I have to change? Is there another Codec someone could recomend to get me under 4.7 HD while keeping the full HD quality?
Funny thing is if I play the jittery MP4 H.264 though my Western Digital HD player (plays 1080 movies off a portable usb hard drive to a television monitor up to 1080p via HDMI cable) it plays perfect, no jitters. But if I burn the same file to dvd and open on another computer (after copy/paste to hard drive) it is jittery.
Thanks for the help!!

Ryan,
Please submit a bug report here:
http://adobe.ly/ReportBug
I agree with you that the error message should be more helpful, and I consider the fact that the existing error message is misleading to be a bug.

Flash media 8 encoder missing

since i installed the new medi encoder. the flash pro media
ecoder 8 will not launch. (looking for installer msi) wha's up? I
want the old one back with all the non eta, non live encoding
controls

These two applications, while similar in name, do not have
any reliance on each other. Installing the Flash Media Encoder will
not effect the Flash 8 Video Encoder and vice versa.

Premiere Pro CS5 zeigt beim Exportieren von Medien Hinweisfenster

Hallo @ll,
heute habe ich in Premiere Pro CS5 meinen ersten Film bearbeitet. Als ich den Film exportieren wollte unter Datei --> Exportieren --> Medien, geht als erstes ein Hinweisfenster auf. "Für diese Version von Premiere Pro ist ein Adobe Media Encoder-Update verfügbar. Um das neuste Update herunterzuladen, starten Adobe Updater über das Hilfemnü oder besuchen Sie die Seite xxxxxxx Update Seite von Adobe.
Ich habe aber alle Programme von CS5 auf den neusten Stand. Adobe Premiere Pro Version 5.0.3 und Adobe Medi Encoder Version 5.0.1.0 64 bit.
Wenn ich auf OK klicke schließt sich das Fenster und ich kann, wenn denn Adobe Premiere Pro nicht abstürzt, den Film exportieren.
Mein System ist Windows 7 Ultimate 64 bit, Speicher 12 GB.
Kann mir evtl jemand helfen wie ich das Hinweisfenster abgeschaltet bekomme.
Viele Dank im voraus.
Gruß Burghard

Hallo Carlos,
den Fehler kannst du wie folgt beheben.
Gehe in den Ordner wo Adobe Media Encoder liegt. Bei mir ist es C:/Program Files/Adobe/Adobe Media Encoder.
Erstelle vom Media Encoder Programm eine Verknüpfung auf dein Desktop. Diese Verknüpfung kopierst du dann direkt in den Ordner von Adobe Premiere Pro CS5. Die Verknüpfung vom Desktop kannst du danach wieder löschen.
Dann funktioniert alles und Adobe Premiere Pro CS5 startet ohne diese Meldung.
Der Fehler muss bei mehreren aufgetreten sein. Adobe hat extra dafür ein Ticket eröffnet.
Ich hoffe ich konnt dir helfen.
Gruß Burghard

CS4, reverting to CS3 (and getting a refund!) but still interested in opinions

I've just spent the last 24 hours trying to muscle my way through the myriad of problems I'm finding with CS4. I've managed to alleviate some, but still can't produce my end video.
To start off, I'm running on Windows Vista. All the problems seem to centre around Media Encoder (although I didn't get far enough to play with Encore or On Location).
Initial problems where to do with installation. If CS3 is removed after CS4 is installed the link to Media Encoder fails, you then have to removed CS4 and reinstall. Uninstall doesn't work correctly or completely, it leaves a fair amount of files behind that have to be manually removed, failure to do so resulst in Error 2 on reinstall (I'm guessing because the install tries to create some of the working directories, and fails because they are already there?).
After reinstallation, the job appeared correctly in Medie Encoder when it was fired up from Export in PP, and it was also now possible to add files to Encoder directly. I tried a test run of my project with the following settings:
H264
Width : 1280
Height : 720
fps : 25
Field order : Progressive
Quality : 4.0 and 5.1 (tried to runs)
Bit rate : can't remember, but atleast 12M for target and perhaps 30M for max?
VBR 2 pass
Sound : AAC
The end video was incredibly jerky.
I tried a second time using the following settings:
Quicktime
Codec : H264
Quality : 100
Width : 1280
Height : 720
fps : 25
Field Order : progressive
Pixel Aspect : square
Use maximum bit depth ticked
Bit rate : 1k (I tried to move this to 5k however it kept reverting back)
Sound : AAC
Export from PP initially failed, the job appeared in the queue, however nothing actually happened, it just sat there. I read on another post that updating Quicktime to 7.5.5 fixes that (does PP rely on Quicktime for the codec?), tried and the job then started.
Upon completion, the video played smoothly, although quality was low (low bit rate?). However the video to audio sychronisation was completely out. 30 seconds of play, and the sound was around a second behind the video.
I then tried applying all of the updates. As with other people, the Encoder portion failed initially (even though I started the update process from Encoder), but then succeeded the second time.
Upon completion of the updates, the problem reverted back to the initial, i.e. the job started OK, but didn't actually do anything.
The render settings I'm using are required by the web site I'm trying to create this video for, and also worked without issue in CS3.
It would seem to me that the Media Encoder portion in CS4, on the Windows version atleast, is seriously flawed (and no, I'm not going to buy a MAC ;-)).
I would like some answers to these problems, despite all the issues, I did like the overall look and feel of the product compared to CS3, and I also now need the AVCHD support.
Forgive any innacuracies in the phrases used, settings etc, CS4 has been removed from my system for now, so it was all from memory.

Stuart,
Maybe I'm just too old and have seen too many "revolutions," to get onto that wagon.
However, the more I follow CS4 threads, the more I am starting to question whether I will upgrade from CS2, or not. Some things look useful to me (more than with CS3), but then there are the problems.
Adobe IS listening, as evidenced by a few of the folk on the team dropping by to give info on updates, etc. Having some major "fixes" so soon upon release, indicates to me, that they are working on it.
I didn't move to CS3 for similar reasons. Also, it really did not offer ME much in the way of useful features.
Whether it's through bug reports, posts in the forum or direct correspondence with Adobe, the best way to get their attention, and provide them with useful data, is to offer as much detail on the specific problem(s) as one can and demonstrate repeatability. General posturing might make one feel better, but does little to get improvements in the program.
As you state, some of the problems are probably OE. Some are system specific, and others are related to 3rd party software. Still, there do seem to be a lot of issues that ARE CS4-specific. These worry me. These are the issues that I would like to see Adobe address. So far, they seem to be, albeit maybe not quickly and efficiently enough for many users. CS4 does seem to be more of a "work in progress," than I am willing to take on just yet, especially as it would also likely mean a new workstation and new OS (one that is not without some problems of its own and a new learning curve also).
I'm fortunate enough to have CS2 and a rock-solid group of systems to use it on. It does 95% of what I'd like for it to do, and that extra 5% has yet to intice me, especially with the "problems" that I've been reading about.
As for the Adobe faces in the forum, they have shown up, when they could actually tell us something. I view that as a very positive sign. Even when they have dropped in, too many people demand to know "WHEN?" something will be fixed. If they knew, they'd tell us.
I'm sorry that CS4 has not gone more smoothly, upon release. It saddens me greatly. However, it is also why I will be waiting and keep reading. For me, this will be an upgrade that will be very expensive, because it's not just the software. I hope that Adobe does get it all running and running smoothly.
I would anticipate, and hope, that the next update fixes most of the issues. I anticipate, and hope, that Adobe will provide us with the same sort of info on it, as they have done with 4.0.1 & AME's update. I also hope that the forum subscribers will concentrate on the info provided and cease with the "WHEN?" The Adobe posters do not know yet, as the coders are still working on it. It *seems* that rushing to meet a product release date might have gotten us into this trouble to begin with.
My fingers are all crossed. Maybe 4.0.2 will signal that it's time for me to make the jump.
Hunt

Settings for web straeming

I need to get good settings for web streaming, and for seeking to work with mp4-files.
If I use Handbrake to encode video (H.264 MP4) and check the box "Web optimized" the seeking works, but if I use Meda Encoder settings it does not. ME has no "web optimized" as far as I can see - is it another setting in PP CC or ME CC I should use to get the same result? (In Handbrake the "web optimize"
places the container header at the start of the file, optimizing it for streaming across the web (fast-start))
Thanks in advance for any suiggestion!
/Håkan

From the CS5 user guide PDF
Stream for best performance
You can stream FLV and F4V files to eliminate download time. FLV and F4V files also have deep interactivity and navigation capabilities when they are streamed. Streaming FLV and F4V files allow you to monitor quality of service. You can stream FLV and F4V files with the Flash Media Server. Alternatively, you can use a hosted service from one of the FLV/F4V Streaming Service partners available through the Adobe website. For more information, see "Delivering Flash Video: Understanding the Difference Between Progressive Download and Streaming Video" on the Flash Developer Center website.

Media encoder CC x86

Bonjour, je recherche une version d'adobe media encoder CC mais en 32 bit, j'ai bien la version 64 bit mais il n'y a pas moyen de la lancer comme d'ailleurs les version 64bit de indesign/illustrator/lightroom... y a que photoshop qui fonctionne en 64bit chez moi!
J'ai cherché dans la page téléchargement d'adobe mais je ne trouve que la version 64bit. Donc si quelqu'un a un lien ou une solution je suis preneur.
merci a vous, bon aprém.

merci de votre réponse rapide, le contenu de l'info-système de photoshop CC x64 :
Version Adobe Photoshop : 14.2.1 (14.2.1 20140207.r.570 2014/02/07:23:00:00) x64
Système d'exploitation : Windows 7 64 bits
Version : 6.1 Service Pack 1
Architecture système : UC Intel Famille :6, modèle :10, niveau :7 avec MMX, SSE Entier, SSE FP, SSE2, SSE3, SSE4.1, SSE4.2, HyperThreading
Nombre de processeurs physiques : 4
Nombre de processeurs logiques : 8
Vitesse du processeur : 3392 MHz
Mémoire intégrée : 8087 Mo
Mémoire libre : 4116 Mo
Mémoire disponible pour Photoshop : 7074 Mo
Mémoire utilisée par Photoshop : 60 %
Taille de la mosaïque d'images : 1024K
Niveaux de mémoire cache de l'image : 4
Aperçu de la police : Moyenne
Compositeur de texte : Latin
Affichage : 1
Limites d'affichage : haut = 0, gauche = 0, bas = 1080, droite = 1920
Affichage : 2
Limites d'affichage : haut = 48, gauche = 1920, bas = 948, droite = 3360
Affichage : 3
Limites d'affichage : haut = 180, gauche = 3360, bas = 948, droite = 4720
Dessin OpenGL : Activé.
Anciens GPU OpenGL autorisés : Non détectés.
Mode de dessin OpenGL : Avancé
Mode OpenGL normal autorisé : Vrai.
Mode OpenGL avancé autorisé : Vrai.
AIFCoreInitialized=1
AIFOGLInitialized=1
OGLContextCreated=1
NumGPUs=2
gpu[0].OGLVersion="3.0"
gpu[0].MemoryMB=1024
gpu[0].RectTextureSize=16384
gpu[0].Renderer="GeForce GTX 555/PCIe/SSE2"
gpu[0].RendererID=4614
gpu[0].Vendor="NVIDIA Corporation"
gpu[0].VendorID=4318
gpu[0].HasNPOTSupport=1
gpu[0].DriverVersion="9.18.13.3788"
gpu[0].Driver="nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um"
gpu[0].DriverDate="20140519000000.000000-000"
gpu[0].CompileProgramGLSL=1
gpu[0].TestFrameBuffer=1
gpu[0].OCLPresent=1
gpu[0].OCLVersion="1.1"
gpu[0].CUDASupported=1
gpu[0].CUDAVersion="6.0.1"
gpu[0].OCLBandwidth=7.46599e+010
gpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.40 NVIDIA via Cg compiler"
gpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[16384]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
gpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
gpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
gpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
gpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
gpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
gpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
gpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
gpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
gpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
gpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
gpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1
gpu[1].OGLVersion="3.0"
gpu[1].MemoryMB=2108
gpu[1].RectTextureSize=16384
gpu[1].Renderer="GeForce GTX 555/PCIe/SSE2"
gpu[1].RendererID=258
gpu[1].Vendor="NVIDIA Corporation"
gpu[1].VendorID=32902
gpu[1].HasNPOTSupport=1
gpu[1].DriverVersion="9.17.10.3347"
gpu[1].Driver="igdumd64.dll,igd10umd64.dll,igd10umd64.dll,igdumd32,igd10umd32,igd10umd32"
gpu[1].DriverDate="20140129000000.000000-000"
gpu[1].CompileProgramGLSL=1
gpu[1].TestFrameBuffer=1
gpu[1].OCLPresent=1
gpu[1].OCLVersion="1.1"
gpu[1].CUDASupported=1
gpu[1].CUDAVersion="6.0.1"
gpu[1].OCLBandwidth=7.47211e+010
gpu[1].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.40 NVIDIA via Cg compiler"
gpu[1].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[16384]
gpu[1].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]
gpu[1].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]
gpu[1].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]
gpu[1].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]
gpu[1].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]
gpu[1].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]
gpu[1].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[2048]
gpu[1].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]
gpu[1].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]
gpu[1].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1
gpu[1].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1
gpu[1].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1
gpu[1].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1
gpu[1].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1
gpu[1].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1
gpu[1].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1
gpu[1].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1
gpu[1].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1
gpu[1].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1
Type de licence : Abonnement
Numéro de série : 90970196649322984791
Dossier de l'application : C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\
Chemin des fichiers temporaires : C:\Users\mickael\AppData\Local\Temp\
Le disque de travail de Photoshop comporte l'E/S asynchrone activé.
Volume(s) de travail :
C:\, 930,3 Go, 321,0 Go libres
Dossier des modules externes obligatoires : C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Required\Plug-Ins\
Dossier principal des modules externes : C:\Program Files\Adobe\Adobe Photoshop CC (64 Bit)\Plug-ins\
Composants installés :
   ACE.dll   ACE 2013/10/29-11:47:16   79.548223   79.548223
   adbeape.dll   Adobe APE 2013/02/04-09:52:32   0.1160850   0.1160850
   AdobeLinguistic.dll   Adobe Linguisitc Library   7.0.0
   AdobeOwl.dll   Adobe Owl 2013/10/25-12:15:59   5.0.24   79.547804
   AdobePDFL.dll   PDFL 2013/10/29-11:47:16   79.508720   79.508720
   AdobePIP.dll   Adobe Product Improvement Program   7.0.0.1786
   AdobeXMP.dll   Adobe XMP Core 2013/10/29-11:47:16   79.154911   79.154911
   AdobeXMPFiles.dll   Adobe XMP Files 2013/10/29-11:47:16   79.154911   79.154911
   AdobeXMPScript.dll   Adobe XMP Script 2013/10/29-11:47:16   79.154911   79.154911
   adobe_caps.dll   Adobe CAPS   7,0,0,21
   AGM.dll   AGM 2013/10/29-11:47:16   79.548223   79.548223
   ahclient.dll    AdobeHelp Dynamic Link Library   1,8,0,31
   aif_core.dll   AIF   5.0   79.534508
   aif_ocl.dll   AIF   5.0   79.534508
   aif_ogl.dll   AIF   5.0   79.534508
   amtlib.dll   AMTLib (64 Bit)   7.0.0.249 BuildVersion: 7.0; BuildDate: Thu Nov 14 2013 15:55:50)   1.000000
   ARE.dll   ARE 2013/10/29-11:47:16   79.548223   79.548223
   AXE8SharedExpat.dll   AXE8SharedExpat 2011/12/16-15:10:49   66.26830   66.26830
   AXEDOMCore.dll   AXEDOMCore 2011/12/16-15:10:49   66.26830   66.26830
   Bib.dll   BIB 2013/10/29-11:47:16   79.548223   79.548223
   BIBUtils.dll   BIBUtils 2013/10/29-11:47:16   79.548223   79.548223
   boost_date_time.dll   DVA Product   7.0.0
   boost_signals.dll   DVA Product   7.0.0
   boost_system.dll   DVA Product   7.0.0
   boost_threads.dll   DVA Product   7.0.0
   cg.dll   NVIDIA Cg Runtime   3.0.00007
   cgGL.dll   NVIDIA Cg Runtime   3.0.00007
   CIT.dll   Adobe CIT   2.1.6.30929   2.1.6.30929
   CITThreading.dll   Adobe CITThreading   2.1.6.30929   2.1.6.30929
   CoolType.dll   CoolType 2013/10/29-11:47:16   79.548223   79.548223
   dvaaudiodevice.dll   DVA Product   7.0.0
   dvacore.dll   DVA Product   7.0.0
   dvamarshal.dll   DVA Product   7.0.0
   dvamediatypes.dll   DVA Product   7.0.0
   dvaplayer.dll   DVA Product   7.0.0
   dvatransport.dll   DVA Product   7.0.0
   dvaunittesting.dll   DVA Product   7.0.0
   dynamiclink.dll   DVA Product   7.0.0
   ExtendScript.dll   ExtendScript 2013/10/30-13:12:12   79.546835   79.546835
   FileInfo.dll   Adobe XMP FileInfo 2013/10/25-03:51:33   79.154511   79.154511
   filter_graph.dll   AIF   5.0   79.534508
   icucnv40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   icudt40.dll   International Components for Unicode 2011/11/15-16:30:22    Build gtlib_3.0.16615
   imslib.dll   IMSLib DLL   7.0.0.145
   JP2KLib.dll   JP2KLib 2013/10/29-11:47:16   79.248139   79.248139
   libifcoremd.dll   Intel(r) Visual Fortran Compiler   10.0 (Update A)
   libiomp5md.dll   Intel(R) OMP Runtime Library   5.0
   libmmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0
   LogSession.dll   LogSession   2.1.2.1785
   mediacoreif.dll   DVA Product   7.0.0
   MPS.dll   MPS 2013/10/29-11:47:16   79.535029   79.535029
   msvcm80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcm90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcp100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcp80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcp90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   msvcr100.dll   Microsoft® Visual Studio® 2010   10.00.40219.1
   msvcr80.dll   Microsoft® Visual Studio® 2005   8.00.50727.6195
   msvcr90.dll   Microsoft® Visual Studio® 2008   9.00.30729.1
   PatchMatch.dll   PatchMatch 2013/10/29-11:47:16   79.542390   79.542390
   pdfsettings.dll   Adobe PDFSettings   1.04
   Photoshop.dll   Adobe Photoshop CC   CC
   Plugin.dll   Adobe Photoshop CC   CC
   PlugPlugOwl.dll   Adobe(R) CSXS PlugPlugOwl Standard Dll (64 bit)   4.2.0.36
   PSArt.dll   Adobe Photoshop CC   CC
   PSViews.dll   Adobe Photoshop CC   CC
   SCCore.dll   ScCore 2013/10/30-13:12:12   79.546835   79.546835
   ScriptUIFlex.dll   ScriptUIFlex 2013/10/30-13:12:12   79.546835   79.546835
   svml_dispmd.dll   Intel(r) C Compiler, Intel(r) C++ Compiler, Intel(r) Fortran Compiler   12.0
   tbb.dll   Intel(R) Threading Building Blocks for Windows   4, 1, 2012, 1003
   tbbmalloc.dll   Intel(R) Threading Building Blocks for Windows   4, 1, 2012, 1003
   updaternotifications.dll   Adobe Updater Notifications Library   7.0.1.102 (BuildVersion: 1.0; BuildDate: BUILDDATETIME)   7.0.1.102
   WRServices.dll   WRServices Mon Feb 25 2013 16:09:10   Build 0.19078   0.19078
Modules externes obligatoires :
   3D Studio 14.2.1 (14.2.1 x001)
   Aérographe 14.2.1
   Aplatissement 14.2.1 (14.2.1 x001)
   Aquarelle 14.2.1
   Asymétrie 14.2.1 (14.2.1 x001)
   Barbouillage 14.2.1
   Bas-relief 14.2.1
   BMP 14.2.1
   Camera Raw 8.4.1
   Carrelage 14.2.1
   Chrome 14.2.1
   Cineon 14.2.1 (14.2.1 x001)
   Cisaillement 14.2.1
   Collada 14.2.1 (14.2.1 x001)
   CompuServe GIF 14.2.1
   Contour accentué 14.2.1
   Contour déchiré 14.2.1
   Contour encré 14.2.1
   Contour lumineux 14.2.1
   Contour postérisé 14.2.1
   Contraction 14.2.1
   Coordonnées polaires 14.2.1
   Correction de l'objectif 14.2.1
   Couleurs NTSC 14.2.1 (14.2.1 x001)
   Couteau à palette 14.2.1
   Craie/Fusain 14.2.1
   Craquelure 14.2.1
   Crayon Conté 14.2.1
   Crayon de couleur 14.2.1
   Cristallisation 14.2.1
   Croisillons 14.2.1
   Découpage 14.2.1
   Demi-teintes couleur 14.2.1
   Désentrelacement 14.2.1
   Diagonales 14.2.1
   Dicom 14.2.1
   Dispersion 14.2.1
   Eazel Acquire 14.2.1 (14.2.1 x001)
   Ecart type 14.2.1 (14.2.1 x001)
   Effet mosaïque 14.2.1
   Effet pointilliste 14.2.1
   Emballage plastique 14.2.1
   Enregistrer pour le Web 14.2.1
   Entropie 14.2.1 (14.2.1 x001)
   Eponge 14.2.1
   Etalement 14.2.1
   Extension WIA 14.2.1 (14.2.1 x001)
   Extrusion 14.2.1
   Fibres 14.2.1
   Filtre Camera Raw 8.4.1
   Filtre Collection d'images 14.2.1 (14.2.1 x001)
   Filtre Rogner et désincliner les photos 14.2.1
   Flash 3D 14.2.1 (14.2.1 x001)
   Flou de l'objectif 14.2.1
   Flou optimisé 14.2.1
   Flou radial 14.2.1
   Fluidité 14.2.1
   Format IFF 14.2.1
   Fresque 14.2.1
   Fusain 14.2.1
   Galerie de filtres 14.2.1
   Google Earth 4 14.2.1 (14.2.1 x001)
   Grain 14.2.1
   Grain photo 14.2.1
   Grand-angle adaptatif 14.2.1
   Halo 14.2.1
   HDRMergeUI 14.2.1
   Insertion filigrane 4.0
   JPEG 2000 14.2.1
   Lecture filigrane 4.0
   Lueur diffuse 14.2.1
   Matlab Operation 14.2.1 (14.2.1 x001)
   Maximum 14.2.1 (14.2.1 x001)
   Médiane 14.2.1 (14.2.1 x001)
   Mezzo-tinto 14.2.1
   Minimum 14.2.1 (14.2.1 x001)
   Moteur 3D Photoshop 14.2.1 (14.2.1 x001)
   Moyenne 14.2.1 (14.2.1 x001)
   Moyenne 14.2.1 (14.2.1 x001)
   Multiprocesseur 14.2.1 (14.2.1 x001)
   Néon 14.2.1
   Noir/Blanc 14.2.1
   Noyau de mesures 14.2.1 (14.2.1 x001)
   Nuages 14.2.1 (14.2.1 x001)
   Nuages par différence 14.2.1 (14.2.1 x001)
   Océan 14.2.1
   Onde 14.2.1
   Ondulation 14.2.1
   OpenEXR 14.2.1
   Papier gaufré 14.2.1
   Papier humide 14.2.1
   Pastels 14.2.1
   Patchwork 14.2.1
   PCX 14.2.1 (14.2.1 x001)
   Peinture à l'huile 14.2.1
   Photocopie 14.2.1
   Photoshop Touch 14.0
   Pinceau à sec 14.2.1
   Pixar 14.2.1 (14.2.1 x001)
   Placage de texture 14.2.1
   Plâtre 14.2.1
   Plume calligraphique 14.2.1
   PNG 14.2.1
   Point de fuite 14.2.1
   Pointillisme 14.2.1
   Portable Bit Map 14.2.1 (14.2.1 x001)
   Portée 14.2.1 (14.2.1 x001)
   Radiance 14.2.1 (14.2.1 x001)
   Réduction du tremblement 14.2.1
   Réticulation 14.2.1
   Rogner et désincliner les photos 14.2.1 (14.2.1 x001)
   Routines FastCore 14.2.1 (14.2.1 x001)
   Routines MMXCore 14.2.1 (14.2.1 x001)
   Solarisation 14.2.1 (14.2.1 x001)
   Sommation 14.2.1 (14.2.1 x001)
   Soufflerie 14.2.1
   Sous-couche 14.2.1
   Sphérisation 14.2.1
   STL 14.2.1 (14.2.1 x001)
   Sumi-e 14.2.1
   Support de script 14.2.1
   Tampon 14.2.1
   Targa 14.2.1
   Tourbillon 14.2.1
   Tracés vers Illustrator 14.2.1
   Trame de demi-teintes 14.2.1
   Variance 14.2.1 (14.2.1 x001)
   Variantes 14.2.1 (14.2.1 x001)
   Verre 14.2.1
   Vitrail 14.2.1
   Wavefront|OBJ 14.2.1 (14.2.1 x001)
   Wireless Bitmap 14.2.1 (14.2.1 x001)
   Zigzag 14.2.1
Dossier des modules externes tiers et facultatifs :
   PSHostAdapter NO VERSION
Modules externes dont le chargement a échoué : AUCUN
Flash :
   Ink
   Mini Bridge
   Prisma
   Adobe Exchange
Modules TWAIN installés : AUCUN

Adobe Media Encoder CC constantly crashing during batch encodes

Hello!
We just made the big switch to Premiere Pro CC for our TV shows and now that it's time to finalize our first few episodes we are having some major problems batch exporting segments of the show. Sometimes it works, sometimes it works half way through the batch list then crashes, sometimes it crashes right away. There is no consistency, other than crashes are happening all the time. Here's what is happening:
• AME 7.2.0.43 (64-bit)
• Mac OS X 10.9.1 on 2x2.66 GHx 6-Core Intel Xeon, 40 GB 1333MHz DDR3 RAM
• Startup disk is SSD w/ 4GB free space (all footage is on external storage)
• Using Premiere Pro CC to export via AME.
• All recent updates insatlled as of 3/10/14.
The source footage is ProRes 422 720p 59.94 footage from AJA KiPros. Each project has 16 segments - these are individual sequences. There are 7 tracks of audio and 4-5 tracks of video in each. In addition to the video there are targa files that include the score bug, full screen graphics, etc (this is sports). There are also some Adoby Dynamic Link After Effects elements throughout.
Editing has been fairly crashless - however when I File > Export > Media and queue it up in AME, that's when the fun starts.
I can rarely get through an entire batch list - generally within a few files the preview window at the bottom shows that it has halted and nothing further will encode. There is no way to stop or close the program without force quitting. When I have tried to encode from Premiere Pro CC directly, it works, although it is much slower and will only do the one sequence at a time.
I have been trying to encode to two different formats from within AME:
1.) ProRes 422 720 59.94 (just like the source footage) with 4 channels of audio.
2.) ProRes 422 1080i29.97 with 4 channels of audio.
We have different broadcast partners so we need to deliver in these two difference specs. I get crashes regularly on both outputs.
Possibly unrelated but also weird - I've noticed that when AME starts this crashing cycle sometimes Premiere CC won't let me save anyome. The status bar comes up like it's going to save the project but it goes nowhere. I have to quit without saving. Weird.
Can anyone help me further troubleshoot? This is bordering near deal breaker to continue using this software if I have this much trouble when trying to get my project outputted. Thank you!

Agreed, I now have a project to GET OUT, and AME crashes consistently 1/3 into the render. It appears to halt all processing after (real time) 00:02:30
Am seriously considering uninstalling CC as I am beginning to find other issues in some apps, and going back to CS6/MC just so I can get work out. Durn it Adobe this is AWFUL!!
Alright, let's try to be constructive instead of throwing rocks... but the frustration level is high, and I have material on deadline. Let's get with this, guys...
What OS Win7, 64-bit
What version of AME/PPro (Please be specific by getting the full version number in the About Adobe Media Encoder screen) 8.2.0.54 Ppro: 8.2.0 (65)
When is it crashing (Again, the more detail here about where it was in the encoding process the better) roughly 1/3 into the sequence, always on exactly the same frame - tried replacing the clip with something different to see if it was a timeline error, and NO EFFECT.
What is your source (PPro project or media file (what kind?)) PPro
If the source if a PPro project, does it work when exporting directly from PPro? NO
What format are you exporting to? H.264, QT, WM, tried everything my client can play.
Do other formats work? MPEG2, QuickTime, etc? NO
Have you tried with GPU rendering on? How about turning it off by switching to Software-only mode? Mine doesn't have any choice, it's software-only.
Have you tried disabling Native Sequence Loading? (AME Preferences: General > Enable Native Sequence Loading) No effect
Other things I tried: uninstalling/reinstalling AME, setting cache to a fast local disk.

Adobe Media Encoder .. und CS4

Hallo liebe Adobler und Adobemacher,
ich muss jetzt gerade mal meinen Frust loswerden. Vorsichtig ausgedrückt:
Kotze seit Tagen mal mehr, mal weniger auf CS4 ab - und heute abend ist das Maß voll!!!!!
Habe den Megastress heute gehabt, möchte zum Abschluss ein leckeres Mpeg-1 aus Premiere exportieren,
was in der Version 2 nur ein paar Klicks war.
Naja, Media Encoder. Nun ja. Nachdem ich meine Einstellungen für Video und Audio gemacht habe, stelle ich fest,
dass das Mpeg-1 Multiplexing zwar einzustellen ist, aber bei der Übergabe sich verdammt noch mal immer wieder
auf "None" zurücksetzt. Also als Ausgabe Audio und Video seperat. Und die Erkenntnis, dass die Sch... sich immer
wieder zurücksetzt kostete mich jedesmal 2h Compositingzeit.
Sorry an der Stelle wegen den Gefühlsausbrüchen, aber das Problem war definitiv vorher nicht vorhanden, bzw. die Lösung
dafür ist mit einem lustigen Trick verbunden.
Für weiteres Comp sind zwei seperate Files ja willkommen, aber nicht für eine Preview beim Kunden, bei dem bei dem Format mpv oder mpa
ein Mega-Fragezeichen wächst.
Ok hab ich mir dann in der Not gesagt - exportier den Krams schön als Targa und Wave PCM und Comp die zwei Streams in nem
Programm, dass nicht so Zicken macht. Renderzeit wieder 1:37 h.
Beim Durchsehen sind mir etliche Fehler in den Einzelbilder aufgefallen, als ob bei verschiedenen Skalierungen von Footages AntialiazingFehler
aufgetreten sind. Fazit: Export wieder für die Tonne. Anscheinend Hat der Wegwünschenswerte Mediaexporter Probleme mit dem TGA-Export.
(Versteh eh nicht bis heute, warum man hier immer noch nicht die RLE-Kompr. wie bei AE aktivieren kann).
ALso nochmal ein Exportversuch mit BMP - Antializing- oder Skalierungsfehler sind weg. Mal sehen, was mich noch für Überraschungen
erwartet.
Die Probleme sind mit CS2 definit nicht aufgetreten. Warum ist z.B. die Funktion Doppelklick + STRG = Neues Dokument in Photoshop CS4
nicht mehr vorhanden, oder Rechtsklick auf den Dokumentenrahmen=Bildgröße etc.?????
Mag sein, dass man alles irgendwie einstellen kann - aber dann bin ich mal gespannt wo sich die Knöpfe verstecken
Gruß,
frustrierter LS

I could really use some help on this . . .
Could it be a codec is missing or something?
Does anyone know of another way I can get help if not from here?
Thanks.

Importing picture sequence in Media Encoder ? like in the help

If you look in this help document http://help.adobe.com/en_US/AdobeMediaEncoder/4.0/WS8A54CAA7-268E-4af0-B8A4-0EA3EACEC1A3.h tml
it says you can import TGA sequence and JPG sequence. From the document :
- JPEG and JPEG sequence (JPE, JPG, JFIF)
- Targa and Targa sequence (TGA, ICB, VDA, VST)
but I was unable to do that. You can drop a jpg file in MEdia Encoder and it will convert just fine - but only the first frame. How to load the entire sequence ?

I'm trying to import. When you're working with 3d graphics and rendering - the common work-flow would be to render a series of frames, a sequence. Many people work like this also even with normal footage.
Or some programs expect also a sequence. For example the software Nuke (commonly used for compositing in films like Watchmen and Avatar).
And because I think Adobe Media Encoder is one of the fastest encoders around I would like to use it to convert a sequence of JPG in a WMV or H264.
Since it can export a sequence of TGA or BMP it's only normal to expect that it can read also a sequence. And more so the Help says it can :
Supported still‑image formats :
JPEG and JPEG sequence (JPE, JPG, JFIF)
Targa and Targa sequence (TGA, ICB, VDA, VST)
But if I drag a JPEG file in the encoder - it reads only the first frame. Is there a special method to read the rest of the frames ? Maybe a script , or maybe I have to make a text file like a playlist ..or something.

External sample clock encoder

hello,
my problem is very urgent, I have to sample 3 analog input synchronised to an encoder. How can use the channel from the encoder and use them to generate a external sample clock for acuiring the analog signals?how can I phisically attache the wire from the encoder to the digital line?and how the vi should be??my encoder has A, Anot,B,Bnot channel, but eventually with a circuit I can get just A and B. I have a PCI6221.
Please is very urgent!!

Hi orsogna,
see the example Cont Acq&Graph Volt-Ext clock in the Labview Example Finder.
About wirings, you have to connect our encoder signal (A signal is good) to a PFI input in order to correctly read the TTL signal.
Ciao!
Simone S.
Academic Field Engineer - Med Region

MEDIE ENCODER, TARGAS & ÜBERWACHTE ORDNER

Similar Messages

Maybe you are looking for