GSpot-related memory error ...

[absinthe]

I'm having this weird little problem with GSpot (latest beta). More of an annoyance, really.

Every time I close it, I get an "application error." Such and such memory cannot be referenced at such and such a location. Click OK to terminate.

It all works fine except for that annoying error and the hideous Windows error sound that accompanies it. I've been letting it go now for a couple of months but it's on my last nerve. I've tried uninstalling and reinstalling.

Ideas?

-abs

[niamh]

Does the same to me. I don't really mind :)

[cypher_soundz]

must not post link... :D (http://forum.doom9.org/showthread.php?t=96137)
Regards
cyph

[GrofLuigi]

I'm having this weird little problem with GSpot (latest beta). More of an annoyance, really.

Every time I close it, I get an "application error." Such and such memory cannot be referenced at such and such a location. Click OK to terminate.

It all works fine except for that annoying error and the hideous Windows error sound that accompanies it. I've been letting it go now for a couple of months but it's on my last nerve. I've tried uninstalling and reinstalling.

Ideas?

-abs

I had exactly the same behaviour when I had ffdshow installed (various builds, up to maybe a month ago). I think ffdshow itself was not guilty, but some setting of it (the colorspace (in combination with graphic card (i.e. whether it accepts YV12)); or the audio (had the same problem with some audio programs)).

After I uninstalled ffdshow, it all went away.

GL

*edit - wasn't really readable without nested brackets :D

[Shinigami-Sama]

the hideous Windows error sound that accompanies it.

Ideas?

-abs
turn them off :D
I did, saved what was left of my sanity :)

[yaz]

imho, the beast is called ff_acm.acm regged in drivers32 (msacm.avis key). it sets when avisynth script serving is requested. (i guess, it's for audio serving)
i got some other problematic items in the codecs list (say, what 3ivx left behind) but that do not trigger the error.

anyway, it doesn't harm. so, if u need ffdshow script support, live with it, don't set it otherwise.

the bests
y

[absinthe]

I had exactly the same behaviour when I had ffdshow installed (various builds, up to maybe a month ago). I think ffdshow itself was not guilty, but some setting of it (the colorspace (in combination with graphic card (i.e. whether it accepts YV12)); or the audio (had the same problem with some audio programs)).

After I uninstalled ffdshow, it all went away.
Interesting. However, I don't want to do without ffdshow. I note that if I uncheck the "enable interaction with system codecs" option, the probably goes away. Unfortunately, so does the usefulness of ffdshow.

Guess I'll have to live with it until we get a fix. I wonder if this has been reported.

-abs