From: Alexis de Lattre <alexis@via.ecp.fr>
To: mossroy <mossroy@free.fr>
Cc: linux-media@vger.kernel.org,
Christoph Pfister <christophpfister@gmail.com>,
n_estre@yahoo.fr, alkahan@free.fr, ben@geexbox.org,
xavier@dalaen.com, jean-michel.baudrey@orange.fr,
lissyx@dyndns.org, sylvestre.cartier@gmail.com,
brossard.damien@gmail.com, johann.ollivierlapeyre@gmail.com,
jean-michel-62@orange.fr
Subject: Re: Updates to French scan files
Date: Mon, 27 Jun 2011 00:00:22 +0200 [thread overview]
Message-ID: <1309125622.5421.15.camel@wide> (raw)
In-Reply-To: <4E079E9F.7050004@free.fr>
Dear LinuxTV friends,
Le dimanche 26 juin 2011 à 23:03 +0200, mossroy a écrit :
> I would suggest to :
> - delete the 19 remaining fr-* files
> - make the French users use the auto-With167kHzOffsets file (should we
> create a fr-All file, that would be a link to auto-With167kHzOffsets ?)
> - create a file with a more complete list of frequencies, that would
> also include the +333 and +500 offsets, in case they were used. We might
> call it auto-WithUnusualOffsets for example
> I might provide a patch for that, of course.
I fully support your suggestion. I think that the
one-scan-file-per-transmitter is a non-sense (unfortunately, I
participated to this non-sense... but I was just doing "as everybody
else"). We should have one freq file per country, even if it takes more
time to scan... but as scanning is done only once, it is not a problem.
I think that we should have switched to the "one-scan-file-per-country"
a long time ago, because it would have simplified the job of Linux users
of lot !
I am aware that, for France :
Freq in Mhz = 306 + (8 x N) + (0,166 x D)
N = UHF channel number, between 21 et 69
D can be -1 , 0 , 1 , 2 or 3 = small freq offset
In order to simplify things, I would propose only ONE scan file with
offset -166, 0, 166, 333 and 500. OK, it will take more time for users
to run a scan (+66 %) compared to having a file with only offsets -166,
0, 166 but at least we are sure to cover all the possible offset that
can be used in France, and we simplify things as much as we can for
users.
Regards,
--
Alexis de Lattre
next prev parent reply other threads:[~2011-06-26 22:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-20 20:04 Updates to French scan files mossroy
2011-06-20 20:09 ` Antti Palosaari
2011-06-22 5:28 ` mossroy
2011-06-26 14:56 ` Christoph Pfister
2011-06-26 21:03 ` mossroy
2011-06-26 22:00 ` Alexis de Lattre [this message]
2011-06-27 6:31 ` Johann Ollivier Lapeyre
2011-06-28 5:47 ` Christoph Pfister
2011-07-02 21:32 ` mossroy
2011-07-16 15:06 ` Christoph Pfister
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=1309125622.5421.15.camel@wide \
--to=alexis@via.ecp.fr \
--cc=alkahan@free.fr \
--cc=ben@geexbox.org \
--cc=brossard.damien@gmail.com \
--cc=christophpfister@gmail.com \
--cc=jean-michel-62@orange.fr \
--cc=jean-michel.baudrey@orange.fr \
--cc=johann.ollivierlapeyre@gmail.com \
--cc=linux-media@vger.kernel.org \
--cc=lissyx@dyndns.org \
--cc=mossroy@free.fr \
--cc=n_estre@yahoo.fr \
--cc=sylvestre.cartier@gmail.com \
--cc=xavier@dalaen.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