Hello everyone, I got very sick some time ago. That’s why I couldn’t be here.
New version for Orange boards (Orange Pi Lite, Orange Pi PC, Orange Pi One):
>>>Volumio-3.198-2022-01-31
New kernel (5.10.60) with patch (works native DSD) for USB DAC:
E1DA 9038d
Tempotec Sonata E44.
1 Like
DSD Test for Tempotec Sonata E44:
DSD128:
volumio@volumio:~$ cat /proc/asound/card5/pcm0p/sub0/hw_params
access: RW_INTERLEAVED
format: DSD_U32_BE
subformat: STD
channels: 2
rate: 176400 (176400/1)
period_size: 22050
buffer_size: 88200
volumio@volumio:~$
The sound is just awesome!!!
I even like it better than the USB DAC - E1DA 9038d.
It’s working as well on Orange Pi Zero 1 LTE, good job !
I am asking the opinion of users: do I need to make myVolumio in v.3?
Without this, automatic installation of plugins from the store in version V3 is impossible without (free) login to myVolumio.
Plugins are currently being installed manually.
1 Like
See my comments on the other thread, (in my limited experience) myVolumio doesn’t work well on 512MB devices… Moreover, the image size is bigger, so as per this
Volumio requires at least 512MB of RAM, 1GB is strongly suggested.
It has nothing to do with Nodejs but with the fact that Volumio loads the entire OS in RAM to avoid SD Card corruption and improve performances, so ideally RAM should be 2X the OS Size (which is rougly 500mb)
The following board configurations are currently on sale:
Orange Pi PC - 1GB
a) Orange Pi One - 1GB
b) Orange Pi One - 500MB
Orange Pi Lite - 1GB
Is 1GB enough?
The new version for Orange Pi PC 2:
Volumio-3.224-2022-02-14-orangepipc2.zip
Kernel 5.10.60 with patch (works native DSD) for USB DAC:
E1DA 9038d
Tempotec Sonata E44.
The new version 3.236 for Orange Pi boards (Orange Pi Lite, Orange Pi PC, Orange Pi One and Orange Pi PC2 ) :
Volumio-3.236-*
kernel 5.15.26 (with patch (works native DSD) for USB DAC)
node js on OrangePi PC2 (aarch64) failed while emulating the CP15 Barrier instruction (solved)
add Volumio FIFO ALSA plugin to the base image
Now you can install (in manual mode) the plugin FusionDsp and it works!
Thanks @balbuze !
Download the plugin and unzip
wget https://github.com/balbuze/volumio-plugins/raw/alsa_modular/plugins/audio_interface/FusionDsp/fusiondsp.zip
mkdir fusion
miniunzip fusiondsp.zip -d ./fusion
cd fusion
In Install.sh change
if [ $cpu = "armv7l" ]
becomes
if [ $cpu = "aarch64" ]
Save and install
volumio plugin install
I pushed an update to allow install on aarch64
So, no need to tweak files now
wget https://github.com/balbuze/volumio-plugins/raw/alsa_modular/plugins/audio_interface/FusionDsp/fusiondsp.zip
mkdir fusion
miniunzip fusiondsp.zip -d ./fusion
cd fusion
volumio plugin install
cd ..
rm -Rf fusion*
That’s excellent. It will be easier to install
@milom , try installing the Volumio-3.236-2022-03-07-orangepipc2 .
He is also on H5. It should start and work.
Check it out, I’m interested myself.
3.236 run very slow on 1GB OrangePi Lite
1 Like
This is a test image for the operation of the plugin DSP.
Install the version 3.198, but the DSP plugin will not work there.
Thanks, But 3.198 is slow and frozen, too.
1 Like
On my board (1GB OrangePi Lite), both images work fast.
I checked it again yesterday - re-installed on Samsung microSD (32 Gb). It works quite speedly.
PS: some time I installed on a no name microSD card and the system was slowing down.
Darmur
April 25, 2022, 8:41am
31
awesome! I didn’t expect MPD OLED to be working on other platforms rather than raspberry pi
what did you do to make it working? I’d like to try on NanoPi NEO2
1 Like
I did it according to the instructions:
# Install instructions for Volumio 3
These instructions are for installing mpd_oled with a binary package on
Volumio 3.
The binary package should be the best option for most people, but if you
would like to build and install the current mpd_oled repository code then see
[Install instructions for Volumio 3 using source](install_volumio3_source.md).
## Base system
[Volumio](https://volumio.org/) should be installed. Ensure a command line
prompt is available for entering the commands below (e.g.
[use SSH](https://volumio.github.io/docs/User_Manual/SSH.html).)
## System settings
Configure your system to enable I2C or SPI, depending on how your OLED
is connected.
This file has been truncated. show original
It’s very simple there.
The main thing is to find out the device address:
sudo i2cdetect -y 1
or
sudo i2cdetect -y 0
My address is: 3c
volumio:~$ sudo i2cdetect -y 0
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- 3c -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
And accordingly, I changed the launch of the service:
sudo mpd_oled_service_edit -o 3 -B 0 -a 3c -b 10 -g 1 -f 15
All parameters are clear from the file README.md or running
mpd_oled -h
1 Like
Hi VyacheslavS
I have installed rev 3.236 with pcm5102a on Orange Pi PC.
48kHz 16bit music sounds good.
But 96 kHz 24 bit no sound at all.
$ cat /proc/asound/card1/pcm0p/sub0/hw_params
access: MMAP_INTERLEAVED
format: S24_LE
subformat: STD
channels: 2
rate: 96000 (96000/1)
period_size: 8000
buffer_size: 48000
I checked Volumio 2 does not work too.
Please explain pcm5102a >48kHz works or not?
Thanks
@phenolog , I can hardly help you, I don’t use a pcm5102a DAC and I can’t check and change something. Once upon a time I had such a DAC, but I was not satisfied with the sound. Now I have several different USB DACs and the sound quality is much better.