wuzel
15th May 2003, 23:42
hi there,
after lurking for a loong time, this is finally my first but longish post.
i noticed some nasty behaviour with virtual dubīs real-time capturing mode and although there have been similar posts here and at other forums as well the issue has never really been tracked down... so this is my final try to do so.
during real-time capture virtual dub crashes on a constant but not repruduceable basis.
it can happen after just 10 minutes or even after three hours.
when this happens the whole windows gui freezes i.e. no more mouse movement, no more system-time updates; only sound is still playing in real-time.
the computer can only be brought back to life by a hardware-reset.
iīve seen this behavoiur with quite different hardware configurations so it probably isnīt a hardware-related prob.
hardware:
happend with my old PIII system:
Asus P3BF mainboard, 128 MB SDR-RAM, GForce 1 SDR, IBM 25GB harddisk 5400 rpm, soundblaster 16 PCI; just as well as with my newer PIV one:
Asus P4PE, 512 MB DDR-Ram, GForce 4 TI, Maxtor 80GB 5400 rpm, on-board sound)
the only hardware-components that have not been changed up to now are the microsoft mouse - think we can forget about this particular one - and the hauppauge win TV pci card.
both systems have always been configured properly (constantly updated drivers, no overclocking at all)
software:
iīve seen the famous freezing bug throughout all virtualdub versions from 1.4 on to the current release, including all modified versions iīm aware of (vd-vcr,-sync,-mod)
so the problem could eventually be hidden deeply in the guts of virual dub -or there is no relation between vdub and these crashes at all.
freezes happen with all codecs i ever used (obsolete indeo4 just as well as divx 3,4 and xvid, both stable and alpha builds, including the ones by koepi,nic and umaniac)
vdub settings:
resolution: 512*384, preview mode on/off (hide on capture);
since i never get any dropped frames (except for all frames after the system freezes...) it is probably not a matter of system-overload or a pci bandwith issue.
always used win98se.
the second thing wich has never been changed was the use of hauppauges vfw drivers. so maybe this could be the eye of the storm.
i tried wdm drivers instead, both from hauppauge and the open-source alternative but those are way too slow (thanks to microsofts wrapper?) for real-time capture at my desired resolution (loads of dropped frames).
finally i noticed that the number of failed captures seems to increase as the system matures (re-installing vfw drivers has a tendency to prevent the next three captures from crashing)
but maybe some voodoo could result in just the same effect.
hopefully those few user who reported the freezing bug before me can recognize their problem here.
(you donīt have to buy new hardware just to find out, nothing finally improves the situation)
if anybody experienced those crashes and found a solution to it (except for buying a vcr) donīt hesitate to save the freezing-plagued minority of vd-users.
after lurking for a loong time, this is finally my first but longish post.
i noticed some nasty behaviour with virtual dubīs real-time capturing mode and although there have been similar posts here and at other forums as well the issue has never really been tracked down... so this is my final try to do so.
during real-time capture virtual dub crashes on a constant but not repruduceable basis.
it can happen after just 10 minutes or even after three hours.
when this happens the whole windows gui freezes i.e. no more mouse movement, no more system-time updates; only sound is still playing in real-time.
the computer can only be brought back to life by a hardware-reset.
iīve seen this behavoiur with quite different hardware configurations so it probably isnīt a hardware-related prob.
hardware:
happend with my old PIII system:
Asus P3BF mainboard, 128 MB SDR-RAM, GForce 1 SDR, IBM 25GB harddisk 5400 rpm, soundblaster 16 PCI; just as well as with my newer PIV one:
Asus P4PE, 512 MB DDR-Ram, GForce 4 TI, Maxtor 80GB 5400 rpm, on-board sound)
the only hardware-components that have not been changed up to now are the microsoft mouse - think we can forget about this particular one - and the hauppauge win TV pci card.
both systems have always been configured properly (constantly updated drivers, no overclocking at all)
software:
iīve seen the famous freezing bug throughout all virtualdub versions from 1.4 on to the current release, including all modified versions iīm aware of (vd-vcr,-sync,-mod)
so the problem could eventually be hidden deeply in the guts of virual dub -or there is no relation between vdub and these crashes at all.
freezes happen with all codecs i ever used (obsolete indeo4 just as well as divx 3,4 and xvid, both stable and alpha builds, including the ones by koepi,nic and umaniac)
vdub settings:
resolution: 512*384, preview mode on/off (hide on capture);
since i never get any dropped frames (except for all frames after the system freezes...) it is probably not a matter of system-overload or a pci bandwith issue.
always used win98se.
the second thing wich has never been changed was the use of hauppauges vfw drivers. so maybe this could be the eye of the storm.
i tried wdm drivers instead, both from hauppauge and the open-source alternative but those are way too slow (thanks to microsofts wrapper?) for real-time capture at my desired resolution (loads of dropped frames).
finally i noticed that the number of failed captures seems to increase as the system matures (re-installing vfw drivers has a tendency to prevent the next three captures from crashing)
but maybe some voodoo could result in just the same effect.
hopefully those few user who reported the freezing bug before me can recognize their problem here.
(you donīt have to buy new hardware just to find out, nothing finally improves the situation)
if anybody experienced those crashes and found a solution to it (except for buying a vcr) donīt hesitate to save the freezing-plagued minority of vd-users.