New Hauppauge pre-release drivers

[groover km]

andlju, if you look above in tipstir's PVAS log file you'll see -


Number of audio tracks has changed. Splitting.
Last fileset:
2551303280 total bytes written
Video 1: 106843 frames, 00:59:24.994
Audio 1: 149700 frames, 00:59:52.800

I suspect that you have the same in yours, which is why you get multiple small files. When you use PVAS to repair a file, make sure that "split on audio change' is deselected, see...

hope this helps.

[UncleJohnsBand]

Here is info from a 2 minute clip that I was able to put together for sub to look at. It seems much easier to get an invalid timeline if I am watching something at the same time. This would mean there are 4 flows to the hard drive.....3 from the tunners recording and one from the GBPVR/MVP stream.

Found 1 video stream.
Found 1 MPEG audio stream.

VIDEO #1
Resolution 720 x 480
Aspect ratio is 4:3
Frame rate 29.97 fps
Nominal bitrate 8250000 bps
First PTS: 00:00:00.333

MPEG AUDIO #1
MPEG1, Layer 2
stereo, sampled at 48.0 kHz.
Bitrate 224 kbps
Each frame contains 24.0 ms audio (672 bytes)
First PTS: 00:00:00.333

***
*** PVAStrumento 2.1.0.15
*** running at 02-13-2006 18:34
***
Pre-Scanning input. Takes some time.
Stream info for
L:\FTP\Private\sub\25 AMC_20060212195400.mpg

Found 1 video stream.
Found 1 MPEG audio stream.

VIDEO #1
Resolution 720 x 480
Aspect ratio is 4:3
Frame rate 29.97 fps
Nominal bitrate 8250000 bps
First PTS: 00:00:00.333

MPEG AUDIO #1
MPEG1, Layer 2
stereo, sampled at 48.0 kHz.
Bitrate 224 kbps
Each frame contains 24.0 ms audio (672 bytes)
First PTS: 00:00:00.333


==SCANNING==
Input: L:\FTP\Private\sub\25 AMC_20060212195400.mpg
Closing starting GOP.
Aiming for sync at 00:00:00.333
Streamstart seems to be in (reasonable) sync:
Video 1 starts at 00:00:00.333
Audio 1 starts at 00:00:00.333

ALERT> PTS reset in video. Have to re-sync.
Re-syncing.
Closing starting GOP.
Aiming for sync at 00:01:01.821
Cutting video.
Audio stream 1: PTS DISCONTINUITY
Closing starting GOP.
Aiming for sync at 00:00:00.900
Cutting audio.
Audio stream 1 now starts at 00:00:00.909
Video stream 1 now starts at 00:00:00.900
ALERT> PTS reset in video. Have to re-sync.
Re-syncing.
Closing starting GOP.
Aiming for sync at 00:00:14.445
Cutting video.
Audio stream 1: PTS DISCONTINUITY
Closing starting GOP.
Aiming for sync at 00:00:14.637
Cutting video.
Audio stream 1: PTS DISCONTINUITY
Closing starting GOP.
Aiming for sync at 00:00:00.900
Cutting audio.
Audio stream 1 now starts at 00:00:00.909
Video stream 1 now starts at 00:00:00.900
****FileSpan for PES packet
ALERT> Audio 1: 5 audio frames missing at EOF
Last fileset:
77899504 total bytes written
Video 1: 3251 frames, 00:01:48.475
Audio 1: 4551 frames, 00:01:49.224

Sync estimate at EOF:
MPEG Audio #1 : sync

Video statistics
================
GOP length (min/avg/max):
13 / 14 / 15 [frames]
241914 / 344804 / 441774 [Bytes]
GOP bitrate (min/avg/max):
3866 / 5518 / 7061 [kbps]

[groover km]

This is interesting - it seems that very PVAS log file posted displays similar results regarding dropped audio frames... correlation?

[UncleJohnsBand]

Hit a recording from last night that was off as well:

***
*** PVAStrumento 2.1.0.15
*** running at 02-13-2006 20:55
***
Pre-Scanning input. Takes some time.
Stream info for
E:\Mencoder\Originals\Greys Anatomy_20060212_22012300_original.mpg

Found 1 video stream.
Found 1 MPEG audio stream.

VIDEO #1
Resolution 720 x 480
Aspect ratio is 4:3
Frame rate 29.97 fps
Nominal bitrate 8250000 bps
First PTS: 00:00:00.333

MPEG AUDIO #1
MPEG1, Layer 2
stereo, sampled at 48.0 kHz.
Bitrate 224 kbps
Each frame contains 24.0 ms audio (672 bytes)
First PTS: 00:00:00.333


==SCANNING==
Input: E:\Mencoder\Originals\Greys Anatomy_20060212_22012300_original.mpg
Closing starting GOP.
Aiming for sync at 00:00:00.333
Streamstart seems to be in (reasonable) sync:
Video 1 starts at 00:00:00.333
Audio 1 starts at 00:00:00.333

ALERT> PTS reset in video. Have to re-sync.
Re-syncing.
Closing starting GOP.
Aiming for sync at 00:22:25.917
Cutting video.
Audio stream 1: PTS DISCONTINUITY
Closing starting GOP.
Aiming for sync at 00:00:00.900
Cutting audio.
Audio stream 1 now starts at 00:00:00.909
Video stream 1 now starts at 00:00:00.900
****FileSpan for PES packet
ALERT> Audio 1: 14 audio frames missing at EOF
Last fileset:
2518240636 total bytes written
Video 1: 105433 frames, 00:58:37.947
Audio 1: 147210 frames, 00:58:53.040

Sync estimate at EOF:
MPEG Audio #1 : sync

Video statistics
================
GOP length (min/avg/max):
13 / 14 / 15 [frames]
113510 / 344104 / 633534 [Bytes]
GOP bitrate (min/avg/max):
1814 / 5500 / 10126 [kbps]

[andlju]

I suspect that you have the same in yours, which is why you get multiple small files. When you use PVAS to repair a file, make sure that "split on audio change' is deselected, see...

Ahh, I see.. I basically didn't have the energy to try anything else than just running it with the default settings. Getting hold of the latest Desperate Housewives episode via "unofficial channels" was far easier than trying to fix my faulty file..

Thank's for the tip though, I'll try that if I run into the same problem again..!

[UncleJohnsBand]

This is interesting - it seems that very PVAS log file posted displays similar results regarding dropped audio frames... correlation?

Interesting that people that were having Audio issues over the last year revert back to the 2035 drivers to correct their sound problem and a few people here have reported that their timeline issue goes away with these same drivers. Unfortunately, it does not go away for all of us.

[User]

It's not that the driver fixes the sound problem, actually the distortion is still there when it's installed. The key is that the tweaker tool that allows you to adjust the audio, (and video) works with this driver, so you can clean it up. I have had zero timeline issues with this driver, which is also a must have.

[tieke]

Just thought I would mention that I too have been having the timeline issues, and I am on PAL. Basically will be watching a recording and will either freeze or will suddenly "fast-forward". If you skip back to just before the problem then short-skip over the affected patch you can get over it.
Have a PVR-150 and a Twinhan DVB-S card, athlon 2800, 1G of RAM.

(Nightly defragging, changing comskip to post-processing rather than concurrent, increasing the gb-pvr priority and disabling the Twinhan don't appear to fix it, so am trying the earlier drivers - was running 074).

cheers,

tieke
(if it happens again I could probably provide sub with a DVD of the dodgy file if that helps)

[wtg]

Just thought I would mention that I too have been having the timeline issues, and I am on PAL. Basically will be watching a recording and will either freeze or will suddenly "fast-forward". If you skip back to just before the problem then short-skip over the affected patch you can get over it.
Have a PVR-150 and a Twinhan DVB-S card, athlon 2800, 1G of RAM.

Was the timeline off on the video though? Did it show the correct duration?

I ask only because you mention skipping over the problem. This is never possible with the files I've encountered. If the timeline shows a 2 hour video is 15 minutes long, you may be able to skip forward up to 15 minutes, but after you've went past the reported duration, skipping in any direction is impossible. It skips, but never any predictable amount of time and it's virtually impossible to position yourself within the video, or resume playback of one that you've stopped and are resuming.

Maybe they are the same problem, but your symptoms don't sound like what I've experienced.

[Lucas_24]

tipster, I'm anxious to hear your results. I've been running 2.24.???? since I installed my PVR500 card. I've issues with sound dropping out repeatedly since I installed the card. Just trying to find down time on the PVR to mess with drivers. As well I have no idea which drivers to try. I don't have the patience required right now to test multiple driver versions to find the least harmful.