philippe_44 wrote:
Sounds like a faulty device or a configuration problem, as if you used
PCM 44.1/16 they are just raw. Don't want to defend Sonos against
Squeezebox line :) here but as much as one can be not happy with the
PLAY:1, 3 or 5 loudspeaker characteristic, the CONNECT when used
Ok , two was fixing this .
Get a more powerfull server .
Make yourself 24/48 copies of the 24/96 files ( flac is a good idea ),
very easy to do with dBpower amp or foobar and dozens of other apps .
Main hifi: Touch + CIA PS
kh6idf wrote:
I returned the Sonos Connect after listening to it for a week. Using
the digital out (coaxial or optical) the sound was thin, bass-shy and
more 2-dimensional than the Squeezebox. So much so that I found myself
not wanting to listen. Today I put the SB3 back in place and
I'm not at all impressed with the sound quality of my Sonos connect
(it's not entirely bad, too. It's simply average) but hey, we are
talking about Rhapsody here, aren't we? I mean, it doesn't get much
worse there days if we talk about sound quality so what you stream it to
pretty much doesn't
alfista wrote:
Can you present a market analysis backing that?
I think there are two developments which would make a market analysis
interesting. First, the market exploded shortly after Logitech exited.
Second, the products offered on the market changed.
The first development is obvious. A
Ikabob wrote:
I believe they'd really be able to market them to bring in a very big
profit.
Can you present a market analysis backing that?
alfista's Profile: http://forums.slimdevices.com/member.php?userid=32396
Now that Logitech seems to have turned it back on Squeezebox won't it be
time to rename the product to Slimserver again?
A waste of time. As long as there are no serious problems with the name
I won't touch it. SlimServer most likely would cause new problems anyway.
--
Michael
You are SOL.
http://forums.slimdevices.com/showthread.php?103529-Rhapsody-no-audio-with-Logitech-SB3
toby10's Profile: http://forums.slimdevices.com/member.php?userid=12553
View this thread:
I am starting to build a small library of hi-res files and noticed an
unusual behaviour when playing them on my SB3 and Radios.
I use a QNAP TS-212P as server (LMS 7.8.0) and never had any issues with
my large library of standard 44.1kHz/16bit files, mostly CD rips in
uncompressed alac and flac,
I've got the damnest problem that I can't figure out. I own a Squeezebox
Classic as well as a Squeezebox Radio. When I try to play a selection
from Rhapsody through the Classic using the Logitech Media Server (LMS),
I get no audio. The display shows the audio streaming, and if I go to
the
th00ht wrote:
Now that Logitech seems to have turned it back on Squeezebox won't it be
time to rename the product to Slimserver again?
I was wondering, as I might take on a mod on the Arch package to load
sources from github instead of the download slimdevices.com servers.
If you have any
Now that Logitech seems to have turned it back on Squeezebox won't it be
time to rename the product to Slimserver again?
I was wondering, as I might take on a mod on the Arch package to load
sources from github instead of the download slimdevices.com servers.
Ripping: 'EAC (free and great)'
This is not entirely complete .
http://wiki.slimdevices.com/index.php/Hardware_comparison
There are product links at the top .
But in your case SB3 and radio supports up to 24bit 48kHz natevily so
SoX will be running on 24/96 files .
it should not be running with 24/44.1 files ? is this a
kh6idf wrote:
I got the following email from Rhapsody today:
Hi-
Thank you for writing back to Rhapsody support.
There was a server problem from Rhapsody and it is now resolved. Please
sign out from Rhapsody, restart device and try to sign in to access
music with out any problem.
I
Sox means resampling. That should not happen for 44.1/48 kHz material,
all players support that (except slimp3) also with 24 bit.
Only touch, transporter and most software players support 96 kHz, all
others need resampling which is CPU heavy
---
learn more about iPeng, the iPhone and iPad
MeSue wrote:
Here's how they replied to my goodbye message on their Fb page...
I'm flabbergasted at her response. I've been a subscriber to Rhapsody
since they were owned by Real. Guess it's time for Spotify for me!
Oh, and depending on your server setup ALAC might always be transcoded
to FLAC. ALAC is natively supported by Touch (and some software players,
like iPeng) only but the default server setup even transcoded for these
players until 7.7.3 or so. ALAC to FLAC transcoding should not require a
lot of
Thanks for the reply. If that's true, and apparently it is, I'm done
with Rhapsody. Too bad since I've been a subscriber since they were
owned by Real.
Spotify, here I come.
bocaboy's Profile:
bocaboy wrote:
I'm having the same problem. Your e-mail is dated late April, and I'm
writing this in the first part of May. How can they allow a problem like
this to go on for so long??!!
If you have an SB3 or duet ,classic or boom or tranporter your problem
will never be resolved as the
pippin wrote:
Oh, and depending on your server setup ALAC might always be transcoded
to FLAC. ALAC is natively supported by Touch (and some software players,
like iPeng) only but the default server setup even transcoded for these
players until 7.7.3 or so. ALAC to FLAC transcoding should not
You are right, the default is still off but at least it's now
configurable in settings. In the past native ALAC was commented out in
the convert.conf.
---
learn more about iPeng, the iPhone and iPad remote for the Squeezebox
and
Logitech UE Smart Radio as well as iPeng Party, the free
Thank you for all the info, just repeated some testing with alac and
flac and up to 48kHz/32 bit there is no problem... I must have confused
some files, earlier. Max cpu was 16% for alac 48/32 on SB3 (faad and
sox), while just a few % for Radio with the same file.
Problems then happen only with
22 matches
Mail list logo
