Squeezebox Transporter: Delayed Start and Frequent Stops (ref#LUEA2R)

Support
1

What best describes your playback issue?

· Music doesn't start when I press "Play"

What type of Zone is affected by this problem?

· *Network Zones* are affected.

Is the affected network Zone connected with Ethernet or WiFi?

· WiFi

Does the issue affect all file formats?

· The issue affects *multiple/all* file formats.

Does the issue happen with local library music, streaming service music, or both?

· *Both streaming and local* *library* music are affected.

Do you encounter any playback errors with the "System Output" Zone?

· The System Output has *no problem*, it's only my other Zone.

How is the affected Zone connected to your RoonServer machine?

· Network - WiFi

Which network audio protocol is the Zone using with Roon?

· Squeezebox

Does the device show up at all in Roon Settings -> Audio?

· Yes, it shows up there, but it isn't Enabled

Does the "Enable" button unlock the Zone?

· I pressed Enable, but the Zone remains disabled

Does the device play audio from another source when using the same connection?

· The device has no problems with another audio source

Have you checked that Roon is whitelisted in any firewalls?

· I've checked the firewall and the issue remains

If the device has multiple output options, do the other options work as expected?

· Multiple output types are affected

Is the device using the latest firmware as per the manufacturer?

· Firmware is up-to-date but the issue remains

Do you have an approximate timestamp of when the issue last occurred?

· As previous said: 13:30 local time, local stored track "Differently" from Marian Hill

What are the make and model of the affected audio device(s) and the connection type?

· Squeezebox Transporter

Describe the issue

Hello

I'm back with the same issue that appeared on previous ticket "Squeezebox Transporter experiences delayed start and frequent stops with connectivity issues (ref#PV4R66)" that I closed as magically solved.

But not, I am afraid.

More details: for avoiding any kind of IP conflicts I made a reservation on the router table by MAC so always same internal IP assigned.

Transporter screen is blinking as not finding the server. Sometimes error message, sometimes clock as screensaver.

After some blinkings, when it appears as "connected" you can see it as available player but no music play on it. Or (only few times) can start the track and stops after 1 second or so.

The track time on Roon screen does not advance.

Failure happend now, 13:30 when playing local file from "Marian Hill" musician, track "Differently".

At your disposal if further information is needed.

Describe your network setup

NAS with music and Roon installed, cable connected to router. Squeezebox Transporter connected by WiFi (from router to Transporter like 20 cm distance)

2

Screenshot_20251026-135734_Roon
Screenshot_20251026-135734_Roon1080×2220 162 KB

After opening the ticket, Squeezebox has been disconnected from power but I still see it, choose it and try to play.

3

are you using Bixby to control roon, or the Transporter?

is there an LMS instance running somewhere on your network?

4

Hello

Bixby appears on the screenshot by mistake. Me, touching everything on the screen for making the capture:)

It is not even configured

I do not use LMS, but I use other Squeezebox’s players with no issues. Today I did before trying to use the Transporter

1 Like
5

are any of the other squeezeboxen a SB Touch? if so, and you may have already done so, check and make sure the built in server on the Touch is not running.

6

Is a Touch :slight_smile:

Server is Off, as I am using Roon for everything.

1 Like
7

good luck, i hope @support has a solution.

8

Hello @Jose_Alconchel,

Thank you for reaching out and for the detailed description.

Based on the information provided, I’d like to point out a few things that might be contributing to the issue:

  1. System resources – Your Roon Server runs on a NAS with 2 GB of RAM. Unfortunately, this setup doesn’t meet the minimum requirements for Roon, and performance or connectivity issues (especially with network zones) are expected in such cases.
  2. Network connection – Since the Squeezebox Transporter is only about 20 cm from the router, please try connecting it via Ethernet instead of WiFi. WiFi connections can sometimes appear stable but still introduce brief dropouts or discovery issues with older Squeezebox devices.
  3. Next steps – To get a stable experience, we strongly recommend running Roon Server on a more capable device (for example, a modern PC, NUC, or NAS with at least 4–8 GB RAM) and using wired connections for both the core and network players.

Once you’ve tested this setup, let us know how it behaves — we’ll be happy to assist further from there.

9

I have the same hope

10

I can add more RAM to the NAS

It will improve the performance?

11

Hi @Jose_Alconchel,

Considering your library size, I do think increasing the RAM to at least 4GB would definitely help! :+1:

12

I expect new RAM to arrive this Wednesday so there will be 2Gb + 8Gb on the free slot available.

New tests to perform on Thursday.

13

And also I will change to RJ45 connectivity

What a pity. I was trying to avoid cables as much as possible.

The rear part of my living room furniture is a chaotic mess of plugged thinks and connected stuff.

1000024906
10000249061920×1440 138 KB

Lucky me, front part is hidding the cables (almost).

14

Hello @Jose_Alconchel,

Thank you for the update — it’s great to hear you’re planning to add more RAM and switch to a wired connection. Both changes should noticeably improve stability and playback performance.

Please also note that your NAS uses an Intel Celeron J3355 processor, which is below our officially supported specifications for running Roon Server. This CPU can struggle with database management and real-time audio streaming, especially when handling network zones or high-quality music, or DSP settings

image
image1905×942 57.9 KB

While your planned upgrades will certainly help, if playback issues persist even after these improvements, we recommend considering running Roon Server on a more powerful dedicated device (for example, an Intel NUC or desktop computer) for the best experience.

Let us know how things behave after you’ve installed the RAM and moved to Ethernet — we’ll be happy to review the results with you.

15

Screenshot_20251029-235637_DS finder~2
Screenshot_20251029-235637_DS finder~21080×845 58.2 KB

RAM has grown

I was using a NUC before moving to the NAS, and the NUC I got was not enough, neither, according to your explanations.

I am sorry but sometimes seems users has to be one step ahead from Bill Gates to have enough stuff at home for using Roon.

BTW sorry if I did not explain good enough. NAS has been always connected directly to Router by cable, never by Wi-fi.

Issues described twice are with NAS straight to router, no WiFi neither any switch.

16

Can you explain about my library size? :slight_smile:

Sounds like I have the Library Of Congress on my NAS.

I am under 20k tracks and I have seen here collections on 70k tracks which are working better than my thiny one.

17

Hi @Jose_Alconchel,

What specifically would you like to know about your library size?
@vadim was referring to your server’s processor - it doesn’t meet all the necessary requirements to run Roon Server properly. This issue isn’t related to your library size, but rather to the hardware needed for Roon Server to function correctly.

Thank you!

18

Crystal clear, then.

I did not understood the library size message as something directly related to my slow/poor equipment.

I understood it as “due to this size you would experience some issues” and my answer was related to this as I have seen (well, I have read :slight_smile:) people with 70k tracks.

19

Squeezebox Transporter is working connected by RJ45, no issues.

I cannot compare about Roon performance under Synology 218+ but there is more RAM available for processing.

I understand you can close this ticket

1 Like
20

Hello @Jose_Alconchel ,

Glad to hear that there are no further issues. We’ll go ahead and mark your thread for closure as requested, happy listening!