I am fairly new to RTI and am running into a little problem. I have a T3 that will have 2 different volume controls and mute buttons (1 for microphone and another for program audio). When Mute is pressed I would like it to stay in the active state until unmuted. I went to try to do this through macro programming but can not do page jumps through macros. I can program different pages to reflect the button status but run into the same problem with having both mutes pressed. Any insight would be greatly appreciated.

Here is a screen shot of the panel. Notice that the heading is Cable and the cable button on the left is yellow not green, I want the same thing to happen with the mute button. The rectangle on the bottom is just a place holder for a company logo to be added later.

FAIK, you can not change a button state based on a flag.

I have requested this before, as I'm used to doing this since I'm a crestron guy. We could also do that with variables on the MX-3000, last I looked.

Requested this from RTI a while back, but never got a response.

Hopefully we will see more features like this when we get 2-way features.

FYI, you can change pages in a macro if you make the button containing the macro a "Stand Alone" button. In stand alone mode, you would have to call a system macro from inside the button macro in order to send rf commands. otherwise, all commands sent in the macro will be direct IR from the front of the remote.

Thank you, I will give the Stand Alone approach a shot.

You can't directly, but there is an easy workaround.

1. Create two flags- Mic_Mute and Prog_Mute;
2. Create four pages- one with both mute buttons in the unpressed state, one with just the mic mute in pressed state, one with just the program mute button in the pressed page, and one with both of them in the pressed stage;
3. Start with the first page (the one with both unpressed). If the mute button is pressed, set the Mic_Mute flag and jump to the page with this button in the pressed state. If the mute button is pressed from the first page, set the Prog_Mute flag and jump to the page with this button in the pressed stage.
4. From those pages, test the Mic_Mute and the Prog_Mute page to see which page you need to jump to. Page jumps can be inserted in a button macro.

CJ

suggestion: easy on the drop shadows, they hurt my eyes.

Davenport - I know but the customer likes and I know in a month or two I will be back to change the buttons with text to not have the drop-shadows so I am duplicating the files with one that only has the shadows on the outside of the button and not on anything on the button.

Heads up!
Based on your screen shot, you will need 4 pages for each of your 5 source pages (20 pages), if you also want to show the selected source as well as the mute status.
I did this with a 3 zone, 3 source selection page, and ended up with 32 pages.

estech is correct 4 pages per source. Got the mute status going fine even switching between sources the status is correct.