06-18-2008 01:47 AM
06-19-2008 02:35 PM
Hi Michael,
Unfortunately, none of our frame grabbers are able to natively perform the tasks you requested. To perform these operations you will need to look into purchasing one of our VideoMASTER- complete video test systems. This system can run a wide array of different video standards and can analyze both digital and analogue tasks. I have linked below where you can find additional details about this PXI system. Let me know if you have any further questions.
Testing Analog and Digital Video with LabVIEW and PXI
http://zone.ni.com/devzone/cda/pub/p/id/239
http://zone.ni.com/devzone/cda/tut/p/id/6967
Thank You,
Eric Reid
Applications Engineer
06-20-2008 04:28 PM
06-23-2008 03:11 PM
A. Well, the most important feature that we would require is the ability to save the frame as a file which contains YCrCb data, which is also sometimes refered to as YUV, or CCIR 601.
None of our frame grabbers can save a file as YUV data. You can however save as a RGB file and convert via matrices to Y’UV. The following operation will perform this transformation.
For more information on this refer to the Wikipedia source on Y’UV matrices transformations (http://en.wikipedia.org/wiki/YUV). The NI PCI 1405 can do CCIR input (http://sine.ni.com/nips/cds/view/p/lang/en/nid/14209).
B. Now the capturing in a YCrCb data format is needed for only 2 types of digital signals. What I mean is that I need only to capture a Standard Definition Video Signal, coming out from an external Serial Data Interface, and a High Definition video signal, coming from an external Serial Data Interface.
Analog signals support is only a "nice to have" option at this point.
Can you explain this process a little bit more? Our cards can do Standard definition but not High Definition video signals. If this is just serial information perhaps another card could be used.
C. There is no problem if I would be required to purchase 2 frame grabbers, one which supports storing Standard Definition Digital Signals and another for High Standard. It doesn't have to come in one device.
To intake a digital signal you will need to look into one of our high speed digitizers. There are no frame grabbers that support Standard and an High Standard digital signals.
D. Also, can anyone explain a bit on what type of files are used for storing YCrCb information ? ( Their structure, common extensions, ect.). My knowledge is not vast in this area.
I am unaware of any way to save YCrCb information other than converting to an array with RGB components.
I hope that helps Michael, let me know if you have any further questions.
Thank You,
Eric Reid
06-26-2008 06:16 PM
Hi Eric, thanks
Using a digitizer is indeed an interesting option.... very much so.
And now, another question if I may...
I've read somewhere that MPEG2 format is a stream of YCbCr data inside.
Suppose I would like to extract this data, at least a couple of lines of a frame, in Labview.
How do I get started ? Where can I get help with it ?
Regards,
Michael.
06-27-2008 06:16 PM
Hi Mike,
I don't know of a way in labVIEW to natively take in a MPEG2 file and extract
frames from it. You could however convert the MPEG data into an uncompressed
AVI and then read that in as IMAQ frames into labVIEW. I also noticed a similar
discussion to this in the labVIEW forums discussing the creating of mpeg's
http://forums.ni.com/ni/board/message?board.id=170&message.id=202758&requireLogin=False.
Thank You,
Eric Reid
08-14-2008 09:31 AM
Hi Mike,
Could you find any way to grab the frame . Would be great if you could post it. I am trying to develop a simillar program .
Thanks
12-26-2012 07:59 AM - edited 12-26-2012 08:19 AM
Hai
any one know how to display ycbcr image in labview
12-27-2012 03:37 PM
Greetings, Sankar;
You might want to post this question under a new thread - it will give it much more visibility.
However, I am not aware how we would go about displaying a YCbCr image in LabVIEW without first making the image into RGB or some such. An example of using YCbCr in LabVIEW might be found in the following link:
http://digital.ni.com/public.nsf/allkb/B692D952063765418625795D00662A31?OpenDocument
Simon P.