public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Jelle de Jong <jelledejong@powercraft.nl>
To: video4linux-list@redhat.com
Subject: Re: one dvb-t devices not working with mplayer the other is, what is going wrong?
Date: Fri, 24 Apr 2009 14:37:56 +0200	[thread overview]
Message-ID: <49F1B2A4.3060404@powercraft.nl> (raw)
In-Reply-To: <49DC5033.4000803@powercraft.nl>

Jelle de Jong wrote:
> Jelle de Jong wrote:
>> Jelle de Jong wrote:
>>> Hello everybody,
>>>
>>> As you may read in my previous thread, i am trying to switch from my
>>> em28xx devices to a device that works with gpl compliant upstream kernel
>>> source code.
>>>
>>> My em28xx devices all played back video and audio only dvb-t channels:
>>> Pinnacle PCTV Hybrid Pro Stick 330e
>>> Terratec Cinergy Hybrid T USB XS
>>> Hauppauge WinTV HVR 900
>>>
>>> I build script for this to automate the process, however i now swiched to
>>> my dvb-t only usb device:
>>> Afatech AF9015 DVB-T USB2.0 stick
>>>
>>> And it with totem-xine it plays the same as the em28xx devices, so the
>>> devices does kind of works (see the totem-xine bug, please commit to this
>>> bug if you have the same behavior)
>>>
>>> # device info
>>> http://debian.pastebin.com/d3e942c02
>>>
>>> # totem-xine bug
>>> http://bugzilla.gnome.org/show_bug.cgi?id=554319
>>>
>>> # mplayer issue
>>> http://debian.pastebin.com/d34d92e64
>>> ^ anybody have any idea what the heck goes on why doesn't mplayer work
>>> with this device, nothing changed in the commands i used.
>>>
>>> using:
>>> mplayer
>>> Version: 1:1.0.rc2svn20090330-0.0
>>> linux-image-2.6.29-1-686
>>> Version: 2.6.29-1
>>>
>>> Thanks in advance, for any help.
>>>
>>> Best regards,
>>>
>>> Jelle de Jong
>> some more info:
>>
>> device0 (not working, Afatech AF9013 DVB-T)
>> http://filebin.ca/ypxkw/mplayer0.log
>>
>> device1 (working, Micronas DRX3973D DVB-T, em28xx, markus not gpl code)
>> http://filebin.ca/zecdjm/mplayer1.log
>>
>> device2 (working, Zarlink MT352 DVB-T, em28xx, markus not gpl code)
>> http://filebin.ca/fzxtcx/mplayer2.log
>>
>> All devices work with totem-xine but only the em28xx devices works with
>> mplayer, whats going on?
>>
> 
> Anybody?
> 
> Best regards,
> 
> Jelle
> 

Would somebody be willing to test this with there device, see the first
mail for the commands I used, they are in the attached files.

Being able to use mplayer to listen to dvb-t radio is mandatory for me.

Thanks in advance,

Jelle

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

  reply	other threads:[~2009-04-24 12:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03 17:18 one dvb-t devices not working with mplayer the other is, what is going wrong? Jelle de Jong
2009-04-03 17:58 ` Jelle de Jong
2009-04-08  7:20   ` Jelle de Jong
2009-04-24 12:37     ` Jelle de Jong [this message]
2009-04-24 18:18       ` Antti Palosaari
2009-04-25  8:00         ` Jelle de Jong
2009-04-25  8:17           ` Antti Palosaari
2009-04-25  8:54             ` Jelle de Jong
2009-04-25  9:05               ` Antti Palosaari
2009-04-25  9:43                 ` Jelle de Jong
2009-04-25  9:50                   ` Antti Palosaari

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49F1B2A4.3060404@powercraft.nl \
    --to=jelledejong@powercraft.nl \
    --cc=video4linux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox