xxx does not have any lines supporting xxx

richard612

Registered
Thread Starter
Joined
Oct 27, 2024
Posts
4
Getting this error when trying to choose EXCL as my input:


1730080992618.png


My MOTU M2 offers only 24-bit selections (from 44.1 to 192) in the Windows dialogs; no 16 or 32-bit.

At start-up csjsound-lib.log logs roughly 4000 lines similar to:
02:01:35.4589807 DEBUG [src\wasapi_impl.rs:248] Capture device Loopback (MOTU M Series) does not support format WaveFormat { nAvgBytesPerSec: 768000, cbSize: 22, nBlockAlign: 16, wBitsPerSample: 32, nSamplesPerSec: 48000, wFormatTag: 65534, wValidBitsPerSample: 32, SubFormat: 00000001-0000-0010-8000-00AA00389B71, nChannel: 4, dwChannelMask: 0 }:

Not sure if this is just normal device query procedure? A few of the lines do indicate success.

...It rolls through my various sound devices and ends with success. Then I change the input to EXCL:

02:01:44.7796035 DEBUG [src\lib.rs:238] Java_com_cleansine_sound_provider_SimpleMixer_nOpen [AWT-EventQueue-0]: Opening Capture device 02:01:44.7828221 DEBUG [src\wasapi_impl.rs:883] Found device In 1-2 (MOTU M Series) 02:01:44.783079 DEBUG [src\wasapi_impl.rs:309] Opening Capture device In 1-2 (MOTU M Series): rate: 48000, validbits: 24, frame_bytes: 8, channels: 2, buffer_bytes: 192000 02:01:44.7836638 DEBUG [src\wasapi_impl.rs:312] Capture: default period 106667, min period 30000 02:01:44.7836698 DEBUG [src\wasapi_impl.rs:334] Capture: align_segment_bytes: 128, align_segment_ns00: 26666.666666666668, align_segments 11 in approx_dev_period 300000 02:01:44.7836706 DEBUG [src\wasapi_impl.rs:341] Capture: Using device period 293333 02:01:44.7836731 DEBUG [src\wasapi_impl.rs:368] CAPT: Preallocating 34 chunks 02:01:44.7856233 DEBUG [src\wasapi_impl.rs:883] Found device In 1-2 (MOTU M Series) 02:01:44.7860012 DEBUG [src\wasapi_impl.rs:239] Capture device In 1-2 (MOTU M Series) supports format WaveFormat { nAvgBytesPerSec: 384000, cbSize: 22, nBlockAlign: 8, wBitsPerSample: 32, nSamplesPerSec: 48000, wFormatTag: 65534, wValidBitsPerSample: 24, SubFormat: 00000001-0000-0010-8000-00AA00389B71, nChannel: 2, dwChannelMask: 3 } 02:01:44.786007 DEBUG [src\wasapi_impl.rs:868] Opening device In 1-2 (MOTU M Series): supports format WaveFormat { nAvgBytesPerSec: 384000, cbSize: 22, nBlockAlign: 8, wBitsPerSample: 32, nSamplesPerSec: 48000, wFormatTag: 65534, wValidBitsPerSample: 24, SubFormat: 00000001-0000-0010-8000-00AA00389B71, nChannel: 2, dwChannelMask: 3 } 02:01:44.7860105 DEBUG [src\wasapi_impl.rs:837] Opening Capture device In 1-2 (MOTU M Series): will use format WaveFormat { nAvgBytesPerSec: 384000, cbSize: 22, nBlockAlign: 8, wBitsPerSample: 32, nSamplesPerSec: 48000, wFormatTag: 65534, wValidBitsPerSample: 24, SubFormat: 00000001-0000-0010-8000-00AA00389B71, nChannel: 2, dwChannelMask: 3 } 02:01:44.7930584 ERROR [src\wasapi_impl.rs:854] Calling method audio_client.initialize_client failed: Error { [B]code: 0x8007000E, message: Not enough memory resources are available to complete this operation[/B]. } 02:01:44.7931277 ERROR [src\lib.rs:245] Java_com_cleansine_sound_provider_SimpleMixer_nOpen [AWT-EventQueue-0]: open_dev failed: DeviceError { desc: "PB: error: Not enough memory resources are available to complete this operation." }

-Xmx4096m didn't help. Any suggestions for troubleshooting?
 

phofman

Member
Joined
Jun 26, 2019
Posts
180
Not sure if this is just normal device query procedure? A few of the lines do indicate success.
Yes, that procedure checks many format params combinations to find which are supported for every audio device at REW start.

My MOTU M2 offers only 24-bit selections (from 44.1 to 192) in the Windows dialogs; no 16 or 32-bit.
IIUC the actual HW supports only 32bits both on playback and capture https://community.volumio.com/t/volumio-3-on-odroid-n2-with-motu-m2-no-audio/59584 . But no idea what the proprietary Motu driver does internally.

02:01:44.7930584 ERROR [src\wasapi_impl.rs:854] Calling method audio_client.initialize_client failed: Error { code: 0x8007000E, message: Not enough memory resources are available to complete this operation. }
That error is returned by the wasapi layer while calling https://learn.microsoft.com/en-us/w...client/nf-audioclient-iaudioclient-initialize . While it complains about lack of memory (highly unlikely), a google search suggests it may also mean that the device is not available. Do you have exclusive mode allowed and prioritized in the windows device setup?
 

linuxonly

Member
Joined
Jul 27, 2024
Posts
112
More  
Preamp, Processor or Receiver
Logitech Z906
DAC
AMD FCH Azalia
Computer Audio
SPDIF output with alsa, pipewire, wireplumber on Fedora 40
Streaming Equipment
Kodi
Front Height Speakers
33 in
Middle Height Speakers
30 in
Rear Height Speakers
57 in
Video Display Device
X11/VGA + X11/DVI
Getting this error when trying to choose EXCL as my input:
This happens to me on windows every time I want to use the EXCL:Speaker which is already used by CamillaDSP as playback device in exclusive mode. Killing CDSP gives REW access to it.
 

richard612

Registered
Thread Starter
Joined
Oct 27, 2024
Posts
4
This happens to me on windows every time I want to use the EXCL:Speaker which is already used by CamillaDSP as playback device in exclusive mode. Killing CDSP gives REW access to it.

I do have EqAPO installed but it's bound only to an output device; not the Motu.

1730216854004.png
 
Top Bottom