How to get RTP Streaming to work
- Yippee38
- Posts: 28
- Joined: Fri May 09, 2014 11:35 pm
- Location:
- HTPC Specs:
How to get RTP Streaming to work
I know this is a waste of time, but I have to ask somewhere.
Has anybody gotten rtp streaming to work on a Ceton InfiniTV PCIe card? I can get output via mplayer, but cannot get any rtp output even though the web client says it is "Playing".
Anybody?
Has anybody gotten rtp streaming to work on a Ceton InfiniTV PCIe card? I can get output via mplayer, but cannot get any rtp output even though the web client says it is "Playing".
Anybody?
- Crash2009
- Posts: 4357
- Joined: Thu May 17, 2012 12:38 am
- Location: Ann Arbor, Michigan
- HTPC Specs:
have you looked into XBMC or Media Browser 3
- Yippee38
- Posts: 28
- Joined: Fri May 09, 2014 11:35 pm
- Location:
- HTPC Specs:
Yeah, though those still need MythTV to run as the backend for live TV capture (as far as I can tell), and MythTV now (I don't understand why) requires RTP streaming rather than direct access. As far as I can tell, this card just does not stream rtp. My Ceton InfiniTV was defective. I was hoping that that was the reason why it wouldn't stream. I've got a replacement installed now, but it still doesn't stream RTP. Kinda starting to wish I had gone with different hardware.Crash2009 wrote:have you looked into XBMC or Media Browser 3
-
- Posts: 161
- Joined: Tue Jan 29, 2013 4:56 am
- Location:
- HTPC Specs:
just a quick question on why MythTV? or is that your back-end of choice (as opposed to WMC)?
- Yippee38
- Posts: 28
- Joined: Fri May 09, 2014 11:35 pm
- Location:
- HTPC Specs:
It's a linux box, so WMC is not an option.sbaeder wrote:just a quick question on why MythTV? or is that your back-end of choice (as opposed to WMC)?
- Yippee38
- Posts: 28
- Joined: Fri May 09, 2014 11:35 pm
- Location:
- HTPC Specs:
I tried using the python client (> python client.py -i 192.168.200.2 -t 0 -c 210). When I do I get the following messages:
> python client.py -i 192.168.200.2 -t 1 -c 210
1404684103.523566 client.py:136 Initializing
1404684105.617841 board.py:46 Found: Ceton InfiniTV PCIe (00-80-73-df)
1404684107.262160 client.py:27 PCRLock: 1
1404684107.268023 client.py:36 AVTransportURI: rtsp://192.168.200.1:8554/cetonmpeg1
1404684107.268155 client.py:38 PrepareForConnection
1404684107.538694 client.py:45 RTSP setup done
1404684107.623292 client.py:52 SetChannel ChannelNumber=210 SourceID=0
1404684107.748393 client.py:55 MPEG data streaming to 127.0.0.1:8000
1404684107.748518 client.py:56 OOB data streaming to 127.0.0.1:8001
(That looks far better than what I was getting with the old card.)
When I try to steam via VLC using "udp://@127.0.0.1:8000", the play button changes to a pause button, but I get no video. If I try using "rtp://@127.0.0.1:8000", I get an error that says, "A description in SDP format is required to receive the RTP stream. Note that rtp:// URLs cannot work with dynamic RTP payload format (28)."
Any suggestions?
> python client.py -i 192.168.200.2 -t 1 -c 210
1404684103.523566 client.py:136 Initializing
1404684105.617841 board.py:46 Found: Ceton InfiniTV PCIe (00-80-73-df)
1404684107.262160 client.py:27 PCRLock: 1
1404684107.268023 client.py:36 AVTransportURI: rtsp://192.168.200.1:8554/cetonmpeg1
1404684107.268155 client.py:38 PrepareForConnection
1404684107.538694 client.py:45 RTSP setup done
1404684107.623292 client.py:52 SetChannel ChannelNumber=210 SourceID=0
1404684107.748393 client.py:55 MPEG data streaming to 127.0.0.1:8000
1404684107.748518 client.py:56 OOB data streaming to 127.0.0.1:8001
(That looks far better than what I was getting with the old card.)
When I try to steam via VLC using "udp://@127.0.0.1:8000", the play button changes to a pause button, but I get no video. If I try using "rtp://@127.0.0.1:8000", I get an error that says, "A description in SDP format is required to receive the RTP stream. Note that rtp:// URLs cannot work with dynamic RTP payload format (28)."
Any suggestions?
- Crash2009
- Posts: 4357
- Joined: Thu May 17, 2012 12:38 am
- Location: Ann Arbor, Michigan
- HTPC Specs:
I read something recently that Eric wrote a few months back, that might be of interest to you. Eric was saying there is a new experimental feature in a new firmware they had released. Maybe you are using it all ready?
http://www.thegreenbutton.tv/forums/vie ... 508#p74508
Stumbled into this while searching that last error you got. http://stackoverflow.com/questions/1921 ... 20p-from-d
http://www.thegreenbutton.tv/forums/vie ... 508#p74508
Stumbled into this while searching that last error you got. http://stackoverflow.com/questions/1921 ... 20p-from-d
- Yippee38
- Posts: 28
- Joined: Fri May 09, 2014 11:35 pm
- Location:
- HTPC Specs:
I am using the beta firmware. I'll check out that article though.Crash2009 wrote:I read something recently that Eric wrote a few months back, that might be of interest to you. Eric was saying there is a new experimental feature in a new firmware they had released. Maybe you are using it all ready?
http://www.thegreenbutton.tv/forums/vie ... 508#p74508
Stumbled into this while searching that last error you got. http://stackoverflow.com/questions/1921 ... 20p-from-d
-
- Posts: 1378
- Joined: Mon Aug 22, 2011 9:23 pm
- Location:
- HTPC Specs:
If you're still having trouble, I would recommend you do a packet capture on the InfiniTV's interface while video should be streaming and see if data is flowing.
Quality Assurance Manager, Ceton Corporation
- Yippee38
- Posts: 28
- Joined: Fri May 09, 2014 11:35 pm
- Location:
- HTPC Specs:
It looks like something is happening. I get a bunch of lines that look like this except the time signature changes:erkotz wrote:If you're still having trouble, I would recommend you do a packet capture on the InfiniTV's interface while video should be streaming and see if data is flowing.
15:08:21.222104 IP 192.168.200.1.43012 > htpcback-ceton.irdmi: UDP, length 1328
(Thanks for the help BTW.)
-
- Posts: 1378
- Joined: Mon Aug 22, 2011 9:23 pm
- Location:
- HTPC Specs:
Can you post the InfiniTV log when you expect video to be streaming, but it is not?
Quality Assurance Manager, Ceton Corporation
- Yippee38
- Posts: 28
- Joined: Fri May 09, 2014 11:35 pm
- Location:
- HTPC Specs:
Jan 1 06:31:02 ocur[21]: ocur: [0] Attempting to SetChannel (Channel=210 SourceId=0 Mode=0)
Jan 1 06:31:02 ocur[21]: ocur: Disabled table monitor for instance 0
Jan 1 06:31:02 ocur[21]: ocur: [0] Program number set to 0, was 0
Jan 1 06:31:02 ocur[21]: ocur: [0] Tune to 210 (mod=q256, freq=111000, program=210, std=9)
Jan 1 06:31:03 ocur[21]: ocur: [0] Program number set to 210, was 0
Jan 1 06:31:03 ocur[21]: ocur: Disabled table monitor for instance 0
Jan 1 06:31:03 ocur[21]: ocur: [0] Locked: 1 Acc E: 444
Jan 1 06:31:03 ocur[21]: ocur: [0] Getting pmt for program 210
Jan 1 06:31:03 ocur[21]: ocur: [0] Got pmt for program# 210
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x1ffc
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x1c50
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x0080
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x0090
Jan 1 06:31:03 ocur[21]: upnp: Event(tuner[0]): PCRLock, "1"
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x0000
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x1c51
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x1c5d
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x1c52
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x1c53
Jan 1 06:31:03 ocur[21]: ocur: Disabled table monitor for instance 0
Jan 1 06:31:03 ocur[21]: ocur: Enabled table monitor for instance 0
Jan 1 06:31:03 ocur[21]: ocur: [0] Channel is scrambled, expecting CCI
Jan 1 06:31:03 ocur[21]: ocur: [0] Sending ca_pmt to CableCARD for program number 210 index 0
Jan 1 06:31:04 ocur[21]: ocur: [0] CCI 00 arrived for program# 210
Jan 1 06:31:08 ocur[21]: ocur: [0] stream request 192.168.200.2:8000 start:1 prot: 0
Jan 1 06:31:08 ocur[21]: ocur: WARNING: [0] Connection denied: Stream in use by c0a8c802
Jan 1 06:31:08 ocur[21]: ocur: [0] rtp setup for client 192.168.200.2:8000
I don't know why it's showing a date of 01/01/06. My system date is correct.
Jan 1 06:31:02 ocur[21]: ocur: Disabled table monitor for instance 0
Jan 1 06:31:02 ocur[21]: ocur: [0] Program number set to 0, was 0
Jan 1 06:31:02 ocur[21]: ocur: [0] Tune to 210 (mod=q256, freq=111000, program=210, std=9)
Jan 1 06:31:03 ocur[21]: ocur: [0] Program number set to 210, was 0
Jan 1 06:31:03 ocur[21]: ocur: Disabled table monitor for instance 0
Jan 1 06:31:03 ocur[21]: ocur: [0] Locked: 1 Acc E: 444
Jan 1 06:31:03 ocur[21]: ocur: [0] Getting pmt for program 210
Jan 1 06:31:03 ocur[21]: ocur: [0] Got pmt for program# 210
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x1ffc
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x1c50
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x0080
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x0090
Jan 1 06:31:03 ocur[21]: upnp: Event(tuner[0]): PCRLock, "1"
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x0000
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x1c51
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x1c5d
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x1c52
Jan 1 06:31:03 ocur[21]: ocur: [0] Adding pid 0x1c53
Jan 1 06:31:03 ocur[21]: ocur: Disabled table monitor for instance 0
Jan 1 06:31:03 ocur[21]: ocur: Enabled table monitor for instance 0
Jan 1 06:31:03 ocur[21]: ocur: [0] Channel is scrambled, expecting CCI
Jan 1 06:31:03 ocur[21]: ocur: [0] Sending ca_pmt to CableCARD for program number 210 index 0
Jan 1 06:31:04 ocur[21]: ocur: [0] CCI 00 arrived for program# 210
Jan 1 06:31:08 ocur[21]: ocur: [0] stream request 192.168.200.2:8000 start:1 prot: 0
Jan 1 06:31:08 ocur[21]: ocur: WARNING: [0] Connection denied: Stream in use by c0a8c802
Jan 1 06:31:08 ocur[21]: ocur: [0] rtp setup for client 192.168.200.2:8000
I don't know why it's showing a date of 01/01/06. My system date is correct.
- Yippee38
- Posts: 28
- Joined: Fri May 09, 2014 11:35 pm
- Location:
- HTPC Specs:
Does that stuff look right to anybody who has a working card (if anybody has a working card in linux)?
- Crash2009
- Posts: 4357
- Joined: Thu May 17, 2012 12:38 am
- Location: Ann Arbor, Michigan
- HTPC Specs:
I don't have any experience with this type of project, the only thing that looks odd to me is:
Jan 1 06:31:08 ocur[21]: ocur: WARNING: [0] Connection denied: Stream in use by c0a8c802
Do you get the same warning if you use a different channel?
Jan 1 06:31:08 ocur[21]: ocur: WARNING: [0] Connection denied: Stream in use by c0a8c802
Do you get the same warning if you use a different channel?
- Yippee38
- Posts: 28
- Joined: Fri May 09, 2014 11:35 pm
- Location:
- HTPC Specs:
Yeah. The exact same warning on all channels. I wish I knew what c0a8c802 is.Crash2009 wrote:I don't have any experience with this type of project, the only thing that looks odd to me is:
Jan 1 06:31:08 ocur[21]: ocur: WARNING: [0] Connection denied: Stream in use by c0a8c802
Do you get the same warning if you use a different channel?
I wonder if the streaming problem could be a permissions problem, though I don't know on what files the permissions would be incorrect.
- Crash2009
- Posts: 4357
- Joined: Thu May 17, 2012 12:38 am
- Location: Ann Arbor, Michigan
- HTPC Specs:
c0a8c802 search it here at TGB, appears to have something to do with your cableCARD, or Headend.
- Yippee38
- Posts: 28
- Joined: Fri May 09, 2014 11:35 pm
- Location:
- HTPC Specs:
There's only one other message where that is mentioned, and it offers no information concerning that device (?). Even if it did, and I knew for sure that it is related to the card, that doesn't help me figure out why that card is locking streaming. I don't think it could be the headend because how could they be locking streaming output from the cablecard?Crash2009 wrote:c0a8c802 search it here at TGB, appears to have something to do with your cableCARD, or Headend.
I suspect that there is something "wrong" with my configuration, or that my distro does something that conflicts with the driver. I just don't know how to diagnose that further (I don't know anything about writing/modifying drivers).
- Yippee38
- Posts: 28
- Joined: Fri May 09, 2014 11:35 pm
- Location:
- HTPC Specs:
I thought maybe I'd find the part of the code that generated that error message and maybe that would lead to a solution. I couldn't find that anywhere in the code.
-
- Posts: 5738
- Joined: Tue Jun 21, 2011 7:23 pm
- Location: Titusville, Florida, USA
- HTPC Specs:
Have you tested the tuner card in Windows Media Center to see if it works there? It might be a good idea to prove that the CableCARD is paired correctly before you try to make it work in Linux.
-
- Posts: 115
- Joined: Thu Aug 02, 2012 8:39 pm
- Location:
- HTPC Specs:
c0.a8.c8.02
192.168.200.2
Maybe that will help
192.168.200.2
Maybe that will help