Would Like to Start Working on USBUIRT Fix: Where Do I Start (1 Viewer)
- Thread starter SteveV
- Start date
- Thread starter
- #62
Ok, I think I found the problem. I have put together a test version that writes additional info to the mediaportal.log file. You can download it here.
Backup your original configuration.exe and core.dll files and extract the zip in your mediaportal dir. Launch configuration.exe and let me know if it works.
If it *doesn't* work I'll need to usbuirt log entries that begin with "12/23/2005 7:30:33 AM Checking USBUIRT Status...". Please try clicking the "Learn settop box commands" with the USBUIRT connected and disconnected and post log entries for both cases.
Steve
Backup your original configuration.exe and core.dll files and extract the zip in your mediaportal dir. Launch configuration.exe and let me know if it works.
If it *doesn't* work I'll need to usbuirt log entries that begin with "12/23/2005 7:30:33 AM Checking USBUIRT Status...". Please try clicking the "Learn settop box commands" with the USBUIRT connected and disconnected and post log entries for both cases.
Steve
Learning works now. The driver stays loaded and I can go into the learning window. But there are problems.
I can initially learn stb codes and testing each one works, but once I close the setup program some stop working. I can learn 0-9 in one session and 2368 won't work, in another session I can learn 0-9 and 0147 won't work. I've tried learning each individually, all at once, even goings as far as learn each individually and closing the setup program between each attempt.
The only sure fire way I can be sure it learned the code and will save correctly is to keep relearning until it shows 2 codes in the 'Learned Transmit IR Codes(s)' box. Even if the test works, if there isn't 2 codes for each, it will stop working after you close the setup program.
But once everything is learned and saved correctly it does work great
This is what I have after learning stb codes:
This is what I have after trying again and again:
Tested in
MP 0.2.0 RC2 + CVS build 12-23-2005--10-41 + test configuration.exe/core.dll
MP 0.2.0 RC2 + test configuration.exe/core.dll
I can initially learn stb codes and testing each one works, but once I close the setup program some stop working. I can learn 0-9 in one session and 2368 won't work, in another session I can learn 0-9 and 0147 won't work. I've tried learning each individually, all at once, even goings as far as learn each individually and closing the setup program between each attempt.
The only sure fire way I can be sure it learned the code and will save correctly is to keep relearning until it shows 2 codes in the 'Learned Transmit IR Codes(s)' box. Even if the test works, if there isn't 2 codes for each, it will stop working after you close the setup program.
But once everything is learned and saved correctly it does work great
This is what I have after learning stb codes:
Code:
<docElement>
<entry index="0" istoggle="False">F2BR02EA80C080C03080923080923030308092308092308092303030303080923080923030303030303080923030303030303080923080923030303030809230</entry>
<entry index="0" istoggle="True">F2BR02EA80C080C13080923080923031308092308092308092303130313080923080923031303130313080923031303130313080923080923031303130809230</entry>
<entry index="1" istoggle="False">F2BR02EA80C080C13080923080923030308092308092303030303030303030809230303030303030809230303030308092308092308092308092303030809230</entry>
<entry index="1" istoggle="True">F2BR02EA80C080C03080923080923030308092308092303030303030303030809230303030303030809230303030308092308092308092308092303030809230</entry>
<entry index="2" istoggle="False">F2BR02EA80C080C03080923080923030308092308092308092303030303030308092303030303030308092303030303030308091308092308092303030809230</entry>
<entry index="2" istoggle="True">F2BR02EA80C080C03080923080923030308092308092308092303030303030308092303030303030308092303030303030308092308092308092303030809230</entry>
<entry index="3" istoggle="False">F2BR02EA80C080C03080923080923030308092308092303030809230303030308092303030303030308092303030303080923030308092308092303030809230</entry>
<entry index="3" />
<entry index="4" istoggle="False">F2BR02EA80C080C13080923080923030308092308092308092308092303030303080923030303030303080923030303030303030308092308092303030809230</entry>
<entry index="4" />
<entry index="5" istoggle="False">F2BR02EA80C080C13080923080923031308092308092303130313080923031308092303130313031308092303130313080923080923031308092303130809230</entry>
<entry index="5" />
<entry index="6" istoggle="False">F2BR02EA80C080C13080923080923031308092308092308092303130809230313080923031303130313080923031303130313080923031308092303130809230</entry>
<entry index="6" />
<entry index="7" istoggle="False">F2BR02EA80C080C13080923080923031308092308092303130809230809230313080923031303130313080923031303130809230313031308092303130809230</entry>
<entry index="7" />
<entry index="8" istoggle="False">F2BR02EA80C080C13080923080923031308092308092308092308092308092303130809230313031303130809230313031303130313031308092303130809230</entry>
<entry index="8" />
<entry index="9" istoggle="False">F2BR02EA80C080C13080923080923031308092308092303130313031308092308092303130313031308092303130313080923080923080923031303130809230</entry>
<entry index="9" />
<entry index="10" />
<entry index="10" />
</docElement>This is what I have after trying again and again:
Code:
<docElement>
<entry index="0" istoggle="False">F2BR02EA80BF80C13080923080923031308092308092308092303130313080923080923031303130313080923031303130313080923080923031303130809230</entry>
<entry index="0" istoggle="True">F2BR02EB80BE80C13080923080923031308092308092308092303130313080923080923031303130313080923031303130313080923080923031303130809230</entry>
<entry index="1" istoggle="False">F2BR02EA80C080C13080923080923031308092308092303130313031303130809230313031303130809230313031308092308092308092308092303130809230</entry>
<entry index="1" istoggle="True">F2BR02EA80C180C13080923080923031308092308092303130313031303130809230313031303130809230313031308092308092308092308092303130809230</entry>
<entry index="2" istoggle="False">F2BR02EA80C080C13080923080923031308092308092308092303130313031308092303130313031308092303130313031308092308092308092303130809230</entry>
<entry index="2" istoggle="True">F2BR02EA80C080C13080923080923031308092308092308092303130313031308092303130313030308092303130313031308092308092308092303130809230</entry>
<entry index="3" istoggle="False">F2BR02EA80BF80C13080923080923031308092308092303130809230313031308092303130313031308092303130313080923031308092308092303130809230</entry>
<entry index="3" istoggle="True">F2BR02EA80C080C13080923080923031308092308092303130809230313031308092303130313031308092303130313080923031308092308092303130809230</entry>
<entry index="4" istoggle="False">F2BR02EA80C080C13080923080923030308092308092308092308092303130313080923031303130303080923031303030313031308092308092303030809230</entry>
<entry index="4" istoggle="True">F2BR02EA80C080C13080923080923031308092308092308092308092303130313080923031303130313080923030303130313031308092308092303030809230</entry>
<entry index="5" istoggle="False">F2BR02EA80C080C13080923080923031308092308092303130303080923030308092303130303030308092303030313080923080923030308092303030809230</entry>
<entry index="5" istoggle="True">F2BR02EA80C080C03080923080923030308092308092303030303080923030308092303030303030308092303030303080923080923030308092303030809230</entry>
<entry index="6" istoggle="False">F2BR02EA80C080C03080913080913030308092308091308092303030809230303080923030303030303080913030303030303080913030308092303030809230</entry>
<entry index="6" istoggle="True">F2BR02EA80C080C03080913080923030308092308092308092303030809230303080923030303030303080923030303030303080923030308092303030809230</entry>
<entry index="7" istoggle="False">F2BR02EA80C080C03080923080923030308092308092303030809230809230303080923030303030303080923030303030809230303030308092303030809230</entry>
<entry index="7" istoggle="True">F2BR02EA80C080C03080923080923030308092308092303030809230809230303080923030303030303080913030303030809230303030308092303030809230</entry>
<entry index="8" istoggle="False">F2BR02EA80C080C03080923080923030308092308092308092308092308092303030809230303030303030809230303030303030303030308092303030809230</entry>
<entry index="8" istoggle="True">F2BR02EA80C080C13080923080923030308092308092308092308092308092303030809230303030303030809230303030303030303030308092303030809230</entry>
<entry index="9" istoggle="False">F2BR02EA80C080C13080923080923031308092308092303130313031308092308092303130313031308092303130313080923080923080923031303130809230</entry>
<entry index="9" istoggle="True">F2BR02EA80C080C13080923080923031308092308092303130313031308092308092303130313031308092303130313080923080923080923031303130809230</entry>
<entry index="10" istoggle="False">F2BR02EA80C080C13080923080923031308092308092303030303080923080923031303030303030308092303030303080923080923030303030809230809230</entry>
<entry index="10" istoggle="True">F2BR02EA80C080C03080913080913030308091308091303030303080913080913030303030303030308091303030303080913080913030303030809130809130</entry>
</docElement>Tested in
MP 0.2.0 RC2 + CVS build 12-23-2005--10-41 + test configuration.exe/core.dll
MP 0.2.0 RC2 + test configuration.exe/core.dll
- Thread starter
- #64
Ok, a couple of things; you may be doing most or all of these but we need to start some place and the begining is as good a place to start as any.
First, you'll only see 2 entries per button in the UIRTUSB-tuner.xml file *if* your stb remote transmits toggle format codes such as RC5 or RC6.
Toggle code formats like Philips RC5, RC6, and similar, only toggle the code on alternate key presses. The toggle does not occur on repeats when you press and hold the key. In other words; press and release the "1" button and the remote will transmit code "1a". Press and hold the same button and the remote will xmit code "1b" (the toggled version of 1a) for as long as the button is held down. Press the same key a third time and the remote will transmit code "1a".
The USBUIRT teaching function asks you to learn each button twice. if both codes match, we make the assumption that we're not using a toggle code format. However, there are a couple of potential problems with this assumption. Let assume you're teaching the "1" button on your remote. Consider what might happen if you successfully teach the first code but inadvertantly tap, rather than hold, the button for the second learn. The USBUIRT would ignore the second code because the ir stream was too short. As such you would need to press and hold the button a third time. Since toggle codes only happen on alternate button presses, you would have taught the same code twice and only one entry would show up for the "1" button in the UIRTUSB-tuner.xml file.
When teaching the USBUIRT it important that you your remote is 1-2" away from the USBUIRT *and* that you press AND hold the key you are teaching *until* you receive the confirmation message box that the code was learned properly. Tapping or pressing the buttons rapidly *might* result in the capture of a code but it will very likely not work properly.
So, I'd ask that you go through the learn process again for each code, pressing and holding each key until you receive a confirmation message. When you have gone through the entire process examine the UIRTUSB-tuner.xml file to see whether you've learned one or two codes per button. If you're seeing 2 entires for some codes and 1 enrty for others we'll need to determine why that's happening before proceeding further.
Once you've gotten all of that sorted out you can begin testing whether it works propely with your stb. If it's still unreliable, the "Inter-command delay ms" value (the amount of time to wait between digits) and/or the "Command repeat count" (the amount of times the same ir code is sent) may need to be increased.
Hope this helps,
Steve
First, you'll only see 2 entries per button in the UIRTUSB-tuner.xml file *if* your stb remote transmits toggle format codes such as RC5 or RC6.
Toggle code formats like Philips RC5, RC6, and similar, only toggle the code on alternate key presses. The toggle does not occur on repeats when you press and hold the key. In other words; press and release the "1" button and the remote will transmit code "1a". Press and hold the same button and the remote will xmit code "1b" (the toggled version of 1a) for as long as the button is held down. Press the same key a third time and the remote will transmit code "1a".
The USBUIRT teaching function asks you to learn each button twice. if both codes match, we make the assumption that we're not using a toggle code format. However, there are a couple of potential problems with this assumption. Let assume you're teaching the "1" button on your remote. Consider what might happen if you successfully teach the first code but inadvertantly tap, rather than hold, the button for the second learn. The USBUIRT would ignore the second code because the ir stream was too short. As such you would need to press and hold the button a third time. Since toggle codes only happen on alternate button presses, you would have taught the same code twice and only one entry would show up for the "1" button in the UIRTUSB-tuner.xml file.
When teaching the USBUIRT it important that you your remote is 1-2" away from the USBUIRT *and* that you press AND hold the key you are teaching *until* you receive the confirmation message box that the code was learned properly. Tapping or pressing the buttons rapidly *might* result in the capture of a code but it will very likely not work properly.
So, I'd ask that you go through the learn process again for each code, pressing and holding each key until you receive a confirmation message. When you have gone through the entire process examine the UIRTUSB-tuner.xml file to see whether you've learned one or two codes per button. If you're seeing 2 entires for some codes and 1 enrty for others we'll need to determine why that's happening before proceeding further.
Once you've gotten all of that sorted out you can begin testing whether it works propely with your stb. If it's still unreliable, the "Inter-command delay ms" value (the amount of time to wait between digits) and/or the "Command repeat count" (the amount of times the same ir code is sent) may need to be increased.
Hope this helps,
Steve
Steve, I first want to thank you for all your hard work on this project and the work you are doing on the Music portion of MP. Keep up the good work.
I think I have an issue that relates to the USB-UIRT plug-in. It seems like Previous menu is different that Previous window (escape) is on the keyboard. I assumed that these were the same things even when the names were slightly different. I don't know if this is how its suppose to be or what, but when I use previous menu using my remote and USB-UIRT it does funny things. If I am watching a movie in full screen and hit previous menu it does just that. However, it does not display the video in the corner but the sound is still playing. If I keep hitting previous menu to go all the way to the start screen it removes the buttons on the top. I am talking about the 3 buttons to close MP. The Only way to fix this is to set up the command "jump to full screen TV/movie" with the remote. I hit that and then I must exit out of the video and when I go back to the first screen my buttons come back. I am using the bluetwo skin.
When you have time to look at this... and you think this needs to be fixed... I would like to see something along these lines.
1. The previous menu be the same as previous window (or if that is how its supposed to be) add the command previous window.
2. I don't see the command Switch between GUI and full screen TV/movie. Now I know I could do the same thing with Previous window (escape) and then Jump to full screen but if I use that way, I would need 2 keys. With a toggle button, I could just use one key.
3. I think the Stop playing only works with full screen video. (might need to test this further) So if I hit escape and have the small video playing there is no way to stop this without going back in to full screen and stopping it there. I would like to see this key work more like the B key on the keyboard. Where it will stop any video playing regardless of where you are at.
I want to state that this is in now way of telling/bossing/begging type of crap. You have given us so much with all your hard work. I am a tester of the product and just want to make it the best it can be by reporting back bug/problems.
I want to thank you again for all your hard work… and have a happy holidays!!!
I think I have an issue that relates to the USB-UIRT plug-in. It seems like Previous menu is different that Previous window (escape) is on the keyboard. I assumed that these were the same things even when the names were slightly different. I don't know if this is how its suppose to be or what, but when I use previous menu using my remote and USB-UIRT it does funny things. If I am watching a movie in full screen and hit previous menu it does just that. However, it does not display the video in the corner but the sound is still playing. If I keep hitting previous menu to go all the way to the start screen it removes the buttons on the top. I am talking about the 3 buttons to close MP. The Only way to fix this is to set up the command "jump to full screen TV/movie" with the remote. I hit that and then I must exit out of the video and when I go back to the first screen my buttons come back. I am using the bluetwo skin.
When you have time to look at this... and you think this needs to be fixed... I would like to see something along these lines.
1. The previous menu be the same as previous window (or if that is how its supposed to be) add the command previous window.
2. I don't see the command Switch between GUI and full screen TV/movie. Now I know I could do the same thing with Previous window (escape) and then Jump to full screen but if I use that way, I would need 2 keys. With a toggle button, I could just use one key.
3. I think the Stop playing only works with full screen video. (might need to test this further) So if I hit escape and have the small video playing there is no way to stop this without going back in to full screen and stopping it there. I would like to see this key work more like the B key on the keyboard. Where it will stop any video playing regardless of where you are at.
I want to state that this is in now way of telling/bossing/begging type of crap. You have given us so much with all your hard work. I am a tester of the product and just want to make it the best it can be by reporting back bug/problems.
I want to thank you again for all your hard work… and have a happy holidays!!!
- Thread starter
- #66
Hi ASiDiE,
No problem--I'll have a look at it.
No problem--I'll have a look at it.
- Thread starter
- #67
Igthorn,
Any progress?
Any progress?
- Thread starter
- #68
ASiDiE,
I fixed the previous window bug you reported. It's in CVS now and should show up in the next snapshot. You shouldn't need to do anything as long as you already have the PREVIOUS_MENU action assigned.
Let me know how you make out.
I fixed the previous window bug you reported. It's in CVS now and should show up in the next snapshot. You shouldn't need to do anything as long as you already have the PREVIOUS_MENU action assigned.
Let me know how you make out.