Hi, this is Wayne again with a topic “Dealing with ASIO4ALL on the Surface Pro 4”.
Hello, I’m right in the middle of doing a getting started, making music guide for your surface pro 4. I ran into a bit of a problem with the a 0 for all driver, so I thought I’d do this very quick video just showing how I got through the problem, what you need to do, how you need to deal with it and how it’s all wonderful! Once you do, I suppose, anyway, so a little while ago, I sent you off to download the a 0 for all driver so that we can get better performance out of the audio drivers in the surface pro 4. Now, what you expect when you install the answer for all driver is lower latency and better performance, and what I’ve actually got is this. So, as you can hear, and see, hopefully terrible latency, or at least latency, that’s no better than it was without the answer. For all driver and this horrible crackle, which we didn’t have before at all, it’s what the heck’s going on well, we have to dig a little bit deeper into the settings to find out what this little bugger was doing.
I’Ve started up reactor which has got a good sort of simple interface when it comes to the audio engine and will let us know and show us what’s going on. Hopefully so there’s our sin. That would just show you how it’s connected together. So here you’ve got the audio media settings. You’Ve got the SEO for all driver loaded there.
I can go to the routing and show you that it’s set to the second output, which is the output for the headphones, which is there, which is what it should be. Then, if we click on this button here the audio config, it will bring up the SEO for all control panel. So in here the answer for all driver has wrapped up the realtek drivers.
The realtek is the onboard sound and you’ve got audio output and you’ve got audio second output. First, one is the speakers. The second one is the headphone output.
Now we have to look behind this plus button to see what’s going on. So I’m connected to the second output at the headphone output at the moment, and that has a number of things under here. The first one says out 2 times: 44 point: 1, 2, 48 kilohertz second one says out 2 times 8 to 192 kilohertz. Now, how did nightly 2 kilohertz? It’S a huge sample rate, the sort of thing used in crazy bonkers, high definition audio. So maybe that has something to do with it.
So if we change it to the forty four point, one like so the latency has gone is back to what it should be. It sounds more like 128 samples that it should be because that’s what the buffer size is set to so whatever is that 8 292 kilohertz setting is that part of the Audio Driver that as you’re always somehow extracted, is not what we’re after it’s no good? It seems to add latency, presumably to allow the CPU time to process audio with that kind of sample rate still GAR. Crackle, though, to get rid of the crackle. What you have to do is disable the driver you’re not using so we’re using the headphones.
So you need to disable the other one because for some reason it can’t cope with having both active at the same time, which I suppose makes some kind of sense. So let’s go back up to the other one up here and uncheck. It check it now at that point reactor crashes, because what we’re messing around with is audio engine, so I’m not at all surprised, so we have to close out of that and get reactor working again. Ok, no sound! So it’s going to our audio settings! It’S still on a zero for all.
The routing is now no longer connected, so if we route it to the second output that I’ll set for the second output there’s our audio with no, that is what it should have been. That is what it should have been now. I understand why Microsoft decided to give it to separate drivers or to seperate endpoints. If you like, it’s because the experience you have through headphones in experience, you have two speakers, it’s very different and it needs to be processed differently.
You know that’s all fair enough, however, for us doing this, it’s a complete pain in the ass and a zero for all, rather than being its usual helpful self, because it pulls out all of the options and different weirdness within the driver. It actually makes itself incredibly and stupidly complex. However, once you’ve set it up once you’ve got it working.
It should just stay like that. So if I close reactor reopen it awesome, will it stop two speakers for me, of course not, but let’s go to bring up the control panel. If I turn that one back on and that one off change the routine back to one set, it make sure it’s set to 44.1. Then there’s my speakers see. That was easy.
There is no trouble there at all piece of cake and to set it back to this feather again, tuck that in let’s turn that off turn that on, let’s turn them on turn that off now we’re coming together. So, to summarize, then, as here for all, is a bit of a bugger, the audio drivers in the surface pro 4 are a bit of a bugger, so we’re kind of in this stupid screwy situation. However, once you’ve got the o0 fuel drivers loaded, the latency is playable and far far better than using the windows drivers by themselves. So is it worth the struggle yeah? Of course it is because this is what we want. We can’t be dealing with unplayable latency. That’S just ridiculous, so you just have to get to grips with the azio for all control panel and make sure your routing is right that your routing to the output that you’re using that you’ve got that one and only that one selected and that it’s set to 44.1, of course, the best solution is to get yourself a bleeding USB audio interface with proper SEO drivers. You can plug that in the side and then have nice, low, latency and lovely sound we’re having to deal with the onboard drivers, but there you go so there’s a quick look at house here for all now. I think we can move on .