28. August 2019 at 11:16 #46892
Thanks for asking, we will soon release the official image for the Pi4. However, the current beta will also be updatable to the official release, so you can already set it up now and update to the proper version just by clicking the normal update Max2Play button.26. September 2019 at 21:15 #47167
Found one issue. I don’t manage to install Shairtunes2. When I try to open the plugin settings page I get:
404 Not Found: plugins/Extensions/settings/plugins/ShairTunes2W/settings/basic.html
So the plugin doesn’t seem to install properly. Installing the SSL fix on the Squeezebox Server page in max2play doesn’t help.30. September 2019 at 23:19 #47205
Over at the slim devices forum somebody fixed it with
sudo apt install libcrypt-openssl-rsa-perl27. Dezember 2019 at 15:19 #47836
I have installed the Buster image on a Pi4. After updating Max2Play to the latest versions I tried updating Raspbian with
sudo apt-get update
sudo apt-get dist-upgrade
After the upgrade the Pi no longer boots. I have tried this a few times and another user on the slimdevices forum has confirmed that he also found the same issue after performing the upgrade.
Any ideas?27. Dezember 2019 at 18:15 #47838
So you can’t even get to the command line?
Or you can just see if installing the PI OS and then do them commands.
-Raymond Day26. Januar 2020 at 13:29 #47969
Have you planned to make LMS 8 available via the Squeezebox Server tab in max2play (http://max2play/plugins/max2play_settings/controller/Squeezeserver.php)?2. Februar 2020 at 11:00 #47977
Will the new buster 64 bit kernel with latest beta run
1. On pi 2 ?,
2. On pi 3 ?
3. Will there be speed increase, eg. in Kodi YouTube searches or in Logitech media server database updates when building up huge music collection on big hd ?
Is there now a stable max2play buster, incl. 64 bit?
Wird der buster 64 bit kernel mit der neusten Beta auch 1. Auf pi 2 , 2. Auf dem pi 3 laufen?
3. Wird es den beschriebenen geschwindigkeitszuwachs geben?
Oder gibts nun eine max2play stable mit buster und 64 Bit?18. Februar 2020 at 16:49 #48039
If you do this then don’t try to update using
If you do your Pi will no longer boot. So you are likely to be stuck with the old kernel with the associated temperature issues.
This would not be an issue if a Max2Play version based on the latest Raspbian Buster with updated kernel was available for download.18. Februar 2020 at 18:37 #48040
It’s funny you should say that because that’s exactly what I did and yes, The Pi4 wouldn’t boot. I simply started again but didn’t do the Apt-get dist-upgrade the second time.
I was only experimenting to see how easy it is to get Max2Play and Pi-hole operating on the same Pi which I was able to do once I’d changed the port number of Pi-hole.
I tried to get Max2Play to use the 64bit kernel using the switch in v2.51 but nothing happened which I assume is because I’m not a paid up user?22. Februar 2020 at 17:31 #48058
I have a HiFiBerry DAC+ ADC running on a Raspberry Pi 4.
I am using Max2Play latest beta for the Pi4 and I am using the default LMS server and squeeze player.
Playing music from my NAS works perfectly, but I cannot play anything from the aux/line-in source on the DAC.
I have setup by following these instructions: https://www.hifiberry.com/docs/software/integrate-analoge-audio-devices-into-your-multi-room-system/?utm_campaign=website&utm_source=sendgrid&utm_medium=mail
I have set the URL for the wavein plugin to wavin:default and I have also tried wavin:sysdefault because I found some information on this forum and saw that my default soundcard in M2P is named “sysdefault”. https://www.max2play.com/en/forums/topic/using-the-input-function-of-hifiberry-dac-adc-pro/
Nothings works – does anyone have any suggestions? Is anyone else able to get this working with a DAC+ ADC and a Pi V4?
25. Februar 2020 at 18:08 #48079
- This reply was modified 5 days, 21 hours ago by andy2111.
I am running the Hifiberry DAC+ADC on a Pi 4 with the WaveInput plugin.
In difference to your case, I do not use the analog output. Only the analog input and HDMI for digital audio output isin use.
To get WaveInput running, you need to know the correct soundcard and channel of the audio input of the ADC.
On my installation I entered wavin:plughw:1,0 as favorite and it runs correctly.26. Februar 2020 at 23:38 #48090
Thanks for your reply.
I’ve tried various things with no luck and looking at the format of the soundcard name you used I still can’t figure out mine.
I have the following set as my default in the audio player settings:
plughw – snd_rpi_hifiberry_dacplus, -Hardware device with all software conversions, CARD=sndrpihifiberry,DEV=0
Any idea from the above what I would put after „wavin:“ ?
And it looks like I have a couple of other options I can set as the soundcard – I’ve tried unsuccessfully here too..
hw – snd_rpi_hifiberry_dacplus, – Direct hardware device without any conversions, CARD=sndrpihifiberry,DEV=0
sysdefault – snd_rpi_hifiberry_dacplus, – Default Audio Device, CARD=sndrpihifiberry,DEV=0
Any help is very gratefully received!27. Februar 2020 at 11:37 #48092
For me its easier to check the right soundcard on the command line. So I logged into the RPi by SSH (Logon: pi, Password: max2play) and become root („sudo bash“).
With the command arecord -L you get a list of the available audio input interfaces.
To your information: It is not possible to use the Audio-In Port in parallel with the Audio-Out Port, using SqueezeLite/WaveInput: Squeezelite normally uses the highest bit rate possible, WaveInput uses 16 Bit. The Hifiberry sound chip is not capable using different bit depth/sampling frequencies for simultainiously input and output.27. Februar 2020 at 12:40 #48093
Ahhhh…. that’s the whole reason I bought the hifiberry and setup M2P – I wanted to switch between the line-in port and streaming music from my NAS. 🙁
I know Volumio supports the line-in port, but only on their top paid plan.
I might switch to plan B and use an external amplifier and use a hardware switch to select the input feed to the amp
Many thanks for all your help – at least I know not to try any more – I could have wasted even more hours getting frustrated!!
You must be logged in to reply to this topic.