[mythtv-users] Some scheduled recording not showing in play list. (Live tv conflicts?)

Steven Adeff adeffs.mythtv at gmail.com
Wed Nov 14 21:36:56 UTC 2012


On Wed, Nov 14, 2012 at 11:37 AM, Kevin Johnson <iitywygms at gmail.com> wrote:
> Hi all.
> Running mythbuntu .26 with the latest fixes.  Separate fronend/backend.
> I have 4 tuners.  I hdhr and 2 atiwonders, all working correctly.
> Lately, if I have a show scheduled to record, and I happen to be watching
> live tv on the same channel as the recording, the show will not be available
> in my recording list.
> If I go to the backend and look, it shows as being recorded.  And
> mythcomflag is running on that very show.  But when I go to recorded
> programs, it is not there.
> I can get it to appear in the recorded shows if I stop the recording, then
> start it again.
> The only thing I see in the logs is this.
>
> Nov 13 20:59:54 mythbackend mythlogserver: mythbackend[1477]: I
> ProcessRequest ringbuffer.cpp:1098 (WaitForAvail)
> RingBuf(/var/lib/mythtv/livetv/1021_20121114043801.mpg): Waited 0.2 seconds
> for data #012#$
> Nov 13 21:00:00 mythbackend mythlogserver: mythbackend[1477]: I TVRecEvent
> tv_rec.cpp:1043 (HandleStateChange) TVRec(1): Changing from None to
> RecordingOnly
> Nov 13 21:00:00 mythbackend mythlogserver: mythbackend[1477]: I TVRecEvent
> mythdbcon.cpp:409 (PurgeIdleConnections) New DB connection, total: 16
> Nov 13 21:00:00 mythbackend mythlogserver: mythbackend[1477]: I TVRecEvent
> tv_rec.cpp:3562 (TuningCheckForHWChange) TVRec(1): HW Tuner: 1->1
> Nov 13 21:00:00 mythbackend mythlogserver: mythbackend[1477]: N Scheduler
> autoexpire.cpp:264 (CalcParams) AutoExpire: CalcParams(): Max required Free
> Space: 3.0 GB w/freq: 7 min
> Nov 13 21:00:00 mythbackend mythlogserver: mythbackend[1477]: I Scheduler
> scheduler.cpp:2646 (HandleRecordingStatusChange) Tuning recording: "New
> Girl":Menzies: channel 1021 on cardid 1, sourceid 1
> Nov 13 21:00:00 mythbackend mythlogserver: mythbackend[1477]: N CoreContext
> autoexpire.cpp:264 (CalcParams) AutoExpire: CalcParams(): Max required Free
> Space: 3.0 GB w/freq: 7 min
> Nov 13 21:00:01 mythbackend mythlogserver: mythbackend[1477]: E TVRecEvent
> recordinginfo.cpp:984 (InsertProgram)
> RecordingInfo::InsertProgram(ProgramInfo(1021_20121114050000.mpg):
> channame(KTVU-HD) startt$
> Nov 13 21:00:01 mythbackend mythlogserver: mythbackend[1477]: I CoreContext
> scheduler.cpp:655 (UpdateRecStatus) Updating status for "New Girl":Menzies
> on cardid 1 (Tuning => Recording)
> Nov 13 21:00:01 mythbackend mythlogserver: mythbackend[1477]: I
> HDHRStreamHandler tv_rec.cpp:3359 (RingBufferChanged) TVRec(7):
> RingBufferChanged()
> Nov 13 21:00:01 mythbackend mythlogserver: mythbackend[1477]: I
> HDHRStreamHandler tv_rec.cpp:830 (FinishedRecording) TVRec(7):
> FinishedRecording(1021_2012-11-14T04:38:01Z) damaged recq:<RecordingQuality
> o$
> Nov 13 21:00:01 mythbackend mythlogserver: mythbackend[1477]: I TVRecEvent
> tv_rec.cpp:4056 (TuningNewRecorder) TVRec(1): rec->GetPathname():
> '/D2/tvrecordings/1021_20121114050000.mpg'
> Nov 13 21:00:03 mythbackend mythlogserver: mythbackend[1477]: I
> ProcessRequest ringbuffer.cpp:1098 (WaitForAvail)
> RingBuf(/var/lib/mythtv/livetv/1021_20121114043801.mpg): Waited 2.0 seconds
> for data #012#$
> Nov 13 21:00:04 mythbackend mythlogserver: mythbackend[1477]: I Socket
> mythdbcon.cpp:409 (PurgeIdleConnections) New DB connection, total: 17
>
> I have new girl set to record at 9.
>
> Now, possible reason may be my setup of the cards in the backend??
> I have the tuner cards priorities set up like this.
>
> Card 1.  Live tv 1, Rec tv 4
> Card 2  Live tv 2, Rec tv 3
> Card 3, Live tv 3, Rec tv 2
> Card 4, Live tv 4, Rec tv 1
>
> I did it like that to avoid conflicts with live tv.  (Using the allow live
> tv to move shows does not seem to work in the frontend setups.)
>
> So, is this a bug or do I have the tuner cards setup wrong?  And if they are
> setup wrong, what is the right way so I dont get tuner conflicts while
> watching tv?
> Thanks to all.

there was a bug that has existed since at least 0.25 (some people say
0.24 had it as well, though others like me do not remember
experiencing it), that had similar effect. Check your Live TV group
and see if it is in there, if so, then as some have reported this bug
apparently still exists in 0.26. I'm not sure if there is an open
ticket still/again for this bug in 0.26, but it might be time to
create one if this is true.

-- 
Steve
http://www.mythtv.org/wiki/User:Steveadeff
Before you ask, read the FAQ!
http://www.mythtv.org/wiki/Frequently_Asked_Questions
then search the Wiki, and this list,
http://www.gossamer-threads.com/lists/mythtv/
Mailinglist etiquette - http://www.mythtv.org/wiki/Mailing_List_etiquette


More information about the mythtv-users mailing list