HVX Direct to disc Shooting
- Thread starter MagicCat
- Start date
Shiloh Arts
Well-known member
Barry_Green said:
As always...giving the answers that count...thanks Barry:dankk2:
Shiloh Arts
Well-known member
Anomolee said:Shiloh Arts:
Still having trouble doing a direct to disk capture from the HVX to FCP?
Make sure that you have your setting matched in the HVX to your Log and capture setting in FCP.
<interested to see how your Macbook performs>
please post your results with all the specs of your Macbook.
Thanks!
Wow! Thanks ...I noticed all those settings, but wasn't able to figure out which is best for what I wanted to get done. I have 1 8Gig p2. However will be probably getting the fs-100. It's now just a matter of finding the correct workflow that fits me. I assume FCP can read panny's mxf files fine...right? (haven't been able to really toy with the cam & workflow much)
Anomolee said:
You know what the worst part of the new MacBook is...Apple discontinued PCMCIA SUPPORT in place of smaller flash SD memory (Go figure).
I have a shoot later today and will try out your workflow, I'll let you know how the MacBook stands up to the test as soon as today maybe. :dankk2:
Last edited:
bbalser
Veteran
Focus will have a White Paper on the whole work flow from HVX200 to FS-100 to FCP by next weekend. It will be very comprehensive.
As for capturing live to a Mac laptop of any model is the Firewire port. First up, capturing to the system drive is a very bad idea, and gives you super limited disk space, anyway. And you HAVE to have some software to read the data stream from the Firewire port and write the video files. FCP and QTPro will do it, but you get QT files, and they will contain all the P2 metadata. To get the original P2 data structure, you have to use P2 cards in-camera or the FS-100.
You have to add an external drive to the system. Problem, all Mac laptops have only one FireWire "data buss" that all the FW "ports" (or plugs) share. This data pipe is too narrow to ingest the live footage and pump it back out live to the hard drive. I've worked with this for quite some time now.
You have to get a PC card that gives you another FW port/buss. Then you have two FW busses and can do a live capture on a Mac laptop. Same problem holds ture for PC laptops.
FCP will ingest the P2 data just fine. Read that I said it will "ingest" it fine. What it does is converts the P2 data files into QuickTime files in your Capture Scratch folder. Thus, "ingesting" direct from the P2 cards or the FS-100 (which I just completed a review on, July Event DV magazine, and it's a fantastic product, just needs a larger hard drive in it).
If you copy your CONTENTS folder to your local drive, the only thing that does is gives you a back up copy of your P2 original data. FCP's QT files contain all the metadata from the P2, so you basically have two copies of everyting.
As for capturing live to a Mac laptop of any model is the Firewire port. First up, capturing to the system drive is a very bad idea, and gives you super limited disk space, anyway. And you HAVE to have some software to read the data stream from the Firewire port and write the video files. FCP and QTPro will do it, but you get QT files, and they will contain all the P2 metadata. To get the original P2 data structure, you have to use P2 cards in-camera or the FS-100.
You have to add an external drive to the system. Problem, all Mac laptops have only one FireWire "data buss" that all the FW "ports" (or plugs) share. This data pipe is too narrow to ingest the live footage and pump it back out live to the hard drive. I've worked with this for quite some time now.
You have to get a PC card that gives you another FW port/buss. Then you have two FW busses and can do a live capture on a Mac laptop. Same problem holds ture for PC laptops.
FCP will ingest the P2 data just fine. Read that I said it will "ingest" it fine. What it does is converts the P2 data files into QuickTime files in your Capture Scratch folder. Thus, "ingesting" direct from the P2 cards or the FS-100 (which I just completed a review on, July Event DV magazine, and it's a fantastic product, just needs a larger hard drive in it).
If you copy your CONTENTS folder to your local drive, the only thing that does is gives you a back up copy of your P2 original data. FCP's QT files contain all the metadata from the P2, so you basically have two copies of everyting.
Last edited:
If HD Log latches on to your iSight, go to the Video menu -> Sound Settings and select any audio source other than the built in mic. If the setting doesn't retain, then you'll need the latest version (v3.6.1).
Like FCP, HD Log needs a P2 structure (CONTENTS folder with or without LASTCLIP.TXT) in order to parse MXF files correctly. The ability to read MXF files directly may be added eventually, but it isn't a top priority right now.
We're looking at adding a mode that will capture live video from the camera. The result would be stored in a QuickTime file like FCP, but it would have embedded timecode, read from the frames.
Like FCP, HD Log needs a P2 structure (CONTENTS folder with or without LASTCLIP.TXT) in order to parse MXF files correctly. The ability to read MXF files directly may be added eventually, but it isn't a top priority right now.
We're looking at adding a mode that will capture live video from the camera. The result would be stored in a QuickTime file like FCP, but it would have embedded timecode, read from the frames.
Shiloh Arts
Well-known member
I know it's a real bad Idea to capture direct to main disk. It's just that after the purchase of the MacBook, I realized that there is absolotly no more PCMCIA slots, thus no more bulit-in P2 support. So, I'm returning the P2 solution to go with the FS-100. Neverthless, I would like to know how to utilize the other options.
BenB, thank you for explaining the MXF file conversion. I think what you're saying is that FCP tranlates the MXF file plat-form to QT similar to what the DV Film software does, only a Mac solution...right?
Did you attend the Streaming Media East conference in NY?
BenB, thank you for explaining the MXF file conversion. I think what you're saying is that FCP tranlates the MXF file plat-form to QT similar to what the DV Film software does, only a Mac solution...right?
Did you attend the Streaming Media East conference in NY?
Last edited:
LearningVideo
Well-known member
One thing that the HVX will not do, which probably many newB including myself where hoping that it will do, is connect to a PC and simply record on the harddrive.
HVX cannot do that at all without a Capturing Software Running on that PC. And if you have two cameras, then you need TWO PCs each running its own capturing software. Unfortunately, up to now, this "capturing Software" happened to be the FULL BLOWN NLE! (Edious and AVID for PC)
So is this issue addressed?
1) Panasonic solution for the above is the P2 card. And in the long term, as capacity of P2 cards increases and IF prices keep going down, is truely the ideal solution.
2) "Intelligent Hardware": Focus and others. They really really need to watch their prices to continue to be a viable option.
3) DVC-RACK: instead of utilizing the NLE, use a smaller utility in which you can run the capture and conversion, then load to the NLE.
4) MY CURRENT SHORT TERM SOLUTION AND PLEASE DO NOT LAUGH: SHOOT DV ON MINIDV TAPE
5) I am sure many options will be presenting themselves. Practical options that might force some of the above solutions to go obsolete.
HVX cannot do that at all without a Capturing Software Running on that PC. And if you have two cameras, then you need TWO PCs each running its own capturing software. Unfortunately, up to now, this "capturing Software" happened to be the FULL BLOWN NLE! (Edious and AVID for PC)
So is this issue addressed?
1) Panasonic solution for the above is the P2 card. And in the long term, as capacity of P2 cards increases and IF prices keep going down, is truely the ideal solution.
2) "Intelligent Hardware": Focus and others. They really really need to watch their prices to continue to be a viable option.
3) DVC-RACK: instead of utilizing the NLE, use a smaller utility in which you can run the capture and conversion, then load to the NLE.
4) MY CURRENT SHORT TERM SOLUTION AND PLEASE DO NOT LAUGH: SHOOT DV ON MINIDV TAPE
5) I am sure many options will be presenting themselves. Practical options that might force some of the above solutions to go obsolete.
