robert_e_bone
Moderator
- Total Posts : 8968
- Joined: 2007/12/26 22:09:28
- Location: Palatine, IL
- Status: offline
OK anyone else getting this kind of ASIO impact on NON-ASIO Windows sound?
Running Sonar Platinum - this issue is present in both 2017-01 and 2017-02.
When I change my ASIO Buffer Size to 2048 for mixing, it somehow is causing problems with sound quality of things like videos played back in YouTube or songs played in Windows Media Player - where Windows isn't even using the ASIO drivers - it is just using the on-board audio. Only Sonar is using ASIO.
If I run the ASIO Buffer Size at 1024, NO such sound degradation occurs for YouTube videos or Windows Media Player songs - again Windows Default Audio Device is NOT pointing at the ASIO drivers - but only to the on-board audio.
The larger buffer size of 2048 actually drops the CPU load from 36% (buffer of 1024) down to 31%, and neither is taxing the CPU - at a buffer size of 128, CPU load is still only 62% with project loaded. So, this is not a CPU load issue.
I am quite baffled by this.
The audio interface happens to be in this case a Yamaha/Steinberg UR22, (as my son has made off with my Presonus AudioBox 1818VSL AND the expansion unit, and my best vocal mic, and a grand piano - he is SO grounded even though he already has engineered several albums with the gear - hee hee).
SO - just wondering if anyone else has experienced any issues like mine, where somehow the sizing of the ASIO Buffer Size is causing a problem if I play something completely external to Sonar that doesn't even use the ASIO drivers.
I would SURELY like to understand how this could happen, and if there is some kind of workaround, or something I am just plain missing.
Bob Bone
Wisdom is a giant accumulation of "DOH!" Sonar: Platinum (x64), X3 (x64) Audio Interfaces: AudioBox 1818VSL, Steinberg UR-22 Computers: 1) i7-2600 k, 32 GB RAM, Windows 8.1 Pro x64 & 2) AMD A-10 7850 32 GB RAM Windows 10 Pro x64 Soft Synths: NI Komplete 8 Ultimate, Arturia V Collection, many others MIDI Controllers: M-Audio Axiom Pro 61, Keystation 88es Settings: 24-Bit, Sample Rate 48k, ASIO Buffer Size 128, Total Round Trip Latency 9.7 ms
|
KPerry
Max Output Level: -44 dBFS
- Total Posts : 3120
- Joined: 2011/04/26 15:13:15
- Location: London, UK
- Status: offline
Re: OK anyone else getting this kind of ASIO impact on NON-ASIO Windows sound?
2017/03/18 08:09:52
(permalink)
Buffer control probably shared between driver modes - my MOTU buffer size control affects both ASIO and WDM for example.
Windows 7 x64 SP1 SONAR x86/x64 Intel Q6600/8GB MOTU UltraliteMk3 (USB/ASIO) Edirol PCR300
|
soens
Max Output Level: -23.5 dBFS
- Total Posts : 5154
- Joined: 2005/09/16 03:19:55
- Location: Location: Location
- Status: offline
Re: OK anyone else getting this kind of ASIO impact on NON-ASIO Windows sound?
2017/03/18 09:20:16
(permalink)
I'd say it shouldn't be doing that. On my setup there's no physical connection between the two and they work fine independent of each other. They're also set to different bit depths and sample rates. ASIO is set to have exclusive control, onboard sound is not.
My interface doesn't do 2048 but @1980 and 2200 there's no issues while running both sound devices.
|
KPerry
Max Output Level: -44 dBFS
- Total Posts : 3120
- Joined: 2011/04/26 15:13:15
- Location: London, UK
- Status: offline
Re: OK anyone else getting this kind of ASIO impact on NON-ASIO Windows sound?
2017/03/18 09:43:04
(permalink)
My bad - I'd misread about the interface. Yeah, should be no interaction if they're different devics.
Windows 7 x64 SP1 SONAR x86/x64 Intel Q6600/8GB MOTU UltraliteMk3 (USB/ASIO) Edirol PCR300
|
tenfoot
Max Output Level: -53.5 dBFS
- Total Posts : 2186
- Joined: 2015/01/22 18:12:07
- Location: Qld, Australia
- Status: offline
Re: OK anyone else getting this kind of ASIO impact on NON-ASIO Windows sound?
2017/03/18 10:04:33
(permalink)
I don't know if it's related Bob, but when I take my asio buffer size in Sonar or Abelton Live above 1024 whilst using midi sync to other devices/programs such as Traktor Pro or DMX control software, irrespective of the driver mode the other software is running (it is obviously never asio), the wheels fall off as well. They lose sync entirely. Anything below 1024 is fine. A weird quirk I have dodged for a couple of years now.
Bruce. Sonar Platinum 2017-09, Studio One 3.5.3, Win 10 x64, Quad core i7, RME Fireface, Behringer X32 Producer, Behringer X32 Rack, Presonus Faderport, Lemure Software Controller (Android), Enttec DMXIS VST lighting controller, Xtempo POK.
|
azslow3
Max Output Level: -42.5 dBFS
- Total Posts : 3297
- Joined: 2012/06/22 19:27:51
- Location: Germany
- Status: offline
Re: OK anyone else getting this kind of ASIO impact on NON-ASIO Windows sound?
2017/03/18 10:32:50
(permalink)
Theoretically that can be CPU issue. What you see as a "CPU load" is an average load. In fact momentary load is always 100% (I mean when some program runs with memory only data, it consumes all possible CPU cycles).
So if something let say block CPU for continuous 0.3 sec every sec (so the rest 0.7 sec it does not use CPU at all), you definitively get problems with audio/other streams while the average load is 30%.
In reality that is not so bad, you have more then one core, there are priorities, interruptions, etc. which "break" that 0.3 sec. But the scenario can be similar (especially if Sonar is using many cores) since to avoid audio glitches, Sonar tries to call the audio processing with priority while other applications (like youtube) and standard audio processing chain care much less to make everything in time.
I mean VST needs 2x time more to process one buffer of 2048 samples compare to 1024 samples and so the resources (CPU) can be a kind of blocked for that time. Depending on the stream setting, this time can be close to the buffer size of Windows audio...
Sonar 8LE -> Platinum infinity, REAPER, Windows 10 pro GA-EP35-DS3L, E7500, 4GB, GTX 1050 Ti, 2x500GB RME Babyface Pro (M-Audio Audiophile Firewire/410, VS-20), Kawai CN43, TD-11, Roland A500S, Akai MPK Mini, Keystation Pro, etc. www.azslow.com - Control Surface Integration Platform for SONAR, ReaCWP, AOSC and other accessibility tools
|
pwalpwal
Max Output Level: -43 dBFS
- Total Posts : 3249
- Joined: 2015/01/17 03:52:50
- Status: offline
Re: OK anyone else getting this kind of ASIO impact on NON-ASIO Windows sound?
2017/03/18 11:07:06
(permalink)
robert_e_bone
Running Sonar Platinum - this issue is present in both 2017-01 and 2017-02.
is it there if you rollback to an earlier version than 2017-01? is it there if you change driver mode (to wdm or wasaspi)? is it there only with ur22 or any device? is it there on both your pcs?
|
John
Forum Host
- Total Posts : 30467
- Joined: 2003/11/06 11:53:17
- Status: offline
Re: OK anyone else getting this kind of ASIO impact on NON-ASIO Windows sound?
2017/03/18 12:03:27
(permalink)
I have found that too big a buffer is just as bad as too small a buffer.
|
soens
Max Output Level: -23.5 dBFS
- Total Posts : 5154
- Joined: 2005/09/16 03:19:55
- Location: Location: Location
- Status: offline
Re: OK anyone else getting this kind of ASIO impact on NON-ASIO Windows sound?
2017/03/19 09:17:26
(permalink)
KPerry
My bad - I'd misread about the interface. Yeah, should be no interaction if they're different devics.
Hah. I was speaking to the OP but my comment probably applies to yours as well... maybe... I dunknow. My interface control has separate buffer controls for streaming, ASIO & WDM but can't speak for other brands. The onboard card shouldn't affect the interface and vice versa. System memory & CPU might though.
|