Hello,
i have the same problem on two 4Bs.
Have you find the problem?
Peter
Hello,
i have the same problem on two 4Bs.
Have you find the problem?
Peter
Billjon: Thanks for the suggestion for the suggestion about the router. That may have been part of the problem.
Pedder3: I haven’t fully solved the problem, but most of it has resolved. I still have a stop after a half second the first time I play something, but the second time it now works fine. I can now see my devices even after a long period of inactivity. It doesn’t seem to be a Volumio issue. I haven’t done anything with Volumio, but the problem improved after two events: The Spotify Android app was updated and we had a local power outage resetting the router and all device connections.
Kevin
Same issues here for me guys. Tracks will play for around a second then drop out. @volumio any progress on this please?
*** For info, the issue occurring on visible plugin and beta install.
Hi,
I have made an Volumio installation on my Pi4. I have a premium account.
Tidal is working fine, but Volumio won’t show up as a selectable option in my phone when using Spotify. The strange thing is, if I start playing a song from Spotify inside the Volumio app it’s working, and then when I open the Spotify app Volumio is suddenly selected as source? But without starting in Volumio app first, I don’t get the option in Spotify…
Any idea?
Hi everyone. I’ve been silent for a long time because frankly I hated to come here promising improvements when we had no viable options. So I took a different route, got to work hard in the background.
Finally, I have a very, very good news to share.
Over the summer we have been working on a total rewrite of the plugin (both of the daemon and the plugin itself). And finally, this week, we have a version where we are really satisfied.
It just works. 1000 times better than the current plugin.
To avoid any confusion and commotion, we are performing the last QA and final bugfixing in order to release it when it is fully ready for battle testing, and then hopefully releasing to everyone shortly after.
Thanks everyone for your patience. We made it a point of honour to get this plugin to the best possible shape. We care about it and about all Volumio users.
Stay tuned!
Thanks Volumio and Dev’s for the great efforts!!!.
are the use cases used to do the rewrite public?
What do you mean?
program specs, test cases, function list, plans etc
sorry my terminology maybe regional or outdated.
documents that you use to test the program against to prove it provides the functions people will use
ex. add local music files and spotify songs in queue and they all play.
this worked in the old plugin but does not work in the current version.
just looking for something to read until the finish plugin is released
I can use Spotify Connect from my phone, but when I use Spotify Windows App (v 1.220.1216.0) to connect to my local LAN Volumio player, it shows green for about 2 seconds, then kicks back to black and plays via local computer.
Welcome to Volumio for Raspberry Pi (5.10.92-v7+ armv7l)
volumio@volumio-allo-digione:~$ cat /sys/firmware/devicetree/base/model
Raspberry Pi 3 Model B Plus Rev 1.3volumio@volumio-allo-digione:~$
The Spotify Plugin on Volumio web GUI shows 3.0.9.
Here are couple of screen grabs of the spot in the Windows App
The little icon just won’t turn green and connect!
That is awesome!! Thanks for all the hard work. Is there a place we can see if the bugs we reported have been fixed?
specifically:
Excited for battle testing as soon as it is available!!
omg so happy to hear this! the poor spotify plugin has been a real paint point for many, so very excited to try the new version!
Almost there
Internal QA is done. Now next QA with the mods and devs group
If that goes well, release is very very near
i can’t wait for it Most of my friends depend on this is working.
any chance to get into the magic circle for testing ?
Best Regards
Josef
Volumio Version: 3.512
Hardware: Rasp PI 4B
DAC: HiFiBerry Digi Pro
info: CoreStateMachine::play index undefined
info: CoreStateMachine::setConsumeUpdateService undefined
info: CorePlayQueue::getTrack 1
info: CoreStateMachine::startPlaybackTimer
info: CorePlayQueue::getTrack 1
info: [1696772576367] ControllerSpotify::clearAddPlayTrack
info: CoreCommandRouter::volumioGetQueue
info: CoreStateMachine::getQueue
info: CorePlayQueue::getQueue
info: Setting this device active
info: [GPIO_Control] *** musicStop ***
info: [GPIO_Control] Delaying: 0ms
info: [GPIO_Control] Turning GPIO 12 Off (musicStop)
info: touch_display: Setting screensaver timeout to 0 seconds.
[Vollibrespot] : Fetching autoplay context uri
[Vollibrespot] : Event: TrackChanged { old_track_id: SpotifyId { id: 6597951733573032606610955304546343246, audio_type: Track }, track_id: SpotifyId { id: 6597951733573032606610955304546343246, audio_type: Track } }
info: CoreCommandRouter::volumioGetState
info: CorePlayQueue::getTrack 1
[Vollibrespot] : error 400 for uri hm://autoplay-enabled/query?uri=
[Vollibrespot] : AutoplayError: MercuryError
info: touch_display: Using Xserver unix domain socket /tmp/.X11-unix/X0
info: touch_display: Setting screensaver timeout to 0 seconds.
[Vollibrespot] : Pause
[Vollibrespot] : Event: PlaybackStopped { track_id: SpotifyId { id: 6597951733573032606610955304546343246, audio_type: Track } }
[SpotifyConnect] Cradled
[SpotifyConnect] Pause
[SpotifyConnect] PlaybackInactive
[Vollibrespot] : Fetching autoplay context uri
[Vollibrespot] : Event: TrackChanged { old_track_id: SpotifyId { id: 6597951733573032606610955304546343246, audio_type: Track }, track_id: SpotifyId { id: 214137770048703878492574283710770164039, audio_type: Track } }
[Vollibrespot] : error 400 for uri hm://autoplay-enabled/query?uri=
[Vollibrespot] : AutoplayError: MercuryError
[Vollibrespot] : Loading with Spotify URI
[Vollibrespot] : (1440013 ms) loaded
[Vollibrespot] : Alsa error PCM open ALSA function 'snd_pcm_hw_params_set_buffer_size_near' failed with error 'EINVAL: Invalid argument'
[Vollibrespot] : Could not start audio: Alsa error: PCM open failed
[Vollibrespot] : Alsa error PCM open ALSA function 'snd_pcm_hw_params_set_buffer_size_near' failed with error 'EINVAL: Invalid argument'
[Vollibrespot] : Could not start audio: Alsa error: PCM open failed
[Vollibrespot] : Pause
[Vollibrespot] : Event: PlaybackLoading { track_id: SpotifyId { id: 214137770048703878492574283710770164039, audio_type: Track } }
[Vollibrespot] : Event: Pause { track_id: SpotifyId { id: 214137770048703878492574283710770164039, audio_type: Track }, position_ms: 43 }
[SpotifyConnect] Octavarium
[SpotifyConnect] Pause
[SpotifyConnect] Device palyback is loading
[SpotifyConnect] pause
[Vollibrespot] : Alsa error PCM open ALSA function 'snd_pcm_hw_params_set_buffer_size_near' failed with error 'EINVAL: Invalid argument'
[Vollibrespot] : Could not start audio: Alsa error: PCM open failed
thread '' panicked at 'called `Option::unwrap()` on a `None` value', /build/cache/git/checkouts/librespot-6f197fd632ef9380/08d8bcc/playback/src/audio_backend/alsa.rs:129:35
stack backtrace:
0: 0x9b8444 - std::backtrace_rs::backtrace::libunwind::trace::h40a4eff66330a36d
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/../../backtrace/src/backtrace/libunwind.rs:93:5
1: 0x9b8444 - std::backtrace_rs::backtrace::trace_unsynchronized::hbce01963451b0cd5
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
2: 0x9b8444 - std::sys_common::backtrace::_print_fmt::h95da650d09c7e00b
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:66:5
3: 0x9b8444 - ::fmt::h33b23b1d14f668ff
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:45:22
4: 0x9e10dc - core::fmt::write::h6320fb0e6ac90e58
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/fmt/mod.rs:1190:17
5: 0x9b04c4 - std::io::Write::write_fmt::h33b25d4810ca481f
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/io/mod.rs:1657:15
6: 0x9baef4 - std::sys_common::backtrace::_print::h7e61c5be69c715ef
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:48:5
7: 0x9baef4 - std::sys_common::backtrace::print::h3cee176d7c8dab8b
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:35:9
8: 0x9baef4 - std::panicking::default_hook::{{closure}}::h2d0211dd2e97dc43
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:295:22
9: 0x9bab14 - std::panicking::default_hook::hcbdb3b7c40dca30c
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:314:9
10: 0x9bb694 - std::panicking::rust_panic_with_hook::h4ce49e7a343dc12b
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:698:17
11: 0x9bb360 - std::panicking::begin_panic_handler::{{closure}}::h4961100fae529fe9
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:586:13
12: 0x9b89c4 - std::sys_common::backtrace::__rust_end_short_backtrace::hf2e68e62c7a80f1f
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys_common/backtrace.rs:138:18
13: 0x9bb098 - rust_begin_unwind
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/panicking.rs:584:5
14: 0x49e6f4 - core::panicking::panic_fmt::h84c42730e4a50809
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/panicking.rs:143:14
15: 0x49e5c8 - core::panicking::panic::h929d4344847bfdba
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/core/src/panicking.rs:48:5
16: 0x5d9158 - ::write::h2857e81996e06a1e
17: 0x5bb814 - ::poll::hf6331a81451dbb28
18: 0x4e36c0 - futures::task_impl::std::set::hb731921744f9247e
19: 0x4d4708 - futures::task_impl::Spawn::poll_future_notify::h08f2c87ba9a4eead
20: 0x4e8158 - std::sys_common::backtrace::__rust_begin_short_backtrace::hb598e9d2970dbf13
21: 0x514e70 - core::ops::function::FnOnce::call_once{{vtable.shim}}::h7f140b0cfa5289e1
22: 0x9bfebc - as core::ops::function::FnOnce>::call_once::hbc4d03a1815e028a
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/alloc/src/boxed.rs:1853:9
23: 0x9bfebc - as core::ops::function::FnOnce>::call_once::h6055603e421418e8
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/alloc/src/boxed.rs:1853:9
24: 0x9bfebc - std::sys::unix::thread::Thread::new::thread_start::h0518d9d0e6b0ba31
at /rustc/7737e0b5c4103216d6fd8cf941b7ab9bdbaace7c/library/std/src/sys/unix/thread.rs:108:17
info: Is Not Connect Playback
info: [1696772577471] ControllerSpotify::pushState
info: CoreCommandRouter::servicePushState
info: CorePlayQueue::getTrack 1
info: CoreStateMachine::syncState stateService play
info: CoreStateMachine::syncState currentStatus stop
[SpotifyConnect] Octavarium
info: Is Not Connect Playback
info: [1696772577948] ControllerSpotify::pushState
info: CoreCommandRouter::servicePushState
info: CorePlayQueue::getTrack 1
An update will be released soon
Hi, so as it seems, that there are a lot of people having interesting issues with this plugin (and I think not too less people use Spotify here) - a more “precise” timeframe than soon would help us during this time suffering with this and that issue…
Also in case you need testers - please let me know, could not be worser than now
The post above from @volumio is as precise in terms of a robust testing schedule as can reasonably be expected. There’s no point in giving an exact release date until this stage of testing is completed satisfactorily.
"Internal QA is done. Now next QA with the mods and devs group.
If that goes well, release is very very near"
hi
I am using volumio 3.512 on a raspberry pi with spotify plugin 3.0.9.
I was just wondering if it is to be expected that this spotify plugin falters so often: I will for instance select an album to play, and after perhaps 4 tracks it will just stop. This happens very often.
Is that “normal” or can I perhaps try to do something about it?
regards, Danny.