Crestron processors definitely do support DST offsets. When you set the time-zone, DST is automatically factored in. On 2-series, this was done via the CLOCK symbol. For 3 and 4-series, you can use th

Definitely agree with Jeremy and Eric... I also find it helpful to assign joins so that the last digit matches what I'm using it for. So, for my source and destination signals, src1 might be at join 4

Do yourself a favor, and under-promise on how awesome/perfect it will be. If you try to make the camera shots really tight on one person, it'll often be not quite right, and you'll spend a lot of time

SETL 0 That's the command Lincoln was referring to. Sets the auto-log-off time of a processor, in minutes. Zero turns the function off. -- Josh Winn The LiquidPixel Group

I had an issue recently that's maybe similar. On the suggestion of others, I added to my s+ a local string variable. Assigned the incoming string to the local variable, then did whatever other process

Hey Tim, Not sure why you're having trouble. I just downloaded the files from this group and ran the demo program and it works correctly for me. You definitely should not have to add fake feedback to

Matt - make sure you've enabled "Simple IP Control" or something like that within the TV's menu. -- Josh Winn The LiquidPixel Group

Hey Tim. Are you getting successful video routing, but just no analog routing feedback? Are you sure you have all of the serials toward the bottom of the module defined, and getting good strings for t

You'd need to use the Biamp Generic Control module within your SIMPL program (it's part of the Tesira package from the application marketplace). I forget why, but the Biamp State Control doesn't work

We usually do "signal present" indicators...less traffic to the panel. -- Josh Winn The LiquidPixel Group

If you're looking to get started controlling NVX from SIMPL, I just uploaded our entire suite of modules for this. Just search the files section for "LiquidPixel NVX Control Suite" There's a SIMPL dem

Not exactly, but if you've ruled out actually programming issues, it's probably time to initialize the touch panel and send a freshly compiled project. -- Josh Winn The LiquidPixel Group

Yep... exactly as Brendon said. It sounds a bit convoluted, but once you see it in a folder structure, it's not bad at all. Also, make sure you have the source names tied to an MSP (or a touch panel)

Yeah, it's nice to have your crosspoint joins match your touch panel joins, where possible (at least it helps me keep things straight). But there are usually some other things that need to go over the

The signals you need are on the top level of the device definitions for NVX when you add them in SIMPL. You'll also need to enable Automatic Initiation on the devices. Here's a screenshot showing an e

We use streamLocation strings for routing, instead of subscriptions, since it's less time configuring devices. But it's a little more programming if you want to drive routing with analog values. So if

Yes. Have seen the exact same behavior. I don't know the cause though. I usually do an INITIALIZE at that point. Not really sure if that is helping, but it doesn't seem to happen for a while then. Or

Yeah, I'm using AutoHotKey for basically the same thing! 1 second (1000) is plenty for that delay, but it's not necessary to unregister it first. That happens when you kill the program anyway. I'm usi

Here's what I've found by aggregating this thread and some others, and from my own testing. Feel free to copy this into a .txt if you want to hang on to it (Courier font will keep the alignment). And

What's the current best practice on stopping the program (so you can load new code)? I've been using... PROGREG -p:1 -u KILLPROG -p:1 But I see an old post where Dave H recommended... STOPPROG -P:# PR