public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: video4linux M/L <video4linux-list@redhat.com>
Subject: Re: Upgrading from FC4 to current Linux
Date: Wed, 14 Oct 2009 17:34:10 -0400	[thread overview]
Message-ID: <4AD643D2.1080904@tmr.com> (raw)
In-Reply-To: <829197380910021134t4df64ddq279ab817b792855@mail.gmail.com>

Devin Heitmueller wrote:
> On Fri, Oct 2, 2009 at 2:15 PM, Bill Davidsen <davidsen@tmr.com> wrote:
>   
>> I fear you are concentrating on the analog which is only a discussion of
>> where things were when there was support. But since you didn't offer any
>> suggestions for some user-friendly app I could give users, and I haven't
>> found any, I have to assume that the tools which I did find, all requiring a
>> significant user expertise to install, configure, and use, are all that's
>> available any more.
>>     
>
> Ah, well, we can talk about digital TV as well, although I had
> excluded it since your references were to analog and this was sent to
> the video4linux mailing list as opposed to linux-media.
>
> Compared to digital television support for international standards
> like DVB-T, the application support for ATSC/ClearQAM is much weaker.
> I added ATSC support to Kaffeine last year, and ClearQAM *should* work
> under Kaffeine but it is not heavily tested.  Me-TV supports ATSC as
> well, although it has considerable playback problems at high bitrates
> (channels such as CBS-HD).  I don't know of any applications that are
> easy to use and have support for both digital and analog.  The "easy
> to use" apps generally support one or the other, as they tend to have
> been developed by different groups of people.
>
> The reason for ATSC/ClearQAM support not being as good as DVB is
> pretty simple:  I can count the number of developers who actively
> contribute to it on one hand (three of which work for KernelLabs).
>
> The driver support for both ATSC and ClearQAM is pretty mature, but
> again most of the problems you will find are in the applications
> space.  There also is an issue where because ClearQAM devices are much
> newer, there tends to be fewer devices that support both ClearQAM
> *and* analog.  There are plenty of devices that support ATSC and
> analog but not ClearQAM, and there are plenty of devices that support
> ATSC and ClearQAM but not analog.  There are fewer devices though that
> support all three.
>
>   
>> Perhaps the days of the Linux desktop are over, at least
>> for people who want to install and have it work.
>>     
>
> Well, I'm not as extreme as some other developers as to say that
> "analog is dead", but like most developers, I don't have any personal
> interest in going out of my way to continue supporting it.
>
>   
First, thanks for your detailed response. As long as cable providers 
have a policy of providing analog in clear for customers with old TV 
hardware, and only broadcast local in clear-qam (because they must), 
users will want support for analog, because the digital is encrypted and 
needs a cable box. So analog won't be dead any time soon, at least in 
much of the US.

In looking for solutions I got an HDhomerun box, and while it's pretty 
much a single user solution, it works well for clear-qam, although the 
tuning is awkward, you don't need to be a genius to use it. 
Unfortunately it seems to not do the analog, so it's less than ideal as 
an overall solution. I haven't found any solution for S-video, other 
than to drop back to FC6 and use old analog apps. I have a bunch of 
cards (mostly PCI) and several USB dongles, none seem to do S-video 
under Linux. That's turned out to be more of an issue than I expected as 
well, I considered feeding the USB to a VM and Windows under KVM, but I 
really want Windows out!
>> I guess staying with FC4 or going Windows are the only options for users who
>> want something easy to use, thanks for assuring me that I didn't miss
>> something.
>>     
>
> Yeah, short of some commercial entity being willing to support
> maintenance of the apps and adding support for new devices, it seems
> likely that this is where things are going.  People seem to think they
> are somehow entitled for this stuff to "just work" when in reality it
> takes an enormous amount of effort, and if developers don't have an
> interest in doing it, and nobody is willing to pay for it, then
> support will indeed continue to get smaller and smaller.
>   

These folks have money, for political reasons they prefer open source, 
but that's the end of it, it's not a deal breaker to buy a solution by 
the seat.

Again, thanks for clarifying the dismal situation, I'm surprised that 
none of the developers is in an area where the majority of the signal 
are still analog, but that seems the case.

-- 
Bill Davidsen <davidsen@tmr.com>
  Unintended results are the well-earned reward for incompetence.

--
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-10-14 21:34 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-02 13:04 Upgrading from FC4 to current Linux Bill Davidsen
2009-10-02 16:40 ` Devin Heitmueller
2009-10-02 18:15   ` Bill Davidsen
2009-10-02 18:34     ` Devin Heitmueller
2009-10-14 21:34       ` Bill Davidsen [this message]
2009-10-14 21:42         ` Devin Heitmueller
2009-10-14 22:39           ` Bill Davidsen
2009-10-02 20:14 ` Andy Walls
2009-10-03  3:24   ` Jarod Wilson
2009-10-03  6:50     ` Devin Heitmueller
2009-10-05  6:22   ` linux-media@vger.kernel.org is gmane.linux.drivers.video-input-infrastructure Arthur Marsh

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=4AD643D2.1080904@tmr.com \
    --to=davidsen@tmr.com \
    --cc=dheitmueller@kernellabs.com \
    --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