Need help adding new codes to your Slingbox, this is the place to ask. You're welcome to ask general Slingbox questions here, but be aware that most of us are not Slingbox experts.
Remember to provide feedback to let us know how the problem was solved and share your upgrades.
Tip: When creating an upgrade, always include ALL functions from the oem remote, even if you never plan on assigning them to a button. Complete function lists makes an upgrade more helpful to others.
Decided it might make more sense to simply post the PROTOCOLS.INI that I use, which includes all the newer protocols and all the 'no repeat' protocols. Acts as a back up for me if I ever lose the original
Wonderful - thanks a lot! I will give it a try tonight. In the readme.txt I am encouraged to communicate if a particular remote image matches well. In the Sling device directory, the "Kabel Deutschland AG" device called "DVR20" has an image of the exact remote that sits on my coffee table.
Not sure if that info helps but I thought I'd put it out there.,
- In principle it works (yay!)
- Instead of jumping one item of the list when pressing an arrow key, I now have to press each arrow key twice to have an effect. This is much more workable than the situation with the jumps so if that's what it takes to get it to work, I'm perfectly happy. If you have the ambition to get it 100% right, I'm happy to do further testing
- Not sure what to expect from the "realistic image" in the 2nd post. Should I be looking for an RC that looks exactly like the one on my coffee table (and in the DVR20 of the Slingbox directory)? That is not the case. To me, it looks as generic as the previous one (V2010_PL) and works just as well. Both files work fine with the above constraint.
Thanks for the pointers. I have a 350 and made sure I selected the manufacturer correctly. Thought I had done that yesterday but I tried again today and it works: I now have the realistic image.
Everything works now with the constraint that I have to press each arrow button twice to jump one item (before, pressing once jumped 2 items). Not sure if you'd like to do anything about it. In any case: I appreciate your help!
Well all this started with me building you a non-repeating remote to cure a double skip. So why don't we try reversing that and going back to a repeating protocol ?
alanrichey wrote:Well all this started with me building you a non-repeating remote to cure a double skip. So why don't we try reversing that and going back to a repeating protocol ?
I hate to say it, but this version does the skipping thing again (press arrow key twice, move 2 rows or columns in the navigation). As mentioned before, yesterday's version requires pressing an arrow button twice to yield a move by 1. Some sort of middle ground would be the ultimate behavior but as I said before: I am happy with yesterday's version as well.
By the way, I made an interesting observation just now: As I mentioned, e.g. pressing down twice moves the cursor down one step. Out of curiosity, I tried down/up to see if the commands cancel each other out or something along those lines. What actually happened, was that the cursor always moved in the direction of the 2nd push. Pressing down/up moves it up one step, pressing right/down moves it down one step - you get my drift. It is almost like the first push initializes something and the second one executes it. Forgive my certainly amateurish lingo but I thought that the observation is somewhat systematic and may be able to help you pinpoint what's going on.
In a couple of days, I'll have time to make an executor that sends exactly two frames. That may fix your problem, or the problem may actually be related to the toggle bit in the Nokia protocol. Depending on everybody's patience, we should eventually be able to tame this.