Crash trying to save frame accurate edits

[Trippy]

I've just discovered this program after browsing through the BeyondTV forums and have been testing the program on TV tuner captures from my ATI 9600 Pro AIW card and I'm having an problem trying to save videos with "Frame Accurate Editing" turned on. With that turned on VideoReDo will quit without any message (build 221) or crash with an error (from the Event Viewer):

Faulting application videoredo.exe, version 1.5.5.233, faulting module videoredo.exe, version 1.5.5.233, fault address 0x0003f145.

(build 233).

The weird thing is that in the test case I've tried to create with just a single edit selection it doesn't always crash -- sometimes it will save the video without any error. If you try and save it again immediately after a successful save it will crash on my system.

If I turn *off* "Frame Accurate Editing" I have not, so far, been able to crash the program.

I've packaged up a test case into a ZIP file called "Trippy_Crash_Test.zip" with more information and instructions on how to (hopefully) reproduce the problem and am in the process of uploading the file right now to your uploads directory (will take a while, I only have 128 Kbps upload).

[DanR]

Hello Trippy, Sorry you're having this problem and thanks for uploading the project. Will get right on it.

[Trippy]

Hi Dan, thanks for replying so quickly (do you even sleep?). You might not want to spend too much time looking at this problem, however. I just finished installing VideoReDo on another computer with a totally different hardware configuration and so far I haven't been able to reproduce the problem. So it's possible there's just something funky about my main computer (which has built up quite a bit of cruft, I have like 6 MPEG-2 decoders installed, heh) that's causing this crash.

[DanR]

Found IT! The problem is (was) that the ATI MPEG stream has some I-Frames in the middle of a GOP. This is allowed under MPEG2, but very rare. When you made the cut, we looked for the previous start of GOP and picked up that I-Frame as the start when it fact it wasn't the original start. From there on everything else went downhill.

Question, I'm curious why are you recording audio at 44.1KHz instead of the more DVD standard of 48KHz?

[Anonymous]

Found IT! The problem is (was) that the ATI MPEG stream has some I-Frames in the middle of a GOP. This is allowed under MPEG2, but very rare. When you made the cut, we looked for the previous start of GOP and picked up that I-Frame as the start when it fact it wasn't the original start. From there on everything else went downhill.

Interesting. I wonder why I haven't had the crash yet on another computer.


Question, I'm curious why are you recording audio at 44.1KHz instead of the more DVD standard of 48KHz?

Good question :lol: Checking the different presets it looks I must have based my preset on the provided "Good" setting which has the audio set to 44.1KHz (that's also why it's at 704 instead of 720 horizontal resolution).

[Trippy]

Whoops, the above post was from me :oops: Didn't realize you could post as a guest and didn't know I was logged out.

[DanR]

Interesting. I wonder why I haven't had the crash yet on another computer. That's a good question as well. With memory issues, which this was, you never quite know when things will blow up or not. That's why they are so hard to check. Also, this particular error is very frame dependent. Moving the cut one or two frames either way could change all the dynamics that caused the problem in the first place.

Also, I might suggest that you disable inverse 3:2 pulldown. Find it hard to belive that it will significantly improve compression and some DVD authoring programs exhibit sync issues when 3:2 pulldown is randomly applied as it is with the ATI inverse 3:2.

[Trippy]

Also, I might suggest that you disable inverse 3:2 pulldown. Find it hard to belive that it will significantly improve compression and some DVD authoring programs exhibit sync issues when 3:2 pulldown is randomly applied as it is with the ATI inverse 3:2.

Thanks I'll give that a try.