sf_max2play

Forum Replies Created

Viewing 10 posts - 1 through 10 (of 10 total)
  • 21. Mai 2018 at 21:36 #35795

    Hi Heiner,

    Thanks for letting me know. I just installed the new image, along with the RPiDisplay and JiveLite plugins, and it all appears to be working correctly. Appreciate you taking care of it.

    25. April 2018 at 22:27 #35335

    Hi Heiner,

    I was able to do some experimenting with the Raspbian config.txt file and I can confirm that by changing the resolution manually in the config file, the QVGATOUCH_Skin now fits correctly. The Raspberry display was previously set to 640×480, which was why the skin was too big. I set it to 320×240 to make it fit.

    I’m curious, do you know how I would go about finding or creating a 640×480 skin for Joggler?

    25. April 2018 at 21:56 #35334

    Hi,

    Hope you enjoyed your holiday!

    It’s true that the instructable is for a different display, but the only thing I should need to do differently is select the Adafruit 2.8″ version in the RPi Display installer, correct? My understanding was that all the other steps are the same.

    25. April 2018 at 21:53 #35333

    Hi,

    Yes, I can select any of the skins, and they all adjust the overall image of Jivelite in different ways. Here are what some of them look like:

    QVGATOUCH_SKIN – The top left quarter of the screen is all that is used. The rest is blank. So it’s about a fourth of the size of the display.
    QVGA Landscape Skin – Same as above, just the top left quarter is used.
    Joggler Skin – Image is too big. Part of the right and bottom of the display is cut off.
    HD Skin (640×480) – Similar to Joggler Skin, but even more is cut off on the right and bottom of the display.

    Thanks for getting back to me.

    19. April 2018 at 6:17 #35226

    I never had any success getting the RPi Display plugin to work correctly. I did, however, get the display to work using Adafruit’s guide (https://cdn-learn.adafruit.com/downloads/pdf/adafruit-pitft-28-inch-resistive-touchscreen-display-raspberry-pi.pdf).

    I’m having an issue with Jivelite, but I will start a new thread for that.

    31. Januar 2018 at 19:53 #33778

    Hi,

    I have been able to recreate it on the Jessie build, too, so it must be related to a change on my NAS. Disregard. I will take that issue to the correct post.

    I will try this new Stretch Beta this week.

    Thanks for the update.

    30. Januar 2018 at 6:30 #33744

    Hi,

    This beta has worked really well as a Bluetooth player connected to the Squeezebox server on my NAS.

    However, I installed Squeezebox server on the Pi, then added a mountpoint to my NAS’s music folder. Once I reboot, the Pi goes offline and I can no longer access it via the network, even if I pull the plug and reconnect it. This is over LAN. I’ve replicated the issue twice. I thought maybe it was just scanning the library for a long time, but even after a day of running it was inaccessible.

    12. Januar 2018 at 0:11 #33365

    I am using the built-in RP3 bluetooth. Today I let it run, and sometime around 3 hours in it seemed to stop working, at which point I needed to restart the speaker and the Pi to get it to go again.

    I’ve noticed that the synchronize function doesn’t work so well in the latest update, though. I have a Logitech Boom and the Max2Play Pi both connected to LMS running on a NAS. If I tell the Pi to sync to the Boom, the Boom will play, but the Pi will stop and everything will need to be reset. If I tell the Boom to sync to the Pi, it works fine, though there is a minor audio delay between the two, which I may be able to adjust for in the LMS settings. I also had an issue today where, during synchronized playback, I could stream a podcast fine, but if I played a track from my NAS, or via Spotty, music would play for a short period, before abruptly stopping, then starting over from the beginning.

    Not sure if the sync issue is related to Bluetooth or not. I’m happy to start a thread elsewhere if that’s preferable.

    9. Januar 2018 at 0:23 #33313

    Hi,

    I’m having much better Bluetooth streaming performance now than I had before. I updated the Pi 3 to latest everything and am running Max2Play 2.45. I also reset all the settings and am running it just as an audio player (no multisqueeze, or server). Those functions may work, but I don’t need them at the moment, so I’m not loading them.

    I played audio to a Bluetooth speaker for two hours straight today, with no issues. It also reconnects automatically to my Bluetooth speaker when I turn it on.

    So far, so good. I’ll post if there are anymore quirks. Thanks for continuing to improve the product.

    26. Oktober 2017 at 5:32 #32116

    Hi Heiner,

    That’s too bad, but I appreciate your honesty! I bought Max2Play for this function specifically, so I’m hoping it will be fixed in the next round.

    Thanks for the response.

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