MME, Windows DirectSound or Wasapi
so im using Audacity and was wondering wich recording device/system I should use for the best audio quality? There is MME, Windows DirectSound and Wasapi.Im on a Windows 7 laptop and I tried them all and I dont see much difference among the three.By default,settings were on MME.
thank you
windows-7 audio recording audacity
add a comment |
so im using Audacity and was wondering wich recording device/system I should use for the best audio quality? There is MME, Windows DirectSound and Wasapi.Im on a Windows 7 laptop and I tried them all and I dont see much difference among the three.By default,settings were on MME.
thank you
windows-7 audio recording audacity
add a comment |
so im using Audacity and was wondering wich recording device/system I should use for the best audio quality? There is MME, Windows DirectSound and Wasapi.Im on a Windows 7 laptop and I tried them all and I dont see much difference among the three.By default,settings were on MME.
thank you
windows-7 audio recording audacity
so im using Audacity and was wondering wich recording device/system I should use for the best audio quality? There is MME, Windows DirectSound and Wasapi.Im on a Windows 7 laptop and I tried them all and I dont see much difference among the three.By default,settings were on MME.
thank you
windows-7 audio recording audacity
windows-7 audio recording audacity
asked Mar 29 '15 at 22:06
Phil_oneilPhil_oneil
39349
39349
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
MME is often the default selection since it is supported by most Windows OSes (MME was released in 1991). Between DirectSound and WASAPI there is not a big difference, as DirectSound is basically just a DirectX-related Interface to the Windows Audio Session API (WASAPI) underneath. WASAPI features the lowest latency of all (by design) and therefore should be preferred for recording (especially when it comes to multi-track).
Interesting, in Savihost I was able to get near zero latency (60 samples buffer at 48 kHz) with MME and nothing close to it with DirectSound. DirectSound required way bigger buffer to achieve stability.
– Vlastimil Ovčáčík
Jan 20 '16 at 16:23
I'd add that if one's not doing a real-time streaming/performing then there's no much difference which API to use.
– montonero
Jan 18 at 9:28
add a comment |
According to Audacity:
"MME: This is the Audacity default and the most compatible with all audio devices.
Windows DirectSound: This is more recent than MME with potentially less latency.
Windows WASAPI: This host is the most recent Windows interface, that Audacity supports, between applications (such as Audacity) and the soundcard driver. WASAPI was first officially released in 2007 in Windows Vista. WASAPI is particularly useful for "loopback" devices for recording computer playback. 24-bit recording devices are supported. Playback is emulated using this host. As a result, the playback slider in Mixer Toolbar will only scale the system playback slider's current level up or down rather than directly manipulating that system slider."
Everything between the quotes came directly from Audacity. Seems they had a lot to say about WASAPI.
add a comment |
MME (Multimedia Events, aka WinMM [Windows Multimedia APIs]) should be an old interface that exists since as early as Windows 95 (or even earlier). WASAPI comes with the new audio stack on Windows Vista and higher. As mentioned by Jan in his answer, the WASAPI provides the minimal latency. On my computer, sending audio data to DirectSound seem to have a built-in buffer, so that playback from Audacity is more stable on DirectSound than on WASAPI. But for recording, Audacity using WASAPI captures the audio perfectly.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f895525%2fmme-windows-directsound-or-wasapi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
MME is often the default selection since it is supported by most Windows OSes (MME was released in 1991). Between DirectSound and WASAPI there is not a big difference, as DirectSound is basically just a DirectX-related Interface to the Windows Audio Session API (WASAPI) underneath. WASAPI features the lowest latency of all (by design) and therefore should be preferred for recording (especially when it comes to multi-track).
Interesting, in Savihost I was able to get near zero latency (60 samples buffer at 48 kHz) with MME and nothing close to it with DirectSound. DirectSound required way bigger buffer to achieve stability.
– Vlastimil Ovčáčík
Jan 20 '16 at 16:23
I'd add that if one's not doing a real-time streaming/performing then there's no much difference which API to use.
– montonero
Jan 18 at 9:28
add a comment |
MME is often the default selection since it is supported by most Windows OSes (MME was released in 1991). Between DirectSound and WASAPI there is not a big difference, as DirectSound is basically just a DirectX-related Interface to the Windows Audio Session API (WASAPI) underneath. WASAPI features the lowest latency of all (by design) and therefore should be preferred for recording (especially when it comes to multi-track).
Interesting, in Savihost I was able to get near zero latency (60 samples buffer at 48 kHz) with MME and nothing close to it with DirectSound. DirectSound required way bigger buffer to achieve stability.
– Vlastimil Ovčáčík
Jan 20 '16 at 16:23
I'd add that if one's not doing a real-time streaming/performing then there's no much difference which API to use.
– montonero
Jan 18 at 9:28
add a comment |
MME is often the default selection since it is supported by most Windows OSes (MME was released in 1991). Between DirectSound and WASAPI there is not a big difference, as DirectSound is basically just a DirectX-related Interface to the Windows Audio Session API (WASAPI) underneath. WASAPI features the lowest latency of all (by design) and therefore should be preferred for recording (especially when it comes to multi-track).
MME is often the default selection since it is supported by most Windows OSes (MME was released in 1991). Between DirectSound and WASAPI there is not a big difference, as DirectSound is basically just a DirectX-related Interface to the Windows Audio Session API (WASAPI) underneath. WASAPI features the lowest latency of all (by design) and therefore should be preferred for recording (especially when it comes to multi-track).
answered Nov 9 '15 at 11:01
Jan WJan W
765
765
Interesting, in Savihost I was able to get near zero latency (60 samples buffer at 48 kHz) with MME and nothing close to it with DirectSound. DirectSound required way bigger buffer to achieve stability.
– Vlastimil Ovčáčík
Jan 20 '16 at 16:23
I'd add that if one's not doing a real-time streaming/performing then there's no much difference which API to use.
– montonero
Jan 18 at 9:28
add a comment |
Interesting, in Savihost I was able to get near zero latency (60 samples buffer at 48 kHz) with MME and nothing close to it with DirectSound. DirectSound required way bigger buffer to achieve stability.
– Vlastimil Ovčáčík
Jan 20 '16 at 16:23
I'd add that if one's not doing a real-time streaming/performing then there's no much difference which API to use.
– montonero
Jan 18 at 9:28
Interesting, in Savihost I was able to get near zero latency (60 samples buffer at 48 kHz) with MME and nothing close to it with DirectSound. DirectSound required way bigger buffer to achieve stability.
– Vlastimil Ovčáčík
Jan 20 '16 at 16:23
Interesting, in Savihost I was able to get near zero latency (60 samples buffer at 48 kHz) with MME and nothing close to it with DirectSound. DirectSound required way bigger buffer to achieve stability.
– Vlastimil Ovčáčík
Jan 20 '16 at 16:23
I'd add that if one's not doing a real-time streaming/performing then there's no much difference which API to use.
– montonero
Jan 18 at 9:28
I'd add that if one's not doing a real-time streaming/performing then there's no much difference which API to use.
– montonero
Jan 18 at 9:28
add a comment |
According to Audacity:
"MME: This is the Audacity default and the most compatible with all audio devices.
Windows DirectSound: This is more recent than MME with potentially less latency.
Windows WASAPI: This host is the most recent Windows interface, that Audacity supports, between applications (such as Audacity) and the soundcard driver. WASAPI was first officially released in 2007 in Windows Vista. WASAPI is particularly useful for "loopback" devices for recording computer playback. 24-bit recording devices are supported. Playback is emulated using this host. As a result, the playback slider in Mixer Toolbar will only scale the system playback slider's current level up or down rather than directly manipulating that system slider."
Everything between the quotes came directly from Audacity. Seems they had a lot to say about WASAPI.
add a comment |
According to Audacity:
"MME: This is the Audacity default and the most compatible with all audio devices.
Windows DirectSound: This is more recent than MME with potentially less latency.
Windows WASAPI: This host is the most recent Windows interface, that Audacity supports, between applications (such as Audacity) and the soundcard driver. WASAPI was first officially released in 2007 in Windows Vista. WASAPI is particularly useful for "loopback" devices for recording computer playback. 24-bit recording devices are supported. Playback is emulated using this host. As a result, the playback slider in Mixer Toolbar will only scale the system playback slider's current level up or down rather than directly manipulating that system slider."
Everything between the quotes came directly from Audacity. Seems they had a lot to say about WASAPI.
add a comment |
According to Audacity:
"MME: This is the Audacity default and the most compatible with all audio devices.
Windows DirectSound: This is more recent than MME with potentially less latency.
Windows WASAPI: This host is the most recent Windows interface, that Audacity supports, between applications (such as Audacity) and the soundcard driver. WASAPI was first officially released in 2007 in Windows Vista. WASAPI is particularly useful for "loopback" devices for recording computer playback. 24-bit recording devices are supported. Playback is emulated using this host. As a result, the playback slider in Mixer Toolbar will only scale the system playback slider's current level up or down rather than directly manipulating that system slider."
Everything between the quotes came directly from Audacity. Seems they had a lot to say about WASAPI.
According to Audacity:
"MME: This is the Audacity default and the most compatible with all audio devices.
Windows DirectSound: This is more recent than MME with potentially less latency.
Windows WASAPI: This host is the most recent Windows interface, that Audacity supports, between applications (such as Audacity) and the soundcard driver. WASAPI was first officially released in 2007 in Windows Vista. WASAPI is particularly useful for "loopback" devices for recording computer playback. 24-bit recording devices are supported. Playback is emulated using this host. As a result, the playback slider in Mixer Toolbar will only scale the system playback slider's current level up or down rather than directly manipulating that system slider."
Everything between the quotes came directly from Audacity. Seems they had a lot to say about WASAPI.
answered Apr 21 '18 at 5:05
EdRiEdRi
11
11
add a comment |
add a comment |
MME (Multimedia Events, aka WinMM [Windows Multimedia APIs]) should be an old interface that exists since as early as Windows 95 (or even earlier). WASAPI comes with the new audio stack on Windows Vista and higher. As mentioned by Jan in his answer, the WASAPI provides the minimal latency. On my computer, sending audio data to DirectSound seem to have a built-in buffer, so that playback from Audacity is more stable on DirectSound than on WASAPI. But for recording, Audacity using WASAPI captures the audio perfectly.
add a comment |
MME (Multimedia Events, aka WinMM [Windows Multimedia APIs]) should be an old interface that exists since as early as Windows 95 (or even earlier). WASAPI comes with the new audio stack on Windows Vista and higher. As mentioned by Jan in his answer, the WASAPI provides the minimal latency. On my computer, sending audio data to DirectSound seem to have a built-in buffer, so that playback from Audacity is more stable on DirectSound than on WASAPI. But for recording, Audacity using WASAPI captures the audio perfectly.
add a comment |
MME (Multimedia Events, aka WinMM [Windows Multimedia APIs]) should be an old interface that exists since as early as Windows 95 (or even earlier). WASAPI comes with the new audio stack on Windows Vista and higher. As mentioned by Jan in his answer, the WASAPI provides the minimal latency. On my computer, sending audio data to DirectSound seem to have a built-in buffer, so that playback from Audacity is more stable on DirectSound than on WASAPI. But for recording, Audacity using WASAPI captures the audio perfectly.
MME (Multimedia Events, aka WinMM [Windows Multimedia APIs]) should be an old interface that exists since as early as Windows 95 (or even earlier). WASAPI comes with the new audio stack on Windows Vista and higher. As mentioned by Jan in his answer, the WASAPI provides the minimal latency. On my computer, sending audio data to DirectSound seem to have a built-in buffer, so that playback from Audacity is more stable on DirectSound than on WASAPI. But for recording, Audacity using WASAPI captures the audio perfectly.
answered Jan 18 at 9:17
robbie fanrobbie fan
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f895525%2fmme-windows-directsound-or-wasapi%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown