Decklink Intensity Card Notes - Success!


    Apr 12 2007 | 11:45 pm
    Ive spent some hard earned time today with the Decklink Intensity Card.
    It most definitely works with a computer driven DVI source with a DVI- >HDMI adaptor or cable, so the YUV "consumer" HDMI vs RGB DVI computer colorspace "issue" is not a problem per se for the Intensity card as was speculated. I have only tested with my MacBook Pro, but I would be surprised if this was an issue with other systems.
    jit.qt.grab finds the card just fine and will work with colormode argb or uyvy and produce proper results either way.
    Currently the Decklink drivers support only one card. Even though their On Air software sees both cards we have installed, quicktime does not. Decklink is aware of this and will be supporting 2 cards eventually with a software update, so I am told.
    I havent been able to quantify, but there is a noticeable frame lag from the output device to the intensity card input and display. It seems like 3-5 frames delay, not huge, but there.
    My laptop sees the Intensity card and can drive it at 1920x1080 Interlaced or 1280x720 Progressive. I dont think all systems will be able to see and drive the intensity card properly. A friends 12" Powerbook did not properly see the 720P, it output 720 interlaced, so it would not lock up at that resolution.
    Back to Jitter:
    jit.qt.grab on a 2 x 3.0 Ghz Intel Mac Pro with 8GB ram, x1900 with 512MB Vram:
    1920x1080 Interlaced:
    @colormode uyvy @1920x1080 to a videoplane @uyvy = 60fps
    @colormode uyvy to the cc.uyvy2rgba.jxs shader, to a jit.gl.slab @file td.sinefold.jxs, then mixed with the original texture using one of the composite shaders to a videoplane @ rgba, is 60 fps.
    the above, but at colormode rgba sans uyvy/rgba conversion shader is a paltry 30 fps. :)
    1280x720 Progressive:
    720p @ colormode argb with the above shaders ran at 50 -55 fps, and looks lovely being progressive and all.
    Everything else (colormode uyvy, etc) ran at 60fps, but the ARGB progressive mode has a much much nicer image quality. Drastically superior, why would anyone want to deal with Interlacing in this day and age anyway?
    Color differencing (using RGB color mode @720P)
    There are very slight color shifts. Using Final Cut Pro to output SMTPE video bars @720p. I measured the color accuracy using the Digital Color Meter supplied by Apple.
    Local 720p Bars (in RGB as percentage) Red : 70.6% 0. 0. Blue: 0. 0. 70.6 % Green: 0. 70.6 0%
    After Intensity /Jitter to the Mac Pro displayed via GL Red: 73.3 0. 0. % Blue: 0. 0. 73.3 % Green: 0. 73.3 0.%
    Blacks were super black at 0% on both systems
    Pedestal was 2.0% local, 2.7% on intensity card, so some luma/gamma shifting brighter
    The colors after going through Intensity card look really good, and the shifts were not noticeable in any way, but they are there. Not sure if this is a Jitter issue on a Quicktime/Decklink issue, but, at the end of the day they are not really an issue. More testing could reveal the source of the issue.
    I was also able to record using jit.gl.texture to jit.matrix readback, which considering the PCIe bandwidth did not significantly lower performance. I had a greater fps hit dropping in a pwindow that had use onscreen 1 enabled. Recording the 720p content to motion jpeg lowered my framerate to about 35 fps all while driving a full screen display @ 1280x720 progressive with slab effects enabled and mixing.
    Could not Test video out ironically because we had no HDMI viewing monitor. Once they have the second (or hopefully more) card supported, this will make a wonderful platform to use for HD.
    This is really good news.
    I hope this is helpful to the list.
    I hope to test on a PC shortly, but it may be sometime.
    v a d e //
    www.vade.info abstrakt.vade.info

    • Apr 13 2007 | 12:07 am
      Hi Anton,
      Thanks for this info. Lots of good information. If you want to further benchmark (i.e. above 60fps), you can disable vsync for jit.window.
      > 1920x1080 Interlaced:
      What about 1080p 30fps? Is that supported by the card and DVI->HDMI config?
      As for color quality in UYVY mode if it's useful for more performance with multiple sources, you can get nicer gamma correction looking footage from a UYVY signal by using cc.uyvy2rgba.exp.jxs with an exponent of something like 1.2 (might want to adjust some of the other brightness/contrast/saturation controls to your liking too).
      -Joshua
    • Apr 13 2007 | 3:42 am
      Unfortunately, 1080p is not supported by the Intensity card, at least as stated on Decklinks tech page for the product -
      and I did not see a progressive option available in my monitors/ displays for 1920x1080.
      However, Ive been meaning to ask, is a de-interlacing shader possible/ available for 108060i mode? (or, er, any mode?)
      Also, I could see no difference with the chroma_smooth option for the uyvy2rgba shader, what is the intended purpose?
      I can post some picts of the output should it be necessary so we arent too vague. Thanks, glad its helpful.
      On Apr 12, 2007, at 8:07 PM, Joshua Kit Clayton wrote:
      > Hi Anton, > > Thanks for this info. Lots of good information. If you want to > further benchmark (i.e. above 60fps), you can disable vsync for > jit.window. > >> 1920x1080 Interlaced: > > What about 1080p 30fps? Is that supported by the card and DVI->HDMI > config? > > As for color quality in UYVY mode if it's useful for more > performance with multiple sources, you can get nicer gamma > correction looking footage from a UYVY signal by using > cc.uyvy2rgba.exp.jxs with an exponent of something like 1.2 (might > want to adjust some of the other brightness/contrast/saturation > controls to your liking too). >
      v a d e //
      www.vade.info abstrakt.vade.info
    • Apr 13 2007 | 6:44 am
      vade, thank you.
      On 4/13/07, vade wrote: > > Unfortunately, 1080p is not supported by the Intensity card, at least as > stated on Decklinks tech page for the product - > http://decklink.com/products/intensity/techspecs/ > > and I did not see a progressive option available in my monitors/displays > for 1920x1080. > However, Ive been meaning to ask, is a de-interlacing shader > possible/available for 108060i mode? (or, er, any mode?) > > Also, I could see no difference with the chroma_smooth option for the > uyvy2rgba shader, what is the intended purpose? > > I can post some picts of the output should it be necessary so we arent too > vague. Thanks, glad its helpful. > > > > On Apr 12, 2007, at 8:07 PM, Joshua Kit Clayton wrote: > > Hi Anton, > > Thanks for this info. Lots of good information. If you want to further > benchmark (i.e. above 60fps), you can disable vsync for jit.window. > > 1920x1080 Interlaced: > > > What about 1080p 30fps? Is that supported by the card and DVI->HDMI > config? > > As for color quality in UYVY mode if it's useful for more performance with > multiple sources, you can get nicer gamma correction looking footage from a > UYVY signal by using cc.uyvy2rgba.exp.jxs with an exponent of something > like 1.2 (might want to adjust some of the other > brightness/contrast/saturation controls to your liking too). > > > > *v a d e //* > > *www.vade.info* > *abstrakt.vade.info* > > > > > >
    • Apr 14 2007 | 2:37 am
      Im a jerk!
      I forgot to add the @dimscale 2. 1. to the cc.uyvy2rgba.jxs shader. It looks lovely now, no noticeable difference and very fast. Ive got a bunch of performance tests/color tests from PD, Quartz Composer and Jitter.
      Jitter seems to perform highest of all 3 'diy' patching platforms. QC has some really odd issues, lagging up to 45 frames (!!!) behind in 10 bit mode, sometimes less, sometimes more. 8 bit seems to lag more than Jitter or PD/Gem
      Gem works nicely, same order of performance as Jitter, but, its a bit rough around the edges and theres some things to know to get the most performance out of the system, had to ask because it seemed really slow from the get go.
      :)
      On Apr 12, 2007, at 8:07 PM, Joshua Kit Clayton wrote:
      > Hi Anton, > > Thanks for this info. Lots of good information. If you want to > further benchmark (i.e. above 60fps), you can disable vsync for > jit.window. > >> 1920x1080 Interlaced: > > What about 1080p 30fps? Is that supported by the card and DVI->HDMI > config? > > As for color quality in UYVY mode if it's useful for more > performance with multiple sources, you can get nicer gamma > correction looking footage from a UYVY signal by using > cc.uyvy2rgba.exp.jxs with an exponent of something like 1.2 (might > want to adjust some of the other brightness/contrast/saturation > controls to your liking too). >
      v a d e //
      www.vade.info abstrakt.vade.info
    • Apr 14 2007 | 8:43 pm
      Hello Vade, this is good news. Interesting to see how the people at Blackmagic don't even know themselves what they actually make...;-) Did you find out why your laptop works and the 12 inch not? does it have to do with the graphics card? did you test with a mac pro as input? Best Lucas
      On Apr 13, 2007, at 1:45 AM, vade wrote:
      > Ive spent some hard earned time today with the Decklink Intensity > Card. > > It most definitely works with a computer driven DVI source with a > DVI->HDMI adaptor or cable, so the YUV "consumer" HDMI vs RGB DVI > computer colorspace "issue" is not a problem per se for the > Intensity card as was speculated. I have only tested with my > MacBook Pro, but I would be surprised if this was an issue with > other systems. > > jit.qt.grab finds the card just fine and will work with colormode > argb or uyvy and produce proper results either way. > > Currently the Decklink drivers support only one card. Even though > their On Air software sees both cards we have installed, quicktime > does not. Decklink is aware of this and will be supporting 2 cards > eventually with a software update, so I am told. > > I havent been able to quantify, but there is a noticeable frame lag > from the output device to the intensity card input and display. It > seems like 3-5 frames delay, not huge, but there. > > My laptop sees the Intensity card and can drive it at 1920x1080 > Interlaced or 1280x720 Progressive. I dont think all systems will > be able to see and drive the intensity card properly. A friends 12" > Powerbook did not properly see the 720P, it output 720 interlaced, > so it would not lock up at that resolution. > > Back to Jitter: > > jit.qt.grab on a 2 x 3.0 Ghz Intel Mac Pro with 8GB ram, x1900 with > 512MB Vram: > > 1920x1080 Interlaced: > > @colormode uyvy @1920x1080 to a videoplane @uyvy = 60fps > > @colormode uyvy to the cc.uyvy2rgba.jxs shader, to a jit.gl.slab > @file td.sinefold.jxs, then mixed with the original texture using > one of the composite shaders to a videoplane @ rgba, is 60 fps. > > the above, but at colormode rgba sans uyvy/rgba conversion shader > is a paltry 30 fps. :) > > 1280x720 Progressive: > > 720p @ colormode argb with the above shaders ran at 50 -55 fps, and > looks lovely being progressive and all. > > Everything else (colormode uyvy, etc) ran at 60fps, but the ARGB > progressive mode has a much much nicer image quality. Drastically > superior, why would anyone want to deal with Interlacing in this > day and age anyway? > > Color differencing (using RGB color mode @720P) > > There are very slight color shifts. Using Final Cut Pro to output > SMTPE video bars @720p. I measured the color accuracy using the > Digital Color Meter supplied by Apple. > > Local 720p Bars (in RGB as percentage) > Red : 70.6% 0. 0. > Blue: 0. 0. 70.6 % > Green: 0. 70.6 0% > > After Intensity /Jitter to the Mac Pro displayed via GL > Red: 73.3 0. 0. % > Blue: 0. 0. 73.3 % > Green: 0. 73.3 0.% > > Blacks were super black at 0% on both systems > > Pedestal was 2.0% local, 2.7% on intensity card, so some luma/gamma > shifting brighter > > The colors after going through Intensity card look really good, > and the shifts were not noticeable in any way, but they are there. > Not sure if this is a Jitter issue on a Quicktime/Decklink issue, > but, at the end of the day they are not really an issue. More > testing could reveal the source of the issue. > > I was also able to record using jit.gl.texture to jit.matrix > readback, which considering the PCIe bandwidth did not > significantly lower performance. I had a greater fps hit dropping > in a pwindow that had use onscreen 1 enabled. Recording the 720p > content to motion jpeg lowered my framerate to about 35 fps all > while driving a full screen display @ 1280x720 progressive with > slab effects enabled and mixing. > > Could not Test video out ironically because we had no HDMI viewing > monitor. Once they have the second (or hopefully more) card > supported, this will make a wonderful platform to use for HD. > > This is really good news. > > I hope this is helpful to the list. > > I hope to test on a PC shortly, but it may be sometime. > > > v a d e // > > www.vade.info > abstrakt.vade.info > > >
    • Apr 14 2007 | 9:24 pm
      The 12 inch will drive the Intensity card at 1920x1080 interlaced and 480 progressive, it just would not see the progressive 720p. The intensity will not lock to interlaced 720 :)
      On Apr 14, 2007, at 4:43 PM, subzero wrote:
      > Hello Vade, this is good news. Interesting to see how the people at > Blackmagic don't even know themselves what they actually make...;-) > Did you find out why your laptop works and the 12 inch not? does it > have to do with the graphics card? did you test with a mac pro as > input? > Best Lucas > > On Apr 13, 2007, at 1:45 AM, vade wrote: > >> Ive spent some hard earned time today with the Decklink Intensity >> Card. >> >> It most definitely works with a computer driven DVI source with a >> DVI->HDMI adaptor or cable, so the YUV "consumer" HDMI vs RGB DVI >> computer colorspace "issue" is not a problem per se for the >> Intensity card as was speculated. I have only tested with my >> MacBook Pro, but I would be surprised if this was an issue with >> other systems. >> >> jit.qt.grab finds the card just fine and will work with colormode >> argb or uyvy and produce proper results either way. >> >> Currently the Decklink drivers support only one card. Even though >> their On Air software sees both cards we have installed, quicktime >> does not. Decklink is aware of this and will be supporting 2 cards >> eventually with a software update, so I am told. >> >> I havent been able to quantify, but there is a noticeable frame >> lag from the output device to the intensity card input and >> display. It seems like 3-5 frames delay, not huge, but there. >> >> My laptop sees the Intensity card and can drive it at 1920x1080 >> Interlaced or 1280x720 Progressive. I dont think all systems will >> be able to see and drive the intensity card properly. A friends >> 12" Powerbook did not properly see the 720P, it output 720 >> interlaced, so it would not lock up at that resolution. >> >> Back to Jitter: >> >> jit.qt.grab on a 2 x 3.0 Ghz Intel Mac Pro with 8GB ram, x1900 >> with 512MB Vram: >> >> 1920x1080 Interlaced: >> >> @colormode uyvy @1920x1080 to a videoplane @uyvy = 60fps >> >> @colormode uyvy to the cc.uyvy2rgba.jxs shader, to a jit.gl.slab >> @file td.sinefold.jxs, then mixed with the original texture using >> one of the composite shaders to a videoplane @ rgba, is 60 fps. >> >> the above, but at colormode rgba sans uyvy/rgba conversion shader >> is a paltry 30 fps. :) >> >> 1280x720 Progressive: >> >> 720p @ colormode argb with the above shaders ran at 50 -55 fps, >> and looks lovely being progressive and all. >> >> Everything else (colormode uyvy, etc) ran at 60fps, but the ARGB >> progressive mode has a much much nicer image quality. Drastically >> superior, why would anyone want to deal with Interlacing in this >> day and age anyway? >> >> Color differencing (using RGB color mode @720P) >> >> There are very slight color shifts. Using Final Cut Pro to output >> SMTPE video bars @720p. I measured the color accuracy using the >> Digital Color Meter supplied by Apple. >> >> Local 720p Bars (in RGB as percentage) >> Red : 70.6% 0. 0. >> Blue: 0. 0. 70.6 % >> Green: 0. 70.6 0% >> >> After Intensity /Jitter to the Mac Pro displayed via GL >> Red: 73.3 0. 0. % >> Blue: 0. 0. 73.3 % >> Green: 0. 73.3 0.% >> >> Blacks were super black at 0% on both systems >> >> Pedestal was 2.0% local, 2.7% on intensity card, so some luma/ >> gamma shifting brighter >> >> The colors after going through Intensity card look really good, >> and the shifts were not noticeable in any way, but they are >> there. Not sure if this is a Jitter issue on a Quicktime/Decklink >> issue, but, at the end of the day they are not really an issue. >> More testing could reveal the source of the issue. >> >> I was also able to record using jit.gl.texture to jit.matrix >> readback, which considering the PCIe bandwidth did not >> significantly lower performance. I had a greater fps hit dropping >> in a pwindow that had use onscreen 1 enabled. Recording the 720p >> content to motion jpeg lowered my framerate to about 35 fps all >> while driving a full screen display @ 1280x720 progressive with >> slab effects enabled and mixing. >> >> Could not Test video out ironically because we had no HDMI viewing >> monitor. Once they have the second (or hopefully more) card >> supported, this will make a wonderful platform to use for HD. >> >> This is really good news. >> >> I hope this is helpful to the list. >> >> I hope to test on a PC shortly, but it may be sometime. >> >> >> v a d e // >> >> www.vade.info >> abstrakt.vade.info >> >> >> >
      v a d e //
      www.vade.info abstrakt.vade.info
    • May 25 2007 | 6:20 pm
      hi-
      i'm working on an interactive music therapy program with harvard med school.
      we are trying out pattr to collect data during therapy sessions and it seems to work very well for our purposes...
      however, the xml file written does not convert very easily to spreadsheet programs for data analysis.
      has anyone dealt with such issues?
      if so, do you have any advice for flexible xml parsing into spreadsheet formats?
      hope this isn't too tangential...
      thanks brian
      -----Original Message----- From: jitter-bounces@cycling74.com on behalf of vade Sent: Thu 4/12/2007 11:42 PM Subject: Re: [jitter] Decklink Intensity Card Notes - Success!
      Unfortunately, 1080p is not supported by the Intensity card, at least as stated on Decklinks tech page for the product -
      and I did not see a progressive option available in my monitors/ displays for 1920x1080.
      However, Ive been meaning to ask, is a de-interlacing shader possible/ available for 108060i mode? (or, er, any mode?)
      Also, I could see no difference with the chroma_smooth option for the uyvy2rgba shader, what is the intended purpose?
      I can post some picts of the output should it be necessary so we arent too vague. Thanks, glad its helpful.
      On Apr 12, 2007, at 8:07 PM, Joshua Kit Clayton wrote:
      > Hi Anton, > > Thanks for this info. Lots of good information. If you want to > further benchmark (i.e. above 60fps), you can disable vsync for > jit.window. > >> 1920x1080 Interlaced: > > What about 1080p 30fps? Is that supported by the card and DVI->HDMI > config? > > As for color quality in UYVY mode if it's useful for more > performance with multiple sources, you can get nicer gamma > correction looking footage from a UYVY signal by using > cc.uyvy2rgba.exp.jxs with an exponent of something like 1.2 (might > want to adjust some of the other brightness/contrast/saturation > controls to your liking too). >
      v a d e //
      www.vade.info abstrakt.vade.info