[jogal]

Just a quick note to mention I tested TrueHD in current master at 279cedb314105b47e4baf5dc03a6fb7fb4eb55de (almost Alpha 3) and no dropouts found.

Tested all trouble scenes of Rogue One, Uncharted, Hellboy, Free Guy, Black Adam and others...

There is no evidence that v21 Alpha 3 can do worse than v20.1 or v20.2 in this regard (TrueHD drop-outs or frame skip).

This is on Shield 2019 latest firmware 9.1.1 + HotFix (future 9.2.0 when released).

[Nuklear92]

Just a quick note to mention I tested TrueHD in current master at 279cedb314105b47e4baf5dc03a6fb7fb4eb55de (almost Alpha 3) and no dropouts found.

Tested all trouble scenes of Rogue One, Uncharted, Hellboy, Free Guy, Black Adam and others...

There is no evidence that v21 Alpha 3 can do worse than v20.1 or v20.2 in this regard (TrueHD drop-outs or frame skip).

This is on Shield 2019 latest firmware 9.1.1 + HotFix (future 9.2.0 when released).

I was about to say the same, currently using the very latest nightly build that came out today Sept, 7th. Watched a TrueHD video of 25 minutes and didn’t had a single audio dropout or frame skips. I’ll keep testing more, so far very stable. Hoping to stay that way 👍

Thanks for the continued improvements! 💙

[HomerJau]

Just a quick note to mention I tested TrueHD in current master

The recent issues are only with Atmos JOC (Dolby Digital Plus) not TrueHD based on my two LibreElec NUCs. All LE 12 Alpha builds after August 21 have Atmos JOC audio skips at regular intervals (TrueHD Atmos play perfectly).

[Draconix]

Indeed, the audio dropouts that I experienced definitely happened on a file with DD+ (likely with Atmos). TrueHD Atmos and DTS-HD MA have been perfect.

Strangely though, I haven't experienced audio dropouts in a while so I'm having a hard time nailing down the cause of the issue.

[HomerJau]

Anyone else notice that latest LibreElec 12 nightly plays Dolby Atmos JOC (streaming Atmos) as Dolby Digital 5.1 only? Is this LE only or in all flavors of Kodi?

My Denon amp displays the codec as 'Dolby Digital Plus' with nothing from height speakers. Previous Versions show 'DD+ Atmos' with height speakers active.

In addition Atmos TrueHD now only displays as 'Dolby TrueHD' (but plays heights) whereas it used to display 'Dolby Atmos'

I have not updated bm Denon firmware. Is it possible a recent change in the Kodi player is sending changed metadata?

THX

[fritsch]

Please don't highjack other threads with latest and greatest LE specific issues: https://github.com/LibreELEC/LibreELEC.t...dec64d4fac

[faust1103]

Indeed, the audio dropouts that I experienced definitely happened on a file with DD+ (likely with Atmos). TrueHD Atmos and DTS-HD MA have been perfect.

Strangely though, I haven't experienced audio dropouts in a while so I'm having a hard time nailing down the cause of the issue.

Did you receive any microstuttering or freezes using the latest Kodi 21 nightly / stable alpha V3?
I did when I upgraded from stable alpha V2 to V3.

[Draconix]

Did you receive any microstuttering or freezes using the latest Kodi 21 nightly / stable alpha V3?

I have not experienced any stuttering or frame drops since the solution was found a while ago. Are you using the default behavior, or an advancedsettings.xml with maxpassthroughoffsyncduration?

This is my advancedsettings.xml  file:

xml:
<advancedsettings>

  <audio>

    <maxpassthroughoffsyncduration>92</maxpassthroughoffsyncduration>

  </audio>

  <video>

    <latency>

      <delay>-40</delay>

    </latency>

  </video>

  <loglevel>-1</loglevel>  

</advancedsettings>

[Nuklear92]

@Draconix do you use that file alongside the one for video cache? I mean can both files be used at the same time or only one, since the video cache buffer one is also called advancedsettings. If you try to copy both files to the userdata folder, it will ask you if you want to replace or keep both. If you select keep both, then it does renames one of the two as “advancedsettings (1)”. However, Idk if the added (1) ruins the setting and doesn’t activate in kodi and only the file that’s called advancedsettings solely will be the one working. 🤔

[b1ggles]

@Draconix do you use that file alongside the one for video cache? I mean can both files be used at the same time or only one, since the video cache buffer one is also called advancedsettings. If you try to copy both files to the userdata folder, it will ask you if you want to replace or keep both. If you select keep both, then it does renames one of the two as “advancedsettings (1)”. However, Idk if the added (1) ruins the setting and doesn’t activate in kodi and only the file that’s called advancedsettings solely will be the one working. 🤔

You only have one advancedsettings, if you already have one you add that text to it.

[Nuklear92]

I understand, but my point is does adding multiple advancedsettings that does different tasks, say I already have the advancedsettings for video cache. And I decide to add the one for max video Passthrough. Does the file need to have the name “advancedsettings” to work or even if you add “advancedsettings(2).xml” does that still make the file work inside kodi.

In other words does it matter more what’s inside the file for it to activate and work in Kodi or does the “advancedsettings” name is also important and if it has any additional wording like “(2)” then it won’t activate. 🤔

[Hitcher]

https://kodi.wiki/index.php?title=Advanc...xml#Layout

[faust1103]

Did you receive any microstuttering or freezes using the latest Kodi 21 nightly / stable alpha V3?

I have not experienced any stuttering or frame drops since the solution was found a while ago. Are you using the default behavior, or an advancedsettings.xml with maxpassthroughoffsyncduration?

This is my advancedsettings.xml  file:

xml:
<advancedsettings>

  <audio>

    <maxpassthroughoffsyncduration>92</maxpassthroughoffsyncduration>

  </audio>

  <video>

    <latency>

      <delay>-40</delay>

    </latency>

  </video>

  <loglevel>-1</loglevel>  

</advancedsettings>

Hi Draconix,

I am using this advance settings



<advancedsettings>

<cache>

<buffermode>1</buffermode>

<readfactor>20</readfactor>

<memorysize>278921216</memorysize>

</cache>

</advancedsettings>


So no maxpassthroughoffsyncduration.
Do you think his make a difference?
Thanks.

[SoulReaver]

Do you think his make a difference?
Thanks.

Yes. You can just add his settings to your own advancedsettings.xml so it looks like this in the end and test it again.

xml:
 <advancedsettings>

<cache>

<buffermode>1</buffermode>

<readfactor>20</readfactor>

<memorysize>278921216</memorysize>

</cache>

<audio><maxpassthroughoffsyncduration>92</maxpassthroughoffsyncduration>

  </audio>

  <video>

    <latency>

      <delay>-40</delay>

    </latency>

  </video>

  <loglevel>-1</loglevel>  

</advancedsettings>

[Fjodor2000]

For those that are still having problems when using currently latest version of Kodi (20.2) + NVidia Shield Pro FW (9.1.1) + Samba network share as media source:

I also got mixed video stuttering and pausing problems when playing big 4K movie files (~20-30+ GB). I sometimes also got "Source too slow for continuous playback" error reported in Kodi.

However the root cause of these problems seems to be that the setup described in the first sentence does not work properly if you configure the samba network share from inside Kodi. Instead you have to configure it in the NVidia Shield Android settings. Once configured, you can then use the now already configured samba network share as media source inside Kodi. After doing so all problems of the type mentioned above were solved for me.

For more details on how to set this up, see this post:

https://forum.kodi.tv/showthread.php?tid...pid3164278

I'm informing about this since the errors are quite similar to some of those discussed in this thread. So people with the kind of setup that I described should follow the instructions in the post linked to above first, to see if that solves your problem.