[Chris Henderson]

Tried it. Did not work on Driver pack 9.5.2 as a plain ol’ extended desktop. The Blackmagic Design System Preferences panel did not show anything described in the manual.

Chris.

[Chris Henderson]

Bump. I have an Intensity as well. Version 9.1 drivers do not allow for an extended desktop. Downloading latest today and trying again. If they can do it on the Decklink cards, this should be a no-brainer.

Chris.

[Chris Henderson]

Does your AC3 have embedded timecode or other header info that the AC3 decoder in FFMPEG doesn’t support?

-CJ

[Chris Henderson]

I understand that PSF is a manufacturer’s method of making a cheaper card by ingesting and processing the video using 2 fields with the same timestamp versus true interlaced where the fields have different timestamps. The Kona3 control panel clearly states that when a 1080PSF signal is selected as the input, the framebuffer’s primary and secondary outputs cannot select 1080P as an output result. That said, software on my PC capture rigs changes the video from PSF to P on the fly all the time and my automated compression software reads it just fine on a Windows-generated QT file using DNxHD. Granted Avid’s codec has it’s own progressive/PSF handling versus ProRes’. I’ve tried to get this one vendor of mine on DNx, but they won’t have it. They will only deliver FCP-captured ProRes files to us because of it’s realtime capture ability, so I’m trying to work with them on this. That is the why I’m doing this.

Thanks for your help if have a way to do this. I’m also going to try Jeremy’s method with them as well.

Chris.

[Chris Henderson]

Thanks Jeremy! Will try that and report back to confirm.

Chris.

[Chris Henderson]

I want to capture progressive ProRes instead of interlaced from a PSF source. Right now, the Kona3 framebuffer won’t do it so I’m looking around a capture software that may do it on the fly from the Kona’s input. I’m running the QT update to 7.6 now and will be doing the FCP update (from 6.0.2) shortly thereafter. Perhaps my negligence to update in the last few months is what is leaving me with this issue. I was capturing with the Compression tab’s interlaced setting set to off and it still captured flagged as interlaced. The app we use to do encodes grabs interlaced/progressive settings from the source file’s video header info to attempt to gauge whether to encode with matching field flagging automatically.

Anyway, you verified the info I needed and I’ll see if it works.

Thanks!
Chris.

[Chris Henderson]

What version of FCP are you using that this works on? I’m on FCP 6.02, QT 7.5.0, and OSX 10.4.11. It still gets flagged as Interlaced even with the checkbox in the QT Settings set to Interlaced Off.

Thanks in advance,
Chris.