darrenyeats wrote:
> Thanks Clive.
>
> To summarise what members utgg has clarified for us, a Touch volume
> setting of 40 (~-30db) or higher will be bit perfect with 16 bit source.
> So in this respect at least, similar to earlier Squeezeboxes according
> to your link.
>
> That just leaves us
Thanks Clive.
To summarise what member utgg has clarified for us, a Touch volume
setting of 40 (~-30db) or higher will be bit perfect with 16 bit
source.
That just leaves us the problem of below Touch volume 39 or less.
Check it, add to it! http://www.dr.loudness-war.info/
SB Touch
-
toby10 wrote:
> Yes, hardware limited including digital outs. That's why many prefer
> the Touch+EDO for external DAC's (at a fraction of the price). :)
> Or just Touch alone as downsampling to Touch native resolution makes no
> audible difference.
Touch without EDO is 24/96 same as transporte
darrenyeats wrote:
> Can you remember where you read that?
Sorry, this goes back to 2005 or 2006. I have tried searching the forums
to find the threads that discussed the firmware updates in detail, but
without success. But I do distinctly remember seeing discussions about
how the volume adjustme
utgg wrote:
> The table gain values of 2048 and greater are all multiples of 256. That
> means if you multiply 16-bit data by the table values, the least
> significant 8 bits of the 32-bit result will be all zeros - so there is
> no truncation when the most significant 24 bits are fed to a 24-bit
garym wrote:
> As toby10 notes, YES, it is limited to 24/96 without the possibility of
> a change (such as using EDO).
thanks, and i appreciate the lack of ad hominem statement wrt sq.
--
4 TB Drobo-->FW 800-->mac mini-->Ethernet
Transporter--> Wireworld Eclipse 6 coax-->Meridian G61
G61--> N
darrenyeats wrote:
> utgg, do you know where and how could one invoke this function?
> >
Code:
> >
> --provide hook for applets to modify the gain curve
> function overrideDefaultVolumeToGain(self, value)
> _defaultVolumeToGain = value
> end
>
---
toby10 wrote:
> Yes, hardware limited including digital outs. That's why many prefer
> the Touch+EDO for external DAC's (at a fraction of the price). :)
> Or just Touch alone as downsampling to Touch native resolution makes no
> audible difference.
As toby10 notes, YES, it is limited to 24/96
utgg wrote:
> The table gain values of 2048 and greater are all multiples of 256.
I missed that. Probably because 256, 512 etc are missing below 2048! Why
on earth try to follow some notional curve when SOME of these were for
the taking?! We could have had some volume settings with non-truncation
TimT wrote:
> DavidNL,
>
> I just placed an order for a Rasp Pi 2 & Hifiberry DAC+ and the needed
> parts (case, SD card, PSU). Some say that this is a simple DIY project.
> Watch this space; I will let you know if it is.
It is simple. 20 minutes to put it together and have it playing music.
p
netchord wrote:
> a bit off topic, but does anyone know if the transporter's digital
> OUTput is limited to 24/96? if one *could* theoretically send a 24/192
> signal to the TP, would it pass it along intact via it's coax/bnc output
> w/o downsampling?
Yes, hardware limited including digital ou
a bit off topic, but does anyone know if the transporter's digital
OUTput is limited to 24/96? if one *could* theoretically send a 24/192
signal to the TP, would it pass it along intact via it's coax/bnc output
w/o downsampling?
--
4 TB Drobo-->FW 800-->mac mini-->Ethernet
Transporter--> Wirew
darrenyeats wrote:
> Thanks Mynb,
> If the aim is not to truncate, the first numbers I expect to pop out are
> binary roots of 65536 (i.e. powers of 2) e.g. 256, 512, ..., 16384,
> 32768. Their absence indicates that avoiding truncation was not a goal
> at all.
>
The table gain values of 2048 a
13 matches
Mail list logo
