From: Oliver Schinagl <oliver+list@schinagl.nl>
To: Adrian Minta <adrian.minta@gmail.com>
Cc: Antti Palosaari <crope@iki.fi>, linux-media@vger.kernel.org
Subject: Re: update scan file for ro-DigiTV
Date: Tue, 03 Dec 2013 10:36:18 +0100 [thread overview]
Message-ID: <529DA612.2050704@schinagl.nl> (raw)
In-Reply-To: <529B4007.3060603@gmail.com>
On 01-12-13 14:56, Adrian Minta wrote:
> I took the .scm file from my Samsung TV and I use SamyGO-ChanEdit-v54 to
> look inside.
> The values where tested with kaffeine and w_scan. All the TV and Radio
> Channel where detected successfully.
Thanks, I have pushed it to the repo's.
Oliver
>
> This is the channels.conf file obtained with w_scan version 20120605
> (compiled for DVB API 5.5):
> http://pastebin.com/pXtnFq9T
>
> This is the w_scan log:
> http://pastebin.com/HG0zy1hJ
>
>
>
> On 01.12.2013 14:44, Antti Palosaari wrote:
>> Hello Adrian
>>
>> On 01.12.2013 09:54, Adrian Minta wrote:
>>> Hello,
>>> this is a scan file data for Romanian DigiTV
>>> http://www.rcs-rds.ro/personal-tv?t=cablu&pachet=digital
>>>
>>> Please add this to the list so other people can use.
>>>
>>>
>>> [dvb-c/ro-DigiTV]
>>> C 306000000 6900000 NONE QAM64
>>
>> How you obtained these values?
>> Almost all muxes are QAM64 which is quite weird. Usually that table
>> looks just like table where is QAM128 instead of QAM64, or even QAM256.
>>
>> regards
>> Antti
>>
>>
>
next prev parent reply other threads:[~2013-12-03 9:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-01 7:54 update scan file for ro-DigiTV Adrian Minta
2013-12-01 12:44 ` Antti Palosaari
2013-12-01 13:56 ` Adrian Minta
2013-12-03 9:36 ` Oliver Schinagl [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-05-14 19:09 Adrian Minta
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=529DA612.2050704@schinagl.nl \
--to=oliver+list@schinagl.nl \
--cc=adrian.minta@gmail.com \
--cc=crope@iki.fi \
--cc=linux-media@vger.kernel.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