garym;604261 Wrote:
I can't speak to the consensus, but plenty of smart people on this forum
that know a lot more than me don't think that decoding on the server
side vs Touch matters to the ultimate sound quality. Try it both ways
and see what you think. It's just a couple of settings in
Using ethernet can make 24/96 more snappy wether you decode on server or
not.
it was almost impossible to use wifi and 24/96 the first weeks of Touch
life but this has improved greatly .
Seems like WPA2 decryption uses a lot of cpu making it somewhat
sluggish ? to handle.
Run ethernet wires if
Rick58;604292 Wrote:
I hope this is what is going on with my setup, and that you excuse a
couple of 'noobie' questions.
iMac - Airport Extreme (wireless) - Touch - optical out - Cambridge
840C
The 840C indicates =20 which seems strange, when the song being
played is 16/44.1 AIFF or
But it must be a difference in some bit as his dac reports 24bit when
conected directly to his computer via toslink ?
--
Mnyb
Main hifi: Touch + CIA PS +MeridianG68J MeridianHD621 MeridianG98DH and
assorted amps SiriuS,
guidof;604286 Wrote:
Quite true!
I just think that, to the extent that there are differences to be
perceived, they are more likely to become apparent when listening to a
variety of recordings over extended periods.
Sometimes judgments are formed based solely on repeated listening to
Mnyb;604332 Wrote:
But it must be a difference in some bit as his dac reports 24bit when
conected directly to his computer via toslink ? THANKS folks for the replies!
With the direct link, it actually indicates =24/96 which I interpret
to mean 24/96 ... but if it says =20/96 even tho in my
doh! maybe this shows how much I don't know and that's OK, if I learn
something. I don't really want to learn 'everything' about this, but
would like to understand a little more than I do now ...
The status bits that are referred to are in the data stream itself,
(i.e. the original source (FLAC,
Phil Leigh;604333 Wrote:
I don't want to get into a big heated debate about this, but to do a
meaningful assessment over time, one needs to switch back to the
original settings occasionally, otherwise there is no comparative
baseline - it's exactly like the burn-in situation. If you only
roscored1000;604051 Wrote:
thanks once again, great unit by the way isnt it?
Yes, it is. Enjoy :)
--
GeeJay
2-SB3s, 1-Duet, 1-Touch...and an iPeng convert.
GeeJay's Profile:
Hi guys.
Yep, it's me once more.
For those of you who're enjoying my Toolbox.
I launched a new tweak. (Perhaps we should call it something else,
you'll see what I mean later on)
I talked about that mod respectively announced its effects earlier. ;)
Just follow the TT Beta Blog link in my
Rick58;604384 Wrote:
doh! maybe this shows how much I don't know and that's OK, if I learn
something. I don't really want to learn 'everything' about this, but
would like to understand a little more than I do now ...
The status bits that are referred to are in the data stream itself,
Phil Leigh;604464 Wrote:
get some insulating tape and place it over the display - problem solved
:-)
LOL yes, I could not use my 'binoculars' to look at the display, I
guess! It's about 12' away, I can't quite read whether it shows 20 or 24
from my chair!
OTOH, after rereading the 'bug
Hi All,
New to the streaming thing, but having trouble liking the Touch so far.
I guess from previous threads that my using iTunes might be my issue.
Problems include;
Refusing to group multi-disc albums together.
Randomly missing artwork.
Sometimes turning artwork by 90 degrees.
Randomly
1) On the SBS web ui, check your setting on Settings My Music Group
Discs. Also check your album tags. If they are not perfectly identical
(eg, they have 'disc 1' and 'disc 2' in the tags) then they won't be
grouped.
2) Shouldn't be a problem if you have a cover.jpg image in each album's
Is there any interference from the Touch when placed near a loudspeaker?
I'm contemplating the Touch in stead of Duet but the only place is next
to a loudspeaker (about 30 cm).
--
Hans Gerrits
Hans Gerrits's Profile:
Hans Gerrits;604472 Wrote:
Is there any interference from the Touch when placed near a loudspeaker?
I'm contemplating the Touch in stead of Duet but the only place is next
to a loudspeaker (about 30 cm).
No it has an lcd display no risk of bending the picture on it with the
speakers magnets
Thank you for the quick reply. I wasn't actually thinking of a
loudspeaker interfering with the Touch screen, but the other way
around: does the (electric field of the) player intefere with the sound
from the loudspeaker?
--
Hans Gerrits
Thanks for reply, I have definitely got the disk tags all correct but no
joy there.
I have no need for playlists from iTunes so would happily lose it but
if you ditch iTunes and simply browse to the music folder, is there any
way to browse all albums with covers showing?
Each time I rescan or
Hi Klaus,
I read your blog about your latest change
Let me know what you think. I do expect that you'll hear what I hear.
The question will be how to make Logitech accept their own logic:
100 = 100 = false^2
Now. Seriously.
I'd like to say that the difference in sound
Hans Gerrits;604477 Wrote:
Thank you for the quick reply. I wasn't actually thinking of a
loudspeaker interfering with the Touch screen, but the other way
around: does the (electric field of the) player intefere with the sound
from the loudspeaker?
If you speakers are passive (i.e., don't
Hans Gerrits;604477 Wrote:
Thank you for the quick reply. I wasn't actually thinking of a
loudspeaker interfering with the Touch screen, but the other way
around: does the (electric field of the) player intefere with the sound
from the loudspeaker?
That would be very unlikely I have not
bluegaspode;604480 Wrote:
So SqueezePlay (the firmware of the Touch) indeed uses the maximum
possible value for it's internal gain setting when you set it to 100%.
'65536' is exactly the same value that is used in your mod.
I think the modded '65536' easily outperforms the original
Mnyb;604483 Wrote:
... the usual rat nest of cables behind a hifi is a more likely trouble
source.
Thanks again for the reply. The rat nest made me laugh :)
--
Hans Gerrits
Hans Gerrits's Profile:
Rick58;604467 Wrote:
LOL yes, I could not use my 'binoculars' to look at the display, I
guess! It's about 12' away, I can't quite read whether it shows 20 or
24 from my chair!
OTOH, after rereading the 'bug report' I see the issue MAY be related
to something the Touch itself sends:
I can just tell you that I received numerous feedbacks about the audible
differences, what I expected. Just read the latest comment over there.
I'm not doing any debugging. Non of the modifications I introduced
respectively its effects I'd expect to show up in a debugger.
What I guess though
Phil Leigh;604490 Wrote:
You might get lucky - but it's a rather niche, cosmetic issue...
Tell you what, I'll vote for the bug :-)
But wouldn't all DACs that report bit depth along with sample rate
benefit? Maybe the Cambridges are the only ones ... if so, oh well.
If you know, could you
Rick58;604467 Wrote:
Looks to me that setting Channel Status Word bit 2 to '1' (and maybe
forcing bits 3-5 to 'zero') when 24 bit data is being sent should
'solve' the issue.
The channel status word bit 2 defines the copyright bit (DCMS). It has
*nothing* to do with wordlength. I have the
Griffin;604495 Wrote:
The channel status word bit 2 defines the copyright bit (DCMS). It has
*nothing* to do with wordlength. I have the official spec on my desk at
work but ePanorama has a nice overview 'here'
(http://www.epanorama.net/documents/audio/spdif.html) (scroll down to
channel
You -can- apparently set this with alsa ? It's actually beyond me if you
actually should ?
Apearently you can also chose between consumer spdif or pro AES-EBU
over spdif .
But modern DAC's reciever chips read both format equally well afaik ?
so it should not matter much.
But consensus seems to
soundcheck;604493 Wrote:
It seems to happen more than just setting that parameter. As soon as I
set the parameter as petersw ( I made a reference to his proposal on my
blog btw.), things are changing.
So thanks first for referencing peterw's post - this makes it possible
to at least
bluegaspode;604515 Wrote:
So thanks first for referencing peterw's post - this makes it possible
to at least know what your are doing.
In the end you just changed a single line in the sourcecode, did you
(the one suggested by peterw) ? Nothing deleted, nothing added, just
one simple line
But to not be the lonely critic here:
Anyone who is not able to put his volume to 100% (maybe just 99%
without knowing) will of course get improvements.
Not only does his audio get a tiny bit louder (which will always sound
better as we all know) but as said the raw material won't be changed.
Hmm volume lock the logitech way works too, I used peters hack before
there was an official way to do it.
Trying with DTS files to my HT amp they still work so 100=100 So the
volume is the same.
But there is still a bug in sbs where volume lock does not work for the
web-UI
So there is still a
What format are your files? If MP3, I suggest you try putting them in a
good tagging program like mp3tag (www.mp3tag.de) to have a really close
look, including at the extended tags and the possibility of different
tag types such as both ID3v1 and ID3v2. If your multi-disc albums are
getting split
paulster;594334 Wrote:
If you want really good artwork and don't mind a bit of manual work then
www.albumartexchange.com really has no competition for quality of
images.
It's more involved than using an automated tool but the quality is
fantastic.
+1
This and VSO's Image Resizer, makes
bluegaspode;604519 Wrote:
But to not be the lonely critic here:
Anyone who is not able to put his volume to 100% (maybe just 99%
without knowing) will of course get improvements.
Not only does his audio get a tiny bit louder (which will always sound
better as we all know) but as said the
Mnyb;604520 Wrote:
So there is still a reason to fix it a the player level, god knows what
happen when involwing mysb.com.
locked this way I think the player happily ignores all replaygain
crossfade and whatnots you can turn on on the server.
So the result is exactly the same but it
2^16 = 65536
And the volume maps is earlier in the same file so you can actually see
that 65536 is what logitech consider 100 volume.
I can confirm that it works, trying rigth now
--
Mnyb
Main hifi: Touch + CIA PS
QUOTE=bluegaspode;604515]In the end you just changed a single line in
the sourcecode, did you (the one suggested by peterw) ? Nothing
deleted, nothing added, just one simple line changed.
Instead of passing a variable (i.e. the internal volume value) that is
computed in the lines before (with and
Mnyb;604520 Wrote:
locked this way I think the player happily ignores all replaygain
crossfade and whatnots you can turn on on the server.
Nope.
ReplayGain and Crossfades are still applied directly within the player
(in addition to the volume).
Can be disabled in the Playback.lua at the
bluegaspode;604519 Wrote:
But to not be the lonely critic here:
Anyone who is not able to put his volume to 100% (maybe just 99%
without knowing) will of course get improvements.
Not only does his audio get a tiny bit louder (which will always sound
better as we all know) but as said the
bluegaspode;604534 Wrote:
Nope.
Replaygain and crossfades are still applied directly within the players
decoding routines (which cannot be changed as the decoding routines are
compiled and not scripted).
They can still be disabled in the Playback.lua by sending manipulated
values to the
Mnyb;604505 Wrote:
You -can- apparently set this with alsa ? It's actually beyond me if you
actually should ?
Apearently you can also chose between consumer spdif or pro AES-EBU
over spdif .
Interestingly there is a difference between consumer and pro .
AHA ... maybe this is the
Interesting... fwiw, the multi-disc issue was my own doing. Whilst the
tagging was all correct, within the file directories, the separate
discs were in 2 separate folders, so some rearranging can sort that.
As I use solely MP3s, I will look into the program you mention, I have
seen it mentioned
Mnyb;604541 Wrote:
Ben has some kind of patch I just applied described in this bug:
http://bugs.slimdevices.com/show_bug.cgi?id=14807
If you applied soundchecks or peterw's mode you won't need Bens patch.
Actually I think it's buggy anyway, don't use it (I left a comment in
the bug
scooot;604546 Wrote:
i managed to implement the original 2.0 mods.i have tried the volume fix
but keep getting ttvol100 not found when i execute it in he command
line.any help would be appreciated.regards scott
Did you download the beta package (touchtoolbox20BB1.tar) and unpack it
in the
JHedley;604543 Wrote:
Interesting... fwiw, the multi-disc issue was my own doing. Whilst the
tagging was all correct, within the file directories, the separate
discs were in 2 separate folders, so some rearranging can sort that.
If the files are tagged correctly then it doesn't matter if they
bluegaspode;604544 Wrote:
If you applied soundchecks or peterw's mode you won't need Bens patch.
Actually I think it's buggy anyway, don't use it (I left a comment in
the bug report).
I'm a coder, I know the effects without a need to try them out ;)
As I had to implement playback and
48 matches
Mail list logo
