Atlantic Bird 1 was renamed to Eutelsat 12 West A in 2012 and moved from
12 to 36 degree's in 2016 and was thus not accurate anymore. In 2018 it
was repositioned to 59 east and renamed to Eutelsat 59A as can be seen
at [0]. So far there are no active transponders.
[0] http://space.skyrocket.de/doc_sdat/atlantic-bird-1.htm
Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
Hello,
The latest update for the file Atlantic-Bird-3-5.0W (Ku Band) is 2015-03-28:
https://git.linuxtv.org/dtv-scan-tables.git/log/dvb-s/Atlantic-Bird-3-5.0W
but since March 2015 there are a lot of changes in the tranponders list.
And now, a lot of transponders for Algerian, French and Italian TV and
Radio channels are missing.
Attached is an updated config scan file (Atlantic-Bird-3-5.0W.patch
file) for Atlantic-Bird-3-5.0W transponders in dvbv5 format.
Could you please ensure that this new patch is committed into the DVB
source code tree repositery?
PS : Attached there is also the full up to date file :
Atlantic-Bird-3-5.0W-2017-01-09.NEW.FULL if you need it
Thank you
Best regards
According with http://www.satbeams.com/satellites?id=2641, Intelsat 34
has:
"22 C-band channels to provide services to to North and South America and
Europe and 18 Ku-band channels to provide services to Mexico, Central
America, Brazil, the Caribbean, Europe, a portion of the United States,
and the northern part of the Atlantic Ocean. It will serve the role
originally intended for Intelsat 27 that was lost at launch failure and
will replace Intelsat 805 and Galaxy 11 at 304.5 degrees East longitude
position."
Currently, we have only C-band frequencies for this satellite.
Add Ku-bands as used currently in South America.
The transponders that were obtained from Vivo TV package
matches the ones at:
http://www.portaleds.com/satelites/listar.php?sat=3045
with a difference of 1-2 MHz.
The LNBf I have is not capable of tuning the two IP data channels
there, but I'm adding it, anyway, as it could be useful for someone.
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Hello,
There is no file for Paris Eiffel Tower DVB-T transmitters at https://git.linuxtv.org/dtv-scan-tables.git/tree/dvb-t/ .
Attached is a config scan file for Paris Eiffel Tower transmitters in dvbv5 format.
Could you please ensure that this new file is committed into the DVB source code tree repositery ?
Thank you
Best regards
Contributed-by: Leny <leny@netcourrier.com>
Signed-off-by: Olliver Schinagl <oliver@schinagl.nl>
Several channels used at Bamberg and Hesselberg have been changed at the
start of 2017 to avoid potential interference with the new DVB-T2 service
started at the end of March. EinsPlus has been replaced with One in
October 2016.
Full details are available (in german) at http://dvb-t-bayern.de/ .
Signed-off-by: Reinhard Speyerer <rspmn@arcor.de>
In summer 2016 some DVB-T/DVB-T2 frequencies were changed by the broadcaster Digita. Here are some that have already changed.
Signed-off-by: Olli Salonen <olli.salonen@iki.fi>
Remove channels 52 thru 69 for those in the USA or Canada who may want
to save a few clock cycles avoiding scanning through ch 52 to 69.
Signed-off-by: Bill Murphy <gc2majortom@gmail.com>
Those channel contributions were sent to me as part of a
patch for Kaffeine.
Contributed-by: Придворов Андрей "(Pridvorov Andrey)" <ua0lnj@bk.ru>
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
I have moved the channel numbers into the CHANNEL lines. I used the “physical channel number” which seems appropriate in this case. I would like to add a working entry for 22, but not sure what the DELIVERY_SYSTEM is?
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
This file is renamed to more accurately reflect its contents, as well as including all channels every used in NTSC. This is primarily of historical interest, the ATSC file has a more up-to-date (and much shorter) list to scan against. I notice that my local repo has the rm, but this isn’t reflected in the patch (of course), is there something else I should have done as well?
Signed-off-by: Mauro Carvalho Chehab <mchehab@s-opensource.com>
The pl-Krosno_Sucha_Gora file, added in commit
4cb113fd15, is the only file that
contains non-ASCII characters in the tree. This causes a number of
build issues with other packages that don't necessarily handle very
well non-ASCII file name encodings.
Since no other file in the tree contain non-ASCII characters in their
name, this commit renames pl-Krosno_Sucha_Gora similarly.
Examples of files that are named with only ASCII characters even if
the city name really contains non-ASCII characters:
- pl-Wroclaw should be written pl-Wrocław
- se-Laxsjo should be written se-Laxsjö
- de-Dusseldorf should be written de-Düsseldorf
- vn-Thaibinh should be written vn-Thái_Bình
Since there is no real standardization on the encoding of file names,
we'd better be safe and use only ASCII characters.
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Hi Oliver,
Attached is an updated scan file for au-Goulburn-Rocky_Hill in dvbv5 format, as created by dvbv5-scan. Could you please ensure that this is committed into the DVB source tree.
Many thanks from sunny Goulburn.
Dear Oliver,
enclosed you find a new list with tuning data for Unity Media Hessen.
The old list (de-Unitymedia) is not valid anymore for Hessen.
Enclose you also find the output of w_scan (the dvbv3 file). It
automatically added the comment "Unitymedia UPG Hessen" behind each
channel. For this reason I think that instead of replacing the old
de-Unitymedia file, we should simply create the new de-Unitymedia-Hessen
file.
Best regards and greetings from Hessen!
x264
Remove tuning file for Eurobird1 at 28.5E.
The satellite was moved to 33.0E (July 2015) and is now known as
Eutelsat 33C using different transponders.
Signed-off-by: Nick Morrott <knowledgejunkie@gmail.com>
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
One channel has no frequency. Remove the channel.
One channel is lacking a '[' before CHANNEL. Add it.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Some channels are assigned to the VHF frequency range.
My script were not expecting it, and initialized the
files with empty frequencies.
Fix it.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
