[mythtv-commits] Ticket #3307: "Never Record" in Scheduled Recordings doesn't always work.
MythTV
mythtv at cvs.mythtv.org
Fri Apr 13 18:47:23 UTC 2007
#3307: "Never Record" in Scheduled Recordings doesn't always work.
-----------------------+----------------------------------------------------
Reporter: anonymous | Owner: xris
Type: defect | Status: new
Priority: minor | Milestone: unknown
Component: mythweb | Version: 0.20-fixes
Severity: low | Resolution:
-----------------------+----------------------------------------------------
Comment(by tmetro+mythtv-bugs at gmail.com):
> fyi, if you have a slow backend, it can take several seconds for the
scheduler to catch up.
Without a benchmark for some particular operation to compare against, I
can't say whether something is out of tune on my back-end causing it to
behave slowly, but the problem is easily reproducible on a system with:
# cat /proc/cpuinfo
model name : AMD Athlon(tm) XP 2600+
cpu MHz : 2088.170
cache size : 256 KB
bogomips : 4179.22
while sitting idle.
I suppose the delay will vary based not only on the system, but the
complexity of the schedule. I hadn't given it much thought, but I suppose
the problem has gotten worse as the number of items on my schedule has
grown.
> There's nothing I can do to speed this up. It's just a factor of how
things are for now.
I wasn't looking for a speedup, but a more deterministic way to know when
the updated value was ready.
For example, is there a way to ask the back-end if it is in the midst of a
schedule recalculation? Can you get notified when a recalculation is
complete?
Why is a schedule recalculation needed in order to update a "never record"
setting? Clearly it affects the schedule, but shouldn't the "never record"
status be immediately reflected in the recording settings for that entry?
Or does the process require that you adjust a schedule setting, and then
the back-end propagates that change to the specific program record being
shown by mythweb? (I'm guessing a program detail page in mythweb combines
data from both a program record and a schedule record.)
If the request to change the value succeeded (assuming the back-end
provides such feedback), and you have every reason to believe the
scheduler will change the status of "never record", can you "cheat" and
carry that information forwarded to the page being rendered?
Why doesn't modification of any of the other scheduling parameters (all
the stuff in the blue box) not suffer from this same delay problem? Is
that because that data is held in a scheduling record that mythweb
accesses directly and gets updated immediately, without needing the
scheduler to update it?
So presumably the "Possible conflicts with this show" list shown on the
show detail page is similarly suffering from delayed updating after a
scheduling change, just that it is less noticeable.
Thanks for the reply.
-Tom
--
Ticket URL: <http://svn.mythtv.org/trac/ticket/3307#comment:1>
MythTV <http://svn.mythtv.org/trac>
MythTV
More information about the mythtv-commits
mailing list