Assertion failed error on video

[armyofquad]

I've been having a real struggle with deinterlacing on larger files.

Virtualdub is a dumpsterfire, creates bad files all the time.

I think I have a bug in my capture.

Regularly I have to repair my captures in easeus fixo due to a missing index. Usually the repair is fine.

Lately I've run into 2 files that have had a problem that when trying to deinterlace, I get an assertion failed error at the same point in the video. The first time I had to give up, and recapture the whole 2 hour tape. This is unreasonable, and not an acceptable solution, I should not have to recapture the 2nd tape, and keep doing multiple captures of tapes due to some idiotic bug that no one seems to be able to acknowledge or fix.

I think the problem existed on the file before running through fixo - if I tried to deinterlace the file with out the index, it would just get stuck at that point and keep growing the new file indefinitely until I crashed it out, creating a difficult to delete large file.

After running through fixo I have a playable file, but now at that point it keeps crashing with this error:


[Attachment 84576 - Click to enlarge]

Seems to be referencing the dll for the cineform codec I'm using for compression. Been using this codec for quite a while now without issues, so I don't believe there really is a problem with that dll.

I think the problem lies with virtualdub, as it is consistently creating problematic files.

I've used different versions of virtualdub, on different computers, and I have consistently no matter what had frequent problems of buggy problematic files created, usually without index, that requires the fixo app to repair.

I'm completely baffled at the complete lack of knowledge or awareness of these problems, as they are so frequent and consistent I do not see how it could only be happening to every computer I touch, and never for anyone else. Yet there seems to be no insight or knowledge to this.

I'm at a complete lost, and quite honestly, quite angry at the amount of wasted time these bullshit errors are costing me.

Someone out there must know something about this crap!

What I require:

A solution/fix for the problem of virtualdub regularly capturing/creating files with no index and with errors/bugs.

A consistent file repair option for problematic files so I don't have to recapture a 2 hour tape for a file that has 1 spot that crashes everything.

[LigH.de]

So you are blaming one of the most reliable video capturing tools known. And without telling in detail what you are doing, it is hard to defend it.

We don't know which video source and capture device you are using. We don't know how you set up VirtualDub, most of all which resolution, video format, codec you set up during the capture phase (it should be matching your analog video source's specifications, at most a lossless codec with fast compression if not even no compression but plain YUY2/UYVY, and certainly no deinterlacing filter during the capture, deinterlacing will be applied to the recorded video later).

[armyofquad]

So you missed the part where I clearly stated I'm using the cineform codec?

[davexnet]

There are quite a few reports (Google search on "cfhd.dll") on this from Sony Vegas and Adobe users,
the common advice seemed to be to delete that dll.
Maybe you should read up on it yourself

[armyofquad]

I read that, it makes no sense. Never in my life have I encountered an error with a library, that the solution is to simply delete the library. That file was put there for a reason, it's only causing an error on a small number of files - I don't want some bullshit unexplained hack, I want an explanation, and a real fix.

Anytime I start messing around with .dll files, it might fix one thing, but break another. I have no idea what things I do are relying on that file. To simply "delete the file" is not an acceptable answer, unless there's some explanation for why, and a guarantee that anything relying on it will fail over to something else, consistently.

[davexnet]

I read that, it makes no sense. Never in my life have I encountered an error with a library, that the solution is to simply delete the library. That file was put there for a reason, it's only causing an error on a small number of files - I don't want some bullshit unexplained hack, I want an explanation, and a real fix.

Anytime I start messing around with .dll files, it might fix one thing, but break another. I have no idea what things I do are relying on that file. To simply "delete the file" is not an acceptable answer, unless there's some explanation for why, and a guarantee that anything relying on it will fail over to something else, consistently.

I understand your stance. Sounds like you better start some research ...