hanoba

Forum Replies Created

Viewing 10 posts - 1 through 10 (of 10 total)
  • Back to forum
    Posted in: Allo USB Bundle
  • hanoba premium
    12. Dezember 2017 at 10:14 #32878

    Snapcast (https://github.com/badaix/snapcast/) is an open source synchronous multi-room audio player. It cannot be used with Max2Play.

    • This reply was modified 6 years, 11 months ago by hanoba.
    hanoba premium
    11. Dezember 2017 at 19:16 #32870

    I was not able to solve the BT problem that I had (I used MAX2PLAY as BT sink/receiver – see above #32549).
    I guess there is simply a bug in the MAX2PLAY BT plugin.
    Meanwhile I am using SnapCast for my multi-room system. With SnapCast the audio playback is stable for hours when streaming via BT.

    hanoba premium
    29. November 2017 at 23:44 #32712

    Hi Heiner,

    Please find the debug info below.
    The playback stopped after 35 minutes. I used no Wifi and the Beta-171123 SW.

    BR Harald

    Service_shell_exec (0.012102127075195 sec): cat /opt/max2play/playername.txt
    Service_shell_exec (0.014658212661743 sec): grep -i „^Max2PlayNetworkLookup=1“ /opt/max2play/autostart.conf
    Service_shell_exec (0.015033960342407 sec): grep -aP „^[ \t]*removedonate[ \t]*\=“ /opt/max2play/options.conf | sed -n -e „s/^[ \t]*[A-Za-z_0-9\.]*\=//p“
    Service_shell_exec (0.015793085098267 sec): cat /proc/cpuinfo | grep ‚Hardware\|Revision‘
    Service_shell_exec (0.015537023544312 sec): grep -aP „^[ \t]*license[ \t]*\=“ /opt/max2play/options.conf | sed -n -e „s/^[ \t]*[A-Za-z_0-9\.]*\=//p“
    Service_shell_exec (0.016083002090454 sec): grep -aP „^[ \t]*license[ \t]*\=“ /opt/max2play/options.conf | sed -n -e „s/^[ \t]*[A-Za-z_0-9\.]*\=//p“
    Bluetooth_shell_exec (0.015780925750732 sec): grep -aP „^[ \t]*license[ \t]*\=“ /opt/max2play/options.conf | sed -n -e „s/^[ \t]*[A-Za-z_0-9\.]*\=//p“
    Bluetooth_shell_exec (0.22246098518372 sec): lsb_release -a 2>/dev/null | grep „Distributor\|Codename“ | sed „s/Distributor ID:\t//;s/Codename:\t//“
    Bluetooth_shell_exec (0.0085458755493164 sec): grep -aP „^[ \t]*BLUETOOTH_MACADDRESS_MAINPLAYER[ \t]*\=“ /opt/max2play/audioplayer.conf | sed -n -e „s/^[ \t]*[A-Za-z_0-9\.]*\=//p“
    Bluetooth_shell_exec (0.0087761878967285 sec): grep -aP „^[ \t]*PLUSEBLUETOOTH_DEBUG[ \t]*\=“ /opt/max2play/autostart.conf | sed -n -e „s/^[ \t]*[A-Za-z_0-9\.]*\=//p“
    Bluetooth_shell_exec (0.0085070133209229 sec): grep -aP „^[ \t]*readonly[ \t]*\=“ /opt/max2play/options.conf | sed -n -e „s/^[ \t]*[A-Za-z_0-9\.]*\=//p“
    Bluetooth_dynamic_script (0.082557916641235 sec): #!/bin/bash

    /usr/bin/bt-device -l
    Bluetooth_dynamic_script (0.0936119556427 sec): #!/bin/bash

    /usr/bin/bt-device -i ‚Echo-ESK‘
    Bluetooth_dynamic_script (0.042471885681152 sec): #!/bin/bash

    hciconfig
    Bluetooth_dynamic_script (0.11969685554504 sec): #!/bin/bash

    su -l pi -c „pacmd list | grep active“
    Bluetooth_dynamic_script (0.14293503761292 sec): #!/bin/bash

    su -l pi -c „pacmd list | grep sink“
    Bluetooth_dynamic_script (0.097270011901855 sec): #!/bin/bash

    ps -Al | grep lxsession | wc -l
    Bluetooth_dynamic_script (0.11297202110291 sec): #!/bin/bash

    su -l pi -c „pacmd list-cards“
    Bluetooth_shell_exec (0.0082709789276123 sec): grep -i „^bluetooth=1“ /opt/max2play/autostart.conf
    Bluetooth_shell_exec (0.0089459419250488 sec): grep -i „^PLUSEBLUETOOTH_AUTOSTART_SBS=1“ /opt/max2play/autostart.conf
    Service_shell_exec (0.0088820457458496 sec): grep -aP „^[ \t]*showHelpOnSidebar[ \t]*\=“ /opt/max2play/options.conf | sed -n -e „s/^[ \t]*[A-Za-z_0-9\.]*\=//p“

    ———————————————————–
    #### Bluetooth Installation ####

    #### Bluetooth Dongle ####
    hci0: Type: BR/EDR Bus: UART
    BD Address: B8:27:EB:82:FC:8A ACL MTU: 1021:8 SCO MTU: 64:1
    UP RUNNING
    RX bytes:109748335 acl:183695 sco:0 events:225 errors:0
    TX bytes:4991 acl:91 sco:0 commands:104 errors:0

    #### DEVICE Echo-ESK ####
    [34:D2:70:24:17:4E]
    Name: Echo-ESK
    Alias: Echo-ESK [rw]
    Address: 34:D2:70:24:17:4E
    Icon: audio-card
    Class: 0xc0414
    Paired: 1
    Trusted: 1 [rw]
    Blocked: 0 [rw]
    Connected: 1
    UUIDs: [AudioSource, AudioSink, AdvancedAudioDistribution, AVRemoteControl, PnPInformation, 4e72b490-1d0f-bf92-0e47-a84e01000000]

    #### PACMD LIST | grep active ####
    active port: <analog-output>
    active port: <analog-output>
    active profile: <output:analog-stereo>
    active profile: <output:analog-stereo>
    active profile: <off>

    #### PACMD LIST | grep sink ####
    Default sink name: null
    name: <module-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 = „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“
    3 sink(s) available.
    driver: <module-null-sink.c>
    driver: <module-null-sink.c>
    sinks:
    sinks:
    0 sink input(s) available.

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

    #### PULSEAUDIO RUNNING ####
    1 S 1000 1220 1 21 80 0 – 30450 – ? 00:11:41 pulseaudio
    0 S 1000 1514 1 0 80 0 – 18634 – ? 00:00:00 pulsebluetooth

    #### BLUETOOTH SQUEEZEBOX SERVER AUTOSTART ####
    Socket created
    Sending : path ?
    Lastpath: wavin%3Abluez_source.34_D2_70_24_17_4E

    Socket created
    Sending : playlist insert wavin:bluez_source.34_D2_70_24_17_4E
    Socket created
    Sending : playlist index +1
    Socket created
    Sending : playlist play

    #### PACMD LIST-CARDS | DEBUG COMPLETE ####
    3 card(s) available.
    index: 0
    name: <alsa_card.platform-soc_audio>
    driver: <module-alsa-card.c>
    owner module: 7
    properties:
    alsa.card = „0“
    alsa.card_name = „bcm2835 ALSA“
    alsa.long_card_name = „bcm2835 ALSA“
    alsa.driver_name = „snd_bcm2835“
    device.bus_path = „platform-soc:audio“
    sysfs.path = „/devices/platform/soc/soc:audio/sound/card0“
    device.string = „0“
    device.description = „bcm2835 ALSA“
    module-udev-detect.discovered = „1“
    device.icon_name = „audio-card“
    profiles:
    output:analog-mono: Analog Mono Output (priority 100, available: unknown)
    output:analog-stereo: Analog Stereo Output (priority 6000, available: unknown)
    off: Aus (priority 0, available: unknown)
    active profile: <output:analog-stereo>
    sinks:
    alsa_output.platform-soc_audio.analog-stereo/#1: bcm2835 ALSA Analog Stereo
    sources:
    alsa_output.platform-soc_audio.analog-stereo.monitor/#1: Monitor of bcm2835 ALSA Analog Stereo
    ports:
    analog-output: Analoge Ausgabe (priority 9900, latency offset 0 usec, available: unknown)
    properties:

    index: 3
    name: <alsa_card.platform-soc_sound>
    driver: <module-alsa-card.c>
    owner module: 31
    properties:
    alsa.card = „1“
    alsa.card_name = „snd_rpi_hifiberry_dacplus“
    alsa.long_card_name = „snd_rpi_hifiberry_dacplus“
    alsa.driver_name = „snd_soc_hifiberry_dacplus“
    device.bus_path = „platform-soc:sound“
    sysfs.path = „/devices/platform/soc/soc:sound/sound/card1“
    device.string = „1“
    device.description = „snd_rpi_hifiberry_dacplus“
    module-udev-detect.discovered = „1“
    device.icon_name = „audio-card“
    profiles:
    output:analog-stereo: Analog Stereo Output (priority 6000, available: unknown)
    off: Aus (priority 0, available: unknown)
    active profile: <output:analog-stereo>
    sinks:
    alsa_output.platform-soc_sound.analog-stereo/#2: snd_rpi_hifiberry_dacplus Analog Stereo
    sources:
    alsa_output.platform-soc_sound.analog-stereo.monitor/#4: Monitor of snd_rpi_hifiberry_dacplus Analog Stereo
    ports:
    analog-output: Analoge Ausgabe (priority 9900, latency offset 0 usec, available: unknown)
    properties:

    index: 4
    name: <bluez_card.34_D2_70_24_17_4E>
    driver: <module-bluez5-device.c>
    owner module: 32
    properties:
    device.description = „Echo-ESK“
    device.string = „34:D2:70:24:17:4E“
    device.api = „bluez“
    device.class = „sound“
    device.bus = „bluetooth“
    device.form_factor = „speaker“
    bluez.path = „/org/bluez/hci0/dev_34_D2_70_24_17_4E“
    bluez.class = „0x0c0414“
    bluez.alias = „Echo-ESK“
    device.icon_name = „audio-speakers-bluetooth“
    profiles:
    a2dp_source: High Fidelity Capture (A2DP Source) (priority 10, available: unknown)
    a2dp: High Fidelity Playback (A2DP Sink) (priority 10, available: unknown)
    off: Aus (priority 0, available: yes)
    active profile: <off>
    ports:
    speaker-output: Speaker (priority 0, latency offset 0 usec, available: no)
    properties:

    speaker-input: Bluetooth Input (priority 0, latency offset 0 usec, available: unknown)
    properties:

    hanoba premium
    28. November 2017 at 18:59 #32682

    Hi Heiner,

    I have tested this: Wifi was deactivated (ethernet cable) and the distance between M2P/Raspi and Alexa was only about 40 cm.
    Also with this setup the playback stopped after some time.

    It would be good if you could try to reproduce the problem in your lab: Just stream for several hours music from Amazon Echo to your BT plugin.

    BR Harald

    hanoba premium
    26. November 2017 at 1:19 #32640

    Update: In new tests I made today with the the M2P beta SW 171115 (which once worked for 1.5h), the playback stopped already after about 20 minutes. After disconnecting/connecting BT and pressing stop/start the playback worked again.

    Conditions were as before:
    – distance between Echo and Pi to 40cm
    – Pi WLAN off (using ethernet cable)

    hanoba premium
    23. November 2017 at 22:33 #32610

    I installed the BT plugin from your website last Saturday. I guess this is the latest official version.

    hanoba premium
    21. November 2017 at 23:08 #32580

    One additional comment: In the thread https://www.max2play.com/en/forums/topic/bluetooth-addon-beta/ several other people reported problems when streaming from Echo to RPI!

    hanoba premium
    21. November 2017 at 23:01 #32579

    Hi Heiner,

    Thanks a lot for your answer.

    Regarding your question: The phone was closer to the Pi than the Echo!

    Meanwhile I made more tests:
    – I noticed that also streaming from the phonestopped after about 20 minutes
    – I reduced the distance between Echo and Pi to 40cm. In this case the streaming stopped only after ~20 minutes
    – I streamed my Amazon Echo via BT to an Ubuntu server (3m distance) with a loop from BT input loop to HDMI audio output. Everything was stable for several hours!
    – Yesterday, I tried the M2P beta SW 171115. The streaming worked for 1.5 hours! When I checked again after 2.5 hours the streaming was stopped. The BT connection was still active. After disconnecting/connecting BT the streaming worked again.

    My assumption is that there is a bug in the M2P BT plugin! Whenever there is a short BT connection problem (which can always happen due to WiFi/BT interference) then the plugin stops working. The problem seems to be improved in the beta SW, but it is not completely solved.

    Did you test your BT plugin in your lab with Amazon Echo running for several hours with a Wifi interference from neighboring access points?

    Thanks and regards

    Harald

    hanoba premium
    20. November 2017 at 14:24 #32549

    I have the same problem as several people in this thread: When streaming music from Amazon Echo to RPI3/M2P, the Squeezebox server stops after 3-20 minutes. After disconnecting and reconnecting the BT link it works again for some time, but then it stops again.

    When I stream my Amazon Echo via BT to an Ubuntu server not running M2P (with a loop from BT input loop to HDMI audio output) everything is stable for hours!

    My assumption is that there is a bug in the M2P BT plugin! Whenever there is a short BT connection problem (which can always happen due to WiFi interference) then the plugin stops working.


    @Heiner    : Did you ever test your BT plugin with Amazon Echo running for several hours with a Wifi interference from neighboring access points?

    Thanks and regards

    Harald

    hanoba premium
    19. November 2017 at 12:47 #32534

    I have the same problem with my Amazon Echo, but it works with my iPhone 6+. I installed the latest max2play yesterday (Version 2.44 on RPI 3).

    @Heinzrumpel: Did you solve this issue?

    Thanks and regards

    Harald

Viewing 10 posts - 1 through 10 (of 10 total)