<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
On 27/05/2019 22:43, Klaas de Waal wrote:<br>
<span style="white-space: pre-wrap; display: block; width: 98vw;">> 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 <a class="moz-txt-link-rfc2396E" href="mailto:lists@glidos.net"><lists@glidos.net></a>
> 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.
>> _______________________________________________
</span><br>
<p><br>
</p>
<p>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.</p>
<p>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).<br>
</p>
<p>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</p>
<p>sudo systemctl stop mythtv-backend</p>
<p>then<br>
</p>
<p>mythtv-setup</p>
<p><br>
</p>
I have rechecked on current mythtv 29 (built from source).<br>
<br>
The only times I get the "Error parsing parameters" message with
Full Scan (Tuned) using defaults for my tbs 6981 tuners) :<br>
<br>
1. No Frequency is set.<br>
<br>
2. Frequency includes non numeric characters, only numbers 0-9
should be used, no decimal point, commas etc.<br>
<br>
For Astra 28E2 satellite I use and only have to set Frequency and
Symbol Rate<br>
<br>
Frequency: 10714000<br>
<br>
Polarity: H (default)<br>
<br>
Symbol Rate: 22000000 (default was 27500000)<br>
<br>
Mod Sys: DVB-S (default)<br>
<br>
FEC: Auto (default)<br>
<br>
Modulation: QPSK (default)<br>
<p>Inversion: Auto (default)</p>
<p>Roll-off: 0.35 (default)</p>
<br>
<p>Mike<br>
</p>
</body>
</html>