I'm glad to hear the Pronto team is on top of issues. This is why I decided to go ahead and take the plunge and get a TSU3000. I just got it delivered tonight, and immediately put on the new firmware. I set it up with the default screens, brand programmed buttons, and a few learned codes so far and it seems to work pretty good.

Here is a suggestion that will help make the software more efficient to use. When importing a png or bmp graphic, a window opens containing a list of files in a specified directory. It would be very nice if, instead of a list, the graphics themselves could be viewed similar to the way they would appear in a Photoshop or PSP Browse Window.

It works on mine. You can use the view menu button (small button at the top of the window on the right hand side). Choose Thumbnails. I'm on XP Pro but I think this applies to other OSs as well.

Jon

I went through the effort of inputing .1 sec delays in all my DirecTV channel buttons. This DID NOT fix the problem. Some channels works now and others do not. This has really ruined my Pronto experience....how do I get back to the old firmware? Or, does anyone have any other suggestions? If I put more than 0.1 sec delay, will that help?

Thanks in advance.

Jrexi

It should help if you make the delay longer. Assuming you linked you icons to the keypad buttons you can put your delay after each command on the keypad. This will slow down your button pressing but it will put the necessary delays on all of the icons quickly. Once you find the right delay you can change all of the icons if you want.

Jon

Philips is really dropping the ball here, and I can't believe so many are lemmingly willing to accept this. What's the big deal to add .1s to all your code? Well, for starters this turns the code into a macro, thus makes it un-repeatable. Second, it has me go over my entire PCF file and add this hack everywhere, all of this because Philips can't test their firmware or are unwilling to fix it. I have contacted them separately and the responses I got was far from enlightened, basically, they refuse to admit they did anything wrong with the latest firmware. This just sucks. Lastly, the problem cannot be fixed on some devices, even with the .1s hack, my X10 IR receiver for instance stopped working altogether (or would only accept random codes).

Philips is really dropping the ball here, and I can't believe so many are lemmingly willing to accept this. What's the big deal to add .1s to all your code? Well, for starters this turns the code into a macro, thus makes it un-repeatable. Second, it has me go over my entire PCF file and add this hack everywhere, all of this because Philips can't test their firmware or are unwilling to fix it. I have contacted them separately and the responses I got was far from enlightened, basically, they refuse to admit they did anything wrong with the latest firmware. This just sucks. Lastly, the problem cannot be fixed on some devices, even with the .1s hack, my X10 IR receiver for instance stopped working altogether (or would only accept random codes).


I agree completely. Talk about messed up. I reverted back to the older firmware through no help from Phillips. I could care less about the speed increase with this latest firmware, especially when it breaks so much. I was never unhappy with the speed of the remote to begin with.

-Lowpro

There have been many responses from X10 users saying their commands, even the gradual dim, work perfectly. You might want to double check for dirty codes. I had a couple when I upgraded the firmware..but found them and fixed them. All works well with no .1 second delay.