H.264 Encoding for TV

I have a bunch of old videos and would like to encode them for watching on TV via Front Row (or similar) using H.264.
What would be a good data rate for this?
Thanks!

Generally speaking H264 is supposed to be about twice as efficient as MPEG2. I think that's probably overstating the case somewhat (i.e. H264 isn't really twice as "good"). However you can certainly cut back somewhat from what you'd use with MPEG2.
Next consideration is the resolution/dimension of the final video. Do you want to go 640x480 (NTSC 4:3 aspect ratio) or something smaller? Since you're starting with video tape I'd suggest something like 480x360 (that should be large enough by a good margin to get all of the quality from a video tape). However, you might even want to drop down to 320x240 since that would be compatible with the video iPod and potentially other mobile, hand-held devices.
Finally, if you go with 640x480 I'd suggest something in the 3Mb to 4Mb per second range (for relatively demanding material, less for so-called "talking heads," and perhaps a bit more for extreme action), that would scale to 1.7Mb to 2.3Mb per second for 480x360, and 750Kb to 1Mb per second for 320x240. If you plan on using Front Row and want to store your video on a remote server (accessed either wirelessly or over ethernet) then you will definitely want to enable the "streaming" option when you encode the video. In fact you may want to use the streaming option in every case (for future compatibility).
If you plan on viewing this video on a computer display or any type of LCD or high-definition device you may also want to consider a de-interlace step for the 640x480 and 480x360 resolutions. You won't need that for the 320x240 video since 240 is exactly one half of the vertical resolution for standard NTSC DV (720x480). However, if you're using PAL you'll need to adjust all of the above resolutions to fit the proper form factors.
As always, the beauty will be in the eye of the beholder. Thus I'd suggest that you try something near the above and adjust accordingly (based upon what you see and like or dislike).

Similar Messages

Have plan feature H.264 Encoding for Cameras on Mobile?

Have plan feature H.264 Encoding for Cameras on Mobile?
Thank you

Generally speaking H264 is supposed to be about twice as efficient as MPEG2. I think that's probably overstating the case somewhat (i.e. H264 isn't really twice as "good"). However you can certainly cut back somewhat from what you'd use with MPEG2.
Next consideration is the resolution/dimension of the final video. Do you want to go 640x480 (NTSC 4:3 aspect ratio) or something smaller? Since you're starting with video tape I'd suggest something like 480x360 (that should be large enough by a good margin to get all of the quality from a video tape). However, you might even want to drop down to 320x240 since that would be compatible with the video iPod and potentially other mobile, hand-held devices.
Finally, if you go with 640x480 I'd suggest something in the 3Mb to 4Mb per second range (for relatively demanding material, less for so-called "talking heads," and perhaps a bit more for extreme action), that would scale to 1.7Mb to 2.3Mb per second for 480x360, and 750Kb to 1Mb per second for 320x240. If you plan on using Front Row and want to store your video on a remote server (accessed either wirelessly or over ethernet) then you will definitely want to enable the "streaming" option when you encode the video. In fact you may want to use the streaming option in every case (for future compatibility).
If you plan on viewing this video on a computer display or any type of LCD or high-definition device you may also want to consider a de-interlace step for the 640x480 and 480x360 resolutions. You won't need that for the 320x240 video since 240 is exactly one half of the vertical resolution for standard NTSC DV (720x480). However, if you're using PAL you'll need to adjust all of the above resolutions to fit the proper form factors.
As always, the beauty will be in the eye of the beholder. Thus I'd suggest that you try something near the above and adjust accordingly (based upon what you see and like or dislike).

H.264 encoding for export - CS4

Does higher bitrate encoding equal higher quality results in all instances?
I can of course see increased bitrate encoding reflected in
incrementally larger file sizes, but the quality difference
seems to be much more subtle.
thanks

My understanding of how material is broadcast these days is no matter what
you supply to the broadcaster... it is going to be "converted to something more
convenient for them to "send" to air. Especially so with satellite where bandwidth is a
bigger issue. Much broadcast media is file streamed from servers so understandeably the files sizes are eventually reduced.
I provide uncompressed avi and movs that in the final out come..., I know are broadcast at some level of MPEG.
eg 30 second HD TVCs at 2GB files become 50mb mpegs.
My rationale is that give them the highest quality possible and let any degredation occur their end ( where I have no control)

H.264/AVC software encoding for cameras

Hi All,
             Please let me know, how can we activate H.264/AVC video encoding (new feature in Flash player 11 [H.264/AVC software encoding for cameras]) using actionscript 3 in AIR application, I think, it could not be by default as there are no updates available for flash builder 4.5. So, how can we pick the encoding option. Any new API or methodology for this?
Any one any idea??

H.264/AVC software encoding is not turn on by default. You need to assign the NetStream.videoStreamSettings property an H264VideoStreamSettings object. Here's a very simple example;
package
          import flash.display.Sprite;
          import flash.events.NetStatusEvent;
          import flash.media.Camera;
          import flash.media.H264VideoStreamSettings;
          import flash.net.NetConnection;
          import flash.net.NetStream;
          public class TestAVC extends Sprite
                    private var _nc:NetConnection;
                    private var _ns:NetStream;
                    private var _camera:Camera;
                    private var _h264Settings:H264VideoStreamSettings;
                    public function TestAVC()
                              _h264Settings = new H264VideoStreamSettings();
                              _nc = new NetConnection();
                              _nc.client = this;
                              _nc.addEventListener(NetStatusEvent.NET_STATUS, onNetStatus);
                              _nc.connect("some fms server");
                              _camera = Camera.getCamera();
                    private function onNetStatus(e:NetStatusEvent):void
                              switch (e.info.code) {
case "NetConnection.Connect.Success":
                                                  _ns = new NetStream(_nc);
                                                  _ns.addEventListener(NetStatusEvent.NET_STATUS, onNetStatus);
                                                  _ns.client = this;
                                                  _ns.attachCamera(_camera);
                                                  _ns.videoStreamSettings = _h264Settings;
                                                  _ns.publish("testAVC");
                                                  break;
                    public function onBWDone():void {}
                    public function onMetaData(o:Object):void {}

Please clarify availability of H 264 encoding in AIR for iOS/Android

Hello,
I've written an app to send a live camera stream via RTMP in H 264/Nellymoser from mobile devices. The app works fine on AIR when tested on my Win7 desktop, but when I publish to AIR 3.2 for Android or AIR for iOS, it seems that the H264VideoStreamSettings are simply ignored and the video ends up in Sorenson. Is H264 supported for encoding/publishing on AIR for mobile devices? If not, is this planned for the future?
Thanks!

Unfortunately, the release notes say H.264 encoding from AIR is for the desktop version only:
http://helpx.adobe.com/x-productkb/multi/release-notes-flash-player-11.html
H.264/AVC Software Encoding for Cameras (desktop) — Stream high-quality video from your computer's camera with higher compression efficiency and industry stanard support, enabling both immersive real-time communications such as video chat/conferencing and live video broadcasts.

New H.264/AVC encoding for cameras

Hi All,
Please let me know, how can we activate H.264/AVC video encoding (new feature in Flash player 11 [H.264/AVC software encoding for cameras]) using actionscript 3 in AIR application, I think, it could not be by default as there are no updates available for flash builder 4.5. So, how can we pick the encoding option. Any new API or methodology for this?
In short, how to publish live stream to FMS using H.264 encoding with actionscript 3. [not with FMLE]
Any one any idea??

Hi All,
Please let me know, how can we activate H.264/AVC video encoding (new feature in Flash player 11 [H.264/AVC software encoding for cameras]) using actionscript 3 in AIR application, I think, it could not be by default as there are no updates available for flash builder 4.5. So, how can we pick the encoding option. Any new API or methodology for this?
In short, how to publish live stream to FMS using H.264 encoding with actionscript 3. [not with FMLE]
Any one any idea??

For h.264 encoding, what size does the project need to be to avoid black bars on the top and bottom.

For h.264 encoding, what size does the project need to be to avoid black bars on the top and bottom. I am exporting the mp4 to Brightcove.

Hi there,
Which version of Adobe Captivate (If it is Adobe Captivate) is it and which Operating System is it?
Thanks.

Support for NVidia GPU hardware H.264 encoder (NVENC)?

The latest NVidia GPU architecture, Kepler, now has a dedicated hardware H264 acceleration block, NVENC.
It is similar in function/purpose to "Intel's Quicksync" (except that Quicksync works with more codecs: MPEG-2, VC-1, and H264. NVENC only supports H264 encoding.) The company claims the hardware-block can encode 1080p video much faster than the host-CPU alone (probably at the loss of some image quality.) This feature is supported on desktop NVidia GPUs with the model GT640, GTX6xx. And in laptop NVidia GPUs GT640M, GT650M, GT680M (and a few others.)
Does Premiere Pro CS6 take advantage of NVENC? If not, are there any third-party plugins that add NVENC-support to CS6?
If not, I'd like to try writing a plugin that uses NVENC, though that'd definitely be an ambituous undertaking!

I have finished a 'proof-of-concept' NVENC Exporter plugin for CS6. This took much longer than I thought it would (mostly due to my inexperience in interacting with Adobe's 'suite' API.) And the beta-plugin is very rough around the edges (no audio or muxing support), and needs some further speed-optimizations, but works well enough for me to start basic testing and behavior characterization.
The following comments are based on my proof-of-concept NVENC-exporter plugin, run on a Geforce GTX650 1GB. The plugin is compiled from the NVidia NVENC Public Beta SDK 2.0 (Dec 2012) and Geforce 314.07 drivers (Feb 2013). The programmer-API to access NVENC is protected by a license-key. The SDK comes with a free trial-key, but doesn't indicate how it compares to a (purchased) retail-key (i.e. does it perform the same but with restricted features/functionality, or does a retail-key offer higher quality encodes?)
First off, how is the video image-quality (compared to the MainConcept H264 that Adobe bundles with CS6)? Based on naked-eye comparisons, NVENC is anywhere from slightly to somewhat worse. As such, since the quality delta was easily discernable at all bitrates, I didn't find it necessary to take objective psnr measurements.
(1) At "low bitrates" (eg. 6mbps or less at 1920x1080 24fps), NVENC is noticeably worse than Mainconcept. The fixed GOP-pattern (group-of-picture) really kills the output-video at scene-transitions, because the encoder doesn't make intelligent decisions about where to place reference-frames.
(2) At "high bitrates" (eg. ~25mbps for 1920x1080 24fps), NVENC is slightly worse than Mainconcept, though now the two are almost neck-to-neck. NVENC seems to have problems tracking very subtle color transitions. For example, on animated/computer-generated scenery (like a Disney cartoon), NVENC had shows a tendency to introduce blocking artificats into sky gradients and other tonal-gradients. Mainconcept was much better in this regard.
Next, what about speed? Speedwise, NVENC easily wins (as expected.)
(3a) For 1080p video, NVENC consistently finished straight "media-export" jobs in Adobe Media Encoder (i.e. straight "in to out" without any adjustments/changes to the source video) roughly 3x faster than the Mainconcept H264-Bluray codec. For example, NVENC needed 30 seconds to re-encoded a 120second Bluray clip. Mainconcept usually took 90 seconds. (Both encodes were single-pass VBR; run as video-only, no audio, no muxing.)
(3b) for 3840x2160 video, NVENC's speed-advantage shrinks to roughly 2x. (This is likely due to a very slow hostmem-hostmem frame-copy operation inside my plugin.)
(4) NVENC CPU-usage hovers between 30-40% during the Adobe Media Encoder session. Mainconcept always used near 90-100% CPU. (My machine is an Intel i5-3570K 4-core CPU.) If someone were comparing NVENC/Mainconcept on a 2-core laptop, the speed-difference would be closer to 6x. Even so, NVENC falls behind Intel's "QuickSync" technology (unfortunately, Intel doesn't offer a Quicksync exporter-plugin for CS6.)
In summary, in its current state NVENC isn't good enough to replace MainConcept in the content mastering and final encode process. But many users may find it useful as a 'quick preview tool'; to generate fast encodes for a bunch of different edit/cut tests (with the intention of throwing most of them away.)

FLV supporting but .mp4 (H.264 encoded) video not supporting in mobile browser?

Hi
I want to know one things, is there any other settings required to publish the swf file for playing mp4 file in mobile browser also. I am able to play ".FLV" in mobile browser but not able to play ".MP4" (H.264 encoded) in my mobile browser.
MP4 file required Flash Player 10 to play video I know this,I can watch video from youtube.com in mobile bowser also.
Please look at the following url which is not opening in Mobile browser but can open in computer broswer.
http://karzzzz.bigflix.com/m/
I want the above url to be play in both computer and mobile browser also as it calling .mp4 file from Flash Media Server.
Thanks
Sunil Kumar Sah

Are you using Flash Lite Plug-in or Flash Player Plug-in on your mobile browser. I have a feeling that you are using Flash Lite Plug-in and flash lite plug-in (latest is 4.0 i suppose) does not support H264 encoded files.
MP4 file which you are playing from youtube might not be H264 encoded , it might be On2 VP6 which is supported in MP4 container.

Playing video encode for a PSP on iPhone

Hello.
When the iPhone is launched in the UK can anybody tell me if i can use video that i have encoded for my PSP on it? The screen sizes are quite close and as i have gigs of stuff i have encoded i really don't want to have to do it all again.
Kind Regards
Alanstubbyfingers

It will have to be recoded using the h.264.

Very Slow H.264 Encoding in FCP 10.1.2 and Compressor 4.1 on nMP

I have a fully maxed out 12-core nMP and editing with this machine in FCP 10.1.1 has been a delight. I recently completed a 4K project from footage shot with the Sony AX-100 and then output the project from FCP X using File>Share>Master File to ProRes 422. This operation occurred in about the same length of time as the length of the project (18.5 min.). I then brought this 75 GB ProRes .mov file into Compressor 4.1, and set up Compressor to encode to an H.264 file at 70 Mb/sec. This encode to h.264 is only 1/4 complete at 48 min. and it appears that it will take Compressor about 4 hours to encode this 18 min. project to h.264. Furthermore, I noticed that with the share to a master prores file FCP X was using 50-60% of my total CPU resources while the encode to h.264 in Compressor is using barely 16% of the total CPU. Thus it appears to me that while FCP 10.1.1 is optimized for the nMP, certainly Compressor 4.1, at least for h.264 encoding, is not.
My question is basically what am I missing? Is there a better workflow than using Compressor 4.1 for high bit rate h. 264 encoding of 4K? If so, what is the best way to use my nMP to get a high bit rate h.264 4K file for sending to YouTube and other online streaming?
Thanks for sharing any thoughts on this you may have.
Tom

Russ,
Thanks for responding.
I am encoding only a single project from FCP X in Compressor 4.1 and using only a single instance of Compressor. I don't really see that using multiple instances of Compresor with a single job would be helpful, but perhaps I don't understand something.
The project has now been encoding for 2.5 hr and is slightly less than half complete. The CPU usage is still at 16-17%. Overall this seems like a ridiculously slow encode to h.264 from a ProRes 422 file in Compressor 4.1.
Here are some thoughts on alternatives that I may try. (1) Take the Pro Res 422 file into Adobe's Media Encoder CC and encode it to high bit rate 4K h.264. (2) Take the Pro Res 422 file into Handbrake and encode to high bitrate 4K h.264. Handbrake does seem to make far more use of the nMP's CPU's than Compressor 4.1. Don't know about Media Encoder since I have not tried any h.264 encoding in Media Encoder.
The irony is that my nMP will play then entire 18.5 minute 4K project from the timeline with virtually no dropped frames, but rendering it to h.264 at 4K and high bit rate seems to take forever.
If you have any other thoughts, I would love to hear them. Thanks so much for responding, and I would love to hear from any FCP X experts who are encoding 4K to h.264.
Tom

H.264 encoding issues with Premiere Pro CC 2014

After updating to Premiere Pro CC 2014 yesterday, I see encoding artifacts on my H.264 exports.
Same source video imported into CC v2014 and v7, and exported using the YouTube 1080p 29.97 fps settings. The artifacts manifests itself as softness/blurriness in parts of the image every few seconds, especially notice the area with a red circle below.
Here are the source file (GoPro HERO3 Black Edition), the v2014 render and the v7 render.
Original: https://drive.google.com/file/d/0B2rJe0xgMTxFYXJiMjZpZ0stUzQ/edit?usp=sharing
CC v2014 render: https://drive.google.com/file/d/0B2rJe0xgMTxFQ1B0Z09GS3I0a1E/edit?usp=sharing
CC v7 render: Premiere Pro CC.mp4 - Google Drive
[Version numbers corrected.]
Message was edited by: Jim Simon

Mark Mapes wrote:
This is a known issue introduced in CC2014.0. Some h.264 encodes have blurriness or noise periodically in some areas of the frame. The problem is most pronounced in regions of the frame with very little detail, like grass or pavement--or the T-shirt in the sample frame. We are working on a fix. Before you ask when the patch will be forthcoming, I'm not authorized to even hint at the timeframe.
Unfortunately, the only real workaround is to export to a format other than h.264. If that's not an option for you, then your best bet is probably to keep working in CC7.2.2 until the patch is released.
Sorry, but thats not completely true and by far not the correct answer:
The problems with random artifacts occurred with the introduction of a new version of H264 in CS6 but there you still had the option to export with the previous H264 Version via Media Encoder.
Since the previous H264 version is not available in CC, using CC7.2.2 is not a solution either.
BTW
Updating to CC and using the new Mac Pros with Mavericks is currently a total mess - no open cl rendering, random crashes, no usable h264 ... thanks adobe!!
... but we can track masks in premiere now ... wow!

Issue with Adobe Encore CS5.1 and Matrox MAX H.264 encoding on Windows

Here's some information on an issue that we've identified with Matrox products and Encore CS5.1:
"Issue with Adobe Encore CS5.1 and Matrox MAX H.264 encoding on Windows"

Still flickering on Encore even when rendered in MPEG-2 DVD in Pemiere Pro CS5.5. Looks perfect in Premiere Pro.
Any other ideas?
EDIT: Was looking for Google for people with similar problems to me and I came across this http://forums.adobe.com/message/3959757?tstart=0
I am currently re-rendering the video in PAL DV Widescreen MPEG-2 DVD and using maximum render quality.

Encoding for the iPad

I have a video that is 900x350 that was created in Keynote and exported as an H264, put it into a website and it looks and works great on everything except an iPhone/iPad.
So I tried using the iPad setting in Compressor to encode but it resizes it and it looks bad.
Is there a way to encode this "odd sized video" in Compressor so that it doesn't scale it, looks good and plays on the iPad?

Compressor's iPad preset is going to make it an HD frame size. You need to make the Keynote at least HD frame size to start with. It's being blown up to a larger size, which always pixelates and degrades image quality. Try making the Keynote 1920x1080 (I use 1080x720, DVCPRO-HD export), then export it from Keynote as either ProRes 422 or as DVCPRO-HD, either will work. Take that to Compressor and encode for iPad preset. Don't create an H.264, then try to make an iPad version from that. You're double compressing, and getting bad generation loss.

Audio drifts out of sync encoding for DVD

I am using Compressor 3.0.5.
I have a DVCPRO HD file I'm trying to encode for a DVD.
Even if I use the default settings in "DVD: Best Quality 120 minutes," the audio and video are completely off by the end by several frames.
The source file was generated from FCP6.0.6, and that file doesn't have any drift issues. I have even successfully used Compressor to encode an H.264 file with no drift using the exact same file.
Why then are the m2v and the ac3 files so off then? They are even different lengths by several frames.
I've tried re-encoding the audio separately at 48K 24bit, (same as FCP settings) and that generated an ac3 that was 32 frames longer than the video, which was exported with the exact same in and out point.
I've even tried breaking it up into 5 separate reels to encode each one individually and then join them in DVDSP, but then each of the 5 separate reels are each off as well, anywhere between 5 to 8 frames by the end.
I spoke to Apple tech support, and they don't know why this is happening. Yet I see many people who have this experience and I can't find the solution. Please help!
I read one post that mentioned it might be using a cluster and multiple cores, so I'll try using a single next, but if anyone has a solution please let me know.
Thank you!

I've had the same issue. It seems to only occur when outputting a 23.98 sequence to Compressor using the cluster.
Another related question: Do the sync issues occur whether you use a reference Quicktime or self-contained?

H.264 Encoding for TV

Similar Messages

Maybe you are looking for