jademonkee

Forum Replies Created

Viewing 11 posts - 1 through 11 (of 11 total)
  • 2. Dezember 2015 at 18:35 #17105

    Thanks for the info.
    I opted for the JiveLite version, as I thought it would save the time it takes to compile it. But as you now offer a pre-compiled version, the choice now seems arbitrary.

    12. November 2015 at 22:45 #16892

    Thanks for adding that option – that will work well as a workaround, thanks.

    6. November 2015 at 19:30 #16799

    If it helps any, I’ve found this info on turning on/off the screen:
    https://www.raspberrypi.org/forums/viewtopic.php?f=108&t=120968&start=50

    to turn off:
    echo 1 > /sys/class/backlight/rpi_backlight/bl_power

    To turn on:
    echo 0 > /sys/class/backlight/rpi_backlight/bl_power

    Could it perhaps be possible to have the screen turn off when the Squeezelite player is turned off (as in, when the ‚power‘ button in the top left of the screen is pressed)?

    3. November 2015 at 13:23 #16711

    So, it turns out I can’t reach github from my Raspberry Pi – pings fail.
    Digging a little deeper, someone mentioned that it could very well be related to my netmask setting (as per https://www.raspberrypi.org/forums/viewtopic.php?f=91&t=48866). Indeed, as github is a 192.x.x.x address, if my netmask was 255.0.0.0, then it would assume that github was on my local network.
    Indeed, taking a look at the WIFI/LAN settings page I see that my netmask is 255.0.0.0
    I had the option to „Set fixed LAN IP-Address (eth0)“ enabled, and disabling this option set the net mask back to the correct 255.255.255.0
    I can now reach github. Hooray!

    2. November 2015 at 23:36 #16685

    I also cannot install Jivelite on a fresh install (updated to the latest version).
    However, I’m having a different issue: after pressing the install button, it loads and runs through the entire install process, even saying that it has completed the install succesfully. Howevr, if I reload the page, it says that Jivelite is not installed. I’ve tried installing it again – same process.
    However, I have noticed that during the install, it throws up an error:

    Cloning into 'jivelite'...
    error: Failed connect to github.com:443; No route to host while accessing https://github.com/ralph-irving/jivelite.git/info/refs
    fatal: HTTP request failed
    /opt/jivelite/jivelite/src/resize.c: No such file or directory

    So, I decided to check if that link was correct, and it took me to a page with the error:

    Please upgrade your git client.
    GitHub.com no longer supports git over dumb-http: https://github.com/blog/809-git-dumb-http-transport-to-be-turned-off-in-90-days

    Is there any way I can fix this? Or do I have to wait for a new release?
    Many thanks.

    EDIT: Ah, given the age of the URL the error page links to, I realise that the error page only appeared because I was accessing the link shown in the Jivelite install log using a web browser (of course).
    Any other thoughts? Given I’ve installed it four times now, and I can access github using my browser, I doubt it’s due to my (admittedly unreliable) internet connection.

    • This reply was modified 8 years, 5 months ago by jademonkee.
    16. September 2015 at 20:09 #15718

    That fixed it. Many thanks.

    One final question:
    Do you know if there’s any way to set jivelite’s screensaver to have my monitor go to standby, rather than just a blank screen?

    16. September 2015 at 18:11 #15712

    Ok. Doing so now.

    16. September 2015 at 18:03 #15711

    Excellent to hear. Thank you.
    I should also note that, since writing my second post, I decided that setting PCM to 86% as per the IQaudIO instructions resulted in a better volume than 100% PCM.

    15. September 2015 at 20:32 #15697

    Ok, following the steps in section 12 of the IQaudIO manual (http://www.iqaudio.com/downloads/IQaudIO.pdf) I found that on page 26 it recommends using alsamixer to set „PCM“ to 86% (for approx 0dB output; 100% would be +6dB), and to set „Playback“ to 100 and „Playback Boost“ to 100 too.
    I did all these, and the sound is closer to what I would expect for a suitable output.
    I still expect it to be a little louder, however, so I set the PCM to 100% and it seems about right now.

    And are you able to set these values as default for the DAC+ for future max2play installations?

    Out of curiosity, I was hoping to add a hardware volume control to the DAC+ – would it then be adjusting the PCM value in ALSA, rather than the Squeezelite volume?
    Is it possible to set SqueezeLite to use the PCM ALSA mixer for volume control from a SqueezeBox remote app?

    15. September 2015 at 19:21 #15695

    FWIW: I looked into my LMS settings (I’m running my copy of LMS from a Cubietruck mini computer), I found that album resizing (Advanced > Performance) was set to be done by mysqueezebox.com, so set it to be done by LMS itself.
    I can also see that jiveliteskin has an entry for 250×250 album art (which seems quite small, in truth) under the „Custom pre-caching specifications“ section.
    To be sure, I did a full clear and re-scan of the library with pre-caching album art enabled.

    Sadly, none of this fixed my problem.

    15. September 2015 at 17:34 #15688

    Thanks – I’l see what I can do.

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