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
MediaPortal 1 Talk
Teletext subtitles
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="ziphnor" data-source="post: 179678" data-attributes="member: 14215"><p>It contains information linking subtitle numbers to actual languages. In the teletext header you only get encoding/character table information in the language field, so for example you have no way of telling Norwegian, Swedish and Danish apart (language is 2 (swedish) for all of them). The DVB SI will map (say) page 693 to 'dan' (danish) so that you can select the correct page automatically based on the users language preference instead of having him manually set up subtitle pages. This also enables you to easily make some fixes in the character encoding, such that for danish you for example swap ö for ø (or something like that).</p><p></p><p></p><p></p><p>I was just trying to figure out how what i am doing right now, could be used to achieve what your suggesting, without having to make drastic changes. My point is that its probably best to have the callback in a filter separate filter from TsReader, as TsReader is supposed to be essentially a DirectShow demux'er for TS files, and hence it makes more sense that it just provides a teletext output pin (and also because i already created the code for it <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" />. </p><p></p><p></p><p></p><p>I hate analog TV <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile :)" loading="lazy" data-shortname=":)" /> But couldn't we just structure it so that the teletext module has no clue about whether the source is analogue or digital, after all the only difference is bit of the initial data of each packet (ie run-in is not present in DVB etc ). Once its unwrapped digital and analog should be the same, right? So the teletext module should just have a Receive() method that we can call from DirectShow for digital stuff and then you can create an analog teletext grabber that calls the same method (of course not at the same time ).</p><p></p><p></p><p></p><p>A good place to start.</p></blockquote><p></p>
[QUOTE="ziphnor, post: 179678, member: 14215"] It contains information linking subtitle numbers to actual languages. In the teletext header you only get encoding/character table information in the language field, so for example you have no way of telling Norwegian, Swedish and Danish apart (language is 2 (swedish) for all of them). The DVB SI will map (say) page 693 to 'dan' (danish) so that you can select the correct page automatically based on the users language preference instead of having him manually set up subtitle pages. This also enables you to easily make some fixes in the character encoding, such that for danish you for example swap ö for ø (or something like that). I was just trying to figure out how what i am doing right now, could be used to achieve what your suggesting, without having to make drastic changes. My point is that its probably best to have the callback in a filter separate filter from TsReader, as TsReader is supposed to be essentially a DirectShow demux'er for TS files, and hence it makes more sense that it just provides a teletext output pin (and also because i already created the code for it :). I hate analog TV :) But couldn't we just structure it so that the teletext module has no clue about whether the source is analogue or digital, after all the only difference is bit of the initial data of each packet (ie run-in is not present in DVB etc ). Once its unwrapped digital and analog should be the same, right? So the teletext module should just have a Receive() method that we can call from DirectShow for digital stuff and then you can create an analog teletext grabber that calls the same method (of course not at the same time ). A good place to start. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Talk
Teletext subtitles
Contact us
RSS
Top
Bottom