public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Toth <stoth@linuxtv.org>
To: Devin Heitmueller <devin.heitmueller@gmail.com>
Cc: Linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: [linux-dvb] Revisiting the SNR/Strength issue
Date: Wed, 15 Oct 2008 14:18:34 -0400	[thread overview]
Message-ID: <48F633FA.4000106@linuxtv.org> (raw)
In-Reply-To: <412bdbff0810150740h61049f5fvb679bdebbcd4084d@mail.gmail.com>

Devin Heitmueller wrote:
> On Wed, Oct 15, 2008 at 10:30 AM, Steven Toth <stoth@linuxtv.org> wrote:
>> The SNR units should be standardized into a single metric, something
>> actually useful like ESNO or db. If that isn't available then we should aim
>> to eyeball / manually calibrate impossible boards against known reliable
>> demods on the same feed, it should be close enough.
>>
>> This requires patience and time from the right people with the right
>> hardware.
> 
> I agree that standardizing on a particular unit would be the ideal
> scenario.  Realistically though, do you have any confidence that this
> would actually happen?  Many frontends would have to change, reverse

It will happen when someone cares enough to do it, that's the Linux mantra.

Let's quantify this. How many frontends would have to change?

> engineering would have to be done, and in many cases without a signal
> generator this would be very difficult.  This could take months or
> years, or might never happen.

You don't need a signal generator, you _do_ need a comparison product 
that is reliably reporting db.

> 
> Certainly I'm in favor of expressing that there is a preferred unit
> that new frontends should use (whether that be ESNO or db), but the
> solution I'm suggesting would allow the field to become useful *now*.
> This would hold us over until all the other frontends are converted to
> db (which I have doubts will ever actually happen).

I'm not in favour of this.

I'd rather see a single unit of measure agreed up, and each respective 
maintainer go back and perform the necessary code changes. I'm speaking 
as a developer of eight (?) different demod drivers in the kernel. 
That's no small task, but I'd happily conform if I could.

Lastly, for the sake of this discussion, assuming that db is agreed 
upon, if the driver cannot successfully delivery SNR in terms of db then 
  the bogus function returning junk should be removed.

Those two changes alone would be a better long term approach, I think.

- Steve


_______________________________________________
linux-dvb mailing list
linux-dvb@linuxtv.org
http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb

  reply	other threads:[~2008-10-15 18:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-15 14:24 [linux-dvb] Revisiting the SNR/Strength issue Devin Heitmueller
2008-10-15 14:30 ` Steven Toth
2008-10-15 14:40   ` Devin Heitmueller
2008-10-15 18:18     ` Steven Toth [this message]
2008-10-16 14:28       ` Devin Heitmueller
2008-10-17  9:40         ` Christophe Thommeret
2008-10-17  9:55       ` Andreas Oberritter
2008-10-17 13:31         ` Steven Toth
2008-10-17 14:12           ` Andreas Oberritter
2008-10-17 18:23             ` Steven Toth

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=48F633FA.4000106@linuxtv.org \
    --to=stoth@linuxtv.org \
    --cc=devin.heitmueller@gmail.com \
    --cc=linux-dvb@linuxtv.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