[mythtv-users] Tuning fails on Nova S2 HD with "Error parsing parameters" 29.1

[Mike Bibbings]

On 27/05/2019 22:43, Klaas de Waal wrote:
> A lot has changed since 29.1 in mythtv-setup but with today's master  > everything should work and there should be no "Error parsing > 
parameters" error message boxes unless there are wrong parameters. > 
However, on today's master I cannot reproduce the "Error parsing > 
parameters" error box. This is with my current satellite tuner card > 
collection but that does not include a Nova-S2. Is this problem > 
specific for the Nova-S2 tuner card/stick or does it happen also on > 
other cards? Is it a new "Full Scan (Tuned)" or a "Scan of all > 
existing transports"? A detailed sequence on how to produce the > error 
box would be most helpful. > > On Sun, 26 May 2019 at 20:25, Paul 
Gardiner <lists at glidos.net> > wrote: >> >> On 26/05/2019 09:16, Mike 
Bibbings wrote: >>> On 25/05/2019 19:04, Paul Gardiner wrote: >>>> I've 
been using MythTV for many years now, with the same set of >>>> three 
capture devices, while upgrading the OS on a regular >>>> basis and 
taking on new MythTV versions (although not yet 30). >>>> I tried to 
perform a retune the other day and it failed on just >>>> one of the 
capture devices (an old Nova S2 HD). I get a message >>>> box appear 
saying "Error parsing parameters". I can see no >>>> errors in the logs. 
The other devices, a Nova T 500 and a >>>> Nanostick, are both working 
fine. All three devices record >>>> perfectly well; the problem is only 
with tuning. I'm using v >>>> 29.1 >>>> >>>> Anybody have any advice? 
Anyone know of any MythTV changes that >>>> may have caused this, or how 
best to track down the cause. >>> >>> I can replicate the "Error parsing 
parameters" message, by >>> hitting Escape key instead of using Left 
Arrow key having set the >>> tuning parameters (Frequency etc.) for the 
Satellite for a Full >>> Scan (Tuned) in Scan Type. >>> >>> Note this is 
on mythtv master, not 29.1, but this area of the GUI >>> is relatively 
unchanged since 29.1 which has a new GUI >>> implementation compared to 
previous versions e.g. 0.28 and >>> earlier. >> >> I thought I'd noticed 
a change in the GUI. I think my last >> successful scan on the Nova S2 
HD was with the old GUI. >> >> Mike, it sounds like you are getting a 
little further through the >> process than I do here. >> 
_______________________________________________


Ignore my previous comment about the Escape key, it was due to me using 
ssh to run mythtv-setup on remote machine, the Left arrow comment still 
applies.

I am assuming that mythbackend has been stopped before using 
mythtv-setup using systemctl commands in a terminal session and is 
running on a debian based operating system with systemd (includes 
current Ubuntu etc).

If you get the "WARNING: The backend is currently running" screen with 
Stop Backend and Continue highlighted (it does not actually stop 
mythbackend),  select Exit and use a terminal session

sudo systemctl stop mythtv-backend

then

mythtv-setup


I have rechecked on current mythtv 29 (built from source).

The only times I get the "Error parsing parameters" message with Full 
Scan (Tuned) using defaults for my tbs 6981 tuners) :

1. No Frequency is set.

2. Frequency includes non numeric characters, only numbers 0-9 should be 
used, no decimal point, commas etc.

For Astra 28E2 satellite I use and only have to set Frequency and Symbol 
Rate

Frequency: 10714000

Polarity: H (default)

Symbol Rate: 22000000 (default was 27500000)

Mod Sys: DVB-S (default)

FEC: Auto (default)

Modulation: QPSK (default)

Inversion: Auto (default)

Roll-off: 0.35 (default)


Mike

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20190528/082cabbe/attachment.html>