I noticed today that an export was going along smoothly then suddenly crawled to nearly a halt. Glancing around I just happened to notice that the hard drive the file was being exported to had only a few gigs left on it. Another case of someone putting something into the trash and failing to empty it.
After emptying the trash -and freeing up over 30 gigs of space- the export speed seemed to pick back up to what would be expected. I'm not 100% sure that was the cause, it could have just coincided with exporting (and rendering out since nothing was pre-rendered) a particularly graphic laden section or something.
Showing posts with label exporting. Show all posts
Showing posts with label exporting. Show all posts
Wednesday, July 10, 2013
Tuesday, May 1, 2012
Name Sequences Appropriately Now To Save Time Later
I was watching the "head" of a group of editors a few days ago and while I waited for some photos to come in ("Can you do that moving pictures things like in documentaries?") I watched this person export a sequence, rename it, then compress it to the various formats the client needed then rename it again.
Then I watched him do it again.
And again.
And I realized what bugged me about it. I tend to name my sequences the final output file name right from the get go.
For example in my Bin, I'd have a sequence named along these lines:
An example would be
tyrellcorp-nexus07promo-newVO_V03
So when it's exported from the timeline it becomes:
tyrellcorp-nexus07promo-newVO_V03.mov
That way when I transcode it to something like H.264 or whatever (NO...NO WMVs! Not anymore!) it ends up in a handy name, with notations with version number and no spaces or weird characters that occasionally screw up FTP servers and email links and other various and sundry tend-to-go-wrong-unexpectedly-thingys.
I'll even mention what file type it is on the flashdrive/DVD/HD I hand them right in the file name sometimes:
tyrellcorp-nexus07promo-newVO-V03.h264.mov
tyrellcorp-nexus07promo-newVO-V03.animation.mov
Like that.
What the guy I was watching was doing was changing:
Tyrell Corp Nexus 07promotion with New VO
into something like
tyrellcorp-nexus07promo-newVO-V03.mov
by renaming it in the Finder each time.
My advice: name your sequences something that you won't have to edit later to send to the client or their FTP/cloud/server whatever.
Then I watched him do it again.
And again.
And I realized what bugged me about it. I tend to name my sequences the final output file name right from the get go.
For example in my Bin, I'd have a sequence named along these lines:
An example would be
tyrellcorp-nexus07promo-newVO_V03
So when it's exported from the timeline it becomes:
tyrellcorp-nexus07promo-newVO_V03.mov
That way when I transcode it to something like H.264 or whatever (NO...NO WMVs! Not anymore!) it ends up in a handy name, with notations with version number and no spaces or weird characters that occasionally screw up FTP servers and email links and other various and sundry tend-to-go-wrong-unexpectedly-thingys.
I'll even mention what file type it is on the flashdrive/DVD/HD I hand them right in the file name sometimes:
tyrellcorp-nexus07promo-newVO-V03.h264.mov
tyrellcorp-nexus07promo-newVO-V03.animation.mov
Like that.
What the guy I was watching was doing was changing:
Tyrell Corp Nexus 07promotion with New VO
into something like
tyrellcorp-nexus07promo-newVO-V03.mov
by renaming it in the Finder each time.
My advice: name your sequences something that you won't have to edit later to send to the client or their FTP/cloud/server whatever.
Saturday, July 9, 2011
Fixing Quicktime's Gamma Export Problem with H.264
For a LONG time now Quicktime has had an issue exporting to H.264 where it'll bump up the gamma and make your exports look brighter than it did originally. It's a long-standing bug that I'm fairly shocked hasn't been addressed yet.
A simple-ish fix is to install x264encoder from here. It's FREE.
After installing it, re-launch your export software and select "x264Encoder" from the export options and before anything else, hit the Options… in the lower left.
From there hit "Tagging".
At the top left checkmark "Add gamma 2.2 (SD/HD content)".
This will dramatically fix or at least help the gamma H.264 shifting problem.
x264encoder seems complicated but since there are some really great presets you can get amazing results, small files sizes with only a few clicks. Exports will take longer to encode though sometimes so be aware.
A great article on this is here which goes into much more detail.
For curiosity a deprecated method (in case you don't have x264 installed or have don't a connection on location) is here. x264encoder is something you should have on that flash drive in your pocket, btw.
Thanks to IK for reminding me I never posted this after mentioning it ages ago.
A simple-ish fix is to install x264encoder from here. It's FREE.
After installing it, re-launch your export software and select "x264Encoder" from the export options and before anything else, hit the Options… in the lower left.
From there hit "Tagging".
At the top left checkmark "Add gamma 2.2 (SD/HD content)".
This will dramatically fix or at least help the gamma H.264 shifting problem.
x264encoder seems complicated but since there are some really great presets you can get amazing results, small files sizes with only a few clicks. Exports will take longer to encode though sometimes so be aware.
A great article on this is here which goes into much more detail.
For curiosity a deprecated method (in case you don't have x264 installed or have don't a connection on location) is here. x264encoder is something you should have on that flash drive in your pocket, btw.
Thanks to IK for reminding me I never posted this after mentioning it ages ago.
Labels:
bug,
exporting,
gamma,
h.264,
handy software,
quicktime,
troubleshooting
Monday, March 21, 2011
How To Crop A QuickTime Movie
Cropping a QuickTime Movie is a hassle; but there are some ways to go about it to make it slightly less hassleful. (yes, I just made up that word)
A: Use an image editing program to make a mask.
1. Open the movie file in QuickTime and hit Command + C to Copy it. (You're actually just copying a frame)
2. Launch your image editor and paste in the clipboard's contents (the frame of your video file) into a new document. Make sure the document size is the same size as the image you just pasted.
3. Using the Selection, Paint Bucket, Fill or whatever tools you have available make the part of the video you want solid black. Make the part of the video you want to crop (to go away) solid white.
4. Save out your image as a .jpg or .gif or whatever format you like.
5. Open the movie to be cropped in QuickTime 7 if it's not already, and then hit Command + J for "Show Movie Properties".
6. Click "Video Track" in the top portion of the window.
7. Click "Visual Settings" in the lower portion.
8. Under "Mask" on the left hit the "Choose…" button. (or, even easier, drag your mask image file into the Well here.
9. You'll INSTANTLY see your opened QuickTime movie crop to the mask.
10. Notice that both the Movie Properties and QuickTime Player windows have "unsaved" dots in the close widget. Close the Movie Properties window.
11. Export away.
B: Use MPEG Streamclip.
1. Download and install the FREE program MPEG Streamclip if you don't have it already.
2. Open your QuickTime clip in MPEG Streamclip.
3. Hit Command + E for "Export to Quicktime".
4. At the top of the "Movie Exporter" window that pops up under "Compression" select the codec you want. (yes, you may see ProRes 422 listed twice; no I don't know why. It's likely the bottom one is actually ProRes HQ, but that's just a guess)
5. Monkey with all the rest of the options there if you know what your'e doing. If you don't, don't touch.
6. Near the bottom, above the "Presets…" button Checkmark the "Cropping:" checkbox.
7. At the end of this line you'll see a pulldown. You'll probably want to leave it on "Destination".
8. Now, how the heck do you know what numbers to put into here? Open the SAME QuickTime clip you're cropping in QuickTime 7. Yes, really.
9. Make sure it's full size and then hit this key combo: Command + Shift + 4 which will let you take a screenshot of a portion of the screen. Click-N-Drag out a box that has only what you want the exported QuickTime movie to have. Let go of the mouse. You'll have a screenshot on your desktop.
Note: You can just watch the cursor here to get the numbers right before you let off the mouse but it's up to you.
10. If you didn't memorize the numbers the cursor showed in step 9 before you let off the mouse go and look at the Get Info of the screenshot (on your Desktop) that you just took. Depending on how you have your Finder options set up, you make see the size of the image listed under it or next to it. If you don't, highlight it, tap Command + I for "Get Info" and look for "Dimensions" under "More Info:"
Lets just say it's 604 X 636, for fun.
11. While you have your QuickTime clip opened in QuickTime hit Command + I for "Show Movie Inspector" and jot down the size under the "Format" line. Let's say ours is 830 X 876 to make things interesting.
12. MATH TIME!!!! Now we can rough in the crop numbers.
For the top to bottom take the actual height and subtract the desired height: 830 - 604 = 226. Now divide (we're distributing it equally) it by 2 and we get 114.
For Top and Bottom in MPEG Streamclip's Cropping line enter 114.
Now for the side to side: 876 - 636 = 240 and divided by 2 that equals 120. Type 120 into both the Left and the Right boxes in MPEG Streamclip.
13. Hit the bottom-left "Preview" button at the bottom.
Is it close? Told you we roughed it in.
Adjust the cropping numbers until you're happy.
In my test my final numbers were:
Top: 114 Left: 120 Bottom: 127 Right 124
instead of:
Top: 114 Left: 120 Bottom: 114 Right 120
Oh, and fee free to monkey with the Center options in this window as well. The Positive Numbers in the first box will move your image to the RIGHTWARDS while Positive Numbers in the second box will move your image DOWNWARDS.
Honestly, I'm not sure why it's off like that but I've used this method to rough it in for a while. I discovered it when I was on a company's Mac that didn't have an image editor at the time and the IT people (Grrr…) REFUSED to allow me to install an image editor to make an image mask with.
Sure there are other ways but they usually involve people mentioning VisualHub which is getting mighty long in the tooth and is totally unsupported now (sniff…) or they're even more convoluted than these two methods. If you have another way you like please pass it along.
QuickTip: Keep a flash drive on in your pocket with Gimp installer (it's FREE) on it but it's not much help if you don't have Admin access to the machine anyway. There are ways around this though.
A: Use an image editing program to make a mask.
1. Open the movie file in QuickTime and hit Command + C to Copy it. (You're actually just copying a frame)
2. Launch your image editor and paste in the clipboard's contents (the frame of your video file) into a new document. Make sure the document size is the same size as the image you just pasted.
3. Using the Selection, Paint Bucket, Fill or whatever tools you have available make the part of the video you want solid black. Make the part of the video you want to crop (to go away) solid white.
4. Save out your image as a .jpg or .gif or whatever format you like.
5. Open the movie to be cropped in QuickTime 7 if it's not already, and then hit Command + J for "Show Movie Properties".
6. Click "Video Track" in the top portion of the window.
7. Click "Visual Settings" in the lower portion.
8. Under "Mask" on the left hit the "Choose…" button. (or, even easier, drag your mask image file into the Well here.
9. You'll INSTANTLY see your opened QuickTime movie crop to the mask.
10. Notice that both the Movie Properties and QuickTime Player windows have "unsaved" dots in the close widget. Close the Movie Properties window.
11. Export away.
B: Use MPEG Streamclip.
1. Download and install the FREE program MPEG Streamclip if you don't have it already.
2. Open your QuickTime clip in MPEG Streamclip.
3. Hit Command + E for "Export to Quicktime".
4. At the top of the "Movie Exporter" window that pops up under "Compression" select the codec you want. (yes, you may see ProRes 422 listed twice; no I don't know why. It's likely the bottom one is actually ProRes HQ, but that's just a guess)
5. Monkey with all the rest of the options there if you know what your'e doing. If you don't, don't touch.
6. Near the bottom, above the "Presets…" button Checkmark the "Cropping:" checkbox.
7. At the end of this line you'll see a pulldown. You'll probably want to leave it on "Destination".
8. Now, how the heck do you know what numbers to put into here? Open the SAME QuickTime clip you're cropping in QuickTime 7. Yes, really.
9. Make sure it's full size and then hit this key combo: Command + Shift + 4 which will let you take a screenshot of a portion of the screen. Click-N-Drag out a box that has only what you want the exported QuickTime movie to have. Let go of the mouse. You'll have a screenshot on your desktop.
Note: You can just watch the cursor here to get the numbers right before you let off the mouse but it's up to you.
10. If you didn't memorize the numbers the cursor showed in step 9 before you let off the mouse go and look at the Get Info of the screenshot (on your Desktop) that you just took. Depending on how you have your Finder options set up, you make see the size of the image listed under it or next to it. If you don't, highlight it, tap Command + I for "Get Info" and look for "Dimensions" under "More Info:"
Lets just say it's 604 X 636, for fun.
11. While you have your QuickTime clip opened in QuickTime hit Command + I for "Show Movie Inspector" and jot down the size under the "Format" line. Let's say ours is 830 X 876 to make things interesting.
12. MATH TIME!!!! Now we can rough in the crop numbers.
For the top to bottom take the actual height and subtract the desired height: 830 - 604 = 226. Now divide (we're distributing it equally) it by 2 and we get 114.
For Top and Bottom in MPEG Streamclip's Cropping line enter 114.
Now for the side to side: 876 - 636 = 240 and divided by 2 that equals 120. Type 120 into both the Left and the Right boxes in MPEG Streamclip.
13. Hit the bottom-left "Preview" button at the bottom.
Is it close? Told you we roughed it in.
Adjust the cropping numbers until you're happy.
In my test my final numbers were:
Top: 114 Left: 120 Bottom: 127 Right 124
instead of:
Top: 114 Left: 120 Bottom: 114 Right 120
Oh, and fee free to monkey with the Center options in this window as well. The Positive Numbers in the first box will move your image to the RIGHTWARDS while Positive Numbers in the second box will move your image DOWNWARDS.
Honestly, I'm not sure why it's off like that but I've used this method to rough it in for a while. I discovered it when I was on a company's Mac that didn't have an image editor at the time and the IT people (Grrr…) REFUSED to allow me to install an image editor to make an image mask with.
Sure there are other ways but they usually involve people mentioning VisualHub which is getting mighty long in the tooth and is totally unsupported now (sniff…) or they're even more convoluted than these two methods. If you have another way you like please pass it along.
QuickTip: Keep a flash drive on in your pocket with Gimp installer (it's FREE) on it but it's not much help if you don't have Admin access to the machine anyway. There are ways around this though.
Labels:
crop,
exporting,
gimp,
mpeg streamclip,
photoshop,
quicktime pro,
tips,
transcoding
Wednesday, February 23, 2011
Exporting Long Clips and File Name Corruption
This happens to me frequently enough that it's more hassle than anything else. And I'm not alone on this which has been happening for some time.
For me when I export a clip that's long, say 60mins or so, FCP will occasionally fail to complete writing the file name.
For example if the clip you're exporting from FCP is supposed to be called
"A Long Clip_Version 01" which should appear as
"A Long Clip_Version 01.mov" when exported, it'll sometimes end up as
"A Long Clip_Versi#WTF.mov".
It seems more likely to happen with longer file names as well. The good news is that the file is likely 100% A-OK. The bad news is you have to rename it to what you want. Meh.
I suspect that it has something to do with temporary file names and how the Finder works. When the Finder is working with a file (actually mainly creating a file) it'll will tend to assign a semi-random name to it until it is done with the file. This is especially true if the Finder is replacing a file with a new one.
You can see this in action yourself with a tool like fseventer. There are many reasons why the Finder does this little bit of prestidigitation but one specific example (but not a hard rule) is if you change the preferences to something, the Finder won't always write the changes to the currently in-use pref file but it'll create a new one, with a random name or portion of a name, and when it's done will quickly trash the file in use and name the new one, the old name. The app using the prefs never knows the difference.
For me when I export a clip that's long, say 60mins or so, FCP will occasionally fail to complete writing the file name.
For example if the clip you're exporting from FCP is supposed to be called
"A Long Clip_Version 01" which should appear as
"A Long Clip_Version 01.mov" when exported, it'll sometimes end up as
"A Long Clip_Versi#WTF.mov".
It seems more likely to happen with longer file names as well. The good news is that the file is likely 100% A-OK. The bad news is you have to rename it to what you want. Meh.
I suspect that it has something to do with temporary file names and how the Finder works. When the Finder is working with a file (actually mainly creating a file) it'll will tend to assign a semi-random name to it until it is done with the file. This is especially true if the Finder is replacing a file with a new one.
Friday, August 6, 2010
Quickly Name New Files in Open and Save Dialogs
Here's a quick one.
When you're exporting or saving a file that doesn't have the name you want, and you need to name it something based on another file just click on a similarly named (and greyed out) file in the Open/Save dialog to pre-name it that file name.
For example, lets say you have to export 10 different versions of a edited piece and don't want to type in "Video With A Needlessly Long Name 01", "Video With A Needlessly Long Name 02"...you can click on the greyed out, already there in the folder file with the name you want and the OS will name the currently ready to be exported or saved file identically to the one you clicked on so all you have to do is append your numbering convention, 02, B, Alt, whatever you use.
When you're exporting or saving a file that doesn't have the name you want, and you need to name it something based on another file just click on a similarly named (and greyed out) file in the Open/Save dialog to pre-name it that file name.
For example, lets say you have to export 10 different versions of a edited piece and don't want to type in "Video With A Needlessly Long Name 01", "Video With A Needlessly Long Name 02"...you can click on the greyed out, already there in the folder file with the name you want and the OS will name the currently ready to be exported or saved file identically to the one you clicked on so all you have to do is append your numbering convention, 02, B, Alt, whatever you use.
Tuesday, February 16, 2010
When the Client can't Play the QuickTime File

If you haven't gotten this 3am phone call yet...you will in time. It's inevitable.
A client will one day call you late into a quiet evening saying they can't play the QuickTime files you've sent them. Since they need them in HD and regular DVD's can't (technically unless you mix HD-DVD with some prestidigitation) do HD content you need to send them something they can use...NOW! THE PRESENTATION IS IN 10 HOURS ZOMG!!!1!!1!
You have two options overall:
Send 'em a disc:
1. Send them a Blu-Ray. But, wherever they're playing the thing it won't have Blu-Ray so don't even bother. Seriously. Check this link in a year or seven for updates.
2. Send them a data DVD, wait I should hyphenate that, a data-DVD and tell them to play it on their MacBook Pro hooked up to a projector or whatever using QuickTime or VLC. However, it's likely they won't have a Mac/it won't mount/the file won't play/the projector won't see the laptop... It's possible that not even "marketing" will have a Mac nor will the "creatives" over in advertising. They can edit in After Effects anyway, right?
So you need to send HD content to someone with a PC who is likely still using XP who can't download much at work because the IT guys are scared of those darned h@x0rz who are gonna steal all their creative sekr3tz.
Send 'em a file:
Flash drives are cheap. Macs understand FAT-32 (but not NTFS fully, sorry). I mail flash drives to clients regularly.
I don't allow clients to have .wmv's or .flv's. I don't. I'm like that because I'm not a huge fan of either format, neither is any good and few clients (or the presenters at least) have the cpu to play them smoothly since they're using 48 year old laptops issued by the company that sometimes don't even have CD-ROM drives (but that's for another post/rant).
It's for the client's own good really and I tell them as much. See, your job as editor/shooter/writer/person-who-knows-stuff is to not just deliver what the client wants, but let them know what they want because 99.9854% of the time they have no idea. Dale Carnegie said people are just waiting to be told what to do, and with corporate clients it's thricely true. They need guidance because without it they'll suggest their son or nephew or daughter or someone can do it. They play with neckties and Lotus Notes all day in between bouts of blackberry gazing, lunch an "officeing", they don't know. And honestly, they don't care, they just want it to work. NOW!!!!!...
That's for corporate things; for broadcast or features hand them exactly what they ask for. That way, when it goes ka-bleewy, they can only blame themselves.
So, a real option is to export the HD project as one of the following files:
Animation. Huge files.
Motion JPEG. I've had PC people complain that the video "stutters."
Apple Video. Should work, people seem reluctant.
ProRes. They'll have to download the free codec from Apple.
I'd go with Animation or ProRes for the project. These are easily transcoded to something else. Others work, sure but these are the most reliable I've found. If they're going to play it from a laptop these are good options except for maybe Animation which likes lots of CPU. If they want a standard DVD, tell them that it won't be HD. If they demand HD and their computer/laptop situation is lacking then...
Here's a secret:
The client needs to show an HD video at some convention/presentation/meeting/agency/sub-clientle lunch/what-ever-it-is... tell them to buy one of these:
WD TV Live Media Player. Get them to buy a big 32Gig or larger flash drive (the WD TV Live Media Player understands HFS+ [not journaled]). Encode the HD content to a nice H.264 file then hand them a flash drive with the file, or upload it to them and tell them to transfer it to the flash drive and you'll be done. (Test the set-up though, always test set-ups)
It's small, has a remote, plays tons of formats, shows pictures, plays music, hooks up to the net to stream stuff and has two USB ports. They'll look like a hero because you'll be a hero. And when the next project rolls around you just need to send it to them as an H.264 or even a .mkv and you're done.
There are some codecs you can install or have them install here and try your luck with if they insist on a laptop. Up to you.
QuickTime 7.6 supports these formats.
Just keep repeating this bit from Apple over and over to yourself:
We strive to ensure backward compatibility with content created with older versions of QuickTime. In fact, movies created with QuickTime 1 still play today in QuickTime 7.
Then FedEx them at least two copies or upload it to someplace like Filedropper.com or filemail.com (because they won't have an FTP server or it'll be down or they won't know the password) or send a FAT-32 formatted flashdrive and unplug your phone. Do not send them the codecs that come with Final Cut Studio. Seriously. Charge them for transcoding instead, silly.
Labels:
clients,
exporting,
hi-def,
quicktime,
transcoding
Wednesday, December 30, 2009
Smoothcam Bug in FCP7?
Some people are finding that smoothcam when exported from FCP 7 doesn't export as seen in the viewer or canvas.
A friend just ran into this issue and is now reverting back to FCP 6 and then Leopard (10.5.x) to see which causes the problem if either.
A friend just ran into this issue and is now reverting back to FCP 6 and then Leopard (10.5.x) to see which causes the problem if either.
Thursday, November 26, 2009
Free Tool for Matroska Files
Matroska files are becoming more and more popular. What is it?
The Matroska Multimedia Container is an open standard free container format, a file format that can hold an unlimited number of video, audio, picture or subtitle tracks inside a single file.[1] It is intended to serve as a universal format for storing common multimedia content, like movies or TV shows. Matroska is similar in concept to other containers like AVI, MP4 or ASF, but is entirely open in specification, with implementations consisting mostly of open source software. Matroska file types are .MKV for video (with subtitles and audio), .MKA for audio-only files and .MKS for subtitles only.
I'm a fan of open standards and in my other life I use Ubuntu a lot for this reason. So if your client asks for an .mkv file or you need to monkey with them MKVToolnix, a FREE app to deal with Matroska files may be of some help.
Labels:
.mkv,
encoding,
exporting,
handy software,
matroska,
transcoding
Sunday, May 24, 2009
VisualHub Can't Convert .flv Anymore?


A client has handed you (meaning you've used Command + Option + A in Safari to open the Activity Window and downloaded that really cool video from YouTube to email your friends) a .flv that they need in some other format for something or other. Opening it in VLC you see that it's h264/mp4a and VisualHub begets you an error like "Cannot allocate temp picture, check pix fmt"
What do you do? Well, you can try altering the Decoding parameter in VisualHub to be QuickTime or ffmpeg or whatever but your luck will vary. It may just work, or need Perian or may never work. flvs are fussy like that.
Even the power of QuickTime alone won't do it; you need 3x the transcoding power.
A) Install Perian
B) Install MPEG Streamclip.
C) Launch MPEG Streamclip and drag your fussy .flv into it.
D) Export it to H.264 (QuickTime) or the codec of your choice.
See, QuickTime + Perian will PLAY the .flv but when you export it it'll likely be MOS (Mit Out Sound). But, opening it with the power of Perian plus exporting it with the power of MPEG Streamclip will result in a transcoded file with audio.
Yup. You didn't even have to restart :) The only downside is that the resultant file will be 60-70% larger than the original .flv but monkey with the settings in MPEG Streamclip and you can bring that down significantly without very much of a loss in quality at all. The first thing to change is the Data Rate with a lower kbits/s. Also, unless you need really high quality audio, try lowering the audio to 22.050 kHz.
Great, thanks, Mr. Not Bruce, but how do I delete these two apps now?
From Perian's site:
How do I remove Perian?
Open the System Preferences. Select the Perian pane and 'Remove.' Now 'Show All' preference panes, control-click the Perian pane and 'Remove "Perian" Preference Pane.
As for MPEG Streamclip...just drag it to the trash.
Labels:
exporting,
flv,
handy software,
mpeg streamclip,
Perian,
safari,
transcoding,
visualhub,
vlc
Monday, April 20, 2009
FCP Knowledge Base Updates
Troubleshooting Basics
Green frames or other anomalies on render with REDCODE
Quality issue with movies you export from the Viewer with filters applied
Log and capture with DV50 sometimes does not work in French or Japanese
Speed interferes with Smooth Cam
Some imported PSD files may only contain the background layer
Motion quits unexpectedly when exporting to REDCODE
Compressor Troubleshooting Basics
Green frames or other anomalies on render with REDCODE
Quality issue with movies you export from the Viewer with filters applied
Log and capture with DV50 sometimes does not work in French or Japanese
Speed interferes with Smooth Cam
Some imported PSD files may only contain the background layer
Motion quits unexpectedly when exporting to REDCODE
Compressor Troubleshooting Basics
Labels:
compressor,
exporting,
fcp,
knowledge base,
log and capture,
motion,
photoshop,
redcode,
troubleshooting
Monday, March 9, 2009
How to keep HD Aspect Ratios when exporting to SD
Apple updated a little article today called "How to maintain aspect ratio when exporting high definition formats to standard definition".
It helps you figure out how to export an HD project to an SD file and still maintain it's proper aspect ratio. It basically says use a Reference Movie for non-IMX formats and create a new preset for IMX exports.
It helps you figure out how to export an HD project to an SD file and still maintain it's proper aspect ratio. It basically says use a Reference Movie for non-IMX formats and create a new preset for IMX exports.
Friday, February 20, 2009
Exports From FCP Fail in QuickClusters
Surprise! From Apple's TA1099 Knowledge Base article.
You will not be able to successfully export from Final Cut Pro using Compressor if your computer is set up as a Compressor QuickCluster, or a "Virtual Cluster." If you attempt to send an item from Final Cut Pro to Compressor in such a case, some segments in the job may report "Failed" and processing of the batch will not complete successfully.
What can you do?
You can work around this issue by first exporting a self-contained movie from Final Cut Pro. You can then use a QuickCluster in Compressor to transcode that self-contained movie.
Alternately, you can export from Final Cut Pro directly using Compressor, but use a single-service instance of Compressor instead of a QuickCluster.
You will not be able to successfully export from Final Cut Pro using Compressor if your computer is set up as a Compressor QuickCluster, or a "Virtual Cluster." If you attempt to send an item from Final Cut Pro to Compressor in such a case, some segments in the job may report "Failed" and processing of the batch will not complete successfully.
What can you do?
You can work around this issue by first exporting a self-contained movie from Final Cut Pro. You can then use a QuickCluster in Compressor to transcode that self-contained movie.
Alternately, you can export from Final Cut Pro directly using Compressor, but use a single-service instance of Compressor instead of a QuickCluster.
Labels:
compressor,
exporting,
knowledge base,
quickclusters
Wednesday, September 24, 2008
My 16:9 DV Exports Are Squeezed!

When you bring 16x9 DV footage into FCP it loads it as 720x480 pretty much no matter what. So when you export your timeline with a quick Export To Quicktime Movie you end up with your 16x9 footage squeezed into a 4x3 space. Why? Blame all this non-standardness mess. So, how do you fix it?
First off don't Export To Quicktime Movie, instead use Export Using Quicktime Conversion.
Btw, I've assigned Command + E to "Export To Quicktime Movie" and Shift + Command + E to "Export Using Quicktime Conversion" because I can.
In Final Cut:
01) Make sure the thing you want to export is active (ie..timeline, sequence, viewer...)
02) In the menubar goto File>Export>Export Using Quicktime Conversion.
03) In the Save window that pops up hit Options.
04) In the next window, called Movie Settings, hit Settings under Video.
05) In the next window, called Standard Video Compression Settings (I think), under Compression Type select DV/DVCPRO - NTSC.
06) Then, in that same window at the bottom left set Aspect Ratio to 16:9. The rest of the settings are up to you but I like to choose Progressive and Best quality under the Compressor setting.
07) Hit Ok, hit Ok then hit save (after you make sure it's going to save it where you want it.
Done. Your footage will play back at 853x480 in a nice widescreen QT window. Yays!
Subscribe to:
Posts (Atom)
