Forum Replies Created
-
11. Oktober 2019 at 15:09 #47272
Hallo Herr Tacke,
Welchen Pi nutzen und welches Image nutzen Sie mit Max2Play?
11. Oktober 2019 at 15:08 #47271Hi dconrow,
It is very likely that is an issue with insufficient power via USB. With bigger usb drives, especially HDD that don’t have their own power, we recommend using a powered USB hub to make sure the drive receives enough power.
11. Oktober 2019 at 15:06 #47270Hi mk,
Unfortunately this is not possible from the web interface. However, you can access the samba service via SSH and try setting up different logins for different shares manually.
11. Oktober 2019 at 15:05 #47269Thanks for letting us know it worked with your system 🙂
11. Oktober 2019 at 14:58 #47268Hi Stefan,
Are you using the Spotify Connect Player or Spotty plugin for the Squeezebox server? For the latter, try deselecting the connect devices and reselecting them. For spotify connect player try reinstalling the player with the newest source.
11. Oktober 2019 at 14:56 #47267Hi Third_eye,
We have not heard of this issue before it sounds similar to this topic
11. Oktober 2019 at 14:53 #47266Hi tony,
Sorry about the late reply.
The joggler skin should be preinstalled in Jivelite. Try reinstalling Jivelite from Max2Play to make sure.
11. Oktober 2019 at 13:24 #47264Hello Quentin,
Which selection did you make in the HiFiBerry plugin? Please try selecting none, rebooting and selecting the HiFiBerry DAC without + and rebooting.
11. Oktober 2019 at 13:23 #47263Hallo Kmuf,
Besteht dieses Problem abseits der WLAN Stick Integrationsproblematik?
Welcher Pi wird verwendet?
8. Oktober 2019 at 12:35 #47246Hi Florian,
Unfortunately, we have no image for or experience with the Vana Player. Support is handled entirely by Allo. Here’s their help section
8. Oktober 2019 at 10:14 #47241Hi Ezaul,
I already replied to your comment, you can send your text and photos to info [at] max2play [dot] com and we’ll format and translate it for publication 😉
2. Oktober 2019 at 12:48 #47220Also geht es jetzt um Kodi am Pi oder weiter die Wiedergabe über den TV? Beim TV kriegen Sie die Latenz nicht weg. Das heißt, selbst wenn Sie eine eigene Lösung für Input finden (Max2Play bietet keine direkte Lösung für eingehende Audiosignale), wird eine Verzögerung des Audios zum Video von 1-4 Sekunden nicht vermeidbar sein, da der Audiostream mehrere Konversionen durchmachen muss.
2. Oktober 2019 at 10:58 #47218Hi Ezaul,
Have you had a look at our API Examples plugin yet? You might be able to integrate a lot already.
It lists many essential commands like reboot, play, pause, etc. for your device to just copy and paste to any home automation server you want to use. It comes preinstalled on new images and is free 😉Your project sounds great! We’d love to share with the rest of the community in our blog if you’re interested.
2. Oktober 2019 at 10:48 #47217Hi cramcram,
We were and we’ve added a beta update that adds an automatic installer for the missing package under buster in the lms.
You can try it out by making a beta update and installing the LMS afterwards.
1. Oktober 2019 at 10:01 #47211Hi marc,
Thanks for the detailed update on this. We will try to tackle these issues with the different boards in an upcoming version.
We had a lot of issues with implementing the Zero W because of its different structure, I assume the A+ has similar differences that cause compatibility issues.
Is there a specific reason why one of the A+ Pi’s worked with the 2.26 wheezy instead of the 2.44 jessie? Were there other differences in these setups aside from the sound cards?
1. Oktober 2019 at 9:52 #47209Die Latenz außer Acht lassend, können Sie ggf. mit dem waveinput plugin vom Squeezebox Server etwas ähnliches erreichen. Dies ist jedoch kein Anwendungssfall von Max2Play und wird in Latenz resultieren.
Wie erwähnt wäre der einfachste Weg, über Kodi TV zu sehen und dort das Ausgangsgerät hifiberry bei deaktiviertem eingebautem Audio vom Pi (in den Raspberry Einstellungen) auszuwählen.
30. September 2019 at 10:40 #47201Hallo Stefan,
Das Problem bei TV Ausgabe ist die akute Latenz, die dadurch entsteht. Solange also der TV-Inhalt nicht direkt über Kodi am Pi wiedergegeben wird, gibt es eine Latenz die das funktionale Fernsehen verhindert.
Mit Kodi sollte die Wiedergabe von Videoinhalten, TV-Streams, etc. allerdings kein Problem sein.
30. September 2019 at 10:38 #47200Hi thales,
Please also paste the BT plugin’s green/red box content here.
30. September 2019 at 10:37 #47199Hi wood,
Currently there is no really satisfying cooling solution for any HAT sound card setup. However, the Pi4 just operates at a higher temperature than the Pi3.
But if you do find a more elegant solution than a GPIO extender, please do let us know so we can have a look too 😉
30. September 2019 at 10:35 #47198Hi Erwin,
Have you tried the Raspberry Settings for HDMI yet?
Try the tick with „Force Hotplug“ and reboot.
30. September 2019 at 10:33 #47197Hi cramcram,
Somehow my reply didn’t get posted last week.
The art work cache directory is as follows:
/var/lib/squeezeboxserver/cache/artwork.db30. September 2019 at 10:02 #47194Hi mk,
Yes you can use a SambaShare from our filesystem/mount plugin to open up the directory you want from your SSD. Here’s the wiki on it
27. September 2019 at 10:20 #47172Hi cramcram,
Thanks for the feedback, is the version „shairtunes2 (fork)“ and is no other version of shairtunes active?
27. September 2019 at 10:03 #47169Hallo Stefan,
Bitte deaktivier den build-in audio in den Raspberry Settings. und starte neu. Danach sollte hifiberry in Kodi als Auswahl auftauchen.
27. September 2019 at 10:03 #47168Hi hoge,
For Kodi you need to deactivate the build-in audio in Raspberry Settings and reboot to make the AMP2 the first slot. Then you need to make sure to have „hw:0“ in the command line options of Squeezelite to have it also recognize that it’s now in the first slot.
25. September 2019 at 9:53 #47147Hallo daemmi,
Ist dein System seit dieser Fehlermeldung in irgendeiner Form beeinträchtigt?
-
