flysurfer

Forum Replies Created

Viewing 30 posts - 91 through 120 (of 275 total)
1 2 3 4 5 … 8 9 10
  • Back to forum
    Posted in: Allo DigiOne and MiniBOSS now on Max2Play
  • flysurfer Moderator
    3. Januar 2017 at 15:59 #25407

    Thanks a lot for posting this info! I will change the code to fix it!

    Already added this to the current Beta version of Max2Play.

    All the Best,
    Stefan

    • This reply was modified 9 years, 6 months ago by flysurfer.
    flysurfer Moderator
    3. Januar 2017 at 13:41 #25384

    @TonyW: thanks for the detailled information! I just tested with your settings (enabled DTOverlay for hifiberry dac pro) and it is working for me (BT-adapter available). Just to make sure it is not because of insufficiant power: remove all other devices (usb-drives, display, etc.) from the Raspberry (maybe also remove the hifiberry card) and check if that solves the problem with bluetooth.

    @all: Bad BT-connection and playback errors (crackling sound, breaks) can be because of bad power supply and/or too many connected devices (usb-drives, display, etc.). You probably need a USB-Hub with an external power supply for USB-Drives and a strong power supply if a display is attached to your RPi. If you have your Pi in a solid metal case, this might also cause bad bluetooth signal and you may try an USB-Bluetooth dongle to improve the connection.

    flysurfer Moderator
    2. Januar 2017 at 17:32 #25367

    @all: Happy new Year!!!


    @TonyW    : as your Bluetooth Dongle (inbuild Bluetooth) seems not recognized: Have a look at the „Raspberry Pi Settings“ Page and see if Bluetooth is disabled. Is the Max2Play web interface header telling that you have a „Raspberry PI 3“? Maybe you are running on a RPi 2?


    @mnvelocitypilot    : the long list in your Squeezebox Server playlist and the bluetooth app, that “reasserts” itself, is triggered by the autostart of the Bluetooth („Autostart Bluetooth-Streaming in Squeezebox Server“). Disable this setting at the bottom of the Bluetooth page (restart RPi), and manually start the Bluetooth Stream in your Squeezebox Server to see if this works better. During testing I had a similar problem with the inbuild bluetooth on RPi 3, when the BT-signal was not very good. The dropping of the BT-signal and reconnects confuse the script, that checks for connected audiostreams and starts/stops the streaming in Squeezebox Server. You may try to place your smartphone right beside your PI and the problem is gone – or use an external Bluetooth stick with better performance to improve the distance. I will also try to improve the autostart script with some delays to react little slower, when a stream is interrupted – this should solve it in the next version of Max2Play.

    flysurfer Moderator
    27. Dezember 2016 at 10:38 #25258

    @TonyW: If your Bluetooth Debug log is almost empty, something went wrong during installation. Maybe your filesystem is full? Have a look at the Debug output on the settings/reboot page (bottom of page) to see if there is some space left on your SD-Card.

    @Amazon Echo: I will try to get my hands on one of these to test it. Watching at the Debug of Davey it seems that the Echo is recognized as „AudioSource, AudioSink, AVRemoteControlTarget, AdvancedAudioDistribution, AVRemoteControl“ and although he want’s to use it as Bluetooth speaker, it is connected as Bluetooth source (streaming TO Max2Play instead of being a target to stream to). Right now the Bluetooth Addon can be used to setup both: streaming to speakers and being a Bluetooth speaker itsself. There might be more configuration needed, to make sure the Echo is used as speaker and not as input source (or both together).
    If you want the Echo to be speaker, try to disable the Autostart from the „Autostart Bluetooth-Streaming in Squeezebox Server“.

    flysurfer Moderator
    23. Dezember 2016 at 16:32 #25208

    @ihtruelsen: #1 your devices that are not visible on the Raspberry Pi can connect to other devices, but are not visible to other devices – right? I have to open the bluetooth devices overview on my phone to make it visible to other devices.

    #2 sometimes on a restart (depending on your setup) a second pulseaudio instance is running (this may cause the missing audio although everything seems to play). That is usually solved by a simple restart, if you see a 2 pulseaudio processes in the debug output of the bluetooth addon (at the buttom of the page).

    Another thing: when kodi is running and configured as webservice (remote control) it might block the port 9090 on which the command line interface of squeezebox server is running. If this happens, the bluetooth installer fails to add the favorites entry for the bluetooth device to the squeezebox server and the automatic bluetooth switch (enable streaming once smartphone is playing via bluetooth) won’t work either. I will build a fix for this later.

    flysurfer Moderator
    22. Dezember 2016 at 18:08 #25174

    Hi guybrush,
    when your playback stops:
    – is it still indicated as playing in Squeezebox Server? If not, this may be because auf the „Autostart Script“ that pauses playing when the connection seems to drop in Pulseaudio. I only had this, when the bluetooth connection was really bad.
    – is it still indicated as playing on your phone?
    – is your smartphone still connected on the bluetooth page?

    flysurfer Moderator
    22. Dezember 2016 at 12:33 #25144

    Hi Oliver,

    good to hear, that the Boom2 speaker is working now. This was indeed solved with the latest bugfix 🙂

    Sometimes you may have to click twice on the Reconnect Button for initial setup. Also make sure to open the bluetooth setup page on your smartphone before clicking the button. We addressed this in our video tutorial.
    In our tests with different iPhones and android phones (not with android 7.x) we encountered no problems so far.
    Instead of using chromecast you may also use the DLNA streaming via Squeezebox Server (stream to connected players) and smartphone apps like „AllConnect“ on android.
    Choppy sound might also come frome a bad bluetooth connection. I had no trouble or choppy sound with the RPi2 when testing.


    @ihtruelsen    :
    #1 the other devices you tried to connect do not seem to be visible for the Pi. Maybe due to security settings?
    #2 do your stream to the Squeezebox Server or directly to the Soundcard of your Player? I had this problem only when the bluetooth connection dropped.


    @guybrush73    :
    The bluetooth deivces in LMS favorites are less important when you activate „Autostart Bluetooth-Streaming in Squeezebox Server“. In this case you don’t need to do anything to start streaming from your smartphone (besides connecting and playing from the smartphone itsself).
    I do not have an Amazon Echo for testing, but maybe this is not recognized as input source (only as speaker)? You might see this in the Debug info on the Bluetooth page.


    @Christian     – Feature Request:
    Multiple Bluetooth Speakers might be possible with multiple bluetooth adapters. Connecting more than one stream / source to one adapter doesn’t work. If you want to play audio from smartphone directly to some bluetooth speakers, I’d suggest to skip the device in the middle.

    All the Best,
    Stefan

    flysurfer Moderator
    19. Dezember 2016 at 11:47 #24983

    Hi Wallie,

    sorry, but if you don’t have a Max2Play license the „Raspberry Pi Settings“ Page will not work. This is indicated with the message output above the content („License needed…“). You probably noticed that nothing gets saved when you try to change any values on the page. You may try the 3 month license of Max2Play to set up everything you need.

    All the Best,
    Stefan

    flysurfer Moderator
    13. Dezember 2016 at 17:43 #24834

    Hi Aurélien,

    you are completely right with addressing the problem. It is mainly because of the different subnets. The idea behind the access point plugin was to give users access to the device itsself and maybe to an internet connection behind another router. If you also want to see the devices in your network you need to change the IP address to your existing subnet. In your case you need to:

    edit /etc/dhcpcd.conf and set the IP to some not yet existing IP
    static ip_address=192.168.1.150/24

    edit /etc/dnsmasq.conf to

    
dhcp-range=192.168.1.151,192.168.1.160,255.255.255.0,12h
address=/HOSTNAME/192.168.1.150

    edit /etc/hosts and change IP to 192.168.1.150

    I did not test this setup, but it should work. I’d rather recommend to use a good router and some wireless extenders to set up your wifi as this is better for performance and easy of use.

    All the Best,
    Stefan

    flysurfer Moderator
    13. Dezember 2016 at 12:39 #24816

    Hi yoja,

    the X-Server is used to start the Pulseaudio server (that is used for the Bluetooth connection). As some may use Jivelite or other visualisations and therefor need the X-Server anyway, it is the easiest way to make this mandatory and have only one Pulseaudio instance.

    The running X-Server should not make much of a difference on current Pi (2/3) setups – but yes, on Pi 1 it may take longer to start.

    Support for multiple Bluetooth Adapters may not be too difficult, but the audioquality suffers from bad bluetooth connections and player synchronisation with Bluetooth is also not as good as with normal soundcards (delay between players due to BT-connection). It won’t be possible to stream bluetooth with the normal BT-Dongles through walls…

    Multisqueeze for Multiroom audio is best used with the build-in audiochip (headphone jack on Pi), an additional audiocard like the AMP+ from hifiberry / iqaudio / justboom and maybe one BT-Speaker. With this you can stream to 2 or 3 rooms with just one device wich works great for me.

    Stefan

    flysurfer Moderator
    5. Dezember 2016 at 17:02 #24564

    @oli: streaming in both directions at a time is not possible. I did not have the opportunity to test with the latest android running on Pixel phone. But I tested Android on Samsung S7, HTC and iPhone running iOS 10 without problems. In case you did not modify your Debug log, there are „**“ symbols behind every MAC-Address, so this might be causing the error. You may try to load the latest BETA from Max2Play on the Settings Page, Reboot and try to connect again.


    @rttm    : Der Lautsprecher scheint korrekt verbunden, allerdings ist die Audio-Ausgabe über Pulseaudio nicht korrekt erstellt. Kannst du es mal mit der neusten Beta und einem Neustart versuchen? Hast du die Soundkarte für die Audioplayer auf „Pulse“ umgestellt, bzw. die Audioplayer (oder Kodi) auf dem Gerät deaktiviert? Aus irgendeinem Grund scheint die Soundkarte schon von einem anderen Player belegt zu sein. Probier nach dem Beta-Update auch noch mal den Bluetooth-Lautsprecher aus der Liste zu entfernen und neu zu suchen.

    All the Best
    Stefan

    • This reply was modified 9 years, 7 months ago by flysurfer.
    flysurfer Moderator
    1. Dezember 2016 at 16:10 #24467

    Hi,

    thanks for your detailed debug info. I found a bug in Bluetooth, that prevented some speakers from working (Pulseaudio Bluetooth drivers Bluez5 vs Bluez4) and I built a workaround during connect and added better information to the message output on the connection status.

    If you had problems connecting your speakers until now, get the latest Beta on the Settings Page of Max2Play, remove your speakers from the Bluetooth page, Scan again and click Reconnect next to your speakers.

    @stefano: is your smartphone is indicated green (connected)? Can you post the output messages when clicking “Install Squeezebox Server Streaming”?

    flysurfer Moderator
    30. November 2016 at 11:14 #24363

    Hi,

    everything looks good from the log you posted. Your Squeezebox Server is running on the same device, right? Did you click the „Install Squeezebox Server Streaming“ after the pairing of your Smartphone was successful (this will add the Bluetooth Device to Favorites)?
    One more Point: please enable the Autostart in the Squeezebox Server Bluetooth Streaming Options at the bottom of the Bluetooth page. With this enabled you don’t even need to do anything in your Squeezebox Server and Bluetooth will stream automatically once your Smartphone starts playing.

    flysurfer Moderator
    29. November 2016 at 12:43 #24301

    Hi,

    maybe something went wrong during the installation of Bluetooth. Also, your Bluetooth Dongle seems not to be recognized correctly. To skip all possible errors I recommend that you try a new SD-Card with a fresh Max2Play Image (download the current version).

    flysurfer Moderator
    28. November 2016 at 15:17 #24289

    Hi Simon,

    please have a look at the video-walkthrough on our Plugin page for Bluetooth: https://www.max2play.com/en/portfolio/plugin-bluetooth-2/

    You may also post the Debug Output from the bottom of the Bluetooth Page here, if anything is not working as expected. A little more information is also usefull to help you better: version of Max2Play / downloaded SD-Card Image?

    flysurfer Moderator
    23. November 2016 at 15:53 #24128

    @castalla: great to hear it’s working finally :). If your FireTV gets connected via Bluetooth, it should work like streaming from your phone.


    @smiling-stefano    : did you click reconnect in the web interface next to your phone? A popup should appear on your phones display for pairing after clicking the reconnect button. You may have to do this twice. Castalla had a similar problem – solved it with another BT-dongle.

    flysurfer Moderator
    22. November 2016 at 18:00 #24103

    So you did the reconnect and there is no popup on your phone that asks for you to confirm the connection (you tried at least 2 times). Maybe you have an other phone for testing? The HUAWEI phone might be part of the problem or maybe security settings on your phone that don’t let any device connect.

    flysurfer Moderator
    22. November 2016 at 17:46 #24099

    @castalla: please open the bluetooth page on your smartphone (the one that shows devices – this should also show Max2Play) and do not click on anything. Now click reconnect in the web interface. Do this again, if no message appears on your smartphone.

    On every smartphone I tried (Samsung Galaxy, HTC, iPhone), this worked without problems. Your phone should also say „connected“ on the Bluetooth page after this.

    • This reply was modified 9 years, 7 months ago by flysurfer.
    flysurfer Moderator
    22. November 2016 at 17:29 #24095

    Hi castalla,

    once more: After you click „reconnect“ in the web interface, does your smartphone show a window with „Do you want to connect to Max2Play?“ AND did you confirm this message with „OK“?

    After the first initial setup you just need to choose „Max2Play“ from your smartphone (Bluetooth Settings) to connect.

    • This reply was modified 9 years, 7 months ago by flysurfer.
    flysurfer Moderator
    22. November 2016 at 15:48 #24085

    We will make a video for this to clarify – but the text on the bluetooth page explains everything. There are just 4 buttons to click to install and setup…

    First click: install bluetooth

    Second click: scan for devices

    Third click (where you struggle): When your phone appears after the scan in red, you need to connect to it by clicking „reconnect“ button. Then your phone will ask you to open the connection. After you confirm this your phone will be indicated as connected and green on the bluetooth page.

    Fourth click: at the bottom of the bluetooth plugin page click „Install Bluetooth Streaming for Squeezebox Server“ and optionally enable „Autostart“ below it.

    Everything together takes about 2 minutes of time…

    flysurfer Moderator
    21. November 2016 at 17:35 #24069

    Yeah – right. No audioplayer settings need to be edited. The Bluetooth Streaming to Squeezebox Server works like a radio stream and is fully integrated into Squeezbox Server.

    The Bluetooth Plugin Page might be a little confusing at first, as it offers multiple options, depending on what you want to achieve.

    If the Bluetooth Plugin does not install, there must be something wrong with the system. Maybe the SD-Card had an error on installing.

    flysurfer Moderator
    21. November 2016 at 17:23 #24067

    Hi – the 2.38 should work fine.

    If it cannot install Bluetooth, maybe you forgot to expand the filesystem and the SD-Card is full? After installing Squeezebox Server this might be the problem. You can check this in the DEBUG at the Settings Page.

    flysurfer Moderator
    21. November 2016 at 17:07 #24064

    Hi Castalla,

    it should be really easy – maybe you missed the part where you couple your smartphone with Max2Play? This must be done just once after you installed the Bluetooth plugin and before clicking the „install Bluetooth Streaming to Squeezebox Server“ at the bottom of the Bluetooth Plugin (this really needs to know your smartphone as otherwise it will not start streaming).

    After this you should see the Bluetooth device in your LMS in favorites.

    Errors may occure when:
    – no space left on SD-Card when installing
    – no Bluetooth Connection to your Smartphone (indicated as green)

    Hope this helps – Stefan

    flysurfer Moderator
    21. November 2016 at 15:15 #24049

    Hi Castalla,

    the bluetooth streaming is only supported with the Debian Jessie version of Max2Play on Raspberry Pi (this is the base operating system). When it says „Wheezy Image is not supported“ this indicates, that you are using the older Debian Wheezy System. The jump from Wheezy to Jessie was around 6 month ago. Please flash a new SD-Card with the current download of Max2Play to use Bluetooth streaming to Squeezebox Server.

    Regards,
    Stefan

    flysurfer Moderator
    15. November 2016 at 17:44 #23914

    Hi Hilary,

    please choose „Master“ as mpd mixer control in the MPD settings.

    Regards,
    Stefan

    flysurfer Moderator
    10. November 2016 at 11:39 #23853

    @southafricanrob: there is a setting for this to switch off / on squeezelite player by connection status of bluetooth speakers on the bluetooth page. See also the instruction on this page how to set up.

    flysurfer Moderator
    9. November 2016 at 17:00 #23840

    Hi LowTech,

    dein Grundproblem im Setup mit Squeezelite scheint zu sein, dass standardmäßig beim Abspielen auf die USB-Soundkarte „sysdefault-USB PnP Sounddevice“ wohl nicht direkt auf Hardware abgespielt wird (Mixer Device hängt dazwischen).

    Wenn du direkt auf die Hardware abspielen willst, funktioniert das in der Regel über den genannten Parameter „-o hw:0“, der in den Kommandozeilenparametern von Squeezelite eingefügt wird. Wichtig ist dabei, dass kein anderer Audioplayer oder Kodi aktiv ist, der ggf. das Audiointerface schon exklusiv für sich beansprucht und keine sonstigen Parameter in diesem Feld stehen.
    Falls das nicht geht, gibt es eventuell eine Soundkartenoption, die etwas wie „hardware“ oder „direct hardware output“ im Namen enthält und gewählt werden kann.

    Weitere Möglichkeiten:
    – ein regelmäßger Reboot, um dem Audioproblem zuvor zu kommen (ggf. erstelle ich hierfür mal ein Plugin). Aktuell müsste der Reboot in die Crontab eingetragen werden (z.B. für 6 Uhr morgens)

    # Crontab Editieren über crontab -e
0 6 * * * sudo /sbin/reboot

    – Nutzung von HifiBerry / IQAudIO / Justboom Karten, die alle fehlerfrei funktionieren statt der USB-Soundkarte (ggf. liegt es auch am USB selbst oder an der Stromzufuhr)
    – Umstellen der Audioausgabe auf Pulseaudio (Autostart Desktop aktivieren und Audioausgabe auf Soundkarte „Pulse“/“Pulseaudio“ setzen)

    flysurfer Moderator
    8. November 2016 at 16:59 #23775

    Hallo,

    gibt es einen Grund, warum du nicht einfach „Pause“ im Player drückst, um die Wiedergabe zu unterbrechen?

    flysurfer Moderator
    8. November 2016 at 16:07 #23772

    Hi Georges,

    das Script zum Deaktivieren der Protection muss ausgeführt werden als user root:
    /var/www/max2play/application/plugins/sdcardprotection/scripts/uninstall_sdcardprotection.sh

    Normalerweise sollte das Plugin fehlerfrei funktionieren, solange Max2Play nur als Audioplayer verwendet wird.

    Viele Grüße
    Stefan

    flysurfer Moderator
    4. November 2016 at 12:06 #23662

    Hi jnile1, hi Marc,

    sorry, but the new feature in the Max2Play-Beta to change the build-in wifi interface in Raspberry Pi Settings had a minor bug. Just load the latest Max2Play-Beta and uncheck the Checkbox „Disable Default WiFi Interface WLAN0 on RPI3“ -> click save -> check it again and save.

    After a Restart the build in Wifi will be at position wlan1 and the other stick will have wlan0 and be default.

Viewing 30 posts - 91 through 120 (of 275 total)
1 2 3 4 5 … 8 9 10