[Batiatus]

Next release of ffmpeg has support for DTS-HD MA. Means it will be in Kodi 16

So what's this timeline? And does this "support" address the current problem of 7.1 being recognized by Kodi as 5.1?

Trying to determine just how much of my library I need to fix now if I choose to manualy edit all the media to proper 8 channels through naming convention or if I should wait. Though the problem of nfo files reporting back only 6 channels needs to be corrected no matter what.

[jjd-uk]

There is now an open source decoder for DTS-HD available, so for the 1st time it's now possible to decode losslessly to 7.1 PCM. Since this requires the DTS-HD stream to be correctly parsed the issue of 7.1 content being flagged as 5.1 in the UI should be fixed.

Once Isengard is released, which should be soon, the decoder will be enabled in our builds of ffmpeg and then be available in the development builds for v16.

[Batiatus]

So it's still another year away....

[da-anda]

you can use a nightly from short after Isengard release and this PR merged. I only run on nightlies, because our codebase has become very stable, even with nightlies.

[Batiatus]

you can use a nightly from short after Isengard release and this PR merged. I only run on nightlies, because our codebase has become very stable, even with nightlies.

I'm using 15.0 Beta right now and have found a number of issues with playback controls, on screen displays and so on. Waiting for the full release of 15 to then start messing with new builds of 16 isn't something most users want nor care to do. They would like to know when issues will be resolved though. So seeing that ffmpeg seems to have figured this one issue out but it won't be brought forward to Kodi foranother 2 actual releases from now is a bit of a let down.

As it stands now I can't even easily find where the current discussion of the state of 15.0 is. Seems buried in some sub-sub forum thread. I'm not even sure where to go to ask those "in the know" if they are adding new and useful things to Kodi that have come up in the past year or so and will be coming down the line shortly.

[Martijn]

if you have issues with 15.0 just start a thread with clear descriptions and logs/screenshots. We don't a collection thread of it nor special section. If we know the issues we will tell you then. Most likely we don't know yet.
Always make sure you have the latest available nightly version installed. Waiting till 15 final version to start reporting stuff is too late. Always try with Confluence as we don't support others skins for issues.

If you want to try out the DX11 build for windows you can find that here
http://forum.kodi.tv/showthread.php?tid=218274
which will be merged for 16.0

[Batiatus]

if you have issues with 15.0 just start a thread with clear descriptions and logs/screenshots. We don't a collection thread of it nor special section. If we know the issues we will tell you then. Most likely we don't know yet.
Always make sure you have the latest available nightly version installed. Waiting till 15 final version to start reporting stuff is too late. Always try with Confluence as we don't support others skins for issues.

If you want to try out the DX11 build for windows you can find that here
http://forum.kodi.tv/showthread.php?tid=218274
which will be merged for 16.0

Which is exactly my point. If I've found something buggy or wondering about the progression there's no easy place to look things up. It's a mish-mash of stuff all over the place. Random threads started but never contributed to. Threads in various different platform sub-forums. There isn't even a place to get updates from anyone to see what's new or being addressed. In other words, if you are curious you have to spend far more time than should be required to even just "read along".

Even the answers in this thread pertaining to the topic aren't very clear and give very broad statements with little to no tangible info until further provoked. And even still, if the resolution to this thread topic is out now, why will it take another full Kodi build to implement? See now I've had to ask 4 times to get any real tangible information,

I don't have time to make new threads every time I find a small hiccup, post screens and logs and so on. When I'm sitting and watching a movie and something F's up I'm not stopping my entertainment to pull logs and sort it all out. And then to search the entire forum to see if anyone else is having the same issues lest another thread already exist and re-posting the same question is met with "use the search feature" which is generally useless when threads are named in a million different ways. I'd like to contribute my findings and input when I have time, but as a community it's been made VERY difficult to do so. Having a new forum for the next build (not going 2, 3 or 4 builds into the future) where a general Q&A thread is maintained and questions or bugs can be posted, regardless of the system or hardware or whatever, would be much more beneficial to the community than me going into the Windows sub-forum to post my findings which will get lost among threads from people posting about Helix, Gotham and Frodo still.

[Martijn]

sure that would work if users/community would only post in the section/version they should post into. Fact is they don't and new users only post questions you first have to decrypt with a super computer.
then there's the lack of several hundred more developers and moderators for the forum to answer the question. We have many platforms and as such posts will be scattered although they may be common.
It would also mean creating sub forums for each Kodi versions.


So it is what it is. If you think it's not worth it reporting bugs that's totally up to you and understandable. But don't come back saying "i've noticed this month ago and never mentioned it". You'll have to give info to get anything fixed or even looked at. We don't have crystal balls.

About this thread, you got the reply way in the beginning that it was up to FFmpeg to finally start supporting it and only until very recently it didn't. Now we can only tell you it will likely be in next version but as always we don't give any end dates.

[FernetMenta]

ffmpeg has not even released a version that supports it. the pr mentioned is not intended to be merged with the ffmpeg changes. means the info given stating 'right after release' are not completely correct.

EDIT: depends on the definition of "short after" and the time v15 will be released.

[jjd-uk]

Well I assumed libdcadec would be in the next major point release as it's in master, and that should with us very soon since they've made a major point release a roughly every 3 months in recent times.

[Batiatus]

sure that would work if users/community would only post in the section/version they should post into. Fact is they don't and new users only post questions you first have to decrypt with a super computer.
then there's the lack of several hundred more developers and moderators for the forum to answer the question. We have many platforms and as such posts will be scattered although they may be common.
It would also mean creating sub forums for each Kodi versions.


So it is what it is. If you think it's not worth it reporting bugs that's totally up to you and understandable. But don't come back saying "i've noticed this month ago and never mentioned it". You'll have to give info to get anything fixed or even looked at. We don't have crystal balls.

About this thread, you got the reply way in the beginning that it was up to FFmpeg to finally start supporting it and only until very recently it didn't. Now we can only tell you it will likely be in next version but as always we don't give any end dates.

Not wanting to derail this thread further I'll just say that while you can't fix the stupidity of new/dumb users, I don't think having a new dedicated sub-forum for Q&A, reports and general discussion for each new in development version isn't something that requires hundreds of man hours to implement. Since the questions that do get posted in a million other places tend to find an answer, eventually, it would make life far simpler than any headache it may cause.

For this thread, I asked a long time ago something and then asked about more recent news. I asked if there was some sort of timeline and didn't really get an answer to that. Sometimes getting more than a "in the future" response is like pulling teeth around here and that gets frustrating. If the news came with more upfront information or if questions which I think are thought out enough to elicit more than a very basic and general response could be answered fully, the continued discussion and associated time wouldn't be so needed.

[Martijn]

For this thread, I asked a long time ago something and then asked about more recent news. I asked if there was some sort of timeline and didn't really get an answer to that. Sometimes getting more than a "in the future" response is like pulling teeth around here and that gets frustrating. If the news came with more upfront information or if questions which I think are thought out enough to elicit more than a very basic and general response could be answered fully, the continued discussion and associated time wouldn't be so needed.

Fact is we can't and won't give any timeline other than "somewhere in the future" until it's actually in our code base. If we say a month and it will be 5 then we get blamed for not keeping to our promise
Maybe not you but certainly some one else.

[Batiatus]

For this thread, I asked a long time ago something and then asked about more recent news. I asked if there was some sort of timeline and didn't really get an answer to that. Sometimes getting more than a "in the future" response is like pulling teeth around here and that gets frustrating. If the news came with more upfront information or if questions which I think are thought out enough to elicit more than a very basic and general response could be answered fully, the continued discussion and associated time wouldn't be so needed.

Fact is we can't and won't give any timeline other than "somewhere in the future" until it's actually in our code base. If we say a month and it will be 5 then we get blamed for not keeping to our promise
Maybe not you but certainly some one else.

You can give guidelines. My question could have been answered with more info on the addition of support to ffmpeg which unless users go searching elsewhere hasn't been posted, and how that will fall into the development cycle of Kodi. It could be stated that the target release for 15.0 is say, 2 months give or take and ffmpeg is still not yet released which will not give developers time to integrate it in. You can use generalities but still give some sort of an indication. If people backlash then it's their fault for reading more into general time frames (as I did thinking ffmpeg was up to date as of right now) but in general people have an understanding. Especially if they are interested in topics like these at hand. Being to opened ended can get you into just as much trouble, if not more. Everyone appreciates the work that goes into all this. Well most of us do. Those who don't can take a hike.

[phate89]

For this thread, I asked a long time ago something and then asked about more recent news. I asked if there was some sort of timeline and didn't really get an answer to that. Sometimes getting more than a "in the future" response is like pulling teeth around here and that gets frustrating. If the news came with more upfront information or if questions which I think are thought out enough to elicit more than a very basic and general response could be answered fully, the continued discussion and associated time wouldn't be so needed.

Fact is we can't and won't give any timeline other than "somewhere in the future" until it's actually in our code base. If we say a month and it will be 5 then we get blamed for not keeping to our promise
Maybe not you but certainly some one else.

You can give guidelines. My question could have been answered with more info on the addition of support to ffmpeg which unless users go searching elsewhere hasn't been posted, and how that will fall into the development cycle of Kodi. It could be stated that the target release for 15.0 is say, 2 months give or take and ffmpeg is still not yet released which will not give developers time to integrate it in. You can use generalities but still give some sort of an indication. If people backlash then it's their fault for reading more into general time frames (as I did thinking ffmpeg was up to date as of right now) but in general people have an understanding. Especially if they are interested in topics like these at hand. Being to opened ended can get you into just as much trouble, if not more. Everyone appreciates the work that goes into all this. Well most of us do. Those who don't can take a hike.

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...

[Batiatus]

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.

Second, It wasn't I who posted any information stating the code was (being) implemented by ffmpeg and would then be available in a future iteration of Kodi. The post quoted made it sound like the ffmpeg support was already there but bringing it into Kodi would take more than a year. The information posted was very minimal and asking follow up questions only provided very small bits of information rather than 1 post with a simple but concise answer. That's been my entire point. It's like saying "Hey kids, we're going to Disneyland" but not mentioning Disneyland still hasn't opened yet and you don't know when it will, and then you need to save the money to go, plan the travel, book the hotel and so on.