Volumio 3 RC1 - Open Beta Testing

Hi,
I am on volumio 3.150, manifest ui.
I have a free account. When I sign out from the account on volumio, after a while the volumio login back… Strange.
Thanks

I saw that the new volumio3 is calling very often www.google.com and i ask me why? And then i ask me why the point “Settings → System → Allow UI statistics Collection” is missing. :grimacing:

No bug report, but I want to thank you for the incredible new Manifest UI. It looks amazing. Much better than the previous UI. And navigating it is a real pleasure. Thanks guys!

1 Like

HiFiBerry requested that I post the output of dmesg which I have done. The output show some errors/fails towards the end where the HAT is being ‘loaded’. This is the section, in case someone who knows a lot more than me can see a cause.

[ 14.727607] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned.
[ 14.739028] bcm2835_audio bcm2835_audio: card created with 4 channels
[ 14.742735] bcm2835_audio bcm2835_audio: card created with 4 channels
[ 15.246197] snd-rpi-wm8804 soc:sound: ASoC: failed to init link HiFiBerry Digi+ Pro: -517
[ 15.278498] snd-rpi-wm8804 soc:sound: ASoC: failed to init link HiFiBerry Digi+ Pro: -517
[ 15.571663] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[ 15.771411] cfg80211: Loaded X.509 cert ‘sforshee: 00b28ddf47aef9cea7’
[ 16.023794] snd-rpi-wm8804 soc:sound: ASoC: failed to init link HiFiBerry Digi+ Pro: -517
[ 16.027317] brcmfmac: F1 signature read @0x18000000=0x15264345
[ 16.040148] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 16.040626] usbcore: registered new interface driver brcmfmac
[ 16.047031] snd-rpi-wm8804 soc:sound: ASoC: failed to init link HiFiBerry Digi+ Pro: -517
[ 16.254897] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,3-model-b-plus.txt failed with error -2
[ 16.512705] random: crng init done
[ 16.512722] random: 7 urandom warning(s) missed due to ratelimiting
[ 16.522160] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6
[ 16.546094] wm8804 1-003b: Failed to read device ID: -121
[ 16.546433] wm8804: probe of 1-003b failed with error -121
[ 16.562533] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Jan 4 2021 19:56:29 version 7.45.229 (617f1f5 CY) FWID 01-2dbd9d2e
[ 17.647642] lan78xx 1-1.1.1:1.0 eth0: kevent 4 may have been dropped
[ 17.760893] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
[ 18.195405] uart-pl011 3f201000.serial: no DMA platform data
[ 18.253510] 8021q: 802.1Q VLAN Support v1.8
[ 18.253583] 8021q: adding VLAN 0 to HW filter on device eth0
[ 23.651919] brcmfmac: brcmf_cfg80211_set_power_mgmt: power save disabled
[ 25.224647] Bluetooth: Core ver 2.22
[ 25.224717] NET: Registered protocol family 31
[ 25.224722] Bluetooth: HCI device and connection manager initialized
[ 25.224741] Bluetooth: HCI socket layer initialized
[ 25.224749] Bluetooth: L2CAP socket layer initialized
[ 25.224763] Bluetooth: SCO socket layer initialized
[ 25.250563] Bluetooth: HCI UART driver ver 2.3
[ 25.250575] Bluetooth: HCI UART protocol H4 registered
[ 25.250618] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 25.250776] Bluetooth: HCI UART protocol Broadcom registered
[ 25.465853] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 25.465863] Bluetooth: BNEP filters: protocol multicast
[ 25.465880] Bluetooth: BNEP socket layer initialized

Hi them all,

here my 2ct about the 3.150 Beta on x86.
Log: http://logs.volumio.org/volumiobuster/DOoZIT4.html
Device: 94b69480143676f15f8bb2ad8675de02

  • I’d really love a hint during the “resizing disk” phase during the first boot sequence. This can really take a long time and nothing happens on the black screen of the UI … Some people might not be patient enough to wait for it.
  • :x: After the very first startup after flashing the USB stick I wasn’t able to connect from the volumio device to MyVolumio, tidal, webradio. ssh login was successful. Every network DNS resoluion ended up in 192.168.211.1 (which is not existing in my network). There has been also the old UI active after the first startup. I checked the Version: it was really 3.150 !
  • After a reboot everything worked fine. Login to MyVolumio :white_check_mark: , Tidal playback :white_check_mark: , Tidal connect :white_check_mark: , webradio :white_check_mark:
  • :x: After some time of playing / zaping arount with Tidal Connect the connection was lost and could only be reestablished by loggin out and in into MyVolumio.

Tests regarding output devices.

  • SPDIF :white_check_mark:
  • analogue out :white_check_mark: (but SPDIF keeps beeing active as well)
  • HDMI :white_check_mark: (but hi-res audio files are played broken the first 10 seconds of the track)

The 3.150 seems to be stable and robust so far.

The new UI is amazing - of course it takes a bit time to get warm with it… :wink:

Cheers and take care!
Robert

SilentmaxX Kenko X86 PC (main installation).

Further equipment:

NAD Direct Digital DAC C 510
Trends Audio Class T Amplifier TA-10.2
Dali Zensor 1 + Dali Sub E-9

volumio@smx:~$ inxi -Fxxxz
System:    Host: smx Kernel: 5.10.70 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: 2262 2: 2209 3: 2286 4: 2241
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: 120x50
           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: k5.10.70
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: 43.27 GiB (3.6%)
           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: SanDisk model: USB 3.2Gen1 size: 232.88 GiB serial: <filter> rev: 1.00
           scheme: MBR
           ID-3: /dev/sdc type: USB vendor: Intenso model: Rainbow Line size: 29.69 GiB serial: <filter> scheme: GPT
Partition: ID-1: / size: 25.35 GiB used: 41.7 MiB (0.2%) fs: overlay source: ERR-102
           ID-2: /boot size: 170.8 MiB used: 57.8 MiB (33.8%) fs: vfat dev: /dev/sdc1
Sensors:   Missing: Required tool sensors not installed. Check --recommends
Info:      Processes: 166 Uptime: 41m Memory: 3.70 GiB used: 594.0 MiB (15.7%) 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:~$

1 Like

RPi Zero 2
v3.150
Bluetooth Input Audio Breaks
Log here

Frequent breaks in audio for BBC Sounds & Spotify input by bluetooth even when mobile is sat next to the RPi0-2.

@Darmur Have you tried bluetooth on your RPi0-2?

I am fairly certain this was working fine on a RPi4 a week or so ago for an earlier version of Volumio3, so could be peculiar to RPi0-2??

Edit: behaviour confirmed by Darmur.

not yet, I will try

Hi

Don’t know if related to my message to ALLO for Piano 2.1 driver and communication with Volumio, but the “Piano2.1” DAC choice plus “Dual Mono” or “Dual Stereo” now works in Volumio 3.150.

Thanks to anybody allowing this to work once again (broken since V2.699)!

1 Like

Hello all,

Regarding my issue, I saw that the displayed bit rate in Volumio’s interface is not the original one (from qobuz).
Indeed, when I play a 24bit 44Khz qobuz song, it is showing always 24 bits 96Khz in Web-ui and get the DAC crashed when skipping to next track.
The DAC is not crashing when both bit rates are the same.
I think it is the root cause of my problem.

Is it a Volumio’s bug to have another bit rate displayed in WEB-ui ?
Should I set something to avoid this ?
I got another Atoll DAC100 Signature and the problem is the same.

Many thanks for your help.

Yes, the wrong bitrate is returned by backend to the UI. I do not know if it’s mostly a visual bug, or would it cause some odd behaviour aswell.

Thanks for your reply. Yes I supposed also it was visual bug. My old Micromega MyDAC is working fine, no issue from the beginning. I don’t know why my new Atoll DAC100 Signature XMOS XUF208-128 is not, whereas I can play each song manually it is working (whatever the bit rate), but by the queue it is sometimes crashing. I will check more :slight_smile:

Thank you for the new version of Volumio!

I have two questions:

  1. in version 2 there was a plugin to play Spotify directly in Volumio (not Spotify Connect) - is this plugin also available in version 3? I didn’t find it in the plugin menu.

  2. is it already possible to test the audio playback on a Sonos device? If so, how?

Thanks in advance for an answer
Kai

Its not available, atleast yet.

1 Like

I had to reflash my image over a dozen times thinking it was broken, but on my Raspberry Pi Zero 2 W, it often got stuck in a boot cycle when attempting to boot it while connected to HDMI.

It also never shows the Volumio setup hotspot for me, when I first tried booting it it wouldn’t go after numerous reboots.
Eventually I figured out how to bypass it:
-Reflash the device to a brand new image
-Boot it WITHOUT HDMI or USB ethernet device connected (it will format the sd and such)
-Disconnect it after a while (to make sure it had enough time to set everything up on first boot), connect the USB ethernet device, and power on the Pi again.
-You can now connect to the Pi Web UI, after it has turned on I plugged in HDMI for audio and it works
(It will also function over wifi after setting that up)

No idea how to provide logs in this scenario as it kind of requires the boot logs on first startup, and I am not able to connect devices without it breaking…

All plugins seem to be working great now! (I had 3.129 before with only Spotify2 which did work but installing it was kind of buggy and only worked with test mode enabled, although it did work, on 3.150 now)

Manifest UI looks amazing, but having the same problem here with the My Account page popping up every 5-20 seconds. I will provide logs on this if anyone can point me out how to do this properly and if you would like me to do any specific actions while logging?

I have a system in the configuration:

  • RPI 4 Gb RAM
  • Audiophonics power module
  • HDMI 5 "display
  • Volumiobuster-3.150-2021-11-19-p compilation
  • Built-in Denon PMA1600NE amplifier DAC
    I installed the system on a 16Gb SD card and noticed the following problems:
  1. By sending a USB signal to my DAC, the signal is twice as quiet and lacks dynamics (despite the combination of different settings). I don’t know why maybe it’s the beta version’s fault.
  2. The effect appeared as in the RPI3 version, i.e. jams appear during playback (LAN 1Gb network connected with a cable)
    3.No support for Audiophonics power module (no longer have this plug)

Thanks for a great job!
3.150 runs nice. And the new UI is great. Just I am constantly redirected to ‘/myvolumio/profile’. I leave Volumio on ‘/playback’ or ‘/browse’ and after some time I get ‘/myvolumio/profile’ again.

I think I am getting close to understanding the problem, it seems to be one of timing. The PI takes some time to boot up and so does the DIGI HAT. If the power supply for the boards was not powered, it too will take a little time to bring its voltage and current supply up to the required levels. If these timings conflict a little the DIGI is not initialised and so Volumio cannot use it. (sorry if my description/words are a bit clumsy!)
I think this is probably something that firmware could avoid but until then the only way I have had success is to have the power supply up and running, then connecting it to the devices. This not the way I have powered up my stuff before as I am nervous of fitting plugs into sockets when they powered.
I guess you dev guys will know if there is anything you can do to help with Volumio’s HAT recognition process, I hope you can. :smiley:

version 3.150 on rPi 3b +, new UI Manifest, after a few seconds automatically redirects to “/myvolumio/profile”, is this the intended action? because it looks weak, especially when using an external screen

device: rpi3b, image: Volumiobuster-3.150-2021-11-19-pi
audio output: not relevant
issue:
I was trying to debug a problem in the first start wizard. But every time I try to test things, volumio keeps pestering me about signing up to myVolumio. How do I get rid of this?
I do not want to sign up, I don’t need myVolumio and do not want it.
At present this makes volumio3 completely unusable for me.
I am at a loss for words to explain how annoying this is.

reproduce:
Make a fresh image on an SD card, boot volumio. Run the first run wizard. Then wait until volumio starts asking you about myVolumio. Then try to ignore it. Warning: your head might explode.

@volumio any update on addressing issues with using the WiFi hotspot with the Pi A+ (v2 and v3 have issues). Wanted to know analysis before trying latest v3 image.