python:


command = ["/system/bin/am", "start --user 0 -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -e ROM "xxxx"]

subprocess.call(command, stdout = f, stderr = subprocess.STDOUT, close_fds = True)

(2018-07-05, 10:28)docwra Wrote: Does anyone have any problem with playing FLAC music files?

I'm getting some kind of clipping when playing the songs. MP3 is fine as is playing exactly the same FLAC on a windows machine with Kodi. Seems specific to the Shield(or android).

The song i see it most on is one called "NF - Dreams". I've uploaded a 30second sample here

Can anyone else help confirm the issue?

(2018-07-05, 10:46)knubbze Wrote:

(2018-07-05, 10:28)docwra Wrote: Does anyone have any problem with playing FLAC music files?

I'm getting some kind of clipping when playing the songs. MP3 is fine as is playing exactly the same FLAC on a windows machine with Kodi. Seems specific to the Shield(or android).

The song i see it most on is one called "NF - Dreams". I've uploaded a 30second sample here

Can anyone else help confirm the issue?

Which player are you using?    

(2018-07-06, 15:50)DeejayT Wrote: I have a shield tv lately. Can anyone tell me which are the best settings under kodi and the shield itself to get the best possible quality (audio & video)
Or is there a post/page where I can find it.
thanks

(2018-05-24, 17:55)gilsonsjc Wrote: It is not at this moment - you have to register yourself as a Shield Preview Program member to get it

(2018-06-18, 02:27)wesk05 Wrote: Now that nVIDIA has provided the recovery image download for 7.0.1 update, I updated one of my Shields that has an open bootloader. I did a quick testing of the new gamut mapping API in Android Oreo. It is different from SE 6.3 update especially at 100% saturation levels. The mapped values all seem to lie within Rec. 709 boundaries (In SE 6.3, the 100% points were close to BT.2020 boundaries). With that said, I got some mixed results. While the theoretically calculated CIE 1931 points were very close to the reference Rec.709 points, the results were different when checked on a CIE scope. CIE scope display showed a desaturated image with 7.0.1 update. The desaturation is very obvious in the frame grab. CIE 1931 Chromaticity Chart

Pink diamond: reference Rec.709, Filled circle: Shield Experience 6.3 update, Filled square: Shield Experience 7.0.1 update. Black triangles represent the boundaries for BT.709 and BT.2020 gamuts (smaller one is BT.709).

The tests were done on two different Shield Android TVs, one with 6.3 update and the other with the 7.0.1 update. The test patterns were classic color checker and 100% saturation/stimulus test pattern of primaries and secondaries. The test patterns were played in the latest Kodi Leia alpha build. Shield's output was set to 4K 23.976Hz 12-bit Rec.2020. The code values of the output signal were read of a HDMI analyzer. XYZ and xy calculations were based on ITU-R BT.2020 and BT.709 recommendations.

EDIT 6/17/18
I have removed the CIE scope captures that I posted earlier because I suspect something weird going on with the waveform monitor when the primaries are set to BT.2020.

At this time, I am just going to go ahead and say that the new colorspace API does a good job rendering BT.709 gamut to BT.2020 gamut. It is doing an "absolute" or "saturation" rendering. This is as good as it can get! By making this bold statement, I hope I won't have to eat my hat. 

(2018-07-16, 12:44)cable_guy Wrote: How would you tell Kodi to not use the hardware it's on (the Shield) to upscale, and leave it to the TV though?

(2018-07-16, 12:50)noggin Wrote:

(2018-07-16, 12:44)cable_guy Wrote: How would you tell Kodi to not use the hardware it's on (the Shield) to upscale, and leave it to the TV though?

 Whitelisting has appeared in Kodi Leia builds.  This allows you to select which resolutions and frame rates Kodi will use. If you select 720p and 1080p modes at the frame rates you want - then 720p will be output in 720p, 1080p in 1080p and 2160p at 2160p, leaving your UHD TV to do 720p and 1080p to 2160p upscaling, not Kodi.

NB the approach Kodi devs have taken to whitelisting isn't 100% popular (it's reduce the ease of config of auto refresh rate switching) - and so I wouldn't be surprised if a change to the configuration of the functionality took place, however I expect the functionality itself is likely to continue.