Forum Replies Created
-
Posted in: Allo USB Bundle
-
26. Mai 2018 at 15:23 #35898
Hello again
My license has again become invalid 🙁
Should not remain active for customers?Cheers, Paul
7. April 2018 at 14:33 #35045Looks as though it was an issue with the speaker Heiner.
Tried hooking up to a friends JBL Pulse with no issue.
Thanks for your help & patience.Cheers, Paul
5. April 2018 at 23:00 #35016Hopefully be able to get my hands on one over the weekend Heiner.
Can I ask if the LOGILINK BLUETOOTH ADAPTER you offer is a BT0015 or a BT0037?Cheers, Paul
1. April 2018 at 14:18 #34924Hello again Heiner, no joy I’m afraid 🙁
Here’s the process I followedScan for Bluetooth devices
Following Bluetooth Devices found: SoundCore mini 00:E0:4C:E5:94:51: Connect
Connecting to: 00:E0:4C:E5:94:51
Agent registered
Device: SoundCore mini (00:E0:4C:E5:94:51)
Confirm passkey: 691538 (yes/no)? Trusted: 0 -> 1
[00:E0:4C:E5:94:51]
Name: SoundCore mini
Alias: SoundCore mini [rw]
Address: 00:E0:4C:E5:94:51
Icon: audio-card
Class: 0x240404
Paired: 0
Trusted: 1 [rw]
Blocked: 0 [rw]
Connected: 1
UUIDs: []
YOU PROBABLY NEED TO RESTART your AUDIOPLAYER (e.g. Squeezelite) to get it to work with Bluetooth!Squeezelite Advanced Options edited so that Soundcard Audio Output is: bluetoothspeaker
Debug Information
#### SQUEEZELITE VERSION ####
Squeezelite v1.8, Copyright 2012-2015 Adrian Smith.
#### SQUEEZELITE BUILDOPTIONS ####
Build options: LINUX ALSA EVENTFD RESAMPLE FFMPEG VISEXPORT DSD
#### AUDIOPLAYER CONFIG ####
### Configuration of Audioplayers
SQUEEZELITE_PARAMETER=-o bluetoothspeaker -a 80:4::
SHAIRPORT_PARAMETER=-d bluetoothspeaker
USE_USB_DAC=0
USE_EQUALIZER=0
SYSTEM_USER=pi
GMEDIARENDER_ALSA_DEVICE=plug:plugequal
#### SQUEEZELITE -l ####
Output devices:
null – Discard all samples (playback) or generate zero samples (capture)
plugequal – Equalizer for plughw:0,0
bluetoothspeaker – Max2Play bluetooth speaker
default:CARD=sndrpihifiberry – snd_rpi_hifiberry_amp, – Default Audio Device
sysdefault:CARD=sndrpihifiberry – snd_rpi_hifiberry_amp, – Default Audio Device
default:CARD=ALSA – bcm2835 ALSA, bcm2835 ALSA – Default Audio Device
sysdefault:CARD=ALSA – bcm2835 ALSA, bcm2835 ALSA – Default Audio Device
#### SHAIRPORT (SYNC) VERSION ####
2.2.4-openssl-Avahi-ALSA-soxr
#### OUTPUT SOUND DETAILS CARD 0 ####
closed
#### OUTPUT SOUND DETAILS CARD 1 ####
closedHowever I’m unable to restart Squeezelite:
Trying to launch … NOT successful Click here to show detailed information
[13:14:43.538497] test_open:294 playback open error: Input/output error
[13:14:43.538945] output_init_common:381 unable to open output deviceHopefully this may give you a clue as to the problem.
Cheers, Paul
- This reply was modified 6 years, 8 months ago by Paden.
29. März 2018 at 17:41 #34906Thanks Heiner, will do as you suggest at the weekend 🙂
Am currently using version 2.45 on a Raspberry PI 2, is the Stretch image compatible with this device?Cheers, Paul
28. März 2018 at 22:46 #34851Thanks for your continued support Heiner.
„you were apparently able to connect with the speakers you use“ – to clarify, I was not able to connect from the max2play software although the speaker was visible (unless this is what you mean).
I will try testing playback with the bluealsa output as you suggest.
Are there any other Bluetooth devices I could attempt to connect to for test purposes?Cheers, Paul
26. März 2018 at 22:14 #34767Hello again Heiner
To clarify, I was able to successfully pair with the speaker from both my phone & tablet.
When attempting to pair max2play with both phone & tablet, although each were visible, connection was not possible.
I did not try pairing in the opposite direction i.e. from my phone or tablet.Cheers, Paul
24. März 2018 at 18:49 #34715Hi Heiner, many thanks for the reply.
There isn’t an option on the speaker for pairing,
However I have tried to pair both my phone & tablet without success.
In max2play:
Scan For Bluetooth Devices
Following Bluetooth Devices found: XXX
Connect
Bluetooth Pairing Request code received on device
Request confirmed on device
Connection fails
Do you think it might be a dongle issue?Cheers, Paul
18. März 2018 at 15:34 #34511Hey all
Trying to connect to a Bluetooth speaker which although is visible I’ve been unable to pair.
I’m using a Raspberry PI 2 (Version 2.45), with a Vitalitim B01 Bluetooth 4.0 USB Low Energy Micro Adapter Dongle.
Here is the report from the Bluetooth Setup Page with the DEBUG Information:Connecting to: 00:E0:4C:E5:94:51
Agent registered
Device: SoundCore mini (00:E0:4C:E5:94:51)
Confirm passkey: 369057 (yes/no)? Trusted: 0 -> 1
[00:E0:4C:E5:94:51]
Name: SoundCore mini
Alias: SoundCore mini [rw]
Address: 00:E0:4C:E5:94:51
Icon: audio-card
Class: 0x240404
Paired: 0
Trusted: 1 [rw]
Blocked: 0 [rw]
Connected: 1
UUIDs: []
YOU PROBABLY NEED TO RESTART your AUDIOPLAYER (e.g. Squeezelite) to get it to work with Bluetooth!DEBUG Information
#### Bluetooth Installation ####
#### Bluetooth Dongle ####
hci0: Type: BR/EDR Bus: USB
BD Address: 00:1A:7D:DA:71:13 ACL MTU: 310:10 SCO MTU: 64:8
UP RUNNING
RX bytes:9460 acl:1 sco:0 events:135 errors:0
TX bytes:1405 acl:0 sco:0 commands:89 errors:0Any help appreciated 🙂
Cheers, Paul
24. Mai 2017 at 21:04 #29060Thanks for your help Mohammad , reformatting the drive has solved the issue 🙂
Cheers, Paul
22. März 2017 at 22:16 #27833Hi Mohamamd, thanks for the reply, although I’m unclear as to what hasn’t been configured.
I’ve mounted the drives under:
External Drives on Max2Play – mountpoints for USB-Storage
Which in turn automatically populated:
Filesystem – mount network paths (Samba or NFS)
The „type“ automatically detected is vfat, could it be that the drive is not formatted in the correct format?
Like I said all works fine until a reboot.Cheers, Paul
-