Ezaul Zillmer

Forum Replies Created

Viewing 9 posts - 1 through 9 (of 9 total)
  • Back to forum
    Posted in: Allo USB Bundle
  • Ezaul Zillmer premium
    2. Juni 2024 at 20:40 #53202

    Good afternoon!

    I would like to know if I can update my max2play???

    update to Bullseye or Bookworm

    Is it just me or is this forum abandoned? Nor do developers respond to their customers?

    Could anyone help us update our max2play?

    We would be grateful to have any response in advance.

    Ezaul Zillmer premium
    19. Mai 2024 at 23:04 #53192

    Good afternoon my noble friends!

    I noticed that some years ago we no longer have updates on max2play, I bought a 5-year license, it’s almost expiring and I see that nothing has changed during these 5 years

    Did the project die?

    Are you going to open it up for the community to continue?

    Right now I needed to update my jellyfin which has been running together with max2play for 5 years and I noticed that I can’t update it because it’s still in 32bits

    Could you answer me as I will have to evaluate whether I will buy the Max2play license again

    Personal opinion, sad to see such a project die like this…

    Ezaul Zillmer premium
    17. Juli 2023 at 23:55 #52871

    Goodnight!

    I’m configuring my max2play with my home assistant and I have a problem with max2play that doesn’t accept https:// how can I enable ssl for max2play what would be the procedure?

    Thank you very much in advance

    Ezaul Zillmer premium
    29. März 2021 at 16:37 #51052

    good morning my friend!

    That that would comment on the need to put 8.2 to work ?? here are the changes

    Version 8.2.0

    

New Features:
Try to group online artists with local artists by ignoring slightly different spelling (eg. "The Beatles" vs. "Beatles", "Amy Macdonald" vs. "Amy MacDonald").
a href="https://github.com/Logitech/slimserver/pull/537">#537 - Add audio option to combine channels to build a mono signal (whether player is synchronized or not).
a href="https://github.com/Logitech/slimserver/pull/538">#538 - Add Balance setting for players which support it (thanks philippe44!).

Server Changes:
When an online scan doesn't return any track, but previously had some, do not remove tracks from library. The empty new list is likely due to a scan failure.
Try to improve backwards compatibility with eg. Erland's plugins, which sometimes struggle with the remote tracks.
#411 - Transcoder conversion rules: Support resampling for Ogg/Flac streams (thanks bpa/mw9!)

Platform Support:
#18 - Add a systemd service file for Debian based systems (thanks mw9 & tomscytale).
#22 - Add systemd service configuration for RPM based systems (thanks JohanSaaw!)
#526 - Add Perl 5.32 and 5.30 support for Linux aarch64 platform. (thanks clivem!)
Remove Font::FreeType from Linux distributions. It's easy enough to install it using the system's package manager, and it would conflict on system where we don't provide the binary.

Bug Fixes:
#554 - Long current playlist disappears from UI during wipe and rescan.

Other:
#528 - On Unix-like platforms, we now ensure that plugins are installed in such a way that none of their files are writable by users other than the user running LMS, even if theyʼre stored that way in the plugin ZIP file.

    Bencat57 and as MarioM already said you are having a problem with your installation … redo your card and install the version of Logitech Media Server that you want through the Max2play control pane

    • This reply was modified 3 years, 7 months ago by Ezaul Zillmer.
    Ezaul Zillmer premium
    16. März 2021 at 3:09 #50947

    apt –purge remove logitechmediaserver

    rm /usr/share/squeezeboxserver -Rf
    rm /var/lib/squeezeboxserver -Rf

    install Menu Max2play
    http://downloads.slimdevices.com/LogitechMediaServer_v8.1.1/logitechmediaserver_8.1.1_arm.deb

    Resolvido!

    Ezaul Zillmer premium
    15. März 2021 at 17:53 #50945

    Good afternoon

    Version 2.53
    Raspberry PI 3b+

    Linux max2play 5.10.20-v7+ #1404 SMP Thu Mar 4 19:40:23 GMT 2021 armv7l GNU/Linux

    I’m having a problem with Squeezebox Server on MAX2Play I don’t know if it was after some system update. Simply stopped accessing
    in the Max2play control panel is active

    Status: Squeezebox Server is running with processID 509

    ● logitechmediaserver.service – LSB: Startup script for the Logitech Media Server
    Loaded: loaded (/etc/init.d/logitechmediaserver; generated; vendor preset: enabled)
    Active: active (running) since Sun 2021-03-14 20:12:09 -03; 16h ago
    Docs: man:systemd-sysv-generator(8)
    Process: 374 ExecStart=/etc/init.d/logitechmediaserver start (code=exited, status=0/SUCCESS)
    Tasks: 3 (limit: 4915)
    CGroup: /system.slice/logitechmediaserver.service
    ├─ 509 /bin/bash /usr/sbin/squeezeboxserver_safe /usr/sbin/squeezeboxserver –prefsdir /var/lib/squeezeboxserver/prefs –logdir /var/log/squeezeboxserver/ –cachedir /var/lib/squeezeboxserver/cache –charset=utf8
    ├─4699 /usr/bin/perl /usr/sbin/squeezeboxserver –prefsdir /var/lib/squeezeboxserver/prefs –logdir /var/log/squeezeboxserver/ –cachedir /var/lib/squeezeboxserver/cache –charset=utf8
    └─4700 sleep 5

    mar 14 20:12:08 max2play systemd[1]: Starting LSB: Startup script for the Logitech Media Server…
    mar 14 20:12:09 max2play logitechmediaserver[374]: Making sure that Logitech Media Server is not running first: No process in pidfile ‚/var/run/logitechmediaserver.pid‘ found running; none killed.
    mar 14 20:12:09 max2play logitechmediaserver[374]: Starting Logitech Media Server.
    mar 14 20:12:09 max2play systemd[1]: Started LSB: Startup script for the Logitech Media Server.

    lsof -i -P -n
    COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
    avahi-dae 465 avahi 12u IPv4 15469 0t0 UDP *:5353
    avahi-dae 465 avahi 13u IPv6 15470 0t0 UDP *:5353
    avahi-dae 465 avahi 14u IPv4 15471 0t0 UDP *:36088
    avahi-dae 465 avahi 15u IPv6 15472 0t0 UDP *:55446
    sshd 674 root 3u IPv4 16536 0t0 TCP *:22 (LISTEN)
    sshd 674 root 4u IPv6 16538 0t0 TCP *:22 (LISTEN)
    rpimonito 760 pi 4u IPv4 14986 0t0 TCP *:8888 (LISTEN)
    shairport 787 pi 3u IPv4 16216 0t0 TCP *:5000 (LISTEN)
    shairport 787 pi 4u IPv6 16217 0t0 TCP *:5000 (LISTEN)
    apache2 841 root 3u IPv4 16227 0t0 TCP *:80 (LISTEN)
    nmbd 842 root 16u IPv4 17470 0t0 UDP *:137
    nmbd 842 root 17u IPv4 17471 0t0 UDP *:138
    nmbd 842 root 18u IPv4 17478 0t0 UDP 192.168.10.100:137
    nmbd 842 root 19u IPv4 17479 0t0 UDP 192.168.10.255:137
    nmbd 842 root 20u IPv4 17480 0t0 UDP 192.168.10.100:138
    nmbd 842 root 21u IPv4 17481 0t0 UDP 192.168.10.255:138
    minidlnad 844 minidlna 6u IPv4 17490 0t0 UDP 239.255.255.250:1900
    minidlnad 844 minidlna 8u IPv4 17491 0t0 TCP *:8200 (LISTEN)
    minidlnad 844 minidlna 9u IPv4 17496 0t0 UDP 192.168.10.100:52819
    apache2 846 www-data 3u IPv4 16227 0t0 TCP *:80 (LISTEN)
    apache2 847 www-data 3u IPv4 16227 0t0 TCP *:80 (LISTEN)
    apache2 848 www-data 3u IPv4 16227 0t0 TCP *:80 (LISTEN)
    apache2 849 www-data 3u IPv4 16227 0t0 TCP *:80 (LISTEN)
    apache2 850 www-data 3u IPv4 16227 0t0 TCP *:80 (LISTEN)
    smbd 874 root 33u IPv6 16279 0t0 TCP *:445 (LISTEN)
    smbd 874 root 34u IPv6 16280 0t0 TCP *:139 (LISTEN)
    smbd 874 root 35u IPv4 16281 0t0 TCP *:445 (LISTEN)
    smbd 874 root 36u IPv4 16282 0t0 TCP *:139 (LISTEN)
    apache2 924 www-data 3u IPv4 16227 0t0 TCP *:80 (LISTEN)
    librespot 967 pi 20u IPv4 17706 0t0 TCP *:33493 (LISTEN)
    librespot 967 pi 21u IPv4 17707 0t0 UDP *:5353
    librespot 967 pi 23u IPv4 17720 0t0 TCP 192.168.10.100:37508->104.154.126.254:4070 (ESTABLISHED)
    smbd 1037 root 37u IPv4 18656 0t0 TCP 192.168.10.100:445->192.168.10.102:33696 (ESTABLISHED)
    sshd 4623 root 3u IPv4 26935 0t0 TCP 192.168.10.100:22->192.168.10.50:55606 (ESTABLISHED)
    sshd 4646 pi 3u IPv4 26935 0t0 TCP 192.168.10.100:22->192.168.10.50:55606 (ESTABLISHED)

    root@max2play:/home/pi# tail -f /var/log/squeezeboxserver/server.log
    2021-03-15 12:32:08 Logitech Media Server died. Restarting.
    2021-03-15 12:32:13 Logitech Media Server died. Restarting.
    2021-03-15 12:32:18 Logitech Media Server died. Restarting.
    2021-03-15 12:32:23 Logitech Media Server died. Restarting.
    2021-03-15 12:32:28 Logitech Media Server died. Restarting.
    2021-03-15 12:32:33 Logitech Media Server died. Restarting.

    /usr/sbin/squeezeboxserver –prefsdir /var/lib/squeezeboxserver/prefs –logdir /var/log/squeezeboxserver –cachedir /var/lib/squeezeboxserver/cache –charset=utf8 –d_server –debug server

    ERROR: you didn’t tell me how to implement your appender ’server‘ at /usr/share/squeezeboxserver/CPAN/Log/Log4perl/Config.pm line 347.

    Could someone help me solve this problem?

    Thank you very much in advance

    • This reply was modified 3 years, 8 months ago by Ezaul Zillmer.
    Ezaul Zillmer premium
    2. Oktober 2019 at 14:20 #47222

    Good Morning!
    I would like to share yes! But I still can’t find where does the blog post could give me a link?

    Thanks

    Ezaul Zillmer premium
    2. Oktober 2019 at 0:27 #47215

    Good evening everyone
    I would like to know if we have had any developments in the integration of Max2play with Google Assist?

    If yes what is the procedure I control all my sound environments with max2play and various raspberry through the apartment and I have google assit and would be very top if I could integrate

    Taking advantage I made a project with an old MiniMAC, Raspeberry, MAX2play, HD 1T, CD-ROM, IR, Power Button, LED ON,
    where you could post this on the MAX2Play site

    Ezaul Zillmer premium
    22. Mai 2019 at 14:58 #45474

    Dear all,
    This is about the add-on sound module for the RPi. It is sold as the X6000 by SupTronics OR the ST6000 sold by Audiophonics in France. The boards are identical and even have the same photos of the inputs and outputs especially the 4 x 3.5mm analogue outputs.

    If one shops around, the X6000 can be purchased for AU $64 from dx.com. For the purposes of the discussion, when I refer to the X6000 or ST6000, I shall for simplicity refer to the X6000.

    For your information, the board is sold as an add-on for the RPi. Apart from the mechanical footprint/form, the X6000 does not need the RPi. There is nothing from the RPi’s GPIO that interacts electronically with the X6000.

    Thus you can connect anything to the X6000’s hdmi input. In my situation, I have connected a blu-ray player’s hdmi output to the X6000’s hdmi input. Of course I connected a 5V(dc) 5A supply which is located at the front – either via two pins or a 4.75mm outer-diameter barrel supply or soldering two wires to a 5.5mm outer-diameter socket to the 5.5mm outer-diameter plug from the power supply.

    You may ask: how does it apply to the RPi? My answer is that once you know how the X6000 handles signals, you will know what signals from the RPi’s hdmi output are needed.

    This report is based on my experiments with my blu-ray player. The great bulk of my analysis is found at https://yabb.jriver.com/interact/index. … c=115052.0 under the name „Anthony The Koala“, also at https://www.diyaudio.com/forums/digital … video.html under the name „Anthony The Koala“, 5th November 2018.

    Here is a summary of the facts from my experiments:
    * The X6000’s 3.5mm analogue outputs are decoded LPCM signals. I will return to this.
    * The X6000’s optical SPDIF will pass to a maximum of 5.1 channels .lossy versions of Dolby and DTS.
    * The X6000’s hdmi output will pass all variants of 1/2/5.1/7.1 lossless (1/2/5.1.7.1) variants of Dolby-HD and DTS-MA and LPCM and lossy variants (1/2/5.1) Dolby and DTS variants. To decode these signals you will need an HDMI processor or a/v receiver with hdmi connections that decodes these signals.

    Recall that the X6000’s 3.5mm analogue outputs are decoded LPCM signals. What does this mean?
    * The X6000 does not decode lossless Dolby-HD and DTS-MA signals. NOR does the X6000 decode the lossy versions of Dolby and DTS.
    * the hdmi source signals must be LPCM. If the source signals were bitstreamed lossy or lossless variants of Dolby and DTS signals, YOU WILL HEAR NOISE AND BUZZING on the 3.5mm analogue outputs.

    What is bitstreamed? When the blu-ray player’s hdmi audio output to ‚bitstream‘, your player will send the lossy and lossless versions of Dolby and DTS as well as LPCM. Yes there are some rare occasions where the audio on a blu-ray is LPCM.

    What happens when I set my blu-ray player’s hdmi audio output to ‚LPCM‘, it converts the lossy and lossess Dolby and DTS signals to LPCM. IT IS WHAT IS NEEDED IN ORDER FOR THE X6000 TO DECODE.

    Do all blu-ray players allow conversion of variants of Dolby and DTS signals to multichannel LPCM? NO! Some players such as LG’s BP125, BP240, BP420 and BP450 will downmix all signals to two channel PCM. Other players such as Panasonic’s DMP-BT370 and Laser’s BD3000 have the facility to convert any multi-channel audio signal to multi-channel LPCM.
    Lesson: CHECK YOUR PLAYER’s MANUAL

    Now:
    * we know that to decode the the audio output at the 3.5mm analogue outputs, the X6000’s hdmi input audio signal must be LPCM. Hence the source signal from the blu-ray player, media player and RPi must have its hdmi audio output set to LPCM.
    * we know that the X6000’s hdmi output will pass any signal that is at the hdmi input. That is any lossy and lossless variants of Dolby and DTS even Atmos and X respectively. NOTE: that only occurs if the source signals from a blu-ray player, media player and RPi is bitstreamed. BUT you won’t hear audio at the 3.5mm analogue output.
    * we know that the X6000’s optical/spdif will only pass lossy variants of Dolby and DTS to a maximum of 5.1 channels.

    Now that we know the hdmi’s audio signal input and outputs are for the X6000 will decode ONLY LPCM for the 3.5mm analogue outputs and pass lossy signals through the SPDIF (optical) while the hdmi output will pass lossy and lossless signals.

    How does that apply for one’s RPi? Since the X6000 only decodes LPCM to the 3.5mm analogue outputs, it follows that the RPi’s hdmi output must output its audio signal to the X6000’s hdmi input in LPCM! This is because LPCM is the only kind of audio signal that is decoded by the X6000!

    What does it tell me about the X6000/ST6000?` It tells you that they both come under the same family as other HDMI LPCM audio extractors such as Cypress’s CLUX-11SA and A3080 sold by Altronics. The list is not exhaustive, with a lot of the units looking the same but with different ‚brands‘. They all do the same thing at the analogue 3.5mm outputs – they only decode LPCM.

    But my RPi may handle all the lossy and lossless variants of Dolby and DTS! That may be true especially where there are software packages that decode blu-ray, DVD and other multimedia files Maybe the software does not explicitly inform the user that the lossy and lossless signals are converted to LPCM, the audio signal at the RPi’s hdmi output must be in LPCM otherwise the audio at the X6000/ST6000’s 3.5 analogue outputs will sound noisy and buzzy.

    SUMMARY
    * The X6000/ST6000 is a form of hdmi lpcm audio extractor. Though it has the same mechanical form/footprint as the RPi, any kind of player with an hdmi output can be connected to the X6000/ST6000.
    * The X6000/ST6000 only decodes LPCM at the 3.5mm analogue outputs. Regardless of blu-ray player, media player or RPi with appropriate software, the source hdmi signals must be in LPCM.
    * Once you understand the signal systems of the X6000/ST6000, the performance exceeds those other hdmi lpcm audio extractor. Furthermore if you shop around, the X6000/ST6000 can be lower in price than other hdmi LPCM audio extractors.
    * The X6000/ST6000 will pass at the hdmi output any lossless and lossy signals to a maximum of 7.1 channels or more such as Atmos and X while the SPDIF will only pass lossy signals
    * Of course if you are running the X6000/ST6000, you will still need to connect it to a 5V(dc) 5A supply which can be connected to either two pins or a 4.75mm barrel socket or wiring in a 5.5mm barrel socket.

    I hope that clarifies the issue of using the X6000/ST6000. I am impressed with the sound quality.

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