View Single Post
Old 28 November 2016, 10:35   #1
Dr.Venom
Registered User
 
Join Date: Jul 2008
Location: Netherlands
Posts: 278
RawInput enumeration after "on the fly " screenswitch causing audio/video hickup

I'm running into an issue where the sound / video has a noticable glitch/hickup after a "on the fly" screenswitch (configured with displaydata).

Looking deeper into it, the cause seems to be a full rawinput device enumeration occuring after each screenswitch. So screenswitch finishes and a fraction of a second later full rawinput enumeration gets logged at the same time the audio/video hickup occurs.

I tried to create a "simple" testcase which you can replicate on LED display, using 1080p / 1080i on the fly switching, tested with both NVidia and iGPU.

Displaydata:
displaydata=50.000000,t=lof,pal,nlace,cmd=gfx_width_fullscreen=1920,gfx_height_fullscreen=1080,gfx_linemode=double,gfx_refreshrate=50,gfx_interlace=false,gfx_display=1
displaydata=25.000000,pal,lace,cmd=gfx_width_fullscreen=1920,gfx_height_fullscreen=1080,gfx_linemode=double2,gfx_refreshrate=25,gfx_interlace=true,gfx_display=1

I've been testing with the demo "Big Time Sensuality" from Axis, as it does a series of progressive/lace switchings during the beginning of the demo.

There's an interesting difference between using iGPU or NVidia, and additionally for iGPU a difference between version 3.0.0 and 3.1.0 onwards.

iGPU with WinUAE 3.4.0.b17
after -every- screenswitch a full rawinput enumeration occurs:

46-777 [101 000-000]: RawInput enumeration..
46-777 [101 000-000]: RAWINPUT: found 11 devices
[snip long list of devices..]


Nvidia with 3.4.0.b17
When using NVidia card both the audio/video hickup and the rawinput enumeration after a screenswitch do -not- occur.

iGPU with WinUAE v3.0.0 and 3.1.0 onwards
For the iGPU the issue does not occur in version 3.0.0. It starts occuring from 3.1.0 onwards.

Please see attached logs. Since this device enumeration on iGPU seems to be the cause for the audio video glitch/hickup after each switch, hopefully there a solution for it (or possibly the 3.0.0 behaviour re-enabled).
Attached Files
File Type: txt winuaelog_300_iGPU.txt (15.7 KB, 30 views)
File Type: txt winuaelog_310_iGPU.txt (49.4 KB, 57 views)
File Type: txt winuaelog_340b17_iGPU.txt (57.6 KB, 21 views)
File Type: txt winuaelog_340b17_NVidia.txt (18.8 KB, 60 views)

Last edited by Dr.Venom; 28 November 2016 at 10:47.
Dr.Venom is offline  
AdSense AdSense  
 
Page generated in 0.09142 seconds with 10 queries