Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#4477 closed defect (fixed)

Unable to change DVB-S channels after merge of multirec brench into trunk

Reported by: zdzisekg@… Owned by: Janne Grunau
Priority: minor Milestone: 0.21
Component: mythtv Version: head
Severity: medium Keywords: rotor
Cc: Ticket locked: no

Description

Since the merge of multirec brench into trunk, I am unable to change channels for my DVB-S source. My setup is ROTOR->2 PORT DISEQC->LNB1 & LNB2

What I found so far: 1) Channel tuning works for the initial startchan, but then it fails to change to any channel that is not on the current multiplex. 2) Switching to a channel on the same multiplex as the startchan works. 3) Switching to a channel on another satellite does move the rotor to correct orbital location, but does not lock the signal. 4) The "Rotor" portion of the Signal Monitor display in OSD does not move and stays at 0% when switching to channel on different satelite although as noted in 3) the motor does actually move

Attachments (1)

mythbackend.log (156.3 KB) - added by zdzisekg@… 12 years ago.

Download all attachments as: .zip

Change History (11)

comment:1 Changed 12 years ago by danielk

Status: newinfoneeded_new

I'm going to need a 'mythbackend -v record,channel,siparser' log from the channel change.

Also, if you change the start channel in mythtv-setup to a channel on a different satellite and restart mythbackend does it properly tune to that channel?

comment:2 Changed 12 years ago by Janne Grunau

Milestone: unknown0.21
Status: infoneeded_newnew
Version: unknownhead

I fear it might be broken by [15441]. Please try reverting that changeset and/or applying t4473_v3.diff in #4471.

comment:3 Changed 12 years ago by Janne Grunau

Status: newinfoneeded_new

comment:4 Changed 12 years ago by Janne Grunau

(In [15460]) Fixes #4471, Refs #4477. Force a retune only if the LNB device id has changed.

fixes glitches in recordings when a second virtual DVB tuner changes the channel in the multiplex

comment:5 Changed 12 years ago by Janne Grunau

Resolution: fixed
Status: infoneeded_newclosed

comment:6 Changed 12 years ago by Janne Grunau

Owner: changed from Isaac Richards to Janne Grunau

I'm pretty sure [15460] fixed it. Please reopen if it still broken.

comment:7 Changed 12 years ago by zdzisekg@…

Resolution: fixed
Status: closednew
  • Running r15462 still does not resolve the issue. Log will be attached shortly.
  • To answer your other question, yes the rotor will move and the tunning is successful after manually changing the startchan and restarting backend
  • Log will be attached shortly

Changed 12 years ago by zdzisekg@…

Attachment: mythbackend.log added

comment:8 Changed 12 years ago by zdzisekg@…

Notes on the log:

Channels 12 & 13 are on the same multiplex.
Channels 8 & 6 are on different satellite.

Mythbackend started on chan 12 (ok)
Then I switched to ch 13(ok)
then back to ch 12(ok)
then switch to ch 8 (no lock)
then switch to ch 6 (no lock)
then back to ch 12 (no lock)

Note: The rotor does rotate to correct orbital position, it's just the Signal Monitor that does not show any rotor movement and stays at 0%.

comment:9 Changed 12 years ago by Janne Grunau

Resolution: fixed
Status: newclosed

(In [15471]) Fixes #4477. Fixes tuning for DVB-S rotor setups.

DVBSignalMonitor got not deleted fast enough (might be leaking) DVBStreamHandler was updating the Rotorposition in the old signal monitor so only the first tuning attempt succeed and all further attempts failed

debugged with help from Mark Buechler

comment:10 Changed 12 years ago by Janne Grunau

(In [15509]) Refs #4477. Delete DVB|DTVSignalMonitor actually if deleteLater() is called

Note: See TracTickets for help on using tickets.