public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: David Lister <foceni@gmail.com>
To: Manu Abraham <abraham.manu@gmail.com>
Cc: Andreas Regel <andreas.regel@gmx.de>, linux-media@vger.kernel.org
Subject: Re: [linux-dvb] Most stable DVB-S2 PCI Card?
Date: Sat, 23 May 2009 22:30:19 +0200	[thread overview]
Message-ID: <4A185CDB.1090001@gmail.com> (raw)
In-Reply-To: <1a297b360905231145p1a8dca53jfd3069c7c90971b6@mail.gmail.com>

Manu Abraham wrote:
> On Sat, May 23, 2009 at 10:16 PM, David Lister <foceni@gmail.com> wrote:
>   
>> *OT* I just remembered in connection with Linux DVB-S2 cards: in case
>> some of you also heard about that new dual DVB-S2-CI tuner for PC's with
>> full Linux support, you can forget about it. Or at least I can. When I
>> pre-ordered directly from the Russian manufacturer (NetUP), they said
>> the price for one would be $1000. What a rip-off...
>>     
>
> Indeed it is.
>
> Maybe you will get a DVB card with dual DVB-S2 and CI with hardware
> H.264 decoder and HDMI out for a better deal. You might need to wait for
> the hardware to be available though.
>   

You appear to have different information. Their site and mail
announcements don't mention any H.264 decoder, nor HDMI out. Even the
photo says otherwise. This is the one I mean:
http://www.netup.tv/en-EN/dual_dvb-s2-ci_card.php

If what you say was true, (I wish it would), if it weren't a "budget"
card, I wouldn't call it a rip-off -- it would be a pretty neat piece of
HW. Still a bit pricey, but within limits. Unfortunately, from what I've
gathered from the site, announcements and mails with the manufacturer,
it is just a dual budget card. If so, it is a rip-off. :)

-- 
Dave


  reply	other threads:[~2009-05-23 20:30 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-22 17:32 [linux-dvb] Most stable DVB-S2 PCI Card? Niels Wagenaar
2009-05-22 17:48 ` Manu Abraham
2009-05-22 19:42   ` Goga777
2009-05-22 20:25     ` Manu Abraham
     [not found]       ` <4A171985.3090205@gmail.com>
2009-05-22 21:38         ` Manu Abraham
2009-05-23  5:51           ` David Lister
2009-05-23  6:37             ` Manu Abraham
2009-05-23 10:03               ` David Lister
2009-05-23 10:39                 ` Manu Abraham
2009-05-23 13:30                   ` David Lister
     [not found]                   ` <4A17F4E9.7090503@gmail.com>
2009-05-23 13:39                     ` Manu Abraham
2009-05-23 16:01                 ` Andreas Regel
2009-05-23 18:16                   ` David Lister
2009-05-23 18:45                     ` Manu Abraham
2009-05-23 20:30                       ` David Lister [this message]
2009-05-24  6:45                         ` VDR User
2009-05-25  2:36             ` Re : " Manu
2009-05-25  5:32               ` David Lister
  -- strict thread matches above, loose matches on Subject: below --
2009-05-22 18:02 Niels Wagenaar
2009-05-22 18:12 ` Manu Abraham
2009-05-22 17:23 Bob Ingraham
2009-05-22 17:28 ` [linux-dvb] " Another Sillyname
2009-05-22 17:35 ` Manu Abraham
2009-11-13  1:17   ` Jonas Kvinge
2009-11-13  9:43     ` rulet1
2009-11-13 18:02     ` Magnus Hörlin
2009-11-13 20:11       ` Jonas Kvinge
2009-11-13 20:28         ` hermann pitton

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=4A185CDB.1090001@gmail.com \
    --to=foceni@gmail.com \
    --cc=abraham.manu@gmail.com \
    --cc=andreas.regel@gmx.de \
    --cc=linux-media@vger.kernel.org \
    /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