Dell has an asio driver for the realtek onboard chips. It is from realtek and not a wrapper and works great if you can;t bring your audio interface with your laptop. For monitoring it sound fine. Would not record through it.
If you want it google dell asio driver. Needs a simple trick to install on non dell.

 

The bad news about this: it breaks any virtual midi setup right now (loopmidi, rtpMIDI and so on). They simply don't exist anymore (unless they get updated). Atm there seems to be virtual midi ports installed by windows, but no app can handle or see them.

 

In complete agreement there. But where to? Apple is too expen$ive and proprietary for what you get in return, and as a corporation is just as bad as MS or worse. And Linux - ... well let's just leave it at that...

 

With all this nerdin' where does one find the time to engage the creative part of your brains. Apple too expensive my arse..

 

What kind of latencies do you get with this driver?

I'm asking, because I have downloaded it and installed it on my HP laptop and it doesn't work (no sound and I cannot select hardware I/O in Reaper ASIO settings). But I guess it's because I have the Microslop audio driver installed, not Realtek's proprietary one. I think this ASIO driver may require the presence of Realtek's base audio driver. Could this be the reason?

 

Dawless jamming and capturing everything live on a dedicated unit such as a Tascam DA-6400 but which is expensive and with the need to use I believe a mixing desk as well as outboard gear if not routing through a computer, or a standalone workstation created for just this. There are others at less cost without the track count. It would mean completely changing work flow and not the ability to do the intricate editing and wild modulations that most have become accustomed to....perhaps.

 

In only installed the audio part, no realtek driver. 128 samples worked fine. Does the realtek asio control panel open? Here it worked straight away on a lenove 8th gen intel

 

While there will always be skepticism and aversion to a manufacturer by name, I figure the most useful connecting/interfacing product is always going to be the one that enables all users to get the most accurate and beneficial results when recording and editing in their DAW.

Simply, if it does a better job than everything else out there for everyone, then it does not matter who makes it and good on them for assisting the population at large. Conversely, if it makes it worse, then I suppose whatever crap they get is not unexpected and deserved. I will wait and see if it become PC standard or completely discarded before I start judging anything.

 

Last edited: Apr 3, 2026 at 5:15 PM

If they do it properly, excellent. Otherwise, it will not matter for people that already have good ASIO drivers. So I don't see why it will be something that will affect people here negatively. Therefore, it's probably best to wait and see if they can deliver something useful this time.

 

Because 2020s MS has a very strong track record of breaking seemingly unrelated things for millions of users every time they so much as look at the Windows codebase, let alone when they add new functionality.

Most recent stunt (not even counting the insanity that is W11's slopdates): MIDI services update destroying people's MIDI setups that have been working for decades.

 

You have to have bad experiences with Microsoft's updates yourself before you permanently disable them.

 

What really upsets me here was the fact that the midi updates were put silently under the hood of security patches and no notes about them were given in the changelog. So u think you make your OS more secure with the side effect of broken midi setups. No single information of integrating midi 2.0 and completely removing midi 1.0 - plus this wasn't ONE patch - it went into several security patches so you can't just tell wsupdate to just ignore one.

I guess they thought musicians don't need to be informed about such changes because they are the minority of windows users. Which is BS as the other users maybe never use MIDI at all.

Don't get me wrong here: once Midi 2.0 is fully functional and your soft/hardware can handle it, it's a good change as it makes working with midi way easier and more stable in windows. In theory..

 

Last edited: Apr 6, 2026 at 10:23 AM

Considering that those who use MIDI include those who create for muti-TRILLION dollar industries (movies & gaming) the person in charge of MIDI implementation (the the ONE PERSON...on GITHUB no less) should be a fucking millionaire ordering hundreds on minions around, instead of troubleshooting setups of hobbyists like me. It is pathetic. MS is oblivious.
Unless Hans Zimmer and some others grab MS by the balls, nothing will change.

 

I get your point and you regularly have some well informed and meaningful things to say.
While it is definitely, beyond doubt, easy to point at the most obvious culprits, the deeper I look, the deeper the rabbit hole goes. We, being part of the general population not of the 1%, let them do it in so many ways and we are indirectly responsible for letting it happen. Yeah, I find it hard to admit knowing that I would never want this, but as part of the world we should have stood up and said no a lot earlier.

 

Yeah i saw that github guy while troubleshooting what happened to my rtpMidi setup lately. Although it might be more than one guy working on that (hopefully), i still don't get the point of releasing such an unstable/unfinished implementation of midi 2.0 secretly AND removing midi 1.0 (i think they could co-exist in that midi world of windows, at least for a while). We weren't even able to say no.

 

Considering the mess with Win11 in general. Have you heard about IoT LTSC? It's a bit more like Windows is supposed to be, and so much faster and cleaner. I recon on this forum it's okay to mention it. (Not for private use of course).

 

Been "privately" using it (win 10 LTSC) for a while now.