[mythtv-users] Ceton Infinitv USB issues

michael helmer micmizer at gmail.com
Tue Feb 19 03:16:00 UTC 2013


Ronald,

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?

Here is the Ceton device currently on the system:

@bun2:~/infinitv-usbd-0.1.0$ ifconfig
usb0      Link encap:Ethernet  HWaddr 16:ce:89:a4:bc:92
          inet addr:192.168.180.3  Bcast:192.168.180.255  Mask:255.255.255.0
          inet6 addr: fe80::14ce:89ff:fea4:bc92/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:52032 errors:0 dropped:0 overruns:0 frame:0
          TX packets:35818 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:13125010 (13.1 MB)  TX bytes:3722016 (3.7 MB)


Client script:

@bun2:~/infinitv_client_1_2$ python client.py -i 192.168.180.3 -t 0 -c 2004
1361241192.838491 client.py:136 Initializing
1361241195.192447 board.py:46 Found: Ceton InfiniTV USB (00-80-69-7e)
1361241196.760815 client.py:27 PCRLock: 1
1361241196.938235 client.py:36 AVTransportURI: rtsp://
192.168.180.1:8554/cetonmpeg0
1361241196.938266 client.py:38 PrepareForConnection
1361241198.229179 client.py:45 RTSP setup done
1361241198.333927 client.py:52 SetChannel ChannelNumber=2004 SourceID=0
1361241198.597344 client.py:55 MPEG data streaming to 127.0.0.1:8000
1361241198.597373 client.py:56 OOB data streaming to 127.0.0.1:8001


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".

So just using -l i get 0 byte files, and of course mplayer gives me "stream
contains no data"


@bun2:/$ netcat -l 127.0.0.1 -p 8000 -u > rtp.mpg
^C
bun2:/$ ls -lh
-rw-rw-r-- 1 bun2 bun2    0 Feb 18 20:44 rtp.mpg

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.


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?

bun2 at bun2:~/infinitv-usbd-0.1.0$ ./configure --prefix=/bun2
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
./configure: line 2732: m4-#: command not found
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking how to print strings... printf
checking for style of include used by make... GNU
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking dependency style of gcc... gcc3
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking whether ln -s works... yes
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking how to convert x86_64-unknown-linux-gnu file names to
x86_64-unknown-linux-gnu format... func_convert_file_noop
checking how to convert x86_64-unknown-linux-gnu file names to toolchain
format... func_convert_file_noop
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for dlltool... no
checking how to associate runtime and link libraries... printf %s\n
checking for ar... ar
checking for archiver @FILE support... @
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for sysroot... no
checking for mt... mt
checking if mt is a manifest tool... no
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking for dlfcn.h... yes
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared
libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for gcc... (cached) gcc
checking whether we are using the GNU C compiler... (cached) yes
checking whether gcc accepts -g... (cached) yes
checking for gcc option to accept ISO C89... (cached) none needed
checking dependency style of gcc... (cached) gcc3
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for GIO... yes
checking for GIO_UNIX... yes
checking for LIBNL... yes
checking for GUSB... yes
checking for stdlib.h... (cached) yes
configure: creating ./config.status
config.status: creating Makefile
config.status: creating src/Makefile
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
config.status: executing libtool commands


bun2 at bun2:~/infinitv-usbd-0.1.0$ make
make  all-recursive
make[1]: Entering directory `/home/bun2/infinitv-usbd-0.1.0'
Making all in src
make[2]: Entering directory `/home/bun2/infinitv-usbd-0.1.0/src'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0/src'
make[2]: Entering directory `/home/bun2/infinitv-usbd-0.1.0'
make[2]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0'
make[1]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0'


bun2 at bun2:~/infinitv-usbd-0.1.0$ sudo make install
[sudo] password for bun2:
Making install in src
make[1]: Entering directory `/home/bun2/infinitv-usbd-0.1.0/src'
make[2]: Entering directory `/home/bun2/infinitv-usbd-0.1.0/src'
test -z "/bun2/bin" || /bin/mkdir -p "/bun2/bin"
  /bin/bash ../libtool   --mode=install /usr/bin/install -c infinitv_usbd
'/bun2/bin'
libtool: install: /usr/bin/install -c infinitv_usbd /bun2/bin/infinitv_usbd
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0/src'
make[1]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0/src'
make[1]: Entering directory `/home/bun2/infinitv-usbd-0.1.0'
make[2]: Entering directory `/home/bun2/infinitv-usbd-0.1.0'
make[2]: Nothing to be done for `install-exec-am'.
make[2]: Nothing to be done for `install-data-am'.
make[2]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0'
make[1]: Leaving directory `/home/bun2/infinitv-usbd-0.1.0'

Again, thanks for your help!

--
Michael


On Mon, Feb 18, 2013 at 8:01 PM, Ronald Frazier <ron at ronfrazier.net> wrote:

> On Mon, Feb 18, 2013 at 8:25 PM, michael helmer <micmizer at gmail.com>
> wrote:
> > Ronald,
> >
> > I am fairly certain that the USB drivers are installed correctly. I ran
> > through the README and saw no errors. Not sure of anyway to confirm
> > everything is fine?
> >
> > As for the VLC stuff I got this back from Ceton support "try using vlc
> > udp://@127.0.0.1:8000" which did not work and I havent heard back from
> them
> > since they made that suggestion.
> >
> > The last week and an half I have been messing around with using the
> network
> > tuner configuration on a Windows MCE host and trying to share 3 tuners
> with
> > MythTV. Unfortunately this does not work (for me). When using a network
> > tuner configuration the local MCE host cannot even record on its own
> tuner!
> > Im at a loss as a colleague of mine has this working and was following
> the
> > same configuration.
>
>
> In order to test RTP outside of myth, here's my suggestion. I just
> tested this with the PCIe version. I'm not certain that this will be
> the same for the USB version, but it should be.
>
> 1) First download the python client from here:
> http://cetoncorp.com/infinitv_support/linux_drivers/
>
> 2) cd to the directory you unzipped it to, then run it as follow:
>
> python client.py -i <local ip address> -t <tuner> -c <channel>
>
> Tuner is tuner you want to use (0-3) and channel would be the cable
> channel you want to tune. The tricky part here is local ip address.
> Note that this is NOT the IP address of the ceton's web interface, but
> rather the ip address assigned to the ctn0 network interface (or for
> USB ceton, I think the interface is usb0 or something like that). If
> you do " ifconfig ctn0" (or " ifconfig usb0"), you can get the local
> IP. Also note, that if you have bridging enabled, ctn0/eth0 don't get
> an IP, so use the IP address for br0 instead
>
> Once that starts up, it should tell you something like MPEG data going
> to 127.0.0.1:8000 and OOB data going to 127.0.0.1:8001.
>
> 3) While that is still running, open up another terminal. Run the
> following command:
>
> netcat -l -s 127.0.0.1 -p 8000 -u > rtp.mpg
>
> let that run for about 20 seconds and then Ctrl-C to end. You should
> now have an rtp.mpg file that is at least several MB in size.
>
> 4) now play the video with mplayer:
>
> mplayer rtp.mpg
>
>
>
> If that works, then you can move on to trying to get myth configured.
> If it doesn't work, then either
> 1) you have improperly installed the device (if you installed the USB
> drivers, and not the PCIe drivers, then I suspect this is unlikely)
> 2) your cable card is not properly provisioned
> 3) your cable company forgot tell you that you need a tuning adapter
> (but most cable companies don't need these)
> 4) you have a defective device
>
> From past experience, I'd tend to lean towards #2. But try out the
> above steps and let me know how it goes and we can go from there.
>
>
> --
> Ron Frazier
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>



-- 
Michael Helmer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20130218/58533171/attachment-0001.html>


More information about the mythtv-users mailing list