Reply to thread

Message

<blockquote data-quote="htpcoz" data-source="post: 131956" data-attributes="member: 13987">I've had a look through the postings and I think I know the answer is currently no, as the MCEIR only supports one client at a time, but I thought I'd just ask if there was a fix, or if it was on the roadmap.I have a single PC installation of TVE3, with client and server on one machine.I've had problems with the server blaster not working (raised in another posting), so I went back to the old trusty MCE replacement, and on the server it works perfectly.Now as I needed to install the replacement driver to get the TVE3ReplacementBlaster to work, my native MCE remote support in the MP frontend no longer works. So I need to configure the MCE Replacement in the MP frontend as well.Now at this point all is great the TVE3 is running and will change channel successfully. The MP frontend is working, and the MCE remote is able to control MP perfectly (using the MCE Replacement Plugin).Now, if I change channels, the blaster will blast out OK the channel change, but from that point on, my MP frontend will not respond to remote clicks, I think this is because with the TVE3BLaster using the MCEIR API it effectively &quot;disconnects&quot; the MCE Replacement Plugin.Is there any way to have the TVE3Blaster not &quot;break&quot; the MP Plugin (perhaps after blasting then re-initialse the driver to a sane state for the MP plugin to operate) ? or does the simple event of accessing the API break any other clients using the API?Other thoughts would be if we didn't need the replacement driver then the TVE3 blaster and MP Plugin would be able to operate together, as I don't believe there are similar &quot;re-entrancy&quot; (for want of a better word) issues with the standard driver interface.I've tried using the standard ServerBlaster that comes with TVE3, but it is broken at the moment (won't blast at all).Any ideas?</blockquote>

[QUOTE="htpcoz, post: 131956, member: 13987"] I've had a look through the postings and I think I know the answer is currently no, as the MCEIR only supports one client at a time, but I thought I'd just ask if there was a fix, or if it was on the roadmap. I have a single PC installation of TVE3, with client and server on one machine. I've had problems with the server blaster not working (raised in another posting), so I went back to the old trusty MCE replacement, and on the server it works perfectly. Now as I needed to install the replacement driver to get the TVE3ReplacementBlaster to work, my native MCE remote support in the MP frontend no longer works. So I need to configure the MCE Replacement in the MP frontend as well. Now at this point all is great the TVE3 is running and will change channel successfully. The MP frontend is working, and the MCE remote is able to control MP perfectly (using the MCE Replacement Plugin). Now, if I change channels, the blaster will blast out OK the channel change, but from that point on, my MP frontend will not respond to remote clicks, I think this is because with the TVE3BLaster using the MCEIR API it effectively "disconnects" the MCE Replacement Plugin. Is there any way to have the TVE3Blaster not "break" the MP Plugin (perhaps after blasting then re-initialse the driver to a sane state for the MP plugin to operate) ? or does the simple event of accessing the API break any other clients using the API? Other thoughts would be if we didn't need the replacement driver then the TVE3 blaster and MP Plugin would be able to operate together, as I don't believe there are similar "re-entrancy" (for want of a better word) issues with the standard driver interface. I've tried using the standard ServerBlaster that comes with TVE3, but it is broken at the moment (won't blast at all). Any ideas? [/QUOTE]

Verification