From: Michael Krufky <mkrufky@linuxtv.org>
To: Hans Verkuil <hverkuil@xs4all.nl>
Cc: VDR User <user.vdr@gmail.com>,
Mike Booth <mike_booth76@iprimus.com.au>,
Konstantin Dimitrov <kosio.dimitrov@gmail.com>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: What ever happened to standardizing signal level?
Date: Sun, 30 May 2010 11:18:25 -0400 [thread overview]
Message-ID: <4C0281C1.70506@linuxtv.org> (raw)
In-Reply-To: <201005300923.35376.hverkuil@xs4all.nl>
Hans Verkuil wrote:
> On Sunday 30 May 2010 09:07:46 VDR User wrote:
>> On Sat, May 29, 2010 at 2:09 AM, Mike Booth <mike_booth76@iprimus.com.au> wrote:
>>> i think someone is too concerned about being precisely accurate. So much so
>>> that no-one can see the woods for the trees any more.
>>>
>>> Its not important to me that accuracy is spot on. I only want to know that
>>> when tuning the dish I'm getting \better or worse.
>> I tend to agree with this. Ultimately what's important is not
>> necessarily that the readings are 100% accurate, but rather simply put
>> into some kind of universal scale that provides useful output to the
>> user. Many users were happy to see some activity addressing this
>> issue and unfortunately it seems to have stalled out but I'm not sure
>> why. I honestly felt there was enough common ground being discussed
>> that we'd have a solution by now.
>
> To the best of my knowledge Mike Krufky intended to work on this but he
> clearly no longer has time to do that work.
>
> Mike, can you perhaps explain what you wanted to do? Hopefully someone else
> can find the time to implement it.
>
> Regards,
>
> Hans
>
..."clearly no longer has time" -- please do not speak on my behalf -- I
have taken a break from v4l-dvb, and I will return when I have time for
it again.
I already did a lot of the work for standardizing signal level, but I
need to clean it up, consider new demod modules, push trees and send
pull requests. Right now, correct -- I don't have time for it. I'll
likely get to this by mid-august -- I will have more time again by then.
I have a plethora of changes in my queue that I have to burn through and
merge, including j-rod's lgdt3304 support. I used to get this stuff
done very quickly, but there is a lot of change going on in my life
right now... When things settle down here, I'll be back in full force. :-)
Regards,
Mike Krufky
Regards,
Mike
next prev parent reply other threads:[~2010-05-30 15:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-29 3:09 What ever happened to standardizing signal level? VDR User
2010-05-29 4:45 ` Konstantin Dimitrov
2010-05-29 9:09 ` Mike Booth
2010-05-30 7:07 ` VDR User
2010-05-30 7:23 ` Hans Verkuil
2010-05-30 15:18 ` Michael Krufky [this message]
2010-05-30 15:27 ` Hans Verkuil
2010-05-30 5:52 ` hermann pitton
2010-05-30 7:01 ` VDR User
2010-05-30 7:32 ` Markus Rechberger
2010-05-30 15:21 ` Michael Krufky
2010-05-30 17:29 ` Markus Rechberger
2010-05-31 3:02 ` Michael Krufky
2010-05-31 3:21 ` hermann pitton
2010-05-30 17:21 ` hermann-pitton
2010-06-04 3:30 ` hermann pitton
2010-06-04 5:18 ` VDR User
2010-06-06 22:01 ` hermann pitton
2010-06-06 22:12 ` Lars Schotte
2010-06-06 23:26 ` VDR User
2010-06-06 23:33 ` hermann pitton
2010-06-07 0:55 ` Lars Schotte
2010-06-07 3:21 ` Jed
2010-06-07 3:04 ` Manu Abraham
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=4C0281C1.70506@linuxtv.org \
--to=mkrufky@linuxtv.org \
--cc=hverkuil@xs4all.nl \
--cc=kosio.dimitrov@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=mike_booth76@iprimus.com.au \
--cc=user.vdr@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.