View Issue Details

IDProjectCategoryView StatusLast Update
0006507ardourbugspublic2020-04-19 20:17
Reporterdayvyg Assigned Tox42  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionno change required 
Product Version4.1 
Summary0006507: Ardour does not recognize my audio interface
DescriptionWhen starting the latest version of Ardour (v4.1-622 2015-08-12) I have 2 options for my interface - dummy and PortAudio. When I choose PortAudio the Driver, Input Device, and Output Device are all greyed out and not available.

Using Windows 10 x64. Audio interface is a Steinberg UR824 - ASIO driver.
TagsNo tags attached.

Relationships

related to 0006495 assignedtimbyr Windows Portaudio Backend 

Activities

x42

2015-08-12 18:21

administrator   ~0017013

There was a bug/issue with driver-selection (since 4.1-601 fixed in v4.1-623).

Meanwhile, it may (or may not) help to change the portaudio driver from "ASIO" to "WASAPI" and back.

x42

2015-08-12 18:26

administrator   ~0017014

Last edited: 2015-08-12 18:27

PS. to elaborate: the /old/ ASIO "audio-system" is also just using Portaudio ( http://www.portaudio.com/ ).

It has been removed in favor of a new "audio system" that also uses Portaudio but exposes all of portaudio's drivers (not only ASIO).

x42

2015-08-13 04:30

administrator   ~0017015

aah windows 10 our new friend :)

Looks like adding WASAPI support to the portaudio library (which is used by both: the old ASIO and the new PA/ASIO backend) broke all audio-i/o on Windows 10. A similar issue: http://forum.audacityteam.org/viewtopic.php?p=282912#p282912

Could you please try to replace libportaudio-2.dll in C:\Program Files\Ardour4\bin
with the one found at http://robin.linuxaudio.org/tmp/portaudio-win.zip ?
in your case: 64bit/without_wasapi/libportaudio-2.dll

dayvyg

2015-08-13 12:44

reporter   ~0017016

Okay, I'll give that a try when I get a chance. I'm assuming this dll will work with the 1508 release of Mixbus as well?

Yes, somebody had to open the Windows 10 can of worms. Might as well be me.:)

Thanks.

dayvyg

2015-08-13 16:02

reporter   ~0017017

Yup, the dll without wasapi support resolved the issue. Also worked for Mixbus.

Thanks.

BenLoftis

2015-08-13 16:20

developer   ~0017018

Just as an additional data point:

Current release works fine on win10 for me. I tested Presonus Audiobox (ASIO and WASAPI), Focusrite 2i2 (ASIO and WASAPI), internal Realtek (using ASIO/ASIO4ALL and MME). Can test many others if needed, but we don't have Steinberg UR824.

So this may be a conflict with the specific WASAPI drivers or something similar.

dayvyg

2015-08-13 16:43

reporter   ~0017019

Steinberg has said that there are issues with the UR series and WDM on Windows 10 but made no mention of Wasapi but it definitely appears to be an issue.

How are the startup times (from first launching MB to a functioning session open) on these devices you tested? It takes close to 2 minutes for me with the latest build (1508) on Windows 10. Just wondering if this is also specific to my interface and/or Windows 10.

Thanks.

BenLoftis

2015-08-13 16:49

developer   ~0017020

Startup is basically instant ( same as Mac or Linux ) here on win10 with the listed interfaces.

x42

2015-08-13 16:57

administrator   ~0017021

Thanks for testing the .dll.

It's good to know that there is a work-around. The real problem seems to be specific to some device-drivers (e.g Steinberg UR) on Windows10. So it seems there is nothing we can do on our side.

One option is to make an installer-option to allow a user to select which PA .dll to install.


Startup times: here on Win 7 it takes less than 5 seconds

Scanning the available samplerates is what can take a long time and the new Portaudio backend no longer does that initially (it detects available samplerates only when selecting the device) but that's fast here too (onboard soundcard, PreSonus 1818VSL and Focusrite 18i6).

Does it also take 2 min if you disconnect the UR when starting?

dayvyg

2015-08-13 17:14

reporter   ~0017022

It takes just under 2 minutes from the time I launch MB to initialize the interface and open a session with only a few plugins. The longest time is spent initializing the interface.

If I start a new session and PortAudio is set to use MME, it's fast. As soon as I select ASIO from the drop down it hangs for quite a while before it discovers and initializes my interface. Looks like it's particular to this interface or probably the whole UR series. Here's hoping Steinberg releases a new driver soon.

Just to add another angle to it. Reaper takes about 5 seconds to initialize the same interface and open a session with many plugins (same Windows 10 PC). Not trying to knock you guys, just thinking out loud and wondering what's different about their method.

Anyway, as always, thanks for the fast response. Truly great support. Bravo.

x42

2015-08-13 18:10

administrator   ~0017024

Reaper does not validate (test-run) the available sample-rates.

Trying them is the only reliable way to detect available SR, depending on the soundcard in question changing SR can take some time.

x42

2015-08-13 18:32

administrator   ~0017025

New installer (Ardour 4.2.2) does have an option to select the portaudio .dll.

You can opt-out of using the WASAPI version.
It's not a real solution but that will make things work until the real issue is resolved.

dayvyg

2015-08-13 19:22

reporter   ~0017026

"Reaper does not validate (test-run) the available sample-rates."

That would explain it.

Thanks for the installer option.

x42

2015-08-14 12:12

administrator   ~0017032

Closing this issue because It's not an Ardour bug.

Until the issue gets fixed at Microsoft/Steinberg/?? for Windows 10, there is now the Ardour-installer option for an old libportaudio.

Long load times: that's part of issue 0006495

system

2020-04-19 20:17

developer   ~0023504

Issue has been closed automatically, by Trigger Close Plugin.
Feel free to re-open with additional information if you think the issue is not resolved.

Issue History

Date Modified Username Field Change
2015-08-12 17:35 dayvyg New Issue
2015-08-12 18:21 x42 Note Added: 0017013
2015-08-12 18:22 x42 Relationship added related to 0006495
2015-08-12 18:26 x42 Note Added: 0017014
2015-08-12 18:27 x42 Note Edited: 0017014
2015-08-13 04:30 x42 Note Added: 0017015
2015-08-13 12:44 dayvyg Note Added: 0017016
2015-08-13 16:02 dayvyg Note Added: 0017017
2015-08-13 16:20 BenLoftis Note Added: 0017018
2015-08-13 16:43 dayvyg Note Added: 0017019
2015-08-13 16:49 BenLoftis Note Added: 0017020
2015-08-13 16:57 x42 Note Added: 0017021
2015-08-13 17:14 dayvyg Note Added: 0017022
2015-08-13 18:10 x42 Note Added: 0017024
2015-08-13 18:32 x42 Note Added: 0017025
2015-08-13 19:22 dayvyg Note Added: 0017026
2015-08-14 12:12 x42 Note Added: 0017032
2015-08-14 12:12 x42 Status new => resolved
2015-08-14 12:12 x42 Resolution open => no change required
2015-08-14 12:12 x42 Assigned To => x42
2020-04-19 20:17 system Note Added: 0023504
2020-04-19 20:17 system Status resolved => closed