I'm having a strange problem with my system, with the newest knoppmyth. Some recorded shows, when I play them back, are showing the wrong length.. a half hour show for instance shows as being 1.5 hours long. When I jump ahead, it actualy ends up jumping backwards some ten minutes and I have to then keep jumping to get back to where I was and then to skip ahead..

Its the weirdest thing.

I dont even know where to begin to look for a solution...

I'm not sure if this is the same problem, but if I start watching a program while it is recording, say an hour long program, the time it shows on the OSD when I pause is always way too high (like 2:09:12). When the recroding ends, I can just exit out of playback (bookmarking my place) then start the program again, and the time is now correct.

I don't think I've seen it jump backwards any more than 5 seconds at a time though.

_________________
FRONTEND 1 - R5A16, Athlon 3000+, NVidia Motherboard, SB live, GeForce 5200, AA 9A60
FRONTEND 2 - R5A16, Athlon 2500+, Nvidia Motherboard, SB Live, GeForce 440MX, TV-OUT
BACKEND - R5A16, Althon 1700+, Nvidia MB, 2- HD3000's, 450GB LVM partition

How did you keep these old recordings (presumably from an earlier version of knoppmyth)? Did you backup and then auto-upgrade or did you use the database rebuild script? There are known issues with using the rebuild script for mpeg2 recordings (as opposed to mpeg4 or rtjpeg which should work).

this is a fresh install, and new recordings. I am watching them well after they are done recording, not during.

Its quite anoying!

Fortunately everything else seems to work better with the newest knoppmyth. I havent gotten any freezups or backend crashes like I did before. This is so far the only problem I'm having...

OK I started noticing another time problem confined only to Fox. I recently watched Scream, and Once Apon a Crime, and when I paused them they showed 1 hour 33 minutes. They guide infor clearly showed that both they were two hours long (something like 7:00-9:00). I'm not sure this is related to you original problem. Fast forwarding and rewinding seemed to be right, if I hit forward at the start of one commercial, I got the start of another commercial. The displayed playback time seemed to run a little slow, which it necessarily would in order for 1 hour 33 minutes to last 2 hours

The fact that it's only on Fox seems wierd, I also noticed that any motion in both movies was kind of jerky. I don't have this problem with 1080i why should I have it with 480p programs. Either they are broadscasting stuff with 1/4 of the frames missing, or myth is misinterpreting something about the stream.

Maybe these problems have something to do with how myth calculates how long a show is. like taking the number of frames and dividing by 30 or 60, rather than looking at the timebaseof the start and end frames or some other method.

_________________
FRONTEND 1 - R5A16, Athlon 3000+, NVidia Motherboard, SB live, GeForce 5200, AA 9A60
FRONTEND 2 - R5A16, Athlon 2500+, Nvidia Motherboard, SB Live, GeForce 440MX, TV-OUT
BACKEND - R5A16, Althon 1700+, Nvidia MB, 2- HD3000's, 450GB LVM partition

I'd suggest checking the db for errors.

_________________
cesman

When the source is open, the possibilities are endless!

I found out what was causing my weird time problems, but I dont know why exactly: I had found on the knoppmythwiki site a page about recording profiles so I though I would try setting those up. Not only were they unusable (well, the low quality one was worse than the worst old chewed up vhs tape I've ever seen) but that's when my time problems started.

When I reset them back to the defaults, everything worked fine again.

I now have, finaly, a very stable mythtv box.

Unfortunately now my wife has gotten to like the thing and I can't get her off of it. Now I need to add more tv cards so I can actualy record *my* shows...

I've read that with the hardware encoding cards, you have to be cautious about setting up the recording profiles to match the incoming data rate from the card.

I haven't investigated, but here's my wild-assed guess:

1. With frame-grabbers (cards that do not encode/compress on their own), the vast majority of cards sold before the current generation of hauppauge hardware encoding cards and the like, mythtv has to perform the compression for you, on the fly, as TV signal is coming in.

2. The recording profiles were engineered with this task in mind.

3. THEREFORE, setting them up for the newer *hardware* encoding cards involves matching them against the default frame size/data rate for the driver or whatever you, say, used ivtvctl to set it to.

---

What I don't know is this: if you set the profile to something radically different that what the hardware encoder puts out, is it supposed to a) ignore it, b) trascode it (requiring both decompression and compression on the fly, which is probably sucky) or c) store incorrect data about the stream in the databases? Heh.

-brendan

One of the differences between the PVR-250 and the PVR-150 is that the 150 doesn't support all the same resolutions. The point is that both only support a certain limited set of resolutions, and who knows what happens when you try to go "off the reservation"...

For the PVR-150 these are:

For the PVR-250 Hauppage says:
And I know that it does VCD 480x480 and possibly others as well as the formats listed for the 150... I've actually seen more detailed specs somewhere but can't seem to find them just now...

AHA! http://www.hauppauge.com/pages/faq/support_faq_pvr250-350.html#26