H.264 output

I have another PE11 question for folks.
I work with MPEG clips from digitized VHS 4:3 videotapes and edit them together to be played on both Youtube and for a live audience via digital projector. I'm trying to FTP a file to a contact who wants the edited video in H.264 MP4 format. The problem I'm having seems to be that none of my efforts are as clear as the edited MPEG2 version of the file. For expediency, I've sent him an MPG before and he converted it down with some professional tool, but I'm sure PE11 can save us some time if I can get the correct settings without loss of quality.and create a smaller file.
What he uses is:
NTSC DV H.264 3MB/s
width 720, height 480, frame rate 29.97 field order: lower first, aspect D1/DV NTSC (0.9091)
Profile: Main (or High as an alternative)
Level: 3.1 (or higher)
Bit Rate Settings: VBR 2 Pass, target bit rate 3, max bitrate 6 Audio format: AAC, 48KHz, Stereo, High Quality, 192Kbps
Multiplexer: mp4 standard
So I've attempted this several ways using either AVCHD or Quicktime and altered the settngs to reproduce that. Yet, they still look less crisp.- especially my titles. Not sure if I should be using Standard DV or some 720P or higher format (and what frame rate, etc.).
Any suggestions?

The Buddycat
Clarification timeout...
Have you said that your associate can take one of your .mpg files and turn it into a .mp4 file of the quality that you want with what you are calling professional tool and settings of
NTSC DV H.264 3MB/s
width 720, height 480, frame rate 29.97 field order: lower first, aspect D1/DV NTSC (0.9091)
Profile: Main (or High as an alternative)
Level: 3.1 (or higher)
Bit Rate Settings: VBR 2 Pass, target bit rate 3, max bitrate 6 Audio format: AAC, 48KHz, Stereo, High Quality, 192Kbps
Multiplexer: mp4 standard
All those settings are attainable via the Publish+Share/Computer/AVCHD/ with presets = MP4 - NTSC DV Standard.
At the top of your description, you typed a bitrate of 3 MB/s. That is 3 megabytes per second which equates into 24 megabits per second.
In the bitrate that you cite further down in the description, you write ...target bitrate 3, max bitrate 6.... but what units... megabytes or megabits? I am wondering if there is some confusion here as to the bitrate units. Reason for thinking that...
a. the default target bitrate just happens to be 3, but 3 Mbps (megabits per second) and the default maximum bitrate just happens to be 6 Mbps (megabits per secons). If we are talking megabytes instead of megabits, that translates into 0.375 megabits and 0.75 megabits respectively.
b. yet at the onset you say that your associate used 3 MB/s which reads out to me as 3 megabytes per second (24 megabits per second).
The units given in Premiere Elements export here are in Mbps which represents Mbps megabits per second. When the Profile = High and Level = 3.2, both the target and maximum bitrate have a range of from 0.19 Mbps to 25 Mbps.
Whatever the case, the bitrate setting may be a major factor in what you are able to attain. But, the key answers that we need at this time include:
a. Did your associate take one of your .mpg and turn it into a sharp acceptable .mp4 file for you?
b. This morning did bitrate increase get you to what your associate had achieved with your file?
Taking your Target and Maximum bitrates to the max (24 Mbps) here was just a rough way to gauge the impact of this factor. The level of the bitrate settings and the relative setting between Target and Maximum was to be evaluated once we knew if bitrate was a key player in this task.
Looking forward to your results.
Thanks.
ATR

Similar Messages

Variable Frame Rate on H.264 output

I am using AE CS6 (cloud version). I am trying to render compositions to 1080p mp4. Each time the comp appears to render fine. But bringing it into my NLE crashes my NLE. I brought the media into MediaInfo (app from SourceForge that shows everything about a media clip). It says that the Frame Rate is VARIABLE Min: 60fps; Max 60.6 fps. The composition was 80 fps, and I told the renderer to keep it at 80. MediaInfo also said the duration was over 6 seconds. The composition was a little over 4 seconds. So the overall speed of the comp was incorrect. I've been in the video business for about 10 years. I understand frame rates, etc. Never heard of VARIABLE frame rates until this.
I was able to launder the media file through a freeware media format converter, and got it back into constant frame rate so I could proceed in the NLE with the project. But the time was still 6 seconds. So I had to speed up the clip in the NLE to get it back correct.
Since moving to CS6 from CS4, I decided to start using the H.264 output module. So I've just started encountering this variable frame rate problem.
So my questions... What is variable frame rate, how did I 'request' it, why is even the variable frame rate no where near the comp frame rate, and what do I do to simply get an mp4 with the 80fps that I want?
This is very reproducible for me. My comps are usually either HDTV 1920x1080 or HDV 1440x1080.
Add to Render Queue
Select DV Settings, change field order to none
Select H.264 output module
Render
Can someone explain what's going on?
Thanks.
Jerry

Where did you get that footage and what format was it originally shot in? Was it shot in slow motion or did you change the frame rate in AE? Why would you need 80fps footage unless you're going to slow it down to a normal frame rate?
Also, h.264 is not only a very lossy format, it's also a bad intermediate format. So if you're planning on editting that footage later on in an NLE, I'd suggest rendering it to something else. Premiere should work fine with h.264, but not FCP, although I think they fixed it in FCPX, but you didn't say what NLE you're using.
Second of all, the H.264 encoder is much better in Adobe Media Encoder. Check this post by Andrew Yoole:
3.Andrew Yoole,
Jun 8, 2012 6:34 PM in reply to pkaracas
Report
As the other guys have said, don't use AE to render using temporal codecs. Temporal codecs like H264 rely on storing partial frames based on earlier information. AE renders and encodes one frame at a time, so most of the efficiency of a codec like H264 is lost. The result is that you get much lower overall quality from an AE h.264 render than if you were to encode it externally.
Adobe Media Encoder or Quicktime 7 will encode great quality H.264 files.
Was this helpful? Yes No
As I said I'm not sure why you would need to take an 80fps piece of footage back into an NLE, but if you're trying to make that footage play back in slow motion, you're going to have to re-interpret the frame rate of the footage in After Effects to play back at standard rate. And, if you're going to use the AE Render Queue to output something for more editing, I would suggest using best settings and outputting to a production codec such as a ProRes, Animation, Uncompressed 10bit, Uncompressed 8bit or Black Magic.
Also I've never used that media info app before, but I know that when you open up quicktime and hit command I on the mac to view the inspector, the playing fps jumps around. I think this happens because the player doesn't necessarily play back the correct frame rate at all times.
This Adobe Captivate blog talks about variable frame rates in F4V files. Maybe it might help explain things.
http://blogs.adobe.com/captivate/2010/11/f4v-or-f4v-fixed-frame-rate-what-should-i-go-with .html

Anyone done a comparison between compressor & Squeeze 5 for h.264 output?

Anyone done a comparison between compressor & Squeeze 5 for h.264 output?

I'm not that concerned about speed, primarily interested in quality.
Intended delivery would be over the web, but also on an HDTV flat screen in a waiting room at best resolution (would H.264 be the best choice for that use?).
Source would be 1920 x 1080 24p ProRes 422 (recorded directly from HDMI using a humble Canon HV20 and an Intensity card).
As to the size, that's becoming less of an issue with bandwidth such as it is. 20-30% larger wouldn't make a difference to me.

Missing H.264 Output Module in Render Queue

I've reinstalled AECS4 and still have no H.264 in the output format dropbox. I am missing quite a few compared to CS3. Any ideas why?

What operating system? What other Adobe CS4 applications are on your system? The modules not showing up may also be caused by the licensing system thinking that some pieces are trial versions. In such cases, removing and re-installing the other apps may also be required, especially Encore and Premiere who share these components.
Mylenium

H.264 Output Fails in After Effects and AME

I'm having the same problem - H.264 export crashes around the 1:03 mark every time. DNxHD is fine.
Dragging comps to Adobe Media Encoder and trying to render from there doesn't work either.
My CS6 install [last week] is on a brand new Dell Precision T7600 dual eight core machine with Windows 7.
It's ridiculous to say that we shouldn't render H.264 out of After Effects. Sometimes I render 50+ TV ads at at time from composition templates for delivery to a multitude of media outlets - each with slightly different specs.
Even if AME was a workaround, dragging all these comps over would be a crippling waste of time.
This is an Adobe problem and we've all wasted too much time troubleshooting and talking about it. PLEASE FIX.
Thank you.

What version of After Effects? CS6 with all current updates.
Have you installed the recent updates? Yes.
What operating system? Windows 7 Professional
What kind(s) of source footage? The test composition contains only text created in After Effects. Other test comps have included MTS, MOV, PSD, MP3, WAV, AIF files.
If you are getting error message(s), what is the full text of the error message(s)? After Effects error: Rendering error while writing to file "Q:\...\Test.mov". An output module failed. The file may be damaged or corrupted. (-1610153464)
What were you doing when the problem occurred? Sitting at my workstation with my fingers crossed looking hopelessly at the computer monitors.
Has this ever worked before? Yes. Worked flawlessly in all previous CS releases.
What other software are you running? Other software installed but not running at time of crash: Avid Media Composer 6.5.1, Sorenson Squeeze 8.1, Quicktime 7.5.5 [also didn't work on v7.6.9].
Do you have any third-party effects or codecs installed? Whatever Avid and Sorenson install.
Tell us about your computer hardware.: Dell T7600, Dual Eight Core XEON (E5-2665, 2.4GHz, 20M, 8 GT/s,Turbo+), 32GB, DDR3 RDIMM Memory, 1600MHz, ECC (8 x 4GB DIMMs), 2GB NVIDIA® Quadro® 4000, DUAL MON, 2DP & 1DVI, [1] 1TB system drive, [1] 12TB G-SPEED eS PRO.
Do you have any third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU)? No.
Are you using OpenGL features in After Effects? Yes.
Does the problem only happen with your final output, RAM preview, or both? RAM previews work fine. Crashes occur while rendering to MOV w/H264 in both AE and AME.
Are you using Render Multiple Frames Simultaneously multiprocessing? Yes. But have tried disabling also.
What is the exact sequence of steps that you are taking? Open AE, create new composition, add some text layers, add some animated effects to the text layers, add comp to Render Queue or AME, select MOV with H264 codec.
Thanks in advance Ben.

Question about h.264 output in PE7

I'm a bit confused about h.264, in article
http://gizmodo.com/5093670/giz-explains-every-video-format-you-need-to-know
it states:
"MPEG-4 Part 10, the other part, was actually co-devopled by MPEG and the
ITU-T, so it's also known-in fact, more commonly known-as H.264. It's more
efficient than MPEG-2 and MPEG-4 Part 2, delivering the same quality video
in as little as half the space"
That sounded good and I thought perhaps I should switch from DIVX as my
format for small-footprint avi's residing on the computer to H.264
However when i go to output (share) a file in PE7, selecting MPEG only
provides 4 choices for H.264 and they are all hi-def (1440x1080i) - there is
no option for standard def or smaller. Is this another situation where I
must do DV in PE7 and then use an external converter to convert to the final
format?
Mark

Dude, you are worth every penny Adobe is paying you....lol Mark <[email protected]> wrote in message news:[email protected].. > Nope. You can output to H.264 in any size, quality and frame rate you > want, Mark. It's one of the dozens of "hidden" output formats I wrote > about in my recent Steve's Tips article for <a href=http://www.muvipix.com>. > > To get to them, instead of using Share, just go to File/Export/Movie (with > the timeline selected).

Media Encoder 5.5 - h.264 output sync off by 1 frame

Hello,
I'm having a problem with AME 5.5.0.212 - when trying to ouput an h.264 mp4 file, the audio is out of sync by 1 frame.
Seems to manifest with various source materials.
Frequency is the same, source and target: 48khz, stereo.
I'm on a Mac Pro, OS 10.6.8.
Strangely, it doesn't manifest when I import the videos to Premiere... but when I bring them into Final Cut, the first frame of the h.264 file is aquamarine and the video duration shows 1 frame less than the source file.
So it sounds like Quicktime isn't processing the output file correctly.
But this is a problem, since most of my clients use Quicktime Player for playback, and I have no idea how sites like Vimeo and Youtube will process the file.
Any suggestions?
Thanks,
Taylor

I agree, I use VLC often, and quite dislike Quicktime Player.
But while I can control which program I use, I can't choose what my clients use, so that's not really a solution.
Maybe this is a Quicktime Player issue more than an AME issue, but it would sure be nice to know that the files coming out of AME are going to play well on any player. Otherwise, for h.264, AME is kinda useless to me.
Anybody else have this issue?
Any settings or workarounds?
t

H.264 output settings in CC 2014 v 13

In the Preferences menu, under Output, there is no longer a check box for *Show Deprecated Formats in Output Module Settings*, therefore, leaving me unable to output as an H.264 mp4. Wondering if there is anyway I can fix it or even downgrade back to CC v12.

When you install CC 2014, it doesn't overwrite anything. CC (version 12) should still be on your computer.
There have been several threads about this. Adobe removed the option to encode directly into H.264 from After Effects (thus the term "deprecated" in the last version). The stated reason for the removal is that After Effects does not do a good job at encoding h.264 (due to the inherent nature of how the program works). Thus, the After Effects team removed it rather than continually spending development time on it when a much better solution is available.
The better solution is one that I've always used. I never liked how AE encoded h.264, so I never used it. I always render an intermediate file out of AE and then use the Adobe Media Encoder to create the h.264. I had several reasons for doing this. One reason is that AE can't do multipass encoding and that's something that can really help the quality of video in lower bitrates. Another reason is that I often need to try a few different iterations of compression to make sure I'm getting the highest possible quality at the lowest bitrate possible. As you're, no doubt, aware, it's a delicate balance between data rate and quality. Rendering a lossless intermediate from After Effects lets you try as many variations of compression you want without having to rerender your AE comp each time. If you've got 3d, motion blur, lots of particles, or anything that takes a while to render, this will make a lot of sense.
However, if you already know what settings you like, another great solution is to send your Adobe composition directly to the Adobe Media Encoder via Dynamic Link. This lets the AME begin rendering your AE comp in the background while you continue on to your next AE project and you are still taking advantage of multi-pass encoding if you wish.
So, there you go: two superior workflows even if Adobe hadn't removed the option.

QuickTime Broadcaster, from MPEG-2 to H.264 stream

Can QT Broadcaster connect to a MPEG-2-stream, convert it to H.264 MPEG-4 and broadcast the new stream on the fly?

I could be missing something, but to the best of my knowledge, no, QT Broadcaster cannot. It's not a transcoder; it's intended to capture live audio and video from Firewire, USB or an analog input.
There is at least one real-time MPEG-2 to H.264 transcoder available, from Media Excel, but it's not cheap; ca. $13,500 US. If there's anything less expensive that can convert MPEG-2 to H.264 in real time, I haven't been able to find it.
Your only other option, I think, would be to capture a video output stream from your MPEG-2 content to an analog or DV output, then use QT Broadcaster or another real-time compression tool to handle the H.264 output.

How to speed up render to h.264 in CS6? Adobe QT32 Server.exe causes long delay

(Before you say "Don't use AE to render to h.264; use AME!" – I'd love to, but AME isn't controllable from the command line / batch files the way aerender.exe is)
When I try to render a brain dead simple composition (30 seconds, black background with the word "DUMMY" centered), aerender takes nearly four minutes to complete. This is a Windows Server 2012 box with 32 CPUs (16 cores+16 HT), about ~60GB of memory and I believe it's on 10Gb ethernet. Turning multi-processing off doesn't have effect on the pause.
If I view the task in task viewer, NO CPU is being used and Adobe QT32 Server.exe is running. Analyzing the wait chain for aerender.exe says that a thread is waiting for network i/o to complete (I assume this is Adobe QT32 Server.exe, which uses TCP to talk to Quicktime). After about three minutes, the render continues (and goes blazingly quick, as expected).
WTF?
How can I get around this long, useless pause? Is there an alternative h.264 output module that doesn't use Quicktime?
Thanks in advance!

The flaw is here:
This is a Windows Server 2012 box
Adobe desktop programs are generally not officially supported on server operating systems. Whatever issues you have are probably due to things like local users vs. network users, disk quota, specific group policies or plain and simple another process occupying or blocking the same port that the QT server is using. In any case, this is nothing we can figure out for you. You have to sit down and work your way through the server's administration tools, turn off stuff, change user permissions. Check the event logs for conflicting processes or use tools like Sysinternals' Process Monitor or Wireshark to track down port collisions and otehr problems.
Mylenium

Encoding H.264

Can FCP or Compressor encode h.264 with 5.1 AAC? I have exported through Quicktime but the surround channels cannot be mapped flexibly and the overall bitrate cannot be set. Also, the movie cannot be resized so the original has to be in the final format.

All of this can be done easily woth Compressor, yes. Read the manual's section on H.264 output, and on Dolby Surround Sound channels.

Suiteable output for the web

Hi everyone. I have a series of videos that I will be edit and combine into 4 separate videos. As far as I know, we will be hosting these ourselves, and people with a variety of connection speeds will be accessing the videos. I am going to tell you the specs of the original video I am using as a test piece and then asks some questions.
Original Video:
720 x 480 (.9091)
29.97 fps
48000 Hz Compressed Stereo
6 Minutes and 45 Seconds long
From a Canon FS200 (non-HD Camera)
For posting to the web, where should I focus my trimming back -- frame rate or bitrate? I did a test video with a framerate of 15 fps and a bit rate of 1 Mbps and a max of 1.5 Mbps. I left the audio at 192 Kbps, and it sounded good. The video looked good too. File size was 59 MB.
I made another version of the same video at 30 fps, but dragged the bitrate down to 233 Kbps and a max of 320 Kbps...and the video looked terrible if there was any movement. I took the audio down to 56 kbps, and the audio still sounded good. The file size was around 16 MB.
Additional Questions
1. Does anyone have any other suggestions for reducing the file size to keep the quality? I have been reading on some other forums trying to understand the relationship between fps and bitrate.
2. Should I reduce the resolution? I kept the video in its native resolution of 720 x 480.
3. Do the file sizes I mentioned above sound appropriate for the specs on the video?
4. Should I post 2 separate videos: a low-bandwidth and a high-bandwidth; maybe even offer some info for people to download it for offline viewing.
5. What considerations should I make for hosting? At what point is a file too big? If someone is watching over an hour of video over a DSL connection, they are going to be there for a while, and the video should hopefully fully download in the time it takes to complete, so as long as their downstream speed can keep up with (or stay ahead of) the video playback, does file size really matter a great deal...beyond just making sure we don't go over bandwidth limits with our host, ?
I am using Premiere Pro CS4. We aren't adding any animations, and the editing is real basic -- just chopping out the parts we don't want; no image stabilization, maybe some color correction, and basic transitions. Not sure if any of that matters. Additionally, I end up using the Adobe Media Encoder to generate the final video. I am using the H.264 output, which gives an MP4 file.
Thanks for any help you can offer.
Ian

wow.. that is a lot of stuff to consider and deal with...
theres a thread with some info about delivery from your own server using html 5 here...
html5 video delivery to various browsers and devices info
http://forums.adobe.com/thread/933013?tstart=0
your server bandwidth etc does matter and yes, I would consider making video less than 720x480 ...
look at this test video "page" i made on my own " server" ( i use inmotionhosting.com )
http://rodneybauer.com/whiteboard2.htm
the code in web page determines what is being 'used' by client and delivers what it needs ...and my test page doesnt do that... mine is just a simple test for desktop browsers using flash ( flv ) and a little viewer thing.
you have a lot of stuff to consider re: who you want to view your stuff, on what size " screens" ( little iphones etc? ) and then once you figure THAT out.. how to deliver best product ( video,sound) for streaming..
youre gonna need someone who knows code to do the web part as well as knowing about the codecs and so on.. lots of work etc ahead of you.
good luck !

Package H.264 as ISMV or ISML (via MFCreateFMPEG4MediaSink?)

Hi all,
I have an application that outputs content (dynamically generated with Direct3D) to mp4 via Media Foundation. This code has been working well, and now I'm looking for a way to stream that content with as little latency as possible to a Smooth Streaming publish
point (Azure Media Services in this case). I've successfully created video-only fragmented MP4 files with MFCreateFMPEG4MediaSink and IMFSinkWriter, but I can't find a way to create f-MP4 files that are compatible with the Smooth Streaming Protocol.
The files I can currently output have a ftyp indicating a major brand of "mp42" and compatible brands of "mp41" and "isom". For smooth streaming, this needs to be "isml" with compatible brands "piff" and
"iso2". Also, it looks like every frame is a keyframe, whereas Azure expects key frames every 2 seconds. This may be because the encoder is generating a file where MF_MT_MPEG2_PROFILE is set to the H.264 Simple profile-- and I can't get it to produce
anything else. I tried setting the Main profile on the media type I pass to MFCreateFMPEGMediaSink, but it doesn't seem to affect the file output:
hr = mediaTypeOut->SetUINT32(MF_MT_MPEG2_PROFILE, eAVEncH264VProfile_Main);
Again, setting this or any other profile doesn't seem to have any effect on the output.
I believe the actual H.264 output is correct (and of course the fragmented mp4 video files do play back properly), but need to ensure it is packaged properly. Is there any way to do this with Media Foundation?

kryten2002 wrote:
I have quite literally hundreds of files in HD H264 that I want to use as source, and I really don't want to have to transcode the lot of them.I realise FC isn't happy working natively with H264's, but since this appears to be an issue that crops up so often I was hoping somebody out there had found a workaround either via process or via a plugin.It's the one thing that Premiere does so well, but I'm not ready to stop using FC because of that one (annoying) thing.Thanks all.
Looking back over the development of and the popularity of H.264 and comparing that against the history of NLE product releases, I see that FCP is way behind the curve. Who knows why? The current version of Adobe's suite benefits from many years of FCP's history of failing to meet the needs of a certain niche of users. Perhaps the decision to put all development energy into FCPX at the expense of adding advanced codec handling functions to FCP7? It's a bummer for lots of us that FCP7 came up so short and has now been effectively killed.
Only time will tell if people like you and me will switch to acquire functions we need now or adopt the new paradigm and see if things evolve.
bogiesan
bogiesan

H.264 Export Looks Weak

Hi.
The H.264 output has weak colors, but the export with no conversion is right on time. Is this normal?
I'm using FCE4, a Canon HV20, HDV, 24fps, QuickTime Export with H.264 at best quality.
Thx

http://homepage.mac.com/giantklr/h264issue/fce4qt.jpg
You can't see it here, but in the timeline is another sequence. It's the tab called "color correction" in the back. I put two subclips on it: an uncorrected subclip and a corrected subclip. They're butted up against each other.
So, if 24p is not supported, can I get away with shooting at 30 frames per second and then choosing a frame rate of 24 frames per second at the output/compression stage? I really don't see the need of choosing my frame rate until the output/compression stage, myself. I figure that I'm more interested in my EXPOSURE: aperture/shutter speed/color/gain while capturing. If I get that right I can color grade to my satisfaction and then choose the frame rate. Does that make sense?
BTW, thank you SO much for taking the time to help with this. I'm at wit's end and there's no more that I can do on my own. I certainly appreciate it!

Compressor 3 taking far too long to compress H.264

Origianally posted this here:
http://discussions.apple.com/thread.jspa?messageID=7328851&#7328851
But thought I would start a new topic.
Something is very wrong. I sent a 9 minute MPEG-2 file to Compressor to have compressed to H.264. (H.264 compression is what I would gather many of us are using Comp for in the first place).
I know Compressor can do H.264 comp at about 1.43:1 from tests. So a 9 minute clip should take, 6 minutes or so, and with Q Master it should be even faster. Well, Comp reports 8-9 hours. What the heck is going on.
I have taken MPEG Stream Clip and done the same H.264 output and it takes about 6-7 minutes. Something is up with Comp 3.
Now I have turned off Q Master, Reset the Comp 3 BG Processing, Quit Comp and relaunch, maybe reboot, possibly trash all prefs related to Comp.
And still 8-9 hours?
A 9 minute clip should take 6 minutes and as I say, with Q Master, even faster, that is the point of Q Q Master services
Message was edited by: macguitarman

Took me awhile to get Compressor going reliably but now it has been pretty solid.
I am not sure what settings you are using to encode (for instance Frame Controls can add alot of time), but 8-9 hours for 9 Minutes seems rather extreme. Note though that you are using an MPEG-2 (m2v?) file. You may be better off converting to another Codec or better yet go to the source material you are double encoding.
I just set up a Compressor setting on an Octo 2.8 with everything pushed to the Max on Frame Controls and set to resize a 6 Minute HD AIC stream down to H.264 @25% of the size of the original and sent out to "This Computer" and not the Cluster and it took 17 minutes or so. Even with converting from m2v it does seem like it is taking way too long on the machine for you.
I saw you had done some troubleshooting, but do you have any other details? Was his a clean install of the OS and Studio, or were there upgrades along the way? That caused some issues in the past - meaning between upgrades to Leopard and/or installing Studio 2 over Studio 1.

H.264 output

Similar Messages

Maybe you are looking for