Rich Ellis

Help! I'm seeing weird errors coming from DirectShow when using HDLink. I have a trouble ticket open with Cineform but it's not going anywhere so far. Has anybody seen anything like this? Hoping another user can point me where to look for troubleshooting, at least.

I've installed the Neo HDV trial version, using it to convert AVCHD files from my Canon HF100 into intermediate files so I can edit on Vegas Pro 8. I like the results so far, and I'm thinking about buying the program -- if I can get my head past the fact it's downsizing my 1920 clips to 1440. Cineform says it doesn't matter. I'm taking their word for it so far.

But I'm having a technical issue: I can't convert more than one or two clips at a time. If I select one clip, no matter what it is, it always works. If I select multiple clips it will successfully convert one or two, but when it starts the 3rd (or maybe 4th, or sometimes the 2nd) it crashes. The log contains stuff like this:

...
Bulding conversion graph.
Using Super-Threaded Conversion
Error: m_mediaControl->Run() (0x8007000e - Not enough storage is available to complete this operation.) in (DirectShowGraph.cpp at 218)
Error: m_convertGraph.StartGraph() (0x8007000e - Not enough storage is available to complete this operation.) in (CFCaptureDlg.cpp at 2271)
Error: ConvertClip(next) (0x8007000e - Not enough storage is available to complete this operation.) in (CFCaptureDlg.cpp at 2328)


I have to close the program at that point. I can restart it, select the file that crashed, and convert it with no problems.

I've dealt with Windows XP enough to know that the "not enough storage" error is caused by an out of memory condition more often than an out of disk space condition, and caused by a DLL or registration conflict (or some other configuration problem) more often than both of the first two combined. In any case I know my nearly empty 750 GB hard disk and 2 GB of RAM should not be running out of room.

Per CineForm's tech notes, I've installed CoreAVC Pro and the Haali splitter that came with it. The version of the splitter seems to be the same that's available for download on the Haali splitter website. I know the CoreAVC codec is working because I can play the original AVCHD clips in Windows Media Player.

I'm not familiar enough with DirectShow and how it works to be able to chase this down. If anybody has experienced this and knows how to fix it, they will be my new best friend!

Rich Ellis

Still no word from CineForm in the support ticket, but in case anyone is reading this, I at least was able to find out that it's crashing because of a memory leak. Private Bytes doubles after every converted file. It isn't letting go of something when a file is finished. I have to close the program and rerun it. Don't know if this is because of the HDLink program itself or if it's a problem with something along the DirectShow chain.

Anybody know a way to verify exactly which DirectShow components a program is using? Is there a "debug mode" for HDLink that might dump more info to the log?

Tim Bucklin

Hi Rich,

We've spent parts of the last couple of days trying to get to the bottom of your problem.
We were able to reproduce the problem on *one* of our machines here, yet not on any of the others, so we're in the process of hunting down the potential culprit.

What seems to be happening is that the Haali splitter and AVCHD decoder are negotiating for a subtype of "avc1", which the decoder's having a hard time decoding properly. When it's linked up to our components, it's telling them that the frame size is 0x0 instead of 1440x1080, so it's not allocating the appropriately-sized buffer(s).

The real kicker is that with the exact same source file, Haali splitter, AVCHD decoder, and CineForm components in the DirectShow graph on two different machines is producing different results. We've tried toying around with the Haali settings, but those both match.

Jake should be getting back to you tomorrow morning with a couple things to try and a version of HD Link with some debug output enabled.

You've definitely come up with an odd one, but luckily one of our machines is equally as unhappy as yours.

__________________
Tim Bucklin
CineForm Software Engineer

Rich Ellis

Sorry... well, at least I was able to provide some intellectual challenge.

This is starting to sound eerily like my day job.