Martin

Forum Replies Created

Viewing 16 posts - 1 through 16 (of 16 total)
  • Posted in:
  • 31. März 2022 at 20:16 #52164

    Perhaps I should add that in the M2P web interface, „Show available Versions“ doesn’t display anything. I have tried loading into the field „Alternative source from Slimdevices“ the address for builds for LMS 7.3 and for LMS 8.2, but neither of them installs successfully.

    I see reference on the Forum to use of LMS 8 under M2P, but I don’t know if this includes the Allo Sparky. And the links to LMS 8 seem broken.

    Any help would be appreciated. I have a bug with LMS 7.1 where the speakers go silent but the woofer continues playing.

    31. März 2022 at 0:02 #52160

    I have been using LSN 7.1 for some time. Does a more recent version work with M2P? Perhaps7.3? Or even 8.2?

    I am running Max2Play on an Allo Sparky.

    Thanks

    18. Juni 2019 at 15:02 #45859

    Hi Heiner,

    So the updates to Max2Play for the Sparky (I just upgraded to M2P 2.48) are prepared by Allo?

    Martin

    17. Juni 2019 at 18:57 #45812

    How about the version of Max2Play on the Allo Sparky? I’ve tried using user Allo and password max2play, but without success.

    19. April 2017 at 0:33 #28337

    I was able to install the Allo Plugin (<https://www.max2play.com/en/portfolio/plugin-allo/&gt😉 into the Sparky version of Max2Play version 2.41.

    The sliders that were then visible no longer included the subwoofer volume (Like this image: <https://www.max2play.com/?galleries=plugin-allo-en&gt;), which made me hopeful that there was now a single system volume that could be controlled through iPeng or similar.

    However, after this installation the squeezelite player would no longer run, so I was unable to test this possibility.

    Martin

    16. April 2017 at 3:24 #28267

    Lanny501, I’ve reinstalled with Max2Play 2.41, which does not offer, or call for, a custom kernel. I am currently avoiding 2.42 because I’ve found that with that version:
    1. the message to install the custom kernel reappears each time after I have attempted the install
    2. the sound quality is notably poorer

    With 2.41 I had to set the subwoofer mode to 2.1. However, like you, I’m finding that when I adjust the volume (I use both iPeng and Squeezepad) the subwoofer volume is unchanged.

    Perhaps someone at Max2Play Headquarters can tell us whether the custom kernel is in fact installed by 2.42, and why the sound might be poorer with that installation.

    Anyone else out there using the Piano 2.1?

    Martin

    13. April 2017 at 13:42 #28222

    That seems quite disingenuous, Mohammad. You provide a version of Max2Play that runs on the Sparky (sparky_sd_vana_1_3_200317). This identifies itself as „Version 2.41, Allo Sparky“. It upgrades to „Version 2.42, Allo Sparky.“

    In addition, on the Max2Play website you announced in December 2016, „We are happy to announce a new Max2Play Partner today: Allo. With the Piano Dac 2.1 by Allo, we are now, for the first time, supporting a sound card that also supports a subwoofer… The sound card is compatible with both the Raspberry Pi and the Allo-developed Sparky-Board…. Thus, we recommend the Kali Reclocker in combination with the Piano DAC 2.1 in our Shop. This combination works, as usual with Max2Play, directly out-of-the-box…“

    Where on you webpages do you state that you do not guarantee the behaviour of Max2Play on the Sparky?

    Martin

    12. April 2017 at 21:22 #28190

    There seem to be some oddities about the way Max2Play handles the Allo DAC Piano 2.1. (I should add that I’m running this DAC on the Allo Sparky, not on the Raspberry Pi.)

    The version of Max2Play that is downloaded from the Allo site is 2.41. With this version:
    1. Selecting the Piano 2.1 DAC from the drop down menu makes available the various sliders to control the DAC.
    2. There is no mention of a special driver or kernel being needed.
    3. However, the slider control for the subwoofer (“Settings for Subwoofer Mode (2.0, 2.1, 2.2), Default 2.1”) are set to 2.0, even though it is stated that 2.1 is the default.
    4. There is no sound from the subwoofer.

    After upgrading to Max2Play 2.42:
    1. Messages start to appear that a custom Kernel is needed for the Piano 2.1.
    2. However, these messages refer to the wrong DAC (the Boss, not the Piano 2.1). Consequently, I have ignored them. [I have screen shots of all this]
    3. The slider control for the subwoofer is still set to 2.0 instead of 2.1.
    4. After clicking the button to “restore the defaults” for these sliders, the slider control is now set to 2.1, and there is indeed now sound from all three speakers.
    5. However, the speakers don’t seem very balanced, and I haven’t yet figured out how to actually change the volume etc. ‘on the fly.’ I’m starting to think that playback has to be stopped and started again before changed settings take effect.

    Does anyone know how to check which kernel/driver has actually been installed?

    Martin

    12. April 2017 at 16:59 #28185

    Now all sorts of problems! Switching to the default Allo settings (Dac 2.1; not sure how or when they had switched to 2.0), I get sound from the subwoofer but nothing from the other speakers. Switching back to 2.0, now Max2Play hangs on reboot. Guess I’ll have to burn the image again and start over. 🙁

    12. April 2017 at 16:18 #28184

    I have been trying to install the Allo 2.1 custom kernel, on the Allo version of Max2Play. When I run the install, I get the messages copied below, which I find rather confusing. The installation *seems* to be successful, but after a restart I get the same message as previously: „Important: The PianoDAC with Subwoofer and the Allo Boss need a custom Kernel to run! Click here to install custom Kernel now!“
    ===
    Important: The PianoDAC with Subwoofer and the Allo Boss need a custom Kernel to run! Click here to install custom Kernel now!
    Kernel Update started
    Installation started – This Messages refreshes every 3 seconds to show current installation status. When finished this message disappears.
    2011-01-01 18:17:14|
    Finished – Reboot needed! Click here to Reboot Now

    Important: The PianoDAC with Subwoofer and the Allo Boss need a custom Kernel to run! Click here to install custom Kernel now!
    Boot config parameters changed
    Please restart your device! To restart now just click here.
    Important: The PianoDAC with Subwoofer needs a custom Kernel to run! Click here to install custom Kernel now!

    6. Juli 2016 at 19:30 #21274

    Thanks, Heiner. I had assumed that disabling the plugin would mean that Squeezelite wouldn’t load, but I was evidently wrong! I’ve now turned off both Squeezelite and the Airplay feature, so that’s solved my second problem.

    As for the first, nothing shows in the Mount menu:
    External Drives on Max2Play – mountpoints for USB-Storage
    This list shows all external storages and their mountpoints. You may access the devices by their path in Squeezeboxserver or XBMC/Kodi. Important: the maximum partition size is 2TB. If using larger disks you need to divide the disk space into partitions smaller than 2TB.
    No external devices found.

    But the Squeezeboxserver still sees the drive and happily plays from it. I will need to disconnect the drive to check its format, which I’m reluctant to do. I’ve been using it on a MacMini, so it’s a Mac friendly format. I guess I’ll use SSH to mount it properly

    6. Juli 2016 at 13:35 #21263

    I should have explained that I got the error message before renaming, read your post and renamed from Max2Play to raspberry, but still got the error.

    I have in fact started another topic on the mounting problem.

    cheers

    6. Juli 2016 at 4:04 #21232

    I am using M2P 2.32 and I’ve changed the server name to ‚raspberry,‘ but I am seeing similar errors. For example, when I try to create a mount point:

    sudo: unable to resolve host raspberry Timed out Password for [email protected]//192.168.0.22/: Retrying with upper case share name mount error(6):

    29. Juni 2016 at 19:53 #20913

    Sorry to pester you with questions, Heiner. The installation runs fine, but I can’t get to Max2play in a browser. On my MacBook I can see max2play as a shared computer, but I get an error when I try to connect. Max2play even shows up as a player on my Squeezeserver software. But neither in Safari nor Firebox can I access the web interface. Sometimes the browser finds your web site, other times it can’t open the page. What am I doing wrong?

    29. Juni 2016 at 15:55 #20910

    That’s unfortunate: just yesterday I bought a Class 4 card. Where on the downloads page is it specified that a Class 10 is needed?

    27. Juni 2016 at 19:49 #20901

    Thanks for this information, Heiner. What is a bit confusing is that the other images state explicitly that a 4G card is needed (on the download page). But nothing is said for this image, which suggests that it doesn’t need as card as large as 4G.

    Now I’m off to the store to buy a larger card, and we’ll see how that works! 🙂

Viewing 16 posts - 1 through 16 (of 16 total)