Media Encoder H.264 settings

I hope someone can help me with this. I created a video in CS4 in HDV, I need to output using the following specs my client has asked for:
fullscreen video at 1920 x 1080 resolution,
Quicktime h.264 - best quality / multipass.
Sound is 48 KHz 16b.
They are using FCPro Apple ProRes 422 for compression.
Do I use the H.264 Blu-ray setting for output? Any help on what the setting should be is greatly appreciated - or do I need to get more info from the client.
I've never had to do this type of output before and I want to make sure I give them the correct format.
Thanks

Hi,
When you get the export done and if you like it could you put your settings up here ( maybe a screenshot of settings for video ) and share it with us? Others might profit later as they search this database for answers. Thanks...

Similar Messages

Adobe prem / media encoder h.264 blu-ray jitters, flickers /w slow-mo

hello
using the Adobe Production Premium CS4 pack... hardware is not an issue, also all the latest updates are installed.. prem 4.2.1 (003), encoder 4.2.0.006
after export and authoring, we are having strange glowing flickers, and bad slo-motion effect playback
the problem seems to be consistent with slo-motion and time remapping, frame holds and especially when an additive dissolve is thrown in.
the edit's are far from saturated with these effects, but a simple frame-hold with motion-rotation and motion-scale occurring with keyframes. the problem also happens with something as simple as a 30% speed/duration added onto a clip..
the footage is captured and on a timeline at - 1440x1080 (1.3333) HD Anamorphic, 25fps (50i)
the export profile after edit is - H.264 Blu-ray - 1440 x 1080i 25 High Quality
i get the feeling the problem may be occurring as the footage is remaining as interlaced footage through-out and not being blended or discarded to progressive.
i have tried making the footage progressive on export thinking it might solve the problem, but it turns out there is no such thing as progressive HD PAL in media encoder and encore
i love adobe's workflow but we have never been fond of main-concept from the start with things like this, even Mpeg2-DVD exports come out softer than you'd expect
any thoughts, light or general directions on what to do to help figure out the problem would be great..

after around 30 small sample exports, builds and different renders... I have discovered the problem and am now on track to fixing it..
it turns out certain adobe effects such as 'lighting effects' do NOT work well with slo-mo or frame held clips.. upon taking this one effect off, the clip looks flatter and less dynamic in context of my edit, but the clip plays normally no matter what the export settings, codec or format..
what's hallarious is that these effects and edits export and author perfectly fine onto DVD through Mpeg2.. i guess they just flatten better etc.. i get the impression when Adobe started crafting their software for HD they just built on top of the normal effects etc they already had and expected them to work.. if only Premiere could get the updates, priority and attention Photoshop does..
again, i love premiere's work flow, i just can't see how they can put the word 'Pro / Professional' near this software...
many thanks all
Steve

Flash Media Encoder 2.5 Settings

I found the settings where you can specify the restarting
stuff for the Encoder, I was wondering about days, hours,
minutes... does this mean #of days along with a specific time? If I
put in 4 for hours, would that be at 4am? Do I need all these
settings or are they exclusive with each other meaning I would only
need days if I wanted days.
Also, I'm assuming these settings just go into the XML
profile for each session?

The time is relative to the time encoding started. If you put
4 hrs then FME would restart 4 hours after the start of
encoding

Media Encoder H.264 Doesn't Work

Got a bit of a problem. When I encode videos in H.264 the files come out fine and play through quicktime fine, but on the player on my site they do not work. I'm a bit puzzeled. Is this a known issue?

OK, if they play fine in Apple QT Player, but not on your site, tell us more about the player on your site. Also, what are the problems with that player?
As an aside, some users have had more luck with the Lead, or the MainConcept H.264 CODEC's, than with Apple's. Just something to think about.
Good luck,
Hunt

Media Encoder -- Audio -- Advanced Settings -- Precedence -- What is the difference between the two options presented here and how does it effect the final file?

I see no literature in any of the manuals that explains this option -- what is it exactly and how does it work?

endasil wrote:
Um...have you compared when specifying v = 0x0FFFF, as an arbitrary example?
Edit All right I'll be a little more specific. How the heck would your Test1 method know if it's only being passed int values <= 255?
Edited by: endasil on Nov 6, 2007 8:48 PMI see, well, why would it care? all it does is take int and store it into a byte. what else could it do with an int and byte array? Also, if you wanted to check for values <= 255 one could simply add asm code to do that, after all, Test2.test2() has a signature of ([BI) that is (byte[] ba, int v). So, if the method wants to fool around with v* it can iload_1* and do any comparison tests, ifeq* etc..., and latter stuff it into byte array using bastore* without the unnecessary i2b* call.
I just don't see the use of the i2b* instruction if bastore* could careless. Will this cause the stack to become unlined and cause trouble program down-the-line in execution? I am thinking that I loaded an int*, +4bytes+, but only consumed 1byte. But now that I think about it, iload_1 loads an int* onto local heap so it should get cleaned up when the program exits. So, as long as I made bastore* the last instruction in the program I shouldn't have a problem. Or maybe this doesn't matter either?
*Also, since ba is an byte[] why would I want to check it for anything other than a byte value? if I wanted to get an int I would have created an int[]*
My point is that as long as one wants to stuff an int into a byte array the i2b instruction is overkill, albeit not much, and I just do see the usefulness of it.
This is for when I do something like, byte_array[i] = '-', and the compilers say loss of information and I cast '-' to (byte)'-', meaning I don't care if I loss any information. but it called i2b anyways byte_array[i] = '-' yields the same result.
I just didn't understand what was behind this.
Does that answer that question or am I missing anything?
Edited by: earamsey on Nov 6, 2007 8:04 PM

Adobe Media Encoder .mp4 not playing on iOS

trying to get my video to work on iOS.
i know it has to be .mp4 and i have various videos i have successfully encoded but some do not work when I render them as .mp4
I have been taking the .mov files (they were rendered to QT using Animation)
using Adobe Media Encoder h.264 which gives me a .mp4 file. (but like I said...some are not working on iOS).
so what is the traick with Adobe Media Encoder???
settings:
- Source File: G:\HF_SC_BACKUP\HF_SC\_PT_Final\Open\Final\2009\HF_09b.mov
- Output File: G:\HF_SC_BACKUP\HF_SC\_PT_Final\Open\Final\2009\HF_09b_iOS3.mp4
- Preset Used:
Format h.264
(stream complatabilty did not matter)

IOS does not support autoplay for audio or video.

CS4 Export AVI Media Encoder

Trying to export an uncompressed AVI from CS4 via Media Encoder. Project settings are 1440x1080, 29.97. Project is compromised of mainly images and graphics. Going to be played off laptop connected to Plasma via HDMI. Kind of a short 5 minute presentation.
Issue is I have tried many export settings and using:
Microsoft AVI
Video Codec - NONE
Width - 1440
Height - 1080
Frame Rate 29.97
Field - Progressive
Aspect - HD Anamorphic (1.333)
It exports the AVI but in Windows Media Player it playes 4:3. Can't figure why it keeps going back to 4:3 when aspect is set correctly.
Was so much better in CS3. Any thoughts??

Thanks Jeff. I kind of thought about that after I posted. I did bring it back into Premiere and it was perfect. Everything looked good. Ok so Windows Media Player blows. Now I guess I'll have to find a good player that will be able to handle it. I would just play out of Pr and setup the plasma as a monitor but it might slow things down.

Media Encoder CC 2014 Exports larger file than Media Encoder CC with same settings

We like to deliver final exports to most of our clients with the following settings:
Format: Quicktime
Codec: H.264
Quality: 100
1920x1080, 23.976, progressive, square pixels
use maximum render quality
audio: uncompressed, 48khz, stereo, 16 bit, single track
When I used to export a ~5 minute video using these settings with Premiere or Media Encoder CC (7.2.2.29), I would get a file ~1GB. If I export a ~5 minute video using these settings in Premiere or Media Encoder CC 2014 (8.0.1.48), the result is ~ 4GB.
Any thoughts on why this might be? I assume it's a user error but I can't nail down what it is.
Thanks for your help!

Hi matthewrichie88,
I used the same settings that you have mentioned above on a Windows 7 computer and got the same file size with both versions of Media Encoder. Please specify if you have a Mac or a Windows and which OS exactly? It would really help if you can post screenshots of your export settings with both versions. Give more details about the source files as well.
Thanks!
Rameez

Media Encoder CC exporting the wrong resolution in custom preset h.264

I have two custom presets in Media Encoder CC. The original file is an mov Lossless 720x480 from After Effects. One is h.264 mp4 720x480 and the other is h.264 640x480. When I encode the resolutions are 872x480 and 581x480 respectively. Not sure what I have going on here. The presets worked with the same settings just fine in Media Encoder CS6 on another computer. Any ideas?

Bump

Media Encoder doesn't recognize custom export settings from Premiere Pro CS6

When I use export media in Pr CS6 and use custom settings (H.264) and click Queue when it arrives in Media Encoder none of the custom settings are there, instead it always defaults to .F4V.
Here is a screenshot of custom settings in Pr CS6:
And here is what happens in Media Encoder:
Thanks for your help!
Nick

So, it looks like Media Encoder is stuck in a trial version? The only formats available are indeed .f4v, .flv, .mp3 & h.264. Is a reinstall of Media Encoder the fix?

H.264 Audio Out Of Sync in Media Encoder. Help Needed.

I use Adobe Premiere Pro CS3 and I find that the best way to get a good video with low file size is by Exporting to Media Encoder and using
the H.264 codec. Note, this is the codec by itself NOT the one used with the Quicktime preset.
Here's the problem : When I export these files, they always end up a few frames slower than what I have on the timeline and the audio is always
out of sync by just less than a second. Although it's a very small difference, timing is crucial in editing when it comes to dialogue as I'm sure anyone who uses Premiere understands.
I have tried tweaking with the settings. I've used VBR 1 Pass, 2 Pass, CBR, Progressive Scan, Upper and Lower fields first, all of that.
Has anyone else had this problem, and if so how was it solved?
IF not, can anyone give me a good solution as to how I can get good video quality + low file size. The benchmark is a 45second video takes a maximum of 5MB, Quicktime video. Any suggestions or any methods you find better? Any ideas on how the guys at Apple Trailers manage to do the job so well?
All the help is appreciated. Thanks, guys!

Hi Jeff, I've experimented with a bunch of formats to find the root of the problem, but for this conversation I'll use a Quicktime (.mov) example.
Source Footage Settings :
Video : 640x268, Millions of colors. FPS : 23.98 Data Rate : 1.15mbits/sec
Audio : AAC, Stereo (L R), 44.100 kHz
Sequence Settings :
Video : Quicktime Movie, Pixel Depth : 640, Frame Rate : 23.976
Audio : Source Audio Format : 44100 Hz - 16bit Stereo. Project Audio Format : 44100 Hz - 32bit floating point - Stereo
Average Data Rate : 141KB / second
Pixel Aspect Ratio : 1.0 (Square Pixels)
Export Settings :
Main Concept H.264 Video, Custom Preset.
Video : Frame width & height is same as source. Frame Rate : 23.976. Field Order : None (Progressive) Pixel Aspect Ratio : Square Pixels
Profile : High. Level : 3.0. Encoding : VBR, 1 Pass. Target Bitrate [Mbps] : 1.3. Maximum Bitrate [Mbps] : 1.5
Audio : AAC, Stereo, 44.1 kHz. Audio Quality : High. Bitrate [kbps] : 192. Precedence : Bitrate
Multiplexer : MP4. Stream Compatibility : Standard
NOTE : I have done the same with .avi files as well with the same audio lag issues. As for the file above, it's a trailer off Apple Trailers which also uses the H.264 encoding. To prove that there is a lag, I imported the 'rendered' file back into Premiere, placed it on a seperate layer on top of the original footage in the timeline and pressed play. As expected, there was a difference in audio playback and video was about a frame late.
Any ideas? Thanks!

AE CS4 render engine / Adobe Media Encoder won't create a container for h.264 blu-ray

here's the problem.
First, I tried to render a comp using the render engine inside AE using h.264 blu-ray preset.
It was supposed to create 1 file, but I ended up with 3 : audio track, video and a file with .xmpses extension.
I then decided to render it in lossless .mov, which works fine, but 3:40 minutes is taking up over 8gb, which is of course, unacceptable.
After that, I've put the .mov file into Media Encoder to try h.264 blu-ray there.
Absolutely the same ********.
I'm using the Mac version of AE CS4.
Here is the screenshot of original .mov file and the result. As you see, it refuses to make a container. This is absolutely unacceptable

It raises another question: what settings do I need to encode the comp in 720p resolution without taking up lots of space?
Well, it depends on whether you need a production master (something for broadcast, for example, or to use as a source for other encoding tasks) or if you want a version for distribution. If it's the former, there's nothing wrong with "lots of space" - A Quicktime file with PNG or Animation codec is a good idea, but it will take a lot of space. If it's the latter, H264 is perfect but there's no built-in preset to take 720 material to the web.
You could do this:
* Pick the generic H264 template. You'll see that it will give an error if you attempt to render, because the default setting uses an H264 profile/level which doesn't let you use HD resolutions.
* In the H264 video options, set the "Profile" menu to "Main" and "Level" to 4.0. That will keep it compatible to Quicktime and Flash player, while allowing larger frame sizes and higher bit rates.
* Set Target Bitrate to 5-8 Mbps and Maximum Bitrate to 9-10 Mbps if you're targetting web delivery. That's a bit over what Apple uses for 720p content on the Apple TV, for example.
The H264 original preset will instruct you in the comment field to stretch to 640x480 in Output Module. There's no need, since you are using a profile/level combination which allows higher frame sizes.

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.

CS6-Media Encoder Fails on long (1hr +) H.264 render

Windows 7 - 64 Bit. 8 GBs RAM
Adobe Pr and other programs on C: internal Plenty of hard disk space left 300+GBs
External high speed 7200 RPM RAID 1 where the media is stored.
External high speed 7200 RPM Non RAID drive for rendering to be written to.
Both drives are eSata.
CS6 Pr and Media Encoder 6.0.0.382 (OP update: It appears that has been an update to this version, I am going to download the updates and see if that fixes this.)
FOLLOW UP: It appears that the update did fix the problem. I have multiple workstations and was under the impression I had updated them all. I have not fully tested this yet, but for now, I consider it fixed.
Footage is a single capture of a lecture. 1 hr. 20 minutes.
Shot on Canon xf105 in MXF format at 1280x720 23.976p (US)
Footage goes together fine (many multiple file clips 'chained' or butted up against one another, as is done when you shoot a continuous take)
The footage plays fine in Pr in final form for export.
No special effects. one dissolve (intro title slide to lecture)
Reproduceable problem:
i export to Media Encoder.
I choose H.264 and Vimeo Wide Screen SD 23.976
The file exports about 2/3rds of the way, not the same place each time, and fails with no definitive error message. The log shows, "Export Error: Error compiling movie. Unknown error."
Rendered file to external drive (have more than one, have tried it on two, with same results)
All drives have plenty of disk space on them.
I tried cleaning the Media Encoder Media Cache. Same result.
I tried moving the cache files to an almost empty external disk. No change.
I broke the video into a 10 minute segment, it rendered just fine with the same settings.
This seems to be a bug in Media Encoder. Is there a fix for this? A workaround? My client would like a single long file of the presentation.
Could the 8 GBs of RAM be an issue? Not sure why it would. Or is this a known bug for Media Encoder?
I also had a second job today, similar in that I needed to take 6 multiple takes of the same person, drop them onto a timeline and render it to Vimeo for them to review. same issue. Got 13'05" into the compile and it failed. So something is odd. I have compiled much longer footage before, that was done with this camera.

If you have done a complete reinstall, and ran the Adobe CleanScript CS5 (that is the latest), then a Repair Install should not be needed - it would do nothing.
For info, to do a Repair Install, one would insert the installation disc. When the installer module has loaded, it will survey one's system. If it finds the Adobe program(s), it will ask if you wish to Uninstall, or Repair Install. When one chooses Repair Install, it surveys the system again, for that program, and will replace, or correct any issues. This is usually MUCH faster, than doing an uninstall/reinstall.
Good luck, and not sure what else could be the cause.
Hunt

CS4 Media Encoder- Two Pass CBR settings?

I have come across something strange in the stand alone Adobe Media Encoder CS4 (Windows and Mac) when attempting to encode an FLV with on2vp6.
There is an option under CBR that allows for a two pass, however it also has the minimum bitrate, maximum bitrate and bitrate variability options. This makes sense for VBR, but why are they there for in CBR? Are they inactive for CBR? Shouldn't they be dimmed? Are you supposed to set to 100% and leave it? Is it a bug? I know H.264 only has one pass, and it acts the same way as FLV/on2vp6 One Pass.
One of the whole points CBR is that you have a defined bitrate with no variation, used predominantly for HTTP Pseudo Streaming or Streaming. I have a bitrate limit imposed on a server, so I add video and audio bitrates together and get the total bitrate and I want a steady stream. With minimum and maximum settings it would vary depending on your content hence the term VBR which seems contradictory to CBR...
Can anyone please shed some light on this?
Thanks in advance.
Jon

Thanks again for the reply. The next question would be, is One Pass CBR then the only true CBR (or best for streaming/pseudo streaming)?
Adobe's Docs skipped right over that (2 Pass and CBR)...seems pretty important, maybe they figure most will just use One Pass for CBR.
The funny thing is you can't find any real references on the web to Two Pass CBR either. Even Google wants me to change it to VBR Two Pass in my searches :-)
The reason I ask is that when we ran Two Pass CBR, it flagged an error on the HTTP Psuedo Stream server (similar to Xmoov PHP) because it exceeded the bitrate limit at a portion of the video (evidentially) and stopped it in its tracks... Unless maybe it was a coincidence but it was tried several times supposedly. I didn't witness this, because we don't have access to the client's Intranet/VPN (long story). I built a JWPlayer/Xmoov PHP setup at our site to replicate, but it doesn't have the bandwidth throttling enabled to test that theory. I will try to run some more tests and post back here if I find the anomaly.
I much prefer VBR 2-Pass anyway for quality but you can't really stream it effectively.
-Jon

Media Encoder H.264 settings

Similar Messages

Maybe you are looking for