Michael Cinquin has a pretty amazing page with some handy FREE online tools that you may want to bookmark.
I'm on the road (again) and needed to convert a .srt subtitle file to .stl and his online converter worked beautifully.
Check it out and see if anything is helpful to you and drop him a thank you note if you have the time.
There is help for Final Cut Pro, RedCode, Conforming sounds, Subtitles...and lots more.
Saturday, April 14, 2012
Tuesday, April 10, 2012
Quick Access to Audio Inputs and Outputs
Often I use a USB microphone for quick Voice Overs (for timing) and when I'm on the road I tend to just hook up my Zoom H4N to the laptop and record comments and VO's using it directly into FCP or Quicktime 7.
If you hold down Option while clicking on the volume adjustment menubar item you'll see this:
Instead of the normal volume slider. This is a quick way to access these common settings and get to the the Sound Preferences.
Bonus Tip:
Hitting Option + Volume Up or Down will also take you directly to the Sound panel in Settings.
If you hold down Option while clicking on the volume adjustment menubar item you'll see this:
Instead of the normal volume slider. This is a quick way to access these common settings and get to the the Sound Preferences.
Bonus Tip:
Hitting Option + Volume Up or Down will also take you directly to the Sound panel in Settings.
Wednesday, April 4, 2012
Fixing Camera Bobbles
Let's say you have some footage that's supposed to be a lock-off but somewhere during the filming the camera gets nudged, or bumped or slowly drifts due to a loose lockdown or a sleepy operator.
If it's a short clip and you can't really use smoothcam or some other image stabilization software due to them digitally zooming in I'll do this:
1. Download and install the plugin "DH Grid" from here.
2. Layer that atop the less-than-smooth footage.
3. Resize and reposition the DH Grid overlay so it's grid aligns with a portion of the image that you want to stay where it is.
4. Set a Center keyframe in the Motion tab of the clip.
5. Now using the JKL keys, advance frame-by-frame (or small groups of frames) and Nudge the footage up, down, left and right as needed using the grid to keep it in place.
One great way to do this is to use the little known Nudge key commands in FCP: Option + Arrow Keys. It'll help if you have the Canvas set to Image + Wireframe and you must have the clip you're nudging highlighted in the Timeline.
If you want to nudge a really really tiny amount use Command + Option + Arrow Keys. Depending on how zoomed in you are -or aren't- in the Canvas you may need to zoom in to see these tiny adjustments.
6. Each time you nudge the clip on a particular frame you'll automatically set a keyframe.
7. Render and see how badly you messed up :) Don't worry, it's hard to get it right the first time. And the human eye/mind is so used to seeing movement that is natural, that unnatural movement will seem quite obvious.
Scoot back to the problem frames and adjust them as needed, render, wash, rinse and repeat.
Be aware though that if you've fixed a particularly nasty bobble, you're first inclination after making all these keyframes is to zoom the clip or reposition it (since the bottom or sides or top may be cut off).
DON'T.
If you move the clip now you'll set another Center keyframe and mess things up.
Instead, use this little-known key command: Hold Command + Shift and move the clip in the Canvas. Command + Shift will move the clip AND THE KEYFRAMES en masse without setting any new keyframes. Nifty, eh?
If it's a short clip and you can't really use smoothcam or some other image stabilization software due to them digitally zooming in I'll do this:
1. Download and install the plugin "DH Grid" from here.
2. Layer that atop the less-than-smooth footage.
3. Resize and reposition the DH Grid overlay so it's grid aligns with a portion of the image that you want to stay where it is.
4. Set a Center keyframe in the Motion tab of the clip.
5. Now using the JKL keys, advance frame-by-frame (or small groups of frames) and Nudge the footage up, down, left and right as needed using the grid to keep it in place.
One great way to do this is to use the little known Nudge key commands in FCP: Option + Arrow Keys. It'll help if you have the Canvas set to Image + Wireframe and you must have the clip you're nudging highlighted in the Timeline.
If you want to nudge a really really tiny amount use Command + Option + Arrow Keys. Depending on how zoomed in you are -or aren't- in the Canvas you may need to zoom in to see these tiny adjustments.
6. Each time you nudge the clip on a particular frame you'll automatically set a keyframe.
7. Render and see how badly you messed up :) Don't worry, it's hard to get it right the first time. And the human eye/mind is so used to seeing movement that is natural, that unnatural movement will seem quite obvious.
Scoot back to the problem frames and adjust them as needed, render, wash, rinse and repeat.
Be aware though that if you've fixed a particularly nasty bobble, you're first inclination after making all these keyframes is to zoom the clip or reposition it (since the bottom or sides or top may be cut off).
DON'T.
If you move the clip now you'll set another Center keyframe and mess things up.
Instead, use this little-known key command: Hold Command + Shift and move the clip in the Canvas. Command + Shift will move the clip AND THE KEYFRAMES en masse without setting any new keyframes. Nifty, eh?
Tuesday, March 6, 2012
Pasting Negative Infinity
In the Level setting for audio in the Viewer you can type in all sorts of values to change the level of your audio. But you really can't type in "-inf" if you want the audio from certain channels gone completely while you monitor playback.
But you can drag the slider all the way to the left to "-inf", then highlight and copy (Command + C) then while it's on your clipboard you can paste it (Command+V) into other clip's channel's level settings.
When you paste it into a Textedit document set to plain text, you'll even see that it's "-inf", yet you can't type letters into this box in Final Cut Pro. Weird.
But you can drag the slider all the way to the left to "-inf", then highlight and copy (Command + C) then while it's on your clipboard you can paste it (Command+V) into other clip's channel's level settings.
When you paste it into a Textedit document set to plain text, you'll even see that it's "-inf", yet you can't type letters into this box in Final Cut Pro. Weird.
 |
| Copy Negative Infinity, then Paste Negative Infinity in spite of ram limitations! |
Wednesday, February 29, 2012
Box.net Corrupted File Warning
I'm not sure of the parameters of this one but it seems that if you upload a .NEF (Nikon Electronic Format) to a box.net account and then download it, it sometimes gets corrupted. I noticed this on a client's machine after they placed roughly ten .NEF files in their account and all of them ended up with a Segmentation Fault: "(com.apple.finder[409]) Job appears to have crashed: Segmentation Fault" and Finder crash-relaunch on Snow Leopard, by -and get this- just highlighting a .NEF and hitting Command + I (Get Info) in the Finder.
I tried getting screengrabs of the effect but wasn't able to. But I did manage to get a quick snapshot with the client's phone:
What I saw was the Get Info window zooming out quite choppily leaving echoed windows on the screen, then the actual Get Info window was shifted down leaving blank white space above it while it shuddered slightly up and down before the Finder gave up and relaunched.
Playing around with this I had the client zip an individual .NEF, upload it to Box.net, then downloaded it on another machine and tried Get Info after unzipping it. Everything was fine.
I'm not sure where the problem lay but it smells of the old losing-the-resource-fork file problem of the days of yore.
The solution was to just zip the files and then upload, then download them.
I tried getting screengrabs of the effect but wasn't able to. But I did manage to get a quick snapshot with the client's phone:
 |
| It's kinda like an Ib Melchior movie. |
What I saw was the Get Info window zooming out quite choppily leaving echoed windows on the screen, then the actual Get Info window was shifted down leaving blank white space above it while it shuddered slightly up and down before the Finder gave up and relaunched.
Playing around with this I had the client zip an individual .NEF, upload it to Box.net, then downloaded it on another machine and tried Get Info after unzipping it. Everything was fine.
I'm not sure where the problem lay but it smells of the old losing-the-resource-fork file problem of the days of yore.
The solution was to just zip the files and then upload, then download them.
Sunday, February 5, 2012
Fixing the RT Still Cache is full error message
I mentioned it briefly here but here's how to do something about it.
First off you'll see something like this in FCP 6/7 if you hover over the render indicator in the Timeline:
If you read the entire message you'll see you need to look here:
Where it reads "Thumbnail Cache" just bump up the Disk and or RAM setting a bit to cover the amount of images you're using in the current project to eliminate the warning, and help FCP a little bit with rendering all those stills.
I've left mine bumped up over the years as projects have caused the warning and left it with no ill effects. You'd think this would be dynamic after all this time but then again, OS 9 had separate application memory allotment settings in the old Get Info window.
First off you'll see something like this in FCP 6/7 if you hover over the render indicator in the Timeline:
 |
| Actually, the solution is mentioned right there. |
If you read the entire message you'll see you need to look here:
Where it reads "Thumbnail Cache" just bump up the Disk and or RAM setting a bit to cover the amount of images you're using in the current project to eliminate the warning, and help FCP a little bit with rendering all those stills.
I've left mine bumped up over the years as projects have caused the warning and left it with no ill effects. You'd think this would be dynamic after all this time but then again, OS 9 had separate application memory allotment settings in the old Get Info window.
Tuesday, January 31, 2012
Convert Final Cut Pro 7 projects to Final Cut Pro X
There's a $10 app called 7toX [app store link] that claims to convert Final Cut Pro 7's project files to Final Cut Pro X.
"7toX for Final Cut Pro brings your Final Cut Pro 7 projects forward to Final Cut Pro X so you can use Apple’s powerful new professional editing tools to update or finish your older projects. The lightweight application is simple to use, with drag-and-drop support and progress information. 7toX translates important metadata from your Final Cut Pro 7 Project — including bins, clips and sequences — to a new Event in Final Cut Pro X with the highest fidelity of any translation application for Final Cut Pro. In addition, the application provides clear, detailed reporting after every transfer. "
I haven't had much time to play with it but I'll be looking into it more this week and beyond to see how it fares. I wonder why Apple didn't release an app like this or build something like this into FCPX, even as a "beta" feature.
Had Apple integrated this (as a big red flag warning-ized "beta" feature) and waited until Photoshop Layer import, broadcast monitoring and Multicam editing were ready I believe the adoption rate for FCPX would have been MUCH higher and the bad press would have been MUCH lower. Heck, they may have even had Mac Towers still on display in all of their stores. (meaning, today some Apple stores don't have Mac Towers on display anymore...I know!)
"7toX for Final Cut Pro brings your Final Cut Pro 7 projects forward to Final Cut Pro X so you can use Apple’s powerful new professional editing tools to update or finish your older projects. The lightweight application is simple to use, with drag-and-drop support and progress information. 7toX translates important metadata from your Final Cut Pro 7 Project — including bins, clips and sequences — to a new Event in Final Cut Pro X with the highest fidelity of any translation application for Final Cut Pro. In addition, the application provides clear, detailed reporting after every transfer. "
I haven't had much time to play with it but I'll be looking into it more this week and beyond to see how it fares. I wonder why Apple didn't release an app like this or build something like this into FCPX, even as a "beta" feature.
Had Apple integrated this (as a big red flag warning-ized "beta" feature) and waited until Photoshop Layer import, broadcast monitoring and Multicam editing were ready I believe the adoption rate for FCPX would have been MUCH higher and the bad press would have been MUCH lower. Heck, they may have even had Mac Towers still on display in all of their stores. (meaning, today some Apple stores don't have Mac Towers on display anymore...I know!)
FCPX gets Multicam Editing...finally
Apple has finally updated FCPX with a feature it should have had when launched: multicam editing. And to Apple's credit it now supports 64 streams. They also thought it was time to let FCPX import layered Photoshop files and allow Broadcast monitoring.
How long did that take? And why?
I wonder then how many companies and editors who bought Premiere will even notice given that the gap between launching FCPX without these features and then including them in an update was about seven months.
Some interesting bits:
- Multicam will sync clips based on audio.
- Broadcast Monitoring (technically a beta feature as of this post) requires a PCIe equipped Mac or Thunderbolt.
Compressor and Motion both get some minor updates as well.
How long did that take? And why?
I wonder then how many companies and editors who bought Premiere will even notice given that the gap between launching FCPX without these features and then including them in an update was about seven months.
Some interesting bits:
- Multicam will sync clips based on audio.
- Broadcast Monitoring (technically a beta feature as of this post) requires a PCIe equipped Mac or Thunderbolt.
Compressor and Motion both get some minor updates as well.
Thursday, January 19, 2012
Importing PDF files into Final Cut Pro
Today I was handed a 100+ page PDF to use in a FCP project. The problem is that FCP doesn't really like .PDF's all that much and if you drag a multi-page PDF into FCP you'll get a short clip that will essentially have each page as a frame. Not terribly useful unless that's what you'd like to see when you hit play.
Here are a few ways to get decent results without too much trouble using stuff you likely already have.
01. Open the PDF in Preview.
02. Hit Shift + Command + D to see the sidebar if it's not already open.
03. Hit Option + Command + 2 to see a long list of Thumbnails. Scroll down to the page you want to use in FCP.
Alternatively, if you know the page number of the page you want hit Option + Command + G to bring down the Go To Page text entry box, enter the page number and hit OK. The reason this may not be the best way is that some PDFs numbering schemes are off by a number or two, at least in the few that I've been given to use in FCP: ie.. Page 43 in the thumbnails is actually Page 42 as shown on the PDF.
04. Hit Command + Shift + S for Save As...
05. When the Save As sheet drops down select JPEG for the Format Pull-Down (you can also choose TIFF if you'd like to).
06. Set the Quality Slider to "Best"
07. For Resolution it will likely default to 150 pixels/inch. This should be okay for most situations, but you can bump it up higher if you'd like. I didn't notice too much of a difference between 150 and 300.
08. Tell it where you want to save the file and hit Save.
09. Import the file you just made into FCP.
10. Bring the .jpg or .tiff into the Timeline and Scale it if needed then render.
I've have acceptable results for corporate junk using this method. It's not the best quality but good enough for company work.
01. Open the PDF in Preview.
Here are a few ways to get decent results without too much trouble using stuff you likely already have.
METHOD #01
(Save As... in Preview, better for high-quality requirements like text)01. Open the PDF in Preview.
02. Hit Shift + Command + D to see the sidebar if it's not already open.
03. Hit Option + Command + 2 to see a long list of Thumbnails. Scroll down to the page you want to use in FCP.
Alternatively, if you know the page number of the page you want hit Option + Command + G to bring down the Go To Page text entry box, enter the page number and hit OK. The reason this may not be the best way is that some PDFs numbering schemes are off by a number or two, at least in the few that I've been given to use in FCP: ie.. Page 43 in the thumbnails is actually Page 42 as shown on the PDF.
04. Hit Command + Shift + S for Save As...
05. When the Save As sheet drops down select JPEG for the Format Pull-Down (you can also choose TIFF if you'd like to).
06. Set the Quality Slider to "Best"
07. For Resolution it will likely default to 150 pixels/inch. This should be okay for most situations, but you can bump it up higher if you'd like. I didn't notice too much of a difference between 150 and 300.
08. Tell it where you want to save the file and hit Save.
09. Import the file you just made into FCP.
10. Bring the .jpg or .tiff into the Timeline and Scale it if needed then render.
I've have acceptable results for corporate junk using this method. It's not the best quality but good enough for company work.
METHOD #02
(Dragging out a separate .PDF page)01. Open the PDF in Preview.
02. Hit Shift + Command + D to see the sidebar if it's not already open.
03. Hit Option + Command + 2 to see a long list of Thumbnails. Scroll down to the page you want to use in FCP.
04. Find the page you want and then drag the thumbnail in the sidebar to the Desktop or folder where you want it to go.
This will create a new PDF of just that single page.
05. Import the file you just made into FCP.
06. Bring the .pdf into the Timeline and Scale it if needed then render.
The results won't be perfect but good enough for some projects.
METHOD #03
(Making each page a separate image file. Read the Warning about this!)If you need each page in the PDF as a separate image file here's one quick and dirty way:
01. Open the PDF in Preview.
02. Hit Command + P for Print...
03. After the Print sheet drops down hit the PDF button at the bottom left.
04. Select either "Save PDF to Folder as JPEG" or Save PDF to Folder as TIFF"
WARNING!
Be aware though that when I do this there is no sheet asking where to save the files. For me, and maybe this is some kind of bizarre bug or me doing something wrong, it saved the individual pages as images files in my "-Tmp-" folder, which is inside an invisible folder (not meaning Lion's crazy invisible user folder madness).
Wednesday, January 11, 2012
How to convert a single audio file to separate ones with a .cue file
A client sent me a link to their FTP server of a VO for a project I'm cutting. It turns out that whatever place they used to record the VO, I guess, just left their equipment recording while the VO talent read the script.
Meaning, it's one giant 400 MB .Flac file.
A, why they sent it as a .Flac file is beyond me.
B, why it's one large file is equally beyond me other than they literally never hit pause during the entire recording session, which is exactly what it sounds like they did.
Hearing the client "direct" the professional voice over talent is priceless btw…
But, at least they provided a .cue file.
Seriously. I know.
So my task was to either complain and loose my job and sanity -imagine trying to explain .flac, .mp3 and .cue files to a client- or just find a way to break them up myself.
One solution would be to dump the audio into Final Cut and just Control + V at all the gaps or actually listen to it all and copy paste into new timelines or make subclips or something else equally archaic. Another way was to use an app to cut the audio when it encounters silence but that would likely lead to it cutting at pauses in long sentences.
It turns out it's easier than I had thought. First off Toast won't due it easily (if at all) which was my first thought and attempt. I didn't make much progress with it -it seems the more Toast is updated the more confused it becomes as to what it's main function is- but I did remember a cool little free app called Max that I had used a long time ago so I did what I usually do when awakening an old app…look for any updates first.
Looking at some software sites I saw that Max hadn't been updated in a while but as a "related" search item I saw the FREE app XLD which is an acronym for "X Lossless Decoder" which I knew of but never had much use for outside of the odd conversion.
Now, while Max would likely work I decided to try XLD because it was more recently updated, by a lot.
What you need to do to break up a single file into separate audio files using a provided .cue file (technically you could make your own) is this:
1. Drag your .cue file onto XLD. It'll launch.
2. After XLD's window appears look at the left column. There you'll see the main recording. Make sure it's highlighted and active and you'll see the list of individual tracks on the right in the main window.
3. Hit Command + Comma for XLD's preferences.
4. In the Preferences window select the Output Format you want (double check the Options button if you need precise control of the output format, say for like a TV station or something), then set the Output Directory to where ever you'd like it. You can also set things like the format of the file name and the Maximum number of Threads here. Close the Preferences window.
5. Back in the main window hit the Transcode button and away you go.
Meaning, it's one giant 400 MB .Flac file.
A, why they sent it as a .Flac file is beyond me.
B, why it's one large file is equally beyond me other than they literally never hit pause during the entire recording session, which is exactly what it sounds like they did.
Hearing the client "direct" the professional voice over talent is priceless btw…
But, at least they provided a .cue file.
Seriously. I know.
So my task was to either complain and loose my job and sanity -imagine trying to explain .flac, .mp3 and .cue files to a client- or just find a way to break them up myself.
One solution would be to dump the audio into Final Cut and just Control + V at all the gaps or actually listen to it all and copy paste into new timelines or make subclips or something else equally archaic. Another way was to use an app to cut the audio when it encounters silence but that would likely lead to it cutting at pauses in long sentences.
It turns out it's easier than I had thought. First off Toast won't due it easily (if at all) which was my first thought and attempt. I didn't make much progress with it -it seems the more Toast is updated the more confused it becomes as to what it's main function is- but I did remember a cool little free app called Max that I had used a long time ago so I did what I usually do when awakening an old app…look for any updates first.
Looking at some software sites I saw that Max hadn't been updated in a while but as a "related" search item I saw the FREE app XLD which is an acronym for "X Lossless Decoder" which I knew of but never had much use for outside of the odd conversion.
Now, while Max would likely work I decided to try XLD because it was more recently updated, by a lot.
What you need to do to break up a single file into separate audio files using a provided .cue file (technically you could make your own) is this:
1. Drag your .cue file onto XLD. It'll launch.
2. After XLD's window appears look at the left column. There you'll see the main recording. Make sure it's highlighted and active and you'll see the list of individual tracks on the right in the main window.
3. Hit Command + Comma for XLD's preferences.
4. In the Preferences window select the Output Format you want (double check the Options button if you need precise control of the output format, say for like a TV station or something), then set the Output Directory to where ever you'd like it. You can also set things like the format of the file name and the Maximum number of Threads here. Close the Preferences window.
5. Back in the main window hit the Transcode button and away you go.
Subscribe to:
Posts (Atom)
Posts
