Mailing List Archive

Request for help making live TV useable
I've been using mythtv since around version 0.12 and have never found the live tv function to be terribly useable. For me there have always been lots of crashes and it seems to have only gotten worse.

While I've watched some new functionality like the internal video player go from alpha quality to being a wonderful solidly mature feature, live TV for me is still problematical.

I currently have two sets of capture devices:
a pair of NTSC plextor convertx usb2 external capture units w/ mpeg4 encoding
a pair of HDHomeRun ATSC ethernet external capture units each with a pair of ATSC tuners.

They all work very well for recording.

LiveTV has always had problems tuning. 95% of the time it would crash after a channel change.

For liveTV, version 0.23 got bad and 0.24 has gotten worse. I can no longer switch channels at all.

I'd appreciate any suggestions on how to debug my setup. I'd rather not completely erase my capture cards, as it'll cause all my recordings to no longer display what channel they were recorded from. However, if I have to, then I will.


_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On 04/16/2011 08:24 PM, Adam Felson wrote:
> I've been using mythtv since around version 0.12 and have never found the live tv function to be terribly useable. For me there have always been lots of crashes and it seems to have only gotten worse.
>
> While I've watched some new functionality like the internal video player go from alpha quality to being a wonderful solidly mature feature, live TV for me is still problematical.
>
> I currently have two sets of capture devices:
> a pair of NTSC plextor convertx usb2 external capture units w/ mpeg4 encoding
> a pair of HDHomeRun ATSC ethernet external capture units each with a pair of ATSC tuners.
>
> They all work very well for recording.
>
> LiveTV has always had problems tuning. 95% of the time it would crash after a channel change.
>
> For liveTV, version 0.23 got bad and 0.24 has gotten worse. I can no longer switch channels at all.
>
> I'd appreciate any suggestions on how to debug my setup. I'd rather not completely erase my capture cards, as it'll cause all my recordings to no longer display what channel they were recorded from. However, if I have to, then I will.

First off, make sure you're on current 0.24-fixes. Thanks to some
post-0.24-release fixes by Taylor Ralph and Mark Kendall, Live TV in
current 0.24-fixes is more stable than any prior version's Live TV I can
remember.

Mike
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On 17 April 2011 10:24, Michael T. Dean <mtdean@thirdcontact.com> wrote:
> On 04/16/2011 08:24 PM, Adam Felson wrote:
>> I've been using mythtv since around version 0.12 and have never found the live tv function to be terribly useable.  For me there have always been lots of crashes and it seems to have only gotten worse.
>>
>> While I've watched some new functionality like the internal video player go from alpha quality to being a wonderful solidly mature feature, live TV for me is still problematical.
>>
>> I currently have two sets of capture devices:
>>    a pair of NTSC plextor convertx usb2 external capture units w/ mpeg4 encoding
>>    a pair of HDHomeRun ATSC ethernet external capture units each with a pair of ATSC tuners.
>>
>> They all work very well for recording.
>>
>> LiveTV has always had problems tuning.  95% of the time it would crash after a channel change.
>>
>> For liveTV, version 0.23 got bad and 0.24 has gotten worse.  I can no longer switch channels at all.
>>
>> I'd appreciate any suggestions on how to debug my setup.  I'd rather not completely erase my capture cards, as it'll cause all my recordings to no longer display what channel they were recorded from.  However, if I have to, then I will.
>
> First off, make sure you're on current 0.24-fixes.  Thanks to some
> post-0.24-release fixes by Taylor Ralph and Mark Kendall, Live TV in
> current 0.24-fixes is more stable than any prior version's Live TV I can
> remember.

As Mike has already said, you'll definitely need to get your hands on
the very latest 0.24-fixes - which had its latest livetv related fix
just a couple of hours ago. There's not really a lot that any dev can
do to help out if you're not on something pretty recent as there have
been so many fixes that any debugging of an older version is likely to
be next to useless.

If you can update and you still see problems, then please capture some
logs with '-v playback,file,record' verbosity for both the frontend
and backend (at the same time).

regards

Mark
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
Hello, I am getting similar problem with LiveTV, I have a Debian
Squeeze FE/BE with one DVB-S2 and two DVB-T cards on a Nvidia ION
machine. I have debian-multimedia estable repository version
(0.24+fixes20110121-0.0).

My big LiveTV problems are thoose:

1. When I change channels I get "Error opening jump program file
buffer".This is frontend log:

2011-04-17 10:54:48.187 AO: Pause 1
2011-04-17 10:54:48.193 AO: OutputAudioLoop: audio paused
2011-04-17 10:54:50.899
RingBuf(/mnt/myth/livetv/31410_20110417105448.mpg) Error: OpenFile():
File too small (0B).
2011-04-17 10:54:50.900 Player(1), Error: JumpToProgram's OpenFile
failed (card type: DVB).
2011-04-17 10:54:50.900
LiveTVChain has 9 entries
DUMMY: 31400 (10:53:37 to 10:53:38)
DVB: 31400 (10:53:38 to 10:53:55) discontinuous
DVB: 31410 (10:53:55 to 10:54:06) discontinuous
DUMMY: 29656 (10:54:06 to 10:54:19) discontinuous
DVB: 29656 (10:54:19 to 10:54:29) discontinuous
DUMMY: 31409 (10:54:29 to 10:54:33) discontinuous
DVB: 31409 (10:54:33 to 10:54:38) discontinuous
DVB: 31400 (10:54:38 to 10:54:48) discontinuous
* DVB: 31410 (10:54:48 to 11:30:00) discontinuous

2011-04-17 10:54:50.900 Player(1), Error: Unknown recorder error,
exiting decoder
2011-04-17 10:54:50.987 msg: On known multiplex...
2011-04-17 10:54:50.991 TV: Attempting to change from WatchingLiveTV to None
2011-04-17 10:54:51.163 VDPAU Painter: Clearing VDPAU painter cache.
2011-04-17 10:54:51.298 MythPainter: 8 images not yet de-allocated.
2011-04-17 10:54:51.418 AO: Killing AudioOutputDSP
2011-04-17 10:54:51.443 AO: OutputAudioLoop: Stop Event
2011-04-17 10:54:51.444 AO: kickoffOutputAudioLoop exiting
2011-04-17 10:54:51.512 TV: Changing from WatchingLiveTV to None
2011-04-17 10:54:51.521 ScreenSaverX11Private: DPMS Reactivated 1
2011-04-17 10:54:51.522 TV: Attempting to change from None to None
2011-04-17 10:54:51.543 TV: Attempting to change from None to WatchingLiveTV
2011-04-17 10:54:51.544 MythCoreContext: Connecting to backend server:
192.168.0.5:6543 (try 1 of 1)
2011-04-17 10:54:51.545 Using protocol version 63
2011-04-17 10:54:51.563 Spawning LiveTV Recorder -- begin
2011-04-17 10:54:51.622 Spawning LiveTV Recorder -- end
2011-04-17 10:54:51.639 We have a
playbackURL(/mnt/myth/livetv/31409_20110417105451.mpg) &
cardtype(DUMMY)
2011-04-17 10:54:51.641 We have a RingBuffer
2011-04-17 10:54:51.643 playCtx, Error: Attempting to setup a player,
but it already exists.
2011-04-17 10:54:51.643 TV Error: LiveTV not successfully started

And this is the backend log:

2011-04-17 10:54:48.412 TVRec(1): HW Tuner: 1->1
2011-04-17 10:54:48.442 DVBChan(1:/dev/dvb/adapter0/frontend0)
Warning: Unsupported modulation parameter.
2011-04-17 10:54:48.452 Finished recording Nos gusta el cine : channel 31400
2011-04-17 10:54:48.457 LoadFromScheduler(): Error, called from backend.
2011-04-17 10:54:48.468 AutoExpire: CalcParams(): Max required Free
Space: 3.0 GB w/freq: 14 min
2011-04-17 10:54:48.488 Finished recording Nos gusta el cine : channel 31400
2011-04-17 10:54:48.709 TVRec(1): RingBufferChanged()
2011-04-17 10:54:48.715 Finished recording Nos gusta el cine : channel 31400
2011-04-17 10:54:49.103 MainServer::ANN Monitor
2011-04-17 10:54:49.104 adding: htpc as a client (events: 0)
2011-04-17 10:54:49.105 MainServer::ANN Monitor
2011-04-17 10:54:49.106 adding: htpc as a client (events: 1)
2011-04-17 10:54:51.447 TVRec(1): Changing from WatchingLiveTV to None
2011-04-17 10:54:51.508 Finished recording Pequeños invasores : channel 31410
2011-04-17 10:54:51.545 MainServer::ANN Playback
2011-04-17 10:54:51.546 adding: htpc as a client (events: 0)
2011-04-17 10:54:51.568 TVRec(1): Changing from None to WatchingLiveTV
2011-04-17 10:54:51.578 TVRec(1): HW Tuner: 1->1
2011-04-17 10:54:51.584 LoadFromScheduler(): Error, called from backend.
2011-04-17 10:54:51.594 AutoExpire: CalcParams(): Max required Free
Space: 3.0 GB w/freq: 14 min
2011-04-17 10:54:51.626 DVBChan(1:/dev/dvb/adapter0/frontend0)
Warning: Unsupported modulation parameter.
2011-04-17 10:54:51.652 TVRec(1): Changing from WatchingLiveTV to None
2011-04-17 10:54:51.676 Finished recording Horizontes : channel 31409


2. When I push ChannelUp key it always starts on the first channel on
the current input. For example: If I am watching the channel 5, the I
press ChannelUp key and it goes to channel 2, when I want to go to
channel 6.

The second problem is not really important, I can go to GUIDE and up
channels there. But the first problem is very annoying, I hope it will
solve fast. Tell me if you need more debug info.

I am not expert on code and good english writing, is it possible to
open a ticket with this? I will help as much as I can, is very
important for me.

Thanks and best regards.

--
Josu Lazkano
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
Josu,

Just like the OP fixes have been added to 0.24 recently and the
version you are using is 4 months old. If you update to latest
andRECORDED the issues still exist I am sure that the devs working on
LiveTV (if any at that time) will be interested in your results.

I however have been using MythTV since 0.20; I have never had issues
with crashes or odd behaviour with livetv. On the otherhand LiveTV
means that Myth is trying to schedule recordings in advance, making
judgement calls of when to record things without knowing which tuners
are going to be available at any particular time... MythTV and any DVR
either needs to have TV tuners when it needs them, or have dedicated
live TV tuners.

As such, although I rebelled against it when I started to use MythTV,
I now only use/watch pre-recorded TV, even if that means that I am
watching something a few seconds behind real time.... In other words I
tell mythtv about everything I/we want to watch, whether that is
something that is just being broadcast now and I just spotted or
something I scheduled which is being broadcast in the future, I use
the scheduler (or mythweb) to schedule the recording and then I watch
the recording.

Otherwise you are asking MythTV to schedule with one arm behind its
back (or a blindfold on; choose your metaphor). MythTVs scheduler is
more complex than that of Sky+...

R
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On 11-04-17 02:56 AM, Mark Kendall wrote:
> On 17 April 2011 10:24, Michael T. Dean <mtdean@thirdcontact.com> wrote:
>> On 04/16/2011 08:24 PM, Adam Felson wrote:
>>> I've been using mythtv since around version 0.12 and have never found the live tv function to be terribly useable. For me there have always been lots of crashes and it seems to have only gotten worse.
>>>
>>> While I've watched some new functionality like the internal video player go from alpha quality to being a wonderful solidly mature feature, live TV for me is still problematical.
>>>
>>> I currently have two sets of capture devices:
>>> a pair of NTSC plextor convertx usb2 external capture units w/ mpeg4 encoding
>>> a pair of HDHomeRun ATSC ethernet external capture units each with a pair of ATSC tuners.
>>>
>>> They all work very well for recording.
>>>
>>> LiveTV has always had problems tuning. 95% of the time it would crash after a channel change.
>>>
>>> For liveTV, version 0.23 got bad and 0.24 has gotten worse. I can no longer switch channels at all.
>>>
>>> I'd appreciate any suggestions on how to debug my setup. I'd rather not completely erase my capture cards, as it'll cause all my recordings to no longer display what channel they were recorded from. However, if I have to, then I will.
>>
>> First off, make sure you're on current 0.24-fixes. Thanks to some
>> post-0.24-release fixes by Taylor Ralph and Mark Kendall, Live TV in
>> current 0.24-fixes is more stable than any prior version's Live TV I can
>> remember.
>
> As Mike has already said, you'll definitely need to get your hands on
> the very latest 0.24-fixes - which had its latest livetv related fix
> just a couple of hours ago. There's not really a lot that any dev can
> do to help out if you're not on something pretty recent as there have
> been so many fixes that any debugging of an older version is likely to
> be next to useless.
>
> If you can update and you still see problems, then please capture some
> logs with '-v playback,file,record' verbosity for both the frontend
> and backend (at the same time).


I have the same devices as the OP, plus others, and I agree 99% with his assessment.
0.24-fixes is far, far worse for LiveTV than 0.22, 0.21, 0.20, 0.19, and 0.18 were
with this setup.

I don't have any trouble with liveTV and DVB tuners, nor with the HDHomeRun,
but anything to do with NTSC analog has issues. The ConvertX doesn't work at all
in LiveTV (fine for recording, though), none of my "soft" encoders work
beyond the first channel shown (if that), and even the PVR-250 results in lockups
and FE crashes if I change channels too quickly (more than once every 10 secs or
so).

Dunno why, and don't care enough to spend hours figuring it out and fixing it,
but it's there and not just an isolated incident. (I do spend hours finding
and fixing other stuff, though, just don't have enough of those to worry much
about LiveTV).

I do see that Mark Kendall has a new LiveTV fix in 0.24-fixes today though,
so I'm downloading/rebuilding with that to see if it has any effect here.

Cheers
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On 11-04-17 08:55 AM, Mark Lord wrote:
>
> I have the same devices as the OP, plus others, and I agree 99% with his assessment.
> 0.24-fixes is far, far worse for LiveTV than 0.22, 0.21, 0.20, 0.19, and 0.18 were
> with this setup.
>
> I don't have any trouble with liveTV and DVB tuners, nor with the HDHomeRun,
> but anything to do with NTSC analog has issues. The ConvertX doesn't work at all
> in LiveTV (fine for recording, though), none of my "soft" encoders work
> beyond the first channel shown (if that), and even the PVR-250 results in lockups
> and FE crashes if I change channels too quickly (more than once every 10 secs or
> so).
>
> Dunno why, and don't care enough to spend hours figuring it out and fixing it,
> but it's there and not just an isolated incident. (I do spend hours finding
> and fixing other stuff, though, just don't have enough of those to worry much
> about LiveTV).
>
> I do see that Mark Kendall has a new LiveTV fix in 0.24-fixes today though,
> so I'm downloading/rebuilding with that to see if it has any effect here.


I can still get LiveTV (NTSC OTA) to lock up with about the same
degree of reliability as before. So another small step perhaps,
but somethings still not quite right in there.

However.. I also noticed a bunch of decoder fixes in trunk,
dealing with calculating the number of buffers needed,
and fixing bugs where buffers were being recycled while
still in use and so on.

So I backported those as well to 0.24-fixes. This seems to have made
a noticeable improvement in my PVR-250 LiveTV channel changes.
I can now often change channels 8-10 times without locking up,
whereas normally only (exactly) three channel changes were needed before.

Those patches are definitely a keeper on the machines here!
And they have the side benefit of no longer requiring that I
hardcode vdpaubuffersize=nn on various machines. Woo-hoo! :)

Now.. something weird since I upgraded from 0.22 to 0.24:
When I view LiveTV (for analog OTA NTSC), there are always *two*
files created for each "recording", one of which is a zero-length file,
and the other (created second) has the actual recording.

Is this "normal" ?

Thanks
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On 11-04-17 09:32 AM, Mark Lord wrote:
..
> Now.. something weird since I upgraded from 0.22 to 0.24:
> When I view LiveTV (for analog OTA NTSC), there are always *two*
> files created for each "recording", one of which is a zero-length file,
> and the other (created second) has the actual recording.

(example:)

-rw-r--r-- 1 root root 0 2011-04-17 09:33 1013_20110417093336.mpg
-rw-r--r-- 1 root root 8041688 2011-04-17 09:33 1013_20110417093337.mpg

Is this "normal" ?
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
{Ooops: forgot to set the subject line to route my followup to the correct thread.}
Subject was: Re: [mythtv-users] mythtv-users Digest, Vol 97, Issue 48


I just upgraded from a 24-fixes 4/4 release to today's 4/17 version.

Livetv still is broken. I was actually able to change channels a couple of times, this time on the ATSC tuners, but once I was on an NTSC channel, it lost the ability to change channels. It would go through the motions, but end up back on the same channel.

Backend log:
...
2011-04-17 15:20:35.220 TVRec(3): Found channel (36) on current card(3).
2011-04-17 15:20:35.289 TVRec(3): ClearFlags(RingBufferReady,) -> RunMainLoop,CancelNextRecording,RecorderRunning,
2011-04-17 15:20:35.290 TVRec(3): HandleTuning Request: Program(no) channel(36) input() flags(LiveTV,)
2011-04-17 15:20:35.295 TVRec(3): HW Tuner: 3->3
2011-04-17 15:20:35.296 TVRec(3): ClearFlags(PENDINGACTIONS,) -> RunMainLoop,CancelNextRecording,RecorderRunning,
2011-04-17 15:20:35.296 TVRec(3): Waiting for recorder pause..
2011-04-17 15:20:35.297 TVRec(3): SetFlags(WaitingForRecPause,) -> RunMainLoop,CancelNextRecording,WaitingForRecPause,RecorderRunning,
2011-04-17 15:20:35.324 TVRec(3): ClearFlags(WaitingForRecPause,) -> RunMainLoop,CancelNextRecording,RecorderRunning,
2011-04-17 15:20:35.325 TVRec(3): Recorder paused, calling TuningFrequency
2011-04-17 15:20:35.326 TVRec(3): SwitchLiveTVRingBuffer(discont 1, set_rec 0)
2011-04-17 15:20:35.327 TVRec(3): GetProgramRingBufferForLiveTV()
2011-04-17 15:20:35.328 LoadFromScheduler(): Error, called from backend.
2011-04-17 15:20:35.332 Scheduler: FindNextLiveTVDir: next dir is '/mnt/store2'
2011-04-17 15:20:35.332 RecordingInfo(2036_20110417152035.nuv): StartedRecording: Recording to '/mnt/store2/2036_20110417152035.nuv'
2011-04-17 15:20:35.333 AutoExpire: Cardid 3: is starting a recording on an unknown fsID soon.
2011-04-17 15:20:35.342 AutoExpire: CalcParams()
2011-04-17 15:20:35.344 TVRec(3): StartedRecording(0x8cfad0) fn(/mnt/store2/2036_20110417152035.nuv)
2011-04-17 15:20:35.346 Cardid 3: max bitrate 73828 KB/min
2011-04-17 15:20:35.348 Maximal bitrate of busy encoders is 73828 KB/min
2011-04-17 15:20:35.348 fsID #1: Total: 912.6 GB Used: 756.8 GB Free: 155.9 GB
2011-04-17 15:20:35.350 TVRec(3): FinishedRecording(Book TV) in recgroup: LiveTV
2011-04-17 15:20:35.355 Chain: Updated endtime for '2004_20110417151959' to 20110417152035
2011-04-17 15:20:35.356 Cardid 3: max bitrate 9843 Kb/sec, fsID 1 max is now 73828 KB/min
2011-04-17 15:20:35.357 Max of 73828 KB/min for fsID 1 is higher than the existing Max of 0 so we'll use this Max instead
2011-04-17 15:20:35.358 AutoExpire: CalcParams(): Max required Free Space: 2.0 GB w/freq: 15 min
2011-04-17 15:20:35.358 Finished recording Book TV "Dave Cullen": channel 2004
2011-04-17 15:20:35.362 scheduler: Last message repeated 1 times: Finished recording: Willa's Wild Life "Unbearable Bear; Willa's Fun Raiser": channel 2012
2011-04-17 15:20:35.369 scheduler: Finished recording: Book TV "Dave Cullen": channel 2004
2011-04-17 15:20:35.371 SG(LiveTV): FindRecordingFile: Searching for '2004_20110417151959.nuv'
2011-04-17 15:20:35.371 SG(LiveTV): FindRecordingDir: Checking '/mnt/store2' for '/mnt/store2/2004_20110417151959.nuv'
2011-04-17 15:20:35.372 SG(LiveTV): FindRecordingFile: Found '/mnt/store2/2004_20110417151959.nuv'
2011-04-17 15:20:35.372 ProgramInfo(2004_20110417151959.nuv): GetPlaybackURL: File is local: '/mnt/store2/2004_20110417151959.nuv'
2011-04-17 15:20:35.375 PreviewQueue: Requesting preview for '2004_20110417151959.nuv_0x0_-1s'
2011-04-17 15:20:35.377 PreviewQueue: Requested preview for '2004_20110417151959.nuv_0x0_-1s'
2011-04-17 15:20:35.379 Preview Queued: '2004_2011-04-17T15:19:59' ''
2011-04-17 15:20:35.384 Chain: Appended@9 '2036_20110417152035'
2011-04-17 15:20:35.526 Channel(/dev/video0) Error: SetInputAndFormat(3, NTSC)
while setting input (v4l v2)
eno: Invalid argument (22)
2011-04-17 15:20:35.526 Channel(/dev/video0) Error: SetInputAndFormat(3, NTSC)
while setting format (v4l v2)
eno: Invalid argument (22)
2011-04-17 15:20:35.527 Channel(/dev/video0) Error: SetInputAndFormat(3, ATSC)
while setting input (v4l v2)
eno: Invalid argument (22)
2011-04-17 15:20:35.527 Channel(/dev/video0) Error: SetInputAndFormat(3, ATSC)
while setting format (v4l v2)
eno: Invalid argument (22)
2011-04-17 15:20:35.528 Channel(/dev/video0): SetInputAndFormat() failed
2011-04-17 15:20:35.528 TVRec(3): Starting Signal Monitor
2011-04-17 15:20:35.547 TVRec(3): SetupSignalMonitor(1, 1)
2011-04-17 15:20:35.547 TVRec(3): Signal monitor successfully created
2011-04-17 15:20:35.548 TVRec(3): SetFlags(SignalMonitorRunning,) -> RunMainLoop,CancelNextRecording,SignalMonitorRunning,RecorderRunning,
2011-04-17 15:20:35.548 TVRec(3): ClearFlags(WaitingForSignal,) -> RunMainLoop,CancelNextRecording,SignalMonitorRunning,RecorderRunning,
2011-04-17 15:20:35.549 TVRec(3): SetFlags(WaitingForSignal,) -> RunMainLoop,CancelNextRecording,WaitingForSignal,SignalMonitorRunning,RecorderRunning,
2011-04-17 15:20:35.549 RecBase(3:/dev/video0): SetRingBuffer(0x0)
2011-04-17 15:20:35.550 TVRec(3): SetFlags(DummyRecorderRunning,) -> RunMainLoop,CancelNextRecording,WaitingForSignal,SignalMonitorRunning,ANYRECRUNNING,
2011-04-17 15:20:35.550 DummyDTVRecorder -- started
2011-04-17 15:20:35.551 TVRec(3): SetFlags(RingBufferReady,) -> RunMainLoop,CancelNextRecording,WaitingForSignal,SignalMonitorRunning,ANYRECRUNNING,RingBufferReady,
2011-04-17 15:20:35.551 TVRec(3): ClearFlags(NeedToStartRecorder,) -> RunMainLoop,CancelNextRecording,WaitingForSignal,SignalMonitorRunning,ANYRECRUNNING,RingBufferReady,
2011-04-17 15:20:35.558 TVRec(3): SetFlags(NeedToStartRecorder,) -> RunMainLoop,CancelNextRecording,WaitingForSignal,NeedToStartRecorder,SignalMonitorRunning,ANYRECRUNNING,RingBufferReady,
2011-04-17 15:20:35.559 TVRec(3): Got good signal
2011-04-17 15:20:35.559 TVRec(3): TeardownSignalMonitor() -- begin
2011-04-17 15:20:35.604 TVRec(3): TeardownSignalMonitor() -- end
2011-04-17 15:20:35.605 TVRec(3): ClearFlags(SignalMonitorRunning,) -> RunMainLoop,CancelNextRecording,WaitingForSignal,NeedToStartRecorder,ANYRECRUNNING,RingBufferReady,
2011-04-17 15:20:35.613 TVRec(3): ClearFlags(WaitingForSignal,) -> RunMainLoop,CancelNextRecording,NeedToStartRecorder,ANYRECRUNNING,RingBufferReady,
2011-04-17 15:20:35.614 TVRec(3): Restarting Recorder
2011-04-17 15:20:35.614 TVRec(3): ClearFlags(DummyRecorderRunning,) -> RunMainLoop,CancelNextRecording,NeedToStartRecorder,RecorderRunning,RingBufferReady,
2011-04-17 15:20:35.616 TVRec(3): FinishedRecording(CNN Newsroom) in recgroup: LiveTV
2011-04-17 15:20:35.617 Chain: Updated endtime for '2036_20110417152035' to 20110417152035
2011-04-17 15:20:35.619 Finished recording CNN Newsroom: channel 2036
2011-04-17 15:20:35.622 scheduler: Finished recording: CNN Newsroom: channel 2036
2011-04-17 15:20:35.623 TVRec(3): SwitchLiveTVRingBuffer(discont 1, set_rec 0)
2011-04-17 15:20:35.625 TVRec(3): GetProgramRingBufferForLiveTV()
2011-04-17 15:20:35.626 Scheduler: FindNextLiveTVDir: next dir is '/mnt/store2'
2011-04-17 15:20:35.627 AutoExpire: Cardid 3: is starting a recording on an unknown fsID soon.
2011-04-17 15:20:35.628 AutoExpire: CalcParams()
2011-04-17 15:20:35.632 Cardid 3: max bitrate 73828 KB/min
2011-04-17 15:20:35.632 Maximal bitrate of busy encoders is 73828 KB/min
2011-04-17 15:20:35.633 fsID #1: Total: 912.6 GB Used: 756.8 GB Free: 155.9 GB
2011-04-17 15:20:35.635 Cardid 3: max bitrate 9843 Kb/sec, fsID 1 max is now 73828 KB/min
2011-04-17 15:20:35.641 Max of 73828 KB/min for fsID 1 is higher than the existing Max of 0 so we'll use this Max instead
2011-04-17 15:20:35.642 AutoExpire: CalcParams(): Max required Free Space: 2.0 GB w/freq: 15 min
2011-04-17 15:20:35.628 LoadFromScheduler(): Error, called from backend.
2011-04-17 15:20:35.649 RecordingInfo(2004_20110417152035.nuv): StartedRecording: Recording to '/mnt/store2/2004_20110417152035.nuv'
2011-04-17 15:20:35.652 TVRec(3): StartedRecording(0x89cb40) fn(/mnt/store2/2004_20110417152035.nuv)
2011-04-17 15:20:35.677 TVRec(3): FinishedRecording(CNN Newsroom) in recgroup: LiveTV
2011-04-17 15:20:35.681 Chain: Updated endtime for '2036_20110417152035' to 20110417152035
2011-04-17 15:20:35.683 Finished recording CNN Newsroom: channel 2036
2011-04-17 15:20:35.686 Chain: Appended@10 '2004_20110417152035'
2011-04-17 15:20:35.688 RecBase(3:/dev/video0): SetRingBuffer(0x8b8360) '/mnt/store2/2004_20110417152035.nuv'
2011-04-17 15:20:35.688 MainServer::ANN Monitor
2011-04-17 15:20:35.696 adding: myth as a client (events: 0)
2011-04-17 15:20:35.690 RecBase(3:/dev/video0): SetRecording(0x8a6150) title(Book TV)
2011-04-17 15:20:35.697 MainServer::ANN Monitor
2011-04-17 15:20:35.699 adding: myth as a client (events: 1)
2011-04-17 15:20:35.704 NVR(/dev/video0) Error: Resetting and re-queueing
2011-04-17 15:20:35.704 TVRec(3): ClearFlags(NeedToStartRecorder,) -> RunMainLoop,CancelNextRecording,RecorderRunning,RingBufferReady,
2011-04-17 15:20:35.982 Preview: Preview process returned 0.
2011-04-17 15:20:35.983 Preview: Preview process ran ok.
2011-04-17 15:20:36.867 About to delete file: /mnt/store2/3121_20110417151859.mpg
2011-04-17 15:20:42.877 About to delete file: /mnt/store2/3121_20110417151900.mpg
2011-04-17 15:20:44.884 About to delete file: /mnt/store2/3121_20110417151900.mpg.png
2011-04-17 15:20:53.554 TVRec(3): StopLiveTV(void) curRec: 0x89cb40 pseudoRec: 0x0
2011-04-17 15:20:53.555 TVRec(3): Changing from WatchingLiveTV to None
2011-04-17 15:20:53.556 TVRec(3): ClearFlags(FrontendReady,CancelNextRecording,) -> RunMainLoop,RecorderRunning,RingBufferReady,
2011-04-17 15:20:53.557 TVRec(3): HandleTuning Request: Program(no) channel() input() flags(KillRec,KillRingBuffer,)
2011-04-17 15:20:54.030 TVRec(3): ClearFlags(RecorderRunning,) -> RunMainLoop,RingBufferReady,
2011-04-17 15:20:54.051 RecBase(3:/dev/video0): SetRecording(0x0)
2011-04-17 15:20:54.052 TVRec(3): FinishedRecording(Book TV) in recgroup: LiveTV
2011-04-17 15:20:54.053 Chain: Updated endtime for '2004_20110417152035' to 20110417152054
2011-04-17 15:20:54.055 TVRec(3): ClearFlags(RecorderRunning,) -> RunMainLoop,RingBufferReady,
2011-04-17 15:20:54.055 TVRec(3): Tearing down RingBuffer
2011-04-17 15:20:54.148 TVRec(3): ClearFlags(PENDINGACTIONS,) -> RunMainLoop,RingBufferReady,
2011-04-17 15:20:54.149 TVRec(3): SetFlags(FrontendReady,) -> FrontendReady,RunMainLoop,RingBufferReady,


frontend
...
2011-04-17 15:20:05.623 AFD Warning: ScanATSCCaptionStreams() called with no PMT
2011-04-17 15:20:05.623 AFD: Opened codec 0x7efee4fa10c0, id(MPEG4) type(Video)
2011-04-17 15:20:05.627 AFD: Resetting byte context eof (livetv 1 was eof 0)
2011-04-17 15:20:14.283 pause_active: 0
2011-04-17 15:20:30.726 [mpeg4 @ 0x7efef73c86e0]time_base.den==0
2011-04-17 15:20:30.726 [mpeg4 @ 0x7efef73c86e0]time_base.den==0
2011-04-17 15:20:30.726 [mpeg4 @ 0x7efef73c86e0]header damaged
2011-04-17 15:20:30.726 AFD Error: Unknown decoding error
2011-04-17 15:20:36.004 ScreenSaverX11Private: DPMS Deactivated 1
2011-04-17 15:20:36.088 RingBuf(/mnt/store2/2004_20110417152035.nuv) Warning: Not starting read ahead thread, already running
2011-04-17 15:20:40.881 RingBuf(/mnt/store2/2004_20110417152035.nuv): Waited 0.2 seconds for data
to become available... 32365 < 32768
2011-04-17 15:20:41.368 AFD Warning: ScanATSCCaptionStreams() called with no PMT
2011-04-17 15:20:41.369 AFD: Opened codec 0x20dff30, id(MPEG4) type(Video)
2011-04-17 15:20:41.375 AFD: Resetting byte context eof (livetv 1 was eof 0)
2011-04-17 15:20:46.446 [mpeg4 @ 0x7efef73c86e0]time_base.den==0
2011-04-17 15:20:46.446 [mpeg4 @ 0x7efef73c86e0]time_base.den==0
2011-04-17 15:20:46.446 [mpeg4 @ 0x7efef73c86e0]header damaged
2011-04-17 15:20:46.446 AFD Error: Unknown decoding error
2011-04-17 15:20:48.081 [mpeg4 @ 0x7efef73c86e0]time_base.den==0
2011-04-17 15:20:48.081 [mpeg4 @ 0x7efef73c86e0]time_base.den==0
2011-04-17 15:20:48.081 [mpeg4 @ 0x7efef73c86e0]header damaged
2011-04-17 15:20:48.081 AFD Error: Unknown decoding error
2011-04-17 15:20:53.521 TV: Attempting to change from WatchingLiveTV to None
2011-04-17 15:20:53.526 MythPainter: 6 images not yet de-allocated.
2011-04-17 15:20:54.149 TV: Changing from WatchingLiveTV to None
2011-04-17 15:20:54.151 ScreenSaverX11Private: DPMS Reactivated 1


------------------------------

Message: 21
Date: Sun, 17 Apr 2011 22:43:57 -0500
From: Kenneth Emerson <kenneth.emerson@gmail.com>
Subject: Re: [mythtv-users] Playback problem -- random short pauses
To: Discussion about MythTV <mythtv-users@mythtv.org>
Message-ID: <BANLkTim4wQB3PPj2pH9vV=57UopcmkTDkQ@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

On Sun, Apr 17, 2011 at 4:03 PM, Tom Lichti <redpepperracing@gmail.com>wrote:

> - if you have your backend storage directory nfs mounted on your
> remote frontend, try unmounting it to force the backend to stream it.
> Since I have done that, I have not see one hiccup (aside from when the
> OSD is present, but I can live with that). When there were hiccups,
> they would show as a series of these messages in the frontend log:
>
> 2011-04-17 16:34:58.674 Player(0): Waited 100ms for video frames from
> decoder AAAAAAAAAAAAAAAAA
> 2011-04-17 16:34:58.683 Player(0): Waited 100ms for video frames from
> decoder AAAAAAAAAAAAAAAAA
> 2011-04-17 16:34:58.692 Player(0): Waited 100ms for video frames from
> decoder AAAAAAAAAAAAAAAAA
> 2011-04-17 16:34:58.809 Player(0): Waited 100ms for video frames from
> decoder AAAAAAAAAAAAAAAAA
> 2011-04-17 16:34:58.818 Player(0): Waited 100ms for video frames from
> decoder AAAAAAAAAAAAAAAAA
> 2011-04-17 16:34:59.059 Player(0): Waited 100ms for video frames from
> decoder AAAAAAAAAAAAAAAAA
> 2011-04-17 16:34:59.068 Player(0): Waited 100ms for video frames from
> decoder AAAAAAAAAAAAAAAAA
>
> I know, it's probably obvious to everyone else, but if it helps
> someone else, great!\
>
> Certainly not obvious to me. IIRC, there have been several threads over
the past two years discussing different switches to use when using
nfs-mounted file systems for recordings. A search of the archives can
probably locate them; however, nfs isn't the only reason (evidently) that
causes these errors to crop up, but there may be a common thread between the
nfs issue and what I am seeing (I only have a single box -- combined FE/BE
so no nfs issues).

I reported before that I was going to test to see if background jobs
(transcoding, commflagging, other recordings) could be causing these
"hiccups". Sadly, they don't seem to have any affect on my problem. While
I was watching an mpeg file with no other myth-jobs running, there were
several instances of messeages similar to the above mentioned errors.
Specifically, mine look like:

2011-04-16 21:52:31.692 Player(0): Waited 100ms for video buffers
ALAAAAAAAAAAAAaaA

At this point, I am out of ideas. Very annoying. If anyone has other ideas
to try to help further narrow the search, I'm all ears.

-- Ken Emerson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-users/attachments/20110417/2c8fe23f/attachment-0001.html

------------------------------

Message: 22
Date: Sun, 17 Apr 2011 21:57:46 -0600
From: Greg Grotsky <spikeygg.mythbox@gmail.com>
Subject: [mythtv-users] User Job Progress Meter?
To: Discussion about MythTV <mythtv-users@mythtv.org>
Message-ID: <BANLkTin-XQXGbL3tkS6QX38gaee-vR22ng@mail.gmail.com>
Content-Type: text/plain; charset="iso-8859-1"

I like how commercial detection jobs show the progress status in
percentage on the "System Information" screen and in mythweb. Is there any
way for me to have my user jobs feed back this kind of progress meter?

Thanks,
-Greg
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.mythtv.org/pipermail/mythtv-users/attachments/20110417/5cc20a59/attachment.html

------------------------------

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users

End of mythtv-users Digest, Vol 97, Issue 49
********************************************
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On 17 Apr 2011, at 01:24, Adam Felson wrote:

> I've been using mythtv since around version 0.12 and have never found the live tv function to be terribly useable. For me there have always been lots of crashes and it seems to have only gotten worse.
>
> While I've watched some new functionality like the internal video player go from alpha quality to being a wonderful solidly mature feature, live TV for me is still problematical.

The advice often given is to schedule a recording then immediately start watching that, ignoring the troublesome live TV player, this i what I do on the odd time I want to watch something that is on now, I usually leave the recording a few minutes so the ads can be skipped past too.

Has anyone considered restructuring live tv so it does exactly that?


>
> I currently have two sets of capture devices:
> a pair of NTSC plextor convertx usb2 external capture units w/ mpeg4 encoding
> a pair of HDHomeRun ATSC ethernet external capture units each with a pair of ATSC tuners.
>
> They all work very well for recording.
>
> LiveTV has always had problems tuning. 95% of the time it would crash after a channel change.
>
> For liveTV, version 0.23 got bad and 0.24 has gotten worse. I can no longer switch channels at all.
>
> I'd appreciate any suggestions on how to debug my setup. I'd rather not completely erase my capture cards, as it'll cause all my recordings to no longer display what channel they were recorded from. However, if I have to, then I will.
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
> Message: 18
On Tue, 19 Apr 2011 10:04:57 +0100, Andre <mythtv-list@dinkum.org.uk> spoke
>
>

> The advice often given is to schedule a recording then immediately
> start watching that, ignoring the troublesome live TV player, this i
> what I do on the odd time I want to watch something that is on now,
> I usually leave the recording a few minutes so the ads can be
> skipped past too.
>
> Has anyone considered restructuring live tv so it does exactly that?


I'd hate to see that; why have such complexity on such a simple task?
What I, and I suspect many others, have done is put a tv tuner on my entertainment system and have given up on using mythtv for live tv.

For LiveTV, UI is fine. It should behave like a TV but with the ability to pause and it does when it isn't crashing and when it can actually change channels.

Seems to have strange keyboard assignments. The up/down buttons become channel buttons.
My remote control and most others have separate cursor and channel buttons. Probably a simple setting that I haven't fixed yet.
Another problem with LiveTv is the backend's insistence on using the same capture device.
If I have 4 atsc tuners, tuner 1 is recording, tuner 2 is livetv, and 3 and 4 are unused,
why force the user off tuner 2 or abort the recording if a recording was scheduled for it?
It should simply use one of the unused tuners that have the same source. Such a smart scheduler shouldn't be so rock stupid when it comes to conflicts with the user on livetv.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On Wed, Apr 20, 2011 at 7:19 AM, Adam Felson <adam.mythtv@thefelsons.us>wrote:

>
> > Message: 18
> On Tue, 19 Apr 2011 10:04:57 +0100, Andre <mythtv-list@dinkum.org.uk>
> spoke
> >
> >
>
> > The advice often given is to schedule a recording then immediately
> > start watching that, ignoring the troublesome live TV player, this i
> > what I do on the odd time I want to watch something that is on now,
> > I usually leave the recording a few minutes so the ads can be
> > skipped past too.
> >
> > Has anyone considered restructuring live tv so it does exactly that?
>
>
> I'd hate to see that; why have such complexity on such a simple task?
> What I, and I suspect many others, have done is put a tv tuner on my
> entertainment system and have given up on using mythtv for live tv.
>
> For LiveTV, UI is fine. It should behave like a TV but with the ability to
> pause and it does when it isn't crashing and when it can actually change
> channels.
>
> Seems to have strange keyboard assignments. The up/down buttons become
> channel buttons.
> My remote control and most others have separate cursor and channel buttons.
> Probably a simple setting that I haven't fixed yet.
> Another problem with LiveTv is the backend's insistence on using the same
> capture device.
> If I have 4 atsc tuners, tuner 1 is recording, tuner 2 is livetv, and 3 and
> 4 are unused,
> why force the user off tuner 2 or abort the recording if a recording was
> scheduled for it?
> It should simply use one of the unused tuners that have the same source.
> Such a smart scheduler shouldn't be so rock stupid when it comes to
> conflicts with the user on livetv.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>

There is the configuration option to allow Live-TV to move scheduled
recordings. The alternate is to configure Live-TV to use a tuner which has
little to no scheduled recordings.

--
Working on World Domination since 2001
Re: Request for help making live TV useable [ In reply to ]
Mark Lord <mythtv@rtr.ca> wrote:
> On 11-04-17 09:32 AM, Mark Lord wrote:
> ..
> > Now.. something weird since I upgraded from 0.22 to 0.24:
> > When I view LiveTV (for analog OTA NTSC), there are always *two*
> > files created for each "recording", one of which is a zero-length file,
> > and the other (created second) has the actual recording.
>
> (example:)
>
> -rw-r--r-- 1 root root 0 2011-04-17 09:33 1013_20110417093336.mpg
> -rw-r--r-- 1 root root 8041688 2011-04-17 09:33 1013_20110417093337.mpg
>
> Is this "normal" ?
it is not..
I had to reset all my frontendsettings and the additional zero-length
files were no longer created... In fact i had to reset 2 of my 3
frontends.. (mythfrontend --reset)
Sadly I never figured out what really caused this behavior...

Tobi
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
@mythtv at rtr


>However.. I also noticed a bunch of decoder fixes in trunk,
>dealing with calculating the number of buffers needed,
>and fixing bugs where buffers were being recycled while
>still in use and so on.
>
>So I backported those as well to 0.24-fixes. This seems to have made
>a noticeable improvement in my PVR-250 LiveTV channel changes.
>I can now often change channels 8-10 times without locking up,
>whereas normally only (exactly) three channel changes were needed before.

Hi,
May You post here list of backported commits.
I have quite similar problems to Yours and want to try backport and see how it helps in my case.
Thx
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On Thu, Apr 21, 2011 at 1:47 AM, warpme <warpme@o2.pl> wrote:

> @mythtv at rtr
>
>
> >However.. I also noticed a bunch of decoder fixes in trunk,
> >dealing with calculating the number of buffers needed,
> >and fixing bugs where buffers were being recycled while
> >still in use and so on.
> >
> >So I backported those as well to 0.24-fixes. This seems to have made
> >a noticeable improvement in my PVR-250 LiveTV channel changes.
> >I can now often change channels 8-10 times without locking up,
> >whereas normally only (exactly) three channel changes were needed before.
>
> Hi,
> May You post here list of backported commits.
> I have quite similar problems to Yours and want to try backport and see how
> it helps in my case.
> Thx
>
>
Seems rather odd to me that people would take the trouble to backport most
of master's changes back to 0.24-fixes rather than just run master. You'd
probably have an easier time just running the bleeding edge.
Re: Request for help making live TV useable [ In reply to ]
On 20 Apr 2011, at 15:19, Adam Felson wrote:

>
>> Message: 18
> On Tue, 19 Apr 2011 10:04:57 +0100, Andre <mythtv-list@dinkum.org.uk> spoke
>>
>>
>
>> The advice often given is to schedule a recording then immediately
>> start watching that, ignoring the troublesome live TV player, this i
>> what I do on the odd time I want to watch something that is on now,
>> I usually leave the recording a few minutes so the ads can be
>> skipped past too.
>>
>> Has anyone considered restructuring live tv so it does exactly that?
>
>
> I'd hate to see that; why have such complexity on such a simple task?

>From following various live tv threads over the years I suspect it's already significantly more complicated than that and the code somewhat unloved!


> What I, and I suspect many others, have done is put a tv tuner on my entertainment system and have given up on using mythtv for live tv

That would be fine, I haven't watched any live tv since discovering I could buy cheap betamax vcrs (at the time tapes cost more than the machines) and programme one each for regular weekly TV shows ;-) The family has always worked wacky hours so we had a vcr in the 70's Philips 1500, mythtv is just a logical progression.


> .
>
> For LiveTV, UI is fine. It should behave like a TV but with the ability to pause and it does when it isn't crashing and when it can actually change channels.

There are other htpc projects that behave like that myth seems happy to be different.

>
> Seems to have strange keyboard assignments. The up/down buttons become channel buttons.
> My remote control and most others have separate cursor and channel buttons. Probably a simple setting that I haven't fixed yet.
> Another problem with LiveTv is the backend's insistence on using the same capture device.
> If I have 4 atsc tuners, tuner 1 is recording, tuner 2 is livetv, and 3 and 4 are unused,
> why force the user off tuner 2 or abort the recording if a recording was scheduled for it?
> It should simply use one of the unused tuners that have the same source. Such a smart scheduler shouldn't be so rock stupid when it comes to conflicts with the user on livetv.
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://www.mythtv.org/mailman/listinfo/mythtv-users
>

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
>Seems rather odd to me that people would take the trouble to backport most
>of master's changes back to 0.24-fixes rather than just run master. You'd
>probably have an easier time just running the bleeding edge.

In fact I just started to be prepare to such move. Currently my BE & FE build systems are ready to switch to master via simple 1 line edit.
Issue is that flipping between 0.24 & master is highly asymmetric in terms of labor. 0.24->master is fully automated while master->0.24 req. high amount manual work with DB. I was trying asses what switch to master means
(http://www.gossamer-threads.com/lists/mythtv/users/476819) - but as You without progress.
As my sys is production sys to whole family (3 person with individual FEs) - I MUST be very careful. DB schema changes is only thing causing me to be so conservative.
Alternative here is patching of 0.24. While it requires much more work from me - reverting to stable sys takes 40s (10 sec to reinstall BE bin package on BE server + 30sec to reboot diskless FE with old PXE image).
>From dev point of view I fully agree with You. From user point of view I'm forced to be much more conservative than I want to be....
br



_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On 11-04-21 04:02 AM, diespambox@gmx.net wrote:
> Mark Lord <mythtv@rtr.ca> wrote:
>> On 11-04-17 09:32 AM, Mark Lord wrote:
>> ..
>>> Now.. something weird since I upgraded from 0.22 to 0.24:
>>> When I view LiveTV (for analog OTA NTSC), there are always *two*
>>> files created for each "recording", one of which is a zero-length file,
>>> and the other (created second) has the actual recording.
>>
>> (example:)
>>
>> -rw-r--r-- 1 root root 0 2011-04-17 09:33 1013_20110417093336.mpg
>> -rw-r--r-- 1 root root 8041688 2011-04-17 09:33 1013_20110417093337.mpg
>>
>> Is this "normal" ?
> it is not..
> I had to reset all my frontendsettings and the additional zero-length
> files were no longer created... In fact i had to reset 2 of my 3
> frontends.. (mythfrontend --reset)
> Sadly I never figured out what really caused this behavior...
>
> Tobi


Oh, good. So at least one other person has looked for and seen the same
behaviour. :)
I'll look at trying the mythfrontend --reset on my "test" system here later, thanks.

And then I'll manually reenter all of the original settings,
and see if the misbehaviour returns again (it should).

Cheers
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On 11-04-21 05:07 AM, Gavin Hurlbut wrote:
>
> Seems rather odd to me that people would take the trouble to backport most of
> master's changes back to 0.24-fixes rather than just run master. You'd probably
> have an easier time just running the bleeding edge.


By staying with 0.24-fixes, the database schema remains constant,
ensuring compatibility with all of the various frontends around
the house. This also allows backing-out commits that break things,
without worrying about database issues.

Very sensible.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On 11-04-21 08:54 AM, Mark Lord wrote:
> On 11-04-21 05:07 AM, Gavin Hurlbut wrote:
>>
>> Seems rather odd to me that people would take the trouble to backport most of
>> master's changes back to 0.24-fixes rather than just run master. You'd probably
>> have an easier time just running the bleeding edge.
>
>
> By staying with 0.24-fixes, the database schema remains constant,
> ensuring compatibility with all of the various frontends around
> the house. This also allows backing-out commits that break things,
> without worrying about database issues.
>
> Very sensible.


Oh, and not to mention that 0.24-fixes has xvmc playback support,
which is (due to be?) removed from trunk.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On 11-04-21 04:47 AM, warpme wrote:
..
>> However.. I also noticed a bunch of decoder fixes in trunk,
>> dealing with calculating the number of buffers needed,
>> and fixing bugs where buffers were being recycled while
>> still in use and so on.
>>
>> So I backported those as well to 0.24-fixes. This seems to have made
>> a noticeable improvement in my PVR-250 LiveTV channel changes.
>> I can now often change channels 8-10 times without locking up,
>> whereas normally only (exactly) three channel changes were needed before.
>
> Hi,
> May You post here list of backported commits.
> I have quite similar problems to Yours and want to try backport and see how it helps in my case.
..


I began with this commit from tralph:

https://github.com/MythTV/mythtv/commit/f8c108ef9a5c6bac9ec2414c47e2f404047e43b9

and then added a few follow-on commits from mark-kendall:

https://github.com/MythTV/mythtv/commit/f54bfcb57dc26cc3a084be8fbed4bc4620726b1b
https://github.com/MythTV/mythtv/commit/f2713206d10b3ce3198bf4bb40cb60206a36c3d8
https://github.com/MythTV/mythtv/commit/bd7d2da5b17cdf15c51828548080633be948c79b
https://github.com/MythTV/mythtv/commit/7d302773791cc8e5d31500143549e25a3ab591fc

And finally the commit that eliminates any need to set vdpaubuffersize=
in the playback profiles:

https://github.com/MythTV/mythtv/commit/5e04d57bc87a6f422ccba79a493bebef50566162

Those did not all apply cleanly to 0.24-fixes, so a bit of work was required
to get them to play nicely.

Oh and there was one other commit in there somewhere to initialize
the vdpau surface states or something --> that one gets rid of the corrupted
screen backgrounds after a mythfrontend crash.

Anyway, the patch files that work for me are now on my server
at http://rtr.ca/mythtv_patches/ --> patches 40 through 45.

They probably will apply cleanly to any mythtv-0.24-fixes base,
but there might be a mismatch or two due to other patches
(not yet made available) which I may have applied underneath it all.

Cheers

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On Thu, Apr 21, 2011 at 9:18 AM, Mark Lord <mythtv@rtr.ca> wrote:
> On 11-04-21 04:47 AM, warpme wrote:
> ..
>>> However.. I also noticed a bunch of decoder fixes in trunk,
>>> dealing with calculating the number of buffers needed,
>>> and fixing bugs where buffers were being recycled while
>>> still in use and so on.
>>>
>>> So I backported those as well to 0.24-fixes. This seems to have made
>>> a noticeable improvement in my PVR-250 LiveTV channel changes.
>>> I can now often change channels 8-10 times without locking up,
>>> whereas normally only (exactly) three channel changes were needed before.
>>
>> Hi,
>> May You post here list of backported commits.
>> I have quite similar problems to Yours and want to try backport and see how it helps in my case.
> ..
>
>
> I began with this commit from tralph:
>
> https://github.com/MythTV/mythtv/commit/f8c108ef9a5c6bac9ec2414c47e2f404047e43b9
>
> and then added a few follow-on commits from  mark-kendall:
>
> https://github.com/MythTV/mythtv/commit/f54bfcb57dc26cc3a084be8fbed4bc4620726b1b
> https://github.com/MythTV/mythtv/commit/f2713206d10b3ce3198bf4bb40cb60206a36c3d8
> https://github.com/MythTV/mythtv/commit/bd7d2da5b17cdf15c51828548080633be948c79b
> https://github.com/MythTV/mythtv/commit/7d302773791cc8e5d31500143549e25a3ab591fc
>
> And finally the commit that eliminates any need to set vdpaubuffersize=
> in the playback profiles:
>
> https://github.com/MythTV/mythtv/commit/5e04d57bc87a6f422ccba79a493bebef50566162
>
> Those did not all apply cleanly to 0.24-fixes, so a bit of work was required
> to get them to play nicely.
>
> Oh and there was one other commit in there somewhere to initialize
> the vdpau surface states or something --> that one gets rid of the corrupted
> screen backgrounds after a mythfrontend crash.
>
> Anyway, the patch files that work for me are now on my server
> at http://rtr.ca/mythtv_patches/  --> patches 40 through 45.
>
> They probably will apply cleanly to any mythtv-0.24-fixes base,
> but there might be a mismatch or two due to other patches
> (not yet made available) which I may have applied underneath it all.
>
> Cheers
>

You might want to add this to your back-port recipe as it directly
impacts channel changing:

https://github.com/MythTV/mythtv/commit/4693357f1

Also, the zero-byte file you see is normal and used by the signal monitor.

Regards.
--
Taylor
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On Thu, Apr 21, 2011 at 10:31 AM, Taylor Ralph <taylor.ralph@gmail.com> wrote:
> On Thu, Apr 21, 2011 at 9:18 AM, Mark Lord <mythtv@rtr.ca> wrote:
>> On 11-04-21 04:47 AM, warpme wrote:
>> ..
>>>> However.. I also noticed a bunch of decoder fixes in trunk,
>>>> dealing with calculating the number of buffers needed,
>>>> and fixing bugs where buffers were being recycled while
>>>> still in use and so on.
>>>>
>>>> So I backported those as well to 0.24-fixes. This seems to have made
>>>> a noticeable improvement in my PVR-250 LiveTV channel changes.
>>>> I can now often change channels 8-10 times without locking up,
>>>> whereas normally only (exactly) three channel changes were needed before.
>>>
>>> Hi,
>>> May You post here list of backported commits.
>>> I have quite similar problems to Yours and want to try backport and see how it helps in my case.
>> ..
>>
>>
>> I began with this commit from tralph:
>>
>> https://github.com/MythTV/mythtv/commit/f8c108ef9a5c6bac9ec2414c47e2f404047e43b9
>>
>> and then added a few follow-on commits from  mark-kendall:
>>
>> https://github.com/MythTV/mythtv/commit/f54bfcb57dc26cc3a084be8fbed4bc4620726b1b
>> https://github.com/MythTV/mythtv/commit/f2713206d10b3ce3198bf4bb40cb60206a36c3d8
>> https://github.com/MythTV/mythtv/commit/bd7d2da5b17cdf15c51828548080633be948c79b
>> https://github.com/MythTV/mythtv/commit/7d302773791cc8e5d31500143549e25a3ab591fc
>>
>> And finally the commit that eliminates any need to set vdpaubuffersize=
>> in the playback profiles:
>>
>> https://github.com/MythTV/mythtv/commit/5e04d57bc87a6f422ccba79a493bebef50566162
>>
>> Those did not all apply cleanly to 0.24-fixes, so a bit of work was required
>> to get them to play nicely.
>>
>> Oh and there was one other commit in there somewhere to initialize
>> the vdpau surface states or something --> that one gets rid of the corrupted
>> screen backgrounds after a mythfrontend crash.
>>
>> Anyway, the patch files that work for me are now on my server
>> at http://rtr.ca/mythtv_patches/  --> patches 40 through 45.
>>
>> They probably will apply cleanly to any mythtv-0.24-fixes base,
>> but there might be a mismatch or two due to other patches
>> (not yet made available) which I may have applied underneath it all.
>>
>> Cheers
>>
>
> You might want to add this to your back-port recipe as it directly
> impacts channel changing:
>
> https://github.com/MythTV/mythtv/commit/4693357f1
>

Nevermind, that was already back-ported to 0.24/fixes.

Regards.
--
Taylor
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
On 4/21/2011 08:56, Mark Lord wrote:
> On 11-04-21 08:54 AM, Mark Lord wrote:
>> On 11-04-21 05:07 AM, Gavin Hurlbut wrote:
>>> Seems rather odd to me that people would take the trouble to backport most of
>>> master's changes back to 0.24-fixes rather than just run master. You'd probably
>>> have an easier time just running the bleeding edge.
>> By staying with 0.24-fixes, the database schema remains constant,
>> ensuring compatibility with all of the various frontends around
>> the house. This also allows backing-out commits that break things,
>> without worrying about database issues.
>>
>> Very sensible.
> xvmc playback support, which is (due to be?) removed from trunk.

Followed by much fanfare and celebration.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users
Re: Request for help making live TV useable [ In reply to ]
Mark Lord wrote:
> On 11-04-21 08:54 AM, Mark Lord wrote:
>
>> On 11-04-21 05:07 AM, Gavin Hurlbut wrote:
>>
>>> Seems rather odd to me that people would take the trouble to backport most of
>>> master's changes back to 0.24-fixes rather than just run master. You'd probably
>>> have an easier time just running the bleeding edge.
>>>
>> By staying with 0.24-fixes, the database schema remains constant,
>> ensuring compatibility with all of the various frontends around
>> the house. This also allows backing-out commits that break things,
>> without worrying about database issues.
>>
>>

Or worrying about the WAF.

>> Very sensible.
>>
>

I agree.

> Oh, and not to mention that 0.24-fixes has xvmc playback support,
> which is (due to be?) removed from trunk.
>

Thanks for posting the list of the changes that you have backported.

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://www.mythtv.org/mailman/listinfo/mythtv-users

1 2  View All