Looks like there are not many bugs left to fix. How far is the development? Would you call the current version close to stable? And are plug ins introduced to this version yet? Thanks in advance!
Updated version to 3.078 …
I had installed version 3.074. I noticed a new version is shown is this thread, but it is not detected through the Check Updates feature of the application. Is it possible to install the new version without reverting to the default configuration?
You have to go to http://your-device/dev and enable “Test Mode” to receive onair updates in this version.
I would like to have the following improvement in the Buster version: when using the web UI, the spacebar should toggle between play/pause. Currently, it doesn’t work like this, and the rest of the other applications (i.e. Spotify Web) do it.
Thank you in advance and best regards.
You can achieve that by installing triggerhappy (in v2 it is preinstalled) and configure that in the “audio.conf” file.
Don’t think triggerhappy will work while controlling the device from another device via the webUI - that needs to be implemented in the front end UI logic.
This method works, but it is not plain to me why the design would require enabling updates, through an explicit process even when such updates are initialized manually.
Is this restrictions documented? I have no memory of reading about it.
Well, anyway, I have the update installed, but still have the problem of non-working functionality for appending to the queue.
You have to activate dev mode in order to test untested, unstable version…
The requirement is sensible as stated, but I think the earlier confusion follows from its occurring on a system that already had been running a beta release. Perhaps the requirement should be waived for upgrades along an existing development tract.
The beta version has been pushed in order to be tested. Other build are made for Dev test. They are not intended to be used. Of course you can still test, but it may not work, or features may be disabled.
Let me clarify my comment with a concrete example. Suppose a user is running a beta version and then manually invokes the command to check for a new version. Following the current design, the application will report that no new version is available, if dev mode is not enabled. Why would you characterize this behavior as desirable? If the user is running a beta version and requests a more recent version, then almost universally such a user would wish to see a prompt indicating the availability of any new beta version and an option to proceed installing it. I can think of no obvious general case in which a user running a beta version, and asking the application for a new version, would prefer that the application report no new version being available.
8 posts were merged into an existing topic: Waveshare WM8960
So, you mean that it is still an improvement that has to be implemented in the Web UI, not by the triggerhappy, don’t you?
Thank you for your answers.
Exactly, this feature/improvement would then benefit all versions of Volumio. This should be simple to implement, but of-course I am not a front end guy so I could be wrong
So, let’s hope that Volumio guys take note of this.
Wenn ich HifiBerry Dac2 HD verwende, scheint es nicht zu funktionieren. (Siehe Bilder)
Hifi Berry Dac2HD
Hier das Log: http://logs.volumio.org/volumiobuster/6caEAm1.html
With Allo BOSS there are no mistakes!
Updated version to 3.079 …
I can confirm that, it happened to me too in Qobuz. Sometimes it is 1 minute or more. The track is not over, the GUI continues but the sound is gone …
With Skip the next track is played normally with sound and again at the end the sound is suddenly gone.
No improvement even after reboot.
3.079 buster beta
Qobuz, after 1 day of inactivity. If I want to play a song from a playlist, volumio process goes to 100%. In order to fix this I need to perform a volumio vrestart and it is ok.
Pls fix. This is a payed service.