Roger Heflin wrote:
> stuart wrote:
>> Hi...
>>
>> Was just poking around my MythTV back-end-live-TV stuff and noticed that 
>> MVPMC listed both the normal and high definition channels together.  I 
>> would expect MVPMC to crash on the high definition channels (right now 
>> it's crashing on everything).  But what I wanted to ask here: "Why does 
>> MVPMC list all the stations when my myth front-end will only list the 
>> normal or high definition stations, but not both at the same time (i.e. 
>> you have to hit the "Y" key to change tuners)?".  Hum, I wonder if 
>> that's why it's crashing on everything.
>>
>>     ...thanks
>>
>>   
> 
> MVPMC does not crash on the high-defs for me, it just won't display 
> anything,
> I can see the high bit rate (15-18Mbps).    I kind of though that the 
> live TV
> stuff might be accessing things through NFS and when I have been accessing
> MYTHTV things through NFS and the file is not there, MVPMC does crash
> very very nicely, maybe some error checking for file not found should be
> put in.   Though I am not sure since my live TV works and alot of my NFS
> stuff relies on a symbolic link being put into the main directory (3 
> separate
> recording directories), and the job putting the link in only goes every
> 3 minutes, this will cause a crash if I try to start watching a show that is
> using one of the other 2 directories before the link is created.
> 
> I believe MVPMC sees everything from both tuners.   And MVPMC will
> display the 480p stuff but with no sound.
> 
>                                                 Roger

Hi Roger....

Thanks for the replay.  Actually the MythTV feature of MVPMC behavior I 
see is more complicated than that.  If I use the normal Live TV option 
the MVPMC box sees 2 tuners (good) and list both the normal and high 
definition tuners.  But when I try to tune in what appears to be a 
standard definition station, the MPVMC box resets.  However, if I try 
the New Live TV, it goes directly to a standard definition station and 
plays great.  Except when the tuner is in use.  It doesn't look like New 
Live TV handles this well.  Maybe we need to check and print out a 
message if the tuner is busy.

Viewing lists of recorded shows gets a bit tricky. I usually get the 
"MythTV connection lost!". I immediately tested the back end by running 
the front end and playing several of the pre-recorded shows. It worked 
fine.

In general, the current state of the MVPMC / MythTV  feature appears 
delicate to me.  As more thing worked before I reconfigured my Mythtv 
box to have 2 tuners, I believe it's more to do with unexpected modes of 
a 2 tuner back end than MVPMC.  I recall both the older Live TV and the 
Watch Recordings working before.  However, as I resynchronize with GIT 
often it's hard to narrow down when they stopped working to any one event.

It might be important to note that the duel tuners used above proved 
difficult to integrate into one MythTV box as one is normal and the 
other is high definition. I had to use two different zap2it lineups as I 
did not intend them to receive any common stations. A normal front end 
makes you choose which tuner is to be used for live TV watching. Perhaps 
this might be a reason the older Live TV / MVPMC feature resets (I am 
guessing the older Live TV feature assumes two identical tuners with the 
same lineup).

I recorded the output of the MVPMC box and of the back end when trying 
to list the recorded shows ("Watch Recordings").  First the MVPMC box 
then the MythTV backend:
----------
show busy widget
get recorded failed
mythtv_shutdown(): closing mythtv connection
Event socket closed, shutting down myth
mythtv_shutdown(): closing mythtv connection
MythTV connection lost!
MythTV connection lost!
hide busy widget
-------------
2006-12-16 22:56:21.266 MainServer::HandleVersion - Client speaks 
protocol version 8 but we speak 31!
2006-12-16 22:56:21.271 MainServer::HandleAnnounce Playback
2006-12-16 22:56:21.272 adding: 192.168.0.108 as a client (events: 0)
2006-12-16 22:56:21.274 MainServer::HandleVersion - Client speaks 
protocol version 8 but we speak 31!
2006-12-16 22:56:21.319 MainServer::HandleAnnounce Playback
2006-12-16 22:56:21.320 adding: 192.168.0.108 as a client (events: 1)
-------------

Let me know if there or other outputs and / or events which you might 
want to see.

    ...thanks





-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Mvpmc-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mvpmc-users
mvpmc wiki: http://mvpmc.wikispaces.com/

Reply via email to