[Martijn]

Any way to get a file from Jarvis for long press to work for context menu for kodi 15.2? Is there a key map file in Jarvis that makes this work? Thank you

No

[Tinwarble]

No idea to your audio question. My crystal balls cannot see your Debug Log.

I was half joking, since I've brought this up multiple times before (along with debug logs). And I know (sort of) what is causing it, which is the "hack" (not my word) used in Kodi for pass-through.

Here's your ffprobe output:

Code:

libavutil      55.  5.100 / 55.  5.100
  libavcodec     57. 13.102 / 57. 13.102
  libavformat    57. 13.100 / 57. 13.100
  libavdevice    57.  0.100 / 57.  0.100
  libavfilter     6. 14.101 /  6. 14.101
  libswscale      4.  0.100 /  4.  0.100
  libswresample   2.  0.100 /  2.  0.100
  libpostproc    54.  0.100 / 54.  0.100
Input #0, matroska,webm, from 'Cwcm.mkv':
  Metadata:
    encoder         : libmkv 0.6.5
  Duration: 01:29:53.41, start: 0.000000, bitrate: 5737 kb/s
    Chapter #0:0: start 0.000000, end 287.396722
    Metadata:
      title           : Chapter 1
    Chapter #0:1: start 287.396722, end 536.606844
    Metadata:
      title           : Chapter 2
    Chapter #0:2: start 536.606844, end 873.193100
    Metadata:
      title           : Chapter 3
    Chapter #0:3: start 873.193100, end 1230.258144
    Metadata:
      title           : Chapter 4
    Chapter #0:4: start 1230.258144, end 1465.576556
    Metadata:
      title           : Chapter 5
    Chapter #0:5: start 1465.576556, end 1843.203811
    Metadata:
      title           : Chapter 6
    Chapter #0:6: start 1843.203811, end 2189.633222
    Metadata:
      title           : Chapter 7
    Chapter #0:7: start 2189.633222, end 2570.138344
    Metadata:
      title           : Chapter 8
    Chapter #0:8: start 2570.138344, end 2796.823144
    Metadata:
      title           : Chapter 9
    Chapter #0:9: start 2796.823144, end 3163.856478
    Metadata:
      title           : Chapter 10
    Chapter #0:10: start 3163.856478, end 3307.458267
    Metadata:
      title           : Chapter 11
    Chapter #0:11: start 3307.458267, end 3642.793267
    Metadata:
      title           : Chapter 12
    Chapter #0:12: start 3642.793267, end 3943.426933
    Metadata:
      title           : Chapter 13
    Chapter #0:13: start 3943.426933, end 4383.783511
    Metadata:
      title           : Chapter 14
    Chapter #0:14: start 4383.783511, end 4665.398178
    Metadata:
      title           : Chapter 15
    Chapter #0:15: start 4665.398178, end 5393.409000
    Metadata:
      title           : Chapter 16
    Stream #0:0(eng): Video: h264 (High), yuv420p(tv, bt709), 1920x816 [SAR 1:1
DAR 40:17], 30 fps, 30 tbr, 1k tbn, 180k tbc (default)
    Stream #0:1(eng): Audio: dts (DTS), 48000 Hz, 5.1(side), fltp, 1536 kb/s (de
fault)

[fritsch]

Stream #0:0(eng): Video: h264 (High), yuv420p(tv, bt709), 1920x816 [SAR 1:1
DAR 40:17], 30 fps, 30 tbr, 1k tbn, 180k tbc (default)

^^ does this feel correct?

[fritsch]

I was half joking, since I've brought this up multiple times before (along with debug logs). And I know (sort of) what is causing it, which is the "hack" (not my word) used in Kodi for pass-through.

You speak for android? The rest of the platforms is not "hacked".

[Nekromantik]

Something must have changed as this was working fine before.
On SATV at least.

[Tinwarble]

Stream #0:0(eng): Video: h264 (High), yuv420p(tv, bt709), 1920x816 [SAR 1:1
DAR 40:17], 30 fps, 30 tbr, 1k tbn, 180k tbc (default)

^^ does this feel correct?

No, since Kodi switches to 24p 7 secs into playback.

Now, I'm more than happy to supply any of you guys with anything you need that may help to further along development or fix bugs, as long as I'm capable. But I will say this again........I Don't Care about this. It doesn't affect me in the least and my only part in this was to explain to someone else why they were having an issue, which I think has been done well enough. And as I said, and have said for several years, to anyone using HB to make sure to always tick the "Constant framerate" when encoding.

I was half joking, since I've brought this up multiple times before (along with debug logs). And I know (sort of) what is causing it, which is the "hack" (not my word) used in Kodi for pass-through.

You speak for android? The rest of the platforms is not "hacked".

Yes, I was speaking specifically about Android (or did I wonder into another part of the forum again ).
And "hacked" is what Koying used to describe it.

[fritsch]

The video is 30 fps? That's not really possible for a bluray ... therefore I said: it's wrong from the start.

[Tinwarble]

No, the original BD is 23.976 (as far as I can remember). That's what it was when I ripped it, then when I encoded the mkv using HB I used "Same as source" and "Variable framerate" (default) was ticked.

[Koying]

And "hacked" is what Koying used to describe it.

Apparently, passing IEC61937 passthrough frames to audio moved from "hack" to "undocumented feature" since lollipop.
All the lollipop devices I checked seems fine with it, at least for AC3/DTS.

We must have Kodi fans at Google

[fritsch]

No, the original BD is 23.976. That's what it was when I ripped it, then when I encoded the mkv using HB I used "Same as source" and "Variable framerate" (default) was ticked.

So - you have a file that tells us 30 fps, we switch to 60 hz. I don't see what we are doing wrong? If the file is not 30 fps but the container / whatever tells it is - then there is a bug in the software that is writing this file.

[Koying]

No, the original BD is 23.976. That's what it was when I ripped it, then when I encoded the mkv using HB I used "Same as source" and "Variable framerate" (default) was ticked.

Can we just say that ticking "Variable framerate" in Handbrake is not good, can lead to oddities when using refresh rate syncing and move one, please. This leads nowhere.

[fritsch]

He should file the bug with Handbrake people ... as the container even confuses ffprobe :-)

[Tinwarble]

[So - you have a file that tells us 30 fps, we switch to 60 hz. I don't see what we are doing wrong? If the file is not 30 fps but the container / whatever tells it is - then there is a bug in the software that is writing this file.

Except I have a file that should be 24p (according to HB), that Kodi says is 30fps for only 7 secs and stays at 60Hz then switches 7 secs in and plays the rest of the file at 24Hz.

So either only the first 7 secs of the file is 30 fps (which I'm not saying isn't out of the realm of possibilities) or something else is going on.

But I'm done.........I've already said twice that I didn't care about this.

Can we just say that ticking "Variable framerate" in Handbrake is not good, can lead to oddities when using refresh rate syncing and move one, please. This leads nowhere.

Maybe my mind is going, but didn't I already say that at least a couple of times already.

[Tinwarble]

And "hacked" is what Koying used to describe it.

Apparently, passing IEC61937 passthrough frames to audio moved from "hack" to "undocumented feature" since lollipop.
All the lollipop devices I checked seems fine with it, at least for AC3/DTS.

We must have Kodi fans at Google

It's not the device, it's the AVRs. Mine and apparently a few others have AVRs that don't agree with getting DD/DTS packed in 2 channel.

EDIT: And just to say, it's not that the AVR can't play the audio, it just doesn't know what to do with it and will not change decode modes by it's self. Unlike when using the Video Player, which except for getting a pop at the beginning, doesn't cause my AVR to freak out an think it's getting PCM.

But I'm not sure what the difference is between Kodi and some other apps, like the built in Video Player on the SATV since I don't have the same issue of getting static with those.

[fritsch]

And "hacked" is what Koying used to describe it.

Apparently, passing IEC61937 passthrough frames to audio moved from "hack" to "undocumented feature" since lollipop.
All the lollipop devices I checked seems fine with it, at least for AC3/DTS.

We must have Kodi fans at Google

It's not the device, it's the AVRs. Mine and apparently a few others have AVRs that don't agree with getting DD/DTS packed in 2 channel.

But I'm not sure what the difference is between Kodi and some other apps, like the built in Video Player on the SATV since I don't have the same issue of getting static with those.

What (!) - this is completely bullshit ... just plug in your windows computer to the AVR and you will see that DD / DTS will work. You are aware that DTS/AC3 must work over spdif, too and that there are only 2 pcm channels are available?