Log in Register FAQ Memberlist Search pcHDTV Forum Index
pcHDTV Forum

pcHDTV Forum Index -> General pcHDTV topics -> dtvstream 1.0b2 available Goto page Previous  1, 2, 3, 4  Next
Post new topic  This topic is locked: you cannot edit posts or make replies. View previous topic :: View next topic 
PostPosted: Wed Dec 15, 2004 2:48 pm Reply with quote
Scott Larson
 
Joined: 15 Oct 2003
Posts: 713
Location: Portland, OR




Months ago I had dtvstream dump core thus not recording a program. It happened again but I know what caused it this time: the TV station dropping off the air.
View user's profile Send private message
1.5 drivers with dtvstream
PostPosted: Sat Dec 25, 2004 5:04 am Reply with quote
inkling
 
Joined: 05 Feb 2004
Posts: 342




mspice wrote:
<cut>
I checked and all of the sync errors are excatly 96256 bytes appart. Is that significant at all? Is it possible that the stations in my area send longer/out of spec packets?
</cut>


If the station was sending out of ATSC spec, they would have viewers, advertisers and the FCC on them about it. That's not to say it won't happen, as technical difficulties are to be expected with any new technology.

Sometimes, the stations here forget to plug the audio patch cable in, or so it seems from the receiving end.

Other times their carrier vanishes into the ether, for several hours, in the middle of the day.

Neither failure can be blamed on solar storms or propagation.

LOTR on WB had the oddest glitches coming back from some commercial breaks. They weren't signal strength nor multipath related, it was glitched from the studio. It was a large purple splotch on the left side. Had to skip past it, as xine would stall every time it hit it the purple media eater.

Saw some similar glitches during World Series on FOX.

Are you able to run the 1.5 drivers with kernel 2.6 and did it solve the recurrent glitching?

I've glanced at the data streams generated by pchdtvr with the new drivers and they look OK.

Should I look closer?

-ink
View user's profile Send private message
PostPosted: Sat Dec 25, 2004 3:54 pm Reply with quote
Scott Larson
 
Joined: 15 Oct 2003
Posts: 713
Location: Portland, OR




Well, here's an example that's happening right now. My CBS station uses a Windows machine to generate their PSIP data. Often it will send out garbage unless they reboot it constantly. Since today is Christmas there's no one at the station there to reboot it so it's causing dtvstream to crash:

Code:
(gdb) r  -c 40 -q -v
Starting program: dtvstream -c 40 -q -v
[New Thread 16384 (LWP 15055)]
Tuned "/dev/dtv" to channel 40.
Lost sync at input offset 0
Achieved sync after 148 bytes.
ERROR in TS 0x1ffb pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1d08 pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1e01 pkt Continuity Count - expected 4 got 3
ERROR in TS 0x1e01 pkt Continuity Count - expected 5 got 4
ERROR in TS 0x1e01 pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1e01 pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1e01 pkt Continuity Count - expected 8 got 7
ERROR in TS 0x1e01 pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1e01 pkt Continuity Count - expected 10 got 9
ERROR in TS 0x1e01 pkt Continuity Count - expected 11 got 10
ERROR in TS 0x1e17 pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1e17 pkt Continuity Count - expected 8 got 7
ERROR in TS 0x1e17 pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1e17 pkt Continuity Count - expected 10 got 9
ERROR in TS 0x1d01 pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1d01 pkt Continuity Count - expected 13 got 12
ERROR in TS 0x1e0f pkt Continuity Count - expected 4 got 3
ERROR in TS 0x1ffb pkt Continuity Count - expected 13 got 12
ERROR in TS 0x1ffb pkt Continuity Count - expected 14 got 13
ERROR in TS 0x1ffb pkt Continuity Count - expected 15 got 14
 
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 15055)]
0x080548e5 in check_crc ()
(gdb) bt
#0  0x080548e5 in check_crc ()
#1  0x0804fa90 in atsc_tables ()
#2  0x0804f040 in process_packet ()
#3  0x08049d76 in scan_packets ()
#4  0x08049b93 in main ()
#5  0x4008f917 in __libc_start_main () from /lib/libc.so.6
(gdb) q

xine and mplayer and even psipguide aren't crashing. Is there any way to get dtvstream to ignore the bad PSIP data?
View user's profile Send private message
PostPosted: Sat Dec 25, 2004 3:58 pm Reply with quote
Scott Larson
 
Joined: 15 Oct 2003
Posts: 713
Location: Portland, OR




Here's a better stack trace:
Code:
Lost sync at input offset 0
Achieved sync after 121 bytes.
ERROR in TS 0x40 pkt Continuity Count - expected 1 got 0
ERROR in TS 0x30 pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1ffb pkt Continuity Count - expected 5 got 4
ERROR in TS 0x1ffb pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1e01 pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1e01 pkt Continuity Count - expected 13 got 12
ERROR in TS 0x1e01 pkt Continuity Count - expected 14 got 13
ERROR in TS 0x1e01 pkt Continuity Count - expected 15 got 14
ERROR in TS 0x1ffb pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1ffb pkt Continuity Count - expected 8 got 7
ERROR in TS 0x1ffb pkt Continuity Count - expected 9 got 8
 
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 15122)]
0x080548e5 in check_crc (buf=0x80a8000 <Address 0x80a8000 out of bounds>,
    len=4294967295, crc=15597568) at rt_atsc_parser_mod.c:6829
6829             next_byte = *buf++;
(gdb) bt
#0  0x080548e5 in check_crc (buf=0x80a8000 <Address 0x80a8000 out of bounds>,
    len=4294967295, crc=15597568) at rt_atsc_parser_mod.c:6829
#1  0x0804fa90 in atsc_tables (buf_hdr_ptr=0x80a6aa0, ts_control_ptr=0x80a570c)
    at rt_atsc_parser_mod.c:3072
#2  0x0804f040 in process_packet (packet_ptr=0x80a60f8 "G\037?\030?",
    do_init=0 '\0') at rt_atsc_parser_mod.c:2505
#3  0x08049d76 in scan_packets () at dtvstream.c:576
#4  0x08049b93 in main (argc=0, argv=0xbffffbb8) at dtvstream.c:488
#5  0x4008f917 in __libc_start_main () from /lib/libc.so.6
(gdb)
View user's profile Send private message
PostPosted: Sat Dec 25, 2004 7:46 pm Reply with quote
pdicamillo
 
Joined: 09 Mar 2004
Posts: 68
Location: Needham, MA




Scott Larson wrote:
Is there any way to get dtvstream to ignore the bad PSIP data?


If you have dtvstream save all the packets by using "-p all", then it won't attempt to analyze the data, and you won't get errors like that. However, when you select a particular stream, there's no way to avoid bugs in the stream parser.

I've been testing a new version of dtvstream, 1.1, which may solve your problem. Here's a list of changes:
Quote:

1. Add SIGTERM (kill) to signals that are handled.

2. Support -a "*" to analyze all packets. When * is specified, if
a time limit is specified, it applies to analyzing as well as
processing.

3. Fixed some bugs in the parser, and added checks for problems due
to bad streams

4. Analyzing as well as processing can be interrupted and display
partial results.

5. Minor improvements in stream listing text. Also, the list is now
sorted by stream number.

6. Added status output and options.

7. Added -b option to begin reading a disk file at a specified
offset.


Number 3 is a potential fix for the problem you're having. Please try the new version and let me know if it works any better.

Here are the URLs for downloading version 1.1:

Linux binary:
http://buzzlabs.com/~peter/dtvstream-linux-1.1.tar.gz

Mac OS X binary:
http://buzzlabs.com/~peter/dtvstream-osx-1.1.tar.gz

Source:
http://buzzlabs.com/~peter/dtvstream-source-1.1.tar.gz
View user's profile Send private message AIM Address
PostPosted: Sat Dec 25, 2004 11:02 pm Reply with quote
Scott Larson
 
Joined: 15 Oct 2003
Posts: 713
Location: Portland, OR




This new version of dtvstream does handle the bad PSIP data correctly. It prints a zillion errors but it doesn't crash. I feel more confident that this version won't die and lose the end of my program.
Code:

bash-2.05b$ ./dtvstream -i ../badpsip.ts -q
ERROR in TS 0x1d01 pkt Continuity Count - expected 8 got 7
ERROR in TS 0x1ffb pkt Continuity Count - expected 0 got 15
ERROR in TS 0x1ffb pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1ffb pkt Continuity Count - expected 2 got 1
ERROR in TS 0x1ffb pkt Continuity Count - expected 3 got 2
ERROR in TS 0x1d01 pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1e80 pkt Continuity Count - expected 15 got 14
ERROR in TS 0x1e80 pkt Continuity Count - expected 0 got 15
ERROR in TS 0x40 pkt Continuity Count - expected 2 got 1
ERROR in TS 0x0 pkt Continuity Count - expected 4 got 3
ERROR in TS 0x30 pkt Continuity Count - expected 3 got 2
ERROR in TS 0x1ffb pkt Continuity Count - expected 4 got 3
ERROR in TS 0x1ffb pkt Continuity Count - expected 5 got 4
ERROR in TS 0x1ffb pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1ffb pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1ffb pkt Continuity Count - expected 8 got 7
ERROR in TS 0x1ffb pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1ffb pkt Continuity Count - expected 10 got 9
ERROR in TS 0x1d02 pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1d02 pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1d02 pkt Continuity Count - expected 8 got 7
ERROR in TS 0x1d02 pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1d09 pkt Continuity Count - expected 10 got 9
ERROR in TS 0x1d09 pkt Continuity Count - expected 11 got 10
ERROR in TS 0x1e80 pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1e01 pkt Continuity Count - expected 10 got 9
ERROR in TS 0x1e01 pkt Continuity Count - expected 11 got 10
ERROR in TS 0x1e01 pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1e01 pkt Continuity Count - expected 13 got 12
ERROR in TS 0x1e01 pkt Continuity Count - expected 14 got 13
ERROR in TS 0x1e01 pkt Continuity Count - expected 15 got 14
ERROR in TS 0x1e01 pkt Continuity Count - expected 0 got 15
ERROR in TS 0x1e01 pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1d01 pkt Continuity Count - expected 10 got 9
ERROR in TS 0x1d01 pkt Continuity Count - expected 11 got 10
ERROR in TS 0x1e02 pkt Continuity Count - expected 2 got 1
ERROR in TS 0x1e02 pkt Continuity Count - expected 3 got 2
ERROR in TS 0x1ffb pkt Continuity Count - expected 11 got 10
ERROR in TS 0x1ffb pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1ffb pkt Continuity Count - expected 13 got 12
ERROR in TS 0x1ffb pkt Continuity Count - expected 14 got 13
ERROR in TS 0x1e09 pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1e17 pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1e01 pkt Continuity Count - expected 2 got 1
ERROR in TS 0x1e01 pkt Continuity Count - expected 3 got 2
ERROR in TS 0x1e01 pkt Continuity Count - expected 4 got 3
ERROR in TS 0x1e09 pkt Continuity Count - expected 8 got 7
ERROR in TS 0x1e09 pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1e17 pkt Continuity Count - expected 2 got 1
ERROR in TS 0x1e17 pkt Continuity Count - expected 3 got 2
ERROR in TS 0x1e17 pkt Continuity Count - expected 4 got 3
ERROR in TS 0x1e17 pkt Continuity Count - expected 5 got 4
ERROR in TS 0x1e17 pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1e17 pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1e17 pkt Continuity Count - expected 8 got 7
ERROR in TS 0x1e17 pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1d01 pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1d01 pkt Continuity Count - expected 13 got 12
ERROR in TS 0x1e17 pkt Continuity Count - expected 10 got 9
ERROR in TS 0x1ffb pkt Continuity Count - expected 15 got 14
ERROR in TS 0x1ffb pkt Continuity Count - expected 0 got 15
ERROR in TS 0x1ffb pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1ffb pkt Continuity Count - expected 2 got 1
ERROR in TS 0x1e01 pkt Continuity Count - expected 5 got 4
ERROR in TS 0x1e02 pkt Continuity Count - expected 4 got 3
ERROR in TS 0x40 pkt Continuity Count - expected 3 got 2
ERROR in TS 0x30 pkt Continuity Count - expected 4 got 3
ERROR in TS 0x1ffb pkt Continuity Count - expected 3 got 2
ERROR in TS 0x1ffb pkt Continuity Count - expected 4 got 3
ERROR in TS 0x1e17 pkt Continuity Count - expected 11 got 10
ERROR in TS 0x1e17 pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1e17 pkt Continuity Count - expected 13 got 12
ERROR in TS 0x1d01 pkt Continuity Count - expected 14 got 13
ERROR in TS 0x1d01 pkt Continuity Count - expected 15 got 14
ERROR in TS 0x1e80 pkt Continuity Count - expected 2 got 1
ERROR in TS 0x1e17 pkt Continuity Count - expected 14 got 13
ERROR in TS 0x1ffb pkt Continuity Count - expected 5 got 4
ERROR in TS 0x1ffb pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1ffb pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1ffb pkt Continuity Count - expected 8 got 7
ERROR in TS 0x1e0d pkt Continuity Count - expected 15 got 14
ERROR in TS 0x1e0d pkt Continuity Count - expected 0 got 15
ERROR in TS 0x1e80 pkt Continuity Count - expected 3 got 2
ERROR in TS 0x1e0d pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1e0d pkt Continuity Count - expected 2 got 1
ERROR in TS 0x1e0d pkt Continuity Count - expected 3 got 2
ERROR in TS 0x1e0e pkt Continuity Count - expected 15 got 14
ERROR in TS 0x1e0e pkt Continuity Count - expected 0 got 15
ERROR in TS 0x1e0e pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1e0e pkt Continuity Count - expected 2 got 1
ERROR in TS 0x1e17 pkt Continuity Count - expected 15 got 14
ERROR in TS 0x1d09 pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1ffb pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1ffb pkt Continuity Count - expected 10 got 9
ERROR in TS 0x1ffb pkt Continuity Count - expected 11 got 10
ERROR in TS 0x1ffb pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1d09 pkt Continuity Count - expected 13 got 12
ERROR in TS 0x1e80 pkt Continuity Count - expected 4 got 3
ERROR in TS 0x1e01 pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1e01 pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1e01 pkt Continuity Count - expected 8 got 7
ERROR in TS 0x1e01 pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1e01 pkt Continuity Count - expected 10 got 9
ERROR in TS 0x1d09 pkt Continuity Count - expected 14 got 13
ERROR in TS 0x1d01 pkt Continuity Count - expected 0 got 15
ERROR in TS 0x1d01 pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1d09 pkt Continuity Count - expected 15 got 14
ERROR in TS 0x1e01 pkt Continuity Count - expected 11 got 10
ERROR in TS 0x1e01 pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1e01 pkt Continuity Count - expected 13 got 12
ERROR in TS 0x1e01 pkt Continuity Count - expected 14 got 13
ERROR in TS 0x1ffb pkt Continuity Count - expected 13 got 12
ERROR in TS 0x1ffb pkt Continuity Count - expected 14 got 13
ERROR in TS 0x1ffb pkt Continuity Count - expected 15 got 14
ERROR in TS 0x1ffb pkt Continuity Count - expected 0 got 15
ERROR in TS 0x1e01 pkt Continuity Count - expected 15 got 14
ERROR in TS 0x40 pkt Continuity Count - expected 4 got 3
ERROR in TS 0x1e01 pkt Continuity Count - expected 0 got 15
ERROR in TS 0x30 pkt Continuity Count - expected 5 got 4
ERROR in TS 0x1ffb pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1ffb pkt Continuity Count - expected 2 got 1
ERROR in TS 0x1d02 pkt Continuity Count - expected 10 got 9
ERROR in TS 0x1d02 pkt Continuity Count - expected 11 got 10
ERROR in TS 0x1d01 pkt Continuity Count - expected 2 got 1
ERROR in TS 0x1d01 pkt Continuity Count - expected 3 got 2
ERROR in TS 0x1d02 pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1d02 pkt Continuity Count - expected 13 got 12
ERROR in TS 0x1d02 pkt Continuity Count - expected 14 got 13
ERROR in TS 0x1d02 pkt Continuity Count - expected 15 got 14
ERROR in TS 0x1d02 pkt Continuity Count - expected 0 got 15
ERROR in TS 0x1e01 pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1e02 pkt Continuity Count - expected 5 got 4
ERROR in TS 0x1ffb pkt Continuity Count - expected 3 got 2
ERROR in TS 0x1ffb pkt Continuity Count - expected 4 got 3
ERROR in TS 0x1ffb pkt Continuity Count - expected 5 got 4
ERROR in TS 0x1ffb pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1e02 pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1d01 pkt Continuity Count - expected 4 got 3
ERROR in TS 0x1d01 pkt Continuity Count - expected 5 got 4
ERROR in TS 0x0 pkt Continuity Count - expected 5 got 4
ERROR in TS 0x1e80 pkt Continuity Count - expected 5 got 4
ERROR in TS 0x1ffb pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1e04 pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1e80 pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1ffb pkt Continuity Count - expected 8 got 7
ERROR in TS 0x1ffb pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1ffb pkt Continuity Count - expected 10 got 9
ERROR in TS 0x1ffb pkt Continuity Count - expected 11 got 10
ERROR in TS 0x1e02 pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1d03 pkt Continuity Count - expected 0 got 15
ERROR in TS 0x1d03 pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1d03 pkt Continuity Count - expected 2 got 1
ERROR in TS 0x40 pkt Continuity Count - expected 5 got 4
ERROR in TS 0x30 pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1ffb pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1ffb pkt Continuity Count - expected 13 got 12
ERROR in TS 0x1ffb pkt Continuity Count - expected 14 got 13
ERROR in TS 0x1ffb pkt Continuity Count - expected 15 got 14
ERROR in TS 0x1ffb pkt Continuity Count - expected 0 got 15
ERROR in TS 0x1ffb pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1e80 pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1d01 pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1d01 pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1e01 pkt Continuity Count - expected 2 got 1
ERROR in TS 0x1e01 pkt Continuity Count - expected 3 got 2
ERROR in TS 0x1e01 pkt Continuity Count - expected 4 got 3
ERROR in TS 0x1e01 pkt Continuity Count - expected 5 got 4
ERROR in TS 0x1e01 pkt Continuity Count - expected 6 got 5
ERROR in TS 0x1e01 pkt Continuity Count - expected 7 got 6
ERROR in TS 0x1e01 pkt Continuity Count - expected 8 got 7
ERROR in TS 0x1e01 pkt Continuity Count - expected 9 got 8
ERROR in TS 0x1e17 pkt Continuity Count - expected 0 got 15
ERROR in TS 0x1e17 pkt Continuity Count - expected 1 got 0
ERROR in TS 0x1e17 pkt Continuity Count - expected 2 got 1
ERROR in TS 0x1e17 pkt Continuity Count - expected 3 got 2
ERROR in TS 0x1e01 pkt Continuity Count - expected 10 got 9
ERROR in TS 0x1e01 pkt Continuity Count - expected 11 got 10
ERROR in TS 0x1e01 pkt Continuity Count - expected 12 got 11
ERROR in TS 0x1e17 pkt Continuity Count - expected 4 got 3
Stream contains 2 program(s).
    Program 3:
        Video (MPEG-2)
        Audio (Dolby AC-3)
        Audio (Dolby AC-3)
    Program 4:
        Video (MPEG-2)
        Audio (Dolby AC-3)
        Audio (Dolby AC-3)
bash-2.05b$


Someone got around to rebooting the PC at the station but I saved some of the bad stream to test with.
View user's profile Send private message
PostPosted: Mon Dec 27, 2004 9:28 am Reply with quote
johnclubvec
 
Joined: 17 Nov 2004
Posts: 20
Location: Cambridge, Massachusetts




Peter and pchdtv-tech,

I'm using gcc 3.2.3 and kernel 2.6.7.

Neither dtvstream 1.0b2 nor 1.1 compile against the pcHDTVrev.1.5 driver.

First, as first noted in a post by ink, I think, as in other applications like xine and pchdtvr, there are the errors generated by appearances of "__user" in videodev.h and videodev2.h. However, even after removing those, I still get:

In file included from /usr/include/linux/videodev.h:9,
from tune_to_channel.c:3:
/usr/include/linux/videodev2.h:380: field `timestamp' has incomplete type
make: *** [dtvstream] Error 1

I don't see what's so "incomplete" about the naming of 'timestamp' in videodev2.h, so I'm at a loss.

John Kelleher
View user's profile Send private message
PostPosted: Mon Dec 27, 2004 11:38 pm Reply with quote
cbsmith
Guest
 




johnclubvec wrote:

...
John Kelleher

John, perhaps this is the situation, which happens so rarely, that there's a good reason for not using your real name:wink: I'm sure there are several of people on this forum that arn't aware you're not John Kelleher, the founder.
PostPosted: Tue Dec 28, 2004 5:30 am Reply with quote
johnclubvec
 
Joined: 17 Nov 2004
Posts: 20
Location: Cambridge, Massachusetts




http://pchdtv.com/forum/viewtopic.php?t=273
View user's profile Send private message
PostPosted: Tue Dec 28, 2004 9:29 am Reply with quote
cbsmith
Guest
 




I've seen that, otherwise how would I not know it wasn't the same person but still, not everyone have read that.
PostPosted: Tue Dec 28, 2004 9:46 am Reply with quote
johnclubvec
 
Joined: 17 Nov 2004
Posts: 20
Location: Cambridge, Massachusetts




Site monitor:

I am stopping my watching of this topic because of cbsmith's off-topic and unhelpful posts.
View user's profile Send private message
PostPosted: Tue Dec 28, 2004 10:04 am Reply with quote
cbsmith
Guest
 




johnclubvec wrote:
Site monitor:

I am stopping my watching of this topic because of cbsmith's off-topic and unhelpful posts.

I didn't mean to piss you off, I only brought it up because it confused me for a few seconds until I realized I read before that you're the fake John. Anyhow, I didn't know you're so touchy, keep the name, I don't care that much, not that big a deal. I'll drop it now as itt is off not realted to this thread.

</off-topic>
compiling dtvstream 1.1
PostPosted: Thu Jan 27, 2005 2:56 pm Reply with quote
inkling
 
Joined: 05 Feb 2004
Posts: 342




johnclubvec wrote:
In file included from /usr/include/linux/videodev.h:9,
from tune_to_channel.c:3:
/usr/include/linux/videodev2.h:380: field `timestamp' has incomplete type
make: *** [dtvstream] Error 1

I don't see what's so "incomplete" about the naming of 'timestamp' in videodev2.h, so I'm at a loss.

John Kelleher


I finally got around to compiling dtvstream. Had to use Makefile.notune. There is something odd about the typedef of timestamp that is confusing it. Odder still, the program isn't using v4l2.

I don't need the tuner portion anyway. pchdtvr does all the tuning and capture work.

-ink
View user's profile Send private message
dtvstream 1.1
PostPosted: Fri Jan 28, 2005 2:06 am Reply with quote
inkling
 
Joined: 05 Feb 2004
Posts: 342




dtvstream 1.1 is pretty nice.

Just finished using tsc to filter the raw stream into cuts, and dtvstream to extract a single program from each cut.

I mananged to get about 37 filtered minutes burned to DVD, 1080i stream. It plays back fine from the DVD, with xine-hd. Didn't even have to specifiy the program number.

That's good stuff, man.

-ink
View user's profile Send private message
PostPosted: Fri Mar 04, 2005 2:39 pm Reply with quote
kyoo
Guest
 




I cannot find a link that works to download dtvstream.
dtvstream 1.0b2 available
  pcHDTV Forum Index -> General pcHDTV topics
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT - 7 Hours  
Page 3 of 4  
Goto page Previous  1, 2, 3, 4  Next
  
  
 Post new topic  This topic is locked: you cannot edit posts or make replies.  


Powered by phpBB © 2001-2003 phpBB Group
Theme created by Vjacheslav Trushkin