[davey_boi premium]

davey_boi premium

18. Januar 2019 at 10:08 #43873

This is the same issue I have. Running Rasp pi and IQAudio with Max2play Spotify connect on premium account. Spotty works fine through LMS (havent tried spotify connect through LMS – apparently is an option) but i wanted to switch to using Spotify connect directly on Max2play using the plugin. It works for a few days then the Raspi disappears from devices i can connect to in spotify app. I find that the issue can happen and spotify connect is service stays running but on the last occasion it has stopped. Log talks about panicking and something about rust…

I have the hw card select for audio output in spotify connect settings. Also have command line option: –initial-volume 50.
Also shairport is not set to autostart (squeezelite is).

Tried re-installing Spotify connect plugin but not full Max2play re-install (yet) to no avail. Is there any obvious solution that I am overlooking or should I try re-installing a complete fresh install?

I thought maybe it might be to do with something else taking the access to the audio card but the only thing is squeezelite which is also set up but the issue happens without me playing anything on Squeezelite (maybe having it running is the issue)?

Log file:
INFO:librespot_playback::player: Loading track „One Love“ with Spotify URI „spotify:track:3VGggSf2S6P3779YgPjYEW“
INFO:librespot_playback::player: Track „One Love“ loaded
thread ‚main‘ panicked at ‚connection closed‘, libcore/option.rs:914:5
stack backtrace:
0: 0x9cb9ab – std::sys::unix::backtrace::tracing::imp::unwind_backtrace::h9a3642c9f6f9c72d
at libstd/sys/unix/backtrace/tracing/gcc_s.rs:49
1: 0x9d4b47 – std::sys_common::backtrace::print::h857488e4ca7f183a
at libstd/sys_common/backtrace.rs:71
at libstd/sys_common/backtrace.rs:59
2: 0x9ba3c7 – std::panicking::default_hook::{{closure}}::h69d8f4842e718136
at libstd/panicking.rs:211
3: 0x9ba057 – std::panicking::default_hook::h6dcc687f188bf47f
at libstd/panicking.rs:227
4: 0x9baadb – std::panicking::rust_panic_with_hook::hc321908595307e8d
at libstd/panicking.rs:463
5: 0x9ba617 – std::panicking::begin_panic_fmt::hc982e1fd1fa0bf7c
at libstd/panicking.rs:350
6: 0x9ba5df – rust_begin_unwind
at libstd/panicking.rs:328
7: 0xa1a3b3 – core::panicking::panic_fmt::h604cff786c7fe009
at libcore/panicking.rs:71
8: 0xa23317 – core::option::expect_failed::h5d2f9fad1c053e1a
at libcore/option.rs:914
9: 0x5fa1f3 – <librespot_core::session::DispatchTask<S> as futures::future::Future>::poll::hd19e7eab5344521d
10: 0x66d343 – <futures::future::join::Join<A, B> as futures::future::Future>::poll::he0d34dc52a6dc15e
11: 0x68bbeb – <futures::future::map::Map<A, F> as futures::future::Future>::poll::h72914db6de5c0dc2
12: 0x6a432f – <futures::future::map_err::MapErr<A, F> as futures::future::Future>::poll::hff5a33e13aa63299
13: 0x8e7b3f – futures::task_impl::std::set::h11fbde663e9da23e
14: 0x8e5ee3 – <futures::task_impl::Spawn<T>>::poll_future_notify::h1f5dadf17dc6fed0
15: 0x8ea807 – tokio::executor::current_thread::CurrentRunner::set_spawn::hbea13e558bfa84f5
16: 0x8ef1d3 – <tokio::executor::current_thread::scheduler::Scheduler<U>>::tick::hd8a23f66e53862f4
17: 0x8e5ba7 – <scoped_tls::ScopedKey<T>>::set::hc32e64633834effa
18: 0x8f2603 – <std::thread::local::LocalKey<T>>::with::hf2008c182fa53f44
19: 0x8f1ccf – <std::thread::local::LocalKey<T>>::with::h613425a247458594
20: 0x8f20af – <std::thread::local::LocalKey<T>>::with::hb0b1f89fcde726c3
21: 0x8edc0b – tokio_core::reactor::Core::poll::h854a3e1b89a82b9b
22: 0x5033b7 – tokio_core::reactor::Core::run::ha4d6f8476bb012d1
23: 0x4fd57f – librespot::main::h95a6d9f6a736a6db
24: 0x51c1bf – std::rt::lang_start::{{closure}}::ha1ba30460373e372
25: 0x9ba51f – std::panicking::try::do_call::h7e51fbf12cacd474
at libstd/rt.rs:59
at libstd/panicking.rs:310
26: 0x9dbaab – __rust_maybe_catch_panic
at libpanic_unwind/lib.rs:105
27: 0x9bad4b – std::rt::lang_start_internal::h407c85f0b0630649
at libstd/panicking.rs:289
at libstd/panic.rs:374
at libstd/rt.rs:58
28: 0x4fe1bf – main
29: 0x76c92677 – __libc_start_main

#### Librespot Command Line Options ####
error: Required option ’name‘ missing
Usage: /opt/spotifyconnect/librespot [options]

Options:
-c, –cache CACHE Path to a directory where files will be cached.
–disable-audio-cache
Disable caching of the audio data.
-n, –name NAME Device name
–device-type DEVICE_TYPE
Displayed device type
-b, –bitrate BITRATE
Bitrate (96, 160 or 320). Defaults to 160
–onevent PROGRAM
Run PROGRAM when playback is about to begin.
-v, –verbose Enable verbose output
-u, –username USERNAME
Username to sign in with
-p, –password PASSWORD
Password
–proxy PROXY HTTP proxy to use when connecting
–disable-discovery
Disable discovery mode
–backend BACKEND
Audio backend to use. Use ‚?‘ to list options
–device DEVICE Audio device to use. Use ‚?‘ to list options if using
portaudio
–mixer MIXER Mixer to use
–initial-volume VOLUME
Initial volume in %, once connected (must be from 0 to
100)
–zeroconf-port ZEROCONF_PORT
The port the internal server advertised over zeroconf
uses.
–enable-volume-normalisation
Play all tracks at the same volume
–normalisation-pregain PREGAIN
Pregain (dB) applied by volume normalisation
–linear-volume
increase volume linear instead of logarithmic.

[davey_boi premium]

davey_boi premium

28. Dezember 2016 at 5:52 #25283

@flysurfer, Thanks for the info. Just to clarify, my intention is to use the Echo as a audio source to play to my Max2play, which is connected to ceiling speakers. That way I can be playing music but have the Echo interrupt with responses as necessary. It would be perfect for my home automation set up because I can add voice control but with the feeling that you are talking to your house.

Thanks. I’ll continue to follow this thread and report back if I find any solution.

[davey_boi premium]

davey_boi premium

27. Dezember 2016 at 4:33 #25255

I’m experiencing the same issue as @guybrush73 with an Amazon Echo Dot. I think there is something strange going on with the Echo based on the following issue:

– With Echo connected to Max2play (running LMS locally) the audio (Alexa’s voice) comes through with a massive delay (up to a couple of minutes, and sometimes not at all). Also LMS does not automatically start the bluetooth favourite – I have the select it manually.

Alternatively, I can connect an iPad to max2play and BT streaming happens almost instantly and the LMS bluetooth favourite automatically starts playing and resumes the previous when the phone is stopped. I’ve tried two different RPI2’s (one with Wolfson card and one with IQAudio – same issue for both).

I can connect the Echo to a commercial BT speaker and everything behaves without delays. There seems to be something unique about the Echo and Max2play connected together.

How do I confirm if Max2play is seeing the Echo as a source or an output? I’ve included my debug but I am not sure what to look for.

Does anyone else have any ideas on what the issue could be?

DEBUG included below (I replaced some ID’s with XXXX):

#### Bluetooth Installation ####

#### Bluetooth Dongle ####
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1A:7D:DA:71:14 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:97906905 acl:319725 sco:0 events:571 errors:0
TX bytes:11907 acl:367 sco:0 commands:106 errors:0

#### DEVICE iPad ####

#### DEVICE XXXX ####
[64:A3:CB:7C:7D:D8]
Name: XXXX
Alias: XXXX [rw]
Address: 64:A3:CB:7C:7D:D8
Icon: phone
Class: 0x7a020c
Paired: 1
Trusted: 1 [rw]
Blocked: 0 [rw]
Connected: 0
UUIDs: [00000000-deca-fade-deca-deafdecacafe, ServiceDiscoveryServer, AudioSource, AVRemoteControlTarget, AVRemoteControl, NAP, HandsfreeAudioGateway, PhoneBookAccess, 00001132-0000-1000-8000-00805f9b34fb, PnPInformation]

#### DEVICE Echo-JUQ ####
[88:71:E5:24:08:5F]
Name: Echo-JUQ
Alias: Echo-JUQ [rw]
Address: 88:71:E5:24:08:5F
Icon: audio-card
Class: 0x2c0414
Paired: 1
Trusted: 1 [rw]
Blocked: 0 [rw]
Connected: 1
UUIDs: [AudioSource, AudioSink, AVRemoteControlTarget, AdvancedAudioDistribution, AVRemoteControl, PnPInformation, 00001800-0000-1000-8000-00805f9b34fb, 00001801-0000-1000-8000-00805f9b34fb]

#### PACMD LIST | grep active ####
active port: <speaker-input>
active profile: <a2dp_source>

#### PACMD LIST | grep sink ####
Default sink name: null
name: <module-null-sink>
module.description = „Clocked NULL sink“
module.description = „When a bluetooth sink or source is added, load module-loopback“
module.description = „Automatically restore the default sink and source“
name: <module-always-sink>
module.description = „Always keeps at least one sink loaded even if it’s a null one“
module.description = „When a sink/source is idle for too long, suspend it“
module.description = „Load filter sinks automatically when needed“
module.description = „BlueZ 5 Bluetooth audio sink and source“
argument: <source=“bluez_source.88_71_E5_24_08_5F“ source_dont_move=“true“ sink_input_properties=“media.role=music“>
module.description = „Loopback from source to sink“
1 sink(s) available.
driver: <module-null-sink.c>
driver: <module-null-sink.c>
1 sink input(s) available.
sink: 0 <null>
module-stream-restore.id = „sink-input-by-media-role:music“

#### X-SERVER RUNNING ####
1

#### PULSEAUDIO RUNNING ####
0 S 1000 1249 1 0 80 0 – 18635 – ? 00:00:00 pulsebluetooth
1 S 1000 4723 1 0 80 0 – 25620 – ? 00:06:07 pulseaudio

#### BLUETOOTH SQUEEZEBOX SERVER AUTOSTART ####