bkonijn

Forum Replies Created

Viewing 7 posts - 1 through 7 (of 7 total)
  • Back to forum
    Posted in: Allo USB Bundle
  • bkonijn premium
    28. September 2018 at 22:06 #38232

    Hi, I recently installed M2P and bluetooth plugin on a Zero W. I cannot start the bluetooth soundcard in Squeezelite:

    Trying to launch … NOT successful Click here to show detailed information
    ../../../src/asound/../shared/ctl-client.c:105: Connecting to socket: /var/run/bluealsa/hci0
    [22:01:39.438294] test_open:384 playback open error: No such file or directory
    [22:01:39.438797] output_init_common:382 unable to open output device

    And I cannot connect to my bluetooth speaker:

    Device 40:EF:4C:31:82:94 sonoroRADIO
    trust 40:EF:4C:31:82:94
    Changing 40:EF:4C:31:82:94 trust succeeded
    pair 40:EF:4C:31:82:94
    Attempting to pair with 40:EF:4C:31:82:94
    Failed to pair: org.bluez.Error.AlreadyExists
    connect 40:EF:4C:31:82:94
    Attempting to connect to 40:EF:4C:31:82:94
    Failed to connect: org.bluez.Error.Failed
    quit
    Name: sonoroRADIO
    Address: 40:EF:4C:31:82:94
    Icon: audio-card
    Class: 0x240414
    Paired: 1
    Connected: 0

    Also updated to beta, but still no success…

    bkonijn premium
    2. März 2017 at 12:08 #27392

    Hm, I requested the key a couple of months ago. I understand the request form still works, but I didn’t try…

    bkonijn premium
    1. März 2017 at 21:49 #27384

    Not sure what might be the problem 😉 I am not an expert and it took me at least several hours of googling etc. to get it working. Strictly following the steps in the video is not enough, unfortunately. I had to manually copy the newest ‚commits‘ to prevent SCS from blocking the hifiberry soundcard (that might be the issue). I use „-C 1“ in squeezeplayer, which means that it unblocks the soundcard if it is not playing after 1 second.

    This is exactly why we need Max2play to integrate SCS into their solution 😉

    bkonijn premium
    28. Februar 2017 at 14:22 #27335

    Mit spotify-connect wird die Musik nicht durch Squeezebox Server gestreamt, die Musik ist dann nur auf dem einen Pi hörbar.

    bkonijn premium
    27. Februar 2017 at 22:06 #27294

    Update:
    I managed to implement Spotify Connect on my Max2Play Raspberry Pi + HifiBerry following this instruction: https://www.youtube.com/watch?v=qqMzXmvW4T8 I think other instructions are available as Well.

    I use it in combination with Max2play Squeezelite player. I can switch between spotify-connect and Squeezelite. If you use the newest commits of spotify-connect (especially Pull #18 https://github.com/Fornoth/spotify-connect-web/pull/18) in combination with the -C option in Squeezelite player, the hifiberry audiocard is released by the audioplayer (spotify-connect or Squeezelite) when it is not playing. This works fine.

    bkonijn premium
    27. November 2016 at 11:55 #24280

    Hi,

    I managed to implement Spotify Connect on my Max2Play Raspberry Pi + HifiBerry following this instruction: https://www.youtube.com/watch?v=qqMzXmvW4T8

    The only problem is that both try to use the same output device, I get an error when I try to start Squeezelight:
    [10:35:50.562781] test_open:294 playback open error: Invalid argument
    [10:35:50.563179] output_init_common:381 unable to open output device

    Maybe a solution to switch between players sharing the same output device (similar to MultiShairport) is possible?

    bkonijn premium
    6. August 2016 at 21:26 #22068

    I also think it would be great (!) to implement Spotify Connect as part of max2play.

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