# Should the JUCE team buy a Steinberg UR audio interface?

**URL:** <https://forum.juce.com/t/should-the-juce-team-buy-a-steinberg-ur-audio-interface/41650>\
**Category:** Windows\
**Created:** [September 7, 2020, 4:56pm UTC](https://forum.juce.com/t/should-the-juce-team-buy-a-steinberg-ur-audio-interface/41650 "2020-09-07T16:56:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jpo](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/jpo/32/503_2.png) [@jpo](https://forum.juce.com/u/jpo)\
**Post date:** [September 7, 2020, 4:56pm UTC](https://forum.juce.com/t/should-the-juce-team-buy-a-steinberg-ur-audio-interface/41650/1 "2020-09-07T16:56:01Z")

</div>

It seems there are a lot of issues with these soundcards and JUCE [1], with the ASIO.

I spent the afternoon trying to understand what is going on with the juce\_win32\_ASIO.cpp file and these soundcards but I just can’t understand the flow of events. One of these two is seriously broken, there are semi-random error when launching the juce AudioPluginHost (“create buffer 2 - Invalid Mode”), and then when changing the sample rate from 44100 to 96000 in the juce AudioDeviceSettingsPanel of the AudioPluginHost, most of the time it enters an infinite loop of kAsioResetRequest messages.

Since both JUCE and Yamaha are well established brands I would expect that combination to work a bit better than it does now.

[1] [https://forum.juce.com/t/yamaha-steinberg-usb-asio-problems-since-july-commit/](https://forum.juce.com/t/yamaha-steinberg-usb-asio-problems-since-july-commit/)

---

<div class="post-metadata">

**Author:** ![stian](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/stian/32/17_2.png) [@stian](https://forum.juce.com/u/stian)\
**Post date:** [February 24, 2021, 1:38pm UTC](https://forum.juce.com/t/should-the-juce-team-buy-a-steinberg-ur-audio-interface/41650/2 "2021-02-24T13:38:17Z")

</div>

We are getting these reports, too. Did you find a solution to the issues?

---

<div class="post-metadata">

**Author:** ![jpo](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/jpo/32/503_2.png) [@jpo](https://forum.juce.com/u/jpo)\
**Post date:** [February 24, 2021, 1:45pm UTC](https://forum.juce.com/t/should-the-juce-team-buy-a-steinberg-ur-audio-interface/41650/3 "2021-02-24T13:45:28Z")

</div>

Nope, I’m just telling people to try with asio4all instead of the yamaha asio driver…

I was thinking of reviving the juce portaudio wrapper ( [Portaudio device](https://forum.juce.com/t/portaudio-device/8465) ) and maybe use it instead of juce for ASIO device type.

---

<div class="post-metadata">

**Author:** ![stian](https://sea2.discourse-cdn.com/flex026/user_avatar/forum.juce.com/stian/32/17_2.png) [@stian](https://forum.juce.com/u/stian)\
**Post date:** [February 25, 2021, 7:34am UTC](https://forum.juce.com/t/should-the-juce-team-buy-a-steinberg-ur-audio-interface/41650/4 "2021-02-25T07:34:56Z")

</div>

Thanks! I guess we’ll just have to do the same and advice our users to use asio4all. Hopefully, there’s a way to circumvent the issues with Steinberg’s ASIO drivers in JUCE.