Triode.
I made it also work on the Touch. I do think squeezelite performs
extremely well on the Touch. For sure better then squeezslave.
Though I really had to reshuffle my setup. I couldn't make much use of
my Toolbox settings.
I ran into xruns and other weired behaviour at every corner. So,
Hello all,
I just followed the same instructions and got the same errors as the
previous two posts.
Not really sure where to go from here.
I may have to go the Ubuntu/CentOS route.
Any help would be appreciated.
Amir
lo
Hi,
I am able to download (in the nightly builds section) SqueezePlay for
Windows and Mac, but not for Linux.
Does anyone know where it can be found to download?
Thanks.
Leica's Profile: http://forums.slimdevices.com/mem
I use FreeNAS and Squeezebox will also be happy to test it.
sonaris's Profile: http://forums.slimdevices.com/member.php?userid=58903
View this thread: http://forums.slimdevices.com/showthread.php?t=94320
__
albertone74 wrote:
> Hi,
> After several re-installations (Squeezelite, Ubuntu,ect,.) now I can
> finally listen to my 24 bits FLAC. :)
> The trick was to start with the command: squeezelite -b 256:256
> Would it be possible to let squeezelite know to start with that option
> automatically?
> Th
vortecjr wrote:
> You add your start up command (include the path) in /etc/rc.local and it
> will automatically run it on boot.
>
> Jesus R
HI,
I am just editing the file you suggested. Should I add the line
"squeezelite -b 256:256" soon after the line "mount -a"?
Thanks
-
albertone74 wrote:
> Hi,
> After several re-installations (Squeezelite, Ubuntu,ect,.) now I can
> finally listen to my 24 bits FLAC. :)
> The trick was to start with the command: squeezelite -b 256:256
> Would it be possible to let squeezelite know to start with that option
> automatically?
> Th
Triode wrote:
> You need to get rid of this message:
> [16:05:00.876453] slimproto_run:446 error reading from socket: closed
>
> I think you will see errors in the server log related to this and its
> likely to be due to having more than one process. Try restarting the
> server, removing any pl
Triode wrote:
> Yes the buffer sizes are the two lines above - if you are worried
> whether buffer changes apply, look at these at startup with different -b
> values. [default should work fine though!]
Thanks for the tips. I'm pretty sure I know what is going on now and
it's not software drop o
vortecjr wrote:
> I started playback with 192 content then switched to 352.8:
> [17:20:32.036568] output_init:1268 outputbuf size: 3528000
> [17:20:32.037560] stream_init:264 streambuf size: 2097152
>
Yes the buffer sizes are the two lines above - if you are worried
whether buffer changes apply
On 27/01/13 17:41, Julf wrote:
cdmackay wrote:
It's a shame it doesn't support manual entry of known offset (since I
know that from the XLD log)
It does. rip cd rip -o offset
yup, sorry, I meant whilst verifying, not whilst ripping.
or try to work out the offset by comparing
a given rip t
cdmackay wrote:
> It's a shame it doesn't support manual entry of known offset (since I
> know that from the XLD log)
It does. rip cd rip -o offset
> or try to work out the offset by comparing
> a given rip to the AR DB.
Well, that's pretty much exactly what it does, by doing multiple trial
Triode wrote:
> Start with "-d stream=debug" and "-d output=debug" to see the buffer
> sizes actually used. [pcm decode does make a minor adjustment to the
> pre decode stream buffer when a stream is opened to make to simplify the
> code, but the basic size is what you see at startup.]
I starte
I just bought a Fit-pc to use as a headless unit to run Squeezelite.
Which version of linux would be a good one to install to give best
performance. I can install on a little USB stick or on the 30gb internal
drive. Which is best. Sorry for the newbie questions.
-
Triode wrote:
> Start with "-d stream=debug" and "-d output=debug" to see the buffer
> sizes actually used. [pcm decode does make a minor adjustment to the
> pre decode stream buffer when a stream is opened to make to simplify the
> code, but the basic size is what you see at startup.]
I decide
vortecjr wrote:
> This is really odd if those are the defaults! I was getting some minor
> dropouts with 192 and continuous dropouts with 352.8. I added -b 256:256
> and restarted SL and all was fine. I'll play around with it some more
> and let you know.
>
Start with "-d stream=debug" and "-d
vortecjr wrote:
> Another simple bit perfect test is a HDCD rip played back into a
> receiver/processor or DAC that supports the format. I had a Rotel
> processor once that would display the logo if the data came in
> correctly. I'm confident from what I have seen so far that Sl is bit
> perfect
Mnyb wrote:
> You can also test for bit perfectness with an AC3 or DTS stream .
>
> You could encode the wav file to a flac file it wont compress much but
> you get better suport for tags and embedded cover art etc
Another simple bit perfect test is a HDCD rip played back into a
receiver/proces
vortecjr wrote:
> I found an Intel Core 2 and compatible motherboard with 2GB RAM in the
> boneyard. I loaded Vortexbox 2.2 on a 64 GB SSD and installed
> Squeezelite 0.9beta11 Linux ALSA Intel 32 bit. Last night I connected
> this via i2s to my custom built TPA Buffalo Sabre DAC and streamed
> 2
Triode wrote:
> There's a post higher up the thread on the -b option, but I'm supprised
> you need to use it at those parameters as the defaults are close to: -b
> 2048:3446. I'd expect you wanting to try making them bigger not
> smaller. (I'd leave the output one and adjust the input one)
Thi
vortecjr wrote:
> I found an Intel Core 2 and compatible motherboard with 2GB RAM in the
> boneyard. I loaded Vortexbox 2.2 on a 64 GB SSD and installed
> Squeezelite 0.9beta11 Linux ALSA Intel 32 bit. Last night I connected
> this via i2s to my custom built TPA Buffalo Sabre DAC and streamed
> 2
I found an Intel Core 2 and compatible motherboard with 2GB RAM in the
boneyard. I loaded Vortexbox 2.2 on a 64 GB SSD and installed
Squeezelite 0.9beta11 Linux ALSA Intel 32 bit. Last night I connected
this via i2s to my custom built TPA Buffalo Sabre DAC and streamed
24/352.4. I also tried lower
THX a lot for the feedback. Needs some time to digest. ;)
soundcheck's Profile: http://forums.slimdevices.com/member.php?userid=34383
View this thread: http://forums.slimdevices.com/showthread.php?t=97046
_
soundcheck wrote:
>
> 1.
> Interesting to see that you looked already in SCHED_FIFO scheduling for
> squeezelite.
> If you run the "output" ?? thread SCHED_FIFO, what priority do you
> assign?
> FYI: My favorite audio app -- ecasound -- offers an external prio
> parameter to set the priority
PasTim wrote:
> As a matter of interest, why would one want to run Squeezelite on a
> Touch? Am I missing a clever trick here?
Good question. ;)
Your Touch becomes a NOTouch. A kind of DUET II.
squeezelite would be a much more efficent app than squeezeplay.
In my case, I can easily see ho
One more:
I saw your comment in the code that SCHED_FIFO priorities are likely to
be changed by root only. That's correct if below settings are not done:
Something like below must be added to /etc/security/limits.conf
squeezeboxserver - rtprio 99
squeezeboxse
Hi Triode.
Interesting that it works on your Touch. I need to recheck my Touch and
turn off all my optimizations.
Some more Qs:
1.
Interesting to see that you looked already in SCHED_FIFO scheduling for
squeezelite.
If you run the "output" ?? thread SCHED_FIFO, what priority do you
assign?
27 matches
Mail list logo
