Input/output/channel help.
-
- KVRer
- 29 posts since 30 Jan, 2022
I'll do my best to ask clear questions. The accurate and precise technical jargon eludes me. So, please overlook that if possible. Any help would be greatly appreciated.
I'm typically using Waveform 13.3 on my Win 10 machine which is permanently offline. When I access inputs and outputs, my only options are as follows...
When I go to my Ubuntu 24 machine, Waveform 13.5 and access inputs and outputs, I get a robust list, including channel assignments, as follows...
Is there any way to get my Win 10 version of Waveform to have the same, expanded options as the Ubuntu version of Waveform?
The next two screens shown the settings as they are...
I'm typically using Waveform 13.3 on my Win 10 machine which is permanently offline. When I access inputs and outputs, my only options are as follows...
When I go to my Ubuntu 24 machine, Waveform 13.5 and access inputs and outputs, I get a robust list, including channel assignments, as follows...
Is there any way to get my Win 10 version of Waveform to have the same, expanded options as the Ubuntu version of Waveform?
The next two screens shown the settings as they are...
You do not have the required permissions to view the files attached to this post.
-
- KVRAF
- 1594 posts since 9 Jan, 2018
This is a Windows driver issue. You'll need to figure out what driver your Linux system sees, and then see if there's a compatible Windows version. Don't be optimistic...Windows audio drivers tend to be more limited.
Also, look to see what your audio interface's manufacturer offers for Windows.
Also, look to see what your audio interface's manufacturer offers for Windows.
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
-
- KVRer
- Topic Starter
- 29 posts since 30 Jan, 2022
Thank you for answering. I'll look into it.Watchful wrote: Sun Apr 19, 2026 6:32 pm This is a Windows driver issue. You'll need to figure out what driver your Linux system sees, and then see if there's a compatible Windows version. Don't be optimistic...Windows audio drivers tend to be more limited.
Also, look to see what your audio interface's manufacturer offers for Windows.
I'm an idiot. I see that I posted a Waveform question in the wrong forum.
-
- KVRAF
- 1594 posts since 9 Jan, 2018
No problem. Good news, though: there are quite a few Linux-based Waveform users there. I'm hopeful they can help you!
Spotify, Apple Music, YouTube, and even Deezer, whatever the hell Deezer is.
More fun at Twitter @watchfulactual
More fun at Twitter @watchfulactual
-
Karbon L. Forms Karbon L. Forms https://www.kvraudio.com/forum/memberlist.php?mode=viewprofile&u=29033
- KVRian
- 1411 posts since 10 Jun, 2004 from Inverness, Scotland
M-Audio M-Track Solo has 2 inputs. Windows shows 2 inputs. All good.
Not sure WTF going on with Linux. Assuming same interface used? You're not getting 64 inputs from the Solo any time soon, that's for sure. Some Linux sound system bollocks maybe? Jack? Some kind of software patchbay type carry on?
Not sure WTF going on with Linux. Assuming same interface used? You're not getting 64 inputs from the Solo any time soon, that's for sure. Some Linux sound system bollocks maybe? Jack? Some kind of software patchbay type carry on?
.................................
"Hell is other People" J.P.Sartre
.................................
"Hell is other People" J.P.Sartre
.................................
-
- KVRist
- 374 posts since 18 Nov, 2023
On Linux, using the JACK protocol shows you the correct number of indeed present input and output channels. My experience refers to pipewire-jack usage. This will equal what you correctly see in Windows.
Instead, using ALSA seems to show the amount of channels which the ALSA protocol can manage (64 channels). But this might be much more channels than actually supported by your audio interface device. So, what you see listed under ALSA is not the most user friendly. But now that you are aware of it, make use of the possibility to deactivate on the Settings page all those channels which are anyway not present and only a management artifact. This is one of the reasons why that option there exists. Then, when working with Waveform in a project, in an Edit, you will there only be offered the channels which it makes sense to become offered, which you might indeed want to work with.
For curiosity, is ALSA usage in other DAWs showing a reduced number of channels, only the ones which the audio interface indeed supports?
Instead, using ALSA seems to show the amount of channels which the ALSA protocol can manage (64 channels). But this might be much more channels than actually supported by your audio interface device. So, what you see listed under ALSA is not the most user friendly. But now that you are aware of it, make use of the possibility to deactivate on the Settings page all those channels which are anyway not present and only a management artifact. This is one of the reasons why that option there exists. Then, when working with Waveform in a project, in an Edit, you will there only be offered the channels which it makes sense to become offered, which you might indeed want to work with.
For curiosity, is ALSA usage in other DAWs showing a reduced number of channels, only the ones which the audio interface indeed supports?
Classical guitar --> Line Audio CM4 @ SSL12 --> KDE-Plasma @ Debian-Linux --> Waveform PRO 13.5
- KVRAF
- 4888 posts since 3 Jan, 2003 from Vancouver
Did this thread get moved here recently from somewhere else? It looks like this question was also asked here already.
viewtopic.php?t=629497
viewtopic.php?t=629497
Surely there must be consensus by now...
