H264 progressive / buffering problem - Media Encoder CS3

I am exporting using adobe media encoder CS3 with the following settings:-
Format: h264
Video codec: MainConcept H.264 Video
Frame height/width 640 x 360
Frame rate 25fb
Fields order - None (Progressive)
Pixel aspect ratio: Square pixels
Profile:High
Level:4.1
Audio:ACC, 128 (Kbps), 48Khz, Stereo
Bitrate settings:VBR, 2 Pass, Target 2.00, Max 4.00 (Mbps)
Stream compatability:psp
The files are being played on the web via the Akamai player via HTTP progressive download.
When the file is initally loaded it buffers the WHOLE file instead starting automatically - obviously this is is not acceptable when playing long files - having to wait for the whole file to buffer before it starts playing. I have used free MediaCoder to produce H264 and not had this problem - but to do this i have to export and intermediate avi file from premier and then encode again - however i am not so pleased with the encoding quality and would prefer not to have this extra step in the process.
I have found this fix someone has made to correct the files once exported from Adobe Media Encoder CS3 - 'QTIndexSwapper2' - this works well - files play and start with continuous buffering - but again its an extra step (i have a lot of file to export - just want to export with Adobe media encoder direct to web using the built in FTP function)
Please could someone advise on the correct setting for exporting from Adobe Media Encoder CS3 - so that file start immediatly on loading instaed of buffering the whole file.
Many thanks indvance

Hi,
Thanks for posting that link...some interesting points and comments at the end...re: quicktime "save as" and streamclip ( free ).
I don't do what you're doing ... though I've noticed if I put samples of video for web on my website for people to check out they always DL fully before playing...so I usually tell people to just save to disk first and then play the video...
Anything I uploaded to YouTube gets converted by them and plays right away and beyond that I've had no need to get into this subject.
Good Luck and if you find out more useful info let me know...others could benefit later from your solutions.
Rod

Similar Messages

Can't Activate Flash Media Encoder CS3

I just had a new hard drive installed on my Windows XP SP3, 4 GB RAM, 2 dual core Intel processors machine. I reinstalled Production Premium CS3. All of my Adobe applications activated except Flash Media Encoder CS3. When I enter my serial number, it says it is an incorrect number and places a big red X beside of the number. The number I entered is the number on the box.
I called Technical Support and held for them for over 1 1/2 hours but no one came on to answer my question. I entered the problem in the Support Portal but it has been over 24 hours and no one has contacted me. I like Adobe software but not their technical support.
Can anyone in the Forum help?
Thanks,
Linda

I've tried it (with cookies cleared) on three different browsers now and they all experience the same problem. I am on OS X but that should not affect my ability to connect to a particular server. Here, for example, is a non-functional download link I'm given: http://download.macromedia.com/pub/flashmediaserver/flashmedialiveencoder/installer/AdobeF MLE3.2.1_r.dmg

How do I reinstall missing Adobe Media Encoder CS3 ?

I need some help here ??
When attempting to encode on Vista from Premiere 3.2 the Adobe Media Encode (AME) just goes off and hangs.
Looked for the error log which lives at
C:\Users\user\AppData\Roaming\Adobe\Adobe Media Encoder\4.0\AMEEncodingErrorLog.txt
Make sure you have view hidden files turned on to look for this file..
Ok the folder "Adobe Media Encoder" is not on my machine... It looks like the installation is FUBAR.
I check CS3 Master Collection distribution - I don't see a module for Adobe Media Encoder to reinstall.
So my question is . How do I reinstall the "Adobe Media Encoder" for the CS3 collection ?
Anybody have a clue as how to do this ?
How do I reinstall the Adobe Media Encoder CS3 ?

Mr Hunt...
I my view you're a wizzard with statute more than Merlin...
Here's what I found. Last time I shut down ProPre I was on a dual monitor.
I tossed my laptop in the car went to 2nd location.
Re-configured laptop for single monitor mode.
Upon starting up ProPre hammered encoding and the resulting screen opened ...... which I could not see.
PrePro DOES NOT sense hardware.... Dhaaaaaaaaa
Its stays stuck in dual monitor mode !!!!!
You need a second monitor to unstick it !!!!!
I was unable to set it back to single mode without the 2nd monitor !!!
Yahhoooo !!!! Its working again !!!!!
Dhaaaaaaa

Watch Folder in Adobe Media Encoder CS3

Hello,
We are currently working on a project to automate some video encoding. Files uploaded to a server should get automatically converted into a specific format. (Unfortunately) we only have the CS3 to work with.
We couldn't find the "watch folder function" (like in CS5, CS6) in the CS3 AME (since it is not even an own application, but built into Premiere/AE?). Does this AME version even support the function? Is there any other way we could solve the problem?
Thanks in advance,
- Marc

This functionality is not in the CS3 version of the application.

Trying to export an apple compatible h264 from windows PPCS4 media encoder

So far the only setting that seems to work is "Apple TV" but I can only export up to 720p with that. Do I simply bump up the resolution of the Apple TV setting?
None of the 1080 settings under h264 seem to be recognized by apple when coming from my Vista machine.

Hi,
Hmmmm.. Won't apple recognize Quicktime ? Try using Quicktime and H264...will make a MOV file....set resolution etc as needed...( will be a custom setting probably...)
Using quicktime pro I can import a mov file and then export to various formats, including apple TV...if that's what you're wanting...
Sorry.. but I use windows and CS3 ...so I can't test what you want to do...maybe someone else here can be more helpful...
Rod

Adobe Media Encoder - CS3

In general, which encoding method would provide the least compression, highest quality?

OK, uncompressed or Lagarith or HuffYuv, depending on storage capacity and disk speed. Likely Lagarith is your best option.

Problem Encoding WMV to FLV with Media Encoder CS4 (but not with CS3)

Hello,
I have been attempting to encode some WMV files with Flash Media Encoder CS4 (I have Adobe Creative Suite CS4 installed) but it has failed, generating this error:
- Source File: C:\Documents and Settings\usf\Desktop\incoming\ch01.wmv
- Output File: C:\Documents and Settings\usf\Desktop\incoming\ch01_3.flv
- Preset Used: Custom
- Video: 624x343, Same as source [fps]
- Audio: MPEG Layer III (MP3), 128 [kbps], Stereo
- Bitrate: VBR, 400.00 [kbps]
- Encoding Time: 00:06:36
5/28/2010 11:26:16 AM : Encoding Failed
Error compiling movie.
Unknown error.
On another computer where Adobe Media Encoder CS3 is installed (with Creative Suite CS3), I experience no such problem. I do notice that when I add the WMV to Adobe Media Encoder CS3, it opens a window that prompts me to use "ffdshow", which will apparently work if it's configured to decode the file. I click "OK" and start the queue in the encoder. A few minutes later I get a successfully encoded FLV file.
I have come to question whether Adobe Media Encoder CS4 should be re-installed, whether the entire Suite should re-installed, or if there is some patch or fix I can install somewhere. Adobe Media Encoder CS4 is installed on my "production" computer which also has Adobe Premiere Pro (CS3) and Adobe Premiere Elements (7).
Could use some advice here.
Glen
P.S. the files will also not export to FLV using Adobe Premiere or Premiere elements...

Again, the reason we are capturing with Windows Media Encoder is because we tried using Live Flash Encoder to capture directly into flash but our equipment wasn't fast enough and it was dropping frames all over the place. We also don't have the space to capture into an uncompressed format because we don't have the available storage, and our events can be 8 hours long or more (each video is about 15 minutes, 20 or more videos)
Ive listened to everything in my workflow and it sounds fine until the outputted FLV file from AME.
WME is capturing at the following specs:
160kbps 48KHz Windows Media Audio 9.2 codec (stereo) 1 pass CBR
1800kbps 1 pass CBR video
29.97 fps
640x360 resolution
buffer size: 5 seconds
key frame interval: 8 seconds
I have verified this with a codec info utility I ran on the wmv files.
AME is encoding with the following specs:
FLV Multiplexing
On2 VP6 codec
620x360 resolution
800kbps 2 pass VBR
100% undershoot at best quality
160kbps stereo MP3 audio
I verified the above with the same codec info utility (gspot 2.70a) and it is all acurate, it also told me that the audio is at 44.1KHz rather than 48 (there was no place to specify this, is this a limitatino of the VP6 codec?)
Yes, these are our source assets. They're being captured either through an XL2 via firewire, or from an analog program feed converted to firewire via a Canopus converter box.
If anyone has any suggestions on how to get rid of this, or a different encoder (either to capture with rather low cpu resources, or to encode into flash) let me know. I can provide a sample of the clipping if you need
Thanks,
Peter

"R6025 -pure virtual function call" Error While Use Adobe Media Encoder

I'm trying to use Adobe Media Encoder (CS3) to output a project to H.264. I have about 3 minutes of footage on the Premier Pro CS3 Timeline, all of it in Cineform AVI intermediate format. When I export the movie through AME and select 2-pass VBR, it gets through the first pass, but crashes at 50% on the second pass with the error:
"Microsoft Visual C++ Runtime Library
Runtime Error!
Program E:\Progra...
R6025
-pure virtual function call"
Any ideas what may be causing this error?

Point taken...
I'm on a Dell XPS 720 Windows XP (32-bit) system, with all up-to-date service packs and patches. I have 4GB RAM installed, and Production Premium CS3, TMPGEncXPress and Cineform's Neo Scene. Neo Scene is a recent addition and the problem existed prior to its installation. I have two 7900GS graphics cards (each with 256MB video RAM), running in SLI mode.
I dual boot Windows XP: One system is "Messy" with all kinds of stuff installed. The other is "Clean" and has virtually nothing installed, except for the three suites previously mentioned. No anti-virus or anti-spyware software is installed on the Clean system. I get the error on both systems.
I saw the post from September 2007 reference vcredist_x86. I'll be trying that at my next opportunity, however, I'm not sure that will fix it, as I don't see why both systems would suffer from the same corruption. I'll also be swapping out RAM to see if that fixes the issue.

Sizes In Adobe Media Encoder...

I make a PAL movie in Premiere Pro CS3 with clips from my Panasonic GS500 camera. Export to Adobe Media Encoder CS3 and it gives an output frame size (for FLV) of 1024 x 576.
I open the same sequence in Premiere Pro CS4 and Export to Adobe Media Encoder CS4 and the frame size becomes 1050 x 576.
Why the two different width sizes? I have not done any resizing or cropping.
If I do resize the video by half, so that 576 becomes 288 (keeping the proportion link checked) the size becomes 512 x 288. 512 is not half of 1050.
Also, why is there no Deinterlace button, as there was on CS3. Do we assume that the video is being deinterlaced by default? Or, as some others have complained when exporting to DVD, is the exported video remaining interlaced? This might account for why I cannot get the same FLV picture quality, using exactly the same settings, as I did with CS3.
Any help greatly appreciated.
Spok.

HI Colin,
well, i used to be very happy with SorensonSqueeze, but for more than a year now, I'm just using Compressor (indeed from FCStudio).
It's VERY handy and lets you manage your settings in a way AME can't even think of in version 8... I mean nothing extraordinary, just the way it should, with possibility to move, edit, group, duplicate, rename, describe your settings...
And as for flv encoding (at the time of CS3, which I still have on my desktop machine) by installing the Suite, it would also install the codec for Compressor.. Excellent! Which CS4 doesn't do anymore... which forces us to use this terrible AME.. That's the scandale to my humble opinion!
But ok, via Compressor, you get the settings for flv... with the deinterlace box as on the attached image. Indeed with VP6 encoder.
And no, me neither, i'm not torn up, but it would have been nice Adobe gave us the info!
Compressor does also a great job in slomo. That's quite new but impressive. And Compressor is MUCH faster than AME.. AME takes ages! For a good result, I agree.
voila...

Hilights Clipping Problem with Premiere CS3 Media Encoder

I've just discovered a pretty serious problem with the way Premiere CS3 processes video to the Media Encoder.
Many of you are familiar with the term "super whites", the ability of modern cameras to capture and record levels above 100 IRE. With HDV and newer technology, recording to 109 IRE is quite common.
I was aware for some time that importing this footage into Premiere results in a hard truncation of whites above 100 IRE. However, I discovered last month that the Fast Color Corrector has a Output Levels adjustment that can rescale all the levels to fit down in the 0-100 IRE range. I verified this using the scopes in Premiere and by observing recovered details in my footage. I was even able to export frames to TIFF files and show the recovered highlights in the exported TIFFs. The difference is substantial and not subtle--it's the difference between a sky completely blown to white and one where you can see the sky is blue with clouds in it.
Last night, I discovered that the Unsharp Mask filter doesn't handle footage above 100 IRE, either. Even if I use Levels to set 0-235 RGB range, somehow, Unsharp Mask is processing the un-level-adjusted signal, regardless of stacking order of the filters.
I rendered two Blu-ray discs, one with Unsharp and the other without. To my astonishment, BOTH discs lacked any detail in the highlights--the whites were clipped at 100 IRE!
Now I turned attention to the Media Encoder. Pausing on a frame where I can see the difference between 100 IRE and 109 IRE and shades in between, I fire up the Media Encoder and note that even in ME's previews screens, the whites are already clipped. There is more highlight detail in the program monitor, whereas it's all gone in the Media Encoder's display.
It is obvious that highlight information, even scaled back to 0-235, is being treated as if it were 0-255 and clipped at 235 before passing to the encoder. This is a real disappointment, because there is another half f-stop of detail up there that I was trying to pull into the useable range of 100 IRE for the Blu-ray disc. Since it is very difficult to shoot footage and limit the peak whites in-camera to no more than 100 IRE, nearly all of us are losing valuable picture information.
Even if you can recover the highlights on the timeline through a Levels filter, it gets thrown away again on the way to the Media Encoder. Short of exporting a few hundred thousand frames as .TGA files and then loading those back in and rendering out to whatever motion CODEC, I am at a loss as to how to get Premiere to leave the whites intact.
I haven't seen this issue discussed in any detail here. Has anyone found a way around it, besides reshooting all your footage of one-time events to sub 100 IRE levels?

I'd rather the camera added that extra lattitide within the appropriate 0 to 100 IRE range.
That's a lot like saying you want 10 gallons of water in an 9-gallon jug.
As it is, it looks like such adjustments will need to be done on a clip by clip basis.
Or, you can do it the "Dan" way in AviSynth. I wrote a script function called SoftLimiter: It applies photoshop-style curves on the Y + U + V channels to bring the maximums within legal range… using a sort-of "soft-knee" approach to reducing extreme highlights and/or oversaturated areas.
It causes a tiny bit of posterization in the highlights, just like all 8-bit per channel color adjustments do… but it is hardly noticeable on a computer screen and even less on TVs.
SoftLimiter for AviSynth 2.5
Create a folder C:\SoftLimiterCurves\ and place the .amp curves files in that folder.
Place the other files in your AviSynth 2.5 / plugins folder.
The example below assumes DV avi files and requires a DV codec (such as Cecocida DV, MainConcept, Canopus) that can read / write in YUV formats.
Create a script like this:
AviSource("dv.avi", pixel_type="YUY2")
SoftLimiter()
Open the script in VirtualDub, use Video / Fast Recompress, Select Cedocida DV codec. File / Save as .avi
Before:
After:
And, Jim… you can place your dv2film() command at the end of this script if that's what you're trying to accomplish.

Problem with interlacing when exporting with Media Encoder CS 5.5

It seems that when exporting a Video with interlacing in Premiere 5.5 with Media Encoder 5.5, the exported video is still interlaced although it is rendered with progressive settings. When rendering with the same settings through Premiere 5.5 without Media Encoder 5.5 (Button "Export") it is correct and progressive.
I tried this with H264 and MPEG2. Anyone experiencing this problem too?
Thanx!

Were the field interpretted correctly in the first place? Even if you think they are, try reversing them. I've just been through hell doing something similar with a mishmash of client material from around the world.
In some instances I switched field order (In the File>Modify) although it didn't seem logical. In others, I used AE CS5.5 to added the Reduce Interlace Flicker filter.

Media Encoder CC crashes while working on queued H264 files.

While I am editing my videos I send them to Adobe Media Encoder CC as H264 for youtube. Even with only encoder running windows 7 crashes with the blue screen. This is the only program that causes this. I was looking to uninstall this program and it is not an option in control panel. Do I have to uninstall Premiere CC to have this removed? I was going to try an uninstall/reinstall to test if this fixes it. The machine is a current machine with 64GB ram running on SSD.
Thanks all

A BSOD on Windows 7 is most often a sign of a serious problem, much more frequently caused by faulty hardware or driver than the actual software running when the crash occurred.
As exports often push a system to it's limits, I'd probably start by looking at the cooling of your system.

Adobe media encoder in PP CS3

Hi there
I'm using Premiere Pro CS3, when I try to launch Adobe media encoder or Matrox media encoder, the program bugs. Any help? I'm very new in this field.
Thanx

Pull the Matrox out. Try with a standard project and likely your problems are solved.
Matrox cards are best used in a fashion they were designed for, as a doorstopper.

Exporting in Adobe Media Encoder fails in CS4 after CS3 is removed.

There's an issue with Adobe Media Encoder in CS4 where encoding will fail after CS3 is uninstalled.
If you never had CS3 installed on your machine - no problem.
If you never had CS3 and CS4 installed at the same time - no problem.
If you had CS3 and CS4 installed concurrently, then uninstalled CS3 - Houston, you have a problem.
You will need to uninstall CS4 and then reinstall CS4.
The error message is:
Encoding Failed
Could not read from the source. Please check if it has moved or been deleted.
One more thing I forgot to mention, this is a Win-only issue.

>Does anyone understand this?
Simple:
1. Open a Windows Explorer window and navigate to the folder that contains "dynamiclinkmanager.exe"
2. Open a
second Windows Explorer window and navigate to the folder that contains "Premiere.exe"
3. Arrange the windows side by side.
4. Right-click on "Premiere.exe" and drag to the first explorer window, targeting between the files so as to avoid any specific file.
5. Release the right-hand mouse button.
6. Select "create shortcut here" from the pop-up menu.
Cheers
Eddie
PremiereProPedia (
RSS feed)
- Over 300 frequently answered questions
- Over 250 free tutorials
- Maintained by editors like
you
Forum FAQ

Problems rendering Every-line Composer texts with Adobe Media Encoder

I find the text paragraph setting "Adobe Every-line Composer" a huge time saver when dealing with large amounts of text in after effects. I rarely have to do any manual tracking or line breaks to make it look good, as opposed to working with the standard Single-line Composer.
The problem is that when I render through Adobe Media Encoder (which I'm forced to do since they removed H264-mp4 support from AE:s internal renderer) the text is treated like single-line composed text. So the final render doesn't look like my AE project.
I've found two solutions to this problem:
1. Render a lossless video file in the AE renderer and then compress it with Media Encoder. This takes more time and HDD space, and it doesn't allow me to continue working in AE while rendering.
2. Only use Single-line composed text and make all adjustments manually, the old school way. This would not be a problem if I had not already used, and fallen in love with, the Every-line option.
Is there anyone that can think of a third, and preferably better, solution?
I use the CC 2014 versions of AE and AMC.

No, the text doesn't animate at all. It's just a normal static text box. The text part is extremely simple. All animations are done in other layers and pre-comps, combined with pre-rendered 3D graphics from Cinema 4D, rendered as image sequences. My problem is a bug, plain and simple. Or perhaps you could call it a "lack of feature support" or an "incompatibility between AE and Adobe Media Encoder".
My problem appears only when my AE project has text boxes with the "Every-line Composer" option enabled (press the menu button in the Paragraph window to find it), AND the project is rendered through Adobe Media Encoder, no matter which output format I use. I have no problems what so ever inside of after effects, or when rendering Single-line Composer text in AMC.
So, the problem is that Media Encoder doesn't recognize Every-line composed text. Instead it changes it to Single-line composed text, messing up text tracking and line breaks.
To clarify: the Adobe Every-line Composer is analyzing the entire text box instead of only the current line. That way it can automatically change the tracking of individual lines to better distribute the line breaks and build a better whole, avoiding those stray words on the last line for example. Extremely handy, if you could only render it.
I never wrote anything about animating text or that the codec is related to the text problems in any way. AMC is the problem. The codec is only a secondary problem since its the lack of mp4 H264 support that forces me to use Media Encoder in the first place, instead of using the AE render queue as I did in previous versions of AE. I like many things about rendering through AMC, like being able to continue working in AE while rendering, but there are still way too many glitches. And of course, there's the inability to render flv-files in AMC CC 2014, and Adobe's inability to provide a solution other than "Use an older version of AMC". Flv is their own damn format for christ's sake.
Well, enough rambling.
To put it simple:
Has anyone had a problem with "Every-line Composer" in combination with Adobe Media Encoder? Did you find a solution other than the two less-than-perfect ones in my first message?
Thanks!

H264 progressive / buffering problem - Media Encoder CS3

Similar Messages

Maybe you are looking for