Help Center

Improved

Fixed

volumio

In Review

Planned

In Progress

Completed

Rejected

High Priority

Low Priority

*(Old bug to report)*
*Issue: playback controls issues after pause (Comportamento del player no log)*
After pressing the skip backwards button while paused then play

the indicated song and the actual song playing don’t match.
Demonstration procedure
Step 1: Press pause on track playing page.
Step 2: Press back skip button
Step 3: Press play. Sound picks up where paused. The displayed track information changed to the previous item in list
Step 4: Press forward skip. Currently playing track starts over from beginning. Displayed track information updates to current track.
*Other Issue:*
Step 1: Press pause on track playing page.
Step2: Press next skip button
Step3: Press play (player not responsive)
Step4: The only way to restore the player is to select a track from the queue

Integro 3.785

Rivo Plus connected to Holo Cyan 2 DAC via USB port

use Ethernet cable only
Hardware Revision: 1.0
Firmware Version: 0.2.1
Web Browser: Firefox v. 135.0
Mac OS: Sonoma 14.6.1

SW VERSION: 3.779

Streamplay

sw version 3.754

RIVO

V 3.779

Primo2 ; Rivo ; Integro 

sw v: 3.779

!Screenshot 2025-01-13 at 18.33.13.png|width=595

height=132

alt="Screenshot 2025-01-13 at 18.33.13.png"!

V3.785


Startup sound =>Off
Multiroom => Off


Narrowed the problems down to 2 things with the PrimoV2.

* Multiroom
* Randomizer plugin

when number of tracks exceed 50. all rPi's except this without issues. Doing the same on the Primo it stalls after +/- 20 tracks. Population of queue stalls

Primo stops after first track. If i delete the queue

the queue continues again to populate. And this behaviour continues untill all tracks are loaded. No idea why the Primo act differently than a rPi.

Rpi 4 -V3.742



!Screen Shot 2024-08-07 at 12.15.59.png|width=683

height=378

alt="Screen Shot 2024-08-07 at 12.15.59.png"!

Motivo> Spotify
3.738

device: ALL

sw version: 3.736

Device: Motivo

SW Version: 3737

device: MOTIVO

sw version: 3.736

Device: Motivo

SW: 3.718

Device: Motivo

SV: Not mentioned by client but problems run on 3.742

Motivo

all the sw versions

sw v : 3.742

all the devices

Volumio Version: 3.703
Hardware: Raspberry Pi 5 with touchscreen
Output device: Sabaj A30a (referred to as “DAC” for simplicity)

Motivo > Qobuz 
3.738

MOTIVO

MOTIVO VERSION 3.734

Device: RPI

Sw version: 3.703

sw vers: 3.703

device : RPI



IMPACT: 8X8

2.917
[http://logs.volumio.org/volumio/doRHBcj.html|http://logs.volumio.org/volumio/doRHBcj.html]

[https://youtu.be/aCwC6ESTidM|https://youtu.be/aCwC6ESTidM]



IMPACT: 5X5

IMPACT: 2X2

EFFORT: To be evaluated by the team

IMPACT: 1X1

EFFORT:

IMPACT: 2X2

EFFORT:

device: RPI

sw version: 3.703

IMPACT: 1X1

IMPACT: 4X4

Backlog

Next up

Done

Main Roadmap

Hey {name|there}! 👋

The system sets the volume to max on random occasions at startup. Since it shows the programmed volume of 10%.Furthermore it can’t be changed in this occasionlog: [+<a href="http://logs.volumio.org/volumio/TJlV4oj.html+|http://logs.volumio.org/volumio/TJlV4oj.html" rel="noopener noreferrer" target="_blank">http://logs.volumio.org/volumio/TJlV4oj.html+|http://logs.volumio.org/volumio/TJlV4oj.html</a>]

VOLUME SOMETIMES AT MAX ALTHOUGH SET TO 10%

Davide

Volumio

VOLUME SOMETIMES AT MAX ALTHOUGH SET TO 10%

Subscribe to post

Subscribe to post