[phate89]

Excluding the fact they have VERY good reasons to not give any kind of timing when you asked about the status there was no work in ffmpeg for this feature and nothing planned. If I understood well this decoder is developed from an independent developer and not from ffmpeg itself. Also the first time the decoder code was published is AFTER your last request so they would've needed a crystal ball to answer it.
it's curious that the first time the developer posted its decoder code in github happened less than a day after the last reply on this thread...

You can exclude your opinion all you like, but putting forward a general ballpark timeline is done all the time rather than just "in the future" which means jack squat.

It's not an opinion. It's a fact that they have very good reasons to not say anything.
This is not a regular software you buy. All the people that works in Kodi or ffmpeg didn't do it for work or for money. So it doesn't matter how big, easy and close a feature is. To happen you need someone that actually want to work to it and care about the feature (and none of the devs here said something about them working on it), this person needs to find the time to do it cutting it from it's real life time. Then when it finished other people have to look at it and check if everything is okay and then they can merge it. After that it's still not finished because there are other features that needs to be added or fix for other bugs to wait for the stable release.
Can you predict other people's work timings in their free time? Can you predict that someone with the right skills will want to do it? I can't.
Your posts actually prove that they better not answer about when a feature will be available. You read something that made you think the feature was close and you're here complaining because it's not and it might take time to have it...

[Batiatus]

It's not an opinion. It's a fact that they have very good reasons to not say anything.
This is not a regular software you buy. All the people that works in Kodi or ffmpeg didn't do it for work or for money. So it doesn't matter how big, easy and close a feature is. To happen you need someone that actually want to work to it and care about the feature (and none of the devs here said something about them working on it), this person needs to find the time to do it cutting it from it's real life time. Then when it finished other people have to look at it and check if everything is okay and then they can merge it. After that it's still not finished because there are other features that needs to be added or fix for other bugs to wait for the stable release.
Can you predict other people's work timings in their free time? Can you predict that someone with the right skills will want to do it? I can't.
Your posts actually prove that they better not answer about when a feature will be available. You read something that made you think the feature was close and you're here complaining because it's not and it might take time to have it...

You can keep shouting your opinion as fact and keep this thread off topic but it still doesn't change my point. And there's no need to lecture anyone about who does what to produce Kodi. None of that is lost.

I will say that, as a development team, we'd have general timelines for what we are working on. Doesn't mean a hard and fast release date. Far less off-topic discussion would pollute threads if a ballpark hopeful timeline is given rather than having this useless discussion go on over and over. All my points still stand. There's no simplified place to learn about work being done on future releases, updates to threads such as these give little or hopefully but misrepresented information and notes about "in the future". Free program or not, it's just bad form.

I'm hear hoping that info saying "it's finished" means it's actually close, not needing to ask and ask again and ask some more to actually understand what "it's finished" really means. My posts prove my points correct as this thread has gone way off topic just to get the answers that were requested at the begining. If you don't have an actual timeline it's better to say nothing at all but that's not what happens.

Anyways, dtsHD being proper in Kodi won't happen for a year or more. Shitty but such is life.

[da-anda]

I'm sorry to disapoint you, but our "team" is only a bunch of random devs doing what they feel like. Getting team status/membership is mostly only sign of gratitude for their work on Kodi so far. So there is no overall masterplan for Kodi, no list of features we want to get into a certain release, nothing. There are only devs working on X and Y if they are interested in it, and once there is a PR and it has been reviewed it'll be merged. We can only tell for existing PRs if there is a chance to make it into a release or not, but nothing more. We're no company with a business plan for the product, and we don't have X hours of dev man power to plan with. And while some of the team would like to handle things more professional (in a corporate way) others are opposed to it because Kodi is only a fun project to them and having to deal with the same business bullshit as in their jobs is nothing they want to do in their spare time. And we can't force a dev working for fun in his sparetime to work on a feature he's not interested in. If we'd be more corporate like Mozilla with payed devs, this would work, but not as it is right now.

[FernetMenta]

Somehow I feel with @Batiatus about all that useless words written in this thread here. I, as the main developer of this (at least I have done this in the past) have given a clear view on this: It will be in the upcoming release of ffmpeg and once this has been release we upgrade our fork. If all this useless and countless words did not distract this thread from its actual topic, one could have asked: "when would you expect this to happen?". I would have answered as jjd-uk already did: we intend to release Kodi v15 in July (already slipped because of some critical errors). At this time I also expect ffmpeg 2.7 to be released. So we start v16 with ffmpeg 2.7 from that point in time

[mikeSiLVO]

Ok... Deleted.
Thought I was being helpful to a question posted wether it was on topic or not. Thought topics might change or evolve with the flow of the thread but I apologize for adding to the off topicness.

[FernetMenta]

that was one of the useless off-topic comments I was referring to

[kikassridec2]

my av receiver detects dts-hd ma 7.1 audio stream/track when playing but on movie scrolling (transparency skin) shows only as 5.1,

i know it is only a small gripe but sure is annoying... so really hope this gets fixed in v.16.

[VonMagnum]

I just tested Kodi Jarvis Beta 3 and DTS-HD now correctly detects/displays as DTS-HD MA 7.1 when selecting the Audio in the Audio sub-menu while the movie is playing. That's great! However, the on-screen menu still says 5.1 so I'm assuming something wasn't changed and/or set right there relative to the newer ffmpeg library.

I also tested a couple of DTS-ES (6.1) movies (i.e. Gladiator and The Haunting). Here, the on-screen menu now correctly shows 6.1, but the audio sub-menu selection screen says "DTS 7 Channels" which is correct (6.1 IS 7 channels of information, after all), but it would be cool if they matched given 7.1 says "7.1" and not "8 channels" by comparison. The onscreen menu also shows a special logo for DTS Master Audio versus regular (or core) DTS. It would also be cool if it showed DTS-ES for 6.1 like the official movies show on the box (again just for continuity/consistency).

Other observations regarding file recognition and labeling detection and consistency:

- I've noticed WAV files show up with a "PCM Audio" logo but AIF/AIFF have no logo at all (FLAC, Apple Lossless, OGG, MP3, etc. all have logos)

- DTS Music is detected in WAV format, but it doesn't recognize it if it's AIF/AIFF (which is also uncompressed lossless and unlike WAV supports tagging) or Apple Lossless (compressed lossless) or even FLAC. It would be nice to be able to compress and tag DTS Music with Kodi.

[VonMagnum]

Has anyone noticed that Handbrake's Passthrough for DTS-HD 7.1 shows up as "DTS 2-Channel" in Subler? I've had Jarvis show these as 2-channel after the first play and I can't help but wonder if Handbrake is setting something incorrectly in terms of how it's detected. I found if I don't encode the DTS Passthrough with Handbrake, but add it afterwards with Subler from the MakeMKV .MKV file, then Subler shows 7.1 channels correctly and I think Jarvis does as well. Isengard, however, always shows them as DTS 5.1 channel, but that's still better than showing it as 2-channel since Kodi will automatically pick Dolby 5.1 over DTS if it thinks DTS is only 2-channel (when it's actually 7.1 DTS-HD Master Audio).

The easiest fix I could find would be to delete the DTS track with subler and "optimize" to reclaim the space and then re-add it from the MakeMKV file (I'd have to re-rip if I deleted it prior) with Subler instead so it shows up correctly. I don't know if this is related to changes in FFMPEG or something else (most older programs don't see 7.1 as 7.1 to begin with; MP4Tools shows 6.1 channel as 7-channels (correct), but it sees 7.1 DTS-HD MA as 5.1 DTS. Subler sees them correctly as long as it does it and not Handbrake.

Edit: I did a Fresh Install of Jarvis Beta 4 on my Mac (renamed the old Kodi data folders to test it fresh rather than "upgrade") and it detected all 7.1 Master Audio correctly and 6.1 DTS-ES correctly (save 7.1 shows as "5.1" on the on-screen display, but shows correctly in the Audio selection panel and the database listing). I don't know why I was getting "2-channel" before unless it was either an upgrade issue or only a problem on the ARM version (for my Amazon Fire TV Sticks). I tried a fresh install there the other day and kept showing up as 2-channel for DTS for some reason (kind of like how Subler shows the Handbrake passthroughs). I tried a corrected Subler version where Subler says "8 channels for 7.1 DTS) and one where it says 2-channel DTS and Kodi showed 7.1 in both cases on the clean install, but had issues on the FireTV version for some reason.

Now if only I had a simple way to convert DTS 7.1 HD-Master Audio to Dolby Digital Plus 7.1 to save space and be compatible with the new ATV4. From the feature request area, I gather Handbrake will eventually add it, but it could be some time. TrueHD to Plus would probably be more helpful yet since there doesn't seem to be a way to store TrueHD in a M4V file yet (like DTS) and thus no ATV compatible 7.1 setup like you can do for DTS (i.e. Kodi reads DTS in the M4V but iTunes just ignores it and uses Dolby Digital instead).

[dbldown768]

I just decided to upgrade my system and add 2 more speakers for 7.1. I started to wonder if my media was stored correctly. Like others have mentioned, the media info shows 7.1 dts-ma along with core for movies. When i show the onscreen overlay, it shows 5.1(side), so i was concerned that something was not setup correctly. I do have passthrough enabled for kodi and my receiver's on screen display seems to think that 7.1 input and output is configured. If I understand correctly, kodi should be passing through the audio correctly to my receiver, but just not displaying correctly on the overlay? Is that true?

Below are a few logs that might be useful. It shows my hardware is capable of dts-ma

Code:

18:25:51 T:140032792700800  NOTICE:     Device 1
18:25:51 T:140032792700800  NOTICE:         m_deviceName      : hdmi:CARD=HDMI,DEV=0
18:25:51 T:140032792700800  NOTICE:         m_displayName     : HDA Intel
18:25:51 T:140032792700800  NOTICE:         m_displayNameExtra: ONK TX-NR616 on HDMI
18:25:51 T:140032792700800  NOTICE:         m_deviceType      : AE_DEVTYPE_HDMI
18:25:51 T:140032792700800  NOTICE:         m_channels        : FL,FR,LFE,FC,BL,BR,BLOC,BROC
18:25:51 T:140032792700800  NOTICE:         m_sampleRates     : 32000,44100,48000,88200,96000,176400,192000
18:25:51 T:140032792700800  NOTICE:         m_dataFormats     : AE_FMT_LPCM,AE_FMT_AC3,AE_FMT_DTS,AE_FMT_EAC3,AE_FMT_DTSHD,AE_FMT_TRUEHD,AE_FMT_S32NE,AE_FMT
_S16NE,AE_FMT_S16LE,AE_FMT_AAC
18:25:51 T:140032792700800  NOTICE:     Device 2
18:25:51 T:140032792700800  NOTICE:         m_deviceName      : hdmi:CARD=HDMI,DEV=1
18:25:51 T:140032792700800  NOTICE:         m_displayName     : HDA Intel
18:25:51 T:140032792700800  NOTICE:         m_displayNameExtra: HDMI
18:25:51 T:140032792700800  NOTICE:         m_deviceType      : AE_DEVTYPE_HDMI
18:25:51 T:140032792700800  NOTICE:         m_channels        : FL,FR,LFE,FC,BC,BL,BR,FLOC,FROC,BLOC,BROC,TFC,TC,TFL,TFR,UNKNOWN1
18:25:51 T:140032792700800  NOTICE:         m_sampleRates     : 32000,44100,48000,88200,96000,176400,192000
18:25:51 T:140032792700800  NOTICE:         m_dataFormats     : AE_FMT_S32NE,AE_FMT_S16NE,AE_FMT_S16LE,AE_FMT_LPCM,AE_FMT_DTSHD,AE_FMT_TRUEHD,AE_FMT_EAC3,AE
_FMT_DTS,AE_FMT_AC3,AE_FMT_AAC


18:30:22 T:140030328682240    INFO: ffmpeg[7F5B59FFB700]: [dca] Number of channels changed in DCA decoder (8 -> 6)

18:30:22 T:140030328682240   DEBUG: FactoryCodec - Audio: passthrough - Opened
18:30:22 T:140030328682240  NOTICE: Creating audio thread
18:30:22 T:140030170625792   DEBUG: CDVDPlayerVideo - CDVDMsg::GENERAL_SYNCHRONIZE
18:30:22 T:140030162233088  NOTICE: Thread DVDPlayerAudio start, auto delete: false
18:30:22 T:140030162233088  NOTICE: running thread: CDVDPlayerAudio::Process()
18:30:22 T:140030162233088   DEBUG: CDVDPlayerAudio - CDVDMsg::GENERAL_SYNCHRONIZE
18:30:22 T:140030328682240   DEBUG: OnPlayBackStarted: play state was 1, starting 1
18:30:22 T:140030328682240   DEBUG: CDVDPlayer::SetCaching - caching state 3
18:30:22 T:140032792700800   DEBUG: PlayFile: OpenFile succeed, play state 2
18:30:22 T:140030162233088    INFO: CAEStreamInfo::SyncDTS - dtsHD stream detected (8 channels, 48000Hz, 16bit BE, period: 8192)
18:30:22 T:140032792700800   DEBUG: OnPlayBackStarted: play state was 2, starting 0
18:30:22 T:140030170625792   DEBUG: CDVDPlayerVideo - CDVDMsg::GENERAL_RESYNC(83000.000000, 0)
18:30:22 T:140030170625792    INFO: CDVDPlayerVideo - Stillframe left, switching to normal playback
18:30:22 T:140032792700800   DEBUG: ------ Window Init (VideoOverlay.xml) ------
18:30:22 T:140032792700800    INFO: Loading skin file: VideoOverlay.xml, load type: KEEP_IN_MEMORY
18:30:22 T:140030162233088  NOTICE: Creating audio stream (codec id: 86020, channels: 8, sample rate: 192000, pass-through)

[VonMagnum]

As near as I can tell, they simply didn't update the on-screen display code to correctly show "7.1" in the new betas. Only god knows if they will bother to fix it any time soon since they usually ignore all feedback on the matter and I see no public area to report bugs on the betas anyway. Honestly, I don't care anymore since it's a waste of my time even bothering to report issues they don't read or care about (unless you code the solution yourself). Kodi is for the developers. The only support you will likely get on here are from other users for the most part (I mean you can see that you're the first person to respond beside myself here for a long time).

[dbldown768]

Well as a developer by day I understand they might have a priority of tickets. What seems like an easy fix to us might take more time than we would expect.

I guess I was just really looking for verification my stuff is working properly. I am assuming yes based on the conversation. I appreciate your reply. The on screen information does leave some open questions. All in all, I really like the product and have had pretty good feedback from users on this forum for help.

[VonMagnum]

Well as a developer by day I understand they might have a priority of tickets. What seems like an easy fix to us might take more time than we would expect.

I guess I was just really looking for verification my stuff is working properly. I am assuming yes based on the conversation. I appreciate your reply. The on screen information does leave some open questions. All in all, I really like the product and have had pretty good feedback from users on this forum for help.

You could try some of these (uncompressed 7.1 DTS-HD MA trailers/channel checks will do the trick): http://www.demo-world.eu/2d-demo-trailers-hd/

I don't expect them to address everything instantly, but it would be nice if they would at least acknowledge they've read about a given bug/issue and/or have a master list of known bugs somewhere or something. Posting a bug report to be ignored isn't my favorite hobby and sadly it's par for the course here. Whine enough and they'll hit you with the famous "we're waiting for your fix" type crap. Personally, I'd rather pay for this software if that would mean better support and more pleasant conversations with developers. There aren't a lot of media player options for "roll your own" out there so you either deal or convert everything to M4V or whatever for an AppleTV.

[furii]

devs are working on rewriting, completely, the videoplayer, implementing binary addons, built-in emulator support, among countless other things. but yeah, support here is shite because it says 5.1 instead of 7.1...

[FernetMenta]

Displays correctly here but I don't use passthrough audio