View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 3 posts ] 
Print view Previous topic   Next topic  
Author Message
Search for:
PostPosted: Sat Oct 22, 2005 12:06 am 
Offline
Joined: Fri Jun 17, 2005 10:58 am
Posts: 8
I think I'm getting closer to making this work but running into a problem right now.

I'm using HD-3000 with R5A22 and I get only one HD OTA channel with decent reception...which makes sense because I'm building the machine in my basement.

However, when I did the channel scan during the setup, Myth found 5-7 channels with "decent" signals. Hence, when I try to switch from the good channel to one that is weak, my screen goes blank and after about 6 minutes, it retuns a message "Error was encountered while displaying video". When it's blank, I can't switch the channel or anything. The only way I know to get the screen back is to enter a term screen, kill the frontend and restart myth. This seems very tedious.

Is there anything I can configure so that when Myth encounters a weak signal it does not freeze my screen?


Top
 Profile  
 
PostPosted: Sat Oct 22, 2005 7:36 pm 
Offline
Joined: Thu Sep 30, 2004 11:29 am
Posts: 2419
Location: Mechanicsburg, PA
provato wrote:
Hence, when I try to switch from the good channel to one that is weak, my screen goes blank and after about 6 minutes, it retuns a message "Error was encountered while displaying video".


This seems to be a driver issue. We'll need to wait on a fix from the folks who maintain DVB.

_________________
KnoppMyth R5.5
MythiC Dragon v2.0
Join the KnoppMyth Frappr!


Top
 Profile  
 
 Post subject:
PostPosted: Mon Oct 24, 2005 3:25 pm 
Offline
Joined: Fri Jun 17, 2005 10:58 am
Posts: 8
I read somewhere that the freezing can be caused by a corrupt mpeg file when a channel has a bad reception. The proposed solution was to kill the frontend and re-start.

My guess is that bad reception can be a common problem and others have the same issues. It's hard for me to grasp that everyone will go through the pain of manually handling the problem when it occurs.

Did anyone try the new driver and noticed that the problem went away? (If so, can you share the steps)

Are there any other options to handle this problem?


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 3 posts ] 


All times are UTC - 6 hours




Who is online

Users browsing this forum: Bing [Bot] and 23 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Jump to:  
Powered by phpBB® Forum Software © phpBB Group

Theme Created By ceyhansuyu