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
General Forums
Newcomers Forum
Mediaportal with uncommitted Disceq
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="ozkarah" data-source="post: 895587" data-attributes="member: 112238"><p><span style="font-family: 'arial'">Hello to all,</span></p><p> </p><p><span style="font-family: 'arial'">Since I got the info from MM that the patch for 1.3 will last some long time, I started to find some other easy to use ways for the problem of the mixed usage of non universal lnbs and universal lnbs together. </span></p><p> </p><p><span style="font-family: 'arial'">Finally, I have found a workaround for my problem. No more I need this patch. Workaround is using the universal lnb setting for all lnbs but using different transponder list file with recalculated frequencies for 9750/10600/11700 mhz lnb settings. </span></p><p> </p><p><span style="font-family: 'arial'">My system utilitizes satellite dishes with 7.0 Eutelsat W3A,13.0 Hotbird and 42.0 Turksat; and the dish for 7.0 is equipped with a MDU2 LNB. All I had to do is create a new xml file for 7.0 and edit "satellites.xml". The tricky part is it might be some hard to recalculate the frequencies for the new xml file. </span></p><p> </p><p><span style="font-family: 'arial'">All the files are at home and I am not at home now. Anyone needs more info about it just ask here. I will try to answer very soon.</span></p><p> </p><p> </p><p> </p><p><span style="font-family: 'arial'">PS: However still not able to use MP 1.3a. Because I couldn't make MDAPI+Acamd work with MP 1.3.0a. Everything works fine with 1.2.2 and 1.2.3. My system is running Windows 7 x64 and WinTV HVR 4400 is utilized. If anyone is able to make MDAPI work on 1.3 pls inform me. </span></p><p> </p><p>best regards.</p></blockquote><p></p>
[QUOTE="ozkarah, post: 895587, member: 112238"] [FONT=arial]Hello to all,[/FONT] [FONT=arial]Since I got the info from MM that the patch for 1.3 will last some long time, I started to find some other easy to use ways for the problem of the mixed usage of non universal lnbs and universal lnbs together. [/FONT] [FONT=arial]Finally, I have found a workaround for my problem. No more I need this patch. Workaround is using the universal lnb setting for all lnbs but using different transponder list file with recalculated frequencies for 9750/10600/11700 mhz lnb settings. [/FONT] [FONT=arial]My system utilitizes satellite dishes with 7.0 Eutelsat W3A,13.0 Hotbird and 42.0 Turksat; and the dish for 7.0 is equipped with a MDU2 LNB. All I had to do is create a new xml file for 7.0 and edit "satellites.xml". The tricky part is it might be some hard to recalculate the frequencies for the new xml file. [/FONT] [FONT=arial]All the files are at home and I am not at home now. Anyone needs more info about it just ask here. I will try to answer very soon.[/FONT] [FONT=arial]PS: However still not able to use MP 1.3a. Because I couldn't make MDAPI+Acamd work with MP 1.3.0a. Everything works fine with 1.2.2 and 1.2.3. My system is running Windows 7 x64 and WinTV HVR 4400 is utilized. If anyone is able to make MDAPI work on 1.3 pls inform me. [/FONT] best regards. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
General Forums
Newcomers Forum
Mediaportal with uncommitted Disceq
Contact us
RSS
Top
Bottom