[mythtv-users] consecutive recordings not working

[Josh]

Bruce Markey wrote:
> ryan patterson wrote:
> ...
>   
>> "Previously Recorded" page in mythfrontend just lists the show in yellow 
>> and says "aborted".  I don't see any info for why it was aborted.  I
>>     
>
> That's exactly what I was looking for. This verifies the state.
> The show was slated to record and not a conflict. The device,
> channel info, signal were okay so it could have recorded...
>  
>   
>> checked the full log file but I don't see an explination for why the 
>> recording was aborted there either.  Here is the relevant part of the log:
>>
>> 2007-02-05 20:00:02.905 TVRec(1): RingBufferChanged()
>> 2007-02-05 20:00:02.978 MythSocket(8213b20:-1): writeStringList: Error, 
>> called with unconnected socket.
>> 2007-02-05 20:00:03.001 MythSocket(8206130:-1): writeStringList: Error, 
>> called with unconnected socket.
>> 2007-02-05 20:00:03.002 MythSocket(abc19668:-1): writeStringList: Error, 
>> called with unconnected socket.
>> 2007-02-05 20:00:02.979 Finished recording Wheel of Fortune "Charleston, 
>> S.C. Week": channel 1051
>> 0: start_time: 409.331 duration: 1.159
>> 1: start_time: 409.331 duration: 1.159
>> stream: start_time: 4548.127 duration: 12.880 bitrate=17428 kb/s
>> 2007-02-05 20:00:03.025 AFD: Opened codec 0x81c0cb0, id(MPEG2VIDEO) 
>> type(Video)
>> 2007-02-05 20:00:03.032 AFD: Opened codec 0x824bdb0, id(AC3) type(Audio)
>> 2007-02-05 20:00:02.961 Canceled recording (Aborted): Prison Break 
>> "Chicago": channel 1441 on cardid 1, sourceid 1
>> 2007-02-05 20:00: 03.072 scheduler: Last message repeated 3 times: 
>> Finished recording: Wheel of Fortune "Charleston, S.C. Week": channel 1051
>> 2007-02-05 20:00:03.096 scheduler: Canceled recording (Aborted): Prison 
>> Break "Chicago": channel 1441 on cardid 1, sourceid 1
>> 2007-02-05 20:00:03.112 MythSocket(8213b20:-1): writeStringList: Error, 
>> called with unconnected socket.
>> 2007-02-05 20:00:03.120 MythSocket(8206130:-1): writeStringList: Error, 
>> called with unconnected socket.
>> 2007-02-05 20:00: 03.121 MythSocket(abc19668:-1): writeStringList: 
>> Error, called with unconnected socket.
>>     
>
> So the problem isn't what is coming up at 9pm; it's "Wheel of
> Fortune" that ran until 8pm.
>
>   
>> Could my abort problem be related to the MythSocket error messages?  
>>     
>
> Yes. I don't know of any current bugs that would account for
> this but over the years I've seen the frontend and backend
> get out of sync and in a funky state for their communications.
> Usually this clears up by restarting the master backend so if
> it has been running since before these incidents, try restarting.
>
> That said, I can easily produce an abort with no partial file.
> When a scheduled recording is about to start on the same tuner,
> a menu pops up with three choices and counts down the seconds.
> If I choose "Don't let it record, I want to watch TV" the show
> does not record and is marked as aborted.
>
>   
>> There are a ton of those in the log.  It looks like some body might have 
>> been watching live TV at the time.  But I'm not sure about that.  But I 
>> have two tuners.  So I think the recording should have switched to the 
>> second tuner.
>>     
>
> Nope. The schedule is planned ahead of time and scheduled
> recordings take precedence over channel surfing. If you, or
> someone, are going to surf rather than watch recordings of
> your favorite shows, go to TV Setting->General, first page
> and check "Avoid conflicts between live TV and scheduled
> shows." This isn't a solution for the string list errors but
> may help to continue surfing when there are upcoming recordings.
>
> Because this may have happened two days in a row at 8, I'd
> suggest that maybe a record rule for "Wheel of Fortune" may
> let someone watch it at their leisure while it is being broadcast
> or anytime thereafter.
>
> So, I'd recommend the following:
>
> - Restart the master backend and any slaves during a quite time
> and restart any frontends for good measure.
>
> - Check off the "Avoid conflicts..." option.
>
> - Schedule "Wheel of Fortune" daily at 7:30 on ch 51 possibly
> with a max episodes limit.
>
> - A gentle suggestion that 'watch while it records' is the best
> choice to continue watching a time-shifted live buffer when a
> recording needs to start.
>
> --  bjm
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
>
>
>   
I have to chime in here with my experience. This is a current issue for 
me with .20, but never thought to address it with a bug report since I 
don't have any hard data other then the basic report showing "aborted." 
My issue is exactly the same... if I have 2 recordings scheduled on the 
same channel back-to-back AND I am watching that channel as it records 
(say I forget to exit live TV mode) the 2nd job will "abort" and since 
I'm on the same channel Myth doesn't ask if I want to "continue to watch 
this channel." As an example... I record CSI Vegas on Spike TV and it's 
on for anywhere from 3 - 5 hours depending on the day, if I happen to 
leave Live TV running, I will come home to a single recording and the 
others on that channel would be "aborted." I noticed this a while back 
while recording syndicated Drew Carey on TBS. So now when I'm watching 
live TV and something is set to record on the channel I have to either 
change the channel and let Myth change the channel for me automagically, 
or I have to exit live TV, let Myth start the recording and then go into 
recorded programs and start watching it from there...

-- 
Josh