Forum Replies Created
-
Posted in: Allo USB Bundle
-
15. Juli 2020 at 6:41 #49315
Hi Bencat57,
Super interesting and thank you for sharing your experience. I am one of the (probably) few people out there using an RPi with Max2Play to deliver music to my Linn system – setup:
Raspberry Pi 4B 4GB
iFi iPower 5V Power Supply (yes it works despite 5V)
Max2Play (Beta) Buster Image 2.52
Logitech Media Server 7.9.2
UPnP/DLNA Bridge Plugin *… wireless connection to …
- NAS with FLAC/MP3/Playlists
- Linn Majik DSM/2 * via UPnP/DLNA Bridge Plugin
The Pi has no dedicated sound card HAT installed, and serves purely as a streamer/transport to the Linn.
Given your experience, I am obviously keen to try out an RPi 4 8GB.
I am wondering, are you using LMS to transcode your music before sending it on its way to the players? If yes, could the transcoding step be where the additional RAM and increased performance make a difference?
24. April 2020 at 19:50 #48610Hi MarioM, looks like 2.52 is out according to the changelog page. I’m not getting the usual „Update available“ message though on the Settings/Reboot page. I’m running the Beta RPi4 Raspbian Buster image (which updated from 2.50 to 2.51 with aforementioned update notification). Is 2.52 not yet meant for Buster?
Thanks and best,
jcu-muc16. April 2020 at 21:18 #48532Hi MarioM,
Thanks very much for the update, looking forward to the 2.52!
Looks like it’s going to be significant:
Is a Kernel update foreseen too for the release version?
Best,
jcu-muc11. April 2020 at 21:47 #48471Hi cramcram, under „Squeezebox Server start Installation“ >> „Alternative source from Slimdevices (package must be .deb)“ have you tried directly pasting the path to the lates 8.0 nightly? Located here: http://downloads.slimdevices.com/nightly/index.php?ver=8.0
Currently the latest would be http://downloads.slimdevices.com/nightly/8.0/lms/aaa663bb569ff4438e25c7e9a361d79b3716502d/logitechmediaserver_8.0.0~1586578181_arm.deb which is dated Apr 10.
Disclaimer – I am not affiliated with M2P and have not tried this. I would assume this is officially unsupported right now. But if I were to try it, I would first make a full backup image of my SD card before doing so. That being said, if you do give it a shot, do post results.
1. November 2019 at 8:50 #47459Hi Heiner,
Thank you for your reply. Enabled plugins are:
Max2Play Active Plugins:
– Settings / Reboot
– Audioplayer
– Squeezebox Server
– Filesystem Mount
– WiFi / LAN
– Raspberry SettingsSqueezebox Server Active Plugins:
– Full Text Search
– Mixcloud
– Network Test
– Podcasts
– Radio
– Random Mix
– Save Playlist
– Soundcloud
– UPnP/DLNA BridgeRegarding hardware, it is the RPi4 only – there is no dedicated soundcard. I am running Max2Play with Squeezebox Server, and transporting the music to an external Streamer with DAC via the LMS UPnP/DLNA Bridge plugin.
Best regards,
jcu24. Oktober 2019 at 23:09 #47434I tried it now myself, but made a backup image of the SD card first – which was a good idea:
After enabling „Enable 64 Bit Kernel (Pi4 ONLY)“ on my RPi 4 with 4GB RAM, it would no longer boot and I had to restore the backup image.
Heiner or anybody from the M2P team, any idea what the issue might be?
Many thanks,
jcu27. Januar 2017 at 16:05 #26365Hallo Steini,
siehe bitte hier https://www.max2play.com/en/forums/topic/musikordner-auf-nas-wd-my-cloud-im-squeezeserver-nicht-zu-finden/#post-25837 und probiere es damit.
Viele Grüße
JCU12. Januar 2017 at 23:32 #25837Hallo Ralf,
ich habe bei meinem Setup erst jetzt gemerkt, dass der Raspberry das Playlist-Verzeichnis zwar lesen konnte (ich hatte vorhandene M3U drin), aber in das Verzeichnis nicht schreiben konnte, trotz im WD My Cloud vergebene Schreibrechte für den User Raspberry. Ärgerlich und unverständlich, aber hier die Lösung:
//WDMYCLOUD/Music/Playlists
/media/Music/Playlists
cifs
user=raspberry,password=max2play,file_mode=0777,dir_mode=0777,sec=ntlm,iocharset=utf8Solved!
Viele Grüße
JCU11. Januar 2017 at 22:35 #25801Hello Stefan,
Thanks for this… 😉
— Updated M2P to latest Beta — OK
— Audiophonics Plugin Tab — Display — RE-Install Display Software — OKCleaning up... Set SERVER ADDRESS to 192.168.178.69 Use Interface wlan0 with b8:27:eb:bd:f5:a9 Set MAC ADDRESS to b8:27:eb:bd:f5:a9 Activated Squeezebox Server in RaspDAC-Display Finished - Reboot needed: Click here to Restart Device
— Display now shows track info as intended.
Q: Is it safe for me to edit RaspDacDisplay.py and pages.py in /opt/Raspdac-Display so I can customize the display output? I have customized versions of these files that I would ideally just like to overwrite the current default versions.
Excellent work guys, thank you very much.
Best regards,
JCUEdit: By the way, is it my imagination, or does the I-Sabre-V3 music output sound better now?? Did you tweak some new parameters when selecting the card in the configuration?
11. Januar 2017 at 16:12 #25773Hello Heiner!
Thanks very much for this and apologies for the slow response.
I gave the plugin a try yesterday but must admit I’ve encountered some problems.
— The power button works
— The display turns on and initializes (displays „Ready“ etc. after booting)
— However, the display does not show any music info when playing music – it just remains stuck at „Ready“
I searched for and found the Raspdac-Display configuration files at
/opt/Raspdac-Display/
I checked RaspDacDisplay.py to see if the plugin had properly set the MAC address of my LMS player, which it had not.
For anyone new to this topic, it is important to understand that the following files in /Raspdac-Display/ determine the behavior of the display:
— RaspDacDisplay.py: General settings, time zone, MAC-address of LMS player
— pages.py: Configure what the display shows and set scrolling behaviorFor detailed instructions on what and how to edit these files see https://github.com/dhrone/Raspdac-Display
After manually editing RaspDacDisplay.py and setting my MAC-address as listed in Logitech Media Server, still no luck.
I did notice that the plugin tries to determine the proper MAC address and write it to RaspDacDisplay.py by determining if ethernet is on, or WLAN0. On my RaspDAC, I have no ethernet and use an external Wifi stick for better reception. In Raspberry Settings I have the following activated: „Disable Default WiFi Interface WLAN0 on RPI3“. I unchecked this and went back to the default setting, rebooted, and still no luck…
Any idea? Does anyone else have different results?
Best regards,
JCU9. Januar 2017 at 13:00 #25688Hallo Ralf,
sorry für die späte Reaktion, ich war ein paar Tage unterwegs. Freut mich sehr, dass es nun endlich geklappt hat – auch wenn die Gründe des Gelingens unklar sind. Der Reset der WD My Cloud war wohl der Schlüssel zum Erfolg. Aus eigener Erfahrung kann ich sagen, dass die My Cloud etwas zickig sein kann; wie es sich mit anderen NAS (Synology,QNAP) verhält, kann ich leider nicht sagen.
Anyway – enjoy!
Viele Grüße
JCUFor the English speakers amongst you: After numerous unsuccessful attempts to get a WD My Cloud NAS to work with Max2Play & Logitech Media Server – even with seemingly correct and otherwise proven settings – the solution was to reset the WD My Cloud NAS via its web administration. This evidently did the trick.
4. Januar 2017 at 11:28 #25460Hallo Ralf,
ich habe dir hier ein paar Screenshots von meinen Einstellungen hochgeladen, bitte sage mir wenn Du sie hast, dann nehme ich sie wieder runter:
https://www.dropbox.com/s/1bmur98cv6rpfq9/settings.zip?dl=0
Vergleiche bitte mit deinen Einstellungen und auch mit meiner Mount-Konfiguration vom letzten Post.
Ich würde an deiner Stelle die vorhandenen Mounts löschen und neu anlegen.
Good luck!
JCU4. Januar 2017 at 0:03 #25445Hallo Ralf,
ich habe auch eine WD My Cloud und wie folgt angebunden:
1. In der My Cloud Administration einen User „raspberry“ mit passwort „xyz123“ eingerichtet. Der User raspberry hat Lese- und Schreibrechte auf den Musikordner (auch bei mir ist er public, aber so bekommt er explizite Rechte)
2. In Max2Play sind meine Ordner wie folgt eingebunden:
//WDMYCLOUD/Music/MP3
/media/Music/MP3
cifs
user=raspberry,password=xyz123,sec=ntlm,iocharset=utf8//WDMYCLOUD/Music/FLAC
/media/Music/FLAC
cifs
user=raspberry,password=xyz123,sec=ntlm,iocharset=utf8//WDMYCLOUD/Music/Playlists
/media/Playlists
cifs
user=raspberry,password=xyz123,sec=ntlm,iocharset=utf8Passe die Pfade an, damit sie für Dich stimmig sind. Am Besten die My Cloud neu booten, danach Max2Play auch neu booten, und vielleicht hat das was gebracht.
Viel Glück!
JCUPS – fällt mir gerade ein, vielleicht ist das Leerzeichen in „Shared Music“ ein Problem. Ggf. umbenennen in „Music“.
3. Januar 2017 at 23:33 #25440Hi Oswald,
I have in the past also had LMS library scanning issues – which as it turns out were caused by faulty / corrupted tags. Try rescanning and possibly repairing the tags with Mp3tag (http://www.mp3tag.de/). In my case, some of my files had invalid APE tags.
In Mp3tag, go to Tools – Options – Tags – Mpeg – and under „Read“ select all, under „Write“ select ID3v2 / ID3v2.3 UTF-16 and under „Remove“ select ID3v1 and APE.
Now load all of your music files, select all, and then click the red X („Remove tag“). This will then remove all ID3v1 and APE tags from your files.
Next, select all files and CTRL-S – this will then save and rewrite all tags properly as ID3v2.3 UTF-16.
Finally, in LMS, go to Settings – Rescan Media Library –> Clear library and rescan everything.
No guarantees, but this worked for me. This is particularly helpful if your music files are from various sources with inconsistent and possibly invalid tagging schemes.
Good luck!
JCUPS – further to Heiner’s answer, you can find the explicit LMS media library scan log under Settings – Information (Tab) – scroll to the bottom – Scanner Log File. This will contain any errors the scanner encountered.
8. Dezember 2016 at 19:13 #24708Hi Tmax,
To be honest I am not sure if this setting completely disables the onboard wifi or merely renames and moves it from wlan0 to wlan1. I believe it does the latter.
The setting in any event makes an exterior USB wifi stick the default wlan0. I have two different RPi-Max2Play setups and use USB wifi sticks (and this setting) on both. It made quite a difference in terms of signal connection strength – and in turn in listening enjoyment as well, particularly with larger FLAC files…
8. Dezember 2016 at 18:45 #24704Hi Tmax,
Yes there is, just go to the Raspberry Settings tab and activate
Disable Default WiFi Interface WLAN0 on RPI3 [ ] This moves the build-in WiFi on Pi 3 to wlan1. This is necessary to add another WiFi stick on interface wlan0.
Best regards,
JCU8. Dezember 2016 at 17:58 #24702Hi Christoph,
I see that M2P 2.39 is out as of today and now natively supports the Audiophonics I-Sabre-V3 via the Raspberry Settings tab – thank you!
Just to confirm:
I have selected Audiophonics I-Sabre-V3 and in the Audioplayer tab / Squeezelite Advanced Options added -o hw:0 to the Command Line Options. On the HifiBerry tab, it now reads under Your installed HiFiBerry Card: none
I guess that is all the way it is supposed to be then?
Many thanks!
JCU5. Dezember 2016 at 18:36 #24566Update: I have replaced the RPi3 with a brand new unit and everything is up and running again.
Moral of the story: A normal, everyday static discharge can and will kill your RPi – even when it is inside a proper case. The IQaudIO Pi-DAC+ appears to be in good working order with its new RPi3.
Be warned and take care. 😉
1. Dezember 2016 at 18:51 #24474Nach einigen Recherchen sieht es leider so aus, als ob mein Pi durch die statische Entladung gekillt / gebricked wurde, trotz Verbau im Gehäuse. Dies als Mahnung an alle M2P-Enthusiasten mit Wollpullovern in der kalten Jahreszeit. 😉 Die Entladung ereignete sich übrigens mit dem IQaudIO Case an einem der 4 großen äußeren Metallbolzen…
Siehe auch https://www.raspberrypi.org/forums/viewtopic.php?f=26&t=22152
After having researched the issue a bit, it unfortunately appears that I did indeed kill / brick my Pi via static discharge, even within its casing. This is meant as word of warning to a all M2P-Enthusiasts with woolen sweaters during the cold time of year. 😉 The discharge occcured with the IQaudIO case on one of the 4 big exterior bolts.
See also https://www.raspberrypi.org/forums/viewtopic.php?f=26&t=22152
I will give it another go tomorrow, but I expect the end result will be a required replacement of the RPi3 board. 🙁
30. November 2016 at 0:24 #24362Hi Popper,
Very happy that you were able to get things working, I appreciate it and understand, as I struggled for a while as well. I honestly believe that Max2Play is the best platform out there, at least for me, as it offers Logitech Media Server as a basis. Volumio, RuneAudio have better out of the box support for Sabre DACs, but I need the superior library management etc. that LMS offers.
Regarding the command line option, SSH into your RPi and enter „amixer“ and see what it outputs. That is the official procedure. That being said, that didn’t work for me since evidently the Audiophonics Sabre has no hardware volume control. I just went ahead and entered -o hw:0 -V Digital on good faith and was pleased with the results. If you encounter problems, you can always go back and delete the command line options and carry on. Again, the command line options worked well for me and the sound was instantly much deeper, warmer, richer – essentially what I had been expecting from the DAC to begin with. 😉
If you are a Linux newbie such as myself, you can SSH via Windows with PuTTY, available here: http://www.putty.org/ To determine the IP address you need to SSH into, go to http://max2play/ and go to the tab WiFi/LAN – there you will see the IP address. Username: pi Password: raspberry
Edit: just for the hell of it, if you need admin privileges for anything else, you can su with pw: max2play
Best regards,
Jason29. November 2016 at 17:16 #24355Hi Thomas!
Great to hear from you too, and that you were able to get the power button working on the Audiophonics Network Player. I bet you were relieved when it stopped blinking! 😉
Perhaps (probably!) I am missing something… when I SSH into the IQaudIO RPi and enter ‚amixer‘ I get the following output, and no indication regarding whether to choose ‚Digital‘ or ‚Master‘:
login as: pi [email protected]'s password: The programs included with the Debian GNU/Linux system are free software; the exact distribution terms for each program are described in the individual files in /usr/share/doc/*/copyright. Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent permitted by applicable law. pi@max2play:~ $ amixer Simple mixer control 'DSP Program',0 Capabilities: enum Items: 'FIR interpolation with de-emphasis' 'Low latency IIR with de-emphasis' 'High attenuation with de-emphasis' 'Fixed process flow' 'Ringing-less low latency FIR' Item0: 'FIR interpolation with de-emphasis' Simple mixer control 'Analogue',0 Capabilities: pvolume Playback channels: Front Left - Front Right Limits: Playback 0 - 1 Mono: Front Left: Playback 1 [100%] [0.00dB] Front Right: Playback 1 [100%] [0.00dB] Simple mixer control 'Analogue Playback Boost',0 Capabilities: volume Playback channels: Front Left - Front Right Capture channels: Front Left - Front Right Limits: 0 - 1 Front Left: 1 [100%] [0.80dB] Front Right: 1 [100%] [0.80dB] Simple mixer control 'Auto Mute',0 Capabilities: pswitch Playback channels: Front Left - Front Right Mono: Front Left: Playback [on] Front Right: Playback [on] Simple mixer control 'Auto Mute Mono',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'Auto Mute Time Left',0 Capabilities: enum Items: '21ms' '106ms' '213ms' '533ms' '1.07s' '2.13s' '5.33s' '10.66s' Item0: '21ms' Simple mixer control 'Auto Mute Time Right',0 Capabilities: enum Items: '21ms' '106ms' '213ms' '533ms' '1.07s' '2.13s' '5.33s' '10.66s' Item0: '21ms' Simple mixer control 'Clock Missing Period',0 Capabilities: enum Items: '1s' '2s' '3s' '4s' '5s' '6s' '7s' '8s' Item0: '1s' Simple mixer control 'Deemphasis',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] Simple mixer control 'Digital',0 Capabilities: pvolume pswitch Playback channels: Front Left - Front Right Limits: Playback 0 - 207 Mono: Front Left: Playback 207 [100%] [0.00dB] [on] Front Right: Playback 207 [100%] [0.00dB] [on] Simple mixer control 'Max Overclock DAC',0 Capabilities: volume volume-joined Playback channels: Mono Capture channels: Mono Limits: 0 - 40 Mono: 0 [0%] Simple mixer control 'Max Overclock DSP',0 Capabilities: volume volume-joined Playback channels: Mono Capture channels: Mono Limits: 0 - 40 Mono: 0 [0%] Simple mixer control 'Max Overclock PLL',0 Capabilities: volume volume-joined Playback channels: Mono Capture channels: Mono Limits: 0 - 20 Mono: 0 [0%] Simple mixer control 'Volume Ramp Down Emergency Rate',0 Capabilities: enum Items: '1 sample/update' '2 samples/update' '4 samples/update' 'Immediate' Item0: '1 sample/update' Simple mixer control 'Volume Ramp Down Emergency Step',0 Capabilities: enum Items: '4dB/step' '2dB/step' '1dB/step' '0.5dB/step' Item0: '4dB/step' Simple mixer control 'Volume Ramp Down Rate',0 Capabilities: enum Items: '1 sample/update' '2 samples/update' '4 samples/update' 'Immediate' Item0: '1 sample/update' Simple mixer control 'Volume Ramp Down Step',0 Capabilities: enum Items: '4dB/step' '2dB/step' '1dB/step' '0.5dB/step' Item0: '1dB/step' Simple mixer control 'Volume Ramp Up Rate',0 Capabilities: enum Items: '1 sample/update' '2 samples/update' '4 samples/update' 'Immediate' Item0: '1 sample/update' Simple mixer control 'Volume Ramp Up Step',0 Capabilities: enum Items: '4dB/step' '2dB/step' '1dB/step' '0.5dB/step' Item0: '1dB/step' pi@max2play:~ $
EDIT: Since I have disabled to on-board audio of the RPi3, is it possible that that is the reason why it does not differentiate between Digital and Master, i.e. amixer only „sees“ one audio device, the IQaudIO?
An updated Power Button how-to with your edits would be great, aber kein Stress… 😉
Best regards,
Jason29. November 2016 at 16:23 #24346Hi there, good question, I would also like to know…
I have two RPIs with Max2Play – and on both I have the setting „Disable Build-In-Audio on RPI3“ activated)
1. RPI3 with IQaudIO Pi-DAC+
Here I used -o hw:0 -V Digital and it seems to have worked. Should I use „Master“ instead of „Digital“?
2. Audiophonics RaspDAC with I-Sabre V3 DAC ES9023 TCXO
Here I also used -o hw:0 -V Digital – this card uses the Hifiberry DAC (not DAC+!) I2S driver, and supposedly has no hardware volume controls. I believe the setting made a difference, does that make any sense?
@ Thomas – check this out to set max volume 96%: https://support.hifiberry.com/hc/en-us/articles/205385241-Mixer-controls-on-the-HiFiBerry-boards.
But that does not work for my I-Sabre… alsamixer says no volume control.
Any help or comments?
Best regards,
JCU29. November 2016 at 11:42 #24296Hello,
I have an Audiophonics I-Sabre DAC in one of my RPi setups (it’s a RaspDAC streamer box). Please follow the instructions below, might also work for you:
1. Install Max2Play HiFiBerry Image
2. On the HifiBerry Tab:
Select:
Hifi Berry DAC (PI A/B)
3. On the Audioplayer Tab:
Squeezelite –> Edit advanced options
Soundcard:
sysdefault - snd_rpi_hifiberry_dac, - Default Audio Device, CARD=sndrpihifiberry
ALSA Parameter:
80:4::
Command Line Options:
-o hw:0 -V Digital
This command line option noticeably improved the sound quality, at least to my ears. Please see the following Wiki post for more details:
https://www.max2play.com/en/wiki/optimizing-squeezelites-volume-control/@ Max2Play team – questions about M2P support of I-Sabre DACs are becoming more frequent. Is there any chance you could add proper support for the following DAC in the next release, i.e. so it can just be chosen in the dropdown list? There may also be additional parameters which might further improve sound quality. Please see
AUDIOPHONICS I-Sabre V3 DAC ES9023 TCXO Raspberry Pi 3 / Pi 2 A+ B+ / I2S
Best regards,
JCU- This reply was modified 7 years, 11 months ago by jcu-muc.
18. November 2016 at 11:26 #23962Hallo Thomas,
tut mir leid und siehe bitte unten – ich hatte dummerweise vergessen, dir folgende wichtige Edits zu der Anleitung zu senden. Many apologies. 🙁
TYPO in A. Files for the display
Code:
OLD: sudo cp RaspdacDisplay.py /usr/local/bin/ NEW: sudo cp RaspDacDisplay.py /usr/local/bin/
BUG in file „sds.service“ – needs to be fixed before performing steps in B.
Der folgende Fix ist besonders wichtig, da das falsche File referenziert wird!
Code:
OLD: ExecStart=/usr/local/bin/sds.sh NEW: ExecStart=/usr/local/bin/sdsmax.sh
TYPO in B. Files for the power management function
Code:
OLD: chmod +x /usr/local/bin/sdsmax.sh NEW: sudo chmod +x /usr/local/bin/sdsmax.sh
Code:
OLD: systemctl enable sds.service NEW: sudo systemctl enable sds.service
Sorry nochmals, dass ich das in meiner ursprünglichen Antwort vergessen hatte.
Viele Grüße
Jason10. November 2016 at 12:41 #23858Hallo Thomas,
tja, es gibt gute Nachrichten… 🙂
Schau mal bitte hier https://github.com/dhrone/Raspdac-Display
Dhrone hat sich die große Mühe gemacht um den RaspDac mit Display & Power Button zum Laufen zu bringen. Scrolle runter bis Instructions for Max2Play. Da Du kein Display hast, kannst Du die Configs für die Anzeige einfach weglassen und nur die für den Power Button nutzen.
Ich habe den RaspDAC V3 mit Display – und bei mir läuft M2P 2.37 mit Logitech Media Server jetzt 1A ohne Blinken und mit schöner Anzeige. 🙂
Beste Grüße
Jason24. Oktober 2016 at 17:09 #23560I forgot to mention that the sound quality is GREAT. The IQaudIO feeds a Linn pre-amp –> Linn power amp –> Linn speakers and am smitten to say the least.
24. Oktober 2016 at 17:05 #23558Hi Tim,
I have an RPi3 with an IQaudIO Pi-DAC+ running the current Max2Play image 2.37. My Logitech Media Server runs directly on the Pi (using the latest nightly build) and it gets its music – 35.000+ tracks – from a simple NAS (actually a USB HDD attached to a Fritz Box router). Squeezeplay is also running on the Pi. It works beautifully, the only performance bottleneck being the slow performance of the USB HDD itself… but even that works nicely. 🙂 With this setup it takes around 10 minutes for a library scan to add new music, and a few hours if you’re doing a full database rebuild. I use it entirely via WLAN – and the network throughput works well up to 16 Bit FLAC filesizes. 24 Bit and you would probably fare better using ethernet. My suggestion – go for it and enjoy. 😉
Best,
JCU- This reply was modified 8 years, 1 month ago by jcu-muc.
19. September 2016 at 20:10 #23106Hi Jac,
You can make a bookmark of this URL to shut down safely from any browser within your network:
http://max2play/plugins/max2play_settings/controller/Basic.php?action=shutdown
Alternatively, if your Pi always has the same IP address you can use
http://IP_ADDRESS_HERE/plugins/max2play_settings/controller/Basic.php?action=shutdown
Best regards,
JCU -