Release Audio Profiles (for Kodi 18 and later)
(2023-06-10, 07:45)pkscout Wrote:
(2023-06-10, 03:52)ashlar Wrote: So it seems that Kodi should be able to differentiate. Why it doesn't?

Audio Profiles uses a JSONRPC call to Kodi to get the audio stream details.  The specific call is Player.GetProperties, and the specific thing Audio Profiles asks for is the current audio stream, which returns a Player.Audio.Stream object.  In that object is a string for codec which returns one of the follow values from what I can tell:

'dtshd', 'truehd', 'ac3', 'eac3', 'dts', 'dca'

If you want Atmos returned as a valid value, you need to submit an issue to the Github repo at:

https://github.com/xbmc/xbmc

If the issue is worked and Atmos is added, then I can update the addon to differentiate Atmos.
Since you're a Kodi team member I ask you for confirmation about this.

I have investigated a little but I wish to stress I'm no coder, I'm no dev.

What I found is that there have been three recent commits to ffmpeg, about three weeks after 6.0 final release:

TrueHD - https://git.ffmpeg.org/gitweb/ffmpeg.git...91450c4e60
DD+ - https://git.ffmpeg.org/gitweb/ffmpeg.git...575e5c32f2
DTS:X - https://git.ffmpeg.org/gitweb/ffmpeg.git...ab39b5214e

With these, ffmpeg and ffprobe can provide the info I posted in my previous post.

Now, reading Omega Alpha's release notes, I notice the following:

Use upstream FFmpeg. This is a big achievement and allows easier FFmpeg updates in the future.

So I wonder, would an issue opened on Kodi's GitHub be meaningful or would it be shot down with the usual "we need to wait ffmpeg to implement this". I don't mean it in an ironic or sarcastic way, it's just that I know that things have always worked that way and I don't know if the recent Omega "using upstream FFmpeg" thing has changed that.

PS
And of course ffmpeg had to cut 6.0 a few days before they implemented this. But that is par for the course, Murphy at his finest, etc. Big Grin

PPS
It should go without saying (but I'm pedantic and I'll add it anyway) that implementing the above would allow for Kodi to provide a surefire way to display Atmos and DTS:X labels in skins, without relying on file naming.
For troubleshooting and bug reporting please make sure you read this first (usually it's enough to follow instructions in the second post).
Reply


Messages In This Thread
RE: Audio Profiles (for Kodi 18 and later) - by ashlar - 2023-06-10, 12:49
Logout Mark Read Team Forum Stats Members Help
Audio Profiles (for Kodi 18 and later)0