Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 709252" data-attributes="member: 82144">Hi again BrianGreat <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" />I have absolutely no idea about dynamic refresh rate changer so I'm sorry but I can't help with that.Compiling MediaPortal couldn't be easier if you ask me. I'd absolutely encourage you to &quot;dabble&quot;. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />Your logs show that it is safe to just ignore the error and carry on with tuning. If you look at the source code, all I did was comment out one line in TvEngine3\TVLibrary\TVLibrary\Implementations\DVB\Graphs\TvCardDvbBase.cs:[CODE]&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Log.Log.WriteFile(&quot;dvb:Submit tunerequest calling put_TuneRequest&quot;);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; int hr = ((ITuner)_filterNetworkProvider).put_TuneRequest(tuneRequest);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Log.Log.WriteFile(&quot;dvb:Submit tunerequest done calling put_TuneRequest&quot;);&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; if (hr != 0)&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; {&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; Log.Log.WriteFile(&quot;dvb:SubmitTuneRequest&nbsp; returns:0x{0:X} - {1}{2}&quot;, hr, HResult.GetDXErrorString(hr),&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; DsError.GetErrorText(hr));&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; [B]throw new TvException(&quot;Unable to tune to channel&quot;);[/B]&nbsp; &nbsp; &nbsp; &nbsp; &nbsp; &nbsp; }[/CODE]In other words, if you don't throw the exception, tuning will carry on as usual...I actually wonder whether this issue would be resolved for you if you upgrade to 1.2.0a and use the new &quot;pause graph&quot; option. The real &quot;issue&quot; seems to be that the tuner driver is warning you that it is already successfully tuned to a particular transponder and that it won't retune the hardware. If you were able to avoid submitting a tune request to the driver when it is already tuned to a transponder then I think you would get rid of the error.TV Server already avoids submitting a tune request if you change channels but don't change transponder (which is why you don't see any error happening with that situation). However, when you actually stop TV, TV Server wipes the tuning history (ie. it no longer remembers the last channel you were tuned to). A new tune request will *always* be submitted when you start TV again, and that would trigger the problem that you're seeing here. The tuner driver remembers what channel was last tuned even after we stop the channel but TV Server doesn't (for compatibility and to allow forcing a retune)...Now how might 1.2.0a help I hear you ask? In 1.2.0a we added an optimisation that only *pauses* the channel behind the scenes when you stop live TV. It makes changing channels a lot faster on some tuners. There is a downside in that some drivers don't like us doing that (it is optional, but turned on by default for 1.2.0a). The critical thing is that unlike with a full stop, TV Server actually remembers the tuning history with the pause option. Hence, when &quot;stop&quot; TV (pause behind the scenes) then try to view a channel on the same transponder TV Server will remember that it is already tuned to the appropriate transponder and won't bother submitting a tune request to the driver, theoretically avoiding the issue!I apologise for the technicality of the above explanation but figured that you would probably appreciate a full explanation. Especially considering that you know how to programme. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink&nbsp; &nbsp; ;)" loading="lazy" data-shortname=";)" />The only potential issue that I can see with the above resolution is that the Cinergy may not support the pause behaviour. I guess there is only one way to find out if it will work... <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite8" alt=":D" title="Big Grin&nbsp; &nbsp; :D" loading="lazy" data-shortname=":D" /></blockquote>

[QUOTE="mm1352000, post: 709252, member: 82144"] Hi again Brian Great :D I have absolutely no idea about dynamic refresh rate changer so I'm sorry but I can't help with that. Compiling MediaPortal couldn't be easier if you ask me. I'd absolutely encourage you to "dabble". ;) Your logs show that it is safe to just ignore the error and carry on with tuning. If you look at the source code, all I did was comment out one line in TvEngine3\TVLibrary\TVLibrary\Implementations\DVB\Graphs\TvCardDvbBase.cs: [CODE] Log.Log.WriteFile("dvb:Submit tunerequest calling put_TuneRequest"); int hr = ((ITuner)_filterNetworkProvider).put_TuneRequest(tuneRequest); Log.Log.WriteFile("dvb:Submit tunerequest done calling put_TuneRequest"); if (hr != 0) { Log.Log.WriteFile("dvb:SubmitTuneRequest returns:0x{0:X} - {1}{2}", hr, HResult.GetDXErrorString(hr), DsError.GetErrorText(hr)); [B]throw new TvException("Unable to tune to channel");[/B] } [/CODE] In other words, if you don't throw the exception, tuning will carry on as usual... I actually wonder whether this issue would be resolved for you if you upgrade to 1.2.0a and use the new "pause graph" option. The real "issue" seems to be that the tuner driver is warning you that it is already successfully tuned to a particular transponder and that it won't retune the hardware. If you were able to avoid submitting a tune request to the driver when it is already tuned to a transponder then I think you would get rid of the error. TV Server already avoids submitting a tune request if you change channels but don't change transponder (which is why you don't see any error happening with that situation). However, when you actually stop TV, TV Server wipes the tuning history (ie. it no longer remembers the last channel you were tuned to). A new tune request will *always* be submitted when you start TV again, and that would trigger the problem that you're seeing here. The tuner driver remembers what channel was last tuned even after we stop the channel but TV Server doesn't (for compatibility and to allow forcing a retune)... Now how might 1.2.0a help I hear you ask? In 1.2.0a we added an optimisation that only *pauses* the channel behind the scenes when you stop live TV. It makes changing channels a lot faster on some tuners. There is a downside in that some drivers don't like us doing that (it is optional, but turned on by default for 1.2.0a). The critical thing is that unlike with a full stop, TV Server actually remembers the tuning history with the pause option. Hence, when "stop" TV (pause behind the scenes) then try to view a channel on the same transponder TV Server will remember that it is already tuned to the appropriate transponder and won't bother submitting a tune request to the driver, theoretically avoiding the issue! I apologise for the technicality of the above explanation but figured that you would probably appreciate a full explanation. Especially considering that you know how to programme. ;) The only potential issue that I can see with the above resolution is that the Cinergy may not support the pause behaviour. I guess there is only one way to find out if it will work... :D [/QUOTE]

Verification