369006 New Remote URC-3660

[HamburgerHelper1]

I actually like naming it "LKP" I was just thinking of others.
Your "Held" idea is pretty good too since User manual sometimes state "Hold" Setup until the LED Blinks twice"
But for our use "FFwd_LKP" and "Rew_LKP" works for me

[MrMoody]

I'm good with LKP. It's pretty obvious once you run across the term in the forums or documentation. Could add a short line about it to the Notes.

[mathdon]

I would vote for (Held) rather than LKP as it has a clear meaning for users not familiar with this abbreviation. I would also vote for alias names "next track" and "previous track" for short (unheld) keycodes and "fast fwd" and "rewind" for the held keycodes 71 and 72. My intuition is that a user wanting to fast forward or rewind is likely to hold the key for longer than one wanting just to skip to the next track. We don't know whether these codes are used consistently in built-in setups, or whether the symbols on the keys (which are those normally used for fast fwd and rewind) correspond to a long or short press. As far as I can see, the manuals for all the remotes concerned (3660, 3661 and 3680) make no mention of long or short presses of these keys.

[HamburgerHelper1]

Graham's solution make more sense to me and I agree that the codes may not be consistent with the other built-in setup codes

[mdavej]

I second Graham’s solution.

[MrMoody]

All good with me, only the "Held" and the next/prev track aliases which I agree should be added are any different from what I've been saying.

[HamburgerHelper1]

Graham would you please look at these files. For lack of better description i'll call it macro work around What i'm working on is a timed DSM on the App key
All of my DSM'S Work
Use this RDF to look at it

http://www.hifi-remote.com/forums/dload ... e_id=26527

Also i will give you one of these remotes if you like


http://www.hifi-remote.com/forums/dload ... e_id=26526


http://www.hifi-remote.com/forums/dload ... e_id=26524

[jeajea]

hamburgerhelper mentioned putting functions on the backlight button.
The backlight button appears on the layout tab and appears to allow you to assign a function.
However, it doesn't appear on the button or keymap tab even if you assign a function to backlight.
Backlight is also not in the list of available keys in the add "new" window of the global macros tab.
My guess is this is a RDF issue.

[mathdon]

My guess is this is a RDF issue.

It never occurred to me that functions could be assigned to the Backlight button, so I specifically blocked them. To remove the block, just delete the ":All" at the end of the Buttons section, so the Backlight entry becomes just

Code: Select all

Backlight=$3C

[jeajea]

Thanks
I made the change.
DSM on backlight works.
Global macro on backlight works.

[mathdon]

Graham would you please look at these files. For lack of better description i'll call it macro work around What i'm working on is a timed DSM on the App key
All of my DSM'S Work

I see that you have gone back to the previous RDF that supported Controlled Macros, support that I removed because you said that they did not work. What you have created on the App keys are not Controlled DSMs but Timed DSMs, though I think you know that. I'm not sure how you did that, as RMIR currently does not allow it. It may seem as if it should be a simple task to allow that, but it is not. It is also why RMIR allows editing of Timed Macros but not their creation, it is not a simple thing to do. I will think about how it might be done and report again.

Many thanks for your kind offer to send me one of these remotes. They are not available here and it would be helpful, but out of fairness I will only take up that offer if I think that I can meet your wishes over these Timed DSMs.

[HamburgerHelper1]

Yes i know they are timed DSM.
Its been a fun ride
Since the apps would not show up i took your RDF from v2.14.2 and deleted App3 from
ControlledMacroBind then buuton 2f showed up like i expected it to.
From there i made timed DSM even though box states controlled DSM.
a backdoor hack if you will.
Mainly im just showing that it appears possible to have Timed DSM in this remote
Which makes this remote even more powerful
I should note that I had to use v2.14.2 to get the ball rolling because the RDF with missing app3 would not work in RMIR.v2.14.4

[HamburgerHelper1]

I have working Timed Macro's on all 3 App buttons with these files just made 3_31_22 maybe they will help to understand what is going on in this remote.
Graham if you don't want to pursue it that's fine with me whatever is best for everyone else.
To recap my hack I deleted App3 from ControlledMacroBind then button 2f showed up.
I made timed macro on it and it worked. Since I only had button 2F to work with I cloned the timed DSM to make the next one. When I made the last one was when I ran into some trouble The Macro worked but i could no longer Open the saved IR file i made nor could i download from remote. So thinking about it I put App3 back into the RDF and it now opens file and downloads remote. Maybe this in itself will help you understand what it is doing.
Like i said if it is too much work to pursue this i am fine with it. Ill just use my hacked way of doing it. It has been fun for me anyway

http://www.hifi-remote.com/forums/dload ... e_id=26529

[mathdon]

Graham if you don't want to pursue it that's fine with me whatever is best for everyone else.

I like a challenge, so have been working on it and think, subject to more testing, that I have got it sorted. But you too will have work to do , as it raises further questions. I am allowing Real-time macros and DSMs to be created on shifted App keys, for example, which will need testing to see if they work.

As I am able to meet your wishes on this, then if your offer still stands, I would appreciate you sending me one of these rather interesting remotes.

[HamburgerHelper1]

The challenge is fun isn't it.
I was planning on shipping the remote this weekend to you anyway
Will it only work on shifted keys or will non shifted keys work too?