• unify the output device selection (I2S or USB device) on one page
  
• allow the selection of an I2S driver by device name (as it is now) or by actual driver overlay name
  

(03-12-2022, 01:28 PM)TheOldPresbyope Wrote: @Relocated2007

You may be interested to hear that in the soon-to-be released moOde 8, the Audio Config screen has been improved to

• unify the output device selection (I2S or USB device) on one page
  
• allow the selection of an I2S driver by device name (as it is now) or by actual driver overlay name
  

The first is a matter of convenience to the user; the second makes it easy to configure for a device not yet in moOde's device database.

As well, the kernel and its drivers have been bumped to v5.15.23-v7+

Support other OSes? Any hacker can fork moOde's code repository and have a go. It should work mutatis mutandi. That's a lovely Latin phrase which more or less means "once all the necessary changes have been made" without committing to a statement of what those changes actually are. T.B.D. when the attempt is made. 

For example, I and at least one other user tried porting a much earlier release of moOde to a different ARM-based SBC as well as distro. In my case it was a SolidRun CuBox-i4Pro and the Armbian distro. It worked in the sense that I could play music (only to USB devices, no I2S interface is present) but it was a pain finding work-arounds to account for the differences from an RPi and the Raspbian OS of the time. Supporting the result in the long term would have been a nightmare as the different distros evolved in their own fashions. I patted myself on the back and moved on.

Regards,
Kent

Quote:Check what version of firmware your Pi 4 is running. You can do this by opening a new terminal window and entering the command

Code:

sudo rpi-eeprom-update

(03-12-2022, 11:54 PM)Relocated2007 Wrote:

(03-12-2022, 01:28 PM)TheOldPresbyope Wrote: @Relocated2007

You may be interested to hear that in the soon-to-be released moOde 8, the Audio Config screen has been improved to

• unify the output device selection (I2S or USB device) on one page
  
• allow the selection of an I2S driver by device name (as it is now) or by actual driver overlay name
  

The first is a matter of convenience to the user; the second makes it easy to configure for a device not yet in moOde's device database.

As well, the kernel and its drivers have been bumped to v5.15.23-v7+

Support other OSes? Any hacker can fork moOde's code repository and have a go. It should work mutatis mutandi. That's a lovely Latin phrase which more or less means "once all the necessary changes have been made" without committing to a statement of what those changes actually are. T.B.D. when the attempt is made. 

For example, I and at least one other user tried porting a much earlier release of moOde to a different ARM-based SBC as well as distro. In my case it was a SolidRun CuBox-i4Pro and the Armbian distro. It worked in the sense that I could play music (only to USB devices, no I2S interface is present) but it was a pain finding work-arounds to account for the differences from an RPi and the Raspbian OS of the time. Supporting the result in the long term would have been a nightmare as the different distros evolved in their own fashions. I patted myself on the back and moved on.

Regards,
Kent

Thanks @TheOldPresbyope for an update.

I am sure that can be ported this is Linux after all, but if there are so many distro-specific tweaks it is very difficult indeed and not worth the effort, indeed.


However I am sure that Wolfson DAC from my Rotel A12 can be used and RP4 can play via USB port to it but I am not to that advanced in Alsa, DACs, MPD to make it works. I am just hoping that it will work in the future. There is this website: https://www.horus.com/~hias/cirrus-driver.html where it guides how to make it but I have no luck still.  I am doing something wrong or moOde makes it more difficult.

(03-13-2022, 02:03 AM)DRONE7 Wrote: Out of interest, and having read some of the earlier logs, can you check what firmware your Pi4 is running..

From the RPi foundation.

Quote:Check what version of firmware your Pi 4 is running. You can do this by opening a new terminal window and entering the command

Code:

sudo rpi-eeprom-update

I seem to recall that MoOde runs the updater automatically but would be interested to see what firmware is reported.

(03-13-2022, 02:07 AM)Tim Curtis Wrote:

(03-12-2022, 11:54 PM)Relocated2007 Wrote:

(03-12-2022, 01:28 PM)TheOldPresbyope Wrote: @Relocated2007

You may be interested to hear that in the soon-to-be released moOde 8, the Audio Config screen has been improved to

• unify the output device selection (I2S or USB device) on one page
  
• allow the selection of an I2S driver by device name (as it is now) or by actual driver overlay name
  

The first is a matter of convenience to the user; the second makes it easy to configure for a device not yet in moOde's device database.

As well, the kernel and its drivers have been bumped to v5.15.23-v7+

Support other OSes? Any hacker can fork moOde's code repository and have a go. It should work mutatis mutandi. That's a lovely Latin phrase which more or less means "once all the necessary changes have been made" without committing to a statement of what those changes actually are. T.B.D. when the attempt is made. 

For example, I and at least one other user tried porting a much earlier release of moOde to a different ARM-based SBC as well as distro. In my case it was a SolidRun CuBox-i4Pro and the Armbian distro. It worked in the sense that I could play music (only to USB devices, no I2S interface is present) but it was a pain finding work-arounds to account for the differences from an RPi and the Raspbian OS of the time. Supporting the result in the long term would have been a nightmare as the different distros evolved in their own fashions. I patted myself on the back and moved on.

Regards,
Kent

Thanks @TheOldPresbyope for an update.

I am sure that can be ported this is Linux after all, but if there are so many distro-specific tweaks it is very difficult indeed and not worth the effort, indeed.


However I am sure that Wolfson DAC from my Rotel A12 can be used and RP4 can play via USB port to it but I am not to that advanced in Alsa, DACs, MPD to make it works. I am just hoping that it will work in the future. There is this website: https://www.horus.com/~hias/cirrus-driver.html where it guides how to make it but I have no luck still.  I am doing something wrong or moOde makes it more difficult.

The wolfson driver described in the link you posted is already included in moOde. Have a look in Audio Config in the DT overlay list. This driver is for a wolfson I2S card though and has nothing to do with a USB connected device like your Rotel.

Quote:Speaking of digitally-stored music, also worth noting that while the front-panel input [e.g., the USB port] can accept content on memory devices, its capability is somewhat limited: it'll only accept AAC(m4a), MP3, WAV and WMA (up to 48K 16 bit).

So if you want to play FLAC or Apple Lossless files off a memory stick, as we did at the launch of the 12-Series products down at Rotel distributor B&W in Worthing a while back, you'll be scuppered.

However, the built-in Wolfson WM8740 DAC supports files up to 24-bit/192kHz via the conventional digital inputs, so higher-resolution files could be played into it via a computer with a digital output, or one combined with a suitable USB-to-S/PDIF interface.

(03-13-2022, 01:27 PM)TheOldPresbyope Wrote: @Relocated2007

Sorry if I distracted with a synopsis of several new moOde features.

For a USB DAC, moOde simply "talks" to the Linux USB driver and leaves the nitty-gritty intercommunication to the Linux sound subsystem.

Some DAC vendors do things in non-standard ways. Many of these "quirks" are dealt with in the Linux sound subsystem codebase with catchy names like quirks.c, quirks,h, and quirks-table.h. (Case in point, a DAC might lie about the bit-sampling range it accepts when queried through the USB interface.)

One reason a newer kernel+modules might solve a USB communication problem is if the offending device has been added recently to the quirks codebase.

However, I don't believe the Rotel A12 with Wolfson WM8740 DAC requires a newer kernel. Checking the DAC Compatibility List over at Volumio, I see that a user already reported success with their Rotel A12 in 2019.

I found the following commentary about the Rotel A12 (with Wolfson DAC) on whathifi.com 

Quote:Speaking of digitally-stored music, also worth noting that while the front-panel input [e.g., the USB port] can accept content on memory devices, its capability is somewhat limited: it'll only accept AAC(m4a), MP3, WAV and WMA (up to 48K 16 bit).

So if you want to play FLAC or Apple Lossless files off a memory stick, as we did at the launch of the 12-Series products down at Rotel distributor B&W in Worthing a while back, you'll be scuppered.

However, the built-in Wolfson WM8740 DAC supports files up to 24-bit/192kHz via the conventional digital inputs, so higher-resolution files could be played into it via a computer with a digital output, or one combined with a suitable USB-to-S/PDIF interface.

You might consider using an I2S-S/PDIF hat rather than a full DAC hat. If nothing else, they are cheaper

Regards,
Kent