Hi All,
We're doing are first MXnet project (finally!) and we're needing to use it to pass IR to devices.
I'm confident of the process with the v2.x modules. My question is what is the experience with P+H functions like TV volume, or Guide control (P+H the Up button to have it continuously go up...)
I know that I can use an OSC to retrigger the command string...
What are peoples' experience with this, and has anyone found a better way to deal with it?
Most importantly, how is the client experience with it??

TIA!

TBH, have done quite a few of these guys and never run into a P&H issue, but it makes sense.? All the projects we have dealt with usually feed TV audio back into distribution so its always just a matter of turning the TV on and a local Apple TV or something.? I'm sure there probably is a project or two where we had to use a P&H though for whatever reason and it has worked fine without even thinking about it.? For all intents and purposes, the IR commands, at least for Samsung and Sony displays have worked exactly like they would from a Crestron driver.

As I think about this also, since the new Apple TV OS update kind of jacked some P&H stuff up.? We have rolled in the throttle on the commands and it has worked just like it has from a standard Crestron IR control.

Good to know!!
Just to clarify, My concern with P+H is not for example the recent ATV OS issue where you need two commands (Press and P+H) on the same button.
My concern is when you need a repeating command on a P+H like volume...
In using the IR module in the suite that CCi built, Are you using the Digital Inputs with string in the parameters, or an SIO/AOS into their serial Input?

TIA!

Have used this combo a few times, volume control is a little slow but haven't heard clients complain.

Started doing some testing with IR thru the MXnet devices.
An issue that I see (not specific to MXnet) relates to the recent issues we found with the Apple TV. ex: the Select command does 2-3 things with a short press vs a P+H.
This issue here is that the Apple TV responds differently to the length of the SAME command.
With MXnet being essentially serial, I haven't found a way to recreate the P+H function, and my testing of extended commands do not find any discrete commands that call these add'l functions...

Any ideas??
I'm curious that Crestron is doing with their IR driver commands when you P+H an input...I.e. what's the driver/port doing with the command string???

Also, Geoff Reynolds, I sent you an email on your private account...

Instead of using the AppleTV IR commands drop in a simple Sony universal blu-ray set instead. ?Next step on the ATV go to settings then remotes then learn remote…name it whatever you want at that point in the ATV. ?This will give you the opportunity to teach the ATV a MUCH more comprehensive set of IR commands than available on the standard ATV module. ?It also had a separate instance for the home and the home home command. ?It is very reliable and persists through ATV updates just fine. ?The ATV is a simple device most often only needing simple controls…don’t over complicate it :)

Unless I'm missing something, the issue is that there's not specific, discrete commands for the Press, P+H, Keep Pressing and Holding - These are three different functions.
With the Crestron IR this works because P+H'ing the digital triggers are doing *Something* with the IR (similar to P+H on an actual remote).?
I'm trying to understand what Crestron is doing to transmit that command when P+H'd, and then emulate it with the 'serial-style' system of AVPro and others.

Does anyone know what is happening to the command string when you P+H the Crestron IR Driver??

开云体育