Textsub causes 100% cpu

[foxyshadis]

Anyone else having this problem? This is the first time I've used vsfilter since I got the new computer (core duo, xp pro).

Specifically, what happens is that when I load vdub with a single textsub call, it runs fine but hogging 50% cpu (one core) from the main system. Any more calls and it's 100%. Reloading hangs up vdub completely. Strange part is, if I use process explorer, I see extra vsfilter threads, one for each textsub, sitting there, and if I kill them cpu usage goes down to normal with no ill effect (subtitles work), except that reloads still hang.

I've tried versions of avisynth from 2.5.5 to current cvs, and the latest and an older vsfilter, and they ALL seem to do this. Also the last 3 versions of vdub, and mpc. It happens with any kind of source call, even blankclip(). These exact same subtitle files worked on my two old machines.

Anyone know why vsfilter sits in a busy loop like that?

[Quarkboy]

Did anyone ever solve this problem? I just upgraded to a core 2 duo, and I'm getting the exact same symptoms as the first post... namely that any textsub call causes crazy processor usage.
I wonder if it's a dual core processor problem...

EDIT: I did a bit of testing, and it seems that only VSFilter 2.36 and 2.37 have this program. 2.35 and earlier run fine.
I suspect this is a real bug in vsfilter having to do with the new dual core intel processors. I hope you can get this fixed, as I'm a fansubber and would like my fancy new encoding machine to be able to use the most recent vsfilter.

[squid_80]

I may be completely off track, but I think it might have something to do with vsfilter.dll being a directshow filter as well.

[foxyshadis]

I recall having just made a post yesterday about this to someone else... but yes, I debugged and helped fix it. (Though gabest came up with a better solution.) It is an absolute pain setting directshow and MPC up for debugging the first time, let me tell you.

Ah yes, http://forum.doom9.org/showthread.php?p=864720#post864720

Anyway, the latest celtic_druid compiles should work. Otherwise, I'll upload mine.

[squid_80]

Any source code for the changes? Gabest doesn't seem to use comments with his SVN commits so I've got no idea if the source I'm using is fixed or not.

[foxyshadis]

The specific bug was r610, almost the last update. It was never released as a numbered version but it's been the latest since April. Other related bugs may be in nearby code, but that fixed it for me.

[Quarkboy]

Thanks a lot for all your hard work!
As usual, doom9 forums solves the problem quickly :).
I'll see about that latest celtic druid build.

P.S. if this was a problem with core 2 duo compatibility, I'd suggest releasing a new version with the fix soon, as I can imagine a lot of people upgrading their systems in the next few months to these incredibly fast chips (3.5x faster x264 encoding, w00t!).

[Quarkboy]

Hmm, well I tried the latest celtic_druid compiles, but they would cause avisynth to crash randomly during encodes on my machine.

I guess I'm okay downgrading to 2.35 for now, but I hope the next full release will be stable.

[moonlilly]

I don't know what it is exactly... but I have similar issues with Core 2 Duo - StaxRip, VirtualDub Mod, Xvid.

While trying to encode with xvid 2pass virtualdub mod crashes after completing 1pass successfully (i didn't have these problems before with d805). Is there any known patch or workaround?

I tried encoding with divx (runs stable) but audio is out of sync (???).

Any suggestions?