| Notes: |
|
| 1 |
Scrubbing: Canopus DV Out incurs 8 frame hardware latency which renders
it unusable for scrubbing |
|
Scrubbing: AV10 Video Out incurs significant latency which renders video
out unusable for scrubbing, instead users must use Pro Tools screen scrub
window |
|
|
| 2 |
PCI / CPU Load : AV10 uses the Host CPU for some video decompression, which can be a significant additional load. Also, it precludes the use of the built in Firewire ports for drive access,
so an additional Firewire PCI Card may be necessary |
|
PCI / CPU Load : AV10 uses very high data rate firewire transfer which
shares PCI bandwidth on some CPUs. This effectively eliminates the use of
some PCI slots |
|
PCI / CPU Load : At the time of writing AV10 is not compatible with Mac. Also AV10 only supports HD or ACCEL systems, so PT24, Mix and all LE platforms are NOT supported |
|
|
| 3 |
Hi Def Video : DeckLink SP card can play high definition video with real
time down convert to PAL/NTSC out. Use optional DeckLink HD for HD-SDI out |
|
|
| 4 |
Avid Video Compatibility : VirtualVTR can play QT wrapped Avid Meridien
OMF video on OSX, and QT Wrapped ABVB/Meridien OMF Video on OS9 |
|
|
| 5 |
24 FPS Playback with 3:2 pull up : VirtualVTR and DeckLink play 24 FPS
video with real time 3:2 pull up for NTSC video out |
|
24 FPS Playback with 3:2 pull up : Pro Tools+AV10 cannot perform real
time 3:2 pull up, and so it repeats frames, which causes video stuttering |
|
24 FPS Playback with 3:2 pull up : IgniterLT cannot perform real time 3:2
pull up, and so it repeats frames, which causes video stuttering. |
|
|
| 6 |
Video Capture To Timeline : AV10 requires media to be captured into the external Avid application before transfer to Pro Tools. Video is timestamped. This requires the user to quit applications between operations. |
|
Video Capture To Timeline : V1 and VirtualVTR capture Media with
timestamp in place ready to playback immediately in sync. |
|
Video Capture To Timeline : Canopus and Igniter video must be captured in
3rd party application and cannot be timestamped for Pro Tools so a manual
spot into place is required |
|
|
| 7 |
Format Compatibility : AV10 requires Avid format movies, and QuickTime
DV, DVCPro and DVCPro50, MJPEG etc must be converted to OMF in MediaStation |
|
|
| 8 |
PC/Mac Pro Tools Compatibility : Since VirtualVTR runs on a dedicated Mac
CPU, it supports both Mac and PC Pro Tools systems as controller. |
|
PC/Mac Pro Tools Compatibility : IgniterLT runs on Mac Only |
|
|
| 9 |
Multi-User Control : On a Multi-Pro Tools mix stage, it is desireable to
control the picture from all systems. VirtualVTR can merge control
information |
|
from Several Pro Tools sources with all machines having complete
stop/play/scrub/shuttle control at all times. Any Pro Tools system can be
taken offline for editing without |
|
removing the picture source for the other Pro Tools Systems. |
|
|
| 10 |
AV/XL Price : Since AV10 is not currently available on Mac, AV/XL is sold
with future upgrade to AV10 at AV10 Price. |
|
|
| 11 |
AV/XL Compatibility : AV/XL has limited compatibility, requiring specific
versions of Pro Tools, SCSI Cards, etc. Other compatibility issues also apply |
|
AV10 Compatibility : At the time of writing, AV10 was not supported on Macintosh, Also AV10 only supports HD or ACCEL systems, so PT24, Mix and all LE platforms are NOT supported |
|
|
| N.B |
All data was compiled from a study of information published by the
various vendors, and through testing. E&OE, please contact
info@gallery.co.uk if any of this information is incorrect |
|
|
|
The VirtualVTR system in the comparison was based on a Dual G4 1.25GHz
CPU, with a DeckLink SP Card. Similar results can be obtained using |
|
VirtualVTR with Aurora Pipe, PipePro and Igniter X cards, DeckLink Pro or
HD, Kona SD / HD and other cards, with some small variations in Spec. |
|
In some cases a slower CPU will suffice. When using Video Streamers a
faster CPU is recommended, eg a dual G5 |