Strange behaviour in windowed mode

[lighttear]

I am intensively testing DVBViewer 4.0 since its coming out, and I recently realized this strange behavior:

 

- in windowed mode, when tuned on a sat or terrestrial channel, audio and video are fluently reproduced but DVBV 4.0 seems to lock every 1.5 second for a while (audio and video are not affected by this lock): moving the mouse over the DVBViewer menus stalls for a while, or when increasing or decreasing the volume with the mouse wheel I note periodic stalls (roughly every 1.5 secs).

- when minimized or in full screen this DO NOT HAPPEN

- when in windowed mode I reproduce a video file (not live TV) this DO NOT HAPPEN

 

This occur both on my favorite O.S. Win XP SP2 (see attached support.zip) AND on my Vista business SP1 fresh install partition

 

I am writing this post because this bug is very annoying and this DO NOT HAPPEN AT ALL with older DVBViewer 3.9.4.0 (i made a copy of its full directory before unistalling it)

 

Comments: I tried changing priority , avoiding any plugin, stopping antivirus etc. but the bug is still here

 

Additional information: my mobo is an Asus P5Q3, my video card is an Asus HD3650 silent (driver v. 8.511),

my sat card is a Technisat Skystar HD with latest technisat BDA drivers, my terrestrial card is a Hauppage Nova DVB-T with latest BDA drivers.

 

Thanks for Your kind reply

 

L.

support.zip

[lighttear]

UPDATES:

 

- bug confirmed on a windows XP SP2 totally different computer: periodic stall of dvbviewver 4.0 when tuned on a:

 

- hauppage Nova DVB-T PCI card and latest BDA drivers (here the bug is more evident, several ten's of second of stalls every 1.5 seconds)

 

AND

 

- technisat skystar HD pci card (aka technotrend S2-3200) with latest TECHNISAT BDA driver. NOTE: if latest TECHNOTREND BDA drivers are installed, stalls are (almost) disappeared but ONLY when tuned on sat channel; stalls on dvb-t channels (using hauppage card) still there.

 

 

Confirmed that previous 3.9.4.0 release of DVBViewer has NOT this bug.

 

Thanks for your patience.

 

L.