Android HD Audio (24bit / 192Khz) on NVidia Shield TV
#46
(2016-03-11, 22:25)fritsch Wrote: Yeah - toothing problems ... Android can do to your audio whatever it wants ... if audiotrack wants to mix, it mixes ...

Is 24bit/192Khz stereo files is outputing correctly on Nvidia shield Tv firmvare 5.1 through HDMI? Is anything changed on android 7 on nvidia shield TV using 24bit/192Khz stereo files playing with Kodi /SPMC?
Reply
#47
No. besides that it won't work - nothing. The best that can happen is: 192 / 16 bit. As for 192 khz no float / 32 bit int is available.

Your Debug Log will tell that.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#48
(2017-02-18, 17:16)fritsch Wrote: No. besides that it won't work - nothing. The best that can happen is: 192 / 16 bit. As for 192 khz no float / 32 bit int is available.
I don't think that is the case anymore. With update 5.x, Kodi 17 opens 96/192kHz float (2 channels) and the output is 24-bit (Channel Status Bits of HDMI output, PCM analysis). With the latest Kodi 17.1 RC, 88.2 and 176.4kHz are also supported. 44.1kHz is not supported. All these apply only for stereo audio. Multichannel PCM is still limited to 16-bit 48kHz.

http://pastebin.com/tMV5tcDE
Reply
#49
Nice - that should not happen :-)

Let me check my code on that.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#50
Jep - right - if we have 2 channels, we open Float: https://github.com/xbmc/xbmc/blob/master...K.cpp#L314

Do you want to test a build with multichannel?

Btw. internally we decode the flac to float32 bit and this we send. So good to see that Audiotrack "under the hood" chooses a wide enough format - I think it sends 32 bit int - as all linux do that. And while 24 bit int to 32 bit float to 24 bit int (tunneled in 32 bit with just padding zeros) all is fine.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#51
Building: http://jenkins.kodi.tv/job/Android-ARM/11007/
Will come here: http://mirrors.kodi.tv/test-builds/android/arm/ has flt in its name
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#52
(2017-02-18, 22:58)fritsch Wrote: Do you want to test a build with multichannel?
Sure! I am not sure whether AudioTrack actually supports multichannel Hi-Res output because it doesn't seem to work in the native players.
Reply
#53
From the documentation:

Quote:ENCODING_PCM_FLOAT: Introduced in API LOLLIPOP, this encoding specifies that the audio sample is a 32 bit IEEE single precision float. The sample can be manipulated as a Java float in a float array, though within a ByteBuffer it is stored in native endian byte order. The nominal range of ENCODING_PCM_FLOAT audio data is [-1.0, 1.0]. It is implementation dependent whether the positive maximum of 1.0 is included in the interval. Values outside of the nominal range are clamped before sending to the endpoint device. Beware that the handling of NaN is undefined; subnormals may be treated as zero; and infinities are generally clamped just like other values for AudioTrack – try to avoid infinities because they can easily generate a NaN.
To achieve higher audio bit depth than a signed 16 bit integer short, it is recommended to use ENCODING_PCM_FLOAT for audio capture, processing, and playback. Floats are efficiently manipulated by modern CPUs, have greater precision than 24 bit signed integers, and have greater dynamic range than 32 bit signed integers. AudioRecord as of API M and AudioTrack as of API LOLLIPOP support ENCODING_PCM_FLOAT.

^^ I don't read anything with stereo - curious.
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#54
We will find out soon Smile
Reply
#55
I think I change the code to try FLOAT always and when it can't open - I fall back to 16 bit Int ...
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#56
First build up: http://mirrors.kodi.tv/test-builds/andro...bi-v7a.apk
Second build with fallback is syncing: http://mirrors.kodi.tv/test-builds/andro...bi-v7a.apk (needs some minutes)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#57
It is a no go with the first build. Kodi opens 6 channels float, but the HDMI output is 16-bit 48kHz Stereo.
http://pastebin.com/iixv9ibu

I just downloaded the second one. Will give that a try.
Reply
#58
If kodi is able to open it - then nothing we can do - the rest happens "behind our back" as said above - it's a soundserver after all - it does what it wants :-)
First decide what functions / features you expect from a system. Then decide for the hardware. Don't waste your money on crap.
Reply
#59
I tried the second build also. Here is something interesting: when the track is played first, it is 16-bit 48kHz Stereo. If you stop the playback and then play it again the output is 192kHz 5.1 (24-bit as reported in the Channel Status Bits). But there is a problem, the system sounds in Kodi are distorted. It goes back to normal after you exit from Kodi.

http://pastebin.com/L9FZiFxz (lines 763--> and 866-->)
Reply
#60
I am very happy what I hear from you. Thanks Fritsch and Koying and all KODI team that you make Kodi so great even on os made just for ring tones Smile In the morning I will make my stereo louder. Wesk 05 thanks to you too for noticing that stereo 24/192 works in Kodi 17 on Shield tv version 5.x
Reply

Logout Mark Read Team Forum Stats Members Help
HD Audio (24bit / 192Khz) on NVidia Shield TV0