Mailing List Archive: MythTV: Dev

State of Firewire

Index | Next | Previous | View Threaded

mitchell.gore at gmail

Jun 15, 2009, 11:39 AM

Post #1 of 10 (1047 views)
Permalink

State of Firewire

Hi,

I am using Mythbuntu weekly builds Trunk r20673. Trying to add a firewire
card.

test-mpeg2 and firewire_tester works 100% but myth fails to record any data.

Info:
STB: SA8300HD
MB: M2NPV-VM (onboard nvidia firewire)

I have added the card in setup and configured a channel changer. Everything
seems to be working. When i record a show i get a 5.1kb file. If i view
live tv all i see is a black screen w/ OSD. Myth doesnt even error out.

When a recording occurs i can use firewire_tester and get packets. Also,
test-mpeg2 works. It seems there is something myth is doint internally and
not dumping the stream to disk.

some logs:
mitchell[at]mythtv:~$ sudo ./firewire_tester -p -P 0 -n 1 -r 5
Action: Test P2P connection 5 times, node 1, channel 1
P2P: Testing...Success, 125 packets received
P2P: Testing...Success, 373 packets received
P2P: Testing...Success, 256 packets received
P2P: Testing...Success, 299 packets received
P2P: Testing...Success, 265 packets received

mitchell[at]mythtv:~$ plugreport
Host Adapter 0
==============

Node 0 GUID 0x0011d800018ee05d
------------------------------
libiec61883 error: error reading oMPR
libiec61883 error: error reading iMPR

Node 1 GUID 0x0022cecc76b00000
------------------------------
oMPR n_plugs=1, data_rate=2, bcast_channel=63
oPCR[0] online=1, bcast_connection=0, n_p2p_connections=4
channel=1, data_rate=1, overhead_id=0, payload=146
iMPR n_plugs=0, data_rate=2

mitchell[at]mythtv:~$ test-mpeg2 -r 1 > file.mpg
libiec61883 warning: Overlayed connection on channel 1.
You may need to manually set the channel on the receiving node.
Starting to receive
^Cdone.
mitchell[at]mythtv:~$ ls -lh
-rw-r--r-- 1 mitchell mitchell 12M 2009-06-15 13:14 test.mpg

mythbackend -v channel:
2009-06-15 11:33:08.116 AUTO-Startup assumed
2009-06-15 11:33:08.142 TVRec(3): ASK_RECORDING 3 0 0 0
2009-06-15 11:33:08.225 TVRec(3): Changing from None to Watching
RecordingOnly
2009-06-15 11:33:08.227 TVRec(3): HW Tuner: 3->3
2009-06-15 11:33:08.228 FireChan(0022CECC76B00000): Open()
2009-06-15 11:33:08.234 FireChan(0022CECC76B00000): SetChannelByString(514)
2009-06-15 11:33:08.241 External channel change: sa8300_ch $1 514
2009-06-15 11:33:08.245 Waiting for External Tuning program to exit
Changing channel 514
2009-06-15 11:33:08.537 ret_pid(532) child(532) status(0x0)
2009-06-15 11:33:08.537 External Tuning program no longer running
2009-06-15 11:33:08.537 External Tuning program exited with no error
2009-06-15 11:33:08.537 FireChan(0022CECC76B00000): SetChannelByString(514)
success
2009-06-15 11:33:08.537 FireChan(0022CECC76B00000): Open()
2009-06-15 11:33:08.538 FireSM(0022CECC76B00000): ctor
2009-06-15 11:33:08.538 SM(0022CECC76B00000)::AddFlags: Seen() Match()
Wait(Sig,)
2009-06-15 11:33:08.538 FireDev(0022CECC76B00000): Requesting STB Power
State
2009-06-15 11:33:08.539 FireDev(0022CECC76B00000): STB Power State: On
2009-06-15 11:33:08.547 DTVSM(0022CECC76B00000)::SetProgramNumber(1):
2009-06-15 11:33:08.547 SM(0022CECC76B00000)::RemoveFlags: Seen(PMT,Crypt,)
Match(PMT,Crypt,) Wait()
2009-06-15 11:33:08.548 SM(0022CECC76B00000)::AddFlags: Seen() Match()
Wait(PMT,)
2009-06-15 11:33:08.548 SM(0022CECC76B00000)::AddFlags: Seen() Match()
Wait(PAT,PMT,Pos,)
2009-06-15 11:33:08.548 SM(0022CECC76B00000)::Start: begin
2009-06-15 11:33:08.548 FireDev(0022CECC76B00000): Requesting STB Power
State
2009-06-15 11:33:08.548 SM(0022CECC76B00000)::Start: end
2009-06-15 11:33:08.550 FireDev(0022CECC76B00000): STB Power State: On
2009-06-15 11:33:08.550 SM(0022CECC76B00000)::AddFlags: Seen(STB,)
Match(STB,) Wait()
2009-06-15 11:33:08.551 FireSM(0022CECC76B00000): RunTableMonitor(): --
begin
2009-06-15 11:33:08.551 FireSM(0022CECC76B00000): UpdateValues() -- Waiting
for table monitor to start
2009-06-15 11:33:08.551 FireSM(0022CECC76B00000): UpdateValues() -- Table
monitor started
libiec61883 warning: Overlayed connection on channel 1.
You may need to manually set the channel on the receiving node.
2009-06-15 11:33:08.560 LFireDev(0022CECC76B00000): Buffered packets 2000
(8000 KB)
2009-06-15 11:33:08.560 AutoExpire: CalcParams(): Max required Free Space:
3.0 GB w/freq: 15 min
2009-06-15 11:33:08.562 Started recording: My Dog Skip: channel 3514 on
cardid 3, sourceid 3
2009-06-15 11:33:08.568 scheduler: Started recording: My Dog Skip: channel
3514 on cardid 3, sourceid 3
2009-06-15 11:33:08.992 TVRec(4): ASK_RECORDING 4 0 0 0
2009-06-15 11:33:13.023 mythbackend: Running housekeeping thread

I looked thru the dev and commits messages and didnt really see anything
releavant to this issue. Are others using firewire on trunk?

--
Mitchell

bmayland+mythtv at capnbry

Jun 22, 2009, 8:56 AM

Post #2 of 10 (895 views)
Permalink

Re: State of Firewire [In reply to]

Mitch Gore wrote:
> test-mpeg2 and firewire_tester works 100% but myth fails to record any
> data.
> 2009-06-15 11:33:08.548 SM(0022CECC76B00000)::AddFlags: Seen() Match()
> Wait(PAT,PMT,Pos,)
Looks like your firewire box might not be sending out PAT/PMT tables
needed by MythTV's recorder. Try this test:
1) Record a stream using test-mpeg2 for 10 seconds or s
2) Use dvbsnoop to look through the file for a PAT:
dvbsnoop -s ts -if TESTFILENAME | grep "PID: 0"

Where TESTFILENAME is your file recorded with test-mpeg2. If your cable
box is like mine, you see a ton of "PID: 8191", some of another PID,
then very few (percentage wise) of another PID. If this is all you see,
congratulations, myth can't find your program in the stream!

If this is the case, do not despair, for I can supply you with a patch
that adds PID autodetect and fixes the problem completely. Apply
against libs/libmythtv/
http://capnbry.net/~bmayland/fi/code/sigmon.diff

If responding, make sure you CC my main email address because I rarely
check the list.

_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

mitchell.gore at gmail

Jun 22, 2009, 9:21 AM

Post #3 of 10 (897 views)
Permalink

Re: State of Firewire [In reply to]

On Mon, Jun 22, 2009 at 10:56 AM, Bryan Mayland
<bmayland+mythtv[at]capnbry.net<bmayland%2Bmythtv[at]capnbry.net>
> wrote:

> Mitch Gore wrote:
>
>> test-mpeg2 and firewire_tester works 100% but myth fails to record any
>> data.
>> 2009-06-15 11:33:08.548 SM(0022CECC76B00000)::AddFlags: Seen() Match()
>> Wait(PAT,PMT,Pos,)
>>
> Looks like your firewire box might not be sending out PAT/PMT tables
> needed by MythTV's recorder. Try this test:
> 1) Record a stream using test-mpeg2 for 10 seconds or s
> 2) Use dvbsnoop to look through the file for a PAT:
> dvbsnoop -s ts -if TESTFILENAME | grep "PID: 0"
>
> Where TESTFILENAME is your file recorded with test-mpeg2. If your cable
> box is like mine, you see a ton of "PID: 8191", some of another PID,
> then very few (percentage wise) of another PID. If this is all you see,
> congratulations, myth can't find your program in the stream!
>
> If this is the case, do not despair, for I can supply you with a patch
> that adds PID autodetect and fixes the problem completely. Apply
> against libs/libmythtv/
> http://capnbry.net/~bmayland/fi/code/sigmon.diff<http://capnbry.net/%7Ebmayland/fi/code/sigmon.diff>
>
> If responding, make sure you CC my main email address because I rarely
> check the list.
>
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev[at]mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>

Bryan, Thank You for the reply.

So i install dvbsnoob and ran it on a test-mpeg2 file. When i Grep'ed for
"PID: 0" I got nothing. I then did a grep for just PID. Here is what I
see:

dvbsnoop -s ts -if test.mpg | grep "PID:"
TS-Packet: 00000449 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000450 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000451 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000452 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000453 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000454 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000455 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000456 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000457 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000458 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000459 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000460 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000461 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000462 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000463 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000464 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000465 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000466 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 67 (0x0043) [= ]
TS-Packet: 00000467 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000468 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000469 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000470 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000471 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000472 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000473 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000474 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000475 PID: (Unkown PID), Length: 188 (0x00bc)
PID: 66 (0x0042) [= ]
TS-Packet: 00000476 PID: (Unkown PID), Length: 188 (0x00bc)

Looking thru the file about 99.9% have PID 66 (0x0042) with a few being PID:
67 (0x0043)

So what does this tell me? Will the patch fix it or do i need a diff fix?

--
Mitchell
nosohappyhemayhavetostartcompilinghisowncodeagain

bmayland+mythtv at capnbry

Jun 22, 2009, 1:58 PM

Post #4 of 10 (891 views)
Permalink

Re: State of Firewire [In reply to]

Mitch Gore wrote:

On Mon, Jun 22, 2009 at 10:56 AM, Bryan Mayland <bmayland+mythtv[at]capnbry.net> wrote:

Mitch Gore wrote:

test-mpeg2 and firewire_tester works 100% but myth fails to record any data.
2009-06-15 11:33:08.548 SM(0022CECC76B00000)::AddFlags: Seen() Match() Wait(PAT,PMT,Pos,)

Looks like your firewire box might not be sending out PAT/PMT tables
needed by MythTV's recorder. Try this test:
1) Record a stream using test-mpeg2 for 10 seconds or s
2) Use dvbsnoop to look through the file for a PAT:
dvbsnoop -s ts -if TESTFILENAME | grep "PID: 0"

Where TESTFILENAME is your file recorded with test-mpeg2. If your cable
box is like mine, you see a ton of "PID: 8191", some of another PID,
then very few (percentage wise) of another PID. If this is all you see,
congratulations, myth can't find your program in the stream!

If this is the case, do not despair, for I can supply you with a patch
that adds PID autodetect and fixes the problem completely. Apply
against libs/libmythtv/
http://capnbry.net/%7Ebmayland/fi/code/sigmon.diff"]http://capnbry.net/~bmayland/fi/code/sigmon.diff

If responding, make sure you CC my main email address because I rarely
check the list.

_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev"]http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

Bryan, Thank You for the reply.

So i install dvbsnoob and ran it on a test-mpeg2 file. When i Grep'ed for "PID: 0" I got nothing. I then did a grep for just PID. Here is what I see:

dvbsnoop -s ts -if test.mpg | grep "PID:"
Looking thru the file about 99.9% have PID 66 (0x0042) with a few being PID: 67 (0x0043)

So what does this tell me? Will the patch fix it or do i need a diff fix?

Patch may fix that, because there's definitely no PAT which is what Myth is waiting for. I can't say it will fix it for sure without seeing hex dumps of a bunch of packets, and I'm not even sure I'd be able to see for sure then, because I wrote this patch like 2 years ago.

What the patch actually does is looks at every TS packet coming in and finds a sync byte indicating the start of a PES packet, which contains the type of stream in the PID. If the stream type is an audio or video type, it save the PID and once it gets both it creates a PAT and PMT with the information and injects it into the stream which Myth finds and "locks" and carries on. After Myth locks, no further packets are inspected. I am relatively certain that this procedure will work for you, assuming the file you capture in test-mpeg2 plays in mplayer, because it just plays the first 2 streams it finds.

So if you don't understand the technical aspect of what I said, the answer is "It almost certainly will work". :)

mitchell.gore at gmail

Jun 23, 2009, 8:33 AM

Post #5 of 10 (860 views)
Permalink

Re: State of Firewire [In reply to]

�

> Patch may fix that, because there's definitely no PAT which is what Myth is
> waiting for. I can't say it will fix it for sure without seeing hex dumps
> of a bunch of packets, and I'm not even sure I'd be able to see for sure
> then, because I wrote this patch like 2 years ago.
>
> What the patch actually does is looks at every TS packet coming in and
> finds a sync byte indicating the start of a PES packet, which contains the
> type of stream in the PID. If the stream type is an audio or video type, it
> save the PID and once it gets both it creates a PAT and PMT with the
> information and injects it into the stream which Myth finds and "locks" and
> carries on. After Myth locks, no further packets are inspected. I am
> relatively certain that this procedure will work for you, assuming the file
> you capture in test-mpeg2 plays in mplayer, because it just plays the first
> 2 streams it finds.
>
> So if you don't understand the technical aspect of what I said, the answer
> is "It almost certainly will work". :)
>

Well I applyed the patch and compiled mythtv. Good new, it compiled, bad
news, not any difference in functionality.

Here is the log:
mythbackend -v record,playback,channel
~~~CUT~~~
2009-06-23 10:29:49.954 TVRec(10): StartRecording(Delirious)
2009-06-23 10:29:49.955 TVRec(10): ASK_RECORDING 10 0 0 0
2009-06-23 10:29:50.200 TVRec(10): StartedRecording(0xb0f0a870)
fn(/tv/d1/4552_20090623103000.mpg)
2009-06-23 10:29:50.200 TVRec(10): ClearFlags(CancelNextRecording,) ->
RunMainLoop,
2009-06-23 10:29:50.200 TVRec(10): Changing from None to Watching
RecordingOnly
2009-06-23 10:29:50.200 TVRec(10):
ClearFlags(FrontendReady,CancelNextRecording,) -> RunMainLoop,
2009-06-23 10:29:50.200 TVRec(10): Request: Program(yes) channel() input()
flags(Recording,)
2009-06-23 10:29:50.202 TVRec(10): HW Tuner: 10->10
2009-06-23 10:29:50.202 TVRec(10): ClearFlags(PENDINGACTIONS,) ->
RunMainLoop,
2009-06-23 10:29:50.202 TVRec(10): No recorder yet, calling TuningFrequency
2009-06-23 10:29:50.202 FireChan(0022CECC76B00000): Open()
2009-06-23 10:29:50.204 FireChan(0022CECC76B00000): SetChannelByString(552)
2009-06-23 10:29:50.207 External channel change: sa8300_ch 552
2009-06-23 10:29:50.211 Waiting for External Tuning program to exit
Changing channel 552
2009-06-23 10:29:50.242 ret_pid(1660) child(1660) status(0x0)
2009-06-23 10:29:50.242 External Tuning program no longer running
2009-06-23 10:29:50.242 External Tuning program exited with no error
2009-06-23 10:29:50.242 FireChan(0022CECC76B00000): SetChannelByString(552)
success
2009-06-23 10:29:50.242 TVRec(10): Starting Signal Monitor
2009-06-23 10:29:50.242 TVRec(10): SetupSignalMonitor(1, 0)
2009-06-23 10:29:50.242 FireChan(0022CECC76B00000): Open()
2009-06-23 10:29:50.242 FireSM(0022CECC76B00000): ctor
2009-06-23 10:29:50.242 SM(0022CECC76B00000)::AddFlags: Seen() Match()
Wait(Sig,)
2009-06-23 10:29:50.242 FireDev(0022CECC76B00000): Requesting STB Power
State
2009-06-23 10:29:50.244 FireDev(0022CECC76B00000): STB Power State: On
2009-06-23 10:29:50.244 TVRec(10): Signal monitor successfully created
2009-06-23 10:29:50.244 TVRec(10): Setting up table monitoring.
2009-06-23 10:29:50.247 Using profile 'Live TV' to record
2009-06-23 10:29:50.247 TVRec(10): MPEG program number: 1
2009-06-23 10:29:50.248 DTVSM(0022CECC76B00000)::SetProgramNumber(1):
2009-06-23 10:29:50.248 SM(0022CECC76B00000)::RemoveFlags: Seen(PMT,Crypt,)
Match(PMT,Crypt,) Wait()
2009-06-23 10:29:50.248 SM(0022CECC76B00000)::AddFlags: Seen() Match()
Wait(PMT,)
2009-06-23 10:29:50.248 SM(0022CECC76B00000)::AddFlags: Seen() Match()
Wait(PAT,PMT,Pos,)
2009-06-23 10:29:50.248 TVRec(10): Successfully set up MPEG table
monitoring.
2009-06-23 10:29:50.248 SM(0022CECC76B00000)::Start: begin
2009-06-23 10:29:50.248 FireDev(0022CECC76B00000): Requesting STB Power
State
2009-06-23 10:29:50.248 SM(0022CECC76B00000)::Start: end
2009-06-23 10:29:50.248 TVRec(10): SetFlags(SignalMonitorRunning,) ->
RunMainLoop,SignalMonitorRunning,
2009-06-23 10:29:50.248 TVRec(10): ClearFlags(WaitingForSignal,) ->
RunMainLoop,SignalMonitorRunning,
2009-06-23 10:29:50.248 TVRec(10): SetFlags(WaitingForSignal,) ->
RunMainLoop,WaitingForSignal,SignalMonitorRunning,
2009-06-23 10:29:50.248 TVRec(10): ClearFlags(NeedToStartRecorder,) ->
RunMainLoop,WaitingForSignal,SignalMonitorRunning,
2009-06-23 10:29:50.248 TVRec(10): SetFlags(NeedToStartRecorder,) ->
RunMainLoop,WaitingForSignal,NeedToStartRecorder,SignalMonitorRunning,
2009-06-23 10:29:50.250 FireDev(0022CECC76B00000): STB Power State: On
2009-06-23 10:29:50.250 SM(0022CECC76B00000)::AddFlags: Seen(STB,)
Match(STB,) Wait()
2009-06-23 10:29:50.250 FireSM(0022CECC76B00000): RunTableMonitor(): --
begin
2009-06-23 10:29:50.250 LFireDev(0022CECC76B00000): Starting Port Handler
Thread
2009-06-23 10:29:50.250 LFireDev(0022CECC76B00000): Starting Port Handler
Thread -- locked
2009-06-23 10:29:50.250 LFireDev(0022CECC76B00000): OpenPort()
2009-06-23 10:29:50.250 FireSM(0022CECC76B00000): UpdateValues() -- Waiting
for table monitor to start
2009-06-23 10:29:50.250 FireSM(0022CECC76B00000): UpdateValues() -- Table
monitor started
2009-06-23 10:29:50.251 LFireDev(0022CECC76B00000): OpenPort() -- got lock
2009-06-23 10:29:50.251 FireDev(0022CECC76B00000): AddListener() 1
2009-06-23 10:29:50.251 LFireDev(0022CECC76B00000): Opening P2P connection
libiec61883 warning: Overlayed connection on channel 1.
You may need to manually set the channel on the receiving node.
2009-06-23 10:29:50.259 LFireDev(0022CECC76B00000): OpenAVStream
2009-06-23 10:29:50.259 LFireDev(0022CECC76B00000): Opening A/V stream
object
2009-06-23 10:29:50.259 LFireDev(0022CECC76B00000): Buffered packets 2000
(8000 KB)
2009-06-23 10:29:50.259 LFireDev(0022CECC76B00000): Starting A/V streaming
-- really
2009-06-23 10:29:50.266 LFireDev(0022CECC76B00000): Starting A/V streaming
-- done
2009-06-23 10:29:50.267 LFireDev(0022CECC76B00000), Error: Dropped 349831168
TS packets
2009-06-23 10:29:50.278 AutoExpire: CalcParams(): Max required Free Space:
3.0 GB w/freq: 15 min
2009-06-23 10:29:50.279 Started recording: Delirious: channel 4552 on cardid
10, sourceid 4
2009-06-23 10:29:50.281 scheduler: Started recording: Delirious: channel
4552 on cardid 10, sourceid 4

So where do i go from here?
--
Mitchell

bmayland+mythtv at capnbry

Jun 24, 2009, 7:03 AM

Post #6 of 10 (836 views)
Permalink

Re: State of Firewire [In reply to]

Mitch Gore wrote:
> �Well I applyed the patch and compiled mythtv. Good new, it compiled,
> bad news, not any difference in functionality.
Doh! I'm not sure. You're going to have to dig into the packets to
figure out why myth doesn't like them. My log looks something like this
where yours ends
2009-06-24 09:52:25.516 LFireDev(0050940012345678): Buffered packets
2000 (8000KB)
2009-06-24 09:52:25.516 LFireDev(0050940012345678): Starting A/V
streaming -- really
2009-06-24 09:52:25.523 LFireDev(0050940012345678): Starting A/V
streaming -- done
2009-06-24 09:52:25.523 LFireDev(0050940012345678), Error: Dropped
100663296 TSpackets
2009-06-24 09:52:25.555 Video SID seen in PID 144
2009-06-24 09:52:25.586 Video SID seen in PID 144
2009-06-24 09:52:25.618 Video SID seen in PID 144
2009-06-24 09:52:25.649 AC3A SID seen in PID 145
2009-06-24 09:52:25.649 FireSM(0050940012345678): HandlePAT() got PAT
2009-06-24 09:52:25.649 SM(0050940012345678)::AddFlags: Seen(PAT,)
Match() Wait()
2009-06-24 09:52:25.649 SM(0050940012345678)::AddFlags: Seen(PAT,)
Match() Wait()
2009-06-24 09:52:25.649 SM(0050940012345678)::AddFlags: Seen()
Match(PAT,) Wait()

The difference being mine gets Seen(PAT) and then March(PAT). Also you
see the stream detector finding Video and Audio stream identifiers in
their respective PIDs. Maybe check with dvbsnoop to see if it can
detect the stream types. Run dvbsnoop -s ts -if XXXX | grep PES-stream
==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC
13818-2 or ISO/IEC 11172-2 video stream]
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC
13818-2 or ISO/IEC 11172-2 video stream]
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC
13818-2 or ISO/IEC 11172-2 video stream]

_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

mitchell.gore at gmail

Jun 24, 2009, 10:07 AM

Post #7 of 10 (830 views)
Permalink

Re: State of Firewire [In reply to]

Before I do too much digging does it look like i have the patch on
correctly?

Attached is a diff of the entire tree.

My snoop looks almost identical to yours:
mitchell[at]mythtv:~$ dvbsnoop -s ts -if test.ts | grep PES-stream
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2 or
ISO/IEC 11172-2 video stream]
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2 or
ISO/IEC 11172-2 video stream]
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2 or
ISO/IEC 11172-2 video stream]
==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2 or
ISO/IEC 11172-2 video stream]
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2 or
ISO/IEC 11172-2 video stream]
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2 or
ISO/IEC 11172-2 video stream]
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2 or
ISO/IEC 11172-2 video stream]
==> PES-stream: 189 (0xbd) [= private_stream_1]
==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2 or
ISO/IEC 11172-2 video stream]

Thank you so much for your replies Bryan. Would this be something we could
troubleshoot faster over a chat? I pretty much available whenever (im in
Central timezone)

--
Mitchell

Attachments:

firewire.diff (8.11 KB)

mitchell.gore at gmail

Jun 24, 2009, 10:07 AM

Post #8 of 10 (831 views)
Permalink

Re: State of Firewire [In reply to]

Attachments:

firewire.diff (8.11 KB)

mitchell.gore at gmail

Jun 24, 2009, 11:35 AM

Post #9 of 10 (830 views)
Permalink

Re: State of Firewire [In reply to]

On Wed, Jun 24, 2009 at 12:07 PM, Mitch Gore <mitchell.gore[at]gmail.com>wrote:

> Before I do too much digging does it look like i have the patch on
> correctly?
>
> Attached is a diff of the entire tree.
>
> My snoop looks almost identical to yours:
> mitchell[at]mythtv:~$ dvbsnoop -s ts -if test.ts | grep PES-stream
> ==> PES-stream: 189 (0xbd) [= private_stream_1]
> ==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2
> or ISO/IEC 11172-2 video stream]
> ==> PES-stream: 189 (0xbd) [= private_stream_1]
> ==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2
> or ISO/IEC 11172-2 video stream]
> ==> PES-stream: 189 (0xbd) [= private_stream_1]
> ==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2
> or ISO/IEC 11172-2 video stream]
> ==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2
> or ISO/IEC 11172-2 video stream]
> ==> PES-stream: 189 (0xbd) [= private_stream_1]
> ==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2
> or ISO/IEC 11172-2 video stream]
> ==> PES-stream: 189 (0xbd) [= private_stream_1]
> ==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2
> or ISO/IEC 11172-2 video stream]
> ==> PES-stream: 189 (0xbd) [= private_stream_1]
> ==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2
> or ISO/IEC 11172-2 video stream]
> ==> PES-stream: 189 (0xbd) [= private_stream_1]
> ==> PES-stream: 224 (0xe0) [= ITU-T Rec. H.262 | ISO/IEC 13818-2
> or ISO/IEC 11172-2 video stream]
>
> Thank you so much for your replies Bryan. Would this be something we could
> troubleshoot faster over a chat? I pretty much available whenever (im in
> Central timezone)
>
> --
> Mitchell
>

Ok, i just started from scratch. Deleted my tree than reissued the patch
via:

patch -p0 < /home/mitchell/sigmon.diff

when i was in the libsmythtv folder. seemed to apply cleanly. recompiled
and stateded the backend. I still do not see the
2009-06-24 09:52:25.555 Video SID seen in PID 144
2009-06-24 09:52:25.586 Video SID seen in PID 144
2009-06-24 09:52:25.618 Video SID seen in PID 144
2009-06-24 09:52:25.649 AC3A SID seen in PID 145
lines that you do.

Also one thing to mention. I am not issuing a "make install" I am just
going to the directory and starting the backend via ./mythbackend.... Is
this an issue?

--
Mitchell

dibblah.allan.stirling at googlemail

Jun 24, 2009, 11:45 AM

Post #10 of 10 (830 views)
Permalink

Re: State of Firewire [In reply to]

Mitch Gore wrote:
> Also one thing to mention. I am not issuing a "make install" I am just
> going to the directory and starting the backend via ./mythbackend....
> Is this an issue?

Yes. The changes you are making are in libmythtv.

Cheers,

Allan.
_______________________________________________
mythtv-dev mailing list
mythtv-dev[at]mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com