Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1094856" data-attributes="member: 82144">TVE 3/MP1 should have supported that already for your tuner (in TVE 3 there's an &quot;add s-video channels&quot; button).These are both caused by the same problem, which is the one morpheus_xx mentioned. I've just pushed the fix to my branch.[USER=48495]@morpheus_xx[/USER] I decided to do something slightly different than what your patch does. The replacement function seemed to generate longer strings which are a bit unsuitable for logging in the way I was previously doing. So, I applied your patch but also removed use of the function from the custom device plugins. Further, I completely remove the DxErr9 DLL code and project to avoid chances of people using it again without knowing the consequences. Hope you don't mind too much.I'm not 100% sure what you mean, but failure to lock on signal happens sometimes - especially during scanning. It is now logged as an error to clearly identify it. You can probably consider this to be normal/expected behaviour.That's a bug! Fixed and pushed. Thanks. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" /></blockquote>

[QUOTE="mm1352000, post: 1094856, member: 82144"] TVE 3/MP1 should have supported that already for your tuner (in TVE 3 there's an "add s-video channels" button). These are both caused by the same problem, which is the one morpheus_xx mentioned. I've just pushed the fix to my branch. [USER=48495]@morpheus_xx[/USER] I decided to do something slightly different than what your patch does. The replacement function seemed to generate longer strings which are a bit unsuitable for logging in the way I was previously doing. So, I applied your patch but also removed use of the function from the custom device plugins. Further, I completely remove the DxErr9 DLL code and project to avoid chances of people using it again without knowing the consequences. Hope you don't mind too much. I'm not 100% sure what you mean, but failure to lock on signal happens sometimes - especially during scanning. It is now logged as an error to clearly identify it. You can probably consider this to be normal/expected behaviour. That's a bug! Fixed and pushed. Thanks. :) [/QUOTE]

Verification