avs2avi + mcbob + directshowsource crashes - any ideas?

[wonkey_monkey]

Hi, this is another one of my mysterious problems which I'm not sure anyone will be able to shed any light on...

Using avs2avi to process an AVS script which uses DirectShowSource to load a DV AVI (I can't use AVISource because it's from a DVCPro tape, which neither Cedocida nor VirtualDub's built-in DV decoder can decode properly) results in a crash when it gets to frame 5.

Is it likely to just be another memory thing that I can't do anything about? If no-one knows a solution, I'll just have to recompress it to another codec, but obviously I'd rather avoid that (I don't think I'll have the room for a huffyuv encode).

Thanks,
David

[IanB]

DirectShowSource(..., Logfile="blog.log", Logmask=-1)Post the log!

[wonkey_monkey]

There are two files used as source, so I've uploaded both logs in a zip file, but I get the same error when only using one file. You can probably see in a.log that DSS is starting from 5000 - this is because of a trim command I put into the AVS script, but again, the error is present if I start from 0, and always on the same frame of output.

I don't anything about DSS logs, but nothing jumps out at me as an error from a quick glance.

David

[IanB]

a.log 4 attempts
1. open - close normal
2. returned frame 5033 - truncated? 3 secs per frame
3. open - truncated?
4. returning 5031 - truncated? 3 secs per frame

b.log 3 attempts
1. open - truncated?
2. open - truncated?
3. open - truncated?

At each entry the end of log is missing?

Please describe the crash scenario. I take it these are not Avisynth error traps but are hard process aborts, hence the tail of the log is not flushed.


Does a simple DirectShowSource only, no frills script parse the file?

Does the script preview corectly in VirtualDub?

:script:

[wonkey_monkey]

At it's simplest, the script is this:


a=directshowsource("...
b=directshowsource("...

a+b

converttoyv12(interlaced=true)
mcbob


With the above, avs2avi generates two "memory could not be read" after a few frames and the process aborts. However, if I change "a+b" to simply "a" or "b" (so only reading one of the AVIs), I get a single error - and if I ignore the error messages, the process continues and completes the file exactly as expected!

So it looks like I might get away with it after all, if I join my two AVIs with Direct Stream Copy. The real processing will be done remotely, so the error messages won't appear.

The mystery deepens, yet again... if I use a quickly converted xvid AVI with AviSource, I get a "memory could not be read" error right at the end of conversion. The output file, again, is complete.

So far, VirtualDub hasn't generated any errors.

David