home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Clear QAM DC-II video question
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="jonesdb" data-source="post: 493811" data-attributes="member: 64597"><p>mizzourob:</p><p>I suspect that there are many others with the same issue. My cable provider is Comcast, so that is one example of a large nationwide provider. Since the US standard for cable providers calls out DC-II to be labeled as 0x80 I suspect we would find it in many systems. I suspect that it was easier for the cable providers to implement when obtaining the stream from some of the "cable channel providers". In my case, History, Halmark, SciFi and TruTV all carry the 0x80 tag. Interestingly, not all streams within the physical channel are tagged this way. Some are encrypted, some are MPEG2 and some DC-II. I haven't found any logic behind which channels are tagged 0x80 and which are tagged 0x2.</p><p></p><p>tourettes:</p><p>I ran a search for "SERVICE_TYPE" on the DirectShowFilters solution for 1.1 Alpha and didn't find anything defining 0x80 anywhere, let alone in the pmtParsers for TSReader and TSWriter. The search results are in the attached txt file. I also didn't find anyting defining LPCM. The LPCM search only returned some references to some mediasubtype stuff (looks like DVD related, though still no pmt type of 0x80 as far as I can tell.)</p><p>I'm aware of the use of LPCM in BluRay DVD, but don't see any references to this in MP. </p><p>Thoughts on where to go from here?</p></blockquote><p></p>
[QUOTE="jonesdb, post: 493811, member: 64597"] mizzourob: I suspect that there are many others with the same issue. My cable provider is Comcast, so that is one example of a large nationwide provider. Since the US standard for cable providers calls out DC-II to be labeled as 0x80 I suspect we would find it in many systems. I suspect that it was easier for the cable providers to implement when obtaining the stream from some of the "cable channel providers". In my case, History, Halmark, SciFi and TruTV all carry the 0x80 tag. Interestingly, not all streams within the physical channel are tagged this way. Some are encrypted, some are MPEG2 and some DC-II. I haven't found any logic behind which channels are tagged 0x80 and which are tagged 0x2. tourettes: I ran a search for "SERVICE_TYPE" on the DirectShowFilters solution for 1.1 Alpha and didn't find anything defining 0x80 anywhere, let alone in the pmtParsers for TSReader and TSWriter. The search results are in the attached txt file. I also didn't find anyting defining LPCM. The LPCM search only returned some references to some mediasubtype stuff (looks like DVD related, though still no pmt type of 0x80 as far as I can tell.) I'm aware of the use of LPCM in BluRay DVD, but don't see any references to this in MP. Thoughts on where to go from here? [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
Development
General Development (no feature request here!)
Clear QAM DC-II video question
Contact us
RSS
Top
Bottom