John Morgan
Member
Didn't know how to better get your attention 
With permission from the Axio product manager at Matrox, I would like to say a few things about P2 MXF support that was demoed at NAB2006. As the beta version of AxioUtils 2.5 has evolved since NAB (can't mention release date, but it's very soon), a number of refinements now exist and are working perfectly with P2 MXF. Suport for Sony XDCAM MXF also exists, but I have only tested with the AG-HVX200.
At present, Axio (with beta AxioUtils 2.5) has native support (direct import of MXF files to the Premiere Pro 2.0 timeline) for EVERYTHING* the HVX can throw at it, including Native modes, variable frame rates, DVCProHD of any size, i or p or pN, DVCPro50, and of course DV25/DV. *Please give me till Monday to fully test 1080/24p...but I have tested everything else.
The P2 workflow with Axio works exactly like it was meant to be: offload mxf files direct from P2 cards via camera or other USB2.0 device such as P2 Store (mine's on order), import to PPro2.0 for instant placement on the timeline.
OK, here's the really exciting part. Due to the lower overhead of 24pN frames (no pulldown needed), Axio's performance increases 75%!
For this test I used 24pN (1280x720) footage shot at 60fps.
My system is an HPxw9300 with dual Opteron 280 dual-core processors; 4GB RAM, 4Gb dual-channel fiber Rorke Galaxy HDX running WinXP Pro.
V1 = 24pN/60f footage, 100% opacity, scaling 100% (motion, scale and opacity are Adobe effects)
V2 = 24pN/60f footage, 100% opacity, scaling 30%
V3 = same as V2, placed in a visible spot
V4 = same as V3
V5 = same as V3
V6 = 24pN footage, 40% opacity, scaling 100%
V7 = same as V6
These 7 visible layers will all play in realtime without a render warning (red bar in PPro2.0). Substitue photo stills @ 1280x720@72ppi for video layers above V1, and the layer count increases to 13 layers RT (on my system).
Yes, this is only one specific type of test, but it is the same test I've been using to determine real-time layer capability. Axio has a particular workflow that requires the use of Matrox effects (and/or Adobe motion effects). Adding effects decreases the amount of realtime capability as one would expect.
With 720p/60 footage, I can get 4 layers realtime. This was my former benchmark, so by working in 24pN, I get 3 more layers, or 75% increase.
Please pardon my excitement about Axio, but this is HUGE news about an editing system and workflow that supports you and P2 MXF (including native shooting modes) with native DVCProHD codecs (and others).
I'm in Utah at Salt Lake Community College. Anyone in the vicinity who would like to see Axio at work, contact me privately. As a favor to a superb product and programming team, any of you on the East coast who would like to see Axio, go to:
http://www.matrox.com/video/events/united_states.cfm#ny
Stilll scraping my head together after seeing 7 layers RT!:love4:
John
With permission from the Axio product manager at Matrox, I would like to say a few things about P2 MXF support that was demoed at NAB2006. As the beta version of AxioUtils 2.5 has evolved since NAB (can't mention release date, but it's very soon), a number of refinements now exist and are working perfectly with P2 MXF. Suport for Sony XDCAM MXF also exists, but I have only tested with the AG-HVX200.
At present, Axio (with beta AxioUtils 2.5) has native support (direct import of MXF files to the Premiere Pro 2.0 timeline) for EVERYTHING* the HVX can throw at it, including Native modes, variable frame rates, DVCProHD of any size, i or p or pN, DVCPro50, and of course DV25/DV. *Please give me till Monday to fully test 1080/24p...but I have tested everything else.
The P2 workflow with Axio works exactly like it was meant to be: offload mxf files direct from P2 cards via camera or other USB2.0 device such as P2 Store (mine's on order), import to PPro2.0 for instant placement on the timeline.
OK, here's the really exciting part. Due to the lower overhead of 24pN frames (no pulldown needed), Axio's performance increases 75%!
For this test I used 24pN (1280x720) footage shot at 60fps.
My system is an HPxw9300 with dual Opteron 280 dual-core processors; 4GB RAM, 4Gb dual-channel fiber Rorke Galaxy HDX running WinXP Pro.
V1 = 24pN/60f footage, 100% opacity, scaling 100% (motion, scale and opacity are Adobe effects)
V2 = 24pN/60f footage, 100% opacity, scaling 30%
V3 = same as V2, placed in a visible spot
V4 = same as V3
V5 = same as V3
V6 = 24pN footage, 40% opacity, scaling 100%
V7 = same as V6
These 7 visible layers will all play in realtime without a render warning (red bar in PPro2.0). Substitue photo stills @ 1280x720@72ppi for video layers above V1, and the layer count increases to 13 layers RT (on my system).
Yes, this is only one specific type of test, but it is the same test I've been using to determine real-time layer capability. Axio has a particular workflow that requires the use of Matrox effects (and/or Adobe motion effects). Adding effects decreases the amount of realtime capability as one would expect.
With 720p/60 footage, I can get 4 layers realtime. This was my former benchmark, so by working in 24pN, I get 3 more layers, or 75% increase.
Please pardon my excitement about Axio, but this is HUGE news about an editing system and workflow that supports you and P2 MXF (including native shooting modes) with native DVCProHD codecs (and others).
I'm in Utah at Salt Lake Community College. Anyone in the vicinity who would like to see Axio at work, contact me privately. As a favor to a superb product and programming team, any of you on the East coast who would like to see Axio, go to:
http://www.matrox.com/video/events/united_states.cfm#ny
Stilll scraping my head together after seeing 7 layers RT!:love4:
John
