rs_asio not working on windows 11 with m-audio solo interface

[yvoscia]

it worked wonderfully on windows 10, but, for some reason, now rocksmith crashes to desktop after the pick is shown, not launching any further.

i've reinstalled drivers, etc.

rocksmith does launch with rs_asio disabled, and also via the voicemeeter potato method. however, the latency difference with VP is very noticeable for me.

i can't find any solutions to this specific issue whatsoever.

config and ini files are, of course, set up correctly.

Edit: I forgot to mention that my interface still works very well with my DAW.

Further edit:

Okay, so it is the driver. Windows 11 absolutely requires the latest driver for the M-Audio M-Track Solo (and likely other M-Audio devices), and this newest (1.0.4) driver evidently does not have the necessary 32bit support - I first tried it after reinstalling Windows 10, and it failed. The previous driver (1.0.3) does, however, work very well.

I don't know if there's anything that could perhaps be solved on your end. While I do prefer Windows 10 over Windows 11, it's inevitable that people in my position will have to switch over some day. If such an update to rs_audio is possible, it would be very much appreciated.

Just now, I have also created a support ticket with M-Audio.

[trg6661]

Bro, I have M-Audio M-Track Solo and Duo.
Can you send me a link to the driver you're talking about (1.0.3) ?
On Win 11, the game crashes after configuring RS Asio

он прекрасно работал на Windows 10, но по какой-то причине теперь Rocksmith вылетает на рабочий стол после отображения выбора и больше не запускается.

я переустановил драйверы и т. д.

rocksmith запускается с отключенным rs_asio, а также с помощью метода voicemeeter potato. Однако разница в задержке с VP для меня очень заметна.

я не могу найти никаких решений этой конкретной проблемы.

Файлы config и ini, конечно же, настроены правильно.

Редактировать: Я забыл упомянуть, что мой интерфейс по-прежнему отлично работает с моей DAW.

Дальнейшее редактирование:

Хорошо, значит, это водитель. Для Windows 11 абсолютно необходим последний драйвер для M-Audio M-Track Solo (и, вероятно, других устройств M-Audio), а этот новейший (1.0.4) драйвер, очевидно, не имеет необходимой 32-битной поддержки — я впервые попробовал его после переустановки Windows 10, и это не удалось. Однако предыдущий драйвер (1.0.3) работает очень хорошо.

Я не знаю, есть ли что-то, что можно было бы решить с вашей стороны. Хотя я предпочитаю Windows 10, а не Windows 11, неизбежно, что людям на моем месте когда-нибудь придется перейти на нее. Если такое обновление rs_audio возможно, мы будем очень признательны.

Только что я также создал заявку в службу поддержки M-Audio.

[mdias]

@yvoscia there's nothing I can do in this case.

But I'm finding it odd that you notice high latency with voicemeeter so I'm thinking maybe you didn't have it configured in the most efficient way.
Voicemeeter has a config panel that allows you to directly patch the signal from it's ASIO drivers into your interface's ASIO drivers; there is no mixing involved etc. You'll also need to configure voicemeeter's output to use the ASIO drivers.

This should result in imperceptible latency difference. Although I cannot test it right now, I tested it in the past and was unable to hear any latency difference compared to using the interface driver directly.

[yvoscia]

Voicemeeter is irrelevant to whether your driver works with certain applications. I purchased your product under the expectation that the drivers would facilitate my usage of said product, and, until recently due to a neglectful decision made by M-Audio, they did. Voicemeeter is also not free (unless one wishes to deal with ever-increasing delays for the software to begin functioning). Your customers should not be forced to use third-party software for your product to work, nor be forced to use an operating system that no longer receives updates. Forcing these things upon your customers is a disgraceful business practice. Andrea

…

On Fri, Dec 5, 2025, 1:50 p.m. Micael Dias ***@***.***> wrote: *mdias* left a comment (mdias/rs_asio#577) <#577 (comment)> @yvoscia <https://github.com/yvoscia> there's nothing I can do in this case. But I'm finding it odd that you notice high latency with voicemeeter so I'm thinking maybe you didn't have it configured in the most efficient way. Voicemeeter has a config panel that allows you to directly patch the signal from it's ASIO drivers into your interface's ASIO drivers; there is no mixing involved etc. You'll also need to configure voicemeeter's output to use the ASIO drivers. This should result in imperceptible latency difference. Although I cannot test it right now, I tested it in the past and was unable to hear any latency difference compared to using the interface driver directly. — Reply to this email directly, view it on GitHub <#577 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZI6JENN2WNHHRRFCM4ERQ34AHVYNAVCNFSM6AAAAACKG7U74GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMJYGU3DGNZQGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[mdias]

Hello @yvoscia

I think you misread the previous e-mail, this is RS ASIO, not M-Audio support :)

I'm glad to see you're contacting M-Audio's costumer support; you're not the first one reporting driver issues 👍

[yvoscia]

Oh, shit. My bad. Sorry 😊

…

On Fri, Dec 5, 2025, 5:06 p.m. Micael Dias ***@***.***> wrote: *mdias* left a comment (mdias/rs_asio#577) <#577 (comment)> Hello @yvoscia <https://github.com/yvoscia> I think you misread the previous e-mail, this is RS ASIO, not M-Audio support :) I'm glad to see you're contacting M-Audio's costumer support; you're not the first one reporting driver issues 👍 — Reply to this email directly, view it on GitHub <#577 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZI6JELHD4EMLHAEZ4BSSS34AIMWXAVCNFSM6AAAAACKG7U74GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMMJZGAYDEMZZHE> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[yvoscia]

On windows 11?

…

On Mon, Dec 29, 2025, 5:33 p.m. unfgr ***@***.***> wrote: *unfgr* left a comment (mdias/rs_asio#577) <#577 (comment)> Do not use 1.0.4 Drivers in Windows 11... It will crush the game as soon as it tries to initialize audio. Using 1.0.3 works fine! VBAsioTest32 also crushes with 1.0.4, works fine with 1.0.3 — Reply to this email directly, view it on GitHub <#577 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BZI6JEPT7RZBQSIVGCKTDED4EHB33AVCNFSM6AAAAACKG7U74GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTMOJXHEYTOOBTGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[vyusufcan]

Hi,

This is the link for v1.0.3 driver. https://cdn.inmusicbrands.com/m-audio/Install%20M-Track%20Solo%20and%20Duo%201.0.3.exe It works with win 11

[unfgr]

Oh, shit. My bad.
Sorry 😊
…

On windows 11?
…

yes, sorry deleted my post since you already mentioned the solution to yous first post. Yes Windows 11 Under 32 Bit "driver mode" with version 1.0.4 crush the game. The solution is to use 1.0.3.
Just keep in mind that even 1.0.3 is not perfectly stable.... you will have game crushes every now and then