<div dir="ltr"><br><br><div class="gmail_quote">On Tue, Oct 28, 2008 at 10:05 PM, oleg roitburd <span dir="ltr"><<a href="mailto:oroitburd@gmail.com">oroitburd@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Small snipet from VDR/channels.c<br>
-------------------------------snip------------------------------<br>
const tChannelParameterMap ModulationValues[] = {<br>
{ 16, QAM_16, "QAM16" },<br>
{ 32, QAM_32, "QAM32" },<br>
{ 64, QAM_64, "QAM64" },<br>
{ 128, QAM_128, "QAM128" },<br>
{ 256, QAM_256, "QAM256" },<br>
{ 2, QPSK, "QPSK" },<br>
{ 5, PSK_8, "8PSK" },<br>
{ 6, APSK_16, "16APSK" },<br>
{ 10, VSB_8, "VSB8" },<br>
{ 11, VSB_16, "VSB16" },<br>
{ 998, QAM_AUTO, "QAMAUTO" },<br>
{ -1 }<br>
};<br>
-------------------------------------------snap----------------------------</blockquote><div>Thanks. I'll use it in the dump.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<div class="Ih2E3d">><br>
> FEC you can specify in the frequency file as "AUTO", "1/3", "2/3" and so on.<br>
> I'll update README to make it clear. All frequency files samples show that<br>
> option.<br>
<br>
</div>i have seen, that FEC will be set if FEC is in initial file.<br>
If transponder was found via NIT it will be not set</blockquote><div>Yeah, it was my change since I saw NIT specifying incorrect FEC for a channel that was in my frequency list already!<br>I'll probably change it so NIT will be considered as the correct info unless frequency list include non-AUTO value.<br>
This way it will be possible to overwrite values or rely on network announcements if you want full automatic behavior.<br> <br></div></div><br></div>