Home of the Squeezebox™ & Transporter® network music players.
Page 130 of 132 FirstFirst ... 3080120128129130131132 LastLast
Results 1,291 to 1,300 of 1320
  1. #1291
    Senior Member
    Join Date
    Apr 2008
    Posts
    1,442
    I think this is the same as the already available "Blue Glow" VU in Jivelite setup. Looks like a McIntish power amp


    Quote Originally Posted by slartibartfast View Post
    Sent from my Pixel 3a using Tapatalk

  2. #1292
    Senior Member
    Join Date
    Apr 2008
    Posts
    1,442

    Timing of screen saver in Jivelite

    I have my screensaver set for 10 seconds. The player boots and goes to the menu and then it takes about 45 seconds to go to the screen saver. After that instance it does switch after 10 seconds.

    Is there a way to get the screen saver to come right up after booting rather than the menu?

    Thanks,

    Howard

  3. #1293
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    600
    Hi

    I'm trying out the clock display freezing issue workaround of a cron job to restart it nightly.

    0 2 * * * /usr/bin/pkill -15 jivelite

    However after doing this, I find the display says this in the morning. Playback is fine though. How do I get the display back (other than a reboot?)


    Name:  2021-02-10 08.09.49 (Medium).jpg
Views: 111
Size:  223.6 KB

  4. #1294
    Senior Member
    Join Date
    Apr 2005
    Location
    UK/London
    Posts
    3,643
    Jivelite is the UI not the player (SqueezePlay is the combined player and UI).

    So you appear to have killed the UI but not restarted it.

    Playing works because you have not killed the player.
    Paul Webster
    http://dabdig.blogspot.com
    Author of "Now Playing" plugins covering Radio France (FIP etc), KCRW, Supla Finland, ABC Australia, CBC/Radio-Canada and RTE Ireland

  5. #1295
    You probably have not just killed the jivelite process but also the shell script that controls its startup and spossible restarts.

    Code:
    ~$ ps -eaf | grep jivelite
    root      5852     1  0 Feb09 ?        00:00:00 /bin/sh /opt/jivelite/bin/jivelite.sh
    root      7751  5852  1 Feb09 ?        00:35:03 /opt/jivelite/bin/jivelite
    You could try to kill only the process '/opt/jivelite/bin/jivelite':
    Code:
    0 2 1,16 * * /usr/bin/pkill -x /opt/jivelite/bin/jivelite
    Last edited by jd68; 2021-02-10 at 10:34. Reason: kill it only twice per month

  6. #1296
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    600
    Tx, yes I know jivelite is the UI, I was just saying that the player works as an indication that nothing else was wrong.

    Also I was just going on the advice from below which says that the cmd should restart jivelite.
    https://forums.slimdevices.com/showt...l=1#post908070

  7. #1297
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    600
    @jd68

    Tx - will give it a go.

  8. #1298
    Senior Member mr-b's Avatar
    Join Date
    Feb 2007
    Location
    UK
    Posts
    600
    Quote Originally Posted by jd68 View Post
    You probably have not just killed the jivelite process but also the shell script that controls its startup and spossible restarts.

    Code:
    ~$ ps -eaf | grep jivelite
    root      5852     1  0 Feb09 ?        00:00:00 /bin/sh /opt/jivelite/bin/jivelite.sh
    root      7751  5852  1 Feb09 ?        00:35:03 /opt/jivelite/bin/jivelite
    You could try to kill only the process '/opt/jivelite/bin/jivelite':
    Code:
    0 2 1,16 * * /usr/bin/pkill -x /opt/jivelite/bin/jivelite
    That seems to have done the trick and the display is fine this morning. :-)
    As a matter of interest, why only restart it twice a month?

  9. #1299
    Senior Member
    Join Date
    Apr 2005
    Location
    UK/London
    Posts
    3,643
    Quote Originally Posted by mr-b View Post
    As a matter of interest, why only restart it twice a month?
    Is it to guard against a 20-something days issue where there is some sort of problem handling a date offset overflow?
    Paul Webster
    http://dabdig.blogspot.com
    Author of "Now Playing" plugins covering Radio France (FIP etc), KCRW, Supla Finland, ABC Australia, CBC/Radio-Canada and RTE Ireland

  10. #1300
    Senior Member Jeff07971's Avatar
    Join Date
    Aug 2011
    Location
    London, England
    Posts
    1,591
    Quote Originally Posted by Paul Webster View Post
    Is it to guard against a 20-something days issue where there is some sort of problem handling a date offset overflow?
    I just use the "reboot" cron job every 7 days at ridiculous o'clock.

    Havent had the clock display freeze for many months now

    Jeff

    Want a webapp ? Get SqueezeLite-X ! https://forums.slimdevices.com/showt...l=1#post903953

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •