-
Notifications
You must be signed in to change notification settings - Fork 233
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Motu 828 (28 x 32) support #415
Comments
Show And show the channel map (separate for the playback and capture direction). It means which channel is router to which input/output connector on your device. |
output of: amixer -c 0 info:
|
Channel Map: Output / Playback #(On the back of the device, these are labelled "MAIN OUT (A)" and are XLR connectors): #(On the back of the device, these are labelled "(B)" in the "LINE OUT" section and are balanced 1/4" TRS connectors): #(On the back of the device, these are labelled "LINE OUT" and are balanced 1/4" TRS connectors): #(On the front of the device, these are 1/4" TRS connectors): AUX12 = Headphones 2 (L) #(On the back of the device, this is a single RCA connector, labelled "S/PDIF OUT"): #(On the back of the device, these are optical connectors. AUX24 = Optical B 1 (L) |
Channel Map: Input / Capture #(On the front of the device, these are Combo (XLR + 1/4" TRS) connectors #(On the back of the device, these are labelled "LINE IN" and are balanced 1/4" TRS connectors: #(This is an internal loopback, with no physical inputs) #(On the back of the device, this is a single RCA connector, labelled "S/PDIF IN" #(On the back of the device, these are optical connectors. AUX22 = Optical B 1 (L) |
For what it's worth, here is my attempt to create a UCM configuration. This is not ideally how I would like to set up the card; but it is the default setup and how the device actually behaves (and should behave) out of the box. I personally want to remap output channels to support surround sound mapping; but I'll attempt to do that after I get this working. `LibraryConfig.pcm.Config {
} #Physical Device Outputs: SectionDevice."Line_Out_3-4" { SectionDevice."Line_Out_5-6" { SectionDevice."Line_Out_7-8" { SectionDevice."Line_Out_9-10" { SectionDevice."Headphones_Out_1" { SectionDevice."Headphones_Out_2" { SectionDevice."SPDIF_Out_1" { SectionDevice."SPDIF_Out_2" { SectionDevice."SPDIF_Out_3" { } #Physical Device Inputs SectionDevice."Mic_In_2" { SectionDevice."Line_In_3-4" { SectionDevice."Line_In_5-6" { SectionDevice."Line_In_7-8" { SectionDevice."Line_In_9-10" { SectionDevice."Capture Music" { SectionDevice."SPDIF_In_1" { SectionDevice."SPDIF_In_2" { SectionDevice."SPDIF_In_3" { To summarize what I did (at least this is my understanding):
This has gotten me the furthest; but it seems to fail and then fallback to 2 channel duplex in the pro audio profile. I'm guessing this could be due to xrun or timing? Maybe I have to define a buffer or period? Or maybe I'm missing something else? Here is the output of the command "spa-acp-tool -c 0 -vvvv info":
Any help would be greatly appreciated. |
It's better to use (extend for more channels) the SplitPCM / SplitPCMDevice macros in ucm2/common/pcm/split.conf and use those macros to describe devices. I would start with mono / stereo I/O at first and then add multichannel configuration. The mentioned macros can already override channel mapping (chmap). Create a PR, so we can discuss your changes directly. |
I originally alternatively attempted to use the splitpcm macro as well, based on the Motu M6 configuration file; but it errored out almost immediately with a variable not found. I couldn't get to the bottom of what was different between my Motu 828 and the Motu M6 to cause this. So I took this more manual approach and got further. FWIW, this latest manual attempt seems to hit this same issue described here: alsa-project/alsa-lib#245 Regardless, I will read up on how to create a pull request and include both of my attempts as well there. |
The newest Motu 828 (28x32) does not appear to have a UCM yet. It is a class compliant USB device; so as a result, it generally "works" at a very basic level; but default channel mappings and profiles do not.
The system appears to default to only 2 channels in and 2 channels out. So, for example, surround playback seems to mix into either the left or right channel.
In qpwgraph, it shows 30 inputs (I believe this includes an additional 2-channel loopback at the end) and 32 outputs, all marked as "AUX#," where # starts with 0. I was able to identify which AUX# corresponds to which input or output on the device, through the use of qpwgraph and the device's built-in digital VU meter.
I have tried to create a UCM or even an asoundrc; but I have no idea what I'm doing. The documentation and examples are not intuitive for me.
Could I collaborate with someone in order to get this audio interface supported? I'd be happy to run any commands and tests you advise on.
The text was updated successfully, but these errors were encountered: