Sound Eq
Headphoneus Supremus
- Joined
- Nov 9, 2013
- Posts
- 11,139
- Likes
- 2,811
Sorry - I answered your question, and then my remark about upsampling was aimed at Sound Eq's question - I should have formatted my reply to make it more apparent that I was speaking to each of you, in turn.
But since you asked, when I said 'upsample', I meant, as an example, buying a 16 bit 44.1khz (44,100 samples per second) file and allowing it to be upsampled to, something like 24 bit 192khz, on-the-fly, before it is sent across the digital output of your transport device, to Mojos digital input.
Although it is a very easy mistake to make, you should not confuse the bitRATE of your compressed files with the bit-DEPTH or SAMPLE-rate of the digital signal.
An iTunes file at 256kbps (lossily compressed with .aac codec) will more than likely be a 16 bit 44.1khz file, compressed with the lossy codec, at a bitRATE of 256 kilobits per second. When your digital transport (I mean your computer or your DAP or your smartphone) reads that music file, it will decompress the .aac compression so that a PCM file is created (this is done invisibly, on-the-fly). In my present example, that would mean that within TEMPORARY buffers, the file has remained in 16 bit 44.1khz (samples per second) resolution, but has been freed of the .aac compression codec, and will be sent as an uncompressed 16/44.1khz PCM file, across the digital connection, to Mojo.
You don't have to do anything about this. All you ever need to do is make sure (once) that your transport device is not sticking it's nose in and secretly changing the sample frequency and bit depth (in my example, Android stupidly upsamples EVERY audio track to 24/192khz, regardless of it's original resolution, so a program called UAPP is necessary, to bypass this Android anomally).
On any digital transport, there should be an option to set it to leave every file alone, in it's native sampling frequency and native bit-depth. Once that setting has been correctly set one time, it should never need to be changed again.
There is a partly-related post, here: www.head-fi.org/t/784602/chord-mojo-the-official-thread-please-read-the-3rd-post/16500#post_12525696
If you are using Neutron, then, as far as I'm aware, you are unable to bypass the automatic upsampling to 24/192 that the Android OS stupidly does, without asking.
Therefore, it is to be expected that you may hear a difference in the sound, compared to Neutron feeding Mojo from iOS, since, AFAIK, iOS does not automatically upsample everything to 24/192, like Android does.
Android upsampling files to 24/192 is not a good thing, and, as I earlier remarked, is not recommended by Rob Watts, and some of the reasons are described in his 'interesting posts' section, near the top of post #3.
Some people have also played around with deliberately invoking upsampling-to-DSD, on-the-fly, and said it sounds good, to their ears (and that's their prerogative), but Rob designed Mojo and understands the complex digital theory & mathematics behind such matters - here is one of his responses:
Also relevant:
.
thanks for all the info, but to me i do not think upsampling is happening in my case as i am on lollipop on galaxy note 3 using neutron player, honestly the big difference between android and ios both using neutron is really big in regards to getting a wider sound stage and fuller sound, I asked my friend to listen and he also confirmed the same thing
using neutron in android lollipop android 5.0 does indeed has a much bigger sound stage than when I use my apple iphone 6s plus