When I transformed a ProntoEdit 2000 file to a RC ProntoEdit 6000 file, the volume control codes for the Denon AVR-5800 lost their sustain nature. Each press of the v/c up or down button only moves the v/c level by one digit, no matter how long you hold the button down. Teaching the v/c codes directly into a new Pronto 6000 had the same result, regardless of how long I held the v/c keys down on the Denon remote. Can anyone tell me either how to solve this problem or can anyone please send me a set of Denon sustaining v/c codes that work in the RC Pronto?

Just a few suggestions you might try for better luck in learning codes:

B7-09 How can I get the Pronto to "hold" a button for several seconds in a macro?

Or this quote from THIS link:
"You can forget the instructions about "laying the remotes on a flat surface 4 to 8 inches away from each other..." -- that is pure hooey. The IR sensor in the Pronto is subject to the same room bounce (multi-path) as any other IR sensor. A learning IR does not have the advantage of a particular device IR in knowing exactly what it is looking for. I have found the best trick is to make a 3" long tube about 3/4" in diameter out of black construction paper and tape. Make 4 slits at 90 degrees to each other, about 3/4" long in one end, and flatten out the four tabs thus created. Tape the tabs onto the Pronto around the IR sensor, with the tube sighting into the IR sensor. This eliminates room bounce ("colaminates the signal"), and gets rid of interference from CRT's etc. I have also found that having the remote to learn more like 12" - 24" from the Pronto is better (I believe the intensity is too high from the average remote at 4" -- makes sense, they're supposed to work from dozens of feet.)

With the tube in place and holding the remote further back, I found my ratio of good learns to bogus learns dramatically improved. Also, once you get used to it, you can be in just about any light environment and just hold the Pronto in one hand and the other remote in the other hand (well, assuming you have two hands, sorry if that is ignorant). Try it -- it really helps the learning. "

And finally:

B2-07 How can I tell whether my learned codes are "clean" or not?



MIKE

Thank you MrKlaatu.

The problem luckily cleared itself up and the next time I taught the volume control codes, they worked perfectly. Perhaps there was a little room bounce or dirty codes the first time. However, that doesn't excuse Philips for not being able to convert a perfectly operational set of TSU2000 codes into Pronto Pro codes. I will try the black tube next time.

By the way, is your screen name a reference to "Klaatu Barada Nikto" from "The Day The Earth Stood Still" or from the rock band or is it simply your name?

I have wondered that myself... Mr. Klaatu.

Your codes were probably on the dirty side, and subtle timing differences between the units might have made the difference. I really don't believe that Philips should be expected to ensure that borderline codes work from model to model or software release to software release.

I can remember when upgrading from ProntoEdit 1.04 to 1.05, Philips improved some IR performance, but it did mean I had two codes that wouldn't work any more - relearning them fixed it. I also had to increase some delays because they got it to work faster.

This message was edited by Peter Dewildt on 02/07/02 01:22.05.

                

This is KLAATU. He is completely human in appearance. He is above all an impressive man -- a man of tremendous dignity and presence. He has the tolerant superiority that comes with absolute knowledge.

That's my good buddy Gort on the far left    Gort! Deglet ovrosco!

This message was edited by MrKlaatu on 02/07/02 04:43.17.