Reply to thread

Message

<blockquote data-quote="mm1352000" data-source="post: 1013341" data-attributes="member: 82144">I quote the first post. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />So, the set that you say are working well for you are the PBDA set. That's all well and good. They should work fine... except that if you were running on a 64 bit system you wouldn't have access to them. In addition, there has been enough feedback now to say that they generally perform slower than the other &quot;uuid&quot; tuners which communicate more directly with the hardware.&nbsp;I stand by my recommendation to use the native/DRI interface rather than the PBDA interface. <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Unfortunately your &quot;uuid&quot; log files don't help me very much. What I see is you attempting to tune a channel just as the tuners are detected... which doesn't work out very well.&nbsp;I see you've set the tuners to preload. That's okay, but be aware there will be a significant burst of network activity as/when the tuners are loaded/connected. Attempting to tune at the same time as other tuners are loading (as you unintentionally did in your log files)... I know from experience that trying to have too many &quot;conversations&quot; with the tuners in parallel doesn't work out so well.&nbsp;I note that on your system tuner detection took roughly 15 seconds:&nbsp;I've only seen such slow detection when detection wasn't working correctly and in a VM. It concerns me.&nbsp;Couple questions for ya:<ul>
<li data-xf-list-type="ul">What is your network setup like - wireless G, wireless N, wired 100M, wired gigabit, powerline?</li>
<li data-xf-list-type="ul">Is your server running in a VM?</li>
<li data-xf-list-type="ul">I see you've got 3 IP addresses on three subnets - 192.168.200.2 (Ceton InfiniTV 4), 192.168.1.4 (???), 192.168.128.1 (???). What is the deal with that?</li>
</ul>It'd be great if you could try and grab fresh &quot;uuid&quot; logs. Please allow a bit more time for the tuners to be detected and loaded before attempting to tune.&nbsp;&nbsp;&nbsp;I don't use Argus so I can't tell you if it is causing issues - no experience. If you're using MP's TV Server isn't it relatively easy to disable temporarily and test?</blockquote>

[QUOTE="mm1352000, post: 1013341, member: 82144"] I quote the first post. :) So, the set that you say are working well for you are the PBDA set. That's all well and good. They should work fine... except that if you were running on a 64 bit system you wouldn't have access to them. In addition, there has been enough feedback now to say that they generally perform slower than the other "uuid" tuners which communicate more directly with the hardware. I stand by my recommendation to use the native/DRI interface rather than the PBDA interface. :) Unfortunately your "uuid" log files don't help me very much. What I see is you attempting to tune a channel just as the tuners are detected... which doesn't work out very well. I see you've set the tuners to preload. That's okay, but be aware there will be a significant burst of network activity as/when the tuners are loaded/connected. Attempting to tune at the same time as other tuners are loading (as you unintentionally did in your log files)... I know from experience that trying to have too many "conversations" with the tuners in parallel doesn't work out so well. I note that on your system tuner detection took roughly 15 seconds: I've only seen such slow detection when detection wasn't working correctly and in a VM. It concerns me. Couple questions for ya: [LIST] [*]What is your network setup like - wireless G, wireless N, wired 100M, wired gigabit, powerline? [*]Is your server running in a VM? [*]I see you've got 3 IP addresses on three subnets - 192.168.200.2 (Ceton InfiniTV 4), 192.168.1.4 (???), 192.168.128.1 (???). What is the deal with that? [/LIST] It'd be great if you could try and grab fresh "uuid" logs. Please allow a bit more time for the tuners to be detected and loaded before attempting to tune. I don't use Argus so I can't tell you if it is causing issues - no experience. If you're using MP's TV Server isn't it relatively easy to disable temporarily and test? [/QUOTE]

Verification