Best practice for exporting a .mov file for YouTube

I am using FCPX 10.0.9 with a MacBook Pro. We are needing to upload relatively small-size high school football videos as .mov files to YouTube for my newspaper. I have been choosing the Export File option with the setting set to h.264, exporting the file to the desktop and then uploading that .mov file to YouTube. (I do not have Compressor installed on this Mac.) The other night the first of three files done like this uploaded fine, but the next two just kept processing and processing at YouTube and never finished. The following morning the files processed fine. Any thoughts about why ths might be happening?
And would it be better to export in another file format --.mp4 files -- instead that might cause less of a problem and which of the export options would be best?
Thanks,
Douglas

douglas i wrote:
Am I correctly uploading a .mov file to YouTube by using the Export File command with the export setting set to .h264 then if I wish a reasonable size file for upload?
Sure. There are many ways to get videos to YT and yours is a reasonable approach.
"Reasonable size" should be thought of in terms of upload time. Again, YT will re-compress whatever you give it. So depending on how quickly you need to get it up on the Web, it's better to upload files that have more information than less information. (To that end, some folks upload very large Pro Res files; they also have a lot of patience.) 
Just to let you know, the majority of FCPX users follow one of two workflows:
1) Share>You Tube option and have FCP handle the uploading;
2) Export as a Pro Res Master File; bring the master file into Compressor and apply the user's custom settings; upload using YT's uploader.
FWIW, I prefer the second workflow.
Russ

Similar Messages

  • Best settings for highest quality for exporting a .mov  file to h.264

    Hi,
    I want to know what the best settings are for the highest quality for exporting a .mov file (720p50) to h.264. I want the same quality as the original.
    I want to know the data rate etc.
    regards,
    Jeroen
    Message was edited by: Woudgraaf-AV

    There is no way to get the exact same quality when transcoding from an editing source to a highly compressed H.264 QT. However, you can get a real high quality by adjusting the data rate.
    However, these things depend on the length of the original. I routinely encode H.264s with good results in the 3000-5000 data rate range. I also make sure that I use multiple pass encoding. Take a short snippet of your project (10 seconds or so), and try various bit rates until you have one you like that doesn't take forever.
    Andy

  • Best MPEG Streamclip settings for exporting a .mov file? Please help!

    Am really stuck... I have a 1.6GB VOB file (which also exists in copy as a 2GB and a 1GB .mov file). I need to make a quicktime copy of the movie to upload online, but the maximum limit is 500MB. Because it's for a contact for a film festival, it needs to be as high quality as humanly possible, but has to be sent online. What precise settings should I use? I'm in the UK. Can anyone help me? Would be seriously grateful.

    We don't care how big the original is; it is the length that matters. Take your limit of 500MB and multiply by 1024 to get megabits. Divide that number by the length in seconds of your movie. That is your bitrate in megabits per second. Duplicate one of the best-quality presets and change the bitrate. Make sure all the high quality options are on.

  • Exporting an .mov file with timecode

    Hi -
    I'm trying to find the best way to export an .mov file from Premiere or Encoder with timecode either burned in (as well as embedded in the file). Right now when I export the .mov files no timecode is coming through. Normally I would be able to read the timecode with the earlier version of Quicktime, and I can see it is just starting at 0.
    I'm trying to export as .mov files so they can be given to transcribers.
    Thanks for any help!
    Elisa

    It get's it from where you tell it to in the effect's settings.  If it wasn't right, correct it.

  • Best/Easiest Practice for Distribution of Webhelp files for Fat(ish) Client Application

    So another in my long line of questions in trying to change the implementation of the help systems at my new employer.
    So, the pressure is to convince the existing guard to toss out the old method and go with a new method... One of the issues has come up for CSH Webhelp (via RH10)...
    Apparently, in the old method (where every help topic was it's own CHM - no, I'm not kidding).  They kept it that way so that any time a help file was updated, they could just send out that one chm to update that one topic.
    Now they are worried that if we switch to webhelp using topics in one single big project that we can't just send out a single updated file any more...
    So I'm trying to get ammunition as to how updates to the help can be distributed without it being a big hassle...
    We do have small updates that go out about every week, and they are afraid that going to the webhelp (1 project with lots of topics) method will require more time and effort for the techs because they will have to complete the update of a huge help system every time.
    One solution we have suggested is that we only update help files on major releases and add any changes to help procedures in the Release Notes or in a separate PDF and also include a note that the help files "will be updated to reflect this change in the XX/2015 XYZ Release).
    Does ANYONE have any other ideas of how distribution could be done efficiently so that we don't have to continue this "project per topic" fiasco?
    HELP!!! PLEASE!!!!

    Amebr - you hit the nail on the head... i want to apologize to everyone for all this mass hysteria...but this has been a freaking rollercoaster... one day they are happy with the plan, the next day they decided they want to complicate it more... So now my job is to find out how viable and how tricky and perhaps how dangerous it will be to send out JUST the files that have been changed.  Especially for CSH! 
    Anyone have any experience with this or have any advice?  Peter?  I suspect you might know how this might work... are they any pitfalls to watch out for.. I just have this fear of sending out a few files from an entire project... Altho, it appears when I publish, ONLY the files that have been edited in some way show a new date.. that includes non-topic files - so i'm assuming sending all those will keep the TOC, Index, and Search features working properly... as well as incoming and outgoing links from an edited topic?
    Another question would be how to handle new images in a project... as the image folder tends to be the largest, i don't want to have to send the entire image folder... Thoughts...????  Advice?  Jeff? Peter? Amebr? Bueller?  Bueller?  Bueller....?
    THANKS!Best/Easiest Practice for Distribution of Webhelp files for Fat(ish) Client Application
    OH... and Jeff... my apologies for the misnomer of using the term "Fat-ish" client in reference to this... I totally misspoke and should have said Mobile App... but in my mind, any time you have to download something to use it, it's a fat client... sorry!  :-/

  • Need help exporting .mov files for editing in PE3

    hi,
    i'm trying to export HD .mov files from an Aiptek GO-HD camcorder that seems to record in QT format with some funky codecs. I need to export it into a format that i can edit on a PC using Premier Elements 3.0. The few tests i've run have shown a huge increase in size when exporting from .mov to .avi (100m to 30 GB).
    Does anyone have any suggestions or experience doing this?

    You just need to open the .mov file with Elements.
    You don't need to convert it using QuickTime Pro
    first.
    Premiere may "convert" it to some other format to
    allow editing (I don't know) and that would only take
    some time at import.
    HD files are anywhere from 10 to 60 MB's per second
    (some even higher) so a DV version will drastically
    increase in file size.
    What, besides editing, is the goal of your work?
    that doesn't work with this camcorder. apparently the encoding is called QT, but it really isn't. i have to export into something else in order to edit.
    the goal of my work is to convert choppy family video into something clean that i can share with friends and family via CD / DVD (not streaming on net).

  • How can I convert .mov files for use with other apps?

    When loading movies taken on a friend's digital camera to my PC, the video files were saved as Quicktime .mov files. I am now unable to pull those files into any other software program (I want to put them onto a CD or DVD and play on external players.) How can I convert .mov files to a .wmv or .avi or mpeg?
    Thanks - J
    RS720G   Windows XP  

    Kodak Digital Camera QuickTime MOV Problems
    After battling a number of serious problems with the videos taken by my new Kodak Digital Camera, I decided to write up this page so that anyone searching the web would find out the true answers without as much grief!
    I’ve also made some other comments about my experience with the camera, in case anyone was considering buying a Kodak camera in the near future.
    I bought the camera just before Christmas 2004 in the US. At the time of writing, it is a pretty good model for domestic use—about 5.2 megapixels, costing about US$400 (or AU$600 back here in Australia). From a company as reputable as Kodak, I expected no problems.
    The first disappointing thing was that the spring inside the spring-loaded battery clip, inside the camera, came loose within days. It proved impossible to reattach it without completely dismantling the camera, which (despite my engineering qualifications) I was not willing to do. This would usually have been a warranty item, but Kodak’s warranty does not extend to other countries. I’ve since had to jam cardboard in to keep the battery clip engaged, and have taped the battery bay shut to avoid it opening accidentally when taking the camera out of the case. This works fine with the docking station (an extra AU$100!), but it means I can no longer charge the battery without the docking station (since you need to take it out to charge it). I was not impressed!
    The camera takes good photos, and I have no complaint with that. The controls and camera menus are well-designed. The large display is excellent.
    The EasyShare software is not as easy to use as it looks, has a habit of crashing, has a web update program that is always running in the background of Windows, and transferring images is nowhere as easy or quick as it should be. I’ve now uninstalled it completely, and simply copy the photos directly from the device. (If the camera memory is nearly full, and you just want to transfer the last few photos, then it’s impossible to use the EasyShare software to browse the camera’s photos without it actually downloading the whole lot through the USB cable—and it takes forever! Copying from the device directly doesn’t hit this bug.)
    The capability to take video using the camera was a great attraction when I selected it, and, if it worked properly, it would make it quite a handy little camcorder in its own right. With a 512 MB memory card in it, over an hour of video can be recorded at Video-CD quality (320 x 240 24fps video, 8 kHz audio). It’s not full digital video, but it would still be a pretty good feature for a US$400 camera. If it worked.
    The first disappointing thing about taking videos is that the optical zoom cannot be adjusted while the camera is recording. It can only be adjusted between video sequences. I don’t know why this restriction was made in the design.
    The real problems, however, start when you try to do anything with the video clips captured by the camera. Kodak has chosen to capture the videos in QuickTime format. This is fine—QuickTime is, technically, excellent—except that there is no simple way to convert QuickTime MOV files to AVI or MPEG or VCD. The Kodak software comes with a QuickTime player, so you can see the video clips on the computer you installed the software on—and they look good. Problem is that you can’t just dump those MOV files onto your Video-CD creator (it will usually want AVI or MPEG files).
    It takes some time to realise that Kodak have not even bothered to include any software with the camera that can convert these MOV files to a more useful format. This is a serious PR blunder, and anyone bitten by this is unlikely to go near the Kodak brand ever again.
    After some web searching, owners of these cameras generally find that the best (only?) freeware solution to convert MOV to AVI is Bink and Smacker’s RADtools program.
    RADtools is amazingly powerful for the price (i.e. free), but it hits two fundamental problems with Kodak Digital Camera MOV video files, that are the fault of the Kodak camera, not RADtools. (I know this because every other MOV converter hits the same problems—except one, as you will see below.)
    The first problem is that the sound cannot be converted properly. When you convert any Kodak MOV files, there is an “aliasing” of the sound at the upper frequencies. This is a technical description—you get a whispery, tinny, C3PO type of echo to everything. It really destroys the quality of the video clips (especially bad when I am trying to capture priceless memories of my 4- and 7-year-old sons—I don’t want their voices destroyed for all time).
    Every conversion program I tried ended up with the same audio problem. I concluded that it is something strange in the way the Kodak cameras store the MOV files.
    Strangely enough, I noticed that the QuickTime player didn’t distort the audio like this. The audio sounds just fine through QuickTime. More on this shortly.
    The second, more serious problem is that RADtools could not properly convert some of the video clips at all. (This problem only affected less than 10% of the clips I originally filmed, but most of those clips were very short—less than 20 seconds. It seems that the probability of this problem gets worse, the longer the clip.) RADtools would misreport the number of frames in the clip, and would stretch out a small number of frames of video (in slow motion) to match the length of the audio.
    Again, I confirmed that this is a property of some of the MOV files stored by the camera. Other conversion tools also had problems with the same MOV clips.
    After more angst, I found a number of websites in which frustrated owners of these Kodak cameras have reported the exact same problems.
    It was only then that I discovered that QuickTime itself can convert MOV files to AVI. Believe it or not, it’s built into the QuickTime Player that Kodak supplies, or that you can download free from apple.com. The problem is that you can’t use it unless you pay Apple to upgrade to QuickTime Pro.
    After realising that this would probably be the only way to get decent audio for these clips, I paid the AU$59 to Apple Australia to get the licence key that enables the extra “Pro” menu options in QuickTime.
    Sure enough, you can “Export” any MOV file to a number of formats, including AVI. And guess what? The audio comes out fine!
    So, the first piece of advice I can give is: pay Apple the US$29 (or whatever amount it is in your country) to upgrade QuickTime to QuickTime Pro.
    From here, however, there are still a few snags to untangle.
    The first is that the default settings for Exporting to AVI don’t give a great result. It defaults to the Cinepak codec, medium quality. This looks terrible compared to the original QuickTime movie. Even on maximum quality, that codec just doesn’t give good results.
    I finally found that the best option is to use the Intel Indeo Video 4.4 codec, set on maximum quality. This creates AVI files that are 10 to 20 times larger than the original MOV files, but the quality is there. If (like me) you only want the AVI files so you can dump them into your Video-CD program, then you want to keep the quality as high as possible in this first step. The extra hard disk space is not really a concern. When your VCD program converts the AVI files to MPEG, it will compress them to the usual VCD size.
    Now for the biggest snag: those problem MOV files are still a problem, even for QuickTime Pro. Unbelievably, these Kodak cameras are spitting out MOV files which have some sort of technical flaw in their data specifications. QuickTime is able to play them back fine—and that seems to be all that the Kodak engineers really checked. However, if QuickTime Pro tries to export them, then when the progress bar gets to the end, it never finishes. It just keeps going. If you check the output folder with Explorer, and keep hitting F5 to update the file listing, you can see the file getting bigger, and bigger, and bigger. It never stops.
    That this happens even for QuickTime itself (the native format for these files) confirms that the problem is with the software built into these Kodak cameras. It would be nice it they issued a patch or a fix. I couldn’t find one.
    Fortunately, there is a “workaround” for this problem. I found it when trolling the net trying to find solutions to all these problems. The workaround is to use QuickTime Pro’s cut and paste facility. Open the problem MOV file, then press Ctrl-A (the standard key combination for “select all”—in this case it selects the entire film clip, as you can see by the grey selection of frames at the bottom of the player). Then hit Ctrl-C (i.e. copy, which in this case copies all the frames, but not the incorrect data structure in the original MOV file). Now hit Ctrl-N (i.e. new, in this case a new MOV file or player). In this new player, press Ctrl-V (i.e. paste). Now you have a new version of the MOV file with the bad data structure exorcised. You can save this under a new name, but make sure you specify “Make movie self-contained”—otherwise, it will simply be a link to the original (bad) MOV file, which you are probably going to delete once you save the exorcised version. (You also cannot overwrite the original file, because it needs to access that to make the “self-contained” movie. You need to give it a slightly different name, save it “self-contained”, then delete the original and rename the new copy back to what you wanted it to be. A pain, I agree, but at least the **** thing works—finally!)
    The exorcised MOV file can now be used to Export to AVI format. (I also keep all the MOV files on a separate CD, in case I want to reconvert them to a different format in the future. I figure it’s better keeping the exorcised ones than the haunted ones.)
    So I hope that all this answers a few of your questions. No, you weren’t being incredibly stupid.

  • Importing/converting DVD to .mov file for FCP

    I had a friend give me a homemade DVD that I want to import/convert into a .mov file for editing in FCP. I've read the threads on MPEG Streamclip, but it asks to select the file(s) to import (vs one file). Not sure if I'm on the right track.
    Here's what I see on the DVD:
    http://i149.photobucket.com/albums/s63/jtnacc/ishot-4.jpg
    Any help would be appreciated.
    John

    Hi Piero... Congrats man... your explanation is the best simple explanation of getting material off a DVD into a form where it can be editied in FCP.
    Just to make it clear to anyone else...
    1- go to http://www.squared5.com/ and download the FREE program MPEG STREAMCLIP.
    Install it in your applications folder. Start Mpeg Streamclip, and insert the DVD into your drive.
    2- Go to FILE > OPEN and use that to navigate to the DVD, look in the video_ts file and select the first .vob file of a series, e.g. VTS010.VOB; you'll be asked if you want to open all files of that stream, and you answer yes. You'd better also apply the command Edit/Remove Timecode Breaks before exporting.
    This takes a minute or three depending on how much material ois on the DVD.
    3 - Now go to the Mpeg Streamclip command line and select **Export to QuickTime** (NOT Export to DV)
    Use these settings :
    Compression: Apple DV-PAL (DV-PAL for UK/Europe, or Apple DV-DVCPRO/NTSC), Quality: 100%,
    fps: 25 for PAL or 29,97 for NTSC,
    Audio: uncompressed, Stereo, 48 KHz.
    AND hit go !
    Mpeg Streamclip will promt you to name the new file name and a location for saving.
    This can take a minute for every minute of material.. so is a slow process.
    I decided to use the "in" and "out" markers on Mpeg Streamclip to define smaller chunks of the DVD to convert at a time... rather than risk it running for 40 minutes and crashing (which it did first time). If you're ripping the DVD for editing purposes then this should not cause any problems.
    Once it's finished, go to the save location, and you should see a Quicktime movie with the name you gave it.
    You can now go into FCP and IMPORT this Qtime move and edit it.
    MARVELOUS
    Thanks again Piero - this has really helped me
    P

  • I recently purchased QuickTime 7 Pro to convert avi files to mov files for editing on Imovie. However, QuickTime won't play the files. How can I get them to play and how can I convert them to mov files?

    I recently purchased QuickTime 7 Pro to convert avi files to mov files for editing on Imovie. However, QuickTime won't play the files. How can I get them to play and how can I convert them to mov files?

    I recently purchased QuickTime 7 Pro to convert avi files to mov files for editing on Imovie. However, QuickTime won't play the files. How can I get them to play and how can I convert them to mov files?
    Both the AVI and the MOV file extensions refer to the file container and not the compressed data the file contains. Both are generic file containers in that each may contain any valid combination of audio and/or video data that is compatible with the codec component configuration of the system on which the file was created. On the other hand, whether a file is playback compatible, conversion compatible, and/or edit compatible depends on the data actually contained in the file container. So, you are basically dealing with two separate issues here—the container and what is inside it.
    Basically, if you want to make your files ediit compatible with iMovie, you must change your file container to one that is acceptable to iMovie and convert the data to edit compatible audio and/or video compression formats as may be necessary. The best approach is to determine what codecs were actually used to create the original AVI files and add them to your system if possible. In most cases a codec package like Perian can be added to your system's codec component configuration to may the AVI file playable. Once they are playable, in the QT 7 app then they can be chnged or converted to file types and compression formats that can be edited in iMovie. (While Perian handles most codecs commonly used to create AVI files, it does not handle all possibilities and, while the Perian codec package still works under cureent Mac OS versions, its development group has decided to drop further development/support of the package.)
    Background: AVI is a file container originally developed by Microsoft back in 1992 but for which official support was discontinued about 11 years. Despite its limitations, Windows users still tend to use this file based on its open source ease of use and generic nature, thus, making its use so popular that most users are unwilling to switch to more modern but less generic file types. Since some AVI legacy compression formats have never been transcoded for the Mac or use beyond OS 9 or OS X PPC platforms, it is often important to know what specific compression formats are contained in the AVI file to know which codecs to add to your system and which not to add in order to avoid possible codec conflicts.
    You can use many different converters to convert AVI files to iMovie edit compatible files. Most third-party apps contain their own buit-in codecs which do not relay on the Mac codec component configuration. Free ones, like HandBrake, usually have limited conversion capabilities while those that have more varied outputs are usually commercial in nature and will cost you additional cash. QT 7 Pro or the free MPEG Streamclip app allow you to access you own system's component configuration and use any available codec component like DV, AIC, MPEG-4, H.264, Photo JPEG, etc.—all of which are iMovie compatible for editing purposes—but only after making the AVI file QT 7 player compatible.
    In order to determine what compression formats wewre used in your AVI files you can
    1) Try checking the Finder "Info" window,
    2) Use the "Inspector", "Media Info", or "Properties" window of any player app that will open the file, or
    3) Use a general media utility app like "MediaInfo" to read the file characteristics.

  • Export Quicktime movie is not rendering video track, just the audio track. However, everything works when using Quicktime Conversion menu options. What is wrong with my setting for Export Quicktime movie?

    Export>Quicktime movie is not rendering video track, just the audio track. However, everything works when using Quicktime Conversion menu options. What is wrong with my setting for Export>Quicktime movie?

    When you converted the original files via MPEG Streamclip, what did you convert them to?
    Have you tried trashing your preferences in FCP? Trashing FCP prefs is usually the first step when FCP is performing strangely.
    Download Preference Manager from Digital Rebellion (free) at:
    http://www.digitalrebellion.com/prefman/
    It will allow you to archive your current preferences if you wish to restore them later.
    MtD

  • Is there a workaround for exported Muse html files to render accurately when opened in DreamWeaver d

    Is there a workaround for exported Muse html files to render accurately when opened in DreamWeaver design view?

    Have a look at this thread that should answer your query - http://forums.adobe.com/message/5231996.
    Thanks,
    Vinayak

  • How to use .mov files for video in Flash...

    Hello-
    I am trying to use .mov files for my Flash videos. I know it uses .mp4/flv/f4v, but I really need to use .movs. I know this works... but how?
    Suggestions?

    unfortunately running it through Adobe Encoder makes it a much, much larger file and the quality goes out the window. i really need to use .mov.
    any suggestions?

  • Resolution for .mov files for film festivals

    Some film festivals are asking for .mov files for screenings. Nowhere can I find what type or resolution they want or if there's an industry standard.
    I have seen that if they play it back from a laptop (and you never know) that too high a resolution won't work.
    Is there a standard for movie theaters?
    Thanks.

    Neal Fox wrote:
    … Is there a standard for movie theaters?…
    Yes and No
    DCP is a worldwide, digital delivery standard for commercial theaters. But, by standards, is for example 'limited' to 24fps - sad news, for Mr P. Jackson or J.Cameron (no idea, how HFR nor 3D is delivered…)
    highly complex to encode, there are specialized companies offering 'transfer services' - $$$, creates enormous files (an intra-compression codec), asks for 'Linux formatted/ext2'-drives, etc etc etc ,.. . (just read about it - no clue what I'm talking about!!)
    Plan B)
    ask the theatre what they want …or use.
    Plan C)
    1080/24p, h.264/high profile/20mbps in a mp4 should be very universal … (who asks for mov can playback mp4 too)
    … but then, next question:
    What media? stick, dataDisk, hard drive, ftp-upload?
    What format? fat32 (doesn't work for longer movies…), exFat, ntfs??
    some non-commercial festivals allow/prefer delivery by BluRay or even on DVD ...
    again, 'limited' too, but very, very universal …

  • I'm sorry, I have to convert the mov file. for use with fce and / or imovie11, better ProRes422 or intermediate codec?

    I'm sorry, I have to convert the mov file. for use with fce and / or imovie11, better ProRes422 or intermediate codec?

    FCE only used AIC for HD.
    Al

  • What is the best practice in securing deployed source files

    hi guys,
    Just yesterday, I developed a simple image cropper using ajax
    and flash. After compiling the package, I notice the
    package/installer delivers the same exact source files as in
    developed to the installed folder.
    This doesnt concern me much at first, but coming to think of
    it. This question keeps coming out of my head.
    "What is the best practice in securing deployed source
    files?"
    How do we secure application installed source files from
    being tampered. Especially, when it comes to tampering of the
    source files after it's been installed. E.g. modifying spraydata.js
    files for example can be done easily with an editor.

    Hi,
    You could compute a SHA or MD5 hash of your source files on
    first run and save these hashes to EncryptedLocalStore.
    On startup, recompute and verify. (This, of course, fails to
    address when the main app's swf / swc / html itself is
    decompiled)

Maybe you are looking for