Mpeg stream error

[Spectre]

I am trying to edit out commercials from an MPEG2 file I have captured off Live TV.

This programs seems to be just what I am looking for I can load the file into the program, and make my cuts. when I try to use the joiner I get the following error Mpeg stream error Audio Ring Buffer overflow

This is my Setup..

AMD XP 2500+
ASUS A7N8X-X
896MB PC2100
Hauppauge WINTV 16MB capture card
NVIDIA Geforce 4 Ti4200
NVIDIA NForce Audio
My.TV USB IR Blater


I am Using Snapstream Beyond TV3 for the online program guide and recording settings. I capture in MPEG2 at 640x480 resolution.


I used the AVICODEC tool and got this info about the MPEG2 file:


File : 1782 Mb (0 Mb), duration 0:00:00, type MPG, 1 audio stream(s), quality 98 %
Video : 0 Mb, 7000 Kbps, 29.970 fps, res. 640*480 (16:9), MPG2 = MPEG 2 (SVCD/DVD), supported
Audio : 0 Mb, 224 Kbps, 48000 Hz, 2 chan., 0x51 = Mpeg-1 audio Layer 2 [0xc0], supported


Can anyone help with this issue?

Thanks

[DanR]

You mentioned you got the error in the joiner. Can I assume this was during output?

I can't tell you if there's a quick fix without additional information. Go to Tools > Options > Advanced Stream Parameters. Check Output Debug Data to Log File This will output lots of debugging info into the log file. Re-create the problem and email the log file to us at support@videoredo.com.

If you have lots of edits, you'll probably find it easier to initially save them as a project before doing the output.

I'm sorry you're having this problem, we will work hard to get to the bottom of it quickly.

[DanR]

Spectre, One more question. Do you have multiple input files you are trying to join?

[Spectre]

Email sent with log file..

thanks

[DanR]

Sam, I sent you a private email detailing the cause of the problem. Just came back here to look more closely at your configuration. Noticed that you are using a WinTV capture card. That card doesn't have MPEG2 encoding on it. What happens is that SnapStream does an MPEG2 software conversion on the fly. I don't know how good a job it does, since my SnapStream system uses the PVR-250. However, I just put an old ATI all-in-wonder into a fast (AMD 1700+) Win98 system I'm testing for someone else. I'll load SnapStream on it later this week and see how the software encoding works. My wife has an Athlon 900MHz with a WinTV, with SnapStream it can't do on-the-fly encoding.

At least on the file you sent me there were tons of missing frames, about 25% of the frames by my calcuations. You might consider lowering your bit rate and resolution to see if the encoding is any better. Another thing to check is to make sure there aren't any other programs running at the same time. Things like virus scanners can cause problems if run during real-time encoding.

[Anonymous]

I'm using a PVR-250 with a multi generational VHS tape. The audio and video are in sync when played as an mpeg either in the computer or on the stand alone DVD player. When resaving the file as an mpeg during the VideoReDo resync, the program halts at the 1.5 hours mark of 2 total hours with the "mpeg stream error, ring buffer overflow". I know from analyzing with pvastrumento, that there are quite a few audio errors reported in the section where the program halts. I tried re capturing the video with alternate audio bit rates only to have the same halting at the same place. Another similar tape caused a halt in Videoredo with the same error reported but at an earlier junction.

Interestingly, I took the completed section (the first 1.5 hours) and DVD authored with Ulead DVD Movie Factory 2 SE. For the first time with this tape, the contents were perfectly in sync.

I don't believe this program should ever halt due to a possible stream error. If this bug can be corrected, we will have a winner.

rjrangers

[DanR]

I don't believe this program should ever halt due to a possible stream error. If this bug can be corrected, we will have a winner

I agree with you. These checks were put in to account for "impossible" stream errors. However, I continue to surprised at the variety "impossibilities" :) inside MPEG files. You didn't say whether the ring buffer overflow was an Audio or Video ring buffer.

I've made quite a few fixes in the past week to minimize and correct the streams when it encounters these problems. I'd like you to try the current test version (build 202) to see if it fixes addresses this problem. Please contact me at: support@VideoReDo.com and I'll give you the info on downloading that version from our FTP site.

[nigelb]

I agree with you. These checks were put in to account for "impossible" stream errors. However, I continue to surprised at the variety "impossibilities" :) inside MPEG files. You didn't say whether the ring buffer overflow was an Audio or Video ring buffer.

The Hauppauge WinTV PVR-250/350 seems particularly prone to producing files with impossible stream errors both when used in Media Center Edition & with various standalone recording applications. I have a number of MPEG & DVR-MS files that play happily but have proved inpossible to edit or author to DVD.

If there is some way for you to ignore them or skip over that bad portion of file then that would be a great solution. Given the choice between not being able to author a DVD or just having a glitch for a second or 2 then I go with the glitch.

[DanR]

I have a number of MPEG & DVR-MS files that play happily but have proved inpossible to edit or author to DVD.

If there is some way for you to ignore them or skip over that bad portion of file then that would be a great solution. Given the choice between not being able to author a DVD or just having a glitch for a second or 2 then I go with the glitch.

VideoReDo accepts many, many MPEG2 stream anomolies and tries to either correct them or at worst delete the offending portions and resync the files. The output files from VideoReDo are MPEG2 compliant and should have no problem being authored to DVD, with the caveat that not all MPEG2 compliant files are DVD compliant. DVD has tighter restrictions than MPEG2.

The buffer overflow issues that we've seen with a few files will be addressed in the maintenance next release due out in a week or so. This will include support for streams that have 3:2 pulldown, AC3 bitrate changes in the file and some issues associated with very large GOP sizes (> 30 frames / GOP) all of which caused VideoReDo to hiccup.
The many internal consistency checks within VideoReDo are there to prevent the program from crashing when faced with unknown stream conditions. As these streams are encountered and sent in for support, VideoReDo will be enhanced to attempt a more graceful and automatic correction.

So, the bottom line is, if you get a stream error either from VideoReDo or in a program that uses its output, please let me know and I'll try and fix it.