Jump to content

the_darkness

Members
  • Posts

    6
  • Joined

Reputation

10 Good
  1. Been using iCue for a while now and, despite some of the bugs and crashes, I'm generally very happy with it. However, the number of components that support audio lighting (not CAV) seems limited to basically fans and light strips. Why not the DIMMs (at least the Vengeance Pro RGBs, not sure about Dominator) and keyboard? For aesthetic builds that have a lot of lighting, RAM is literally the focal point as it is right in the middle of the build, appears (IMO) brighter than most other components and is screaming out for this functionality when audio lighting is in use. Third-party software like RGBeat is able to make them dance pretty well, so it would stand to reason that, after years of development and at least 3-4 Kernel changes, Corsair could add that as well. That being said: 1. From a development perspective, are there challenges with adding the audio lighting to these components? 2. Why does the K100 (and others) only get to use CAV and not audio lighting?
  2. The K100 RGB media controls, Spotify and iTunes only have track up and down, which is why track jogging on the control wheel is probably the best feature (+15 secs in Spotify and +5 secs in iTunes). The only other way that I know of to accomplish this is with mouse clicks. I listen to a lot of EDM and when searching for new stuff, I only need to hear a few secs of the hook, groove and bridge to know if I need to invest any more time listening and, having CTS, all that mouse movement and clicking is killing my hands (gotta save 'em for gaming). Mouse wheel up/down or an assignable button would be perfect, but there does not seem to be a way within iCue to assign the track jogging feature to a button and macro recordings do not capture any input from the control wheel. Is there any way at all to assign the track jogging feature to a button or through a Macro? TIA, apologies if this has been discussed before.
  3. That certainly IS interesting as that is exactly what happened. Fans were spinning fine and they adjusted with the perf profiles. As for a bad connector, not likely as it's a brand new braided set, but I suppose I can dust off the multimeter and find out. I've read a lot of posts that also suggest spreading them out too, which is why I originally did that, but if that IS the recommendation, I'd think the hardware or iCue would compensate for it.
  4. So I installed a new H100i platinum yesterday. When I tested originally everything worked. I have a CoPro, a NoCo, the cooler and a RGB fan hub (7 fans in my case). So I moved the cooler's SATA power connection to the same cord as my drives because it was closer in terms of cable management and was thinking of adding a NoPro for additional strip lights. After that, the lights didn't work. Switched back and all was/is fine. On the surface, you'd think power was power and components shouldn't really care where they get it from. So, does someone have a technical explanation of why the RGB's on the 100i won't work if the cooler is NOT on same SATA power cables as the other corsair components/on the same SATA cable as the drives?
  5. Looks like I'll just have to get a USB splitter because the NoCo (RGB hub) apparently can't use the passthrough and has to be connected to the board.
  6. So I have: 4 QL 120s, 3 QL 140s, a CoPro, a NoPro, 1 RGB LED fan hub, 2 RBG Hubs. I do not have any modified connections either, like molex-to-SATA. -I currently have the CoPro hooked up to the mobo's USB port and powered by SATA -The RGB LED fan hub is connected to the CoPro's LED port and is powered by SATA -6 of the 7 fans are connected to the CoPro fan controller ports as well as the RGB LED Fan hub and I've made sure they are in the correct order. -An RGB Hub is connected to the CoPro's LED and USB ports and is powered by SATA. (The RGB hubs that the QLs came with are quite different from the RGB LED fan hubs. This hub has self-contained wiring for USB and SATA and the fan hub has output ports for LED and SATA). All of the fans connected to the fan hub are recognized by iCue and can be controlled. The lone fan on the RGB hub just defaults to spiral rainbow. That setting can't be changed, regardless of what device type I select for the channel. If I swap the 6 over to the RGB hub, same thing - spiral rainbow, no control. Also, when I hook up my NoPro, iCue recognizes it which rules out an issue with the USB port on the CoPro. So, 1. What the difference is between these two types of hubs, other than their physical design? And 2. How do I get the 7th fan to play nice WITHOUT having to get another RGB LED fan hub? Many TIA
×
×
  • Create New...