Closed ChrisMcAAA closed 7 years ago
Here's the log output from the format detection:
01/03/2017 13:49:32 Unknown file format /usr/local/google_hd/media/videos/BadVideoDetect.ts
01/03/2017 13:49:32 TS Filter created ( ver.2.0.9 )
01/03/2017 13:49:32 PSI Filter created ( ver.2.0.1 )
01/03/2017 13:49:32 PSI format Unknown
01/03/2017 13:49:32 TS Parser is created version 2.0.4 .
01/03/2017 13:49:32 Maxium PAT number:6 PMT number:80 Packet length:188
01/03/2017 13:49:32 PTSFIX threshold:0:0:5.000'000.0
01/03/2017 13:49:32 PTSFix is disbaled
01/03/2017 13:49:32 file /usr/local/google_hd/media/videos/BadVideoDetect.ts
01/03/2017 13:49:32 Open slot 0.
01/03/2017 13:49:32 PARSER STATUS: STREAM START
01/03/2017 13:49:32 PARSER STATUS: PARSING STREAM
01/03/2017 13:49:32 PMT-MAP Table is updated
01/03/2017 13:49:32 PAT-0:Program (total channel:1, tsid:1 )
01/03/2017 13:49:32 PMT pid:0x1000 program:0001
01/03/2017 13:49:32 Channel:1 (tsid:1) PMT pid:0x1000 Program:0001 PCR pid:0x0100 .
01/03/2017 13:49:32 Type:0x1b Pid:0x100
01/03/2017 13:49:32 Type:0x0f Pid:0x101
01/03/2017 13:49:32 TS:0 type:0x1b pid:0x100 video H264
01/03/2017 13:49:32 TS:1 type:0x0f pid:0x101 audio AAC
01/03/2017 13:49:32 PCR: pid:0x100
01/03/2017 13:49:32 *Select REMUX_FILE channel (slot:0, media:0) channel:1 tsid:1 sid:1 (1) stream:2
01/03/2017 13:49:32 ES:0:0 strmid:0xe0-0x0 esid:0x0000 video MPEG2 "open"
01/03/2017 13:49:32 ES:0:1 strmid:0xc0-0x0 esid:0x0000 audio MPEG2
01/03/2017 13:49:32 AV:0:1 audio AAC (pos:45120)
01/03/2017 13:49:32 STREAM IS NOT READY (at bytes:31457280, pos:63159352), CHECK AVAILABLE STREAMS
01/03/2017 13:49:32 INPUT|MPEG2-TS;[bf=aud;f=AAC;sr=48000;ch=2;br=0;at=ADTS-MPEG4;main=yes;tag=0101;pid=257;index=1;];
01/03/2017 13:49:32 PTS: first:0x115d82 last:0x149bde8
01/03/2017 13:49:32 Missing SYNC header 2; broken block 0
01/03/2017 13:49:32 Total input packets 169369
01/03/2017 13:49:32 ch:0: ts packets:149243 es blocks:14353
01/03/2017 13:49:32 ch:1: ts packets:11206 es blocks:1422
01/03/2017 13:49:32 ch:2: ts packets:0 es blocks:0
01/03/2017 13:49:32 ch:3: ts packets:0 es blocks:0
01/03/2017 13:49:32 ch:4: ts packets:0 es blocks:0
01/03/2017 13:49:32 ch:5: ts packets:0 es blocks:0
01/03/2017 13:49:32 ch:6: ts packets:0 es blocks:0
01/03/2017 13:49:32 ch:7: ts packets:0 es blocks:0
01/03/2017 13:49:32 TS channel closed. slot:0
01/03/2017 13:49:32 PARSER STATUS: PARSER STOP
01/03/2017 13:49:32 TS channel closed. slot:0
01/03/2017 13:49:32 TS Parser is released .
You can see in there it does find the H264 and AAC streams...but then for some reason it only uses the AAC one as part of the final format.
Here's a comparison from one that works properly:
12/12/2016 14:17:36 Unknown file format /usr/local/google_hd/media/videos/hcw_hd_pvr
2_1080i_h264_0.ts
12/12/2016 14:17:36 TS Filter created ( ver.2.0.9 )
12/12/2016 14:17:36 PSI Filter created ( ver.2.0.1 )
12/12/2016 14:17:36 PSI format Unknown
12/12/2016 14:17:36 TS Parser is created version 2.0.4 .
12/12/2016 14:17:36 Maxium PAT number:6 PMT number:80 Packet length:188
12/12/2016 14:17:36 PTSFIX threshold:0:0:5.000'000.0
12/12/2016 14:17:36 PTSFix is disbaled
12/12/2016 14:17:36 file /usr/local/google_hd/media/videos/hcw_hd_pvr2_1080i_h264_0.
ts
12/12/2016 14:17:36 Open slot 0.
12/12/2016 14:17:36 PARSER STATUS: STREAM START
12/12/2016 14:17:36 PARSER STATUS: PARSING STREAM
12/12/2016 14:17:36 PMT-MAP Table is updated
12/12/2016 14:17:36 PAT-0:Program (total channel:1, tsid:0 )
12/12/2016 14:17:36 PMT pid:0x0100 program:0001
12/12/2016 14:17:36 Channel:1 (tsid:0) PMT pid:0x0100 Program:0001 PCR pid:0x100
1 .
12/12/2016 14:17:36 Type:0x1b Pid:0x1011
12/12/2016 14:17:36 Type:0x0f Pid:0x1100
12/12/2016 14:17:36 Pid:0x1011 descriptor(18) REG(HDMV
12/12/2016 14:17:36 ES:0:0 strmid:0xe0-0x0 esid:0x0000 video MPEG2 "open"
12/12/2016 14:17:36 AV:0:0 video H264 (pos:3572)
12/12/2016 14:17:36 AV:0:1 audio AAC (pos:320)
12/12/2016 14:17:36 stream clock (GMT):{^^
12/12/2016 14:17:36 INPUT|MPEG2-TS;br=2500000;[bf=vid;f=H.264;fps=25.000000;fpsn=25; fpsd=1;ar=1.777778;arn=16;ard=9;w=1920;h=1080;lace=1;main=yes;tag=1011;pid=4113;index=0;];[bf=aud;f=AAC;sr=48000;ch=2;br=0;at=ADTS-MPEG2;main=yes;tag=1100;pid=4352;index=1;]; 12/12/2016 14:17:36 Find AVINF(pos:356260) 12/12/2016 14:17:36 Parsing is Done! 12/12/2016 14:17:36 PTS: first:0x893d last:0xad4bcd 12/12/2016 14:17:36 Missing SYNC header 1; broken block 0 12/12/2016 14:17:36 Total input packets 2787 12/12/2016 14:17:36 ch:0: ts packets:2729 es blocks:117 12/12/2016 14:17:36 ch:1: ts packets:37 es blocks:5 12/12/2016 14:17:36 ch:2: ts packets:0 es blocks:0 12/12/2016 14:17:36 ch:3: ts packets:0 es blocks:0 12/12/2016 14:17:36 ch:4: ts packets:0 es blocks:0 12/12/2016 14:17:36 ch:5: ts packets:0 es blocks:0 12/12/2016 14:17:36 ch:6: ts packets:0 es blocks:0 12/12/2016 14:17:36 ch:7: ts packets:0 es blocks:0 12/12/2016 14:17:36 TS channel closed. slot:0 12/12/2016 14:17:36 PARSER STATUS: PARSER STOP 12/12/2016 14:17:36 TS channel closed. slot:0 12/12/2016 14:17:36 TS Parser is released .
This seems like it's going to be tricky to figure out why it's failing in the native format detection code...there's an easier workaround I can do in Java which'll allow this to work if you set skip_internal_format_parser=true (i can clearly see why it's blocking live TV when that is set).
@technazz If you can build a new JAR file yourself, please do so with the latest code and confirm that my workaround allows you to watch live TV.
@Narflex OK, Ive never compiled but I will read up on it and try it out ASAP. Thanks
@Narflex Ok I get video on other streams but on the streams that i was have trouble with I get an playback exception with skip_internal_format_parser=true Here is a log sagetv_0.txt
I don't see any playback errors in that log file. Were you using SageTVClient on the local machine to play it back while running SageTV in service mode? (that's what it looks like IIRC) I'd then need the sagetvclient_0.txt log file to see what the playback exception was...everything looks fine on the server end.
I don't see a sagetvclient_0.txt log file. How do i set it to log? I don't see an option for in the properties file for the client or the server Yes it was with client on the local machine. That may be the problem if its decoder related. Let me try on my Hd300's and then
For SageTVClient logging, there should be an option in Detailed Setup->Advanced to turn on Debug Logging. You can also set debug_logging=TRUE in the SageClient.properties file.
I really should just change it so that it is just always on for everyone. :)
On Wed, Jan 4, 2017 at 11:30 AM, technazz notifications@github.com wrote:
I don't see a sagetvclient_0.txt log file. How do i set it to log? I don't see an option for in the propertied file for the client or the server Yes it was with client on the local machine. That may be the problem if its decoder related. Let me try on my Hd300's and then
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/sagetv/issues/232#issuecomment-270463473, or mute the thread https://github.com/notifications/unsubscribe-auth/ANEIDGrTixSLF0hd3CcUw4gdlCCyLRqhks5rO_M9gaJpZM4LWc1o .
-- Jeffrey Kardatzke jkardatzke@google.com Google, Inc.
Here is the log. Looks like a decoder issue?
Yeah...you somehow have selected AC3Filter for your video decoder...that definitely won't work. :)
On Wed, Jan 4, 2017 at 11:52 AM, technazz notifications@github.com wrote:
Here is the log. Looks like a decoder issue?
sagetvclient_0.txt https://github.com/google/sagetv/files/685740/sagetvclient_0.txt
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/sagetv/issues/232#issuecomment-270469149, or mute the thread https://github.com/notifications/unsubscribe-auth/ANEIDAxT3DLSblc53nsI9v-t1ujQQ-mfks5rO_h7gaJpZM4LWc1o .
-- Jeffrey Kardatzke jkardatzke@google.com Google, Inc.
I guess not. I dont use my client on the server at all. I was just doing some remote testing from work. What decoder should I install? Its been years since i had to deal with an decoder issue.
LAV Filters are popular these days.
You probably don't need to install another decoder...just select Default for the Video Decoder...or use the Microsoft one. The one you had selected was an audio decoder...so it definitely won't work.
On Wed, Jan 4, 2017 at 12:12 PM, Joseph Shuttlesworth < notifications@github.com> wrote:
LAV Filters https://github.com/Nevcairiel/LAVFilters/releases are popular these days.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/google/sagetv/issues/232#issuecomment-270473904, or mute the thread https://github.com/notifications/unsubscribe-auth/ANEIDB2eS9fFisHtJ-mN7H8B1Tt2SUJhks5rO_0WgaJpZM4LWc1o .
-- Jeffrey Kardatzke jkardatzke@google.com Google, Inc.
Tried LAV and Microsoft and they both had an exception. I will try the HD-300 in a few hours when I get home.
@Narflex I was assuming Windows 10 was being used which has been reported to not have many built in decoders.
@narflex the HD 300's play the live video fine. Has to be a decoder problem on my client that I'm not to worried about because it's headless
When this stream is recorded it will not play live. After the recording is finished it can be played back but only with Audio. Setting skip_internal_format_parser=true will allow the video and audio to be recorded but Live Tv is does not work. Attached is the log and a link to a 5 minute clip.
https://www.dropbox.com/s/q8a5qix4rqn0ksu/32645_140_1226_1616-2.ts?dl=0
sagetv_0.txt