Now we're talking! Random thoughts after a successful setup!

Hi Dave
is there a server variable for the accelerometer on the remote?
I found one for charging and battery life but nothing to show the remote is in use

and how about presets what is that used for?

also a bug if I go to server variables and type in av_47 to narrow down all the variable for my receiver
the last variable in the list is hidden by the frame around the list. If I type the full name I can see it av_47_volume

Thanks

Sat32 wrote:

Hi Dave
is there a server variable for the accelerometer on the remote?
I found one for charging and battery life but nothing to show the remote is in use

and how about presets what is that used for?

also a bug if I go to server variables and type in av_47 to narrow down all the variable for my receiver
the last variable in the list is hidden by the frame around the list. If I type the full name I can see it av_47_volume

Thanks

I haven't looked recently but I don't think there is a variable for the motion sensor as it reports to the OS super fast with very little movement needed.  That would spam the whole network and make it all very slow response.

davep wrote:

I just released a SmartRemote template update that 

1) Adds sample pages for XBox and Playstation. These pages assume you are controlling them via IR and the IR models have the names XBox and Playstation appropriately. The server that was just released adds XBox and Playstation as known sources and will create activation macros for them. NOTE: you will have to edit the activation macros to specify what IR device is controlling the player. The macro has comments where this has to be done.

2) Turns on SmartRemote hard button repeats for the 4 cursor keys, the volume up and down buttons along with the channel up and down buttons. If you press and hold down these buttons they will start repeating at a rate of about 4 per second. The change was made in the SmartRemote.js file. If you update the Designer and then update your SmartRemote project you will pick up this new javascript file. Depending on how it is cached it may be necessary to flush the cache on your SmartRemote.

Consider this an experiment. Let us know how it performs.
 

I created an IR model and named it PlayStation. I then created a new source in Sources & Apps called PlayStation and designated the type of source as the new PlaStation addition. I also went into Sources & Apps by room and added it to Theater (the name of my room).

The system accepted all of this but did not automatically create a new activation macro. I noticed that the new sources type is called PlayStation and was careful to name the IR model the same but I'm not sure if this is important. Thoughts? Perhaps I missed a simple step here?

David Li wrote:

Hi Nillaz
Glad to hear you are really getting your custom system configured!

re: Long Press...I suspect the ability to send a LONG press to a device is based on that devices protocol. Does it accept a long press from an IP connected controller? Can you provide a real use case? re: you might be trying to get into a submenu...but what you REALLY are trying to do is invoke an action IN that submenu. Maybe that is discretely possible by a new command....that could be assigned to the myDesigner defined long press command.
 

I can't speak to the Shield, but the Roku uses long press to bring up a context menu.  For example on Youtube will bring up a menu where you can select between things like viewing the channel, subscribing, etc for the highlighted video.  Each channel can implement whatever it wants for these context menus, it's not something common across the Roku, it's not even common across all context menus within an app (Youtube has a couple different context menus), so it's not something where there's a discrete command you could call.  The Roku interface supports keydown and keyup (ie press/release), and while I haven't had a chance to dig in yet, I believe the apps look at the time between keydown and keyup commands to determine if a long press was received.

My tentative plan is to make a macro (or just embedded command) in myDesigner which sends keydown, waits a bit, and then keyup, and assign that to either an extra button, or maybe a long press.  Which would work but would not necessarily be intuitive, especially "stacking" a long press on the SmartRemote and then having to wait for the macro to execute.

I think an "idea" long term solution would be to have 3 "modes" for buttons.

1. The current mode, where the SmartRemote determines short vs long press locally and performs programmable commands based on that.
2. Repeat mode, what Dave just added for the navigation buttons.
3. Keydown/Keyup mode, where the SmartRemote executes one command on key down/press and another on key up/release.

I realize it's probably a fair bit of work, and there are definitely potential workarounds, but those three modes would allow the SmartRemote to better emulate existing controllers.  For example I'm not sure (and I suspect not) that repeatedly sending the Keypress command to Roku would work as a long press.  I imagine that needs to see a keydown and then keyup command.

I just modified the AndroidTV and Roku drivers to support a Longpress command.

For Android ADB has a native longpress command. I tested a LongPress|Home and it worked.

For Roku Longpress is implemented as a KeyDown,  wait 1.5 seconds then KeyUp. Not sure of the timing. It might be too long or too short.

Let me know how these commands work.
 

davep wrote:

I just modified the AndroidTV and Roku drivers to support a Longpress command.

For Android ADB has a native longpress command. I tested a LongPress|Home and it worked.

For Roku Longpress is implemented as a KeyDown,  wait 1.5 seconds then KeyUp. Not sure of the timing. It might be too long or too short.

Let me know how these commands work.
 

Testing this now and LongPress sends commands to the Nvidia Shield. However, the Center command doesn't result in the context menu opening. On the Shield it performs the same action that you would get with a regular short press, so it looks like the timing might be off. Is it possible that this might be adjustable?