[mythtv-users] various problems after

Scott Kaminski scott.kaminski at gmail.com
Sat Mar 17 19:21:15 UTC 2007


I recently setup a frontend system with a PCHDTV 3000 card that would
use my existing system as a backend. However after i did this i found
that i was not able to get myth to record anymore tv shows.

I setup this new frontend system because based on what i've read the
pchdtv cards conflict with the IVTV drivers especially if you enable
the NTSC part of the PCHDTV card. Well my cable provider encrypts(Shaw
in Vancouver) all the HDTV channels and i can only pick up 1 HDTV
channel via rabbit ears. So its not really worth a hell of a lot to me
with NTSC capabilities.

What i'm looking for is some help in trying to find the source of some
of my problem, I use the svn version of mythtv to build both my
frontend system and my backend.

Here is a summary of my problem:
-can't record any tvshows on frontend or backend systems when scheduling
-can watch livetv on backend system
-can not watch livetv on backend system
-can watch previously recorded content on frontend system and backend
system without any issues

Here is the version info from my backend:

scott at mythtv-64 ~ $ /usr/local/mythtv/bin/mythbackend --version
Library API version: 0.20.20070124-1
Source code version: 13056
Options compiled in:
 linux release using_xvmcw using_lmsensors using_v4l using_oss
using_alsa using_arts using_jack using_ivtv using_firewire using_dbox2
using_hdhr using_iptv using_live using_lirc using_joystick_menu
using_dvb using_x11 using_xv using_xrandr using_xvmc using_xvmc_vld
using_frontend using_backend using_bindings_perl
scott at mythtv-64 ~ $

Here is the same output from my backend:

mini-myth ~ # /usr/local/mythtv/bin/mythbackend --version
Library API version: 0.20.20070124-1
Source code version: Unknown
Options compiled in:
 linux release using_xvmcw using_lmsensors using_v4l using_oss
using_alsa using_arts using_jack using_ivtv using_firewire
using_libavc_5_3 using_dbox2 using_hdhr using_iptv using_live
using_lirc using_joystick_menu using_dvb using_x11 using_xv
using_xrandr using_xvmc using_xvmc_vld using_frontend using_backend
using_bindings_perl
mini-myth ~ #

Things i have done:
-deleted the pchdtv 3000 from mythtv-setup
-deleted both tunner cards from mythtv-setup and added just the one tunner card
-tried scheduling a show on the frontend and backend systems with the
same results
-deleted all channels and reloaded the listings and reran mythfilldatabase
-fiddled around with storage groups
-increased the logging of the frontend and backend in hopes of finding
an error that would indicate the source of the problems

Here is the output from mythbackends log at full verbose debug when i
attempt to list the upcoming recordings:

2007-03-17 12:09:22.975 MythSocket(820a208:17): new socket
2007-03-17 12:09:22.975 MythSocket(820a208:17): setSocket: 16
2007-03-17 12:09:22.975 MythSocket(820a208:16): state change Idle -> Connected
2007-03-17 12:09:22.975 MythSocket(820a208:16): UpRef: 1
2007-03-17 12:09:22.975 MythSocket(820a208:16): socket is readable
2007-03-17 12:09:22.975 MythSocket(820a208:16): cb->readyRead()
2007-03-17 12:09:22.975 MythSocket(820a208:16): UpRef: 2
2007-03-17 12:09:22.975 read  <- 16 21      MYTH_PROTO_VERSION 33
2007-03-17 12:09:22.985 write -> 16 13      ACCEPT[]:[]33
2007-03-17 12:09:22.985 MythSocket(820a208:16): socket is readable
2007-03-17 12:09:22.985 MythSocket(820a208:16): cb->readyRead()
2007-03-17 12:09:22.985 MythSocket(820a208:16): UpRef: 2
2007-03-17 12:09:22.985 MythSocket(820a208:16): DownRef: 1
2007-03-17 12:09:22.985 read  <- 16 23      ANN Monitor mythtv-64 0
2007-03-17 12:09:22.985 MainServer::HandleAnnounce Monitor
2007-03-17 12:09:22.985 adding: mythtv-64 as a client (events: 0)
2007-03-17 12:09:22.985 write -> 16 2       OK
2007-03-17 12:09:22.985 MythSocket(820a208:16): DownRef: 1
2007-03-17 12:09:22.995 MythSocket(81fd818:18): new socket
2007-03-17 12:09:22.995 MythSocket(81fd818:18): setSocket: 17
2007-03-17 12:09:22.995 MythSocket(81fd818:17): state change Idle -> Connected
2007-03-17 12:09:22.995 MythSocket(81fd818:17): UpRef: 1
2007-03-17 12:09:22.995 MythSocket(81fd818:17): socket is readable
2007-03-17 12:09:22.995 MythSocket(81fd818:17): cb->readyRead()
2007-03-17 12:09:22.995 MythSocket(81fd818:17): UpRef: 2
2007-03-17 12:09:22.995 read  <- 17 23      ANN Monitor mythtv-64 1
2007-03-17 12:09:22.995 MainServer::HandleAnnounce Monitor
2007-03-17 12:09:22.995 adding: mythtv-64 as a client (events: 1)
2007-03-17 12:09:22.995 write -> 17 2       OK
2007-03-17 12:09:23.005 MythSocket(820a208:16): socket is readable
2007-03-17 12:09:23.005 MythSocket(820a208:16): cb->readyRead()
2007-03-17 12:09:23.005 MythSocket(820a208:16): UpRef: 2
2007-03-17 12:09:23.005 MythSocket(81fd818:17): DownRef: 1
2007-03-17 12:09:23.005 read  <- 16 19      QUERY_GETALLPENDING
2007-03-17 12:09:23.005 write -> 16 7       0[]:[]0
2007-03-17 12:09:23.005 MythSocket(820a208:16): DownRef: 1
2007-03-17 12:09:24.585 MythSocket(81fc9c0:14): socket is readable
2007-03-17 12:09:24.585 MythSocket(81fc9c0:14): cb->readyRead()
2007-03-17 12:09:24.585 MythSocket(81fc9c0:14): UpRef: 2
2007-03-17 12:09:24.585 read  <- 14 35      QUERY_REMOTEENCODER 3[]:[]GET_STATE
2007-03-17 12:09:24.585 write -> 14 1       0
2007-03-17 12:09:24.595 MythSocket(81fc9c0:14): DownRef: 1


If i attempt to schedule a show to record from the program guide here
is what mythbackend does:

2007-03-17 12:10:24.326 MythSocket(820a208:16): socket is readable
2007-03-17 12:10:24.326 MythSocket(820a208:16): cb->readyRead()
2007-03-17 12:10:24.326 MythSocket(820a208:16): UpRef: 2
2007-03-17 12:10:24.326 read  <- 16 19      QUERY_GETALLPENDING
2007-03-17 12:10:24.326 write -> 16 7       0[]:[]0
2007-03-17 12:10:24.326 MythSocket(820a208:16): DownRef: 1
2007-03-17 12:10:46.426 MythSocket(820a208:16): socket is readable
2007-03-17 12:10:46.436 MythSocket(820a208:16): cb->readyRead()
2007-03-17 12:10:46.436 MythSocket(820a208:16): UpRef: 2
2007-03-17 12:10:46.436 read  <- 16 25      RESCHEDULE_RECORDINGS 253
2007-03-17 12:10:46.436 write -> 16 1       0
2007-03-17 12:10:46.436 MythSocket(820a208:16): DownRef: 1
2007-03-17 12:10:46.436 MythSocket(820a208:16): socket is readable
2007-03-17 12:10:46.446 MythSocket(820a208:16): cb->readyRead()
2007-03-17 12:10:46.446 MythSocket(820a208:16): UpRef: 2
2007-03-17 12:10:46.446 read  <- 16 19      QUERY_GETALLPENDING
2007-03-17 12:10:46.456 write -> 16 7       0[]:[]0
2007-03-17 12:10:46.456 MythSocket(820a208:16): DownRef: 1
2007-03-17 12:11:08.687 MythSocket(820a208:16): socket is readable
2007-03-17 12:11:08.687 MythSocket(820a208:16): cb->readyRead()
2007-03-17 12:11:08.687 MythSocket(820a208:16): UpRef: 2
2007-03-17 12:11:08.697 read  <- 16 25      RESCHEDULE_RECORDINGS 254
2007-03-17 12:11:08.697 write -> 16 1       0
2007-03-17 12:11:08.697 MythSocket(820a208:16): socket is readable
2007-03-17 12:11:08.697 MythSocket(820a208:16): cb->readyRead()
2007-03-17 12:11:08.697 MythSocket(820a208:16): UpRef: 2
2007-03-17 12:11:08.697 read  <- 16 19      QUERY_GETALLPENDING
2007-03-17 12:11:08.697 write -> 16 7       0[]:[]0
2007-03-17 12:11:08.697 MythSocket(820a208:16): DownRef: 1
2007-03-17 12:11:08.697 MythSocket(820a208:16): DownRef: 1

-If i go back to the program guide and look at that channel, i can see
its not scheduled to record and i can repeat that process it does the
same thing.
-I have checked all my mysql tables using myismchk and it reports no
fatal errors with any tables
-I have even turned on the mythbackend process on my additional
frontend system in hopes of seeing what that would do to no luck.
-I'm basically out of ideas as to what else i can do or check

One other thing of intrest i can't watch tv on my frontend system when
the pchdtv card is setup, but i can scan for channels and find the 1
working HDTV channel and all the cable channels when i hook up the
cable and put it in ntsc mode.

-Scott


More information about the mythtv-users mailing list