Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: Google Play Music and high res FLAC on Samsung Galaxy S5 (Read 41574 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #25
The frequency response you measured looks very good indeed. Are you sure the playback sampling rate was 192kHz ? The sweep frequency goes up to 96kHz but "only" 40-something comes out. This could indicate resampling to 96kHz.


OP's sampling rate on the recording side is known to be @ 96.

Creature of habit.

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #26
What are you going to be playing these through? Headphones? IEMs? I've never seen any IEMs that go above 20KHz, I'm sure there are some but even very good ones don't go higher than this.


I'll be playing them through relatively cheap earbuds, mostly.  Guess that doesn't help the case for 96k. 

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #27
Just so I don't leave anyone out, here is the frequency graph from Kees de Visser's 0-48 kHz sine wave sweep, as played back from my phone (thanks!):
It's a 0-96kHz sweep actually. When uploading the testfile I typed that wrong. Moderator Kohlrabi has corrected that, thanks!.
The frequency response you measured looks very good indeed. Are you sure the playback sampling rate was 192kHz ? The sweep frequency goes up to 96kHz but "only" 40-something comes out. This could indicate resampling to 96kHz. That's probably not enough reason to sell your S5 and buy a Pono though


I'm not sure the playback sampling rate was 192, that's why I did the test.  If it resamples to 96, I'm OK with that, as 192 is very much overkill for my purposes anyway (and 96 might be too).  I'll stick with my phone, that Pono looks uncomfortable to put in your pocket. 

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #28
I'll be playing them through relatively cheap earbuds, mostly.  Guess that doesn't help the case for 96k. 


So why do you want lossless 24/192 files again?  I have good IEMs and listen to MP3s.

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #29
Lossless in general, and (IIRC) flac in particular, just isn't efficient for higher bitdepths - and, to a lesser extent, higher sample rates.

I'm not talking about audibility, or anything like that. What I mean is that the extra LSBs are effectively almost all noise, and hence unpredictable, and hence incompressible. For PCM, the raw datarate increases by 50% from 16-bits to 24-bits. For non-loudness war recordings, the increase in FLAC bitrate can be much greater.

The increased sampling rate isn't so much of a killer, especially on the many recordings where essentially "there's nothing extra up there" in the higher frequencies. However, I have a recollection (correct me if I'm wrong) that FLAC's predictors (and maybe its default black size) don't work as well at 192kHz as at 44.1kHz. Even if there's no extra real information (i.e. you simply upsample 44.1 > 192 essentially perfectly), the bitrate increases.


If you want measurable perfection beyond the bounds of the best human hearing while taming bitrates slightly, something like 20/96 with a gentle low pass filter starting at about 25kHz is a good choice. 24/96 or 24/48 run through lossyWAV with conservative settings (including, for examples, always keeping at least 16-bits intact) is another option. A higher bitdepth gives you a wider dynamic range (which you don't need) and the ability to turn the volume up during fades and reverb tails without hearing dither noise; a higher sample rate gives you a wider frequency response (which you don't need) and the ability to play back inaudible test signals instact and without intermodulation due to slow roll off DAC filters. It's things like this that are really important when you're listening to music on the move

Higher bitdepth and sample rate don't make things within the normal audible frequency and dynamic range more accurate. Certain people claim they do, but that's because they don't understand digital audio and, frankly, like to imagine things - or are trying to sell you something. People who believe this stuff often take great care with their recordings, and so they sound very good. The same recordings still sound very good converted to 16/44.1.

Cheers,
David.


Thank you, that's very good info.  I guess the sensible thing to do is just do my own ABX testing and see if I can even tell the difference before devoting gigabytes to high res audio, which I haven't really done in a scientific way.  I know 24/192 is complete overkill, but I'll have to do my own tests with 24/96.  I don't really have a desire to do my own manual tweaking with going to 20/96 and using filters, since there are libraries of music already available in 24/96 (from HD Tracks, for example) and that is a pretty standard format , but I appreciate the suggestion.

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #30
The frequency response you measured looks very good indeed. Are you sure the playback sampling rate was 192kHz ? The sweep frequency goes up to 96kHz but "only" 40-something comes out. This could indicate resampling to 96kHz.


OP's sampling rate on the recording side is known to be @ 96.


Oh yeah, you're right!  I totally forgot that the Mac mini's sound card is limited to 96k.  That would explain why the recording frequencies were cut off for the 96k tone test.  So, the phone can theoretically play back 192, but I have no way of verifying this because I don't have a sound card that supports that high of a bitrate.

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #31
Oh yeah, you're right!  I totally forgot that the Mac mini's sound card is limited to 96k.  That would explain why the recording frequencies were cut off for the 96k tone test.  So, the phone can theoretically play back 192, but I have no way of verifying this because I don't have a sound card that supports that high of a bitrate.


Sample rate, not bit rate!

 

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #32
The frequency response you measured looks very good indeed. Are you sure the playback sampling rate was 192kHz ? The sweep frequency goes up to 96kHz but "only" 40-something comes out. This could indicate resampling to 96kHz.
OP's sampling rate on the recording side is known to be @ 96.
OK, if that's known, than it's fine. I just assumed 192kHz rate since the  frequency axis of the posted FFT goes to 96kHz and the FFT applications I use automatically adjust the scale max. to the Nyquist frequency.

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #33
Thank you, that's very good info.  I guess the sensible thing to do is just do my own ABX testing and see if I can even tell the difference before devoting gigabytes to high res audio, which I haven't really done in a scientific way.  I know 24/192 is complete overkill, but I'll have to do my own tests with 24/96.  I don't really have a desire to do my own manual tweaking with going to 20/96 and using filters, since there are libraries of music already available in 24/96 (from HD Tracks, for example) and that is a pretty standard format , but I appreciate the suggestion.


Seriously man. Don't pick an arbitrary floor with your ABX testing. After proving to yourself there is no need for anything beyond 16/44.1, see just how far down in bit rate you can go with lossy codecs. You may find that you're so grossly overestimating your needs that you're simply wasting tremendous amounts of space on your phone for no real gain. Almost my entire music library is FLAC, but I transcode it all to OGG Vorbis at around 96kbps to load on my phone because, seriously, on the vast majority of my music I just can't tell the difference between lossless and the q2 Vorbis.

For listening, 16/44.1 really is more than enough. And if you objectively test the modern lossy codecs you'll be quite shocked at how good they really are. I used to lossy encode, even AAC and Vorbis, at no less than 160kbps and thought I could tell the difference. ABX shattered that delusion, and ended up almost doubling the amount of music I can store on my devices!

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #34
I'll be playing them through relatively cheap earbuds, mostly.  Guess that doesn't help the case for 96k. 


So why do you want lossless 24/192 files again?  I have good IEMs and listen to MP3s.

I have good headphones and listen to mp3s.

This thread is another example of pervasive audiophile nonsense causing someone to consider fixing something that isn't a problem (sample rate) before fixing something that is (transducers). People sometimes ask what harm can (inaudible) "improvements" do; here is your answer.

Cheers,
David.

P.S. I agree with yourlord entirely, though I use a higher lossy bitrate that I absolutely know I can't ABX (or haven't yet). That way, I can be 99.99% sure that any problems I hear not due to my encoding, but are on the originals, without even having to check. Every time I have checked, the mp3 artefacts I've thought I was hearing have been right there on the original CD (and usually not mp3 artefacts at all, though you'd be surprised what junk does get mastered to CD).

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #35
KitKat documentation clearly states that system provides downsampling without dithering. Regarding testing the files, it is wasting time. First at all you can't hear this frequency so you can't test using ears. Even if you get oscilloscope and connect to Samsung phone jack, you can still see nothing, just because Samsung audio analog track is limited to 20KHz.
If you want to get full advantage of 24/192 you need to connect an external UBS DAC and make sure your audio program is capable to use it. Not so many audio players can utilize it now, but some will be soon. I am holding buying S5 until Kamerton will support external DACs.


Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #37
@MOCKBA: Do you realize that the same post that you are replying to contradicts what you are saying?

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #38
KitKat documentation clearly states that system provides downsampling without dithering. Regarding testing the files, it is wasting time. First at all you can't hear this frequency so you can't test using ears. Even if you get oscilloscope and connect to Samsung phone jack, you can still see nothing, just because Samsung audio analog track is limited to 20KHz.


The only waste of time was your reply from ignorance.  Playback of audio well over 20khz has already been demonstrated.
Creature of habit.

Google Play Music and high res FLAC on Samsung Galaxy S5

Reply #39
Even if you get oscilloscope and connect to Samsung phone jack, you can still see nothing, just because Samsung audio analog track is limited to 20KHz.


FWIW, this is only true at 44.1kHz.  On a modern oversampling DAC (which is the type used in smartphones and other portable electronics), the reconstruction filter cutoff actually scales proportionally with the sampling rate.  So it'll be around 20kHz for 44.1KHz, 22 KHz for 48k, 43KHz for 96k, and so on. 

This is because the actual analog filter is set at about 1/4 to 1/2 the the oversampled rate (typically 5-10MHz) and a variable digital filter is used below that.  Furthermore, when you change the sampling rate, generally the oversampling ratio is adjusted to maintain a nearly constant actual sampling rate.  So for example, at 48kHz, the player might oversample 256x for a rate of 12.3MHz.  At 96k the oversampling ratio will be changed to 128x for a rate that is still 12.3 MHz.  However, the bandwidth of the digital filter will be fixed at approximately 90-95% of the Nyquist rate, hence the actual bandwidth scales with sampling rate, and SNR is approximately constant.