Heiner

Forum Replies Created

Viewing 30 posts - 3,901 through 3,930 (of 4,111 total)
  • Posted in:
  • 1. März 2016 at 17:08 #18942

    The beta is available for download on our download page: https://www.max2play.com/en/max2play-image/
    An update will not suffice.

    1. März 2016 at 15:38 #18905

    Hi q20,
    Good timing on your part! We are just now getting ready to roll out version 2.28 of Max2Play based on Jessie (https://www.max2play.com/en/changelog-max2play/). You can already check it out by updating to the latest beta of Max2Play.

    1. März 2016 at 15:07 #18902

    Hi d4n3ll,
    Sorry about not responding directly. The problem is, we do not use the original Classic and Boom Squeezeboxes since we focus on our own solutions to replace these. Thus, we cannot give you any advice on these devices and would recommend you contact the manufacturer on these issues.
    However, you can try and change the decoder parameters in your Squeezebox Server (we would also recommend the version 7.9 nightly since it supports the most new formats) at Settings -> Advanced -> File Types -> FLAC

    29. Februar 2016 at 17:23 #18857

    the kodi folder’s contents are hidden, hence the .kodi name. You need to access in root mode name: root pw: max2play

    29. Februar 2016 at 16:06 #18852

    Hi Peter,
    Versuch bitte, in Kommandozeilen Optionen, unter Squeezelite’s erweiterten Einstellungen, den Parameter hw:0,0 einzugeben. Das sollte den Equalizer zum laufen bringen.

    29. Februar 2016 at 15:12 #18844

    Hi Roman,
    Unfortunately, the mysqueezebox.com remote control only works with official Logitech products. However, you can use a VPN to your local network, which you can set up in your router, to easily access your home network from anywhere and thus your SB-Server’s interface as well. You can find a lot guides to this on the web if you are interested in such a solution.

    29. Februar 2016 at 15:06 #18841

    Hi q20,
    Thanks for informing us about this server software. Unfortunately, it does not seem to offer any multiroom capabilites, which we are looking for first and foremost.
    However, we would be interested to know what functionalities this server offers over the Squeezebox Server’s Spotify implementation with the triode plugin, aside from the official app and connect support.

    In case you only read the first page, here is the updated version get librespot up to date:

    We now edited the plugin to accommodate any changes in librespot. To get this changed version, just:

    – Go to „Settings/Reboot“
    – Install the Spotify Connect plugin again as you did already with the URL from our website:
    http://shop.max2play.com/media/downloadable/currentversion/spotifyconnect.tar
    – Click „Reinstall“ on the Spotify Connect page
    – Reboot, you’re done! 🙂

    • This reply was modified 7 years, 7 months ago by Heiner.
    29. Februar 2016 at 15:03 #18840

    Hi Simon,
    This application has been discussed here already (https://www.max2play.com/forums/topic/multisqueeze-mit-logflink-7-1-usb-soundkarte/). However, it was unfortunately a German thread. So I will try to convey the discussion in English with the technical logs and commands inserted.

    kippi has a Logilink 7.1 and wants to give each channel on the card a different binding. He uses the Premium Plugin „Multisqueeze“ for these separate channels. In Audioplayer he sets the parameter „-o hw:1,0“, the sound card as USB sound card and sysdefault….alsa
    In MultiSqueeze he goes to the Advanced Options and puts in „-o garage“ (which refers to a binding in the asound.conf)

    He then configures the following under asound.conf (where he set up the sound card and split up the bindings by testing them with headphones):

    `pcm_slave.logilink {
    pcm “hw:1,0″
    channels 8
    rate 44100
    # format “S16_LE”
    # periods 128
    # period_time 0
    period_size 1024
    buffer_size 4096
    }

    pcm.garage {
    type plug
    slave.pcm {
    type dshare
    ipc_key 1024
    ipc_key_add_uid false
    ipc_gid audio
    ipc_perm 0660
    slave logilink
    bindings [ 0 1 ]
    }
    }

    pcm.bad {
    type plug
    slave.pcm {
    type dshare
    ipc_key 1024
    ipc_key_add_uid false
    ipc_gid audio
    ipc_perm 0660
    slave logilink
    bindings [ 2 ]
    }
    }

    pcm.schlaf {
    type plug
    slave.pcm {
    type dshare
    ipc_key 1024
    ipc_key_add_uid false
    ipc_gid audio
    ipc_perm 0660
    slave logilink
    bindings [ 7 ]
    }
    }

    I hope this helped you. If you still have questions about the setup, you might contact kippi in his thread.

    29. Februar 2016 at 14:42 #18839

    Hi Ronald,
    Thanks for the detailed English instruction.
    I recently also pointed this installation process out in our Jivelite comments section (https://www.max2play.com/features/rpi-raspberry-pi-touch-display-installation-fuer-2-8-watterott-display-2-4-4dpi-24-hat-und-7-raspberry-pi-offizielles-display/).

    We have since then added the display as an installation option for the touch display plugin in its current beta release. There, you can just select the Adafruit 2.8 display and those setps are taken automatically.

    29. Februar 2016 at 14:31 #18838

    Hi Lefuneste,
    You can set the hw parameter in our webinterface under the Advanced Settings of Squeezelite, which we would recommend since Max2Play is intended to be controlled over the web interface. Regarding the issues with your USB sound card, we can unfortunately not offer support for specific USB DAC’s since there has been such a vast output of them ranging immensely in quality. We would advise you to contact the manufacturer for support.
    For the best Max2Play result we would recommend using a freshly burnt image and setting the hardware parameter in the web interface.

    26. Februar 2016 at 16:42 #18784

    Hi wanderwell,
    The key bindings for Kodi can be found under /home/pi/.kodi/userdata/keymaps

    25. Februar 2016 at 14:14 #18736

    Hi chrisich,
    The login for the root is indeed root, pw max2play. While the normal login is pi, pw raspberry. But Max2Play is not built for console commands. Have you checked if you can reach our web interface by typing http://max2play in your pc or smartphone while connected to your local network? If your router does not recognize your Max2Play device, your image might be corrupt.
    Also, do not be alarmed that you cannot see your input when typing the login, your input is received but not displayed.

    24. Februar 2016 at 15:18 #18704

    Hallo Stephan,
    Ich habe deine Testdatei hier erfolgreich abgespielt mit einem Squeezebox Server nightly 7.9 und einer Samba Share wo sich die Datei befand. Hast du deine Soundkarte unter Raspberry Settings ausgewählt und danach gecheckt ob sie als Sound Output bei MultiSqueeze in den erweiterten Einstellungen ausgewählt ist? Außerdem wäre interessant wie du die Datei in den Server eingebunden hast.
    Die Datei an sich ist eine normale MP3, der Server sollte also keine Probleme haben, diese abzuspielen.

    18. Februar 2016 at 17:10 #18585

    Stop Jivelite, start Kodi, got to System -> Settings -> System -> Audio Output -> Audio Output Device, save HDMI as output device and start Jivelite again.

    18. Februar 2016 at 16:12 #18583

    Hi Marcel,
    Du kannst checken ob der Prozess von Squeezelite im Webinterface aktiv ist, ob dein lokales Netzwerk deinen Pi und den Server beide erkennt, du kannst versuchen den Namen des Pi zu ändern und Umlaute vermeiden. Du kannst zudem versuchen, einen anderen Player im Netzwerk zu verbinden mit der selben LAN-Verbindung um diese als Problemquelle auszuschliessen.
    Wir haben hier auch einen Squeezebox Server auf unserer Diskstation (Synology) und dieser erkennt alle unsere Squeezelite-Player im Netz. Welche Version von M2P und welchen Raspberry verwendest du?

    18. Februar 2016 at 15:38 #18582

    Hi Tefi,
    You can find all you need to know about the commands for the Squeezebox Server in its own documentation (With IP and port of your SBS http://IP:PORT/html/docs/cli-api.html) and here are some examples: http://tutoriels.domotique-store.fr/content/54/95/fr/api-logitech-squeezebox-server-_-player-http.html

    18. Februar 2016 at 15:26 #18581

    Hi Rainer,
    Wir haben das Problem jetzt wahrscheinlich ausfindig gemacht. Bitte versuche, eine andere Tastatur ohne Spezialtasten, etc. am besten mit PS/2-Anschluss zu nutzen wenn du den Flirc Stick programmierst. Es kann nämlich sein, dass deine Tastatur, falls Sie per USB angeschlossen wird und Sondertasten oder Short-Cuts hat eine leicht problematische Zuweisung liefert die dann nicht richtig funktioniert beim Pi bis man die Tastatur verbindet.
    Außerdem versuche bitte die Sprache des Pi auf englisch umzustellen, dabei können ebenfalls Zuweisungsprobleme behoben werden.

    18. Februar 2016 at 15:04 #18578

    Hi sweet,
    Sorry for the late response. Max2Play supports luajit.
    Good luck with your implementation!

    • This reply was modified 9 years ago by Heiner.
    18. Februar 2016 at 15:02 #18577

    Hi Bazzzer,
    Please try out our new image. The old collaboration with Squeezeplug is not up to date on all our features. The version 2.26 is up for download and even supports the kernel upgrade with the Cirrus Logic card without any problems. Download the image, expand the filesystem, update the image (2.27) and upgrade the kernel.

    18. Februar 2016 at 14:52 #18576

    English is our preferred language in the forums, because the whole community can benefit from the exchanges 😉
    Have you tried entering the Network SSID and the password under the WiFi/LAN menu? If your hidden WiFi bridge is accessible, you should be able to directly log in this way.

    18. Februar 2016 at 14:37 #18573

    Hi fvzeppelin,
    There are a few things you can try to fix the issue. The DAC+ will work great anyways. In your current setup, however, with the HDMI output, the Pi should be the issue. Please check if you have Kodi on or on autostart, test it with just Jivelite and Squeezelite running. Also, please try connecting the Pi to another device like a TV via HDMI to rule out the port as the origin of error.
    If you have another Raspberry, please try it with the image you are using on the one with drop-outs.

    18. Februar 2016 at 14:20 #18572

    Hi Pedro,
    Yes there is a simple way to make this setup work. You can find the Max2Play plugin „DLNA Server“, which lets you install a small DLNA server with the option to directly give a path for your media files. Then, you can use simple Apps like BubbleUPnP to connect that server with your speakers as renderers.
    You can also use the Squeezebox Server, it is also recognized as a server element by the DLNA apps.

    17. Februar 2016 at 15:05 #18537

    Hi Pastinakel,
    When you added the „-v“ parameter, you should be able to switch between visualisation by just tapping anywhere on the screen during normal playback.

    16. Februar 2016 at 15:15 #18518

    Hi micro,
    Noch ein möglicher Fix um das Problem zu lösen:
    Du musst zwei verschiedene Kanäle als Output für Shairport und Kodi festlegen. Shairport sollte ja bereits für die USB-Karte designiert sein. Also musst du nur noch in Kodi den Output umstellen (System -> Settings -> System -> Audio Output -> Audio Output Device) und dort auf HDMI setzen. Dann solten beide gleichzeitig laufen können.

    16. Februar 2016 at 15:12 #18517

    Hi m,
    You need to designate two different audio outputs to Squeezelite and Kodi. So since Squeezelite is already activated for use with your DAC+, you need to go into Kodi’s settings (System -> Settings -> System -> Audio Output -> Audio Output Device) and set the audio output to HDMI. That should make them work simultaneously.

    15. Februar 2016 at 16:45 #18499

    Hi Eric,
    you should find the sliders for volume control in the Raspberry Settings Menu and in the IQaudIO image on the start page.

    15. Februar 2016 at 16:24 #18498

    Hi chancenvergeber,
    Please try the option „upgrade kernel“ in your Raspberry Settings and see if it solves your issues.

    15. Februar 2016 at 14:40 #18496

    The software does that for you.

    15. Februar 2016 at 14:37 #18495

    Hallo wtcE,
    Vielen Dank für deine Nachfrage. Ich kann mich Humpel nur anschließen, grundsätzlich funktioniert das Image mit allen Pi’s. Wir haben jedoch unsere Entwicklung und Tests primär auf Raspberry Pi 2 Modell B’s gemacht und empfehlen daher dieses Modell. Die Soundqualität der normalen Audioausgänge können wir ebenfalls nicht empfehlen und raten eher zu Soundkarten die auch hauptsächlich für den RPi 2 Modell B erhältlich sind.
    Die Einrichtung über WLAN-Stick mit WPS geht jedoch sehr einfach und schnell und sollte keine Probleme darstellen.

    11. Februar 2016 at 13:38 #18458

    You can see under Settings/Reboot in the debug info below how much memory is free. The Odroid image should display a desktop when connected via HDMI. Please try a fresh image and try burning it with Odroid’s Win32DiskImager: http://com.odroid.com/sigong/blog/blog_list.php?bid=144

Viewing 30 posts - 3,901 through 3,930 (of 4,111 total)