02-22-2021, 05:17 PM
@officialsm
The setting is in the moOde System Config panel.
I just looked up the user manual for the CXA81 Cambridge Amp (you still haven't said, so I'm just guessing this is correct).
Here's a quote from page 10
It's been my experience that, out of the box, moOde is able to drive any DAC which is claimed to be Audio Class 2.0. Between the DAC and moOde you have two x two = four different combinations of settings you can try. Have fun.
I can make all sorts of conjectures about the syslog messages but without more information that's all they are, conjectures (aka WAGs). The MTP messages could mean Raspberry Pi OS doesn't know this device needs a special udev rule that says skip the MTP scan for it; the unsupported format message could be true yet have no effect on moOde. OTOH, it's up to the vendor to provide the Linux devs with proper information. The quote from the manual suggests to me they aren't going to bother.
Regards,
Kent
The setting is in the moOde System Config panel.
I just looked up the user manual for the CXA81 Cambridge Amp (you still haven't said, so I'm just guessing this is correct).
Here's a quote from page 10
Quote:USE WITH LINUX
For most builds of Linux with the CXA switched to USB Audio Class 1 the
CXA will work with the native Audio 1.0 driver and accept audio up to
24-bit/96kHz.
Some very new builds of Linux are now supporting USB Audio Class 2
for which the CXA should be switched to Audio 2.0 to accept audio up to
32-bit/384kHz.
For both cases because Linux builds vary according to their creators choice
of software components including drivers it is not possible to guarantee
operation and Audio drivers may need to be loaded.
'Class drivers' as they are called for generic support of Audio Class 1.0 or
Audio Class 2.0 devices may be available from the Linux community, we
do not supply these.
It's been my experience that, out of the box, moOde is able to drive any DAC which is claimed to be Audio Class 2.0. Between the DAC and moOde you have two x two = four different combinations of settings you can try. Have fun.
I can make all sorts of conjectures about the syslog messages but without more information that's all they are, conjectures (aka WAGs). The MTP messages could mean Raspberry Pi OS doesn't know this device needs a special udev rule that says skip the MTP scan for it; the unsupported format message could be true yet have no effect on moOde. OTOH, it's up to the vendor to provide the Linux devs with proper information. The quote from the manual suggests to me they aren't going to bother.
Regards,
Kent
