[mythtv-users] Ceton Infinitv USB issues

Wed Feb 27 14:28:04 UTC 2013

ok so I checked my backend and this is what it loooks like

Encoder 1 [ CETON : 192.168.180.1-RTP.0 ] is local on Opti745 and is not
recording.
Encoder 2 [ CETON : 192.168.180.1-RTP.1 ] is local on Opti745 and is not
recording.
Encoder 3 [ CETON : 192.168.180.1-RTP.2 ] is local on Opti745 and is not
recording.
Encoder 4 [ CETON : 192.168.180.1-RTP.3 ] is local on Opti745 and is not
recording

after you set up your card did you set up a source? I know when I first
started using mythtv i didn't understand what all needed to be done to add
a card. I would be more than happy to look at your backend setup if you
want to give me access. I have installed and reinstalled my own about 20
times now so I am pretty good at it.. lol.

-Krys

On Tue, Feb 26, 2013 at 2:48 PM, Krys Allen <allen.krys at gmail.com> wrote:

> ill take a look at my mythbackend tonight and verify.. if the infinitv_usb
> service is finding the device then I would imaging that the issue lies
> within mythbackend.
>
>
> On Tue, Feb 26, 2013 at 9:39 AM, michael helmer <micmizer at gmail.com>wrote:
>
>> Hi Krys,
>>
>> Yes I tried that last night as well and received a "Unable to open
>> device".
>>
>> --
>> Michael
>>
>>
>> On Feb 26, 2013, at 9:32 AM, Krys Allen <allen.krys at gmail.com> wrote:
>>
>> have you tried 192.168.180.3 for your backend setup? I cant access my
>> house right now but for some reason that seems like what I used.
>>
>>
>> On Mon, Feb 25, 2013 at 10:07 PM, michael helmer <micmizer at gmail.com>wrote:
>>
>>> Guess i spoke to soon. Updating to the latest Beta firmware for the
>>> Ceton USB and running back through the python client I am now able to
>>> capture the stream!
>>>
>>> Not entirely sure what changed but unfortunately MythTV is still not
>>> capturing the stream. What is odd about it is once i have run MythTv i can
>>> no longer capture the stream with the python script until i reboot the
>>> Ceton. This may very well be why it never worked before (Me starting Myth
>>> and never rebooting afterwards). As soon as MythTV attempts a recording the
>>> program information disappears and I am unable to tune any channel from the
>>> Ceton Webpage. I am using 192.168.180.1-RTP.0 in the backend setup.
>>>
>>> I can see the rtp session getting created when I try to watch Live TV in
>>> Myth:
>>>
>>> @bun2:~sudo /bun2/bin/infinitv_usbd
>>>
>>> Starting infinitv-usbd 0.1.0
>>> found infinitv (/sys/devices/pci0000:00/0000:00:12.2/usb1/1-5)
>>> rtp setup 0
>>> rtp destroy 0
>>> rtp setup 0
>>> rtp destroy 0
>>>
>>> MythTV still complains about no recorder...
>>>
>>> 2013-02-25 21:56:30.964048 I  TVRec(10): Changing from None to
>>> WatchingLiveTV
>>> 2013-02-25 21:56:30.968921 I  TVRec(10): HW Tuner: 10->10
>>> 2013-02-25 21:56:31.095688 N  AutoExpire: CalcParams(): Max required
>>> Free Space: 3.0 GB w/freq: 14 min
>>> 2013-02-25 21:56:37.368771 E  TVRec(10): PauseRecorder() called with no
>>> recorder
>>> 2013-02-25 21:56:37.373417 I  TVRec(10): HW Tuner: 10->10
>>>
>>>
>>> Current testing is being done on Ubuntu 12.10 so I may try my 12.04
>>> installation tomorrow.
>>>
>>> --
>>> Michael
>>>
>>>
>>> On Mon, Feb 25, 2013 at 9:06 PM, michael helmer <micmizer at gmail.com>wrote:
>>>
>>>> I have been sticking to MCE at the moment as everything is functional
>>>> (except when i configure networking tuners). Oddly this does not work in
>>>> MythTV or using the python script in Linux. When using the default
>>>> configuration the USB tuner IP is 192.168.180.1 while the rest of my local
>>>> LAN is 192.168.0.xxx.
>>>>
>>>> Ceton provides a "network tuner" configuration option in Windows which
>>>> bridges the Ceton device to your local LAN. In this case the USB tuner has
>>>> an IP address on my local LAN i.e. 192.168.0.8. This does not work in
>>>> Windows.
>>>>
>>>> In both cases the the source port is 43012 and the destination port is
>>>> 5001.
>>>>
>>>> Just thought i would clarify. The behavior is odd and I cannot explain
>>>> it.
>>>>
>>>> --
>>>> Michael
>>>>
>>>>
>>>>
>>>> On Sat, Feb 23, 2013 at 6:37 PM, Ronald Frazier <ron at ronfrazier.net>wrote:
>>>>
>>>>> On Sat, Feb 23, 2013 at 5:28 PM, michael helmer <micmizer at gmail.com>
>>>>> wrote:
>>>>> > Wow... I clearly missed "infinitv_usbd is the user space linux
>>>>> driver for
>>>>> > the Ceton InfiniTV USB." in the README. I foolishly just did the
>>>>> > configure/make/make install. =/ Thanks Allen for pointing that out!
>>>>> >
>>>>> > I am unfortunately still unable to watch/record TV in MythTV. I have
>>>>> also
>>>>> > tried capturing the infinitv client stream with netcat and that is
>>>>> still
>>>>> > producing 0 byte files. The last week I have been trying to get
>>>>> network
>>>>> > tuners working in Windows MCE and I havent had any luck with that
>>>>> either.
>>>>> > Normal tuner configuration works great though! My end goal would be
>>>>> to have
>>>>> > network tuners working in MCE so I can record copy once shows and
>>>>> have 3
>>>>> > tuners presented to MythTV.
>>>>> >
>>>>> > In Windows I know the traffic is there on the wire as I captured a
>>>>> wireshark
>>>>> > trace and can see all of the UDP traffic going to port 5001. When I
>>>>> run the
>>>>> > client.py in Linux and capture on lo I am seeing some bizarre
>>>>> malformed
>>>>> > packets and destination unreachable for ICMP on the local 127.0.0.1.
>>>>> >
>>>>> > This loops forever:
>>>>> > 1    0.000000    192.168.180.3    192.168.180.3    YAMI    1370
>>>>> > [Malformed Packet]
>>>>> > 2    0.000245    127.0.0.1    127.0.0.1    MPEG TS    1358    Source
>>>>> port:
>>>>> > 43409  Destination port: irdmi
>>>>> > 3    0.000264    127.0.0.1    127.0.0.1    ICMP    590    Destination
>>>>> > unreachable (Port unreachable)
>>>>> >
>>>>> > It sure seems like a network issue or something blocking these
>>>>> ports. In
>>>>> > windows I uninstalled all antivirus software and disabled the
>>>>> firewall and i
>>>>> > see the same behaviour. The same is true for my Ubuntu box.
>>>>> >
>>>>>
>>>>>
>>>>> Stick to either trying to get it working in myth (or using the python
>>>>> script) with it installed on your linux box, or in WMC with it
>>>>> installed in your Windows box. The reason I say that is, I think
>>>>> you'll have a bit of difficulty getting it working between systems. By
>>>>> default, the Ceton is on it's own subnet that is separate from your
>>>>> LAN. Thus the RTP packets will never leave the local system. With the
>>>>> PCIe version, you need to bridge the 2 interfaces together and
>>>>> configure the Ceton with a custom IP address on the same subnet as the
>>>>> rest of your LAN. Not sure if that's any trickier to do with USB
>>>>> version or not. And I haven't the slightest clue how to do that under
>>>>> windows.
>>>>>
>>>>> So in short....you'll want to avoid all of that mess until you are
>>>>> positive your hardware works and the cablecard is provisioned
>>>>> properly. Then you can start thinking about the more complex
>>>>> configuration.
>>>>>
>>>>> --
>>>>> Ron Frazier
>>>>> _______________________________________________
>>>>> mythtv-users mailing list
>>>>> mythtv-users at mythtv.org
>>>>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Michael Helmer
>>>>
>>>
>>>
>>>
>>> --
>>> Michael Helmer
>>>
>>> _______________________________________________
>>> mythtv-users mailing list
>>> mythtv-users at mythtv.org
>>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>>
>>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>
>>
>>
>> _______________________________________________
>> mythtv-users mailing list
>> mythtv-users at mythtv.org
>> http://www.mythtv.org/mailman/listinfo/mythtv-users
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.mythtv.org/pipermail/mythtv-users/attachments/20130227/0d3885fa/attachment.html>