Not detecting Lossless audio

I have 4k rip direct from makemkv. The audio is dts-HD MA but the vero4k+ GUI shows it as only dts and that’s what is output. If I select audio settings on the GUI it show English - Surround 5.1 - 0 Channels - 6 Channels.

This would normally say DTS-HD MA 5.1(SIDE)

Running mediainfo on the file gives the following audio info:

Audio
ID                                       : 2
ID in the original source medium         : 4352 (0x1100)
Format                                   : DTS XLL
Format/Info                              : Digital Theater Systems
Commercial name                          : DTS-HD Master Audio
Codec ID                                 : A_DTS
Duration                                 : 1 h 41 min
Bit rate mode                            : Variable
Bit rate                                 : 3 816 kb/s
Channel(s)                               : 6 channels
Channel layout                           : C L R Ls Rs LFE
Sampling rate                            : 48.0 kHz
Frame rate                               : 93.750 FPS (512 SPF)
Bit depth                                : 24 bits
Compression mode                         : Lossless
Delay relative to video                  : 6 s 6 ms
Stream size                              : 2.71 GiB (6%)
Title                                    : Surround 5.1
Language                                 : English
Default                                  : Yes
Forced                                   : No
Original source medium                   : Blu-ray

Any suggestions? I’ve never had any problems like this before.
Thanks

Do you mean you used to be able to get DTS-MA? When did the problem start? Debug logs would help enormously.

Every other dts-HD MA file I have shows correctly on the GUI and is displayed on my amp. The vero seems to think this one is dts. It’s a new 4k disc so I haven’t had this one working correctly.

So it’s unique to this file. Are you able to see a DTS-MA track in the OSD Audio settings while playing the file?

That’s right. I only ripped that one audio track. The vero thinks it’s dts. If I select audio settings on the GUI it show English - Surround 5.1 - 0 Channels - 6 Channels.

This would normally say DTS-HD MA 5.1(SIDE)

Well, post debug logs and we might get some more insight.

https://paste.osmc.tv/ruyanilire

Thanks for looking

The log suggests you ripped the wrong audio track

2024-09-14 08:19:35.801 T:3148     info <general>: ffmpeg[0xb3377da0]:   Stream #0:1(eng): Audio: dts, 48000 Hz, 6 channels (default)

As you say it would/should be something like this

2024-09-14 10:46:49.120 T:12686    info <general>: ffmpeg[0xb3368a08]:   Stream #0:1(eng): Audio: dts (DTS-HD MA), 48000 Hz, 5.1(side), s32p (24 bit) (default)

Why (Kodi’s) ffmpeg would be getting a different reading from mediainfo I’ve no idea. If you install an up-to-date version of ffmpeg and run ffprobe on that file do you get a different result from what’s reported in Kodi?

We’re also wondering about that ‘Delay relative to video’ entry. Sounds odd but I wouldn’t know how to deal with it.

I think there must be something off about the audio track. I also ripped it as FLAC but the sync is way out (and strangely smaller filesize). I’ll just stick with the lossy for now.

Did you check the contents of the makemkv rip to MKV with MKVToolNix ?

By the way, which 4K UHD is it ?

Chris

It’s The Crow (1994). I did look at it in MKVToolnix in the hope that there was a flag I could enable but no such luck.

1 Like

Would you be able to point me in the direction of updating ffmpeg. I’ve not done that before.

I’m not suggesting you update the ffmpeg that comes with Kodi. That one is specific to Kodi but is behind the bleeding edge ffmpeg. I just wondered if a more recent ffmpeg would report something different. If so, it could be something Team Kodi could look into. But if you don’t have that on a PC, say, it’s not worth the bother.

This is looking like the answer is to redo the rip rather than anything that can be fixed in OSMC.

I’ve tried a few rips. Even gave the disc a clean!
ok I have this version of ffmpeg on my laptop:
7:4.4.2-0ubuntu0.22.04.1
I ran the audio through ffprobe and the result is:

Input #0, matroska,webm, from 'The Crow (Remastered).mka':
  Metadata:
    title           : The Crow (Remastered)
    encoder         : libebml v1.4.5 + libmatroska v1.7.1
    creation_time   : 2024-09-16T18:35:34.000000Z
  Duration: 01:41:49.77, start: 6.005991, bitrate: 3818 kb/s
  Chapters:
    Chapter #0:0: start 0.000000, end 273.940333
**snip**
  Stream #0:0(eng): Audio: dts (DTS-HD MA), 48000 Hz, 5.1(side), s32p (24 bit) (default)
    Metadata:
      title           : Surround 5.1
      BPS             : 3815905
      DURATION        : 01:41:49.770345504
      NUMBER_OF_FRAMES: 572791
      NUMBER_OF_BYTES : 2914288300
      SOURCE_ID       : 001100
      _STATISTICS_WRITING_APP: mkvmerge v87.0 ('Black as the Sky') 64-bit
      _STATISTICS_WRITING_DATE_UTC: 2024-09-16 18:35:34
      _STATISTICS_TAGS: BPS DURATION NUMBER_OF_FRAMES NUMBER_OF_BYTES SOURCE_ID


Does this help at all?

Not really. You want to know what ffprobe reports when analysing the whole rip, not just the audio track. If it’s a big file, just post the audio part, we don’t need to see all the Chapter stuff.

When ffmpeg (in Kodi) reads a file, it only reads so much. I’m wondering whether that 6 second delay on the audio track means ffmpeg is not finding it. Struggling with the maths and I don’t know if that read buffer size can be adjusted easily.

Did you try another (older) version of makemkv ?

makemkv has been known to mess up audio/video streams in the past.

I’ve updated the post with the full audio track.

I’ve never come across that before. I’m currently trying 1.17.3 to see if that makes a difference.

Update: No it didn’t

OK so ffmpeg 7 gets it right while 6 (shipped with Kodi) does not.

You could take this up with Kodi but I’m guessing they will say they’ve moved on and won’t want to spend time fixing a Version 21/FFmpeg 6.0.1 corner case.

Unless someone else reading this has any ideas …

1 Like

It will likely have to wait for the next version of Kodi (Kodi v22).
I can’t see Kodi doing a major ffmpeg bump for a point release.