giada icon indicating copy to clipboard operation
giada copied to clipboard

Windows: Audio Interface cannot be configured as input device

Open CTBlaze opened this issue 2 years ago • 14 comments

WHatever I do, and in any other host it's gets recognised and works perfectly, my Steinberg/Yamaha UR22MKII cannot be selected as input in Giada 0.20.0, in WIndows 11 Home, latest Updates. I am very frustrated, after hours of issues with MIDI and now the actual interface input, I have not properly used Giada ONCE yet ;( It MIGHT be the case, that the enumeration in Giada for the selection in config is done the wrong way, or shall I say, the listing of outputs and inputs for routing/selection is missing? in any way, the inputs "UR22mkII L" and "UR22mkII R" are not recognized, and not available for selection. ANd yes, this time I did enable the input area through clicking the rectangle, saved, restarted Giada, no change in behaviour if the input field - greyed out and empty. image

In other hosts (here: Guitar Rig 5), it looks more like: image image

CTBlaze avatar Feb 17 '22 23:02 CTBlaze

@CTBlaze can you please paste here the debug output you get on startup? How to enable logging: Main Menu -> Config -> Misc tab -> Debug Messages -> To File.

This will generate a new file alongside the executable containing the debug log messages. Delete the existing one, if any, before launching Giada. Thanks!

gvnnz avatar Feb 18 '22 10:02 gvnnz

OK, just to be sure, as one has to restart Giada with ANY config change (I did start it like 50 times yesterday, phew)

  • open Giada, do the debug config change, restart Giada
  • shall the audio uinterface be connected already before making the debug change, so that with the next startup regarding info can be dumped?

CTBlaze avatar Feb 18 '22 10:02 CTBlaze

  • open Giada, do the debug config change, restart Giada

No need for that. Restart is currently required only for Audio/MIDI device changes

  • shall the audio uinterface be connected already before making the debug change, so that with the next startup regarding info can be dumped?

Not necessarily. Just make sure your interface is connected/enabled before running Giada. In other words: 1) enable debug log 2) connect your interface 3) restart Giada and grab the debug info.

gvnnz avatar Feb 18 '22 10:02 gvnnz

This will generate a new file alongside the executable containing the debug log messages. Delete the existing one, if any, before launching Giada. Thanks!

there you go, there IS an error with the RtApiAsio::getDeviceInfo ... note the MIDI ports of the interface are detected. BTW, the interface works fine in any other host, Reaper, Maschine, Guitar Rig, ...

[init] Giada 0.20.0 [init] Build date: Jan 22 2022 [init] Release build [init] Dependencies: [init] FLTK - 1.3.7 [init] RtAudio - 6.0.0beta1 [init] RtMidi - 3.0.0 [init] Libsamplerate [init] Libsndfile - libsndfile-1.0.31 [init] JSON for modern C++ - 3.9.1 [init] JUCE - 6.1.2 [KA] Compiled RtAudio APIs: 3 ASIO WASAPI DirectSound [MidiMapper::init] scanning midimaps directory '.\midimaps'... [MidiMapper::init] unable to scan midimaps directory! [MidiMapper::read] midiMap not specified, nothing to do [Engine::init] MIDI map read failed! [KA] using system 0x4 [KA] Opening device out=2, in=-1, samplerate=44100 [KA] RtAudio error 1: RtApiAsio::getDeviceInfo: error (Hardware input or output is not present or available.) initializing driver (Maschine MK3). [KA] Can't probe device 0 [KA] 3 device(s) found 0) ins=0 outs=0 duplex=0 isDefaultOut=0 isDefaultIn=0 sampleRates:

  1. ReaRoute ASIO (x64) ins=16 outs=16 duplex=16 isDefaultOut=0 isDefaultIn=0 sampleRates: 4000 5512 8000 9600 11025 16000 22050 32000 44100 48000 88200 96000 176400 192000
  2. Yamaha Steinberg USB ASIO ins=2 outs=2 duplex=2 isDefaultOut=0 isDefaultIn=0 sampleRates: 44100 48000 88200 96000 176400 192000 [KA] RtAudio error 1: RtApiAsio::getDeviceInfo: error (Hardware input or output is not present or available.) initializing driver (Maschine MK3). [mixer::reset] buffers ready - maxFramesInLoop=529200, framesInBuffer=96 [mixer::enable] enabled [KA] Start stream - latency = 222 [KM] Opening output device 'Giada MIDI output', port=0 [KM] Opening input device 'Giada MIDI input', port=1 [KM] Error opening port 1: MidiInWinMM::openPort: the 'portNumber' argument (1) is invalid. [KM] Device 'Giada MIDI output': 2 MIDI ports found
  3. Microsoft GS Wavetable Synth 0
  4. Steinberg UR22mkII -1 1 [KM] Device 'Giada MIDI input': 1 MIDI ports found
  5. Steinberg UR22mkII -1 0 [ui] All windows closed [Engine::shutdown] KernelAudio closed [mixer::disable] disabled [Engine::shutdown] Mixer closed [Engine::shutdown] configuration saved

CTBlaze avatar Feb 18 '22 10:02 CTBlaze

there is some weird auto-reformatting if I just paste the text in here, so also as attachment: giada_audiointerface_no_input_selection_01.log

CTBlaze avatar Feb 18 '22 10:02 CTBlaze

as a reference, here the Reaper audio device config tab: image

CTBlaze avatar Feb 18 '22 11:02 CTBlaze

So why is Giada trying to initialize Maschine MK3 driver, although that's not selected by me? (is there maybe a problem with enumerating the ASIO drivers? since device 0) which must be the Mascine MK3 ASIO does not have a name in your debug info, PLUS I also cannot see it in the config dialog)

CTBlaze avatar Feb 18 '22 11:02 CTBlaze

OK, my assumption was right, Giada had a problem with the Maschine MK3 ASIO driver, nd although I selected the Yamaha/Steinberg in the device drop down, it tried to initialize the Maschine MK3 , which is not present. I uninstalled that Maschine MK3 driver, and NOW the enumeration works nicely, see new log, and screen. Still, the enumeration of devices in Giada may have issues, as you might find from the first log and the behaviour I described, image

giada - Kopie.log

CTBlaze avatar Feb 18 '22 11:02 CTBlaze

Yeah looks like something is wrong with the Maschine MK3 driver, as reported in the logs here:

[KA] RtAudio error 1: RtApiAsio::getDeviceInfo: error (Hardware input or output is not present or available.) initializing driver (Maschine MK3).

So why is Giada trying to initialize Maschine MK3 driver, although that's not selected by me?

This is because all existing drivers/interfaces are scanned on startup, in order to fill the menu of available devices in the Configuration panel.

Unfortunately we have little control over which driver/interface is supported in Giada, since we rely on an external library (RtAudio) for audio I/O. Might be worth reporting the issue to them...

gvnnz avatar Feb 19 '22 08:02 gvnnz

OK, understood, re RtAudio et al. brainstorming: Since in my case the Maschine MK3 driver was scanned, but omitted for the Giada list due to the error (which is correct), still I couldn't use the selected Yamaha/Steinberg ASIO properly, since it's inputs were not recognized or offered int the respective field in Giada. So there might still be a bug in Giada while enumerating the interfaces and addressing them later, when one or more were omitted due to errors, or with filtering the list for erroneous ones. Just a thought. This issue can be closed at your discretion, please.

CTBlaze avatar Feb 19 '22 11:02 CTBlaze

Let's keep this open as a memo for the future. Thanks.

gvnnz avatar Feb 25 '22 13:02 gvnnz

Hi - I seem to have the same issue with a Focusrite Scarlett Solo (2nd gen). I still had some old audio devices and drivers hanging around, cleaned all that up, Giada logs look clean to me, but still all input devices are greyed out.

image

Logs:

`[init] Giada 0.20.1 [init] Build date: Feb 20 2022 [init] Release build [init] Dependencies: [init] FLTK - 1.3.8 [init] RtAudio - 6.0.0beta1 [init] RtMidi - 3.0.0 [init] Libsamplerate [init] Libsndfile - libsndfile-1.0.31 [init] JSON for modern C++ - 3.9.1 [init] JUCE - 6.1.5 [KA] Compiled RtAudio APIs: 3 ASIO WASAPI DirectSound [MidiMapper::init] scanning midimaps directory '.\midimaps'... [MidiMapper::init] unable to scan midimaps directory! [MidiMapper::read] midiMap not specified, nothing to do [Engine::init] MIDI map read failed! [KA] using system 0x3 [KA] Opening device out=1, in=-1, samplerate=44100 [KA] 10 device(s) found 0) Primary Sound Driver ins=0 outs=2 duplex=0 isDefaultOut=1 isDefaultIn=0 sampleRates: 4000 5512 8000 9600 11025 16000 22050 32000 44100 48000 88200 96000 176400 192000

  1. Speakers (2- Focusrite Usb Audio) ins=0 outs=2 duplex=0 isDefaultOut=0 isDefaultIn=0 sampleRates: 4000 5512 8000 9600 11025 16000 22050 32000 44100 48000 88200 96000 176400 192000
  2. Speakers (High Definition Audio Device) ins=0 outs=2 duplex=0 isDefaultOut=0 isDefaultIn=0 sampleRates: 4000 5512 8000 9600 11025 16000 22050 32000 44100 48000 88200 96000 176400 192000
  3. PA329 (NVIDIA High Definition Audio) ins=0 outs=2 duplex=0 isDefaultOut=0 isDefaultIn=0 sampleRates: 4000 5512 8000 9600 11025 16000 22050 32000 44100 48000 88200 96000 176400 192000
  4. Headset Earphone (Jabra EVOLVE LINK MS) ins=0 outs=2 duplex=0 isDefaultOut=0 isDefaultIn=0 sampleRates: 4000 5512 8000 9600 11025 16000 22050 32000 44100 48000 88200 96000 176400 192000
  5. PHL 322E1 (NVIDIA High Definition Audio) ins=0 outs=2 duplex=0 isDefaultOut=0 isDefaultIn=0 sampleRates: 4000 5512 8000 9600 11025 16000 22050 32000 44100 48000 88200 96000 176400 192000
  6. Digital Audio (S/PDIF) (High Definition Audio Device) ins=0 outs=2 duplex=0 isDefaultOut=0 isDefaultIn=0 sampleRates: 4000 5512 8000 9600 11025 16000 22050 32000 44100 48000 88200 96000 176400 192000
  7. Primary Sound Capture Driver ins=2 outs=0 duplex=0 isDefaultOut=0 isDefaultIn=0 sampleRates: 11025 22050 44100 96000
  8. Analogue 1 + 2 (2- Focusrite Usb Audio) ins=2 outs=0 duplex=0 isDefaultOut=0 isDefaultIn=0 sampleRates: 11025 22050 44100 96000
  9. Microfoon van hoofdtelefoon (Jabra EVOLVE LINK MS) ins=2 outs=0 duplex=0 isDefaultOut=0 isDefaultIn=0 sampleRates: 11025 22050 44100 96000 [mixer::reset] buffers ready - maxFramesInLoop=529200, framesInBuffer=1024 [mixer::enable] enabled [KA] Start stream - latency = 0 [ui] All windows closed [Engine::shutdown] KernelAudio closed [mixer::disable] disabled [Engine::shutdown] Mixer closed [Engine::shutdown] configuration saved `

Any other info I can provide?

frijsdijk avatar Mar 22 '22 21:03 frijsdijk

@frijsdijk make sure you have input enabled by enabling the checkbox on the left side of the dropdown menu, then restart Giada and try again. Does it help?

gvnnz avatar Mar 26 '22 08:03 gvnnz

Right .. that did indeed work. Al though I wasn't able to enable it via de interface, I had to set it to 1 in the gaida.conf file ..

frijsdijk avatar Mar 26 '22 11:03 frijsdijk