Debugging custom DES effect
mtsay
I have developed a custom chroma-keying effect to be used in a
DirectShow Editing Services (DES) timeline, and in the past, it's been
working great. Recently, I switched to use ffdshow encoders and I
started to get a strange problem I'm not sure where to start
debugging.
My pipeline involves recording a video (encode it with ffdshow,
MPEG-4), render the DES timeline (presumably the default decoder will
be ffdshow), and then encode the output from DES timeline using
ffdshow again, and we typically record/render in a batch (50+ in one
sitting).
Sometimes, the video will render correctly for 3-4 videos, and
from that point on, the chroma-key will drop everything (keying out
the entire track) until we exit and restart the program, and it
persists. Now if we re-render the exact same timeline after restart,
it will render correctly (for 3-4 videos) and then the problem came
back.
So it'd appear to be an issue with resource and I'm not certain
how to go about tracking it down. Also, I've monitored the memory
usage of the program during operation and the usage is stable so a
memory leak is unlikely.
This problem appears on some machines which leads me to believe it
may have something to do with external settings with the codec, and if
so, what should I be looking for when I examine the settings?
Any constructive input will be appreciated.
mtsay
I've found the cause and it's something else, consider this thread
closed.