![]() Wasapi shared mode works flawless at 10.0ms, apart from the problematic cores.Įxclusive mode works for most cores with very low latencies. With the X-Fi Titanium the setting needs to 48.0ms to be glitch free for these I have some more results from testing with (yet) another soundcard, the Creative Soundblaster Z. The "problematic" cores (bsnes-mercury-balanced, bluemsx, Vice_c64) need a much higher latency in exclusive mode. RetroArch :: : Luidsprekers (Creative SB X-Fi) RetroArch :: : Enumerating active devices. RetroArch :: : Client initialized (shared, float, 48000Hz, 10.7ms). RetroArch :: : Initializing client (shared, float, 48000Hz). RetroArch :: : Initializing default device. Only difference is that the stream is initialized at 10.7ms instead of 10.0ms as with the Audigy 5/Rx, but apart from that audio latency in shared mode is low / glitch free / great. Shared mode works well for the non-problematic cores (the list in one of my previous messages). I've been doing some tests with Windows10 圆4 and Soundblaster X-Fi Titanium. I'll report back with some That's good to know thanks. I have a Soundblaster X-Fi Titanium lying around, so next I'll be testing it to see how it performs in both exclusive and shared mode. Applications that use integer data will have 4.5ms lower latency." (versus Windows 8.1 / 7). I now understand why you would want floating point mode as preferred setting (as you implemented it), quote "Applications that use floating point data will have 16ms lower latency. (v=vs.85).aspx#Audio_Stack_Improvements_in_Windows_10 I guess you may have seen it already, but this is the part that discusses the very low latency for the new High Definition Audio Device (in shared mode), point 4 under measurement tools:Īlso reading up the paragraph on Audio Stack Improvements in Windows 10 here: It's a bit unfortunate as the Audigy Rx driver is very light on the CPU in shared mode, for which I like it. As I mentioned I don't think this is an issue with your implementation, but more that the Audigy 5/Rx doesn't have proper Wasapi Exclusive mode support, as other applications have the same issue when I select Wasapi-EX. When I raise latency to 150ms it gets much less, but it never dissappears (even with higher latencies). Or mute the I tried the wasapi exclusive mode with my Creative Audigy 5/Rx, but indeed it does not work. Reply to this email directly, view it on GitHub You are receiving this because you are subscribed to this thread. Problems? Can you confirm that other audio drivers working correctly on Are you absolutely sure that WASAPI driver is causing these Impose any restrictions on frame rate value, neither tries to adjust it, soĭon't try random values there (I suggest to leave it at default value ofĤ8000Hz). This is probably because the frame rate was set to 32000Hz. ![]() Second one shows unsupported format errors. I think it is better to put that feature on hold until most of asĬonfirm that current implementation works correctly (with everything thatĭon't depends on audio sync off First log says that WASAPI driver Option, but didn't worked correctly in that mode so I removed that part ofĬode. I did coded driver that supported audio sync off Operation in combination with WASAPI driver is, in programming terms, On Wed, at 5:23 PM, Zoran Vuckovic wrote:Ĭurrently driver have audio sync always on. Highly looking forward to seeing some improvements that could hopefully make this driver the ideal choice for Windows RA users.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |