JP1 Remotes

It would be much nicer to see something useful like "XBOX" instead of "CBL" when that item's selected. Is there a way to change the displayed text for this remote?

Yes, you can, but with an extender in the 8910. Handy feature

Ahh, I see, thanks. Looks like the upgrade requires being able to download from the remote (I don't have a jp1 cable & have just been using ir.exe to generate upgrade wavs), so I guess I'm out of luck for a bit.

ElizabethD,
Have you played with an 8910 and it's extender? Any comparisons with the 8810? I was thinking I'd get a second back-up 8811, but the LCD on the 8910 seems like it might be cool to play with.

Best,
jeff

rev. wrote:Ahh, I see, thanks. Looks like the upgrade requires being able to download from the remote (I don't have a jp1 cable & have just been using ir.exe to generate upgrade wavs), so I guess I'm out of luck for a bit.

Creating and loading an extender file does NOT, in and of itself, require you to be able to download FROM the remote, but if you want to retain all of your previous programming, it helps to able to do so.

You COULD create your IR file, add all of your device upgrades to it (for either RM or KM, manufacture all of your keymoves and macros, all in IR) and upload it to you remote via IRtoWAV. If this is what you HAVE been doing, then you already have an IR file from which to start.

You can then also add the extender this way - create your extended IR file from your original, add all of the Custom Mode Name special protocol functions you want, and upload via IRtoWAV.

At THIS POINT, however, you will require some expert assistance. For a WAV upload to work, the first part of the WAV signal is the remote's signature. If that doesn't match, the remote will ignore the rest of the upload. The extender RDFs all have a different signature than the corresponding unextended RDF (Even when you upload an extender file via the cable, IR asks you whether to ignore a signature mismatch) so your remote won't accept an extender WAV upgrade UNLESS you manually modify your IR file before it's converted to WAV to have the same signature as the unextended remote. I have never tried this, but have been told that the "signature" per se, doesn't really matter to the extended REMOTE, but it's a way to help IR distinguish between the different memory maps.

If all that seems like a lot of work, then just get a cable.

For Liz: I have an 8910 and two HTPros (same remote, but with IR/RF "command center") and the custom mode names are indeed helpful (and pretty cool) - especially when I have the remote screen display "Windw Shad" for my power window shades.

In my 8910 and HTPro I use custom name & I, too, think it's cool
A while back, I had all devices named. But as soon as space got tight, one by one I got rid of some. At this point I just ID two devices to avoid confusion due to 2 receivers(Panasonic, Denon) and 2 DVD/CDs (JVC, Panasonic), so one in each pair is named, the other is default designations. Not good enough.
I may be making this up, but I think Grovestine ,of What and Why fame, has a way to have variable length names not wasting space, but I haven't looked into that one. It might help squeeze in more short IDs.

greenough1 wrote:Have you played with an 8910 and it's extender? Any comparisons with the 8810? I was thinking I'd get a second back-up 8811, but the LCD on the 8910 seems like it might be cool to play with.

I don't know 8810. Isn't that the famous remote used by EVERYBODY who knows ANYTHING here?

8910 has LCD, the best debugging tool for key sets and dev_XXX commands I can think of. But macros are slooooow. Vastly improved with tthe extender, but even here I can see the difference with Cinema7 also running under extension which is superfast.

I like it enough that I got me HTPro so bottom line is - it's great.
The extender is fabulous. Imagine the joy of nesting macros deeper and deeper to the point of utter confusion

Thanks ElizabethD,
On the 8811 (I mistyped in my previsous post as I meant 8811, not 8810), I run the extender so I know what you mean about fast. Many of my devices are slow to respond, so I had to slow things way down. I think it was you that helped me out when I was dumbly running into the 15 (forget the exact number) instruction limit.

Best,
jeff

ElizabethD wrote: But as soon as space got tight, one by one I got rid of some.

What do you mean "tight"? I have 6 bytes of keymove/macro space and ZERO bytes of upgrade space left - WITH the extender!

I may be making this up, but I think Grovestine ,of What and Why fame, has a way to have variable length names not wasting space, but I haven't looked into that one. It might help squeeze in more short IDs.

I believe that you don't HAVE to fill in unused positions with $20s (blanks) in Custom Mode Name keymoves, BUT I also believe that sometimes the second line may just display gibberish if you don't and leave it all blank.

Capn,
I have 34 bytes upgrade , and I thnk the same keymove space left, so I can still play with stuff
Custom name: the bottom line (setup codes) was an issue so I had to fill.

How do u set your own label ?

lowspeed wrote:How do u set your own label ?

What remote?
For 8910 instructions are in CustomModeName.txt that came with the 8910 extender.

I used IR from v5, have not used v6 for this and actually I don't see Custom name in the drop down list (I might be using old RDF, not sure).
Using headings from IR6, you need to end up with a keymove such as this Now when a AUX device macro uses shift-M3 keymove, it displays "DEN 1204" instead of AUX with "1204" on the second line.
If IR won't convert and if you don't feel like doing it, use Extender Code Calculator where you can type in the words and it translates the Ascii letters to hex values.

{deleted}

Ok is here my attempt to change label of cable to test

just doesnt work

what am i doing wrong ?

Please just upload any files you want looked at to the diagnosis section and post a link in your message. It is very difficult to deal with them in the body of a post.

Just wanted to say thanks for the help. The extender seemed to install just fine (by wav file) without any special prep work. The only optional protocol I installed was the custom mode names one (which works great), but I found that after the install button presses were frustratingly unresponsive and slow for some reason and I ended up uninstalling it.