View unanswered posts    View active topics

All times are UTC - 6 hours





Post new topic Reply to topic  [ 143 posts ] 
Go to page Previous  1, 2, 3, 4, 5, 6, 7 ... 10  Next

Print view Previous topic   Next topic  
Author Message
Search for:
 Post subject:
PostPosted: Tue Apr 03, 2007 3:39 pm 
Offline
Joined: Wed Aug 24, 2005 3:44 am
Posts: 210
spalVl wrote:
Anyone try upgrading to latest SVN?

I was having the same problem on QAM channels using my HDhomerun tuner when I 1st got it and that was the fix. The HDhomerun wasn't around before MythtTV .20 so I never seen on previous versions. I don't recall if the SVN fix was specific to the HDhomerun or all QAM tuners.

Some other things, try looking at the "bad recordings" with another media player over the network such as VLC and see if they are playable?


Presumably building the latest SVN may involve building from source?
Will this not have ripple effects/dependencies with other parts of KnoppMyth

Not sure what you mean "bad recordings" - the issue seems to be one of a race condition (the frontend appears to attempt to open a recording before its created) rather than any "bad recordings" - unless of course im mis-understanding you


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 03, 2007 6:32 pm 
Offline
Joined: Mon Aug 29, 2005 4:04 pm
Posts: 729
Location: Philadelphia, PA US
Quote:
Presumably building the latest SVN may involve building from source?
Will this not have ripple effects/dependencies with other parts of KnoppMyth


Yes running SVN means building latest prerelease version of MythTV from source, but it really isn't as bad as it seems. This guide makes it pretty easy.

http://www.knoppmythwiki.org/index.php? ... hTVFromSVN

I didn't have any dependencies issues compiling with R5E50. I could run into some issues when I upgrade to the next version of Knoppmyth that comes bundled with .21 when both are released, but that is a risk I took to get my tuners working.

It seems to me if you guys are taking the time to try MythTV on top of other distros and at this point seems like may be something in MythTV not that hard to upgrade to SVN and rule out a MythTV bug in .20fixes.

Quote:
Not sure what you mean "bad recordings"


I didn't read the thread well enough. My bad. What I was seeing, LiveTV is just a recording stored in /myth/tv/. Even with the "Error Was encountered while displaying video" if I stayed on the error screen and browsed over the network to the LiveTV recording in /myth/tv I could see the recording growing in size and the file was not playable is some Media players and playable in others. Problems sound diffrent when I read the thread more.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Apr 05, 2007 1:26 am 
Offline
Joined: Wed Aug 24, 2005 3:44 am
Posts: 210
I *might* have found something that makes a difference..... not 100% sure yet Im still testing it.

I posted my problems to mythtv bug tracking #2335 and someone has suggested to me that this problem can be overcome my tuning the mysql db.

The theory is based around the performance of mysql. The race condition at the new file creation could be due to sluggish mysql performance.

Ive tried a tuned set of parameters in /etc/mysql/my.cnf and have been testing this for approx 12 hours so far without the error.

If anyone wants me to post the changed file here just shout - but I'm reluctant to post yet it in case its a wild goose chase at this stage.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Apr 05, 2007 6:59 am 
Offline
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 997
Location: Lexington, Ky
declanh,

I was starting to think the problem might be database related as well. I was thinking of restoring an old copy of mine but your approach seems like a better idea.

Please post your changes, I'd like to give them a try.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Apr 05, 2007 10:33 am 
Offline
Joined: Wed Aug 24, 2005 3:44 am
Posts: 210
Quote:
I was starting to think the problem might be database related as well. I was thinking of restoring an old copy of mine but your approach seems like a better idea.

Please post your changes, I'd like to give them a try.


Ok, testing ran for 18 hours or there abouts and then threw the same error
"Error Was encountered while displaying video"

So I does not seem to be a cure, but in this one test run it went thru a lot of boundaries without issue so i dont know if it helps or not


IF you wish to try here is my tweaked my.cnf

Code:
#
# The MySQL database server configuration file.
#
# You can copy this to one of:
# - "/etc/mysql/my.cnf" to set global options,
# - "~/.my.cnf" to set user-specific options.
#
# One can use all long options that the program supports.
# Run program with --help to get a list of available options and with
# --print-defaults to see which it would actually understand and use.
#
# For explanations see
# http://dev.mysql.com/doc/mysql/en/server-system-variables.html

# This will be passed to all mysql clients
# It has been reported that passwords should be enclosed with ticks/quotes
# escpecially if they contain "#" chars...
# Remember to edit /etc/mysql/debian.cnf when changing the socket location.
[client]
port            = 3306
socket          = /var/run/mysqld/mysqld.sock

# Here is entries for some specific programs
# The following values assume you have at least 32M ram

# This was formally known as [safe_mysqld]. Both versions are currently parsed.
[mysqld_safe]
socket          = /var/run/mysqld/mysqld.sock
nice            = 0

[mysqld]
old_passwords = 1 #changed by declan false # inserted by debconf
# Activate the above for connections from hosts running Debian Woody/Sarge!
#
# Prior to MySQL 5.0, user passwords were stored in a rather weak way. This
# has been improved with the drawback that client programs shipped with
# Debian Woody/Sarge (technically: linked against libmysqlclient.so.12 or
# earlier) cannot connect any more if either their account has either been
# created or their password has been modified using MySQL 5.0.
# See http://dev.mysql.com/doc/refman/5.0/en/old-client.html
#
# * Basic Settings
#
user            = mysql
pid-file        = /var/run/mysqld/mysqld.pid
socket          = /var/run/mysqld/mysqld.sock
port            = 3306
basedir         = /usr
datadir         = /var/lib/mysql
tmpdir          = /tmp
language        = /usr/share/mysql/english
skip-external-locking
#
# Instead of skip-networking the default is now to listen only on
# localhost which is more compatible and is not less secure.
bind-address            = 127.0.0.1
#
# * Fine Tuning
#
key_buffer              = 32M # changed by declan 16M
max_allowed_packet      = 16M
thread_stack            = 128K
thread_cache_size       = 200 # changed by declan from 8
table_cache             = 1000 # added by declan (not there before)
sort_buffer_size        = 16M # added by declan (not there before)
net_buffer_length       = 16M # added by declan

#
# * Query Cache Configuration
#
query_cache_limit       = 1048576
query_cache_size        = 25165824 # changed by declan from 16777216
query_cache_type        = 1
#
# * Logging and Replication
#
# Both location gets rotated by the cronjob.
# Be aware that this log type is a performance killer.
#log            = /var/log/mysql/mysql.log
#
# Error logging goes to syslog. This is a Debian improvement :)
#
# Here you can see queries with especially long duration
#log_slow_queries       = /var/log/mysql/mysql-slow.log
#
# The following can be used as easy to replay backup logs or for replication.
#server-id              = 1
log_bin                 = /var/log/mysql/mysql-bin.log
# WARNING: Using expire_logs_days without bin_log crashes the server! See README.Debian!
expire_logs_days        = 10
max_binlog_size         = 100M
#binlog_do_db           = include_database_name
#binlog_ignore_db       = include_database_name
#
# * BerkeleyDB
#
# According to an MySQL employee the use of BerkeleyDB is now discouraged
# and support for it will probably cease in the next versions.
skip-bdb
#
# * InnoDB
#
# InnoDB is enabled by default with a 10MB datafile in /var/lib/mysql/.
# Read the manual for more InnoDB related options. There are many!
# You might want to disable InnoDB to shrink the mysqld process by circa 100MB.
#skip-innodb
#
# * Security Features
#
# Read the manual, too, if you want chroot!
# chroot = /var/lib/mysql/
#
# For generating SSL certificates I recommend the OpenSSL GUI "tinyca".
#
# ssl-ca=/etc/mysql/cacert.pem
# ssl-cert=/etc/mysql/server-cert.pem
# ssl-key=/etc/mysql/server-key.pem



[mysqldump]
quick
quote-names
max_allowed_packet      = 16M

[mysql]
#no-auto-rehash # faster start of mysql but no tab completition

[isamchk]
key_buffer              = 16M

#
# * NDB Cluster
#
# See /usr/share/doc/mysql-server-*/README.Debian for more information.
#
# The following configuration is read by the ndbd storage daemons,
# not from the ndb_mgmd management daemon.
#
# [MYSQL_CLUSTER]
# ndb-connectstring=127.0.0.1


let me know if it helps you

(changed bits should be commented above)


Top
 Profile  
 
 Post subject:
PostPosted: Thu Apr 05, 2007 11:45 am 
Offline
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 997
Location: Lexington, Ky
declanh,

Thanks for posting your file. I just copied the changes:
Code:
# * Fine Tuning
#
key_buffer              = 32M # changed by declan 16M
max_allowed_packet      = 16M
thread_stack            = 128K
thread_cache_size       = 200 # changed by declan from 8
table_cache             = 1000 # added by declan (not there before)
sort_buffer_size        = 16M # added by declan (not there before)
net_buffer_length       = 16M # added by declan

#
# * Query Cache Configuration
#
query_cache_limit       = 1048576
query_cache_size        = 25165824 # changed by declan from 16777216
query_cache_type        = 1
#


Into my.cnf

I usually get an error on every program change boundary. So I should know if it helped later tonight. I will post my results.


Top
 Profile  
 
 Post subject:
PostPosted: Thu Apr 05, 2007 1:58 pm 
Offline
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 997
Location: Lexington, Ky
Well looks like it helped a little, but I still got a failure after 4 program boundary's.
Better than one every one!


Top
 Profile  
 
 Post subject:
PostPosted: Thu Apr 05, 2007 6:46 pm 
Offline
Joined: Tue Aug 22, 2006 9:11 am
Posts: 127
Location: Perth
Will give it a shot, wasn't happening as frequently for me, but generally at the end of the particular show I was watching at night, after having the tv on from the time I get home from work. (round 6'ish and the nearing the end of the shows I watch at night around 9.30ish)

_________________
DRM 'manages access' in the same way that jail 'manages freedom.'
_________________
Intel P4 2.6
Intel Desktop Board
2GB DDR400
nVidia 6600GT
Dvico HDTV+
Dvico Dual 4
200GB WD for Swap /boot & /
2x 500GB WD with LVM & XFS for /myth/tv


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 06, 2007 1:49 am 
Offline
Joined: Wed Aug 24, 2005 3:44 am
Posts: 210
Second test run completed - it took 9 hours (14 show boundaries) before the error appeared again.

At this level of occurence i could nearly live with it.. but i wonder if it occurs more frequently if channel surfing as opposed to my test where i left the box running untouched.

D


Top
 Profile  
 
 Post subject:
PostPosted: Fri Apr 06, 2007 3:07 pm 
Offline
Joined: Tue Aug 08, 2006 7:08 pm
Posts: 561
Location: UK
Not followed in detail this thread, but I also ran into this problem today.

Bruce S.

_________________
Updated 2019/10/26: AthlonII X2 265 Gigabyte GA-970A-DS3P
16Gb PC 1866 DDR3, 500GB+2TB+4TB SATA HDD,
SATA DVD-RW Asus DRW-24D5MT , NVIDIA GeForce GT1080
Hauppauage Nova-T 500, Nova-T LinHes R8.6.1


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 10, 2007 10:41 pm 
Offline
Joined: Fri Dec 22, 2006 3:00 pm
Posts: 158
Has anyone heard if a possible fix is likely to be available soon?

It is an absolute show stopper for me at the moment. It occurs too frequently, often within 30 minutes to an hour and makes my R5E50 box pretty much unusable for watching the clear-QAM channels.

I have a combined front-end/back-end.
Single IDE hard drive
Airstar HD5000-PCI
PVR-500

I also have scoured the internet on this problem; it seems there are great number of people affected by this,

thanks,

Kevin


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 10, 2007 10:55 pm 
Offline
Joined: Tue Aug 22, 2006 9:11 am
Posts: 127
Location: Perth
I wouldn't say I have thoroughly tested this yet, but the problem seems less apparent.

I will do further testing over the next week and post my results.

_________________
DRM 'manages access' in the same way that jail 'manages freedom.'
_________________
Intel P4 2.6
Intel Desktop Board
2GB DDR400
nVidia 6600GT
Dvico HDTV+
Dvico Dual 4
200GB WD for Swap /boot & /
2x 500GB WD with LVM & XFS for /myth/tv


Top
 Profile  
 
 Post subject:
PostPosted: Tue Apr 10, 2007 11:03 pm 
Offline
Joined: Fri Dec 22, 2006 3:00 pm
Posts: 158
thanks techman83,

good luck, I have my fingers crossed.

Having scoured the internet I can't believe how many users are affected by this yet a solution seems so elusive. I guess that it is really difficult to force a scenario which would trigger the error, so I can appreciate that it is very hard to debug,

Kevin


Top
 Profile  
 
 Post subject:
PostPosted: Wed Apr 11, 2007 3:52 am 
Offline
Joined: Wed Aug 24, 2005 3:44 am
Posts: 210
Well, where I'm at with this is ...

I have tested the mysql db config changes over a number of days. It seems to have made the problem a bit better but its still there and I'm still reluctant to move (yet) from r5a16 which seems very stable for me until I can get r5e50 running at a similar stability.

Ive also noticed that fast forward and rewind/skip seem very poor (v v sluggish) on r5e50 compared to r5a16, as yet I've not worried too much about this till i get a solution to the "Error Was encountered while displaying video" problem.

What I would love to understand is why some people do not expereince this problem AT all and others get it alot and there are some who get it occasionally.

Do those who dont see it at all have super high power hardware ?

D


Top
 Profile  
 
 Post subject:
PostPosted: Wed Apr 11, 2007 8:06 am 
Offline
Joined: Mon Apr 10, 2006 3:48 pm
Posts: 997
Location: Lexington, Ky
I've concluded that the mysql tweaks have not really helped. :-(
I'm still getting the problem quite regularly.
I did try upgrading to the latest fixes branch but still have the problem there as well.


Top
 Profile  
 

Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 143 posts ] 
Go to page Previous  1, 2, 3, 4, 5, 6, 7 ... 10  Next



All times are UTC - 6 hours




Who is online

Users browsing this forum: Bing [Bot] and 19 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