[SOLVED Rescanning channels with wirbelscan] ERROR: invalid value for parameter 'M' in yaVDR with VDR 1.7.26 (testing version)

jbjbjb · March 31, 2012 at 10:48 PM

Quote from DaKilla

If you lose the timer for any reason, you have to remove the epgsearch-internal list of completed timers.
I think this goes via the OSD. Menu, search, actions, show created timers, delete all.

Albert

Thanks.

It must be that you say, because epgsearch did not create the recordings scheduled but now it has created a new one for next week.

When I delete again the channels.con except one channel, and reboot. How much time should I wait till the channels are reloaded?

Regards.
jbjbjb

jbjbjb · April 1, 2012 at 1:35 AM

Solved the epgsearch issue deleting the file /var/lib/vdr/plugins/epgsearch/timersdone.conf

Well, before restart the proceeding of deleting channels.conf almost complete (leaving one working channel), I would like to know if the VDR will be (aproximately) more than one hour searching for the channels. It is only to know when I can stop the proceeding, because this morning, in 30 minutes, yaVDR only had found 7 channels (and from the same mux than the channel I left in channels.conf).

Thanks.

jbjbjb

mini73 · April 1, 2012 at 10:07 AM

Hi,

In the first column are the valid values for the parameter M (except -1):

Code

const tDvbParameterMap ModulationValues[] = {
  {  16, QAM_16,   "QAM16" },
  {  32, QAM_32,   "QAM32" },
  {  64, QAM_64,   "QAM64" },
  { 128, QAM_128,  "QAM128" },
  { 256, QAM_256,  "QAM256" },
  {   2, QPSK,     "QPSK" },
  {   5, PSK_8,    "8PSK" },
  {   6, APSK_16,  "16APSK" },
  {   7, APSK_32,  "32APSK" },
  {  10, VSB_8,    "VSB8" },
  {  11, VSB_16,   "VSB16" },
  {  12, DQPSK,    "DQPSK" },
  { 999, QAM_AUTO, trNOOP("auto") },
  {  -1, 0, NULL }
  };

Display More

Try to find the entries in your channels.conf which have other values and correct them.
You'll find the parameters in the third column of your channels.conf.
Maybe you should post your channels so we can take a look at them.

Lars.

jbjbjb · April 1, 2012 at 10:41 AM

Quote from mini73
Hi,

In the first column are the valid values for the parameter M (except -1):
Code
const tDvbParameterMap ModulationValues[] = {
  {  16, QAM_16,   "QAM16" },
  {  32, QAM_32,   "QAM32" },
  {  64, QAM_64,   "QAM64" },
  { 128, QAM_128,  "QAM128" },
  { 256, QAM_256,  "QAM256" },
  {   2, QPSK,     "QPSK" },
  {   5, PSK_8,    "8PSK" },
  {   6, APSK_16,  "16APSK" },
  {   7, APSK_32,  "32APSK" },
  {  10, VSB_8,    "VSB8" },
  {  11, VSB_16,   "VSB16" },
  {  12, DQPSK,    "DQPSK" },
  { 999, QAM_AUTO, trNOOP("auto") },
  {  -1, 0, NULL }
  };
Display More
Try to find the entries in your channels.conf which have other values and correct them.
You'll find the parameters in the third column of your channels.conf.
Maybe you should post your channels so we can take a look at them.

Lars.

Hi Lars.

According to your post, all the channels are wrong. I upload my channels.conf for checking.

Thanks.

Javier

jbjbjb · April 1, 2012 at 11:03 AM

Quote from DaKilla

Back to the root. Did you changed your channel list, as I have suggested this to you? Link.
Why do not uninstall the extrecmenu experimentally?

Albert

Hi.

I tried again, but only the group of the same mux the channel I leaved y channels.conf appeared.

I delete all channels.conf except iptv channels and I try to rescan with wirbelscan (I guess it is the plugin right to do it).

I will tell you.

thx.
jbjbjb

jbjbjb · April 1, 2012 at 11:34 AM

Hi.

The rescan with wirbelscan seems have worked.

I upload my new channels.conf and no 'M' error so far.

Thanks everybody. I will keep you posted.

Regards.
Javier

fnu · April 1, 2012 at 12:03 PM

These two related posts have been on VDR mailing list a couple of minutes ago:

Code

> I recently updated from 1.7.22 to the latest VDR developer snapshot 
> 1.7.27
>
> My DVB-S/DVB-S2 tuners all continued to work fine, but none of my 
> DVB-T channels were accesible anymore.
>
> Checking the logs I noticed numerous "ERROR: invalid value for 
> parameter 'S'" entries, whenever attempting to tune to a DVB-T 
> channel. I presumed this was related to the changes introduced into
> 1.7.23 for not writing values to channels.conf that weren't valid for 
> the given delivery system, but I couldn't find anything in the 
> Changelog that indicated a channels.conf change was needed.
>
> I guessed the simplest way to fix this was to use VDR's channel editor 
> to 'edit' and save my DVB-T channels, without modifying anything, and 
> seeing what change was introduced in channels.conf
>
> - 
> ITV1:642000000:B8C23D12G32M64:T:0:520=2:521=eng@3,522=eng@3:0;523=eng:
> 0:8271:9018:8207:0
> + ITV1:642000000:B8C23D12G32M64S0T8Y0:T:0:520=2:521=eng@3,522=eng@3:0;
> + 523=eng:0:8271:9018:8207:0
>
> It is trivial for me to reproduce this for all my channels. However, I 
> presume this means that scan / w_scan etc. all need to be updated to 
> generate the new channels.conf format for VDR 1.7.23 and newer?


I'm getting the same here.
Will look into it.


Klaus

Display More

Just for your information. It seems a kind of more global issues with channels.conf format for DVB-T entries and the need to recreate/-fresh them ... ?

jbjbjb

Since you're in the meantime on "testing-vdr", you may try update from it, as we're on VDR 1.7.27 now.

Regards
fnu

jbjbjb · April 1, 2012 at 1:50 PM

Quote from fnu

Since you're in the meantime on "testing-vdr", you may try update from it, as we're on VDR 1.7.27 now.

Hi, in the last update I did, the VDR 1.7.27 was installed (see the post ). I had the 'M' error in this version too till I rescanned the channels with wirbelscan.

Regards.
Javier

fnu · April 1, 2012 at 4:33 PM

Quote from jbjbjb

Hi, in the last update I did, the VDR 1.7.27 was installed (see the post ). I had the 'M' error in this version too till I rescanned the channels with wirbelscan.

Ok, I missed that statement, but I didn't thought 1.7.27 does solve your problem. It was just to point to the information, in case you missed that ...

Cheers
fnu

ATD · April 1, 2012 at 5:07 PM

Quote from jbjbjb

I upload my new channels.conf and no 'M' error so far.

Javier, I am glad that it worked. You're a nice guy.

Albert

jbjbjb · April 1, 2012 at 6:16 PM

Quote from DaKilla

Javier, I am glad that it worked. You're a nice guy.

Well, same to you all people. Thanks a lot for your help.

Regards.
Javier

Dread1ord · March 24, 2015 at 3:36 PM

same issues here, with Digital Devices Cine C2T2 V7, media-build-experimental-dkms, yavdr0.5.0a
i compared my new channels.conf with an older version from 2014, and found 167 channels with the parameter ":M998"

i have corrected it with the new parameter ":M999" for QAM_AUTO... and yeah, still works! no more syslog entries.

big thanks to mini73

[SOLVED Rescanning channels with wirbelscan] ERROR: invalid value for parameter 'M' in yaVDR with VDR 1.7.26 (testing version)

Participate now!

Users Viewing This Thread