Reply to thread

Message

<blockquote data-quote="DrMopar" data-source="post: 492544" data-attributes="member: 70303">From what I can see in the links in my previous post and also here<a href="https://forum.team-mediaportal.com/general-development-no-feature-request-here-48/solution-bug-0002069-a-57497/" target="_blank">https://forum.team-mediaportal.com/general-development-no-feature-request-here-48/solution-bug-0002069-a-57497/</a>it doesn't look like a fix is due then either unfortunately. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite3" alt=":(" title="Frown&nbsp; &nbsp; :(" loading="lazy" data-shortname=":(" /> From my limited understanding, it seems that TSReader does not pass all of the info that the codecs need. From the CoreAVC forums the feeling is that this is a problem with TSReader and not the CoreAVC codec. We may be in for a long wait on this one.........</blockquote>

[QUOTE="DrMopar, post: 492544, member: 70303"] From what I can see in the links in my previous post and also here [url]https://forum.team-mediaportal.com/general-development-no-feature-request-here-48/solution-bug-0002069-a-57497/[/url] it doesn't look like a fix is due then either unfortunately. :( From my limited understanding, it seems that TSReader does not pass all of the info that the codecs need. From the CoreAVC forums the feeling is that this is a problem with TSReader and not the CoreAVC codec. We may be in for a long wait on this one......... [/QUOTE]

Verification