Hi,
trying to find out why FLAC songs don't play smoothly on my SlimServer+SB. Looked into the preferences file and found the following setting:
maxbitrate: 320
Can I increase this?
Mats
Results 1 to 10 of 15
Thread: Maxbitrate?
-
2007-11-29, 06:27 #1Member
- Join Date
- May 2007
- Posts
- 50
Maxbitrate?
-
2007-11-29, 06:36 #2Senior Member
- Join Date
- Oct 2005
- Posts
- 7,099
What do you mean by "don't play smoothly", are you getting dropouts?
In which case, increasing the bitrate will make it worse, you don't have enough wireless bandwidth. See http://wiki.slimdevices.com/index.cg...emsSecondGuide
Not only that - I'm not sure where you're seeing that setting or what it's doing. It seems to be a bitrate limiting setting - this will transcode the FLAC to MP3 at the given bitrate. In Player Settings - Audio, you have to activate bitrate limiting, have LAME installed and have FLAC -> MP3 checked in Server Settings - File Types in order for this to work. If it's not activated, activate it, and if it still stutters, turn the bitrate down. You can't turn it up from 320, that's the maximum a standard MP3 encoder allows.
But all this is turning lossless files lossy, so it's best to try to address bandwidth concerns first.
-
2007-11-29, 06:57 #3Member
- Join Date
- May 2007
- Posts
- 50
Hi,
thanks for your reply.
The problem I have is that when I select a song which is in FLAC format (MP3's are not affected) it starts to play, but then there are intermittent dropouts during the first half minute or so. After a while the song plays alright. Any subsequent songs played w/o user interaction play alright.
I have run the SlimServer's network performance test with perfect results up to 4000kpbs, so I doubt this has anything to do with the capacity of the network link.
I also run the SlimServer's server performance monitor, which reported that the player buffer is never filled to any higher degree.
Apparently there's a bottleneck somewhere, the player not being fed with music at a rate that saturates the SB while playing, at least immediately after being instructed to play new songs.
Any idea?
Mats
PS. I am running slimserver on an NSLU2.
-
2007-11-29, 07:03 #4Senior Member
- Join Date
- Oct 2005
- Posts
- 7,099
-
2007-11-29, 07:11 #5Robin BowesGuest
Maxbitrate?
matek994 wrote:
> Hi,
>
> thanks for your reply.
>
> The problem I have is that when I select a song which is in FLAC format
> (MP3's are not affected) it starts to play, but then there are
> intermittent dropouts during the first half minute or so. After a while
> the song plays alright. Any subsequent songs played w/o user interaction
> play alright.
>
> I have run the SlimServer's network performance test with perfect
> results up to 4000kpbs, so I doubt this has anything to do with the
> capacity of the network link.
>
> I also run the SlimServer's server performance monitor, which reported
> that the player buffer is never filled to any higher degree.
>
> Apparently there's a bottleneck somewhere, the player not being fed
> with music at a rate that saturates the SB while playing, at least
> immediately after being instructed to play new songs.
>
> Any idea?
>
> Mats
>
> PS. I am running slimserver on an NSLU2.
I'm almost certain this is a CPU limitation of the NSLU2.
When bandwidth limiting is enabled, slimserver transcodes the flac files
to mp3 (using lame) to reduce the network bandwidth used by file
streaming. The NSLU2 won't have enough CPU power to do this.
mp3 files are not affected because they are streamed direct to your SB.
The fix? Turn off bandwidth limiting so flac files are streamed natively
to the SB.
R.
-
2007-11-29, 09:33 #6Member
- Join Date
- May 2007
- Posts
- 50
My SlimServer version is: 6.5.2 - 12047 - Debian - EN - iso8859-1
Regarding the "maxbitrate" setting, I guess it is perhaps not relevant in this case. The Server Settings reveal that FLAC files are streamed as FLAC. The Player Settings show Bitrate Limiting = No Limit. Sorry for misleading you.
I uploaded the performance log to a temporary web area instead of pasting it here as it became quite large. If you find some hot areas in there, I'll include those in a following post.
http://members.chello.at/matsoek/temp/log.txt
FYI, a few hours ago I posted another question in another area of this forum, http://forums.slimdevices.com/showthread.php?t=40671. It describes my setup a bit more in detail if needed.
-
2007-12-01, 17:24 #7Junior Member
- Join Date
- Jul 2007
- Posts
- 19
I have the same problem playing high bit rate FLAC 24bit/96Khz file I bought. The sound would have couple dropouts in the 1st min and everything plays fine; granted if I start the song over again I don't get the same problem. Annoying.
Transporter - Firmware 33
SqueezeCenter 7.01a
-
2007-12-01, 18:03 #8Senior Member
- Join Date
- Oct 2005
- Location
- Ireland
- Posts
- 11,259
matek994,
How did you create the Flac files - there was another post about dropouts on native Flac playback and it seems that the encoder may be the problem.
-
2007-12-01, 18:56 #9Junior Member
- Join Date
- Jul 2007
- Posts
- 19
The flac are bought from linnrecords @ 24bit/96Khz master quality;
If I let the flac file play for say 20 sec and start the file over, I don't get the sound drop out.
If I put all the flac in a playlist and just let one song play after another, no drop out.
The network performance tests to 3000kps @99% (I am thinking my problem is network related as the files are 2900kps)
My squeezecenter version is SqueezeCenter Version: 7.0 - 14627Last edited by chesebert; 2007-12-01 at 20:01.
-
2007-12-02, 02:26 #10Senior Member
- Join Date
- Oct 2005
- Location
- Ireland
- Posts
- 11,259
chesebert,
This could be a Transporter buffering problem which is exacerbated by the additional small delays inherent when using wifi.
The fact that you can get continuous subsequent audio - means that although your wifi may be marginal - it is OK.
When a track is being played - the Transporter buffer is initially filled up and then when full "play" is initiated. It looks like the Transporter waits just a little bit too long (when using marginal wifi) before asking for the first top up of the buffer. This might because you are using Flac 24bit/96KHz files which require high datarates.
I think you should log this as a bug.

Reply With Quote

