IOHD and hdv

[Gustavo Mendes]

It all depends on your computer and RAD specs, but the short answer is yes.

[Jeff Mack]

Well, I created a new sequence by using an IOHD easy setup. I then copied my clips from the HDV sequence and placed them in the pro res sequence and it works fine – playback. I have a green render par but it previews perfectly. I tried changing the sequence settings on the hdv sequence to match the pro res sequence and that one still won’t playback. The settings are now identical. Can’t figure that out!

JEff

[Michael Sacci]

Well if you cannot figure it out how do you expect any help for anyone here. You have not listed any settings or system specs.

[Jeff Mack]

Hey Michael. I did just figure it out accidentally while on the phone with Jerry at AJA. I thought it was simply an issue of not being able to play 1080i 60 through the IOHD. Anyway, here’s the specs.

MBP 2.16, 2 gb ram, 10.6.3, FCP 7.0.2, IOHD updated, files on 500 gb system internal drive, 250 gb free.

So I capture HDV, 1080i and lay it on my timeline. I turned on my IOHD and got a kernal panic. shut down and restarted. turned on IOHD, then FCP and all ok. Component out of IOHD into my home theatre receiver into a 61″ DLP. I have video playback in a/v settings set to pro res 1920 x 1080.

The problem was that when I play back the HDV footage, it plays like 2 seconds then gives me the dropped frame warning. My original post was intended to ask if HDV could play through the IOHD. I called AJA and they said it couldn’t because my machine wasn’t robust enough.

WHat I did to solve the problem was to select pro res lt as my easy setup. I created a new sequence using that easy setup. I copied and pasted all of the HDV clips onto the new sequence. I got the green render bar. Playback is set to unlimited. Now the timeline plays threough my IOHD without any problems.

I since opened safari and monitor went black. came back into fcp to reactivate the timeline, hit play and got the dropped frame warning again. Then I simply hit easy setup and then setup, the monitor flickered, hit play and all is ok again >I recreated this intermittancy and by hitting easy setup, I lost the dropped frame issue. Note: I have not rendered. The clips are still HDV.

Jeff

[Jeremy Garchow]

[Jeff Mack] “files on 500 gb system internal drive, 250 gb free. “

If you had a faster external drive, you won’t get the dropped frames. ALso, render before playback.

Jeremy

[Jeff Mack]

This is what I am saying. I’m staying on the internal and I did not render and I got rid of the dropped frame warnings.

[Jeremy Garchow]

[Jeff Mack] “I’m staying on the internal and I did not render and I got rid of the dropped frame warnings.”

AN external drive that is not a fw800 drive that the ioHD is looped through (that is, make sure you have a fw800, or esata express/34 card to separate the ioHD bus from the drive bus) and your performance should be even much better.

Jeremy

[Gustavo Mendes]

Honestly, although you had a few instances where it played it fine, without an external drive it just not going to work well. Another problem is that your machine is below the minimum specs, and to render HDV to ProRes on the fly you’ll need something faster.

[Jeff Mack]

Thanks Gustavo Michael and Jeremy, I normally use an expresscard to esata to 4 disk raid when I work. In this case though, I’m sifting through an hour and a half of run and gun to get 3 minutes. I intended to get all of my clips selected and then do a media manage and render the resulting to pro res just to save time and space. Since I haven’t worked through the HDV output before, I didn’t know of it’s shortcomings to just be able to play out through the IOHD. I have it working now but understand it’s not an optimal workflow. The other PITA is that since I have my clips separated in the timeline, every time I hit a blank space, I drop again. Then when I get to the next clip, it’s fine. How weird is that?

Jeff

[Jeremy Garchow]

Try putting a slug in the gaps.