Adobe Media Encoder - Premiere Pro SLOW Rendering

Hi, there
I've been using my laptop which has the specs: 2.8ghz intel core 2 extreme, 4gb DDR2 800mhz RAM, 8800m GTS 512mb.
Now, I've been able to export my videos from Premiere Pro on that machine roughly with a 1:5 time ratio, a 1 minute video might take 5 minutes to render, and no, I'm not complaining about the 5 minutes, please read down before you click off.
I've been exporting with these settings:
-h.264
-1280x720
-3.2
-24fps
-2.0 - 2.3mbps VBR 2 pass
-AAC, 128kbps, stereo, 44.1khz
Anyway... I just installed Master Collection onto my second computer which has the specs: 2.1ghz tri-core AMD Phenom, 4GB DDR2 1066mhz RAM, 9600 GT 512mb (not to mention a faster hard drive)
Now, with this superior machine, it is taking literally over two hours to render a ONE MINUTE video, I have no idea why, I'm using the same settings and have everything up to date.
I've also checked my processes, all three cores are maxed out, I've even adjusted the priority which makes a noticable but little difference.
Does anybody have any ideas?
Thanks a bunch in advance,
Chris

When I say render, I'm referring to rendering inside of Adobe Media Encoder - unless there is something I don't know when it comes to the setting you're referring to.
Also, yes, it has an animated logo - which I use on the other machine too, same exact animation.
As I was writing this response, I just disabled the logo animation - it renders in 4 minutes. However, I need this animation - I'm wondering what to do. It has a 4Kx2K png animated using the basic 3D effect and HLS effect - though, this doesn't delay rendering on my other computer!??
Hmm, thought of a fix though, I’ll render out my logo animation with a transparent channel, this way I just drag the scaled down animation on top of my videos, should improve the render time.

Similar Messages

  • Adobe media encoder cs4 extremely slow (5 hours for 8 minute video)

    I know you have seen slowencoder issues before, but I have tried everything I can to fix this and need help.
    Lets start with basic info:
    8 minute vieo takes over 5 hours to generate final video.
    Observations:  3 processes are running most of the time, with over 2GB memory left over and available, I/O is low, CPU is at 90 to 100 percent for hours during encode.
    PProHeadless.exe 48-50%
    Adobe Media Encoder.exe  30-40%
    ImporterProcessServer.exe  can be from 30-50% CPU but not constant.
    I live in San Jose, and am willng to take this laptop to your Office to debug it personally. (FYI)
    CS4: 4.2.1 with all updates applied
    ALL Encoder OUTPUT is set to a 128GB Solid State Drive drive so there are very low delays on I/O: SAMSUNG MMCRE28G8MXP-0VB.
    This setting is in the general disk setting, media cache files, etc.  All I/O is to this drive, except the project file which for some reason gets copied to temp on c drive... (no I/O there however)
    OS Boot drive is the seagate hybrid drive and is also very fast: ST95005620AS
    H.264 with preset Youtube HD wide screen standard preset
    All Video source files are this format from either a sony HDV or a panasonic HDV.
    SONY HDV:  30 Interlaced
    Type: MPEG Movie
    File Size: 78.3 MB
    Image Size: 1440 x 1080
    Pixel Depth: 32
    Frame Rate: 29.97
    Source Audio Format: 48000 Hz - compressed - Stereo
    Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
    Total Duration: 00;00;24;13
    Average Data Rate: 3.2 MB / second
    Pixel Aspect Ratio: 1.3333
    Panasonic: 60P:
    Type: MPEG Movie
    File Size: 142.0 MB
    Image Size: 1920 x 1080
    Pixel Depth: 32
    Frame Rate: 59.94
    Source Audio Format: 48000 Hz - compressed - 6 channels
    Project Audio Format: 48000 Hz - 32 bit floating point - 6 channels
    Total Duration: 00;00;45;30
    Average Data Rate: 3.1 MB / second
    Pixel Aspect Ratio: 1.0
    Sysinfo:
    OS Name    Microsoft Windows 7 Enterprise
    Version    6.1.7600 Build 7600
    Other OS Description     Not Available
    OS Manufacturer    Microsoft Corporation
    System Name    JBRANDT-WS
    System Manufacturer    LENOVO
    System Model    4389AB8
    System Type    x64-based PC
    Processor    Intel(R) Core(TM) i7 CPU       Q 720  @ 1.60GHz, 1600 Mhz, 4 Core(s), 8 Logical Processor(s)
    BIOS Version/Date    LENOVO 6NET74WW (1.34 ), 10/27/2010
    SMBIOS Version    2.6
    Windows Directory    C:\Windows
    System Directory    C:\Windows\system32
    Boot Device    \Device\HarddiskVolume1
    Locale    United States
    Hardware Abstraction Layer    Version = "6.1.7600.16385"
    User Name    CISCO\jbrandt
    Time Zone    Pacific Standard Time
    Installed Physical Memory (RAM)    8.00 GB
    Total Physical Memory    7.93 GB
    Available Physical Memory    1.99 GB
    Total Virtual Memory    7.93 GB
    Available Virtual Memory    1.58 GB
    Page File Space    0 bytes
    DISPLAY:
    Name    NVIDIA Quadro FX 880M
    PNP Device ID    PCI\VEN_10DE&DEV_0A3C&SUBSYS_214517AA&REV_A2\4&5AED965&0&0018
    Adapter Type    Quadro FX 880M, NVIDIA compatible
    Adapter Description    NVIDIA Quadro FX 880M
    Adapter RAM    1.00 GB (1,073,741,824 bytes)
    Installed Drivers    nvd3dumx.dll,nvwgf2umx.dll,nvwgf2umx.dll,nvd3dum,nvwgf2um,nvwgf2um
    Driver Version    8.17.12.5738
    INF File    oem77.inf (Section052 section)
    Color Planes    Not Available
    Color Table Entries    4294967296
    Resolution    1600 x 900 x 49 hertz
    Bits/Pixel    32
    Memory Address    0xCC000000-0xCDEFFFFF
    Memory Address    0xD0000000-0xDFFFFFFF
    Memory Address    0xCE000000-0xDFFFFFFF
    I/O Port    0x00002000-0x00002FFF
    IRQ Channel    IRQ 16
    I/O Port    0x000003B0-0x000003BB
    I/O Port    0x000003C0-0x000003DF
    Memory Address    0xA0000-0xBFFFF
    Driver    c:\windows\system32\drivers\nvlddmkm.sys (8.17.12.5738, 12.46 MB (13,065,064 bytes), 6/28/2010 6:21 AM)
    Adobe Project file:
      XML 400 pages so skipped
    Encoding additional info:
    I use time Warping ON SOME OF THE CLIPS, and I TOOK 2 of the 60P videos and set the time to 10% and 20% IN THIS PROJECT FOR SLOW MOTION OF THE ENTIRE CLIP.
    Another note that you need to look at separately:
    I have seen issues trying to time warp and 60P video interpreted at 30P and time warped.  It displays fine, but WILL NOT RENDER.  I deleted these and re-did them at 10 and 15% time respectively to get the video rendered.
    Looking forward to help.
    Jim

    Harm:
    Cost: I got 2 of the Kingston 128GB SSD V100 from Costco at around 165 each  (after rebate). They are on sale, and there is a 40 rebate each drive  (up to 2) rebate.
    Yes you are right, I did not expect improvements for Premiere pro, but I installed because I use this configuration on other systems for 1 year... and here are the results...
    ALL of the data on this sytem is backed up on my 8TB server.  I can loose anything here and get it back. I see the OS as just another replaceable disk.
    I used the system motherboard hardware Raid 0 for C: AND...  I put 3 of the 1TB drives on the motherboard hardware raid as a data disk.  Data disk is ALL scratch disk, for the encoded files and cache.  Source files are on the other software striped drive.  Of course I loaded a fresh install and moved to Windows 7 64bit...
    Overall observations:
         As you predicted encode times did not improve much, It was 15 minutes vs 17 minutes at 2.66 clock. I am unimpressed with the Intel Motherboard Raid 0. I saw the SSD was blazingly fast, but I think moving these to a RAID controll they will go faster.  Each SSD drive in 200+MB/S rated.
    What I do see is dramatic improvements in load times of the OS and ANY  program you run.  The pagefile was moved back to this raid 0 drive after  benchmarks. RUNNING ANY application (adobe, microsoft, ALL are blazingly fast to load).
    Example: Premiere pro CS5 from click on launch to CS5 prompting for a project name was  5.5  seconds...  I would not take this out of the system for any money saved.  It is amazing.  Almost as good as the nvidia quadro FX 4000 Display card and the CS5.
    My NEXT investment IS the RAID controller, and 6 of the Hitachi deskstar 3TB 6GPS Sata III drives to replace all my current drives. Next month or so for that.
    I want components that I can keep in the system when I do replace the motherboard and CPU.  I will tune this system as I have funds, and ask for help when this system no longer is viable and replace the motherboard.  I will ask for the fastest motherboard and CPU combo that you can buy, and keep my 730X(treme) case and add a water cooler.  As drives add 1TB a year in size, they seem to meet myneeds and I replace the old every 2 years to get the space I need.
    As always your comments are spot on and I appreciate your reviews.
    Bechmarks are from CPUID's toolkit, here are the disk benchmarks:
    Disk Performance in   MB/S
    OS
    Sequential read
    Sequential Write
    buffered read
    buffered write
    random read
    Improvements:   Sequential write MB/Sec
    Sequential read
    buffered read
    buffered write
    random read
    C: 1   velociraptor
    Vista   Ultimate
    97.38
    72.45
    139.05
    128.52
    33
    Baseline
    Baseline
    Baseline
    Baseline
    Baseline
    C: Motherboard Hardware Raid 0 128G Kingston (220gb)
    Windows   7 64bit
    230.98
    98.92
    229.59
    229.59
    53
    237.19%
    136.54%
    165.11%
    178.64%
    160.61%
    Data 1: software raid 2 drives
    Vista   Ultimate
    108.36
    54.66
    121.05
    73.01
    34
    Baseline
    Baseline
    Baseline
    Baseline
    Baseline
    Data 1: software raid 2 drives
    Windows   7 64bit
    111.35
    55.6
    131.83
    74.58
    25
    102.76%
    101.72%
    108.91%
    102.15%
    73.53%
    Data 2:3 software raid 0 3 drives
    Vista   Ultimate
    129.4
    160.7
    154.49
    143.7
    29
    Baseline
    Baseline
    Baseline
    Baseline
    Baseline
    Data 2: Motherboard Hardware Raid 0 raid 0, 3 drives
    Windows   7 64bit
    132.5
    212.66
    179.59
    162.85
    44
    102.40%
    132.33%
    116.25%
    113.33%
    151.72%

  • Urgent : Plantage constant de Media encoder, premiere pro CC et CC2014.

    Bonjour à tous !
    Je rencontre de grosses difficultés avec Premier Pro et média encoder CC et CC2014.
    Lorsque je veux mettre en fil d’attente mes projets que je passe par Fichier>Importer (composition After ou même Première) ou que je fasse simplement un glisser/déplacer dans Media Encoder....Une fois sur deux ça plante, ne chargeant pas Dynamique link, ou plantage de première pro..... Avec les versions CC comme 2014....Je n'ai pas de message d'erreur particulier. En revanche je suis obligé de killer les processus Dynamique link, adobe (en général : Qt32 server, Adobe ipCbrocker, PProHeadless.exe) via le gestionnaire de tache Windows. Sinon impossible de réouvrir les logiciels.
    J'ai d'ailleurs remarqué que même lorsque les logiciels ne plantent pas, que je ferme premiere ou afx ou autre, les logiciels ne s’enlèvent pas des Processus, il reste ad vitam aeternam, dans les processus actif.
    Lorsque j'arrive quand même à importer mes séquences dans MediaEncoder, celui-ci plante certains encodages mais pas tous....sans raison particulière et ne me disant pas pourquoi il les a planté. S’il ne les plante pas, il tourne en boucle sur la même image et je suis obligé d’arrêter moi-même l'encodage, qui ne se finira jamais. Sachant que tous mes fichiers font parties d'une série, qu'il y a donc exactement la même choses dedans en terme de montage, effet etc. Ce qui en passant n'est que du fondu....
    Mes Rush sont des fichiers MXF. Et j'utilise le dynamique Link pour mes imports de séquences entre première et afx. Bien que ça me fasse exactement le même problème que j'importe directement mon première ou que je passe par dynamique Link.
    Aussi, autre problème lorsqu'il accepte d'exporter (Media encoder j'entend). Il ne m'exporte pas forcement tous le son, il va m'exporter la première séquence par exemple l'intro, puis tous le reste de la vidéo qui est dans une autre séquence et compo, il ne l'exporte pas........
    Je ne sais plus quoi faire la. Au prix ou est vendu cette suite franchement !
    Je suis donc sur :
    Windos Seven PRo 64Bits.
    J'ai un i7 X980 3.33GHZ
    Une Nvidia GTX480 driver 337.88 (les derniers quoi)
    ET 16 Go de RAm
    Mon cache n'est pas plein, je le vide régulièrement. Il est sur un disque au regard des projets, et ne bouge jamais.
    Voilà, si jamais quelqu'un a le même problème, ou connait une solution, je suis preneur.
    Ça tombe au plus mauvais moment, j'ai 200 vidéos à encoder pour dans 1 Mois. 
    Merci d'avance.
    A.H
    Message was edited by: aurel motiond

    Il ne sert pas à grand chose ce forum, sans vouloir être offensant....

  • Urgent: constant Crash Media encoder, premiere pro CC and CC2014.

    (Sorry by advance, its an Google trad)
    Hello everyone!
    I meet great difficulties with Premier Pro and Media encode CC and CC2014.
    When I want to wire my pending projects that I go through File> Import (or even composition After Premier) or I simply do a drag / drop in Media Encoder .... Half the time it crashes, not charging Dynamic link not or crash Premier pro ..... with CC versions like 2014 .... I have no particular error message. However I have to process the killer Dynamic link, adobe (in general: QT32 server, Adobe ipCbrocker, PProHeadless.exe) via the Windows task manager. If not impossible to reopen the software.
    I also noticed that even when the software does not crash, I close the first or afx or other software will not come out of the process, there is ad infinitum in the active process.
    When I still manage to import my sequences in MediaEncoder, this plant some encodings but not all .... no particular reason and not telling me why he crashed. If it does not crash, it runs in a loop on the same image and I have to stop myself encoding, which never end. Knowing that all my files are part of a series, there has exactly the same things in it in terms of editing, effects etc.. Which by the way is only melted ....
    Rush are my MXF files. And I use the Dynamic Link to import my sequences between Premier Pro and afx. Although it makes me exactly the same problem that I import directly my first or I go through Dynamic Link.
    I'm on:
    Windos Seven PRo 64bit.
    I have a 3.33GHz i7 X980
    Nvidia GTX480 driver 337.88 (the latest what)
    AND 16GB RAm
    My cache is not full, I empty it regularly. It is a hard look at projects and never moves.
    So, if anyone has the same problem or knows a solution, I'm interested.
    It falls at the wrong time, I have 200 to encode videos in one month.
    Thank you in advance.
    A.H
    Message was edited by: aurel motiond

    Il ne sert pas à grand chose ce forum, sans vouloir être offensant....

  • Adobe Premiere CS3 crash with Export Adobe Media Encoder

    Hello,
    I having a problem with Premiere. When I want to export my sequence with Adobe Media Encoder, Premiere crash. I tested the solution proposed by this link: http://kb2.adobe.com/cps/404/kb404804.html but no success ...
    My computer configuration:
    - XP 64
    - Dual Xeon
    Thank you,
    Kevin

    A link with many ideas about computer setup http://forums.adobe.com/thread/436215?tstart=0
    Computer DETAILS are always good to provide
    Work through all of the steps (ideas) listed at http://ppro.wikia.com/wiki/Troubleshooting
    If your problem isn't fixed after you follow all of the steps, report back with the DETAILS asked for in the questions at the end of the troubleshooting link

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

  • Crash upon opening Adobe Media Encoder

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

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

  • Adobe Media Encoder (Pr CS4) encodes my videos without the effects of the plugins Genarts Sapp

    Hello,
    My Adobe Media Encoder (Premiere CS4) encodes my videos without the effects of the plugins Genarts Sapphire. I did not have this problem with CS2 and also he encodes all other plugins.
    Do you know why? I really need to solve this serious issue.
    Any help will be apprecieted,

    OK, good. Go to C:\Users\username\AppData\Roaming\Adobe\Premiere Pro\4.0 and look for two files called "Plugin Loading.log" and "Headless Plugin Loading.log" (without the quotes). These are just text documents, so open them up in Notepad or similar and compare the two; what you're looking for are references to your Sapphire plugins. What you'll probably find is that in "Plugin Loading.log", the plugins are loaded successfully--it will say something like "The plugin was successfully loaded from the registry."--whereas in "Headless Plugin Loading.log" the same plugin will be marked "The plugin is marked as Ignore, so it will not be loaded."
    If you see that, let me know and I'll try to walk you through the steps of correcting it. If you like, I'd be happy to look at the log files; attach them to a reply here (they're small documents).

  • Premiere Pro and Adobe Media Encoder running slow

    Hello everyone,
    I'm having trouble with CS4, which is running significantly slower than CS3 did on a older machine. The CS4 suite is installed on a Dell Precision M6400:
    Windows Vista 64-Bit
    Intel Core 2 Duo CPU T9400 @ 2.53 GHz
    8 GB RAM
    NVIDIA Quadro FX 2700M Graphics with 512MB dedicated memory
    The OS is running on a 57.5 GB HD (C:) and the Adobe suite is installed on a 298 GB Solid State HD (D:), except for Adobe Media Encoder, which is installed on the C: drive.
    My project has 4 15-16 minute sequences. The sequences are in DV NTSC, 29.97 fps,  My scratch disks are set to a folder on the C: drive. Media Cache Files and the Media Cache Database points to a folder on the D: drive.
    These are some of the problems I'm having:
    - Premiere Pro CS4 generates peak files every time I open a project
    - It then takes 3-5 minutes to render before I can preview a 16-minute sequence
    - Adobe Media Encoder takes 5 hours to render a 16-minute sequence (as flv) that has been previously rendered
    - AME takes 1 hour to render every 15 minute sequence that has never been rendered before
    Are my settings affecting their performance? Is there any way to improve it? Thanks.
    (Premiere Pro is the only app that is slow)

    The data rate for replay is one thing, the data rate from disk to memory then from memory to CPU and back the other way are different matters and ought not to be confused. It is well-established that for a computer to edit AVCHD you need top end components, and note that I said there were three tasks to distinquish with increasing hardware requirements, namely merely replaying the video, specifying edits in the editor and then the rendering. It is commonly accepted by all the industry vendors that to do remotely commercial AVCHD rendering you need a minimum Quadcore CPU then that eats data fast, in order to not let it go to waste you need a fast motherboard bus fast memory and in order for none of those to go to waste you need the fastest disk set-up you can manage. I in fact have a 4-disk RAID0 volume using SATA (I think the disk model is SATAII but I have to await return from the repair center before I can confirm). For this RAID0 volume I have run speed test software from BlackMagic because I have one of their HDTV capture cards. It recorded that this volume which remember is doing parallelised IO is just fast enough to receive a encoded HDTV stream from the BlackMagic card but too slow to receive an uncompressed HDTV stream, indeed when I tried both I found the volume did keep up with compressed but fell behind with uncompressed. Remember that with a RAID0 volume of 4 SATAII disks a given file gets spread over the four disks and hence IO is spread over those 4 3G/s data lanes. Also remember with these disks 3G/s is just a burst speed, for AVCHD we are interested in sustained serial IO which is much less.
    Before my machine broke down, I found that it took 5 hours to render 33 minutes of HDTV albeit as it went along it transcoded from AVCHD to a Microsoft HD format for Vista-only. Another interesting thing is that I found that the longer this render ran the slower it became, the estimated time started at 3 hours but the actual was five and the last one third took maybe 3 hours. Because the machine broke after that run I couldn't figure the bottleneck. For my machine bear in mind that at the repair shop we found that the Quadcore had only half the necessary electrical power plugged in, the monitor software showed however that it constantly ran around 90% of whatever capacity that reduced power supply permitted. Now then we can puzzle over why it got slower and slower and yet CPU consumption remained consistent and near to full capacity, memory was not the bottleneck because that was constant at 6.4G. But you can say that this was maybe performing like a Dualcore and was hitting some sort of wall, if you had a 1 hour render with that rate of degeneration of performance factored in what would happen to the render time, and for 3 hours you could be running indefinitely. I hope when the machine comes back the correct power supply will make it behave like a Quadcore should for this type of application. Anyway I have two theories for the degradation. First is just that PrProCS4 was getting its knickers in a twist and thereby just doing more computation per minute of video to be rendered as time went by, maybe internal resource management related to OO-type programming maybe, or related to disk IO falling behind, both these theories have problems, for the latter the CPU usage should then have dropped also.
    Anyways, you need really a Quadcore system and blazing fast disk to work fully with AVCHD commercially, we found an external SATAII disk so if I were you I would just go get one and move on with your life.
    Message du 03/06/09 16:08
    De : "Jim Simon"
    A : "JONES Peter"
    Copie à :
    Objet : Premiere Pro and Adobe Media Encoder running slow
    For AVCHD you MUST have FAST disks.
    AVCHD actually has a lower data date than DV. You need lots of CPU muscle, but disk speed is really not a factor specific to AVCHD. Anything that works for DV will work just as well for AVCHD (and HDV as well).
    >

  • Adobe Media Encoder pausing rendering while working in Premiere Pro

    Hello everyone,
    So I am redering a video in Adobe Media Encoder and at the same time I am editing a new one in Premiere Pro.
    I noticed that AME is constantly pausing the rendering and did not know why. It turns out that while I'm editing a video in Premiere Pro, I am constantly pressing the space bar to start/pause the video I'm editing. While I do that, AME keeps pausing/unpausing the rendering. Somehow, pressing the space bar in PP has an effect in AME.
    I have no clue why it does that because the Premiere Pro window has the focus, not the AME one.
    Has anyone ever seen that?
    I use Windows 8 and Adobe CC.

    Hi Rallymax,
    Yes I do queue footage by having an Autowatch set up on the directories where the video is written to.  I rarely do a direct export unless testing new settings.
    Don't take this as gospel but I too had a feeling that GPU acceleration didn't happen with AME, only direct export.  Not sure where that came from, I did watch some of the recent Adobe TV Web Seminar's about new features of CC products etc, so maybe on one of those?
    I found this while trying to find out where I had seen it but it is from AMD site not Adobe so whether it's fully 100% correct I dunno:
    Adobe Media Encoder
    The Adobe Media Encoder (AME), with support for OpenCL™ and GPU acceleration, automates the production of multiple encoded versions of source files, sequences, and compositions in Premiere Pro CC. With the GPU-accelerated AME and AMD graphics technology, editors can quickly encode projects and output files for virtually any destination. AMD GPUs handle the heavy lifting, freeing the system’s CPU to perform other functions.
    I will try the same test as Jason, if I can find any AVHCD video and see what the results are.  Will be interesting.

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

  • Queuing from Premiere Pro to Adobe Media Encoder no longer working? CS6

    Hi there,
    Just very recently adobe media encoder has stopped accepting que's from premiere. I choose export in premiere, setup the export details and hit que, adobe media encoder launches, but then it flashes once (like disappears reappears, very quickly) and then it just simply does nothing. No item appears in the que. I have tried opening the premiere sequence directly from adobe media encoder but it does nothing either. If I drag the premiere project directly onto a preset in adobe media encoder, it crashes every time. (though not sure if it would of done this previous to my problem arising)
    Anyway, very frustrating as I usually work on a different project whilst media encoder is rendering something out. Now i'm stuck with huge down times as I wait till the render is finished.
    Recently updated to Mac OSX 10.8.3 - I think this is when the problem began.
    Just updated the CUDA driver to 5.0.45 but this has not changed anything.
    Working on a Mac Pro 5,1, 2x2.4Ghz 24GB RAM, EVGA GTX 660 FTW,

    Some suggestions and answer at least the 16 questions at the end of the Wiki article.

  • Adobe Premiere Pro Won't Export To Adobe Media Encoder?

    I Work for a news company and we use Adobe for aeverything we need. But when we take a little break from doing videos while we where moving to a new office space, and suddenly we start again and It decided not to export to the Adobe Media Encoder. Usually it was a 5 second process and now it does not work at all. We have adobe premiere pro cs5.5 from the CC (We are currently not planning on upgrading to CS6 anytime soon.) We have no plugins for it and it works for everything else. When I use the Exporter it Exports in in too low of a quality for use. Help? If you need I work at better-community-news.com, Sooolutions (Seprate buisness same owner.) Glad Studios, (also same owner...all the places I work are the same guy), X.L.N.T Marketing and thats about it. Its a team of 3 guys and we would appricate any help! Thanks!
    ~ Better Community News

    Jan 21, 2014 12:51 PM -to- Jan 21, 2014 2:24 PM
    thanks nobody because nobody helped me solve this delima
    You do know that this is a user to user forum, not an official Adobe support site?
    Which means that there is NOT a full time group of people just waiting to answer questions
    Don't you think that complaining about nobody answering in less than 2 hours is a little unreasonable?

  • Rendering in Premiere CS5 vs Adobe Media Encoder? Which is better?

    Exactly what the question says. Is there a difference between rendering in Premiere CS5 to rendering in Adobe Media Encoder? Leave your thoughs. Thanks!

    Then I have made a mistake. I thought that the AV Export function under File>Export had been fully moved to AME. Obviously, I am incorrect.
    No, you're correct: there is not Export > Movie command any longer, and hasn't been since CS3. With CS4, that particular functionality was eliminated, as all exports went through AME, and were logged in the AME queue.
    Things have changed yet again with CS5. There is still no Export > Movie as there was in CS3 and earlier; everything still must be encoded through AME. However, in CS5, when you initiate the export, you have two options: Export and Queue. The latter option does what CS4 exports did: they go into the AME queue for sequential export. The former option basically launches a "headless" version of AME and exports as a one-off. The export is still being performed by AME; it's just that you don't have the virtue of it working in the background as it does with the Queue button. I've also encountered some weirdness with Export when it comes to cropping and using hardware MPE, but that's a different story. I haven't done any hard-and-fast tests of which is faster--Export or Queue--but I'd take Harm at his word that Queue is the faster option.

  • Premiere Pro CS4 and Adobe Media Encoder Problems

    I am using Adobe Premiere Pro CS4 on a Mac running 10.6, and I consistently encounter this problem when trying to export a Premiere project using Adobe Media Encoder.
    What does this mean? And has anyone else encountered this problem as well? I really need a fix if there is one, because I really need to be using Premiere. I have reinstalled several times, but to no avail. Help me please!

    Jim, thanks for testing.
    My concerns are about a)distribution and general b)compatibility.
    a) When videos are distributed most of the users will probably try to open the files with Windows Media Player. So it is not a good start to have fresh exported h.264 videos which won't run fine with the 'main' player on windows
    b) I am wondering if the Problems with Windows Media Player may also be a sign of a general compatibility issue of the h.264 video itself
    At least in case b) Adobe would have to look into this.
    Here is another test video:
    http://www.tsxn.com/storage/transfer/Serenity.zip
    Thank you
    Chris

Maybe you are looking for