View Single Post
Old 20 May 2017, 08:46   #70
ED-209
Registered User

ED-209's Avatar
 
Join Date: Mar 2012
Location: OCP
Age: 37
Posts: 960
Toni I have 2 questions.. both of which are probably annoying

First is I've noticed that the 'min' buffer seems quite high with my card (sb x-fi titanium pcie). I know that using the updated HDAudio driver in conjunction with onboard audio will allow lower limit, but is there any way to force a lower limit with the x-fi card? I could get away with setting max_buffer as low as 256 before pull was implemented.
Here's my startup log with 'min' buffer + low latency vsync. Notice the illegal instruction - this does not appear with other buffer settings.. only 'min'.
Code:
WASAPI: GetCurrentSharedModeEnginePeriod() CH=2 FREQ=48000 BITS=32 CurrentPeriodInFrames=512
WASAPI: GetSharedModeEnginePeriod() DPIF=512 FPIF=512 MinPIF=512 MaxPIF=512
WASAPI: IsOffloadCapable() returned 0 00000000
WASAPI: InitializeSharedAudioStream() Period=512. HRESULT=00000000
WASAPI: GetCurrentSharedModeEnginePeriod() CH=2 FREQ=48000 BITS=32 CurrentPeriodInFrames=512
WASAPI: '{0.0.0.00000000}.{7c412605-1785-4e79-8e0a-645efd07f4f0}'
WASAPI: Shared Pull CH=2 FREQ=48000 BUF=563 (1126)
Illegal instruction: 4e7b at 00FC0564 -> 00FC0582
My other question:
Since using pull mode, I have run many hundreds of OCS demos in CE mode and the vast majority have perfect audio with min buffer setting. However there have been rare cases where certain demos require huge buffer or non vsync mode for audio to be glitch free.
Current case is ASS by Essence.. unless I set to maximum buffer or disable low latency vsync there are audio pops/glitch throughout the entire demo. I'm not getting any pull errors in the log, and CPU usage is always low (~50%).. any idea what could cause this?
ED-209 is offline  
 
Page generated in 0.04833 seconds with 9 queries