Reply to thread

Message: <blockquote data-quote="mm1352000" data-source="post: 1122363" data-attributes="member: 82144">Hello again <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile    :)" loading="lazy" data-shortname=":)" />Okay. What information are you actually hoping to find? Most tuners don't come with much in the way of manuals. Usually the only available information is a list of technical specifications and instructions for installing the hardware and driver.Just to extend my previous answer a little...Those "formats" are only marginally more efficient than TS. If you put exactly the same video, audio and subtitles in TS, MKV and MP4 files, the size would be approximately the same. Significant reductions in file size really only come from re-encoding the video (or audio):<ul> <li data-xf-list-type="ul">translate to a more efficient encoding format (eg. MPEG 2 video => h.264/AVC video) </li> <li data-xf-list-type="ul">resolution and/or bitrate reduction</li> </ul>Tuners don't generally do any re-encoding, as it would require relatively expensive hardware components and could introduce significant problems (glitchy video/audio, loss of video/audio synchronisation etc.). In fact, the only exception to that rule which I can think of off the top of my head is the SiliconDust HDHomeRun TC model(s).As "container formats", the significant point of difference between TS and MKV, MP4 etc. is much more subtle (eg. time codes, CRCs, sync/start codes etc.). MKV and MP4 are designed for reliable file storage; TS is designed for unreliable broadcast Here in NZ most local stores have "money back return if not satisfied" policies. Are there no stores like that which you could buy from?This was the "little" part of the "little or no support" that I was referring to. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink    ;)" loading="lazy" data-shortname=";)" />Yes, the default tuning spaces have been defined. However, if you look more closely you'll see that the CLSID (class ID) value for the ISDB-T and DVB-T tuning spaces is the same. Basically that means that ISDB-T support would be implemented the same as DVB-T.A default tuning space is just a set of values - pretty much meaningless. So, I guess you could say that the MP input is agnostic, but I'd probably say it more like this:DVB-T and ISDB-T are a little similar. In order to tune a DVB-T channel, you need to know the frequency and bandwidth. Same for ISDB-T: frequency and bandwidth are required.We know that Microsoft BDA fully supports DVB-T but does not really support ISDB-T.Since the tuning parameters (frequency, bandwidth) for DVB-T and ISDB-T are the same, tuner vendors realised it is possible to reuse the technical BDA DVB-T stuff (tuning space, network provider, tune request etc.) to create ISDB-T tuner products. In other words, these "BDA-compliant"/WMC-compatible ISDB-T tuners are products with ISDB-T hardware that appear as DVB-T tuners to Windows.Does this make sense?Yes, the value of the ISDB-T bandwidth is usually 6 MHz, and the frequency offset is different to DVB-T. These facts would be used when constructing a tuning detail file for MP. A good example is the ISDB-T tuning details for Sao Paulo Brazil:<a href="https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/TVServer.Base/TuningParameters/dvbt/Brazil.ISDB%20-%20Sao%20Paulo.xml" target="_blank">https://github.com/MediaPortal/MediaPortal-1/blob/master/TvEngine3/TVLibrary/TVServer.Base/TuningParameters/dvbt/Brazil.ISDB - Sao Paulo.xml</a>Once you get a tuner, you can simply copy the tuning details for Sao Paulo and enter the frequencies for your region.</blockquote>

Verification