<div dir="ltr"><div><div><div>Ronald,<br><br></div>Thanks for the help. Unfortunately no dice. Im not an expert on these tuners by any means but could it really be the card or a defective device if I can tune and record 4 channels on windows MCE? I only see a problem in Windows if I configure network tuners. Is there some function of doing RTP versus how MCE is discovering the device that could be related to a faulty card/device?<br>
<br>Here is the Ceton device currently on the system:<br><br>@bun2:~/infinitv-usbd-0.1.0$ ifconfig<br>usb0 Link encap:Ethernet HWaddr 16:ce:89:a4:bc:92 <br> inet addr:192.168.180.3 Bcast:192.168.180.255 Mask:255.255.255.0<br>
inet6 addr: fe80::14ce:89ff:fea4:bc92/64 Scope:Link<br> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1<br> RX packets:52032 errors:0 dropped:0 overruns:0 frame:0<br> TX packets:35818 errors:0 dropped:0 overruns:0 carrier:0<br>
collisions:0 txqueuelen:1000 <br> RX bytes:13125010 (13.1 MB) TX bytes:3722016 (3.7 MB)<br><br><br></div><div>Client script:<br></div><div><br>@bun2:~/infinitv_client_1_2$ python client.py -i 192.168.180.3 -t 0 -c 2004<br>
1361241192.838491 client.py:136 Initializing<br>1361241195.192447 board.py:46 Found: Ceton InfiniTV USB (00-80-69-7e)<br>1361241196.760815 client.py:27 PCRLock: 1<br>1361241196.938235 client.py:36 AVTransportURI: rtsp://<a href="http://192.168.180.1:8554/cetonmpeg0">192.168.180.1:8554/cetonmpeg0</a><br>
1361241196.938266 client.py:38 PrepareForConnection<br>1361241198.229179 client.py:45 RTSP setup done<br>1361241198.333927 client.py:52 SetChannel ChannelNumber=2004 SourceID=0<br>1361241198.597344 client.py:55 MPEG data streaming to <a href="http://127.0.0.1:8000">127.0.0.1:8000</a><br>
1361241198.597373 client.py:56 OOB data streaming to <a href="http://127.0.0.1:8001">127.0.0.1:8001</a><br><br><br>I could not use -l and -s. Using just -s netcat told me "This is nc from the netcat-openbsd package. An alternative nc is available in the netcat-traditional package." Oddly it told me the same thing when doing "nc -l -s 127.0.0.1 -p 8000 -u > rtp.mpg".<br>
<br>So just using -l i get 0 byte files, and of course mplayer gives me "stream contains no data"<br><br><br>@bun2:/$ netcat -l 127.0.0.1 -p 8000 -u > rtp.mpg<br>^C<br>bun2:/$ ls -lh<br>-rw-rw-r-- 1 bun2 bun2 0 Feb 18 20:44 rtp.mpg<br>
<br>This is the same behaviour more or less that I saw with VLC. It took the network stream capturing command but just sits there with a black window.<br><br><br>Here is the USB driver installation portion. I dont see any issues other than "./configure: line 2732: m4-#: command not found" but that does not appear to be an problem?<br>
<br>bun2@bun2:~/infinitv-usbd-0.1.0$ ./configure --prefix=/bun2<br>checking for a BSD-compatible install... /usr/bin/install -c<br>checking whether build environment is sane... yes<br>checking for a thread-safe mkdir -p... /bin/mkdir -p<br>
checking for gawk... gawk<br>checking whether make sets $(MAKE)... yes<br>./configure: line 2732: m4-#: command not found<br>checking build system type... x86_64-unknown-linux-gnu<br>checking host system type... x86_64-unknown-linux-gnu<br>
checking how to print strings... printf<br>checking for style of include used by make... GNU<br>checking for gcc... gcc<br>checking whether the C compiler works... yes<br>checking for C compiler default output file name... a.out<br>
checking for suffix of executables... <br>checking whether we are cross compiling... no<br>checking for suffix of object files... o<br>checking whether we are using the GNU C compiler... yes<br>checking whether gcc accepts -g... yes<br>
checking for gcc option to accept ISO C89... none needed<br>checking dependency style of gcc... gcc3<br>checking for a sed that does not truncate output... /bin/sed<br>checking for grep that handles long lines and -e... /bin/grep<br>
checking for egrep... /bin/grep -E<br>checking for fgrep... /bin/grep -F<br>checking for ld used by gcc... /usr/bin/ld<br>checking if the linker (/usr/bin/ld) is GNU ld... yes<br>checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B<br>
checking the name lister (/usr/bin/nm -B) interface... BSD nm<br>checking whether ln -s works... yes<br>checking the maximum length of command line arguments... 1572864<br>checking whether the shell understands some XSI constructs... yes<br>
checking whether the shell understands "+="... yes<br>checking how to convert x86_64-unknown-linux-gnu file names to x86_64-unknown-linux-gnu format... func_convert_file_noop<br>checking how to convert x86_64-unknown-linux-gnu file names to toolchain format... func_convert_file_noop<br>
checking for /usr/bin/ld option to reload object files... -r<br>checking for objdump... objdump<br>checking how to recognize dependent libraries... pass_all<br>checking for dlltool... no<br>checking how to associate runtime and link libraries... printf %s\n<br>
checking for ar... ar<br>checking for archiver @FILE support... @<br>checking for strip... strip<br>checking for ranlib... ranlib<br>checking command to parse /usr/bin/nm -B output from gcc object... ok<br>checking for sysroot... no<br>
checking for mt... mt<br>checking if mt is a manifest tool... no<br>checking how to run the C preprocessor... gcc -E<br>checking for ANSI C header files... yes<br>checking for sys/types.h... yes<br>checking for sys/stat.h... yes<br>
checking for stdlib.h... yes<br>checking for string.h... yes<br>checking for memory.h... yes<br>checking for strings.h... yes<br>checking for inttypes.h... yes<br>checking for stdint.h... yes<br>checking for unistd.h... yes<br>
checking for dlfcn.h... yes<br>checking for objdir... .libs<br>checking if gcc supports -fno-rtti -fno-exceptions... no<br>checking for gcc option to produce PIC... -fPIC -DPIC<br>checking if gcc PIC flag -fPIC -DPIC works... yes<br>
checking if gcc static flag -static works... yes<br>checking if gcc supports -c -o file.o... yes<br>checking if gcc supports -c -o file.o... (cached) yes<br>checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes<br>
checking whether -lc should be explicitly linked in... no<br>checking dynamic linker characteristics... GNU/Linux ld.so<br>checking how to hardcode library paths into programs... immediate<br>checking whether stripping libraries is possible... yes<br>
checking if libtool supports shared libraries... yes<br>checking whether to build shared libraries... yes<br>checking whether to build static libraries... yes<br>checking for gcc... (cached) gcc<br>checking whether we are using the GNU C compiler... (cached) yes<br>
checking whether gcc accepts -g... (cached) yes<br>checking for gcc option to accept ISO C89... (cached) none needed<br>checking dependency style of gcc... (cached) gcc3<br>checking for pkg-config... /usr/bin/pkg-config<br>
checking pkg-config is at least version 0.9.0... yes<br>checking for GIO... yes<br>checking for GIO_UNIX... yes<br>checking for LIBNL... yes<br>checking for GUSB... yes<br>checking for stdlib.h... (cached) yes<br>configure: creating ./config.status<br>
config.status: creating Makefile<br>config.status: creating src/Makefile<br>config.status: creating config.h<br>config.status: config.h is unchanged<br>config.status: executing depfiles commands<br>config.status: executing libtool commands<br>
<br><br>bun2@bun2:~/infinitv-usbd-0.1.0$ make<br>make all-recursive<br>make[1]: Entering directory `/home/bun2/infinitv-usbd-0.1.0'<br>Making all in src<br>make[2]: Entering directory `/home/bun2/infinitv-usbd-0.1.0/src'<br>
make[2]: Nothing to be done for `all'.<br>make[2]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0/src'<br>make[2]: Entering directory `/home/bun2/infinitv-usbd-0.1.0'<br>make[2]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0'<br>
make[1]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0'<br><br><br>bun2@bun2:~/infinitv-usbd-0.1.0$ sudo make install<br>[sudo] password for bun2: <br>Making install in src<br>make[1]: Entering directory `/home/bun2/infinitv-usbd-0.1.0/src'<br>
make[2]: Entering directory `/home/bun2/infinitv-usbd-0.1.0/src'<br>test -z "/bun2/bin" || /bin/mkdir -p "/bun2/bin"<br> /bin/bash ../libtool --mode=install /usr/bin/install -c infinitv_usbd '/bun2/bin'<br>
libtool: install: /usr/bin/install -c infinitv_usbd /bun2/bin/infinitv_usbd<br>make[2]: Nothing to be done for `install-data-am'.<br>make[2]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0/src'<br>make[1]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0/src'<br>
make[1]: Entering directory `/home/bun2/infinitv-usbd-0.1.0'<br>make[2]: Entering directory `/home/bun2/infinitv-usbd-0.1.0'<br>make[2]: Nothing to be done for `install-exec-am'.<br>make[2]: Nothing to be done for `install-data-am'.<br>
make[2]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0'<br>make[1]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0'<br><br></div>Again, thanks for your help!<br><br>--<br></div>Michael<br></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Mon, Feb 18, 2013 at 8:01 PM, Ronald Frazier <span dir="ltr"><<a href="mailto:ron@ronfrazier.net" target="_blank">ron@ronfrazier.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im">On Mon, Feb 18, 2013 at 8:25 PM, michael helmer <<a href="mailto:micmizer@gmail.com">micmizer@gmail.com</a>> wrote:<br>
> Ronald,<br>
><br>
> I am fairly certain that the USB drivers are installed correctly. I ran<br>
> through the README and saw no errors. Not sure of anyway to confirm<br>
> everything is fine?<br>
><br>
> As for the VLC stuff I got this back from Ceton support "try using vlc<br>
> udp://@<a href="http://127.0.0.1:8000" target="_blank">127.0.0.1:8000</a>" which did not work and I havent heard back from them<br>
> since they made that suggestion.<br>
><br>
> The last week and an half I have been messing around with using the network<br>
> tuner configuration on a Windows MCE host and trying to share 3 tuners with<br>
> MythTV. Unfortunately this does not work (for me). When using a network<br>
> tuner configuration the local MCE host cannot even record on its own tuner!<br>
> Im at a loss as a colleague of mine has this working and was following the<br>
> same configuration.<br>
<br>
<br>
</div>In order to test RTP outside of myth, here's my suggestion. I just<br>
tested this with the PCIe version. I'm not certain that this will be<br>
the same for the USB version, but it should be.<br>
<br>
1) First download the python client from here:<br>
<a href="http://cetoncorp.com/infinitv_support/linux_drivers/" target="_blank">http://cetoncorp.com/infinitv_support/linux_drivers/</a><br>
<br>
2) cd to the directory you unzipped it to, then run it as follow:<br>
<br>
python client.py -i <local ip address> -t <tuner> -c <channel><br>
<br>
Tuner is tuner you want to use (0-3) and channel would be the cable<br>
channel you want to tune. The tricky part here is local ip address.<br>
Note that this is NOT the IP address of the ceton's web interface, but<br>
rather the ip address assigned to the ctn0 network interface (or for<br>
USB ceton, I think the interface is usb0 or something like that). If<br>
you do " ifconfig ctn0" (or " ifconfig usb0"), you can get the local<br>
IP. Also note, that if you have bridging enabled, ctn0/eth0 don't get<br>
an IP, so use the IP address for br0 instead<br>
<br>
Once that starts up, it should tell you something like MPEG data going<br>
to <a href="http://127.0.0.1:8000" target="_blank">127.0.0.1:8000</a> and OOB data going to <a href="http://127.0.0.1:8001" target="_blank">127.0.0.1:8001</a>.<br>
<br>
3) While that is still running, open up another terminal. Run the<br>
following command:<br>
<br>
netcat -l -s 127.0.0.1 -p 8000 -u > rtp.mpg<br>
<br>
let that run for about 20 seconds and then Ctrl-C to end. You should<br>
now have an rtp.mpg file that is at least several MB in size.<br>
<br>
4) now play the video with mplayer:<br>
<br>
mplayer rtp.mpg<br>
<br>
<br>
<br>
If that works, then you can move on to trying to get myth configured.<br>
If it doesn't work, then either<br>
1) you have improperly installed the device (if you installed the USB<br>
drivers, and not the PCIe drivers, then I suspect this is unlikely)<br>
2) your cable card is not properly provisioned<br>
3) your cable company forgot tell you that you need a tuning adapter<br>
(but most cable companies don't need these)<br>
4) you have a defective device<br>
<br>