Re: [mythtv-users] Problem with ffwd/rwd in 0.17 recordings

2005-04-14 Thread Martijn Coenen
Strange I am having similar problems (the endtime is incorrect and
fluctuates when ffwd/rewinding). Altough my database was marked as
corrupt, repairing it does not solve the problem. Has anyone gained any
new insights on this issue?
On 2/28/05, Nicholas McCoy [EMAIL PROTECTED] wrote:
I was having very similiar problems.Jumping around would sometimesbehave almost randomly.I fixed it by repairing the database tablesas described in the following link:
http://www.mysettopbox.tv/phpBB2/viewtopic.php?t=1043This solved the problme for NEW recordings only.The old ones werestill corrupted and exhibited the bad behavior.I have had to rerunthe commands a few times.I think the old recordings had a habbit of
re-breaking everything.It seems to be all smoothed out now.I hope this helps.On Fri, 25 Feb 2005 11:41:02 +1100, Daniel Sheppard[EMAIL PROTECTED]
 wrote: Since installing Myth 0.17, I've had severe problems with navigating recordings. When hitting enter, it displays the length of the recording incorrectly (sometimes 30 seconds, sometimes 10 minutes, sometimes 20
 minutes, but always well short of the actual recording length). Attempting to jump forward into the recording, it will usually hang for a few seconds and then drop back to the listing as if it has reached the
 end of the recording. If the reported length of the recording is long enough, it will sometimes just forward 20 minutes or so into the recording instead. Any attempt to jump backward in the recording will
 then only jump back as far as the point that was jumped forward to. If I just sit and watch the recording, it runs all the way through without hassle, and I can use the time-stretch feature to get past the
 bits I want to skip. I'm getting some of the following messages in my dmesg output, but I'm not sure where they match up timewise (in playback, transcoding or recording).
 bttv0: OCERR @ 1ec29000,bits: HSYNC OFLOW OCERR* bttv0: OCERR @ 1ec29000,bits: HSYNC OFLOW OCERR* bttv0: OCERR @ 1ec29014,bits: HSYNC OFLOW OCERR* bttv0: OCERR @ 1ec29000,bits: HSYNC OFLOW OCERR*
 bttv0: OCERR @ 1ec29000,bits: HSYNC OFLOW OCERR* bttv0: OCERR @ 1ec29000,bits: HSYNC OFLOW OCERR* bttv0: OCERR @ 1ec29000,bits: HSYNC OFLOW OCERR* I'm using a single bt878 capture card in an athlon 1700 with 512MB. I'm
 running a 2.6.10 kernel with gentoo patches (linux-2.6.10-gentoo-r6) I'm running Gentoo, and have run an emerge -e mythtv to make sure that all packages on which myth runs are built properly and nothing is linked
 to the wrong code. My relevant make.conf settings are: USE=x86 mmx 3dnow sse -alsa oss avi crypt cscope dvd flac gif imlib jpeg lirc mad mpeg mysql oggvorbis opengl png quicktime sdl tiff
 truetype X xmms xv zlib nvidia -arts transcode xinerama -nls net joystick matroska -ldap apache2 xvid v3l2 theora ithreads mjpeg xvid CFLAGS=-O2 -march=athlon -fomit-frame-pointer
 CHOST=i686-pc-linux-gnu MAKEOPTS=-j2 I can't remember the reasons why half those USE-flags, so I'm guessing some of those could be breaking things. I'd appreciate a known working
 set of USE/CFLAGSsettings from a fellow gentoo-ist (A list of installed package versions would be great too) with a fully functioning bt878 based 0.17 install so that I can eliminate bad packages as the
 cause. (This message has been crossposted to http://forums.gentoo.org/viewtopic-t-300215-start-0.html) Daniel Sheppard
 http://jroller.net/page/soxbox # This email has been scanned by MailMarshal, an email content filter.
 # ___ mythtv-users mailing list 
mythtv-users@mythtv.org http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users--Nicholas McCoy2008 Pauline Blvd. Apt. TA
Ann Arbor, MI 48103(734) 476-1346___mythtv-users mailing listmythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users___
mythtv-users mailing list
mythtv-users@mythtv.org
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


Re: [mythtv-users] Re: New MythTV Hardware Review

2004-12-10 Thread Martijn Coenen
On Thu, 9 Dec 2004 22:38:37 -0800, nate s [EMAIL PROTECTED] wrote:
 Nah, here in the US we are far too arrogant to adopt other countries
 standards :)

Arrogant or not, the fact that your government pushes HDTV does mean
that you will be able to enjoy it by next year. Here in Europe there
is no such effort and it seems we will have to wait a few more years
(2007/2008 is mentioned...). Of course this gives us the benefit of
open recorders like MythTV. I wonder what I would prefer, SD MythTV or
closed HDTV :)
 
Martijn

 I thought that QAM was only good over cable.  I didn't know it could
 work OTA as well.
 
 -Nate
 
 
 
 
 On Fri, 10 Dec 2004 00:08:58 +1100, Hamish Moffatt [EMAIL PROTECTED] wrote:
  On Sun, Dec 05, 2004 at 11:54:42PM -0800, Brad Templeton wrote:
   ATSC is in fact the only reason people are putting up new antennas.  If
   you get satellite, you must use an antenna to get your local stations.
   The satellite companies don't have the bandwidth to feed all the locals
   in HD, not yet.   For your HD-cable, you can get it without an antenna.
  
   The protocol for that is called QAM, it is different from ATSC and DVB.
   Whether they would let you put a cablecard into a PC and an open
   source PVR is an interesting question.
 
  FWIW, DVB-T uses QAM (16, 32, 64, 128).
 
   Anyway, the pcHDTV card we are all talking about is rumoured to have
   QAM support in development, so it could tune your cable and you
   would not need an antenna.  As to when, who knows?
  
   The QAM signal for your local stations should be unencrypted.  The
 
  This is a bit confusing; the encryption would be at the MPEG level,
  with QAM just being the analog modulation used to carry the MPEG
  data stream.
 
  Any chance the USA would like to adopt DVB-T? :-)
  I hear that QAM is better than 8VSB also (your OTA modulation).
 
  Hamish
  --
  Hamish Moffatt VK3SB [EMAIL PROTECTED] [EMAIL PROTECTED]
 
 
  ___
  mythtv-users mailing list
  [EMAIL PROTECTED]
  http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
 
 
 
 
 
 ___
 mythtv-users mailing list
 [EMAIL PROTECTED]
 http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
 
 

___
mythtv-users mailing list
[EMAIL PROTECTED]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users


[mythtv-users] Bandwidth requirements MPEG2

2004-12-03 Thread Martijn Coenen
Hello all,

I would like to run a mythtv frontend on my xbox. For some very
strange reason my Xbox nic will only work on 10 mbit hubs, for all 100
mbit hubs/switches I tried it fails autonegotation. I've tried
everything, but something must be wrong with the NIC.

Anyway, I read many topics about wireless connections to the
front-end, people complain that 802.11b ain't enough for frontend
(802.11b will boil down to 500/600 KB/s). However I cannot find the
actual bandwith requirements anywhere. I will be able to provide a
sustained 10 mbit feed (around 900 KB/s) to the frontend, do you guys
think it will suffice for average mpeg2 (4000 kbit)?  I know the
numbers say it should suffice, but practice is too often different
from reality.

Thanks,

Martijn Coenen
___
mythtv-users mailing list
[EMAIL PROTECTED]
http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users