![]() ![]() On the Pi side we need a virtual soundcard that exposes eight channels. That might have been the end of the story but wait, I’l continueĪs Roon cannot handle 4-channel devices why not giving Roon an 8-channel virtual device on the Pi side. There is an open feature request for that, one from me ( Support for 3 and 4 channel layouts, Request: Support Four-Channel DACs). Roon isn’t able to deal with 4-channel interfaces! It does with 2.0, 5.1 and 7.1 but not with 4.0. ![]() You can check this with the “aplay -l” command. I could fix that with an external Hub that also has a separate power supply, even better With the Hub the M4 got connected and discovered by ALSA. It is a software issue in the Pi4 USB controller. ![]() I thought it was an issue with power but it was not. Motu M4 is USB powered, so I thought the Pi4 and the M4 together with a Pi4 3A power supply would give a handy and high quality system.ĭuring my effort I was faced a lot of issues but finally I succeeded! I like to report what I did, because my findings may also be relevant for all other 4-Channel audio interfaces.Ĭonnecting the M4 to a USB port of the Pi4 I found, that right after Raspbian discovers the USB device it got disconnected, reconnected and so on. The streaming device should be a cheap Raspberry Pi4 running Raspbian and Roonbridge. The idea was to run it as a playback device in an active F.A.S.T configuration with two woofers and two full range speakers. Recently I bought a Motu M4 USB audio interface because of it’s really excellent technical parameters (, ). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |