Look on their website, they have an .exe that'll give you the string for any level, inc, dec, or preset for every channel. I think the URL might be printed on the protocol sheet that's in the box.

Every time I've used them the electricians grouped them in zones by matching the channels, so I've always just used a SIO to send fixed levels, never needing to make a module to handle true FB.

How much time after the doorbell is pressed do you return the system to its previous state? I figure it's very possible that the person at the door may push the doorbell more than once. I don't really want to flip the system back and forth between successive doorbell presses.
________________________________
From: Heather Baiman
Sent: Saturday, February 06, 2016 12:16 AM
To: Crestron@...
Subject: RE: [Crestron] Re: Doorbell Chime

A new client has moved into an apartment that belonged to one of our longtime clients who has since traded up to a townhouse. The new client wants to ring the doorbell through the room speakers via the PAD8. The email below came up when I searched the group for comments on deploying this feature.

Is it really worth 'ramping' the value between the current source volume and the doorbell volume? I'm not convinced this is necessary or beneficial.

I plan to use a MC3 to play the MP3 doorbell files. Is unity gain for the audio out ~80% as it is for the PAD8?

TIA


________________________________
From: Crestron@... [Crestron@...]
Sent: Tuesday, January 27, 2015 12:27 PM
To: Crestron@...
Subject: [Crestron] Re: Doorbell Chime



Im sure many others have probably written their own code or module to do this. I created one that goes between the bipad or swamp, tracks if the room is currently ON,what input on the audio switcher, what the current volume is. It has parameters where you set which input on the switcher is your doorbell source, how long the doorbell should play, what volume the doorbell should play and what duration to use for ramping the volume up&down when the switcher goes between original source and doorbell.

So basically it just remembers what you were doing if the room was already on. Inside the module were DRAM and ARAM symbols, analog inits, presets and rate limiter. A stepper used the parameters and did the following:

Doorbell pressed:
Store current room settings
Ramp Volume Down
Turn the Zone on the switcher
Switch to doorbell input
set doorbell volume
play dooorbell wav
Cut doorbell volume
recall previous room state
If room was originally off, turn it off again.
Recall previous source (if there was one)
Recall previous volume


It works on the couple jobs I used it, I feel like given more time I could have improved it more but whatever.






============================================================================
Please refer to
for important disclosures regarding this electronic communication.
============================================================================

A new client has moved into an apartment that belonged to one of our longtime clients who has since traded up to a townhouse. The new client wants to ring the doorbell through the room speakers via the PAD8. The email below came up when I searched the group for comments on deploying this feature.

Is it really worth 'ramping' the value between the current source volume and the doorbell volume? I'm not convinced this is necessary or beneficial.

I plan to use a MC3 to play the MP3 doorbell files. Is unity gain for the audio out ~80% as it is for the PAD8?

TIA


________________________________
From: Crestron@... [Crestron@...]
Sent: Tuesday, January 27, 2015 12:27 PM
To: Crestron@...
Subject: [Crestron] Re: Doorbell Chime



Im sure many others have probably written their own code or module to do this. I created one that goes between the bipad or swamp, tracks if the room is currently ON,what input on the audio switcher, what the current volume is. It has parameters where you set which input on the switcher is your doorbell source, how long the doorbell should play, what volume the doorbell should play and what duration to use for ramping the volume up&down when the switcher goes between original source and doorbell.

So basically it just remembers what you were doing if the room was already on. Inside the module were DRAM and ARAM symbols, analog inits, presets and rate limiter. A stepper used the parameters and did the following:

Doorbell pressed:
Store current room settings
Ramp Volume Down
Turn the Zone on the switcher
Switch to doorbell input
set doorbell volume
play dooorbell wav
Cut doorbell volume
recall previous room state
If room was originally off, turn it off again.
Recall previous source (if there was one)
Recall previous volume


It works on the couple jobs I used it, I feel like given more time I could have improved it more but whatever.






============================================================================
Please refer to
for important disclosures regarding this electronic communication.
============================================================================

Went down today and swapped the CP3 for a QM-RMC, and email went straight through every time using the same program. ?

Chip,

This happens if you don't put a value in the File_Name_Prefix parameter.? To stop it from happening put something in there.

Someone also mentioned that strings weren't working properly because of an error in this module.? Here's how he fixed it:

At line 193, for the function?Write_String_Array(), the test statement reads " If(Analog_Enable)", but should read "If(String_Enable)". I guess you wouldn't notice this problem if you had Analog enabled but were recalling strings.

If you pulse the FB of the join created in VTPro the entire audio file plays once regardless of how long you hold the button. If you hold it for longer it still only plays once through. If I want it to play again I must re-pulse the input. (I thought it would repeat if held longer but was wrong)

Are the displays or ?projectors HDCP compliant?

I've done a bunch of combinable rooms in my time.? Sometimes they are fun, sometimes not so much.? They usually give you a sense of pride and accomplishment when they work well though, especially the more complicated ones.

Last week, I just worked on a 2x2 quad combinable room that had 6-7 combine possibilities (it was going to be more, but we found out one of the air-walls weren't all the way across and couldn't be opened in all the ways we though it could.? Luckily, these were fairly small functionality rooms, so it wasn't too bad.

Some tips I would give:
1) make sure you know all the possible combine states that will be required, this is important and determins the best method to the whole program.

2) figure out if all the panels in a combined space need control, or if only a master panel will control the larger space.? This changes depending on requirements, but if only a single panel needs to control a combined space, this is less programming, as you don't have to worry about the 2nd or 3rd panel doing everything as well.

4) Find out how you are going to combine everything in the audio DSP (if one) and determine the best way to handle audio.? In other words, when rooms are separate, each room has it's own volume fader.? When combined, do you need to have both of those faders track each other using code, or can you just adjust the master rooms fader.? The answer to this depends on how the DSP configuration is being created.? I usually discuss with the person doing the DSP config ahead of time so I know how much work I have to do.

3) I would recommend NOT using cross points (but this may be a personal choice).? Buffers make things easier IMHO, and are not crazy in these cases, but Cross-points can make some headache of code.? I've worked behind someone who used cross-points on a system, and I couldn't make heads or tails of it without major code study, and even the original programmer was having a hard time making some of the requirements work out, because the cross-points were painting him in a corner.? When rooms combine, they are not separate zones, they are one large room, so cross-points aren't the best choice to me.? Cross-points are better when you have a "1 to many" relationship, or a "many to many" relationship.? This isn't the relationship that a combinable room has in most cases.

4)? for routing, program every source from all the rooms to be able to route to every display in every room from a single buffer (even a disabled buffer to use a placeholder).? When all the signals and routes are setup to route anything anywhere (as an abstraction), then no matter the combined mode, you have signals and code defined for how to route something to where you need it to go.? An example of this would be say there are 2 rooms, with 2 dispalys each, and each room has 10 inputs.? I would create a buffer for a single display that has signals to route all 20 inputs to the single display and the code after the buffer to handle this (switcher code, projector code, etc.).? Then duplicate this for the next projector, and so on, so that you have code pre-defined to route anywhere.? This gives you a generic routing ability that you can then drive from other buffers depending on how the rooms are combined, and what sources are available at any given time.? Not sure if I explained this well or not, but hopefully you get the gist.

5)? If more than 2 rooms are involved, and especially over 3 rooms, then TruthTables can be your friend to determine configurations and what rooms are combined with what.

I usually allow combining to happen "on-the-fly" at any point.? This makes things more convenient for the users.? This way they don't have to shutdown if they decide to open a wall up and make the room bigger.

If there are partition sensors, then great, if not, I usually try to make only one panel have control of room combine states (usually a master panel, or the head of the room, or whatever makes the most sense for the room layout and such.? (sometimes all of them will need this capability, but since it's a function that can screw up other rooms if they are being used, I try not to do that unless specifically requested).? In any case, I usually add buttons that mimic the partition sensors, so that if they add sensors in later, the logic is already there, I just need to drive it from a sensor instead of a toggle button.? So if there are 3 rooms A,B,C,? I will have 2 buttons, one labeled "Combine A&B", and another that says "Combine B&C" that can be toggled on/off.? In this scenario, the middle room B would have this option on the panel and A and C wouldn't, since B is kind of naturally the master room.? If that is to complicated to use for the end user, I have done all the layouts as separate buttons, such as "All Separate", "A&B Combined", "B&C Combined", "All Combined" etc., but then the logic diverges from how partition sensors would work, so you'd have to rework that if sensors were ever added down the road.

Final Tip:? Plan, plan plan, don't paint yourself into a corner.? Abstract as much as you can, so when changes come up (they will), you aren't chasing spaghetti code trying to make it work in all the combine possibilities.

-jason

Sent.

开云体育

Amen!

"Just did an eVision 4500 the other day, the projector is PJLink compatible, save yourself the hassle and use that instead"

That's a little bizarre.? I'm working with an E-Vision 7500 right now, and the protocol is completely different than the snipped the OP shared.

We've been connecting IP through HDBaseT connections off DM/DMPS units with zero issues...

? - Chip

"No. Like I said on my TSW-750 if I pulse the join, the entire file plays. If I hold it high, it repeats as long as join is high."

I think he's asking feedback-wise?? That the join coming in from the touch panel symbol would/should act like someone is pressing and holding a button with that join value while the file is being played back?

I.E., you send a momentary pulse to that join, the file starts playing - while it's playing, the FB join goes high, then returns low when the .mp3 stops...

Just how I read it.

No insight on the Studio issue...? :)

? - Chip

Just did an eVision 4500 the other day, the projector is PJLink compatible, save yourself the hassle and use that instead.

Hi,

Can anybody help me with DM error with the following message?
HDCP ERRORS
OUTPUT 1 - DM OUTPUT UNAUTHENTICATED
OUTPUT 2 - SAME
OUTPUT 3 - HDMI OUTPUT UNAUTHENTICATED

I cant find these messages in the DM tool. Has anyone ran into this problem?
It also keeps loosing the signals on the displays when watching cable.

Thank you