zapping-misc Mailing List for Zapping, a Gnome TV viewer
Status: Alpha
Brought to you by:
mschimek
You can subscribe to this list here.
2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(78) |
Sep
(63) |
Oct
(82) |
Nov
(112) |
Dec
(70) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2002 |
Jan
(63) |
Feb
(27) |
Mar
(74) |
Apr
(68) |
May
(40) |
Jun
(33) |
Jul
(18) |
Aug
(40) |
Sep
(49) |
Oct
(84) |
Nov
(33) |
Dec
(36) |
2003 |
Jan
(54) |
Feb
(41) |
Mar
(24) |
Apr
(48) |
May
(40) |
Jun
(12) |
Jul
(22) |
Aug
(35) |
Sep
(26) |
Oct
(18) |
Nov
(34) |
Dec
(25) |
2004 |
Jan
(15) |
Feb
(8) |
Mar
(8) |
Apr
(20) |
May
(11) |
Jun
(8) |
Jul
(3) |
Aug
(8) |
Sep
(5) |
Oct
(9) |
Nov
(2) |
Dec
|
2005 |
Jan
(18) |
Feb
(12) |
Mar
(9) |
Apr
(38) |
May
(12) |
Jun
(13) |
Jul
(2) |
Aug
(6) |
Sep
|
Oct
(18) |
Nov
|
Dec
|
2006 |
Jan
(5) |
Feb
(5) |
Mar
(4) |
Apr
(2) |
May
(13) |
Jun
(5) |
Jul
(11) |
Aug
|
Sep
(16) |
Oct
(2) |
Nov
(3) |
Dec
(3) |
2007 |
Jan
(2) |
Feb
|
Mar
|
Apr
(3) |
May
(1) |
Jun
|
Jul
(3) |
Aug
(3) |
Sep
(5) |
Oct
|
Nov
|
Dec
|
2008 |
Jan
(5) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(3) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2015 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(3) |
Oct
|
Nov
|
Dec
|
2019 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2022 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(2) |
Sep
(1) |
Oct
|
Nov
|
Dec
|
From: Ileana D. <ile...@gm...> - 2022-09-02 15:21:45
|
Since it has been two weeks without a reply from the previous maintainer, I am adopting zvbi for future development and created two github repositories for this project. The first includes everything in the sourceforge files tab and is archived as read-only. Release versions for zvbi are tagged. Location is https://github.com/zapping-vbi/vbi-archive The second only includes zvbi and will be used for active development. I have already made commits to update the build system and assure that it works with automake 1.16. Location is https://github.com/zapping-vbi/zvbi I will go through the sourceforge bugs list and transfer zvbi-relevant bugs to the github issues page. For anyone that created patches that have not been applied, feel free to make a pull request, but I will also be going through these patches. Please let me know if there are any issues or suggestions. Contributions are always welcome! Ileana Dumitrescu |
From: Brian E. <br...@ne...> - 2022-08-18 18:20:15
|
I expect you won't get much push-back on adopting the project. It certainly feels like abandonware. I've had a crash-bug, a with reproducible input byte sequence and speculative patch, in the ticketing system for 11 years. I applaud you for stepping up! Cheers, ~Brian Sent with [Proton Mail](https://proton.me/) secure email. ------- Original Message ------- On Thursday, August 18th, 2022 at 8:07 AM, Ileana Dumitrescu <ile...@gm...> wrote: > Hi, > > I am the Debian maintainer of zvbi/libzvbi and wondering if this upstream repository is still maintained. > > If not, I would like to adopt zvbi and address existing bugs and feature requests. In doing so, I would intend to move the source code to github, where it can be more easily maintained especially for Debian use. > > Please let me know if anyone has any issues or suggestions with this. > > Ileana Dumitrescu > > GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354 |
From: Ileana D. <ile...@gm...> - 2022-08-18 15:07:40
|
Hi, I am the Debian maintainer of zvbi/libzvbi and wondering if this upstream repository is still maintained. If not, I would like to adopt zvbi and address existing bugs and feature requests. In doing so, I would intend to move the source code to github, where it can be more easily maintained especially for Debian use. Please let me know if anyone has any issues or suggestions with this. Ileana Dumitrescu GPG Public Key: FA26 CA78 4BE1 8892 7F22 B99F 6570 EA01 146F 7354 |
From: James D'A. <ja...@im...> - 2019-10-30 12:02:00
|
Hello VBI Team. I hope this library is still somewhat active and that someone is out there. I am trying to determine whenever a CAPTION CLEAR COMMAND event occurs in Australain broadcast streams and am wondering if someone can assist. I am referring to the Australian Broadcast standards found at " https://www.freetv.com.au/wp-content/uploads/2019/08/OP-42-Closed-Captioning-Issue-5-May-2018.pdf " Note the relevant section on the first page: CAPTION CLEAR COMMAND A Command to clear any existing caption shall be included in the first two (2) seconds of a program. A Command to clear shall also be included two (2) seconds before the end of a program. A command to clear any existing caption shall be included in the first half (0.5) second of a commercial. Where closed caption data is included, the caption information should commence no earlier than a half (0.5) second after the start of active video and a caption erase signal is required (last caption time code out) not later than a half (0.5) second before the end of active video. First caption time code in will be at an arbitrary point determined by content. First of all, I believe I am correct in believing that the "Caption Clear Command" referred to in the above documents is the "C4 Erase Page" flag (Byte 9, bit 8). Is that correct? If not, then I need to find another path. So, given that that is correct, my goal was to find when this flag was being set. There appeared to be no direct way served up via the zvbi API as it looked at first that VBI header details are not directly available from within the library. But then I noticed some comments in the documentation for the 'VBI_EVENT_TTX_PAGE' event: - If any of the roll_header, *header_update* or clock_update flags - are set *ev.ttx_page.raw_header is a pointer to the raw header data* - (40 bytes), which remains valid until the event handler returns. so I thought all I would need to do is wait until the 'header_update' flag is set and then look at ev.ttx_page.raw_header[8] and see if the C4_ERASE_PAGE bit is set (the eighth bit I think) However, the header_update flag is never set. I have also tried working with the vbi_pfc_demux_new() and vbi_pfc_demux_feed_frame() calls to see if I can get a VbiPageFunctionClearCallback method but the callback is never called. Further, I only ever get VBI_EVENT_TTX_PAGE events, no matter what I set the vbi_event_handler_register flags to. I have had a detailed look at the ffmpeg, vlc and gstreamer code but none of them are going to the level of detail I am after. Can someone point me in the correct direction, perhaps with some sample code please? Kind regards James |
From: Anshul <er....@gm...> - 2015-09-28 10:09:48
|
Hello, I have dumped raw vbi file and trying to get closed caption data from it. I have taken vbi_raw_decoder structure and set its parameter to following value: *scanning = 525.* scanning was set to 525 since in GXF media type was mpeg2 525 its line per frame is also equal to 525 In GXF docs they also said that "The eight most significant bits of the 10-bit sample words shall be stored as uncompressed VBI data. The two least significant bits of each sample shall be discarded. I dont why they have removed 2 bit from lsb, they should have removed 2 bit from msb because in vanc 2 msb represent parity and not of bit 8. but I am not sure that vbi data would contain vanc or something else. so there might be some reason to remove 2 bit lsb. My Question is should I convert 720 bytes to 720word and add some dummy value in lsb. In my GXF video I dont have color difference data but I have luma data, dont know if its called luma difference data, so basically I am confused since I have not told zvbi decoder that data is luma or color difference not sure about following: rd.sampling_format = VBI_PIXFMT_YUV420; I have a chart in GXF video which say your video could be of 50Hz, 59.94Hz, 24/23.98Hz, 25Hz, 30/29.97 Hz but I have feeling that above sample rate is not what zvbi want. I have to search for saample rate some where else. so not sure about following: sampling_rate = 13.5e6; /* Hz */ In GXF specs they say that "Each line shall consist of 720 bytes of luma or color difference data." thats why I have set: bytes_per_line = 720 not sure about this too: offset = 9.7e-6 * 13.5e6; not sure about this too: start[0] = 21; count[0] = 1; not sure about this too: start[1] = 284; count[1] = 1; GXF say that Fields per frame are interlaced interlaced = TRUE; Not sure about it: synchronous = TRUE; I do want caption, may be cdat or vanc so selected since this one looks more promising vbi_raw_decoder_add_services (&my_struct_address, VBI_SLICED_CAPTION_525, 0); /* Decoding loop. Execute once for each frame. */ If some one wants to point me out with some document that would also be much help, I find very little documentation about vbi on internet. Thanks Anshul |
From: anshul <ans...@gm...> - 2015-09-22 10:21:43
|
*I solved it*, It was an error on my part, I destroyed rd after receiving slice for first time. but then I realized while debugging that Rd should be destroyed only when you are done decoding. and rd has very no relation to each slice. On Tuesday 22 September 2015 03:26 PM, anshul wrote: > hello, > > I am trying to parse raw vbi dumped from GXF file. > > What I have done so far? > > Step 1) I created a local structure of vbi_raw_decoder > > Step 2) Initialized decoder > > vbi_raw_decoder_init (&rd); > > Step3) Then Filled mine vbi specification in rd structure, like > scanning line and sampling format > > > Step 4) Calledvbi_raw_decode with initialized rd. > > Problem: I get seg-fault while decode, and that is because > vbi_raw_decode assume that I have initialized pattern inside rd > structure. so my problem is that I dont know how to initalize rd->pattern > can any point me with some working example where patter would be > initalized and I get the information of how it has to be done. > > I have not added my complete source code which use this library and > dump file of vbi. > but if it would help then I can attach or keep it on shared drive as > you wish. > > Disclaimer: I am using this library first time, so dont know about > rules and regulation of this mailing list > please pardon me and correct me if this is not the way to communicate. > > Thanks for this wonderful library > Anshul > |
From: anshul <ans...@gm...> - 2015-09-22 09:57:12
|
hello, I am trying to parse raw vbi dumped from GXF file. What I have done so far? Step 1) I created a local structure of vbi_raw_decoder Step 2) Initialized decoder vbi_raw_decoder_init (&rd); Step3) Then Filled mine vbi specification in rd structure, like scanning line and sampling format Step 4) Calledvbi_raw_decode with initialized rd. Problem: I get seg-fault while decode, and that is because vbi_raw_decode assume that I have initialized pattern inside rd structure. so my problem is that I dont know how to initalize rd->pattern can any point me with some working example where patter would be initalized and I get the information of how it has to be done. I have not added my complete source code which use this library and dump file of vbi. but if it would help then I can attach or keep it on shared drive as you wish. Disclaimer: I am using this library first time, so dont know about rules and regulation of this mailing list please pardon me and correct me if this is not the way to communicate. Thanks for this wonderful library Anshul |
From: David L. <lio...@co...> - 2013-02-11 22:57:46
|
I've been using zvbi-atsc-cc for several years to extract closed captioning from US television broadcasts. It used to work for all channels; on 2011-12-09 it stopped working for CNN and Fox News -- but continues to work great for the other channels. If anyone would like to look at this, I'm happy to contribute transport stream files. Cheers, David |
From: faginbagin <my...@hb...> - 2012-12-08 06:02:34
|
I just submitted a patch here: https://sourceforge.net/tracker/?func=detail&aid=3593886&group_id=2599&atid=302599# Details: Fixes the handling of Preamble Address Codes, Tab Offsets and Mid-Row Codes to match the behavior described in "Code of Federal Regulations (annual edition). Title 47: Telecommunication. Subpart B: Unintentional Radiators. Saturday, October 1, 2011, Section 15.119", which can be found here: http://www.gpo.gov/fdsys/pkg/CFR-2011-title47-vol1/pdf/CFR-2011-title47-vol1-sec15-119.pdf According to this document, Preamble Address Codes and Tab Offsets are non-destructive, and Mid-Row Codes are "spacing attributes which appear in the display just as if a standard space (20h) had been received" Without this patch, libzvbi's handling of Preamble Address Codes and Tab Offsets overwrite the characters between the current position and destination, and Mid-row codes do not insert a displayable space and do not advance the cursor. These problems are most noticeable with closed captions that mix normal and italic text on a single line. This patch also includes fixes required to compile 0.2.33 on debian/ubuntu distributions. See Debian bug report #602880 here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=602880 FWIW, the code is available at: https://github.com/faginbagin/libzvbi-obe-dev It is a fork of the git repo announced back in June 2011 by Kieran Kunhya for the Open Broadcast Encoder project. Regards, Helen |
From: Kieran K. <ki...@ob...> - 2011-06-25 17:56:45
|
Hello, I'm just writing to let you know that there will be some new features added to the libzvbi development tree for the Open Broadcast Encoder project. The tree can be found here https://github.com/kierank/libzvbi-obe-dev We only use the raw decoder in libzvbi, so for the time being only that part will be improved. The plan is to add support for Inverted Teletext, then later on CEA-2020 and ISO 61880-1 formats. Regards, Kieran |
From: faginbagin <my...@hb...> - 2011-06-09 03:56:16
|
Hi Brian, On 6/8/2011 7:53 PM, Brian Enigma wrote: > I have what I believe to be a simple goal that I'd like to achieve > using libzvbi, but after going through the documentation and > tinkering with some test code, I am unable to get zvbi to do what I > need. > > Basically, I have VBI bytes as input. It's not attached to video, > it's just raw ATSC "line 21" bytes, each one starting with the four > characters "GA94" and 0x03 and the other assorted header bytes, > followed by the actual 608/708 triple-byte payloads. As output, I'd > like to get callbacks for captions and XDS data so that I can > programmatically grab the parsed data. It looks like I should be > able to just instantiate a decoder (vbi_decoder_new), add an event > handler (vbi_event_handler_add), then repeatedly throw bytes at it > (vbi_decode) and get callbacks. I'm not sure I quite understand the > vbi_sliced struct. I've tried loading my raw bytes into the "data" > field of vbi_sliced (using a couple of different offsets -- including > the GA94 ATSC header, just after it, starting at the first 608 byte > triplet, etc.) with no luck. I also tried vbi_raw_decode to see if > that will take my raw bytes and package them in a vbi_sliced data > structure. So far, I haven't gotten anything to work. > > I'd like to try out and step through the example code to see what > sorts of bytes they are pushing around, but the apps that take file > inputs seem to want to initialize some /dev device that I don't have, > even when I just point them to files. (I don't have any sort of > special video capture hardware.) > > What am I doing wrong and/or what is the correct way to do this? > > -Brian I have an application that does something similar. It uses mythtv's version of ffmpeg to parse ATSC recordings to get at the EIA-608 caption data, then feeds that data to libzvbi. I use libzvbi's support for generating .png files to create images I can later use with dvdauthor's spumux to convert closed captions into DVD subtitles. If this sounds interesting, you can find more details, as well as a link to the source code here: http://www.hbuus.com/cc2subtitles/ HTH, Helen |
From: Brian E. <br...@ne...> - 2011-06-09 00:24:58
|
I have what I believe to be a simple goal that I'd like to achieve using libzvbi, but after going through the documentation and tinkering with some test code, I am unable to get zvbi to do what I need. Basically, I have VBI bytes as input. It's not attached to video, it's just raw ATSC "line 21" bytes, each one starting with the four characters "GA94" and 0x03 and the other assorted header bytes, followed by the actual 608/708 triple-byte payloads. As output, I'd like to get callbacks for captions and XDS data so that I can programmatically grab the parsed data. It looks like I should be able to just instantiate a decoder (vbi_decoder_new), add an event handler (vbi_event_handler_add), then repeatedly throw bytes at it (vbi_decode) and get callbacks. I'm not sure I quite understand the vbi_sliced struct. I've tried loading my raw bytes into the "data" field of vbi_sliced (using a couple of different offsets -- including the GA94 ATSC header, just after it, starting at the first 608 byte triplet, etc.) with no luck. I also tried vbi_raw_decode to see if that will take my raw bytes and package them in a vbi_sliced data structure. So far, I haven't gotten anything to work. I'd like to try out and step through the example code to see what sorts of bytes they are pushing around, but the apps that take file inputs seem to want to initialize some /dev device that I don't have, even when I just point them to files. (I don't have any sort of special video capture hardware.) What am I doing wrong and/or what is the correct way to do this? -Brian |
From: Ian D. <ia...@ha...> - 2011-01-11 18:18:04
|
That's close, but I'm not actually trying to view the video stream from the TV (and X isn't running). I'm interested solely in the CC stream, so I'd really only be using zvbi-ntsc-cc. I'm using the '-d' flag when running zvbi-ntsc-cc, and '-v' since it segfaults immediatly without it. The full command I'm using: zvbi-ntsc-cc -d /dev/vbi0 -c -v I try falling back to Ubuntu 6 LTS release and see if it works. A recent kernel change may be the culprit. -Ian D. On Tue, Jan 11, 2011 at 12:59:00PM -0500, Freedman, David Scott wrote: > Hi, Believe it or not, I had almost the exact same problem, although with newer kernels (IE, I had no problems with Ubuntu 06 or 07, but after 08...). I solved it by using tvtime with the following command. > > tvtime --input=1 -d /dev/vbi0 --inputwidth=640 > # for some reason you need to point the dev to the vbi device if you want closed captions to work!?!? WTF > > I always had used tvtime prior to this, but the key was telling tvtime to use this device. > > I hope this helps. > > On Jan 10, 2011, at 1:55 PM, Ian D. wrote: > > I've been trying to use my old bt878 PCI cards with zvbi-ntsc-cc to > capture CC streams. These cards worked under kernel 2.4.x but I haven't > tested them in 2.6.x. I'm not sure if the problem is with zvbi, v4l2, or > the bttv/bt878 drivers. > I have a brief writeup of the problem here: > http://ubuntuforums.org/showthread.php?t=1662245 and can provide any > other information needed. Thank you. > -I.D. > > ------------------------------------------------------------------------------ > Gaining the trust of online customers is vital for the success of any company > that requires sensitive data to be transmitted over the Web. Learn how to > best implement a security strategy that keeps consumers' information secure > and instills the confidence they need to proceed with transactions. > http://p.sf.net/sfu/oracle-sfdevnl > _______________________________________________ > Zap...@li...<mailto:Zap...@li...> > https://lists.sourceforge.net/lists/listinfo/zapping-misc > > David S. Freedman > Postdoctoral Research Associate, OCN Lab, ECE, BU > > dfr...@bu...<mailto:dfr...@bu...> > Office: + 1 (617) 358-4131 > Mobile: +1 (949) 244-0999 > |
From: Freedman, D. S. <dfr...@bu...> - 2011-01-11 18:01:07
|
Oh I forgot to mention that I start zvbi-ntsc-cc with -d /dev/vbi0 too. On Jan 10, 2011, at 1:55 PM, Ian D. wrote: I've been trying to use my old bt878 PCI cards with zvbi-ntsc-cc to capture CC streams. These cards worked under kernel 2.4.x but I haven't tested them in 2.6.x. I'm not sure if the problem is with zvbi, v4l2, or the bttv/bt878 drivers. I have a brief writeup of the problem here: http://ubuntuforums.org/showthread.php?t=1662245 and can provide any other information needed. Thank you. -I.D. ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Zap...@li...<mailto:Zap...@li...> https://lists.sourceforge.net/lists/listinfo/zapping-misc David S. Freedman Postdoctoral Research Associate, OCN Lab, ECE, BU dfr...@bu...<mailto:dfr...@bu...> Office: + 1 (617) 358-4131 Mobile: +1 (949) 244-0999 |
From: Freedman, D. S. <dfr...@bu...> - 2011-01-11 17:59:52
|
Hi, Believe it or not, I had almost the exact same problem, although with newer kernels (IE, I had no problems with Ubuntu 06 or 07, but after 08...). I solved it by using tvtime with the following command. tvtime --input=1 -d /dev/vbi0 --inputwidth=640 # for some reason you need to point the dev to the vbi device if you want closed captions to work!?!? WTF I always had used tvtime prior to this, but the key was telling tvtime to use this device. I hope this helps. On Jan 10, 2011, at 1:55 PM, Ian D. wrote: I've been trying to use my old bt878 PCI cards with zvbi-ntsc-cc to capture CC streams. These cards worked under kernel 2.4.x but I haven't tested them in 2.6.x. I'm not sure if the problem is with zvbi, v4l2, or the bttv/bt878 drivers. I have a brief writeup of the problem here: http://ubuntuforums.org/showthread.php?t=1662245 and can provide any other information needed. Thank you. -I.D. ------------------------------------------------------------------------------ Gaining the trust of online customers is vital for the success of any company that requires sensitive data to be transmitted over the Web. Learn how to best implement a security strategy that keeps consumers' information secure and instills the confidence they need to proceed with transactions. http://p.sf.net/sfu/oracle-sfdevnl _______________________________________________ Zap...@li...<mailto:Zap...@li...> https://lists.sourceforge.net/lists/listinfo/zapping-misc David S. Freedman Postdoctoral Research Associate, OCN Lab, ECE, BU dfr...@bu...<mailto:dfr...@bu...> Office: + 1 (617) 358-4131 Mobile: +1 (949) 244-0999 |
From: Ian D. <ia...@ha...> - 2011-01-11 04:57:17
|
I've been trying to use my old bt878 PCI cards with zvbi-ntsc-cc to capture CC streams. These cards worked under kernel 2.4.x but I haven't tested them in 2.6.x. I'm not sure if the problem is with zvbi, v4l2, or the bttv/bt878 drivers. I have a brief writeup of the problem here: http://ubuntuforums.org/showthread.php?t=1662245 and can provide any other information needed. Thank you. -I.D. |
From: <the...@gm...> - 2010-08-17 20:07:13
|
Hello, I am looking for a new tv app and am trying zapping. The problem is that I can't get it to run full screen. When I set it to full screen I get just a line on the screen. It is not a full width line, it covers about a third of the screen. The system is Debian Squeeze (testing), 2.6.35-5 kernel, with onboard intel graphics. The capture card is an old tv-wonder analog card. The hardware works fine in Debian Lenny (stable) using tvtime, but they changed something and tvtime will not run in Squeeze. -- if it ain't broke tweak it |
From: Mikhail R. <mr...@ra...> - 2009-10-10 19:28:59
|
Hello, I am using Debian lenny with its zapping packages: zapping 0.10cvs6, libzvbi 0.2.30. Zapping does start and show TV. However, when I try to auto scan channels or enable "capture mode", I get the message: Cannot start capturing: /tmp/buildd/zapping-0.10~cvs6/src/tveng25.c:map_xbuffers:2578: ioctl VIDIOC_REQBUFS failed: 0, Success Also I see no controls to record audio/video (the reason I want to use zapping over tvtime). However, without capture mode I understand these could be disabled. -- Yours, Mikhail Ramendik |
From: naresh i. <nar...@gm...> - 2009-06-25 10:09:58
|
Dear libzvbi members, I found libzvbi written very nicely with comments as per the Teletext spec 706. I would like to run libzvbi in VC++ platform. Basically i need Teletext decoder standalone. if i can make it standalone, its easy to integrate into my existing dvb live player. I started modifying in VC. Seems to be changes are high. My boss asked me to complete this task in 4 days. I need Teletext decoder with subtitles and other features. It would be ok even if it Linux or other platform. Kindly suggest me how to proceed? Thanks Best regards, Naresh |
From: Pádraig B. <P...@dr...> - 2009-02-13 15:49:09
|
Ed Kapitein wrote: > Hi Padraig, > > I too tried to use vbi data. in my case to extract the PDC signal. > What card are you using ? > i am not sure my card haupage pvr350 has the same chips. I'm using an empia 2883 based device, directly from Empia You can buy this as the "TubeStick hybrid" here: http://www.equinux.com/us/products/tubestick/index.html Or in the EU as "Cinergy Hybrid T USB XS FM" cheers, Pádraig. |
From: Ed K. <ed...@ka...> - 2009-02-13 15:42:05
|
Hi Padraig, I too tried to use vbi data. in my case to extract the PDC signal. What card are you using ? i am not sure my card haupage pvr350 has the same chips. Kind regards, Ed On Fri, 2009-02-13 at 14:56 +0000, Pádraig Brady wrote: > Pádraig Brady wrote: > > I'm having serious trouble with this. > > My tuner/driver on linux only provides raw VBI data. > > > > I've modified contrib/ntsc-cc.c to set: > > strict=0; > > services=VBI_SLICED_CAPTION_525 | VBI_SLICED_VBI_525; > > That's the combination I get furthest with. > > I can see the raw pattern attached with this command: > > ./zvbi-ntsc-cc --cc -v -r11 -w > > However nothing is decoded. > > Turns out this was because the em28xx driver was setting > the wrong vbi.start number. Hence VBI data was noticed > on the 12th row, but the line was reported as 17 rather than 21. > I've fixed the driver and now the decoding is done correctly. > > cheers, > Pádraig. > > ------------------------------------------------------------------------------ > Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA > -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise > -Strategies to boost innovation and cut costs with open source participation > -Receive a $600 discount off the registration fee with the source code: SFAD > http://p.sf.net/sfu/XcvMzF8H > _______________________________________________ > Zap...@li... > https://lists.sourceforge.net/lists/listinfo/zapping-misc |
From: Pádraig B. <P...@dr...> - 2009-02-13 15:13:52
|
Pádraig Brady wrote: > I'm having serious trouble with this. > My tuner/driver on linux only provides raw VBI data. > > I've modified contrib/ntsc-cc.c to set: > strict=0; > services=VBI_SLICED_CAPTION_525 | VBI_SLICED_VBI_525; > That's the combination I get furthest with. > I can see the raw pattern attached with this command: > ./zvbi-ntsc-cc --cc -v -r11 -w > However nothing is decoded. Turns out this was because the em28xx driver was setting the wrong vbi.start number. Hence VBI data was noticed on the 12th row, but the line was reported as 17 rather than 21. I've fixed the driver and now the decoding is done correctly. cheers, Pádraig. |
From: Pádraig B. <Pad...@li...> - 2009-02-09 02:06:46
|
I'm having serious trouble with this. My tuner/driver on linux only provides raw VBI data. I've modified contrib/ntsc-cc.c to set: strict=0; services=VBI_SLICED_CAPTION_525 | VBI_SLICED_VBI_525; That's the combination I get furthest with. I can see the raw pattern attached with this command: ./zvbi-ntsc-cc --cc -v -r11 -w However nothing is decoded. I enabled RAW_DECODER_PATTERN_DUMP in raw_decoder.c, but just get this for each block of VBI data read: services 0x00000060 job 1: 0x00000060 (Closed Caption 525) scan line 6: 01 00 00 00 00 00 00 80 scan line 7: 01 00 00 00 00 00 00 80 scan line 8: 01 00 00 00 00 00 00 80 scan line 9: 01 00 00 00 00 00 00 80 scan line 10: 01 00 00 00 00 00 00 80 scan line 11: 01 00 00 00 00 00 00 80 scan line 12: 01 00 00 00 00 00 00 80 scan line 13: 01 00 00 00 00 00 00 80 scan line 14: 01 00 00 00 00 00 00 80 scan line 15: 01 00 00 00 00 00 00 80 scan line 16: 01 00 00 00 00 00 00 80 scan line 17: 01 00 00 00 00 00 00 80 scan line 317: 01 00 00 00 00 00 00 80 scan line 318: 01 00 00 00 00 00 00 80 scan line 319: 01 00 00 00 00 00 00 80 scan line 320: 01 00 00 00 00 00 00 80 scan line 321: 01 00 00 00 00 00 00 80 scan line 322: 01 00 00 00 00 00 00 80 scan line 323: 01 00 00 00 00 00 00 80 scan line 324: 01 00 00 00 00 00 00 80 scan line 325: 01 00 00 00 00 00 00 80 scan line 326: 01 00 00 00 00 00 00 80 scan line 327: 01 00 00 00 00 00 00 80 scan line 328: 01 00 00 00 00 00 00 80 Your confused, Pádraig. |
From: guillaume r. <gui...@th...> - 2008-08-13 12:04:55
|
i'd like to limit the cache used by libzvbi I found the function vbi_cache_set_memory_limit surrounded by '#if 3 == VBI_VERSION_MINOR' '#endif' since VBI_VERSION_MINOR is 2 in src/version.h, it's not exported and thus not available to me. I'd like to know if it's relatively safe to chance VBI_VERSION_MINOR to 3 in order to be able to use that function? or is there another way to set cache size limit while stickign to MINOR VERSION 2? because from what I understand default cache size is 1GB, and this is something like 4 times the memory available on my system; this is somewhat not acceptable for my case. anyway, I'm quite happy with your lib and really appreciate your work :) cheers. |
From: Ed K. <ed...@ka...> - 2008-07-07 11:51:40
|
Hi all, For a home brew harddisk recorder, i want to implement PDC (vps?). But i don't seem to be able to capture any teletext pages in sliced format. So ./capture --device /dev/v4l/vbi0 --sliced | ./ttxfilter 100 | ./decode -a does not work. if i dump the sliced output to file, there is a file created, but reading from that file with decode -a only gives "decode: End of stream." I can capture teletex pages with the --dump option, but that doesn't give the wanted vps info. i am using a pvr-350 card with the ivtv drivers in an AMD 64 linux computer. alevt does work fine, so hardware seems ok. Any help is highly apreciated. Kind regards, Ed |