Jump to content


c4Forums Member
  • Content Count

  • Joined

  • Last visited

  • Days Won


jackstone last won the day on March 9

jackstone had the most liked content!

About jackstone

  • Rank
    Control4 Guru

Profile Information

  • Gender
  • Location
    Quebec City, Canada

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. You mean, the mixer, not the driver? Can't tell for the US but here in Canada we buy them at inMusic Canada at dealer price.
  2. Crappy decoder exist but this is not usually the cause of a sluggish system... To keep thing responsive, check those brief advises: What to do in large project: - Get most of the config on hardware, not software: Try to put more decoders on the same channel. You don't have to set every decoder to a separate channel if they will be controlled a single group of light you want to stay together. I usually use separated decoder for load balancing for if 3 decoders is needed to control all the low voltage can light in the room, the three decoder will be set a the same channel and thus only one DMX Dimmer driver is needed to control the load in the project, try to avoid using group or scene if the loads are always controlled altogether. You can take advantage of the three channel RGB decoders that way, by overlapping some channel you can connect more loads to be controlled by the same channel, this is by far the most optimized way to build a DMX system for homes, I've done a 15 000 sq ft home with just over an hundred DMX channels, and the whole home is low voltage DMX lighting, and the system is ultra responsive. - DON'T put Group Dimmers in Scene (NEVER do that!) Everyone do that, please stop! - Try to not use C4 Scenes in general, if possible... Try to use Group Dimmer instead, as much as possible, but not in scene, hope that make sense. Scenes are great in smaller project though, and they will react perfectly synchronous. - Try to use Sequential group in any of the group driver (even Effect Switch), if possible. this is highly optimized and will always react quicker than a large random number of channels. - Don't run too many fast RGB effects at the same time (unfortunately, this require lot of commands to be send to the DMX Engine and may slow down the system a bit). Slower color changing effect are highly recommended and those will impact way less the overall response time. - Try to take advantage of the Hardware Scene on the DMX Engine, you can "Snapshot" the current state of a range of channels and save it to one of the 64 built-in hardware scene, recalling those is lighting fast, perfect for all on/off or some commercial project. - If Navigator feedback is not that important, you can enable the High Performance Mode from the DMX Engine driver, this will prevent any bidirectional communication and speed up a lot the system if it is used for driving a large number of color changing effect or if it is the kind of project that run autonomously. Don't do that if you're dealer with a customer that constantly look at his phone app and call you if he see a light ON in the app that is not really ON in his home. - Disable Polling in the DMX Engine driver, it help a little to speed up the system, but not a lot. It is use only to monitor the communication with the DMX Engine and also to keep track of the current DMX light state to bring it back after an outage, it's far from being 100% required... Sorry for the long post. Hope that'll help...
  3. I don't, you should ask the Blackwire staff about that. As for the DMX driver, I did not add any code to enable auto-update because I don't want this to happen. How many time you had a device that auto-updated in the night and half the stuff was not working anymore the next day? (Think AppleTV ) So no, I'm a proud fan of the If It Works, Don't Fix It, especially with something like Lighting Control, that is much more mission critical than a streaming TV service.
  4. BTW there is a new version of the Advanced DMX Driver released a few day ago on BlackWire, this version fix every single bug submitted by all of you over time, it also improve the ColorChanger driver a bit by separating it from the Color Wheel driver. So if you have a lot of RGB lights in a room, you will not clog up your project with a tons of camera drivers. You can now use the Color Wheel to control up to 8 RGB lights, you will select to light to control using the camera preset buttons. If you prefer to keep the preset button as color presets, this is still possible. Next big thing is the added compatibility with the Janus Colour Wheel driver. This is by far the best color wheel driver available right, we worked with Janus Tech to add a true native integration of our DMX driver to their Color Wheel to insure ultra fast response time and accurate feedback. This ColorWheel also work with our Tunable White Dimmer and allow setting the White Temperature using a nice interface. Take a look: https://janustechnology.co.uk/products/drivers/type/lighting/colour-wheel-for-control4/ Yes this is a WebView driver that is supposed to work only on T3, but it's actually really easy to get it to work on mobile phone using a simple URL shortcut on the customer's phone desktop, and it work really well!
  5. There is always a way to optimize large DMX setup by following some best practices, I can help on that, and the result will be zero lag, trust me.
  6. Yes I got the email and the new driver, it seems fine, will confirm once I get back on the job site but i'm not worried. Thanks!
  7. This driver miss the Analog Out (RCA) for zone 6 and 7... Possible to add them?
  8. Just like Savant does with their ip audio stuff... add an amp, get more streams...
  9. Would be nice to see an IO Extender v3 to be released with audio outputs, to put along side the CA-10.
  10. FYI this was caused by a bug in version 2.2.1, it has been solved with the latest release of the driver.
  11. I really not see the point of the CA-10... Dual power supply??? But only one power input??? What? after 25 years working with enterprise servers, there is no feature more needed than two power supplies connected to two different UPS, preventing downtime when one UPS dies...
  12. It is presented as 2 audio matrix. Within C4 limitations, the best you ca do to control Master and Mic/line is to create a separate room and bind the endpoints accordingly... This look odd in Composer but make lot of sense on a T3, I usually automated stuff using an experience button that look like a Mike, the user select the mike and I usable all the rooms bound to the Denon to provide a "Mixer-like" experience when the user select the audio zone control on his T3. I just want to prevent him for having to "add room" to a zone, which does not make sense for that use case. Hard to explain but hope it make some sense...
  • Create New...