Encoding speed limit in Adobe Media Encoder?

Dear All,
I experienced a strange (for me) behaviour of AME. I made an encoding test with different coding profiles used the same 1GB big MOV file (from 5D Mark II) on two PC-s, and got a very similar results regarding encoding duration. This is impossible. The difference was only 4-6 secs, see below:
PC-1:
-          CPU Q9550 (Quad Core 2.8Ghz),
-          6GB /1333 RAM,
-          Vista 64Bit,
-          GT9600TOP,
-          latest update of Media Encoder.
-          Encoding Time: 16:40
PC-2:
-          CPU I7 - 920,
-          6GB /1600C8 RAM,
-          Vista 64Bit,
-          GT9600TOP,
-          latest update of Media Encoder.
      -          Encoding Time: 16:40
The source file was opened directly from AME. Both of them used only 25-35% of CPU. I enclosed two screenshots about it. Any idea? I repeated these tests with DVD and Windows Media 9 profiles, and got similar results.
ps. I have read problems regarding Canon 5DMII videos with PR4. I did not experience any problems expect the preview speed. With I7, it is almost acceptable, but non of slower (tested Q9550, E6400) CPUs gave acceptable playing quality.

- with HDV to DVD, I can reach 100% CPU, but becuse os resizing the frames. If you convert it to Widows Media, or MPEG2-BlueRay, it will not use 100% CPU.
- I have 3 Disks:
a., Vista and programs, SATA2 750GB Samsung with two partitions, second one is for the final DVD / BL folders.
b., "Sources", 1TB SATA2 Samsung 32MB Cache
c. "Projects" and transcoded files, SATA2 750GB Samsung.
If you check the screenshot I sent first, you can see that there was no bi traffic on the disks.

Similar Messages

Adobe Media Server Starter limits? disk quota exceeded

hi, I'm confused...
I'm running an Elemental encoder, publishing to
rtmp://10.151.170.22/livepkgr/livestream?adbe-live-event=liveevent&adbe-record-mode=record
(i've tried with and without the 'record' bit - I actually don't want/need to record).
AMS is on Windows 2008 R2 64 bit, AMS was installed from AdobeMediaServer_5_LS1_win64 with no serial number.
If i delete the stream files and 'reload this application', then the stream runs for a period, actually until it has ~120mbytes in the streams folder.
( << 10 minutes).
Then the livepkgr stops with logs of:
#Fields: date
time
x-pid
x-status
x-ctx
x-comment
2013-06-07
08:51:50
6660
(s)2641173
f4f:livestream - NetStream.Play.UnpublishNotify
2013-06-07
08:51:50
6660
(s)2641173
onUnpublish : livestream
2013-06-07
08:51:50
6660
(s)2641173
f4f:livestream - NetStream.Play.Stop
2013-06-07
08:51:50
6660
(s)2641173
f4f:livestream - NetStream.Unpublish.Success
2013-06-07
08:52:39
6660
(s)2641173
onPublish : livestream
2013-06-07
08:52:39
6660
(s)2641173
Stream name is: livestream and live event is: liveevent
2013-06-07
08:52:39
6660
(i)2611173
Event level recording configuration: General[flags: 1, keyframe interval: 60000, max size: -1, max length: -1, io buffer size: 0], Fragment[frag duration: 4000, seg duration: 400000, duration precision: 0, allowed drift: 1000, frame rate: 0.000000, frames per interval: 0, intervals per frag: 1, frame precision: 1, disk management duration: 3.000000], ContentProtection[enabled=false(overridable)]
2013-06-07
08:52:39
6660
(s)2641173
f4f:livestream - NetStream.Data.Start
2013-06-07
08:52:39
6660
(s)2641173
f4f:livestream - NetStream.Publish.Start
2013-06-07
08:52:39
6660
(s)2641173
f4f:livestream - NetStream.Play.Reset
2013-06-07
08:52:42
6660
(s)2641173
f4f:livestream - NetStream.Record.Start
2013-06-07
09:02:47
6660
(s)2641173
f4f:livestream - NetStream.Record.DiskQuotaExceeded
2013-06-07
09:02:47
6660
(s)2641173
f4f:livestream - NetStream.Record.Stop
The documentation seems to indicate that Starter edition should be unlimited in time of streaming, just limited by number of cllients, as long as you are not protecting the streams, then limited to 30 minutes.
I have checked quoteas in Windows and they are disabled.
Can someone confirm that I should, in starter, be able to continually stream 24/7, and if so give some hint as to what I may have to change to do this?
At the end of the day, all i need to do here is simulate a customer environment for integration effort in players....
Simon

Hi Simon
The HTTP (HDS and HLS) streaming and recording limit in Adobe Media Server 5 Starter is 10 min. You'll need to buy a serial key if you want to record/stream for longer. Also there are no limit on number of clients for HTTP.
Hope this helps.
Thanks,
Apurva

Adobe Media Server pro 5 Scalabiltiy Requirements with respect to the number of clients connected

what are the hardware requirements mapped to the number of clients connected to a vritual server running on a Windows 2008 R2 Server? At what point should the scaling be done, what are the best practices? The encoding rate used is 360 Kbps.

Hi Simon
The HTTP (HDS and HLS) streaming and recording limit in Adobe Media Server 5 Starter is 10 min. You'll need to buy a serial key if you want to record/stream for longer. Also there are no limit on number of clients for HTTP.
Hope this helps.
Thanks,
Apurva

Adobe Media Encoder CS4 Causing Jerky Playback with Speed Changes

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

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

Problem wit the speed of Adobe Media Encoder

Dear Sirs, my computer has two Xeon e5-2687w each 8 core processors. Why is Adobe Media Encoder running to only 20% CPU?
Thanks,
Jiri Stepanek

Dear Sirs, my computer has two Xeon e5-2687w each 8 core processors. Why is Adobe Media Encoder running to only 20% CPU?
Thanks,
Jiri Stepanek

New PC, downloaded CC 2014. Flash not showing up as option to rip in Adobe Media Encoder or in After Effects. Help?

Why is .flv not an option in Adobe Media Encoder or Adobe After Effects?
Also, when Adobe Captivate converts the video it looses the Alpha channel.
Help

Thanks for taking the time to answer this question. Knowing this isn't possible at least narrows my options down. It would be helpful to provide some kind of list of what comp settings carry over into AME from After Effects. Is it essentially everything that is enabled in the Timeline? (I know that motion blur settings do.)
I'll put this in a feature request, but yes, we need the other half of After Effects Render Queue in AME in order for AME to be a good replacement for rendering from AE. I'll give you my thoughts on why Render Settings are essential before you would actually want to render with AME instead of doing so because you have to (either because you want to render in the background, or need a codec that has been removed from AE.)
1. Speed: Simply applying a Render Settings preset is much faster than manually setting motion blur, frame blending, work area, etc.
2. Reliability: Not being able to apply a Render Settings preset at the time of render is a recipe for missing a crucial setting buried in a comp, then having to redo a render and wasting time.
3. Features: As noted above, there is no way to approximate Render Queue's ability to change resolutions at render, which results in a lot of wasted time when that feature is needed.
Render Settings I think are crucial to making AME rendering worthwhile for AE users:
1. Rendering resolution
2. Work Area/Entire Composition toggle
3. Field Rendering (wait, does this mean AME can't currently render to fields?)
4. And PRESET ability these settings, so I'm not doing them manually every time.
I realize that your team clearly doesn't spend the same amount of time I do making low res H264 previews and sending final files out in H264 format, so you don't appreciate the impact of the changes you made. Moving to AME for that stuff is a real inconvenience, but implementing the settings above could help soften the blow.
Thanks,
Jerry

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

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

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

Adobe Media Encoder CC - You Need to Add Unsupported CUDA Cards to supported_cuda_cards.txt

Hi Folks
I'm running on a Mac Pro with an NVidia GTX 770 with 4GB. Premiere Pro CC utilizes the GPU for playback and export but will give you a warning when you first enable CUDA in Mercury Playback Engine. However...
I was noticing that when I queued the export to Adobe Media Encoder CC, it was taking forever to encode simple queued sequences.
After doing a bit of research on the internet and even in these forums I realized that while Premiere Pro was being ok with supporting a non-supported card, Media Encoder was not. I added the GTX 770 to the supported_cuda_cards.txt file locate here: /Applications/Adobe Premiere Pro CC/Adobe Premiere Pro CC.app/Contents/ (you will need to be slightly geeky to find and modify this file - more info than I care to provide in this post but you can look up how to locate files in Mac OS).
Voila! AME now encodes super speedly, like 4 times as fast as before!!!
Thought I'd just provide this little tip for people experiencing this problem.
Adobe... can you do something about this? I know it's a corner case but really - maybe something in AME preferences or something... Like "Use CUDA capable card even if not on supported CUDA list" checkbox or something.
Now I can get back to work.
-Keith

I just made this change in the AME ".txt" file for my GeForce GTX 670 (i7, WIn 7 Pro, 32 GB, and I know it's not "certified" for CUDA), and now have it in both the PPro and AME ".txt" files. While I'm waiting for AME to finish, this thread raises questions in my mind.
It's been my understanding that AME was engineered to run in the background, allowing other work to be done in PPro without the 2 "getting in each other's way".
I'm happy with the rendering speed in PPro, and I see that hardware rendering is working there.
If AME now makes use of the GPU while I'm doing other work in PPro, (like maybe "rendering the selection", or an entire sequence in PPro), does that affect the performance of either the file that AME is currently processing, or does it affect what I can do/performance I'll get while concurrently working in PPro?
Are CUDA/GPU resources "shared" between PPro and AME? Or, are the apps likely to "trip over each other"?
If AME does, in fact, make use of the GPU, is there something other than the ".txt file hack" that I must do to enable the renderer in AME to use MPE hardware? As I type this I have AME working on a PPro sequence but I see that the "Renderer" is showing "Mercury Playback Engine Software Only".
I feel like I'm missing some important tidbir of information, but I don't know what that is.
What am I missing?

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

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

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

Adobe Media Encoder cuts off video layer when the Ultra Key effect is applied

I am working on a Mac (10.8.5) using the latest verison of Premiere Pro CC. I am using Ultra Key to remove the chroma key background from the "talent layer" and adding a "new background layer" behind the talent video layer. When I export directly from Premiere, the sequence exports as expected. However, I have many sequences, and wish to speed up the process using Adobe Media Encoder. When I export the same sequence using Adobe Media Encoder, the top half of the "talent layer" is completly cut off:
The issue has something to do with the Ultra key effect because when I remove the effect from the "talent layer" it exports in tact (with a chroma key background of course). Adobe Media Encoder CC is up to date as well; are there any known bugs with Media Encoder CC and the Ultra Key effect in Premiere Pro?
Thanks!

Block noise in CC2014 Adobe Media Encoder Quicktime H.264 Export

I would love some input from the community here. Perhaps someone else is having a similar issue.
I've been wanting to make a full switch from CS6 to CC2014, but I am experiencing a host of issues that I don't experience in CS6. For one, when I export my Canon 5DMK3 DSLR timeline using Quicktime (H.264), I get an abrasive global noise all over my rendered video as if I was using a low data rate. I use the same settings in CS6 and experience no issues.
Since YouTube compression hides these artifacts, so please download and view original file: Dropbox - RenderArtifactsQuicktimeH264.mp4
Format: Quicktime
Video Codec: H.264
Quality: 100
23.976fps
progressive
Use Max Render Quality
Render at Maximum Depth
10,000 kbps
What I've tried:
1) exporting at 720p and 1080p
2) another codec (H.264 mp4 exports are clean)
3) all combinations of the "Use Max Render Quality" and "Render at Maximum Depth" settings
4) exporting straight from Premiere
5) rendering with and without effects (Magic Bullet Looks, sharpening)
6) GPU (CUDA) enabled and software only (on project and on Adobe Media Encoder)
Custom Desktop Specs:
Intel i7-3960X @ 3.3GHz
32GB RAM
GTX 780 Ti 3GB (and tested Adobe certified regular GTX 780 3GB)
GPU Driver: 340.52 (up to date)
Windows 7 Professional 64 bit
SSD OS drive
WEstern Digital 2TB data drive
SSD adobe cache drive
I'm at a complete loss. What else could be contributing to this?

Hi Mark,
I did install the CC 2014.0.1 update and the issue remained. I had a colleague tell me that he experiences the same issue for Format= Quicktime, Codec= h.264 when he has the "limit data rate" option checked with a value. When I unchecked the limit data rate (of my standard 10,000 kbps 720p preset) I got a clean render devoid of the previously mentioned artifacts. However, it defaulted to a 70,000 kbps data rate which of course is higher than I'd like/need. For now I guess I'll be exporting .mp4 h.264, but I'm still curious why the limit data rate doesn't behave like it did in CS6.

Adobe Media Encoder 4.2 update forces Frame Blend

I didn't really want to repost, but I felt the title and info in my previous post were innacurate (http://forums.adobe.com/message/2576915#2576915)
In my previous post, I thought Premiere was to blame, but after a few reinstallations, I've found that the update to AME 4.2 causes the problem.
I've found that Adobe Media Encoder 4.2 forces Frame Blend, even if it has been disabled on each clip of the timeline, when the frame rate of your sequence settings differ from the frame rate of the target format.
Example: Exporting from 24fps Desktop -> MPEG2-DVD (23.976fps)
Adobe Media Encoder 4.1 does not have this behavior. I've reverted to 4.1 for the time being.
If anyone has a workaround for this, or any other info on this problem, please share.

I am having a similar problem. Is it just me or is it Adobe? I have had so many problems with Adobe Premiere CS4. It may have also been exacerbated by the fact the I updated to 4.2.1 (mostly in part to determine if another issue was resolved with this update).
I have some editing background in the Windows Movie Maker and iMovie world, and was excited to use Adobe Premiere, but I have had nothing but problems.
Everything that I am trying to do, looks really washed out, and renders the video useless.
I am trying to do what you just described, with speeding up and slowing video to match the computer actions with the person's voice. I am capturing video using CamStudio and Helix YV12 CODEC, and tried to use HuffyUV lossless compression: using DV-NTSC as the standard format.
Then I go to compose my video, and output the video, but the video is crap. It sounds like the Adobe Premiere and Media Encoder are having major problems.
I tried rendering it to Uncompressed Microsoft AVI with UYVY @ 100% quality, and tried to compare it with Windows Media at the highest quality, and it is frustrating. When I hear that Frame Blend is being applied, it seems to look worse.
I am running:
Intel Core 2 Quad CPU 2.33 GHz (which is kind of slow)
8 GB RAM, 2 SATA 1 TB Drives WD Caviar Green (a little substandard)
Windows XP 64-bit
Let me know there is another process that I am missing. I don't really want to give up on Adobe Premiere, but from a end-user standpoint, I will have to revert back to using WMM due to time constraints. I want to take full advantage of all of the editing and effects capabilities of Premiere, but can't because I can't even produce a decent export to be used by any other program (and given that every conversion will in some way affect the quality of the output, I want to reduce any intermediate steps).
Arrggh!!!

Adobe Media Encoder: CBR bitrate problem!

Hi!
I'm having some problem with Adobe Media Encoder. I've edited a HD video (recorded with a Sony HDR-FX1) and created a MPEG2 file using the preset "1440 x 1080i 25 Hiqh Quality". The video file size is 7,25 GB.
Now I want to put this video on Motionbox and Vimeo. I found on the web some settings that seems to be perfect for Motionbox and Vimeo.
Here's the link: http://eugenia.gnomefiles.org/images/pcs3-h264.jpg.
As many of you already know, Motionbox doesn't have any file size limit, while Vimeo has (1 GB). So i thought to reduce the bitrate quality for Vimeo, while using, as written in that JPG, 4 Mbps CBR Bitrate. Here's the problem: I change the bitrate (for example 1,6) and I exit the export settings panel, so that I'm back to the AME start screen. If I initaliaze the queue, under the video settings on the left, the CBR bitrate is back to 3. So it seems like I can't change the bitrate.
I've used the same settings that are in that JPG so I can't understand what is going wrong. If I select 4 Mbps it goes back to 3 and the same happens if I select 1,6 or 2 for example. How can I fix this problem?
Thank you so much for your help. Bye!

Jeff,
Off-topic, but related to your naming convention in your reply, post 4.
Adobe has been using the "Pr" to designate Premiere for a version, or two now. I've been using "PP" for Premiere Pro, and "PE" for Premiere Elements, as I follow both fora now. Though it will take some retraining on my part, is the conventional wisdom (no pun here) that the acronym is most correctly stated as "PrP" and "PrE?" I also use PS for Photoshop, and PSE for Photoshop Elements, so it's not a matter of the characters. I just want to use the most correct acronym, for clarity in posts. What are your thoughts?
Thanks,
Hunt

Adobe Media Encoder CS5 MAC Freezes

Hi there,
We all know that exporting files from Premier Pro into flv files (and some others takes some time). An excellent way to work around this is to build up a queue of items in the Adobe Media Encoder. Then, you can run the queue when you are going to leave the computer for any length of time, say, overnight.
I have Premier Pro CS5 and Media Encoder CS5 on a Mac and have just done all the various updates. Unfortunately, this does not solve my problem - if I have about 4 items in the queue, it works fine. However, if I have, say 8 items in the queue, AME will freeze whilst working on about the 4th item. This happens reasonably consistently and is very annoying - any suggestions how I can sort out this problem would be greatly appreciated.
I am using a Macbook Pro with the i7 processor and 4 Gbyte of RAM, 7200 disk speed.
Thanks in advance.

Thank you ExactImage, if that is your real name.... I was able to reset AME 5.5 by holding down the Ctrl+Shift+Alt keys whilst starting the program. Your help is appreciated.

Adobe Media Encoder - not encoding entire video

Hi,
I'm runining CS4 Design Premium on a Windows XP machine. I'm trying to convert an .avi to .flv, but Adobe Media Encoder is only converting the first few minutes of the video. Is there a file size limit for the source media? My .avi is pretty huge, almost 2 GB. Could that be the problem?
Thanks!

I'd ask you to post in the Adobe Media Encoder forum, but I cannot find one :-( Perhaps the After Effects forum or Premiere forum will know an answer or where to look. People here are not likely to have an answer.

Encoding speed limit in Adobe Media Encoder?

Similar Messages

Maybe you are looking for