English Amiga Board


Go Back   English Amiga Board > Support > support.WinUAE

 
 
Thread Tools
Old 12 October 2018, 17:15   #1
Dr.Venom
Registered User
 
Join Date: Jul 2008
Location: Netherlands
Posts: 397
Soundblaster X AE-5

Hi Toni,


I just got a Soundblaster X AE-5 card, which supports up to 384Khz, but I'm having the issue that WinUAE won't accept the 384000Hz (manually entered) when in Wasapi-EX mode, but it works when using Wasapi Shared mode.

Any idea why WinUAE could have an issue with that rate when in Wasapi-EX mode?


Here's some more info:

I thought I'd do some tests with WinUAE, disabling interpolation and filters and seeing whether I can hear a difference with the various frequencies. From some old forum posts I understand that theoretically WinUAE may benefit from higher frequencies because of the Paula audio channel mixing being more accurate; at least as long as none of the interpolation methods, anti or Sinc are being used (i.e. we're just in plain Paula channel mixing mode). Hope I understand this correctly.

I wanted to make the comparison with Wasapi-EX such that that the Windows mixer is bypassed completely.

The issue is that WinUAE accepts 48000, 96000 and 192000 (latter two manually entered) when in Wasapi-Ex mode, but when I enter 384000 it keeps resetting to 192000 when I click OK.

When I set the Win 10 settings to 384000Hz and use Wasapi shared in WinUAE there's no issue, WinUAE accepts the 384000 in shared mode (the selection is by default 384000).

Any idea why in Wasapi-EX mode it keeps resetting to 192000Hz, is this a driver issue or can something be done on the WinUAE side?
Dr.Venom is offline  
Old 12 October 2018, 17:43   #2
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 43
Posts: 22,013
You do know that log probably tells more..
Toni Wilen is offline  
Old 12 October 2018, 23:21   #3
Dr.Venom
Registered User
 
Join Date: Jul 2008
Location: Netherlands
Posts: 397
Yes you're right, hope these are useful. Attached are three logs.

1. Started with saved setting at 192000 -> open GUI, change to 384000 -> close. Open GUI and value is at 192000.

2. Second is started with a manually edited config file, changing the 192000 to 384000. Open GUI shows it at 384000 (but is it really?) -> close

3. Third is again with the manually edited config file from 2 -> Open GUI (value shows 384000), change filter setting to Emulated A1200, close GUI -> Open GUI again and value is at 192000.


Edit: Fourth testcase: with manually edited config file from 2 -> open GUI (value shows 384000) -> close GUI -> Open GUI (value shows 384000) -> close GUI -> Open GUI, value is at 192000.
Attached Files
File Type: zip winuaelog3.zip (14.7 KB, 22 views)

Last edited by Dr.Venom; 12 October 2018 at 23:27.
Dr.Venom is offline  
Old 13 October 2018, 22:52   #4
Toni Wilen
WinUAE developer
 
Join Date: Aug 2001
Location: Hämeenlinna/Finland
Age: 43
Posts: 22,013
I think your test must have been faulty because GUI limits frequency to 192KHz. (I thought problem was something else because you said non-exclusive worked. It should not have been possible..)

Limit increased to over 700Khz.. (and no, it higher frequency preset values won't be added!)
Toni Wilen is offline  
Old 17 October 2018, 14:38   #5
Dr.Venom
Registered User
 
Join Date: Jul 2008
Location: Netherlands
Posts: 397
Thanks, works like a charm now.

I'll be adding custom inputs to switch between rates with a hotkey during runtime and see if I can hear a difference..


I'm running into a minor related issue, which is that I would like to match exact PAL refresh and Paula output rate at default values as a base case, while still having beamracing sync enabled.

I'm doing this:
Code:
displaydata_pal=49.9204092835,locked,pal
in pal long field mode I would expect the audio rate to be exactly 3546895 Hz

but the log reports this: 09-259 [106 000-000]: SNDRATE 313.0*227.0*49.920410=3546895.062012

It seems the custom refresh rate field is truncating/rounding the PAL refresh rate to 49.920410?

I'm "worried" that having the soundrate off by that bit may be introducing aliasing artifacts in the sound stream where it shouldn't.*




*I agree, this assumes a) the custom screenmode has an exact refresh rate match and b) the soundbuffer is stable and no dynamic resampling is done, so this will probably all be a little theoretical, but I rather have the theory perfect than assume differently before trying..
Dr.Venom is offline  
 


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
PCX soundblaster emulation Sandro support.Apps 3 28 August 2015 18:45
Soundblaster Live! with A1200T Mediator vasco_matias support.Hardware 11 01 June 2013 18:32
Soundblaster 128 on Mediator PCI fitzsteve support.Hardware 30 17 September 2010 13:26
Soundblaster 128 Wasagi MarketPlace 0 03 July 2010 13:49
WTB: SoundBlaster 16 CT-1740 keropi MarketPlace 2 14 October 2007 19:37

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT +2. The time now is 13:22.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2018, vBulletin Solutions Inc.
Page generated in 0.06389 seconds with 16 queries