I've run into this a few times. The solution turns out, while simple, is completely non-intuitive.
The problem:
You've connected a client's phone to pull off all the "tons of absolutely great" videos and photos they've taken to "help" with the project. And you, being the editor kinda-sorta have to use them because heck, the client themselves took them just for you for their project.
You connect their phone (or iPad or whatever) to your Mac via the cable and launch Image Capture and nothing shows up. Both the Mac and the phone just sit there. Wonderful.
The solution:
Launch iTunes.
Yep. It'll ask if you want to access the connected device. Hit "Trust" on the phone and they'll show up after a few seconds in Image Capture and you can just highlight them all and drag them off and "forget" to use them later on because they're useless and blurry and shaky.
ProTip:
If you want to "untrust" the phone on your computer or they insist they do (Security! they say, "It's the business phone and our IT guys need it to be secure.") what I think you do, is this mess:
Reset the Lockdown Folder.
Yes. Hard as it is to believe that's how it's done.
If you just want to Untrust the phone you just trusted just now, open the Lockdown Folder and then sort by date created and delete the most recent one.
Showing posts with label import. Show all posts
Showing posts with label import. Show all posts
Saturday, June 21, 2014
Monday, March 24, 2014
Can't Open a PowerPoint to Import into FCP
I ran across this today and the fix is simple.
I have a powerpoint that's a .pptx PowerPoint file. That means it was created in PowerPoint 2007 or later. Now, .ppt is for earlier versions than I think 2007. A client sent me a link to a PowerPoint that was to be used in an edit and for some reason QuickView nor Keynote could open it. Keynote threw out an "Import Error".
I then noticed that the file was filename.pptx.ppt when it should have just been .pptx. Somehow the download service that they used to send me the file for some reason appended on .ppt to the file.
Changing the file from .pptx.ppt to it's original .pptx file extension solved the problem of opening it in Keynote.
I have a powerpoint that's a .pptx PowerPoint file. That means it was created in PowerPoint 2007 or later. Now, .ppt is for earlier versions than I think 2007. A client sent me a link to a PowerPoint that was to be used in an edit and for some reason QuickView nor Keynote could open it. Keynote threw out an "Import Error".
I then noticed that the file was filename.pptx.ppt when it should have just been .pptx. Somehow the download service that they used to send me the file for some reason appended on .ppt to the file.
Changing the file from .pptx.ppt to it's original .pptx file extension solved the problem of opening it in Keynote.
Friday, July 5, 2013
Using .EPS files in Final Cut Pro
A client sent me a slew of images the other day and some were CMYK while others were RGB, yet most were .eps files despite me requesting that they send them as RGB .jpg or .tiff to save time (ermagerd duh deadlinez!) [This is the same client who thought we'd edit the video over the course of a normal workday...day...as in single 8 hour day even though we'd shot for over two full days weeks earlier and I still had no script so no VO]
FCP prefers images to be RGB so I had to convert the CMYK ones in Photoshop (or Pixelmator) but since these were .eps files I had to save them as .Jpgs or .tiffs or something. For some reason some clients really really insist on .tiffs in video projects "They're uncompressed!" they'll tell me. Depending on my mood I'll correct them or just plod along mindless nodding.
Anywho, when you open a .eps file in PS you'll see something like this:
I changed it to something like this:
FCP prefers images to be RGB so I had to convert the CMYK ones in Photoshop (or Pixelmator) but since these were .eps files I had to save them as .Jpgs or .tiffs or something. For some reason some clients really really insist on .tiffs in video projects "They're uncompressed!" they'll tell me. Depending on my mood I'll correct them or just plod along mindless nodding.
Anywho, when you open a .eps file in PS you'll see something like this:
I changed it to something like this:
Since it's a .eps file you can bump up it's resolution while you're here and have something nice a big and hi-res to work with in FCP. Just save it out as a .jpg or if the client is particularly persnickety a .tiff, dump it into FCP and be on your way.
Labels:
.eps,
cmyk,
fcp,
import,
photos,
photoshop,
pixelmator,
resolution,
rgb
Tuesday, June 28, 2011
Final Cut Pro X Can Almost Import Final Cut Pro XML Projects
MacMagazine has discovered [google translation link] that the ability to import a Final Cut Pro XML file is kinda sorta already in Final Cut X but isn't working. Either it's going to be implemented in an update or will work in tandem with a stand-alone app that converts Final Cut Pro XML into something Final Cut X can import.
Either way, there's a little teeny tiny bit of hope.
Either way, there's a little teeny tiny bit of hope.
Tuesday, October 26, 2010
Ripping Sections of DVDs with Free Stuff
I've been working on a monster of a documentary and some of the footage is showing up on DVDs despite what I've been telling sources and clients. I am typing this in english right?
So here's my (free) workflow for ripping portions of source DVDs to extract the bits of footage that's needed for this project.
You'll need:
MPEG Streamclip
Perian
Optional:
Fairmount
I'm avoiding using Cinematize Pro because, frankly, it's old. I think the last update was something like two years ago. Ok, here we go...
0) Optionally, use Fairmount to copy the DVD's VIDEO_TS to your hard drive. (I'll let you figure this one out on your own but it's of Very Low Complexity)
1) Open up the VIDEO_TS folder and start looking at the .VOB files until you find the one with the clip you need. With Perian, you can open them up in Quicktime Player 7 (which I like to call Quicktime That Doesn't Suck).
2. Make notes of which .VOB files you need and then open them up with MPEG Streamclip. Why not open then with MPEG Streamclip right away? It's your choice but I feel that Quicktime is faster for previewing.
Oh, Quicktime will likely be unable to play the audio since they're MUXed files so if audio is important head straight to MPEG Streamclip here. I should have told you that earlier.
Now, when you open a .VOB file with MPEG Streamclip you may (probably will) see this:
Since the purpose of this post is to just get sections of .VOB files and not the entire file hit "Open 1 file".
3) Now, set In and Out points in MPEG Streamclip using the I and O keys. How about that?
4) Under File in MPEG Streamclip select "Export to Quicktime..." and choose your poison. I like ProRes but select whatever you want. Hit "Make Movie" and grab a sip of coffee.
5) There is no step 5. Hah!
So here's my (free) workflow for ripping portions of source DVDs to extract the bits of footage that's needed for this project.
You'll need:
MPEG Streamclip
Perian
Optional:
Fairmount
I'm avoiding using Cinematize Pro because, frankly, it's old. I think the last update was something like two years ago. Ok, here we go...
0) Optionally, use Fairmount to copy the DVD's VIDEO_TS to your hard drive. (I'll let you figure this one out on your own but it's of Very Low Complexity)
1) Open up the VIDEO_TS folder and start looking at the .VOB files until you find the one with the clip you need. With Perian, you can open them up in Quicktime Player 7 (which I like to call Quicktime That Doesn't Suck).
2. Make notes of which .VOB files you need and then open them up with MPEG Streamclip. Why not open then with MPEG Streamclip right away? It's your choice but I feel that Quicktime is faster for previewing.
Oh, Quicktime will likely be unable to play the audio since they're MUXed files so if audio is important head straight to MPEG Streamclip here. I should have told you that earlier.
Now, when you open a .VOB file with MPEG Streamclip you may (probably will) see this:
Since the purpose of this post is to just get sections of .VOB files and not the entire file hit "Open 1 file".
3) Now, set In and Out points in MPEG Streamclip using the I and O keys. How about that?
4) Under File in MPEG Streamclip select "Export to Quicktime..." and choose your poison. I like ProRes but select whatever you want. Hit "Make Movie" and grab a sip of coffee.
5) There is no step 5. Hah!
Labels:
CD/DVD,
handy software,
import,
ripping,
transcoding
Saturday, June 26, 2010
Importing Apple Pages scripts into Celtx
A client handed me a script (screenplay format, not two column AV, thankfully) that they had written in Apple Pages which is all well and good but the AD needs it in Celtx for whatever she's going to do with it.
Now, I love Celtx because it's simple, feature-rich and FREE (for most of it). And I have no problem with Pages myself; I use it nearly every day but getting something from Pages into Celtx and retaining all the formatting was a challenge.
There's a help page about precisely this here. See Celtx only imports plain text files and formats them as long as certain conventions are in the text file. So you'd think it's as easy as exporting the screenplay in Pages to a text file and then importing it into Celtx. Nope. Course not, silly.
See for some reason completely lost to me Pages does export Scene Headers (Slug Lines) as all capitals even though they're all capitals in the Pages document. I know. Maybe the original author messed something up, I dunno. Even copy and paste will not retain the all caps scene headers even if you paste it into a rich text document or a plain text one in SimpleTex...I mean TextEdit.
So to workaround this issue I did this:
0. Remove all pages numbers from pages and all Headers and Footers (use the Inspector Window)
1. In Pages export the script as a PDF file. File > Export >PDF
2. Open that PDF in Preview. (Scene Headers should still be in all caps)
3. Copy the text beginning with the FIRST INT. or EXT. (ignore the title page and anything before this) by selecting (dragging) from the first INT. or EXT. to some other text then hitting the End key to move to the end of the script and while HOLDING SHIFT click at the end of the script. It should all be highlighted now.
Be SURE that the highlight is from the very first INT. or EXT. till the end. For me it kept auto-annoyingly selecting a "FADE IN:" at the beginning but we'll deal with that in a 'mo.
4. Hit COMMAND+C to Copy.
5. Launch TextEdit and make sure it's set to Plain Text format. (Format > Make Plain Text)
6. Paste the clipboard's contents into the plain text document. COMMAND + V.
For me the FADE IN: that was highlighted when I did the copy wasn't pasted in. Weird. Double check the beginning of the script to make sure (again) that it begins with either EXT. or INT. Also double check to make sure that character names for their dialog are in all caps as well. Celtx uses these things to format the script and tell what's from what.
7. Save. COMMAND + S
8. Do this:
Then Save.
9. Launch Celtx
10. Create a new "Film" project.
11. Select Script > Import Script from the menubar.
IT WILL NOT BE PERFECT. But it'll be close. I couldn't find a way to get it to import the script with 100% perfect formatting. The AD will go through and clean it up but for now, on short notice, this is the best I could come up with.
Anyone have any tips or suggestions?
Now, I love Celtx because it's simple, feature-rich and FREE (for most of it). And I have no problem with Pages myself; I use it nearly every day but getting something from Pages into Celtx and retaining all the formatting was a challenge.
There's a help page about precisely this here. See Celtx only imports plain text files and formats them as long as certain conventions are in the text file. So you'd think it's as easy as exporting the screenplay in Pages to a text file and then importing it into Celtx. Nope. Course not, silly.
See for some reason completely lost to me Pages does export Scene Headers (Slug Lines) as all capitals even though they're all capitals in the Pages document. I know. Maybe the original author messed something up, I dunno. Even copy and paste will not retain the all caps scene headers even if you paste it into a rich text document or a plain text one in SimpleTex...I mean TextEdit.
So to workaround this issue I did this:
0. Remove all pages numbers from pages and all Headers and Footers (use the Inspector Window)
1. In Pages export the script as a PDF file. File > Export >PDF
2. Open that PDF in Preview. (Scene Headers should still be in all caps)
3. Copy the text beginning with the FIRST INT. or EXT. (ignore the title page and anything before this) by selecting (dragging) from the first INT. or EXT. to some other text then hitting the End key to move to the end of the script and while HOLDING SHIFT click at the end of the script. It should all be highlighted now.
Be SURE that the highlight is from the very first INT. or EXT. till the end. For me it kept auto-annoyingly selecting a "FADE IN:" at the beginning but we'll deal with that in a 'mo.
4. Hit COMMAND+C to Copy.
5. Launch TextEdit and make sure it's set to Plain Text format. (Format > Make Plain Text)
6. Paste the clipboard's contents into the plain text document. COMMAND + V.
For me the FADE IN: that was highlighted when I did the copy wasn't pasted in. Weird. Double check the beginning of the script to make sure (again) that it begins with either EXT. or INT. Also double check to make sure that character names for their dialog are in all caps as well. Celtx uses these things to format the script and tell what's from what.
7. Save. COMMAND + S
8. Do this:
Importing from Pages for Macintosh
- File->Export using the Plain Text Setting.
- Open in BBedit ( the free version will work)
- Delete all formatting characters at the beginning of the script; there will be some arrows or non alpha characters
- Delete all the lines before the first text characters.
- In BBedit, do Edit->Zap Gremlins, with the non-ASCII set to "Delete"
- Use "Convert to ASCII" ( forget where the menu choice is)
Then Save.
9. Launch Celtx
10. Create a new "Film" project.
11. Select Script > Import Script from the menubar.
IT WILL NOT BE PERFECT. But it'll be close. I couldn't find a way to get it to import the script with 100% perfect formatting. The AD will go through and clean it up but for now, on short notice, this is the best I could come up with.
Anyone have any tips or suggestions?
Friday, December 4, 2009
5DtoFCP
I don't have need of it and can't test it, but I ran across this FREE app listing today.
5DtoFCP - 5DtoFCP is a complete FCS workflow package to get footage from a Canon5DmkII/7D/1D into Final Cut Pro at 25fps. Custom droplets, correctly configured sequence settings and flow chart included to make getting the HD H264 files into FCP easier & quicker.
5DtoFCP - 5DtoFCP is a complete FCS workflow package to get footage from a Canon5DmkII/7D/1D into Final Cut Pro at 25fps. Custom droplets, correctly configured sequence settings and flow chart included to make getting the HD H264 files into FCP easier & quicker.
Monday, March 9, 2009
Super-Quick Way to Import CD (RedBook) Audio
Here's a quick one:
If you need to "rip" some music from a CD a client has burned off as a regular (RedBook) audio CD, don't bother going into iTunes or QuickTime or anything like that. Just pop the CD into the Mac, open it up in the Finder and Drag the audio files to your project's media folder, then load them into FCP.
The process of dragging them from the CD's window in the Finder to your Media folder (or anywhere else) rips them as .AIF files automatically.
If you need to "rip" some music from a CD a client has burned off as a regular (RedBook) audio CD, don't bother going into iTunes or QuickTime or anything like that. Just pop the CD into the Mac, open it up in the Finder and Drag the audio files to your project's media folder, then load them into FCP.
The process of dragging them from the CD's window in the Finder to your Media folder (or anywhere else) rips them as .AIF files automatically.
Wednesday, February 11, 2009
How to open iMovie HD projects in Final Cut Pro

A good friend of mine was working on a project in iMovie HD (iMovie 6.0.3) and because of some hardware issues with his Mac was unable to keep working on it while the Mac was being repaired. So he asked me if I could help him in Final Cut Pro. I don't know iMovie at all. I've never even launched it.
iMovie saves it's projects in a file that looks like a single file but it's actually a folder or package. If you have iMovie installed you can second click on it and "Show Package Contents" where you'll find all the footage and music and so forth.
If you don't have iMovie installed you'll just see the file as a standard folder. Inside the folder you'll see two files ending with ".iMovieProj" and "~.iMovieProj". I think the one with a tilde is a backup or something, I'm not sure.
Anyways, if you drop the .iMovieProj into the terminal under the File command you'll see it's actually "XML 1.0 document text". But FCP can't import it even though it's an XML file. As far as I know iMovie HD doesn't have an option to export a project as a .xml file.
The trick? Make a copy of the .iMovieProj file and rename with .xml appended at the end. Then import it using Final Cut Pro's File > Import >XML... command. You'll have to choose "Show All Files" from the Import window, and then after it imports the .xml file you'll be prompted to save the project as a standard .fcp Project file.
You'll see it churn away for a moment or two, then your iMovie HD project will open as normal in Final Cut Pro. The only drawback is that it's very likely you'll have to render ALL of your audio. And if need be, you can Media Manage the project into a new more organized folder.
IMPORTANT: If using FCP's Import XML command doesn't work and you see an error like "Unable to Open Project File" or something about FCP needing a translation file there's another way to try and open the iMovie HD project's .xml file.
First you MUST keep the .xml file inside the iMovie HD's project folder (or package if you have iMovie HD installed, and by this I mean the iMovie HD's save file which is a hidden package/folder). If it's outside of this folder it will often fail to properly load into FCP.
Second, if importing the .xml file fails via FCP's Import .xml menu, and it's inside the iMovie folder/package, just try double-clicking the .xml file (the one you duplicated and renamed by appending .xml to the end) and it should load that way. Then save it out as a regular .fcp project save file.
Also, and I don't know how helpful this is, not having the .xml file extension hidden but un-ticking the Hide Extension checkbox in the file's Get Info window may help.
I don't know if this trick works with Final Cut Express, however.
Thursday, September 18, 2008
Random Green Frames
I was working on a small 30sec commercial that someone handed off to me which was mainly graphics and VO when I noticed that every time I rendered it a seemingly random and different each time frame was just full screen green.
Usually QuickTime does this when it can "read" a file or codec or something along those lines. Checking the timeline I saw that the background layer, the only thing to go green in a bad way, was a .mpg, specifically MPEG2 Muxed. Quicktime seemed to have an issue with it either rendering in the timeline or exporting to a QT Movie.
So, I tossed the offending .mpg into QT Player, exported it as a DV stream (this wasn't HD, obviously) imported it into FCP and replaced the old .mpg with it in the timeline and all was well after re-rendering and re-exporting.
The lesson here is despite what Apple and the FCP manual's tell you highly compressed codecs aren't the best thing to work with if there is a lesser compressed choice.
Yes yes, I'm aware of generational lossy-ness...
Usually QuickTime does this when it can "read" a file or codec or something along those lines. Checking the timeline I saw that the background layer, the only thing to go green in a bad way, was a .mpg, specifically MPEG2 Muxed. Quicktime seemed to have an issue with it either rendering in the timeline or exporting to a QT Movie.
So, I tossed the offending .mpg into QT Player, exported it as a DV stream (this wasn't HD, obviously) imported it into FCP and replaced the old .mpg with it in the timeline and all was well after re-rendering and re-exporting.
The lesson here is despite what Apple and the FCP manual's tell you highly compressed codecs aren't the best thing to work with if there is a lesser compressed choice.
Yes yes, I'm aware of generational lossy-ness...
Monday, July 28, 2008
P2 Log Pro
P2 Log Pro is an app which:
Sounds neat. A bit redundant, but neat.
can instantly view all formats of native P2 (MXF) video in any format or frame rate. Insert the P2 card into a PowerBook or read it from the camera or FireStore. P2 Log Pro views the card displaying thumbnails, metadata, and links to the video clips. Enter text, sort, re-name, or delete clips. Marks clips to output what you need to Final Cut Pro via XML. Exporting automatically converts MXF clips to HD QuickTime files, ready for editing. With P2 Log Pro, you can also save new P2 Volumes of select clips for direct importing into Avid and other P2 compatible NLEs.
Sounds neat. A bit redundant, but neat.
Thursday, June 5, 2008
Flip Mino Footage
If you're unfortunate enough to have to use some footage someone brought in captured with a Flip Mino, I feel for ya. Here's a page I found after someone phoned me asking how to do it.
I love the bottom part which is all you really need to know:
If that's not "Mac Friendly" I don't know what is. Thanks Flip! (Warning, their site plays music as soon as it loads...yay!) This from the company who's working with Apple to resolve the problem -like it's theirs- ...yeah, whatever.
Next up we're going to start getting footage recorded via Google's Vidnik.
At least the Vidnik guys have a clue and actually try and fix things:
I love the bottom part which is all you really need to know:
After ensuring the "Open Using Rosetta" is not selected, and DivX is installed, you should be able to view your videos in iMovie '06.
If that's not "Mac Friendly" I don't know what is. Thanks Flip! (Warning, their site plays music as soon as it loads...yay!) This from the company who's working with Apple to resolve the problem -like it's theirs- ...yeah, whatever.
Next up we're going to start getting footage recorded via Google's Vidnik.
At least the Vidnik guys have a clue and actually try and fix things:
Quicktime is producing MPEG-4 encoded movies with an edit list. The first displayable frame of the movie is a b-frame, not an i-frame. Other transcoders and players, when they encounter such movies, drop the initial sequence of b-frames from the video. I'm making a change to Vidnik detect that the first displayable frame is not an i-frame, and rewrite those movies, such that the first frame is an i-frame. I'll test, then upload a new version.
Subscribe to:
Posts (Atom)