I just wanted to follow up on the thread regarding HD input into
Jitter. Previously I had mentioned that HDV input wasn't possible and
DVCProHD was possible with the FCP installed QT input component on
Regarding DVCProHD, upon further scrutiny, we noticed only ~10fps as
output via the QT input component provided with FCP regardless of the
framerate the patch was capable of regardless of the vmode used.
Regarding HDV, as is known, there's no QT supplied input component.
However, both of these problems should be possible to overcome by
using an input board such as the Kona LHe or BlackMagic DeckLink HD
(allegedly with better quality than either the DVCProHD or HDV codecs
if your camera ouputs the original frame rather than the compressed
frame decompressed again).
For many cameras you will only be able to take analog HD output, but
if your device supports HD-SDI (like the new Canon HDV camera does)
you can get an uncompressed digital signal. Still the analog HD
output from cameras such as the HVX200, despite any additional analog
noise issues, is allegedly better quality than the compressed
These cards aren't exactly cheap ($1000-$2000), and they require a
desktop machine with the appropriate variant of PCI slot, but they
should provide the best (and most CPU efficient) way to get HD
footage into jit.qt.grab (and jit.dx.grab for cards with a Direct X
input component). I might try to get my hands on the Kona LHe
sometime in the next year, but If anyone else has any experience to
report on the use of these cards with HD input into jitter, please
share your results.
For those of you looking to avoid this PCI card based solution, If we
discover any way to make the DVCProHD QT input component deliver more
frames per second, or a third party HDV Direct X or QT input
component we'll let you know.