R2 vs R4
vining
Posts: 4,368
I'm wondering what folks who have used the R2 think of it. I haven't yet used one but I am now thinking it would be a better fit in most jobs than the R4. Although I've used R4 in every job since they came out I find that in every new job I'm sending less feedback to them than I did the job before and subsequently I'm asking it to do less and less because of that. So that I'm now at the point where I have almost no feedback at all and just make them control the basic surround system related stuff like a universal remote. The grand ideas that I had when these first came out have long since turned into one dissappointment after another so I'm now thinking what's the point and the R2 has hard buttons for transport controls too, so, why not.
So anyone that is familar with the R2 and the RF receiver I'd like to hear your opinions.
So anyone that is familar with the R2 and the RF receiver I'd like to hear your opinions.
0
Comments
R4s are great if you have the budget and if you need some feedback from 2-way devices. However I have seen these fall off line and take a few seconds to come back.
How do you interact the URC with AMX by IR or did you use an MSC400 to send RS-232 strings to the AMX controller?
Just in case; URC = Universal Remote Control
We used RTI for a remote solution for a particular budget minded project. I would have rather used an R4, I've programmed 15 or so R4s to be used with big systems. We mainly do large scale distribued audio/video systems. Once you know the limits of the device they are great to work with. I think the difficulty is people assume they are a touch panel, which they aren't. I've modified my ARQ, Cable/sat, Radio, Kscape module all to work with an R4 and it works like a charm.
You can't have as much dynamic text sent to it, because yes it will fall offline constantly. If you program around the parameters of the unit...its quite a great solution. Our company due to the RTI project (which came out very well) has decided we will never mix AMX and another manufacture like that again (unless they need a hot tub remote). We use URC for small projects when they come around if the client doesn't want to spring for the big bucks for an AMX system. I like the ability to change the ports and channel numbers, it severely lessens the amount of code I need to write and although I have a different UI module for the device I can have it follow similar ports to my touch panels.
TurnipTruck wrote: Yeah that would be a bummer. I've already spent enough time rewriting code to minimize feedback to these remotes so the idea throwing out that work and rewriting code to accomodate single port multiple device control doesn't sound like anything I want to get into unless the $$ aren't there for R4s.
I the RTI route looks promising and the style is very similiar the the MIO remotes so I think in situation where feedback isn't needed, no movie or song lists it would be more than adequate.
You can't change the channels associated with the remote's buttons.
You could have ten remote with exactly the same functionalities. That's would be it.
A press of a play button on any remote would trigger the same incoming push on the master regardless of which R2 it came from.