Home of the Squeezebox™ & Transporter® network music players.
Page 111 of 121 FirstFirst ... 1161101109110111112113 ... LastLast
Results 1,101 to 1,110 of 1210
  1. #1101
    Senior Member
    Join Date
    Apr 2005
    Posts
    143
    8.2.0 had a squeezelite lockup again this morning. I have turned logging back on to confirm that it's the same error. Once that is confirmed, I will binary search through the intervening versions to see which version the problem started with.

  2. #1102
    Junior Member
    Join Date
    Jun 2018
    Posts
    25

    Adding a new album, why doesn't it show up on my squeezebox?

    Hi All.

    I've got a Squeezebox connected to picoreplayer and it's running really nicely. I've also connected my pc to the pi via samba and have pointed MusicBee to it. Again all running well.

    I'm trying to add new albums to this setup and the simplest route seems to be just opening an explored on my pc, going to the music folder on the pc and just copying the new album there. Then I go to MusicBee and do a scan for new music. agani this works great. However, how do I get the new album to show up when I connect via my squeezebox? The new album simply refuses to show up there? Is there a scan function on the squeezebox itself I have to run? If so I can't find anyway to do that?

    Does anyone know what I should do? Any help much appreciated.

  3. #1103
    Senior Member
    Join Date
    Apr 2005
    Location
    UK/London
    Posts
    6,274
    In LMS web interface you can tell it to scan.
    Settings/Basic Settings/Rescan
    Paul Webster
    Author of "Now Playing" plugins covering Radio France (FIP etc), PlanetRadio (Bauer - Kiss, Absolute, Scala, JazzFM etc), KCRW, ABC Australia and CBC/Radio-Canada
    and, via the extra "Radio Now Playing" plugin lots more - see https://forums.slimdevices.com/showt...Playing-plugin

  4. #1104
    Senior Member
    Join Date
    Apr 2005
    Posts
    143
    Quote Originally Posted by John Stimson View Post
    8.2.0 had a squeezelite lockup again this morning. I have turned logging back on to confirm that it's the same error. Once that is confirmed, I will binary search through the intervening versions to see which version the problem started with.
    Here's what the log looked like this morning when I found it unable to play:
    Code:
    [15:36:39.499800] sendRESP:226 RESP
    [15:36:39.589421] write_cb:145 setting track_start
    [15:36:39.589596] resample_newstream:189 resampling from 44100 -> 88200
    [15:36:39.589662] resample_newstream:214 resampling with soxr_quality_spec_t[precision: 28.0, passband_end: 0.911328, stopband_begin: 1.000000, phase_response: 50.0, flags: 0x80000000], soxr_io_spec_t[scale: 0.89]
    [15:36:39.590423] process_newstream:124 processing: active
    [15:36:39.590520] process_newstream:145 creating process buf in frames: 25600
    [15:36:39.591154] process_newstream:152 creating process buf out frames: 51200
    [15:36:39.612368] _output_frames:65 start buffer frames: 28804
    [15:36:39.612540] _output_frames:153 track start sample rate: 88200 replay_gain: 0
    [15:36:39.614061] sendSTAT:195 STAT: STMs
    [15:36:39.614334] sendSTAT:195 STAT: STMt
    [15:36:39.622719] output_thread:685 open output device: front:CARD=AUDIO,DEV=0
    [15:36:39.625128] alsa_open:354 opening device at: 88200
    [15:36:39.628143] alsa_open:425 opened device front:CARD=AUDIO,DEV=0 using format: S24_3LE sample rate: 88200 mmap: 1
    [15:36:39.628331] alsa_open:516 buffer: 80 period: 4 -> buffer size: 7056 period size: 1764
    [15:36:40.615284] sendSTAT:195 STAT: STMt
    [15:36:41.616611] sendSTAT:195 STAT: STMt
    [15:36:41.993550] process:528 strm
    [15:36:41.993660] process_strm:280 strm command t
    [15:36:41.993695] sendSTAT:195 STAT: STMt
    [15:36:42.994890] sendSTAT:195 STAT: STMt
    [15:36:43.996284] sendSTAT:195 STAT: STMt
    [15:36:44.997624] sendSTAT:195 STAT: STMt
    [15:36:45.993544] process:528 strm
    [15:36:45.993655] process_strm:280 strm command t
    [15:36:45.993692] sendSTAT:195 STAT: STMt
    [15:36:46.994896] sendSTAT:195 STAT: STMt
    [15:36:47.996308] sendSTAT:195 STAT: STMt
    [15:36:48.997598] sendSTAT:195 STAT: STMt
    [15:36:49.994291] process:528 strm
    [15:36:49.994403] process_strm:280 strm command t
    [15:36:49.994438] sendSTAT:195 STAT: STMt
    [15:36:50.995234] sendSTAT:195 STAT: STMt
    [15:36:51.999476] sendSTAT:195 STAT: STMt
    [15:36:53.000818] sendSTAT:195 STAT: STMt
    However, when I restarted squeezelite, the same messages display while playing. There isn't anything suspicious in dmesg. There's only 1 line after the one that says "Finished PiCorePlayer startup".

    I am confused by the timestamps in the squeezelite log file, though. After the freezeup, the new entries being added to the bottom did not seem to correspond to the current time. Or the whole log wasn't being displayed.

    Could the capacity of the boot SD card be a problem? I am using a 1GB SD card for my pCP image.

    Where are the log files stored? What happens when the device they are on gets full?

  5. #1105
    Senior Member
    Join Date
    Apr 2005
    Posts
    143
    Okay, squeezelite froze again and this time I was able to load more of the squeezelite log file. The critical change appears to be:
    Code:
    [14:54:45.966312] process:528 strm
    [14:54:45.966412] process_strm:280 strm command t
    [14:54:45.966457] sendSTAT:195 STAT: STMt
    [14:54:46.434711] output_thread:772 pcm wait timeout
    [14:54:46.434856] ALSA snd_pcm_hw_start:688 SNDRV_PCM_IOCTL_START failed (-77)
    [14:54:46.434919] output_thread:762 start error: File descriptor in bad state
    [14:54:46.445067] ALSA snd_pcm_hw_start:688 SNDRV_PCM_IOCTL_START failed (-77)
    [14:54:46.445116] output_thread:762 start error: File descriptor in bad state
    [14:54:46.455293] ALSA snd_pcm_hw_start:688 SNDRV_PCM_IOCTL_START failed (-77)
    [14:54:46.455343] output_thread:762 start error: File descriptor in bad state
    [14:54:46.465467] ALSA snd_pcm_hw_start:688 SNDRV_PCM_IOCTL_START failed (-77)
    [14:54:46.465515] output_thread:762 start error: File descriptor in bad state
    [14:54:46.475628] ALSA snd_pcm_hw_start:688 SNDRV_PCM_IOCTL_START failed (-77)
    [14:54:46.475715] output_thread:762 start error: File descriptor in bad state
    Repeating that last pair of messages about every hundredth of a second I guess until the log ran out of space. I'm going to roll back to 8.0.0 and see how that goes.

  6. #1106
    Senior Member paul-'s Avatar
    Join Date
    Jan 2013
    Posts
    4,959
    John, usb sound cards disconnecting and then reconnecting require some special udev rules to work. The first question is does your soundcard go to sleep and shutdown? Can you turn off any power savings feature and see if you still see disconnects?
    piCorePlayer a small player for the Raspberry Pi in RAM.
    Homepage: https://www.picoreplayer.org

    Please donate if you like the piCorePlayer

  7. #1107
    Senior Member
    Join Date
    Apr 2005
    Posts
    143
    Quote Originally Posted by paul- View Post
    John, usb sound cards disconnecting and then reconnecting require some special udev rules to work. The first question is does your soundcard go to sleep and shutdown? Can you turn off any power savings feature and see if you still see disconnects?
    It is a dongle style USB to SPDIF converter that's powered by the USB input cable. If it is plugged into a live USB port, it's on. It doesn't sleep or shut down. It has not had this problem during years of use with pCP 7.0.0 and 6.0.0.

    This is the USB output device I am using: https://www.aliexpress.com/item/2251800354199830.html

    Output setting: hw:CARD=AUDIO,DEV=0 (front:CARD=AUDIO,DEV=0 also works, and leaving it blank also works -- the onboard audio is disabled from the ALSA mixer page, so the USB-SPDIF dongle is the only available device)
    ALSA setting: buffer=80, period=4, MMAP=1
    Maximum sample rate: 88200,96000
    Upsample setting: vLE

  8. #1108
    Junior Member
    Join Date
    Jun 2018
    Posts
    25
    Quote Originally Posted by Paul Webster View Post
    In LMS web interface you can tell it to scan.
    Settings/Basic Settings/Rescan
    Of course! Thanks so much!

    Another quick question. I've been getting quite a few rebuffering and disconnects from my pi recently. Does anyone know what might be causing this? I'm using a zero2 so would have thought it would be reasonably stable and zippy. Would a regular pi4 connected via ethernet improve these dropouts?

  9. #1109
    Senior Member
    Join Date
    Apr 2005
    Location
    UK/London
    Posts
    6,274
    If your LMS is running on a machine that only has WiFi then maybe try with a USB to Ethernet adapter (check that pCP supports it) or move your LMS to a system with Ethernet already working.
    Paul Webster
    Author of "Now Playing" plugins covering Radio France (FIP etc), PlanetRadio (Bauer - Kiss, Absolute, Scala, JazzFM etc), KCRW, ABC Australia and CBC/Radio-Canada
    and, via the extra "Radio Now Playing" plugin lots more - see https://forums.slimdevices.com/showt...Playing-plugin

  10. #1110
    Senior Member
    Join Date
    Oct 2009
    Location
    Western/Northern New York
    Posts
    1,369
    Quote Originally Posted by Paul Webster View Post
    If your LMS is running on a machine that only has WiFi then maybe try with a USB to Ethernet adapter (check that pCP supports it) or move your LMS to a system with Ethernet already working.
    @Gizmo99 - I think you only have two posts on this thread, right? Rebuffering issues are all over this forum, but a good place to start is to describe your system - where does LMS reside, what are the players, how are they connected, etc.

    In my experience, first place to look at rebuffering is your wifi (if used) connection. Try ethernet (understand the zero does not support) per Paul's suggestion, or, just try moving the pi zero closer to the router (even just as a test).

    Not sure of your player, but in (a touch or radio) settings->advanced->player info there is a "wireless signal strength". Not a great indicator, but in general you want 75% or more (my guidelines). I had a receiver that rebuffered at 60ish.

    I doubt you need more "horsepower" (pi4, if you can find them) but it can't hurt. You should be able to run LMS or a player on a zero. Others have

    Jim

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
  •