Exporting to H264

What is the data rate when setting quality to "best" when exporting to H264 directly for FCP? I get better results from Quicktime than from Squeeze. Max data rate from the pulldown in Squeeze is 1600 kbps. That gives a bit smaller file size and less color than for Quicktime/FCP.

QT H.264 is as good a quality as anyone else's. But you can purchase the MainConcept package (it's pretty expensive), but you won't get any better H.264 from it.

Similar Messages

  • How to do frame-by-frame editing in iMovie 08 and export in H264?

    I wish to edit some videos and then export them in H264 so I can use them on a website.
    I have tried to edit with iMovie 08 but can only edit second-by-second. I want to edit frame-by-frame ie to the millisecond. And it appears that iMovie 08 does not export in H264.
    I have looked at iMovie 11 which has a Precision Editor which would work to edit as I want but for that I would have to upgrade from Leopard to Snow Leopard which I don't want. It would export H264.
    I also have QuickTime Player 7 Pro but that too seems to edit only by the second not by the frame; it does however seem to produce H264
    How can I edit these videos precisely and produce H264? Is there another application which would work better (and doesn't cost a fortune).
    Thanks for any ideas

    iMovie exports in h.264 by default. All the presets are h.264 (except Tiny).
    If you need to adjust the h.264 in some way, then SHARE.EXPORT USING QUICKTIME.
    To edit to the nearest frame, Go to iMovie/Preferences and select Display Time Codes.

  • How to edit videos frame-by-frame and export in H264?

    I wish to edit some videos and then export them in H264 so I can use them on a website.
    I have tried to edit with iMovie 08 but can only edit second-by-second. I want to edit frame-by-frame ie to the millisecond. And it appears that iMovie 08 does not export in H264.
    I have looked at iMovie 11 which has a Precision Editor which would work to edit as I want but for that I would have to upgrade from Leopard to Snow Leopard which I don't want. It would export H264.
    I also have QuickTime Player 7 Pro but that too seems to edit only by the second not by the frame; it does however seem to produce H264
    How can I edit these videos precisely and produce H264? Is there another application which would work better (and doesn't cost a fortune).
    Thanks for any ideas

    I want to edit frame-by-frame ie to the millisecond.
    Am a bit confused by what you say. iMovie and QT 7 Pro are both "frame" level editors. However, some forms of editing are, by their very nature, applied over a range of frames which may be a part of your problem. In addition, since "normal" movies have frames which are spaced apart in the 16 to 42 ms range, your requirement to be able to edit to the nearest millisecond would seem unreasonable and would probably be unsupported for playback purposes without skipping 90+ percent of the frames on most platforms.
    And it appears that iMovie 08 does not export in H264.
    All of the "Share" and/or "Export" options (except Final Cut XML...) either default to H.264 or allow export to H.264 (or X264 if installed) video compression.
    How can I edit these videos precisely and produce H264? Is there another application which would work better (and doesn't cost a fortune).
    Difficult to say since you have not given any indication as to what you mean by "editing" here. You could, for instance, edit normal movie clips in a normal manner and then use an application like the JES Deinterlacer to change the playback time reference to achieve an effective 1 millisecond/frame playback rate you seem to want to target even though your platform cannot play every frame during playback.

  • Why can´t I Export my H264 file as a VMW file in quick time 7. The program only does 30 seconds?.

    Why can´t I Export my H264 file as a VMW file in Quick time 7pro. The program only does 30 seconds of the file?

    Why can´t I Export my H264 file as a VMW file in Quick time 7pro. The program only does 30 seconds of the file?
    The Windows Media codec you are using is running in the "demo" mode. To export full clips you must purchase or upgrade to one of the export capable codec components like those included in the "Studio" or "Studio Pro HD" software package.

  • Exporting ANYTHING (h264) in Q.7 errors...

    Ok, using Quicktime7 Pro for windows. Everytime I open a file in quicktime and go to export to H264 my PC errors.
    Every single time.
    Whatever movie is opened in Q7 can play fine; avi, mpeg, soreson3 vid, anything. But as soon as I go to export, it starts and will get between 10-30% done and then errors.
    I tried using SorensonSqueeze and AfterEffects, but both of those programs also error everytime I try to use the H264 codec. I've also reinstalled Q7 3times now, so yea... I'm at a loss at how to export movies to H264. I can play 'em fine, H264 vids, but not make 'em.
    Any help is appreciated.

    Actually, the AAC is going to be more dependent on your I/O sub-system, than on your CPU. Please give us the details of your I/O, i.e. your HDD's, their size, speed, controller type and how you have the HDD's allocated.
    Also, for AAC, I use Audacity to convert to PCM/WAV 48KHz 16-bit. Even the pro audio-editing program, Audition, does not like AAC files.
    Highly-compressed Audio formats/CODEC's are often highly problematic, and most users find that converting to PCM/WAV is by far, the best way to go. The quality loss will NOT be regained, but the ease of editing will be greatly improved.
    Good luck,
    Hunt

  • How long should it take to export to H264?

    Hello,
    I been asked to convert a VOB file to FLV. I converted the VOB to MKV using Handbrake. I brought the MKV file into FCE, made a few edits and am exporting to an MOV using the H264 format. The plan was to then convert to FLV using Sorensen.
    FCE is telling me the export to H264 is going to take 3 hours. Its a 7 minute video. Can this be right? Is there a better, faster way to do this? I saw that I could export directly to FLV using the Sorensen Quicktime Conversion but that was going to take even longer.
    I'm on a 4 yr old MacBook Pro loaded with memory so I would think I am ok there.
    Thanks for any advice your can offer.

    No offense, but this is simply a terrible workflow for several reasons. First of all, you are at the moment trying to do at least three conversions. Each conversion requires recompression and quality loss. Secondly, FCE does not work with MKV files. Let's try to simplify the workflow to make it faster and get better results.
    1. Use the free [MPEG Streamclip|http://www.squared5.com> in addition to the $20 [MPEG-2 Component|http://www.apple.com/quicktime/mpeg2> to convert your VOB files to DV-NTSC.
    2. Import your DV-NTSC files into FCE and make the edits required in a DV-NSTC sequence.
    3. Export as a lossless Quicktime Movie via +File > Export > Quicktime Movie.+ The resulting file won't take to long to export (especially if you select a reference file instead of a self-contained one) and won't involve recompression.
    4. Take the resulting file to Sorenson or another program and convert to FLV.
    Hope that helped a bit,
    Sasha

  • Jumpy playback from image sequences rendered in Apple Prores and then exported to h264

    I will start by saying I have been using FCP since 1.0 and am in no way new to this software, but this issue has me going crazy.
    First the Specs:
    MacPro 2 x 2.66 Quad cor Intel Xeon
    16 gig Ram
    OS 10.9.2
    FCP 7.0.3 (sorry but I am not a fan of FCP10 at all)
    In other words, a beast of a system that has played back everything I have ever built on it for years until now. So now for the issue: I work with an amazing 3D Max builder and we have created a building animation exported from that program into and image sequence ( we have tried JPG, TGA and PNG still all with the same effect). I open Quicktime 7 Pro, build the image sequence, save as .mov, import into FCP and drop it into my 1080p30 Apple Prores (HQ ... we also tried SQ) timelines. The timeline renders perfectly and I can play the video perfectly through my system out of Firewire 800 to my Motu V4HD device which then converts the signal to HDMI to my 55" LED TV. The video and playback is perfect.... until:
    If I try to play back the same exact time line into an exported video file, the file will play back with random jumpyness in it. I say random since you can play it back 10 times and it will hiccup during playback at different spots in the video. If you review every frame in the file though using Quicktime 10, 7 or VLC viewer, every frame is perfect. So, it must be the data rate right? Wrong. I have exported now to H264 MP4, M4V, MOV , ect, etc at different data rates from 4mb to 40 mb per second. They all have the same randow jumpyness to it. So it must be my computer right? Nope. I have a Macbook pro that is more powerful than this machine and I rebuild the file using the same method (something I have done a thousand times before) and the exported file does the same thing on that machine. I had my friend do it on his machine... same thing. ERRRR....
    We have even tried using After Effects and Premier to the same result. Rendered it straight from Quicktime Pro, same. Rendered it to 720p30, same. Render it to 24fps, same. I had another editor render it using whatever methods he wanted to use... same. Tried Compressor, SAME.  Tried Adobe Media Encoder, SAME......We even, god forbid, used a PC running Premier and built the image sequence and rendered to h264 at 30fps, 5mbs.... @#$@#$ SAME!
    We just remade the 3D Studio Max export into a 60fps animation since I thought that the individual frames we appearing too far apart and thus causing the jumpyness. That was causing the playback of the upclose objects flying across the screen fast to appear jittery, but not the random playback jumps. The 60fps did smooth out the animation greatly during fast flybys, but the playback jumps are still there in all players, QT, VLC, the web, etc.
    I was starting to think this issue is realted to Mavericks, but since the PC did the same thing that is not it either. I have linked a sample of the clip below exported to 720p30, 25mbs... something that is much smaller than the original and should playback smooth very easily on any of my systems.
    FYI: I have now opened numerous projects I have edited over the last few years and noticed that all of them are now jumpy, so this isn't just an image sequence issue. While the other projects don't use image sequences and instead are shot footage edited together, there is still the random jump (far less than the image sequence as you will see) but they are now there... ***? I have cleared preferences in FCP which helps for a short period of time, but once exported I get the same glitch.
    As I said... I am stumped... ANYONE have ideas for me to try?
    Here is a sample file for you all to see and please tell me if anyone does not see the issue after playing it several times in a row.
    www.media3lv.com/switch/NORTH-sample-720p30_25mb-sec.zip
    One last thing to note... my main goal for these videos is YouTube or Vimeo playback via our company website. I have a few other animations online right now using YouTube and the problem is also showing there. At first I thought it was just my videos, but I have looked at numerous YouTube videos now showing 3D animation and alot of them are jumpy.
    www.supernap.com/supernap-building-design.html
    www.supernap.com/supernap-tscif-exchange.html
    These don't show the issue as bad since the camera fly is much slower, but why is this occuring and is it coming from my source, or is this a known youtube issue? I can program this using out own modules, but YouTube and Vimeo allow for multiple resolutions and a checker script which makes it easier to share over all devices at all quality up to 1080p.
    Advice is welcome and appreciated?

    I have tried at actual, full screen, using 1080p30 size from the original compressed to 4mbs (something my system can handle without blinking), 720p30, etc. etc. etc.  Nothing stops the jumps. Even the activity monitor shows only 5%-15% processing being used by QT and/or FCP.
    I plan to pull my old G5 out of the closet, it runs 10.6.8 and is still rock solid for video editing in FCP7.  If it plays smooth on that 8 year old system then I know it's Mavericks. I'll try that tonight. It floors me though why the original 1080p30 will playback perfect via FCP and Motu, but once I turn of external monitoring and just try to play it via the preview monitor it is jumpy as **** and then the exported file does the same thing.  So strange.  I even deleted prefences of FCP and that does help with screen playback initially, but it always gets jumps in it after playing for a while.
    I knew I should not have started using Mavericks and I HATE FCP10.

  • Colors are screwed up after export / import h264/avc

    Assume we have created some raw colors with AE. And exported the file with h264/avc codec (see the picture).
    I understand that exporting with chroma 4:2:0 can change the colors a little. It's ok. We play the file with local video player, RGB values are 1-2% away from original, it's not critical.
    But what I don't understand is - why re-encoding the file to h.264/avc with Adobe Media Encoder as standalone application leaves all the colors 100% correct, but if I will import the file to Premiere or AE, colors are visibly screwed up?
    Then export composition to h264/avc with the same settings as stand alone encoder and the colors are screwed up one more time by 1-2%!
    Am I doing something wrong? How to keep the colors when importing?

    Either the good old H.264 Gamma problem or simple quantization errors which you might probably avoid by working in 16bpc or 32bpc. Also keep in mind that AE can use color management and you may already see those differences when setting the comp viewer proofing to you monitor profile. Generally, though, such color issues are extremely difficult to track down. Things like your graphics hardware's acceleration features, VLCs selected decode method, color profiles and other color tweaks can influence this, both in mere perception of colors as well as actually skewing them. Start by working in higher bit-depths when re-importing files into AE and tippi-toe your way to the aforementioned color management stuff and so on...
    Mylenium

  • Exporting to h264 - color madness

    Hi,
    i am trying to overcome color matching issues and did some tests with Motion 4.0.3 now.
    (On 10.6.4, macPro 8core 2008)
    Basic setup: Have an empty scene with a green background set to RGB (0,93,40).
    *First attempt - direkt import:*
    1. Export directly from motion to h264
    2. reimport the just made movie and make a check with a colorpicker.
    3. In my case the colors are way off, showing a value of RGB(17,19,43)
    *2nd attempt - using share and send to compressor*
    1. use share and send to compressor
    2. in Compressor use the standard Quicktime h264 setting
    3. Result is even worse
    *3rd attempt, only use Compressor*
    1. Export the scene as Prores 422 HQ
    2. Reimport that to motion, make a color check, colors are the same (in my case)
    3. Use the Prores Clip in Compressor, use standard Quicktime h264 setting and export.
    4. reimport the h264 to motion, make a color picker check
    5. Bingo, in my case this is almost the same now with RGB (0,93,41) instead of RGB (0,93,40).
    Question: Why is that? It takes the double time to first write Prores and then use Compressor.
    Is that a gamma issue? I tried to check that by changing the media settings gamma of a reimported testfile, so that i get a almost close result by eye - but the color picker sees the difference.
    Any info is greatly appreciated
    Message was edited by: MarjanP

    H.264 always affects color. Color information is greatly compressed in H.264. I am not surprised that after throwing away tons and tons of info, then attempting to re-constitute it, you see some shifting. H.264 is a web delivery format.
    And it's not "double time" to export first as ProRes - that would be considered the "rendering". Then you compress that. If you try to go out H.264 directly, you're trying to "render" and "compress" at the same time. It's usually faster to do it sequentially. (One reason being that if Compressor is doing best compression, it makes two passes thru the material. If it is not rendered, it must render it twice. If it's already rendered, it's only a file read - much faster).
    Patrick

  • Why does PrP CC export an AVC codec file when I export an H264??

    Hey everyone,
    I'm new to PrPro from FCP7. I'm so used to exporting a .mov file with H.264 compression and I can't believe that I can't do that inside PrPro. I'm sure it must be something simple that I am not seeing. When I export H264 from Media Encoder I end up with an .mp4 file which if I open in QT and look at the specs says that it's an AVC codec and it won't even show me the data rate... It's really annoying and quite frankly looks like a mistake to me, even though the file "looks" good. Can someone please explain to me what I'm missing here??
    I really appreciate any info on this. Thanks in advance!!

    A very common and way-too-easy problem. Formats & codecs & "wrappers" are confusing enough the whole concept HAD to have originally been thought up by some particularly frustrated, ignored, and venal low-level bureaucrat just to get his revenge on the world. Unfortunately for us, he succeeded beyond anything he could have imagined. 
    Neil

  • Why do files exported with H264 randomly slip out of sync.

    I am currently in the middle of exporting 34 individual videos/sequences.
    I am using the H264 codec. Some of them are in sync and some seem to have the audio lagging roughly a frame behind. The videos are of musical instrument demonstrations so there is no margin for error. It seems totally random as to whether they come out of Adobe Media Encoder in sync or out of sync. I have to export each one and then if it's incorrect I have to manually drag the audio a frame forward on the timeline and outout an 'out of sync' timeline in order to get an 'in sync' video! Needless to say, all of the audio is perfectly in sync on the timeline. Plenty of the them are fine and I'm not changing the settings, so it must be some kind of inconsistency with the encoding.
    Why is this always such a problem with Adobe Premiere? Even in the past it's been really difficult to get acceptable quality videos out of the software package.
    If anyone can offer a solution to this it would be greatly appreciated!

    That is the realty of the situation.
    Just like a cinematographer, who works so hard making the image look just the way he wants, has no guarantee that the end viewer will have a properly calibrated display and see the film the way it was intended to be seen.
    All you can do is your job correctly, and offer suggestions to those whose systems don't work right.  Which in this case means using a decent media player.

  • AE CS5 (v10.0.1.19) export as .h264 Streaming Problem

    I already submitted this to Adobe as a bug but want to inform everybody about this issue.
    If you export/render a file (Render Queue) as .h264 (mp4) and set under Output Module -> Format Options -> Multiplexer -> Stream Compatibility = Standard
    you do not get a streaming file!
    I tested this and I was not able to stream the file from an online webserver with a standard Flash video player.
    If you want streaming files then use the Adobe Media Encoder CS5.
    I tested it with the same file or After Effects composition and the same exact settings with Adobe Media Encoder CS5 and the resulting files stream perfectly from an online webserver!
    So be aware of this issue...
    I have to encode my 50 files again!
    Just to clarify: when I am using the word streaming I mean I think it's called "progressive download" and not real streaming like flash media server would do.
    If you want to try it yourself or for confirmation here are the steps to reproduce the bu
    ***BUG***
    1. Import a video file and drop it into a new composition of same size
    2. Add Composition to Render Queue
    3. Render Queue -> Output Module -> Format = .h264
    4. click on Render Queue -> Output Module -> Format Options
    5. set Multiplexer -> Stream Compatibility to Standard
    6. Render File
    7. Try to stream this file from an online web server
    8. Streaming this file is not possible. A Flash video player have to load the whole file before it can play it! File does not stream!
    ***Workaround***:
    1. render the same composition or video file with same settings with Adobe Media Encoder CS5
    2. This file streams perfectly! A Flash video player does not have to load the whole file before it can play it! Playing of the file starts immediately. File streams!
    I hope this is somehow helpful for some users
    http://www.felixdames.de

    I used AE for encoding because I have had a bunch of old video files (some are interlaced and needed a special deinterlace operation, some needed to get edited, some files were combined into one file....) for a redesign of my web page ...
    So the easiest and fastest workflow was to use AE.
    You are right with the 2 pass encoding... but I usually only use 1 pass encoding because it's much faster to encode and the difference in terms of file size and quality is not that much...
    I only posted this issue here for users (like me) who think that it is possible to export .h264 files for streaming purpose out of AE but as this test shows to me AE is not a good choice if you need the files for streaming.
    If you don't care about the streaming.... the files from AE look as good as when encoded with Adobe Media Encoder.
    My workaround was to save every AE project to disk and then I imported the AE composition directly into Adobe Media Encoder CS5 via Dynamic Link.
    Worked great...
    http://www.felixdames.de

  • Premiere PRO Crashes when exporting to H264

    I'm running Premiere Pro 6 on a Windows machine. I find if I export a sequence of over 30 mins length to H264, HD 1080i 25, it regularly crashes - I have the box marked 'Maximum Render Quality' ticked. Would appreciate any advice on how to prevent this!

    It would be very helpful to know the full details of your computer, your Source Files, and your Sequence Settings. See this FAQ Entry for what info you should post: http://forums.adobe.com/thread/961741?tstart=0
    Good luck,
    Hunt

  • Export to H264: FCP X vs Compressor 4

    I have a 6 minute clip.
    Exporting from within FCP X (cmd-E --> H264) takes about 7 minutes and I see about 42% CPU usage.
    This is not bad.
    I hoped however that using Compressor I could do it faster, perhaps utilizing more of my computer's processing power.
    So I chose "send to Compressor" and using the "HD 1080p video sharing" preset I got the following results:
    100% CPU utilization and 20 minutes compressing time.
    This is a huge difference. About 4 times more processing time.
    So I am left wondering.
    Is it a difference in the presets (e.g. single pass VS double pass) or is it something else going on here?
    Is there a way to discover what settings the built-in H264 export uses? A look at the manual was not helpful...
    Taking a look at Activity Monitor I noticed the well known "compressord" processes of the past, which remain 32-bit.
    When exporting directly from FCP X, it is the Final Cut Pro 64-bit process which does all the work.
    Of course the 64bit vs 32bit issue alone, cannot explain this huge difference in processing time.
    Is it perhaps OpenCL vs no OpenCL at all ? I have an ATI HD4870 graphics card, which could make a difference
    with OpenCL. At least this is what Apple promised when they started advertising OpenCL 2.5 years ago.
    I cannot say I am impressed by Compressor 4. Qmaster does not even run as a service.
    You have to keep Compressor open all the time, for your cluster to be available.

    Uncompressed and 4x4 are way, way overkill and make enormous files. There are actually five flavors of ProRes. 422 is the middle one, good for most things, but still pretty high data rate. There's also ProRes LT, which is a lower data rate, variable, but also 4:2:2 color. DV50 is twice the size of standard DV, but the 4:2:2 space is a great boon.
    To access the additional codecs you need to duplicate one of the Compressor presets. In the inspector, in the second button for the Encoder, click on the Video Settings button. There you can access the codecs like DVCPRO50 (Panasonic's designation).

  • Compressor3.53 genrating dulipcate frames when exporting from H264 to Apple Prores

    whn i was trying convert Animation playblast(H264 Codec) in compressor to appleprores422...genrating dulipcate frames..at 13th frame ....Orginally the animator will take playblast in NON-codec .OR Wraw codec formate ....later it will converts into H264 using Quicktime ..while the playblast playing like vedioShutters..wat i converted in Compressor
    i was using same preset from long bak...........this promble occuring for few days
    iam using compressor 3.5.3......QT.time 7.0 .. mac

    Not surprised the 10bit uncompressed won't play back on an iMac. Is 10-bit HD....? Yes, in fact in some opinions, 10 bit IS (the appropriate bit-depth for) HD.
    The other thing is that you must select your render codec and directory BEFORE you load the Render Queue. Otherwise everything goes out 'default',and to top it off, the XML export will reflect the changes you made AFTER -- which will then be, as they say, "wrong".... so yes, it matters.
    Internal Hard Drive is nowhere near what you'll need. Doing a compression from it shouldn't be a problem, though. Anything that doesn't need to run in real time should be okay. Heck, you could probably do 4K -- but not much of it, or very quickly.
    Seems like FCP really wants to work in bit depths in multiples of 8. Funny thing, that.
    I'm also mystified about the 'render in original codec' wrinkle in your fabric... I've never had an issue with DVCProHD like that. And the ProRes422HQ thing... I'm looking at a 5 minute project right now (just Media Managing the corrected version back to hard drive as I write this) that would duplicate your initial workflow and it looks, well, lovely. You may be simply overwhelming your hardware.
    jPo
    Message was edited by: JP Owens

Maybe you are looking for