Megantonneke

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Back to forum
    Posted in: Allo USB Bundle
  • Megantonneke premium
    2. September 2017 at 11:27 #31083

    I made short tutorial video on my youtube channel, on how to install the plugin. I did this previously also for the Volumio Spotify connect plugin so it seemed fair to have also a video to show similar functionality in Max2play. Great to see that Max2play put so much effort in bringing this functionality also to their platform!

    So far I have tested the Spotify connect beta plugin on a raspberry pi zero (running Max2play Version Beta-170523) and a zero W (running Max2play Version 2.43) and have following issues:

    – The intial volume when you switch to max2play Spotify connect device is at max. (I understand that this a librespot issue)
    – Spotify connect devices disappearing over time, while the Spotify connect service is still running on the device. It seems that is when this
    system stay idle for some time the connection with the Spotify connect server is lost. I have checked if squeezelite was active and interfering but this was not the case. Stopping and restarting the Spotify connect service via the WebUI, resolved the issue, but is inconvenient if you just want to play something using spotify.

    Megantonneke premium
    19. Mai 2017 at 13:33 #28955

    Thanks for the effort Heiner, I will be testing the M2P spotify connect implementation as soon as I can, and spread the word!

    Greetings,

    Megantonneke

    Megantonneke premium
    20. Januar 2017 at 23:57 #26173

    I cannot install/use the Rpi display add-on as my screen is not one of the supported screens from the pull-down menu, when want to install this addon. I am almost sure that when I would select one of the listed screens, I might end up with no image at all. My screen uses the HDMI output of Rpi and not GPIO or Screen header of the board.

    Megantonneke premium
    20. Januar 2017 at 13:21 #26152

    Yes, an implementation of the Spotify Connect Server would be a big step forward for M2P, in my view. To be honest I am flabbergasted that M2P as „Multiroom Audio OS“ does not seem to take this seriously.

    I am currently using Max2play with a Squeezeserver and JiveLite on a Rpi 3 + touchscreen to control a Pi zero running Max2play and a Squeezebox receiver unit and stream Spotify audio to them. It works, but Squeezeserver feels and looks dated and for example sound synchronization is flaky. This works for example better using the Squeezer android app than using the JiveLite interface. The interface of the Spotify plugin is also not great in comparison to the native Spotify app/software and this plugin does not get any further development or support by Triode anymore.

    I am keeping a keen eye on the developments at Volumio, with the Spotify Connect add-on. I am already considering to switch my playback devices to Volumio+Spotify Connect and to install Android on my Rpi 3 + touchscreen to be able to run the Spotify App natively and control the playback devices using that…

    Greetings, Anton

    Megantonneke premium
    9. Januar 2017 at 14:21 #25693

    Hi Dboy,

    I myself am also using a logitech duet receiver unit with LMS on a Raspberry Pi 3 and I have it working. But I am in the unfortunate situation that my Duet controller unit has charging issues so I can’t use it.

    But in my search for solutions I came across a perl script, which can be used to access the configuration of the logitech reciever directly and adjust settings, This may also help you. It is called Net:UDAP. This article explains how to use it and explains the different setup parameters. Especially the server_address:
    squeezecenter_address: should reflect the IP address of your LMS server machine.

    I am currently controlling the my logitech squeezbox receiver using Rpi 3 with LMS using max2play and jivelite using touchscreen. This works, but only with WiFi enabled, while my Rpi 3 has also an ethernet-connection using a cable. I am still puzzled by that bit myself.

    Greetings,

    Megantonneke

    Megantonneke premium
    4. Oktober 2016 at 22:13 #23277

    I tried again using the exact same /etc/X11/xorg.conf.d/99-calibration.conf entries as explained in the previous mentioned tutorial, as it deals with the extact same monitor. This works! I still don’t know why it got botched by the actual calibration numbers that xinput_calibrator recordered, but I am gonna leave it with that.

    So /etc/X11/xorg.conf.d/99-calibration.confnow states:

    Section "InputClass"
	Identifier	"calibration"
	MatchProduct	"ITM Inc USB Touch Panel"
	Option	"Calibration"	"125 4015 3940 160"
	Option	"SwapAxes"	"1"
	Option "InvertX" "true"
	Option "InvertY" "true"

    Greetings,

    Megantonneke

    • This reply was modified 7 years, 6 months ago by Megantonneke.
Viewing 6 posts - 1 through 6 (of 6 total)