Showing posts with label ingest. Show all posts
Showing posts with label ingest. Show all posts
Tuesday, June 21, 2011
FCPX Options for Ingesting Media from Photo-Based Devices
Apple has put up a page covering the basics on ingesting and importing media from "photo-based devices" into FCPX which really means SD cards and DSLRs.
Panasonic's P2 Card and the Format Error!
Hopefully you'll never see this:
It's a FORMAT ERROR! (I think it actually reads "FORMAT ERR!") which can occur very rarely on P2 cards for seemingly no reason. Recently we had one while on location.
What happened was someone forgot a standard USB cable to load in footage from an HVX200 camera to a Hard Drive - I've had extremely bad luck with going directly from the camera to a hard drive in the past so I avoid it at almost all costs now - and since we were on location with pretty much nothing around us in the way of stores and rummaging around through everyone's bags and equipment cases looking for a USB cable I decided to load in the footage via Firewire.
Now this camera and another we've been using have had Firewire issues in the past. Namely extremely slow and getting slower over time Firewire transfers. Resetting the cameras and restoring the Firmware seems to have no effect. USB xfers are multiple times faster than Firewire at this point so I've been going with USB regularly, often and without issue when there's no card reader available.
So, finding a Firewire cable and setting the camera to be a Firewire device and hooking everything up I began the copy from camera to laptop. While slow -as expected- it was going and I told everyone to take a coffee break while it copied over.
About 400MBs into the copy there was a Finder Read/Write error, I didn't have permission for something or other and it konked out. I suspect it was something to do with the "LASTCLIP.TXT" file which is locked by default.
So I tried to unmount the camera with no response and ended up just power cycling it since it was completely unresponsive and the Finder on the laptop couldn't unmount it even after waiting 5+ mins.
Powering it back on I saw the dreaded "FORMAT ERROR!" in red on the screen.
Now this is a very rare error and unfortunately there's not much you can do about it on location. Some people have had luck with a few power cycles and mounts and unmounts, others have had luck with Disk Utility repairing it but I wasn't one of them. I'm reluctant to have the Mac do anything to the cards but we were desperate and the director said go ahead so I tried a few repairs with the Terminal and Disk Repair but nothing seemed to help.
We ended up calling and overnighting the card to Panasonic who was able to recover the footage in their labs. They copied the footage back to the same card of ours and shipped it back to us. Panasonic was amazing, fast and helpful.
So the bottom line solution for us, upon seeing FORMAT ERROR! was to just ship the card to Panasonic and have them recover the footage.
My new rules for loading footage from a P2 card when you have to use the camera as a reader is to:
1. Lock the card with the write protect switch before mounting it on the Mac.
2. NEVER use Firewire. USB only from now on.
![]() |
| The error message blinks which is why it looks faded here. |
It's a FORMAT ERROR! (I think it actually reads "FORMAT ERR!") which can occur very rarely on P2 cards for seemingly no reason. Recently we had one while on location.
What happened was someone forgot a standard USB cable to load in footage from an HVX200 camera to a Hard Drive - I've had extremely bad luck with going directly from the camera to a hard drive in the past so I avoid it at almost all costs now - and since we were on location with pretty much nothing around us in the way of stores and rummaging around through everyone's bags and equipment cases looking for a USB cable I decided to load in the footage via Firewire.
Now this camera and another we've been using have had Firewire issues in the past. Namely extremely slow and getting slower over time Firewire transfers. Resetting the cameras and restoring the Firmware seems to have no effect. USB xfers are multiple times faster than Firewire at this point so I've been going with USB regularly, often and without issue when there's no card reader available.
So, finding a Firewire cable and setting the camera to be a Firewire device and hooking everything up I began the copy from camera to laptop. While slow -as expected- it was going and I told everyone to take a coffee break while it copied over.
About 400MBs into the copy there was a Finder Read/Write error, I didn't have permission for something or other and it konked out. I suspect it was something to do with the "LASTCLIP.TXT" file which is locked by default.
So I tried to unmount the camera with no response and ended up just power cycling it since it was completely unresponsive and the Finder on the laptop couldn't unmount it even after waiting 5+ mins.
Powering it back on I saw the dreaded "FORMAT ERROR!" in red on the screen.
Now this is a very rare error and unfortunately there's not much you can do about it on location. Some people have had luck with a few power cycles and mounts and unmounts, others have had luck with Disk Utility repairing it but I wasn't one of them. I'm reluctant to have the Mac do anything to the cards but we were desperate and the director said go ahead so I tried a few repairs with the Terminal and Disk Repair but nothing seemed to help.
We ended up calling and overnighting the card to Panasonic who was able to recover the footage in their labs. They copied the footage back to the same card of ours and shipped it back to us. Panasonic was amazing, fast and helpful.
So the bottom line solution for us, upon seeing FORMAT ERROR! was to just ship the card to Panasonic and have them recover the footage.
My new rules for loading footage from a P2 card when you have to use the camera as a reader is to:
1. Lock the card with the write protect switch before mounting it on the Mac.
2. NEVER use Firewire. USB only from now on.
Labels:
error message,
hvx-200,
ingest,
p2,
panasonic,
troubleshooting
Sunday, June 19, 2011
MacBook Pro 2011 Not Recognizing SanDisk Class 10 SD Cards
A few people are reporting that a Class 10 SanDisk SD Card won't be reliably recognized in a 2011 MacBook Pro.
What does seem to work as a temporary workaround is restarting the Mac with the card already inserted. But even then it's not recognized if you remove the card and then reinsert it or another similar card.
"I use a Sandisk SDHC Extreme Class 10 SD Card and have problems getting it to read through the inbuild SD card reader.
I tried the following:
Reformatting on Disk Utility
Reformatting on my Canon 450D
Restarting Laptop
Resetting PRAM
Resetting SMC
Repairing Disk Permissions
Repairing Disk
All of these did not solve my problem. I have a card reader which when plugged into the MBP, works fine and detects the card.
The Weird Part
I plugged the card into a friend's iMac and it detects it every time. And then right after I do that, I plug it into my MBP, and it detects the card, but the problem is once I eject it, and slot it back in, it fails to detect again! However if I try this method again (Slot to iMac, remove, slot back to MBP), it will fail the second time. "
Someone tried a card in MacBooks at an Apple store and:
"They had me EFFA back the machine, and provided me with a new one. I tested the new one right out of the box and it worked fine, but after Migration, it no longer worked. Restoring using the included disk back to factory specs DID NOT restore the ability to read the card.
In checking random machines at the apple store, only 1 on the entire floor recognized that a card was inserted, when I tried the Sandisk SDHC Extreme Pro 8GB 45MB/S card."
Apparently Apple and SanDisk are aware of the problem but if you use SD Cards for production or have them sent to you for editing it's a good idea to be aware of this issue. I've not seen it as I've been using an external USB card reader. Hopefully it'll be addressed soon with a software update.
What does seem to work as a temporary workaround is restarting the Mac with the card already inserted. But even then it's not recognized if you remove the card and then reinsert it or another similar card.
"I use a Sandisk SDHC Extreme Class 10 SD Card and have problems getting it to read through the inbuild SD card reader.
I tried the following:
Reformatting on Disk Utility
Reformatting on my Canon 450D
Restarting Laptop
Resetting PRAM
Resetting SMC
Repairing Disk Permissions
Repairing Disk
All of these did not solve my problem. I have a card reader which when plugged into the MBP, works fine and detects the card.
The Weird Part
I plugged the card into a friend's iMac and it detects it every time. And then right after I do that, I plug it into my MBP, and it detects the card, but the problem is once I eject it, and slot it back in, it fails to detect again! However if I try this method again (Slot to iMac, remove, slot back to MBP), it will fail the second time. "
Someone tried a card in MacBooks at an Apple store and:
"They had me EFFA back the machine, and provided me with a new one. I tested the new one right out of the box and it worked fine, but after Migration, it no longer worked. Restoring using the included disk back to factory specs DID NOT restore the ability to read the card.
In checking random machines at the apple store, only 1 on the entire floor recognized that a card was inserted, when I tried the Sandisk SDHC Extreme Pro 8GB 45MB/S card."
Apparently Apple and SanDisk are aware of the problem but if you use SD Cards for production or have them sent to you for editing it's a good idea to be aware of this issue. I've not seen it as I've been using an external USB card reader. Hopefully it'll be addressed soon with a software update.
Wednesday, March 23, 2011
How To Convert .MOD files for Final Cut Pro
I've mentioned .MOD files before but thought I'd just update a bit of my workflow when using them.
I'm getting ready for a multi-cam project that involves many, many small Cannon cameras (all synced) which create troublesome .MOD files.
Now a .MOD file is just an mpeg2 file with another name. Look at a .MOD file using the File command in the terminal and you'll see:
"MOV001.MOD: MPEG sequence, v2, program multiplex"
So, it really isn't anything special but Final Cut Pro won't ingest them.
What happens if you rename one to say .mpg? Quicktime will open it (not sure if Perian helps here or a default install will do) and will report that it's an "MPEG2 Muxed @ 29.97 fps.
After renaming it FCP will ingest it but, as it's a Muxed file, there will appear to be no audio tracks; the same goes or when it's opened in Quicktime.
You must convert -actually transcode- it and my transcoder of choice in this case would be MPEG Streamclip.
Open the .MOD file in MPEG Streamclip and hit Export. But make sure that you've set it to the correct aspect ratio because depending on the type of camera and what it's set to the image may be 4:3, 16:9 and /or Squeezed…or not. That's what the handy "Preview" button is for. Oh, you don't need to rename it in order to transcode it.
I like to transcode them to ProRes (especially for multi-clip editing) but the export format is up to you. I recommend testing a small file (or portion thereof) first for testing your export settings.
I'm getting ready for a multi-cam project that involves many, many small Cannon cameras (all synced) which create troublesome .MOD files.
Now a .MOD file is just an mpeg2 file with another name. Look at a .MOD file using the File command in the terminal and you'll see:
"MOV001.MOD: MPEG sequence, v2, program multiplex"
So, it really isn't anything special but Final Cut Pro won't ingest them.
What happens if you rename one to say .mpg? Quicktime will open it (not sure if Perian helps here or a default install will do) and will report that it's an "MPEG2 Muxed @ 29.97 fps.
After renaming it FCP will ingest it but, as it's a Muxed file, there will appear to be no audio tracks; the same goes or when it's opened in Quicktime.
You must convert -actually transcode- it and my transcoder of choice in this case would be MPEG Streamclip.
Open the .MOD file in MPEG Streamclip and hit Export. But make sure that you've set it to the correct aspect ratio because depending on the type of camera and what it's set to the image may be 4:3, 16:9 and /or Squeezed…or not. That's what the handy "Preview" button is for. Oh, you don't need to rename it in order to transcode it.
I like to transcode them to ProRes (especially for multi-clip editing) but the export format is up to you. I recommend testing a small file (or portion thereof) first for testing your export settings.
Monday, March 21, 2011
Ingesting & Importing A Screen Recording .mov into Final Cut Pro
As if we didn't have reason enough to hate QuickTime X here's another:
You can't just ingest a Screen Recording you make into FCP. Nope. You have to convert it first to something else.
I suspect it's because of the odd frame rates that screen recordings are in. Take a look at this example:
8.23 FPS.
If you try and ingest it into FCP you'll see this:
What's going on? How can you load a QuickTime movie (a format by Apple) made by Quicktime X (software from Apple) into Final Cut Pro (Video editing software made by Apple)?
Insane, right?
I think it has something to do with the frame rate. Although I can't fathom why, FCP seems to want some "normal" frame rates in this case.
Test #1 - Export using QuickTime 7 to H.264 @ 29.97 FPS
Result: FCP will accept.
Test #2 - Export using QuickTime 7 to H.264 @ "current" FPS (8.23)
Result: FCP will NOT accept.
Test #4 - Export using QuickTime 7 to ProRes (non HQ) @ 29.97 FPS
Result: FCP will accept.
Bonus Test #1 - Export using QuickTime 7 to ProRes (non HQ) @ 8 FPS
Result: FCP will accept.
Bonus Test #2 - Export using QuickTime 7 to H.264 @ 8 FPS
Result: FCP will accept.
I have no idea why QuickTime X records Screen Recordings at a frame rate that FCP doesn't like. Likewise, I have no idea while FCP won't accept certain frame rates, but at least there's a work-around.
Btw, this is FCP 6.0.6. I haven't tested it under FCP 7.x yet.
I'd recommend transcoding your Screen Recordings into ProRes at 8 FPS which will make them a bit smaller compared to 29.97 (obviously) and less CPU intensive.
You can't just ingest a Screen Recording you make into FCP. Nope. You have to convert it first to something else.
I suspect it's because of the odd frame rates that screen recordings are in. Take a look at this example:
8.23 FPS.
If you try and ingest it into FCP you'll see this:
What's going on? How can you load a QuickTime movie (a format by Apple) made by Quicktime X (software from Apple) into Final Cut Pro (Video editing software made by Apple)?
Insane, right?
I think it has something to do with the frame rate. Although I can't fathom why, FCP seems to want some "normal" frame rates in this case.
Test #1 - Export using QuickTime 7 to H.264 @ 29.97 FPS
Result: FCP will accept.
Test #2 - Export using QuickTime 7 to H.264 @ "current" FPS (8.23)
Result: FCP will NOT accept.
Test #3 - Export using QuickTime 7 to ProRes (non HQ) @ "current" FPS (8.23)
Test #4 - Export using QuickTime 7 to ProRes (non HQ) @ 29.97 FPS
Result: FCP will accept.
Bonus Test #1 - Export using QuickTime 7 to ProRes (non HQ) @ 8 FPS
Result: FCP will accept.
Bonus Test #2 - Export using QuickTime 7 to H.264 @ 8 FPS
Result: FCP will accept.
I have no idea why QuickTime X records Screen Recordings at a frame rate that FCP doesn't like. Likewise, I have no idea while FCP won't accept certain frame rates, but at least there's a work-around.
Btw, this is FCP 6.0.6. I haven't tested it under FCP 7.x yet.
I'd recommend transcoding your Screen Recordings into ProRes at 8 FPS which will make them a bit smaller compared to 29.97 (obviously) and less CPU intensive.
Labels:
ingest,
quicktime x,
screen recording,
transcoding,
troubleshooting
Tuesday, February 3, 2009
HPX500 shows nothing to ingest
Yikes.
I like Apple's use of the word "try" in the long resolution which you can read here. At its most basic, you change ingest prefs, sequence settings, import, load into a timeline, then export then re-import.
On rare occasions, media shot on a Panasonic HPX500 camera may not ingest in the Log and Transfer window. A warning “Error: No Data” appears.
I like Apple's use of the word "try" in the long resolution which you can read here. At its most basic, you change ingest prefs, sequence settings, import, load into a timeline, then export then re-import.
Subscribe to:
Posts (Atom)








