Forum Replies Created
-
-
12. Februar 2018 at 11:55 #33951
Hi Hammerhead,
Thanks for following up on your issue, happy to hear you got it fixed over the weekend 🙂
12. Februar 2018 at 11:39 #33950Hi guys,
Thanks for the feedback. We will look into possible solutions for a Roon integration.
12. Februar 2018 at 11:38 #33949Hi Maarten,
Sorry to hear that. Please do keep us up-to-date if you find a fix, though.
12. Februar 2018 at 10:58 #33948Hi Hammerhead,
Which output device do you use? Which version of Max2Play, LMS and Squeezelite?
9 out of 10 times with a share not playing properly, it is connected to the music folder’s rights or format in some way.
Please try checking one or two files in basic format and without special write protection to make sure this is not the case.
9. Februar 2018 at 17:29 #33932Hi Mike,
I would advise trying out playback on a different out device and with a different cable to rule out all possible sources of error. If the noise is still reproducible, you might have to exchange the DAC.
9. Februar 2018 at 17:17 #33931Hi Stefan,
Not in the near future, no. But you can start a thread in our Request forum and if enough other people request this feature, we will analyse possible solutions for feasibility.
8. Februar 2018 at 17:03 #33920Hi madaaf,
Unfortunately, for the RPi Camera, the Pi needs to have write permissions in order to be able to process pictures and video.
8. Februar 2018 at 15:35 #33917Hi Stefan,
The plugin saves the credentials in clear text in the wpa_supplicant.conf.
8. Februar 2018 at 13:56 #33915Hi DocBones,
Our Kodi install is primarily intended for video and is just a direct install from the original Kodi. So based on the version installed, you can use the exact same documentation and help sections for Kodi in general.
However, for music we recommend using the Squeezebox System with Squeezebox Server and Squeezelite. It is much more comfortable and powerful and has its own graphical interface with the Jivelite plugin. Also, its music library management works better. Check out our Audioplayer section under „Features“ in the top bar of Max2Play to see how it works.
8. Februar 2018 at 13:52 #33914Hi Stefan,
Max2Play is not intended to be configured via SSH. You can reach the WiFi/LAN menu of our web interface by entering „max2play/“ in any other device in the network. There, you can activate the “wlan interface laden”, deactivate “aktiviere wps beim booten”, scan for your network, select it, enter your password, save settings and reboot. You also have a debug info window that shows you the WiFi info from the SSH output.
8. Februar 2018 at 13:48 #33913Hi fahzz,
Perhaps you are confusing the Allo Piano 2.1 with the DigiOne setup on Max2Play? We built a dedicated Subwoofer config for the Piano 2.1 and its dedicated Subwoofer output.
Unfortunately, this does not work for the DigiOne as its output is digital and has to be processed by the receiving device of the digital signal while the Piano 2.1 DAC has two separate, analogue outputs that can be manipulated on the Raspberry Pi before being put out.8. Februar 2018 at 13:36 #33911Hi NearTheBeach,
First of all, thank you so much for the detailed and thoughtful response.
If there is still an issue with your setup, please let us know.
7. Februar 2018 at 18:06 #33905Hi ostenax,
Thank you for making us aware of this, we already contacted Audiophonics and will get to check the new version out ourselves by tomorrow.
Please excuse the inconvenience.
7. Februar 2018 at 16:23 #33903Hi robrock,
Check bitte einmal die Rechte und Formatierung deiner Dateien. Die Fehlermeldung bezieht sich höchstwahrscheinlich auf die zu scannenden Dateien selbst. Wenn möglich, versuche einmal einen sehr simplen Mount zu scannen (1-2 mp3’s ohne jegliche Sonderrechte oder Schreibschutz).
7. Februar 2018 at 11:46 #33900Hi Maarten,
Thanks for sharing this issue. We have not encountered it yet.
Let me know if these fixes work of you or not. 🙂
7. Februar 2018 at 11:40 #33899Hi robrock,
Versuche bitte einmal, einen neuen Mountpoint für die Freigabe auszuwählen, „/mnt/share1“, und für das Endgerät die IP anstatt dem Namen.
7. Februar 2018 at 11:18 #33898Why did you change to HDMI? Were the pops gone with DigiAmp+ playback as well?
6. Februar 2018 at 18:05 #33895Hi ofarim,
The topic in question was with a customer who solved his problem via email with us.
Please make sure this issue is not a hardware defect by ruling out the power line first (connect it from a different outlet). If the noise is still there, please write us an email and we will diagnose the problem precisely.
6. Februar 2018 at 17:44 #33894Hi kraker,
Thanks for letting us know.
We will dust off the ol‘ B+ and try to recreate the error.
6. Februar 2018 at 17:41 #33892Hi am,
Diese Dokumentation zum Squeezebox Server sollte dir weiterhelfen können:
Offiziell
Nutzer-zusammgestellt6. Februar 2018 at 17:37 #33891Hi antonio,
According to this post, at least one of them is working well.
6. Februar 2018 at 17:35 #33890Hallo Jürgen,
Verstehe ich richtig, dass der Squeezebox Server auf dem Pioneer läuft? Falls nicht und dieser läuft auf dem Pi kannst du leider keinen Schreibschutz nutzen. Dieser funktioniert nur mit dem Player. Der Ser muss leider durchgehend Zugriff auf die SD-Karte haben und lässt daher keinen Schreibschutz zu.
6. Februar 2018 at 17:32 #33889Hi thefsb,
Unfortunately, we do not have something like this. Your best bet should be the slimdevices forum as this sort of thing is their expertise.
6. Februar 2018 at 17:30 #33888Hi jagu,
Wahrscheinlich die default HiFiBerry Treiber mit „HiFiBerry DAC“, aber bei diesen no name DAC’s können wir leider keine Garantien oder direkten Empfehlungen aussprechen, da wir dessen Herkunft und Verarbeitung nicht kennen.
6. Februar 2018 at 17:28 #33887Hi Mike,
Please remove the „-o“ and leave the rest as is, click save, reboot and try playing something
6. Februar 2018 at 16:10 #33884Hi Gerstel,
Danke für das Feedback. Ich schließe das Topic dann erstmal. Wenn wieder Probleme auftreten kannst du ein neues aufmachen oder hier posten wenn es sich um das gleiche Problem handelt 😉
6. Februar 2018 at 11:34 #33878Hi antonio,
You can turn off the system with the joggler skin, there’s a custom button we added after requests for it.
You can also turn off the system with an http-command. The line in the URL after you click shutdown can be copy pasted and used in any application on any device in the local network to shut the device down.
6. Februar 2018 at 11:07 #33875Hi ofarim,
Do these noises come from the output device (your speakers) or the Pi and sound card themselves?
I assume you mean Sabre V3 for your sound card?
6. Februar 2018 at 11:07 #33876Hi ofarim,
Do these noises come from the output device (your speakers) or the Pi and sound card themselves?
I assume you mean Sabre V3 for your sound card?
5. Februar 2018 at 16:04 #33866Hi macpac,
The power supply is probably too weak. We recommend using a 5V 2.5A PS for the Raspberry Pi 3 with a sound card HAT in general. For the MiniAmp it might even be recommendable to use 3A.
Also, make sure the speakers you use are only around 3W each as that is the maximum capacity of the miniamp. What wattage do your speakers have?
-
