[mythtv-users] Can't record analog from Hauppauge 2255

John P Poet jppoet at gmail.com
Wed Feb 3 22:14:23 UTC 2016


On Wed, Feb 3, 2016 at 11:30 AM David Parker <parker.david.a at gmail.com>
wrote:

> On Wed, Feb 3, 2016 at 12:35 PM, Stuart Auchterlonie <
> stuarta at squashedfrog.net> wrote:
>
>> On 02/02/16 16:17, David Parker wrote:
>> > On Tue, Feb 2, 2016 at 5:51 AM, Stuart Auchterlonie
>> > <stuarta at squashedfrog.net <mailto:stuarta at squashedfrog.net>> wrote:
>> >
>> >     Hi David,
>> >
>> >     Yes you can just apply the same fix to the fixes/0.27 tree, and
>> it's far
>> >     simpler too, no messing around with databases.
>> >
>> >     I'll add a patch file to the ticket to make it even easier ;-)
>> >
>> >
>> > Thanks, Stuart.
>> >
>> > I dropped the patched file into the exiting 0.27-fixes tree I had, but
>> > unfortunately it does not seem to have worked.  Attempting to watch live
>> > TV fails immediately, with these messages in the backend log:
>> >
>>
>> Okay so that didn't work, can you try modifying the string
>> "saa7164" to "saa7164[0]" as that's the driver name being reported by
>> v4l2-ctl.
>>
>
> Thanks, Stuart.  Unfortunately it still gets the same result.
>
> I did notice that there's something in the MythTV frontend log when I
> attempt to watch live TV, although nothing when a recording fails.  When I
> try to watch live TV this gets logged by the frontend:
>
> 2016-02-03 13:04:10.273953 I  TV: Creating TV object
> 2016-02-03 13:04:10.296223 N  Suspending idle timer
> 2016-02-03 13:04:10.297423 I  TV: Created TvPlayWindow.
> 2016-02-03 13:04:10.311289 I  TV: Attempting to change from None to
> WatchingLiveTV
> 2016-02-03 13:04:10.311326 I  MythCoreContext: Connecting to backend
> server: ::1:6543 (try 1 of 1)
> 2016-02-03 13:04:10.322561 N  TV: Spawning LiveTV Recorder -- begin
> 2016-02-03 13:04:10.363476 N  TV: Spawning LiveTV Recorder -- end
> 2016-02-03 13:04:10.364105 E  GetEntryAt(-1) failed.
> 2016-02-03 13:04:10.364122 E  It appears that your backend may be
> misconfigured.  Check your backend logs to determine whether your capture
> cards, lineups, channels, or storage configuration are reporting errors.
> This issue is commonly caused by failing to complete all setup steps
> properly.  You may wish to review the documentation for mythtv-setup.
> 2016-02-03 13:04:10.364205 E  EntryToProgram(0 at 1969-12-31T19:00:00)
> failed to get pginfo
> 2016-02-03 13:04:10.364225 E  TV: HandleStateChange(): LiveTV not
> successfully started
> 2016-02-03 13:04:10.364592 E  TV: LiveTV not successfully started
> 2016-02-03 13:04:10.365858 I  TV: Main UI disabled.
> 2016-02-03 13:04:10.365918 I  TV: Entering main playback loop.
> 2016-02-03 13:04:10.366586 I  TV: Exiting main playback loop.
> 2016-02-03 13:04:10.378108 N  Resuming idle timer
>
> I have no idea what may be misconfigured in the MythTV backend, though, so
> I don't know if that message is accurate.
> <https://forum.mythtv.org>
>

Sorry if I missed you already posting this, but can you add the mythbackend
logs, with mythbackend running with "-v channel,record"?

Thanks,

John
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mythtv.org/pipermail/mythtv-users/attachments/20160203/40ff516a/attachment.html>


More information about the mythtv-users mailing list