Volumio 3 Beta test: New init

[nerd]

From supplied settings and logs there is LU28R55 which only supports USB audio (according to specs) connected to DP-1 on J3455-ITX with Intel HD Graphics 500 capable of HDMI 2.0 - what is used as HDMI audio? Headphones on the LU28R55?

[Robert.Hecht]

Hi,
excuse me - I’m now playing over HDMI connected to an NAD DAC C510
At my first test a week before the HDMI was connected to my Samsung display to check the volumio UI.

This is my current configuration - do you need more information?

volumio@smx:~$ inxi -Fxxxz
System:    Host: smx Kernel: 6.6.29-volumio x86_64 bits: 64 compiler: N/A Console: tty 0 dm: N/A
           Distro: Debian GNU/Linux 10 (buster)
Machine:   Type: Desktop Mobo: ASRock model: J3455-ITX serial: <filter> UEFI: American Megatrends v: P1.40 date: 07/14/2017
CPU:       Topology: Quad Core model: Intel Celeron J3455 bits: 64 type: MCP arch: Goldmont rev: 9 L2 cache: 1024 KiB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 11980
           Speed: 2300 MHz min/max: 800/2300 MHz Core speeds (MHz): 1: 2300 2: 800 3: 800 4: 1400
Graphics:  Device-1: Intel vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5a85
           Display: tty server: X.org 1.20.4 driver: modesetting unloaded: fbdev,vesa tty: 243x56
           Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:     Device-1: Intel Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Audio Cluster vendor: ASRock
           driver: snd_hda_intel v: kernel bus ID: 00:0e.0 chip ID: 8086:5a98
           Sound Server: ALSA v: k6.6.29-volumio
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169 v: kernel port: e000
           bus ID: 01:00.0 chip ID: 10ec:8168
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    Local Storage: total: 1.17 TiB used: 151.40 GiB (12.7%)
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB speed: 6.0 Gb/s serial: <filter> rev: 1B6Q
           scheme: GPT
           ID-2: /dev/sdb type: USB vendor: Intenso model: Rainbow Line size: 29.69 GiB speed: <unknown> serial: <filter>
           scheme: GPT
           ID-3: /dev/sdc type: USB vendor: SanDisk model: USB 3.2Gen1 size: 232.88 GiB speed: 6.0 Gb/s serial: <filter>
           rev: 1.00 scheme: MBR
Partition: ID-1: / size: 25.57 GiB used: 46.7 MiB (0.2%) fs: overlay source: ERR-102
           ID-2: /boot size: 168.4 MiB used: 77.9 MiB (46.3%) fs: vfat dev: /dev/sdb1
Sensors:   Missing: Required tool sensors not installed. Check --recommends
Info:      Processes: 185 Uptime: 37m Memory: 3.70 GiB used: 566.5 MiB (15.0%) Init: systemd v: 241 runlevel: 5 default: 2
           Compilers: gcc: N/A Shell: bash v: 5.0.3 running in: tty 0 (SSH) inxi: 3.0.32
volumio@smx:~$

[Robert.Hecht]

This is a log while playing over HDMI:

http://logs.volumio.org/volumio/fVpZyzw.html

volumio@smx:~$ inxi -Fxxxz
System:    Host: smx Kernel: 6.6.29-volumio x86_64 bits: 64 compiler: N/A Console: tty 0 dm: N/A
           Distro: Debian GNU/Linux 10 (buster)
Machine:   Type: Desktop Mobo: ASRock model: J3455-ITX serial: <filter> UEFI: American Megatrends v: P1.40 date: 07/14/2017
CPU:       Topology: Quad Core model: Intel Celeron J3455 bits: 64 type: MCP arch: Goldmont rev: 9 L2 cache: 1024 KiB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 bogomips: 11980
           Speed: 2196 MHz min/max: 800/2300 MHz Core speeds (MHz): 1: 2196 2: 2196 3: 2196 4: 2196
Graphics:  Device-1: Intel vendor: ASRock driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5a85
           Display: tty server: X.org 1.20.4 driver: modesetting unloaded: fbdev,vesa tty: 163x56
           Message: Unable to show advanced data. Required tool glxinfo missing.
Audio:     Device-1: Intel Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Audio Cluster vendor: ASRock
           driver: snd_hda_intel v: kernel bus ID: 00:0e.0 chip ID: 8086:5a98
           Sound Server: ALSA v: k6.6.29-volumio
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: ASRock driver: r8169 v: kernel port: e000
           bus ID: 01:00.0 chip ID: 10ec:8168
           IF: eth0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    Local Storage: total: 1.17 TiB used: 151.41 GiB (12.7%)
           ID-1: /dev/sda vendor: Samsung model: SSD 860 EVO 1TB size: 931.51 GiB speed: 6.0 Gb/s serial: <filter> rev: 1B6Q
           scheme: GPT
           ID-2: /dev/sdb type: USB vendor: Intenso model: Rainbow Line size: 29.69 GiB speed: <unknown> serial: <filter>
           scheme: GPT
           ID-3: /dev/sdc type: USB vendor: SanDisk model: USB 3.2Gen1 size: 232.88 GiB speed: 6.0 Gb/s serial: <filter>
           rev: 1.00 scheme: MBR
Partition: ID-1: / size: 25.57 GiB used: 53.2 MiB (0.2%) fs: overlay source: ERR-102
           ID-2: /boot size: 168.4 MiB used: 77.9 MiB (46.3%) fs: vfat dev: /dev/sdb1
Sensors:   Missing: Required tool sensors not installed. Check --recommends
Info:      Processes: 181 Uptime: 55m Memory: 3.70 GiB used: 627.9 MiB (16.6%) Init: systemd v: 241 runlevel: 5 default: 2
           Compilers: gcc: N/A Shell: bash v: 5.0.3 running in: tty 0 (SSH) inxi: 3.0.32
volumio@smx:~$

[nerd]

Thank you Robert, this will do for now.

NAD DAC C510 → HDMI x 2 (2-channel PCM). The C 510 accepts PCM data (not DSD via HDMI) rates up to 24 bit 192 kHz.

Can Intel 500 match from HDMI. Hmm. On spec with USB, I2S → yes. HDMI - max rate 24bit only and no density.

This is very interesting indeed.

[nerd]

Perhaps it is trivia - what exact HDMI cable type and length is between J3455-ITX and C510?
The reason I am asking is that there is no clock jitter shown in the logs.

[Robert.Hecht]

I tried 4 or 5 different cables.
The actual one is of 120cm length and the printing says “High Speed HDMI cable E119932-U AWM Style 20276”

[Robert.Hecht]

As long as the synch rate between the volumio PC and the NAD C510 stays equal or below 48k (over HDMI) everything works fine. Synch rates above that show this splintering during the first 10 seconds of the track.

When using the SPDIF connecrion between the two devices, everything wors fine up to synch rates of 192k

[nerd]

@Robert.Hecht

stays equal or below 48k (over HDMI)

This sounds like clock sync jitter. As far as time goes, all HDMI signals are re-clocked at sink based on a formula derived from the source clock. As such, the cable can play little part in the quality of the signal, however cannot be ruled out.
All that can affect the signal is the quality of the source and sink electronics. It is now standard for HDMI chipsets to have jitter performance of less than 1ps, which is way way better than needed for any audio signal.
Big question - is it source or receiver which looses the “tick”.

[Robert.Hecht]

Anyway. I seem to be the only one here experiencing this. And use of the SDPIF interfaces solves the problem for me. I’m fine to park this issue in a separate thread as well.

Issues regarding the general robustness of the system (Tidal Connect, scanning sources building up the lib, player restarts) are - in my point of view - much more important to be solved.

[nerd]

@Robert.Hecht

Anyway. I seem to be the only one here experiencing this. And use of the SDPIF interfaces solves the problem for me. I’m fine to park this issue in a separate thread as well.

Agreed - this can be safely moved to a separate technical discussion.

@Robert.Hecht

Tidal Connect

Is being discussed and worked on.

@Robert.Hecht

scanning sources building up the lib

Is there something you would like to expand on? Are we seeing problems in the 3.674?

@Robert.Hecht

player restarts

I am not following - Are we seeing problems in the 3.674?

[Robert.Hecht]

There seems to be a connection between instability of tidal connect and a running scan process that builds up the lib. This causes player restarts sometimes. That’s the separated issue a few days ago. And: yes, that’s the same in the 3.674 but out of scope of this beta, right?.

[nerd]

@Robert.Hecht

instability of tidal connect and a running scan process

Thank you, understand the context now. The music library (aka lib - right?) will be affected when source is disconnected. This will force mpd process re-cycle. In some cases mpd will land in a state where the database gap can no longer be extrapolated, in such case restart clears the gridlock. Prior mpd version 0.35 there was only an ambiguous {EPIPE} error without knowing which of in/out functions throwing it. Now we know more - what and why is happening. Upstream is working on the fix, no eta.
Either-way - not a subject to this beta test.

[nerd]

3.674

Key improvements:

• Updated socket.io to v2.3
• Improved visualization on 11 inch display
• New onboarding wizard
• Increased icons size of back and home

[Camelot631]

Hello from Switzerland… I’m “only” a silent reader and a “Volumio newbie”, but huge respect and thanks for this work…

I only have one small problem at the moment… it is not possible to restart the Raspi 4 with an SSD/stick on the USB port. The Raspi just gets stuck… See my configuration below.-…

Volumio otherwise works perfectly!

Small wish>> Bluetooth to play on BT speakers & headphones… I installed the Bluetooth instructions here from the forum, but it only works to a limited extent…

2. Small wish>> If user adjustments are made to the system (config files), a new update from Volumio should still be able to be carried out. So far there has been an error message saying that an update is not possible due to user settings and that you should reset Volumio… But I don’t think resetting is good…

Small question>> Are USB-IR supported (Flirc USB v2; IRduino Adafruit)??

My config:

Raspberry PI 4 B 8 GB (current eeprom)
iQaudIO DAC Pro
SSD T7 500GB or USB stick Kingston Data Traveler Kyson 512GB
Tochscrenn follows
Volumio RC 3,676 (since May 15, 2024)

Greetings, Camelot631

[nerd]

Thank you for reporting,

@Camelot631

is not possible to restart the Raspi 4 with an SSD/stick on the USB port.

This is a known, and currently unresolved (no eta) reset state on MD-USB in the RPi firmware. Only cold restart is available. I am testing extra eeprom flags which in theory should keep USB active and initialised during reboots, will share my finding in the due course.

@Camelot631

I installed the Bluetooth instructions here from the forum, but it only works to a limited extent

Can you describe the problem as detailed as you can?

@Camelot631

user adjustments are made to the system (config files),

This will not change. OTA updater will be refused, as it not capable of understanding your particular set of changes. [NOT OFFICIALLY SUPPORTED] Make backup of your changes, perform the reset, restore or merge your changes. [OFFICIALLY SUPPORTED] author and write system plugin, this way changes will be prevalent.

@Camelot631

Are USB-IR supported

I do not see a technical reason why they should not, for as long as uinput device does not change. It is all about events mapping.

[Camelot631]

Hi
Thanks for the feedback.

I installed BT from the forum here:

Bluetooth Speaker Plugin

Hi, thank you! I ended up trying bluetoothctl yesterday and it asked for PIN so I was able to pair it (I see the device even in the plugin). Now, despite being connected, I’m not getting any sound from the speaker so now I’m in the process of solving this. Interesting info about PIN obsolescence, I didn’t know that. But still every now and then I get a request for “0000”, “1234” and these are definitely newer devices than 2.1 so probably there are devices which don’t respect or su…

But post 190 doesn’t work for me. No matter which Volumio version:

Bluetooth Speaker Plugin

Update: I realized that playback with volumio3 and latest version of this plugin is actually a lot better on my JBL Flip 6 compared to volumio2 (version from #149). But still, depending on the source (podcast, local, spotify), playback on JBL Flip 6 was a bit choppy, while the old Bose Color SoundLink worked flawless. I was able to solve this issue for volumio3 by updating to the latest bluez-alsa. To do so, one has to change only two lines in the file “install.sh” inside “bluetooth-controller…

An error message appears when executing “ExecStart” and then in the volume that “bluez-alsa” does not work…

I’ll test IR with USB when I get the part…

[Wheaten]

On the USB-IR, You should be OK as long as you don’t plug it to a different port.
Worst case scenario, you can force a rule. Take a look at:

DEV: [PLUGIN] MPD_OLED for x86 based systems

Hi @Wheaten I looked at a udev rule. Plugging in the USB adapter I can see it is appearing as /dev/i2c-8, then udevadm info /dev/i2c-8 Gives DEVPATH=/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/i2c-8/i2c-dev/i2c-8 Chopping the end off this and adding * gives the rule SUBSYSTEM=="i2c-dev", DEVPATH=="/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.1/1-1.1:1.0/*", SYMLINK+="i2c-99" Unplug the adapter, add the rule, reload the rules and plug in the device, and it can be accessed th…

[Robert.Hecht]

Update from 3.674 to 3.676 ends up in GRUB selection screen where I have to choose manually the single entry there.

Selecting the entry ends up in an error message “no such device”

After a few seconds the system switches back to GRUB.

I tried to update a bootable USB Stick in my X86 / AMD64 system…

[Robert.Hecht]

Flashing the image and trying to startup ends up in the same error message “no such device”…

Might the 3.676 image be corrupt?

[nerd]

@Camelot631

But post 190 doesn’t work for me. No matter which Volumio version

I think continuing troubleshooting should be continued in the plugin’s topic, where the original work is undertaken. There is no change to the bluetooth stack in this beta.