We're Fixing this Anti-Consumer Nightmare OpenPleb Sensors & RGB, ft. Wendell from Level1 Techs
video description
ALOT of those Sites have a FEW Years Into this RGB Mess SO They might be a Fantastic place to get some Guidelines & direction on what are the hurdles they have to tackle when going at the BIG Companies to open up ... and if all else Fails GUYS ... MAKE a Wendell & Steve 1 Hour RANT Video and Name Names on Those Companies who wont help & this way the INTERNET can Do its magic just like .... Broken Egg , Ngreedia and Asus... lol Cow :-o)
Date: 2023-06-10
Related videos
Comments and reviews: 19
Sean
Sharing my experience, I tried to build a RGB heavy pc in 2020. Had a Gamdias case, a 12v led strip, Gamdias AIO, some generic 12v RGB fans, Msi board. Tried to stay in the same manufacturer ecosystem. Gamdias' components don't even work with one another. Had to use one controller that came with the AIO and hodge podge connectors from the case and found out I cant use the fan header on the mobo to control the aio becuase the controller for everything wanted to use a little button cell RGB remote for fan speed. So I had to hope the middle fan speed was enough to cool the AIO, and balance case fan noise with it all. And don't get me started on mystic light software on Msi. That steaming pile of dog crap! You couldn't run the 12v header at the same time as the ARGB header, so you had to pick one or the other because the chip that controlled everything was crap even on a x470 board, not some a320 or b350 entry level board. So I chose ARGB since those parts were more visible and expensive, and after 6 months something was screwy with the signaling and I couldn't even use the ARGB header to control anything. So my 12v RGB parts were dark, my ARGB header and software were dog crap, and I ended up using some crappy default pattern for 3 years. After intermittently reattempting to fix my problems over the years, I decided on a new mission. New case, new board, open source software. Bought a x570 asus board (this was right as you did the asus x3d videos and I got a sick feeling like I made another mistake lol), nzxt flow elite case with their crap controller, and went with some creative wiring. Modified a 12v rgb splitter to connect to the ARGB header, split that signal to the deepcool aio I bought, then to the nxzt controller, and the final to a generic argb video card support. I didn't or uninstalled EVERYTHING for all RGB and ARGB software. Got Signal RGB installed, set the Asus ARGB header to a custom component installed with 24 leds (this was the longest numerical daisy chain of the split signal on a single device), and now everything works. I don't get to use case location based patterns, as everything uses the same 24 string long pattern, but that's totally fine. No bloatware, open source (kinda), hacked wiring, and way too much time spent but now it works. Never the way any of the parts were intended with their hardware and software.
TL:DR, Had to learn on a deep level how argb and rgb worked to reverse engineer a solution and had to replace hardware and software and go about it in a completely different way than any manufacturer intended. Crap software, crap hardware, proprietary crap that wanted me to use their controller for everything, lack of integration with legacy connectors, pulling my hair and coming up with my own FU to all of their crap and running custom wiring, exploiting the standard to trick everything into working, and keeping it as open source as possible.
A video to cover this topic and creating a consortium shouldn't have to exist, but it needs to with all of this e-waste proprietary garbage out there. Thanks Steve and Wendell
reply
Sharing my experience, I tried to build a RGB heavy pc in 2020. Had a Gamdias case, a 12v led strip, Gamdias AIO, some generic 12v RGB fans, Msi board. Tried to stay in the same manufacturer ecosystem. Gamdias' components don't even work with one another. Had to use one controller that came with the AIO and hodge podge connectors from the case and found out I cant use the fan header on the mobo to control the aio becuase the controller for everything wanted to use a little button cell RGB remote for fan speed. So I had to hope the middle fan speed was enough to cool the AIO, and balance case fan noise with it all. And don't get me started on mystic light software on Msi. That steaming pile of dog crap! You couldn't run the 12v header at the same time as the ARGB header, so you had to pick one or the other because the chip that controlled everything was crap even on a x470 board, not some a320 or b350 entry level board. So I chose ARGB since those parts were more visible and expensive, and after 6 months something was screwy with the signaling and I couldn't even use the ARGB header to control anything. So my 12v RGB parts were dark, my ARGB header and software were dog crap, and I ended up using some crappy default pattern for 3 years. After intermittently reattempting to fix my problems over the years, I decided on a new mission. New case, new board, open source software. Bought a x570 asus board (this was right as you did the asus x3d videos and I got a sick feeling like I made another mistake lol), nzxt flow elite case with their crap controller, and went with some creative wiring. Modified a 12v rgb splitter to connect to the ARGB header, split that signal to the deepcool aio I bought, then to the nxzt controller, and the final to a generic argb video card support. I didn't or uninstalled EVERYTHING for all RGB and ARGB software. Got Signal RGB installed, set the Asus ARGB header to a custom component installed with 24 leds (this was the longest numerical daisy chain of the split signal on a single device), and now everything works. I don't get to use case location based patterns, as everything uses the same 24 string long pattern, but that's totally fine. No bloatware, open source (kinda), hacked wiring, and way too much time spent but now it works. Never the way any of the parts were intended with their hardware and software.
TL:DR, Had to learn on a deep level how argb and rgb worked to reverse engineer a solution and had to replace hardware and software and go about it in a completely different way than any manufacturer intended. Crap software, crap hardware, proprietary crap that wanted me to use their controller for everything, lack of integration with legacy connectors, pulling my hair and coming up with my own FU to all of their crap and running custom wiring, exploiting the standard to trick everything into working, and keeping it as open source as possible.
A video to cover this topic and creating a consortium shouldn't have to exist, but it needs to with all of this e-waste proprietary garbage out there. Thanks Steve and Wendell
reply
CalcProgrammer1
This sounds like a great and very necessary effort. The amount of proprietary, undocumented nonsense in the hardware and firmware industry has grown to ridiculous proportions these days. I'm glad to see some other people out there trying to make a difference. I'm the creator and maintainer of the OpenRGB project and I'd like to get in touch regarding RGB standardization and the work you're doing if that is of interest to you.
OpenRGB started out as me just being frustrated that all the different parts in my 2017-era Ryzen build wouldn't work on Linux or sync with each other. I was mainly upset at ASUS Aura for not having an SDK as Razer and Corsair did, so I was able to write a program to sync them. I spent several months reverse engineering the ASUS Aura physical interface with help from GitHub which spawned a massive hundred post thread and took some interesting turns until we finally landed on it being I2C/SMBus and that, at least on Windows, Aura was talking directly to the chipset's SMBus controller registers via IO port memory. From there I wrote some hacky test code that was able to control Aura from Windows and Linux. From there, OpenAuraSDK was born, and I then made a standard API for RGB control so that I could expand it to control all my hardware, then it just grew from there.
We've gotten quite good at reverse engineering all number of interfaces (USB HID, SMBus, NVIDIA GPU I2C, and more). I'd like to help!
reply
This sounds like a great and very necessary effort. The amount of proprietary, undocumented nonsense in the hardware and firmware industry has grown to ridiculous proportions these days. I'm glad to see some other people out there trying to make a difference. I'm the creator and maintainer of the OpenRGB project and I'd like to get in touch regarding RGB standardization and the work you're doing if that is of interest to you.
OpenRGB started out as me just being frustrated that all the different parts in my 2017-era Ryzen build wouldn't work on Linux or sync with each other. I was mainly upset at ASUS Aura for not having an SDK as Razer and Corsair did, so I was able to write a program to sync them. I spent several months reverse engineering the ASUS Aura physical interface with help from GitHub which spawned a massive hundred post thread and took some interesting turns until we finally landed on it being I2C/SMBus and that, at least on Windows, Aura was talking directly to the chipset's SMBus controller registers via IO port memory. From there I wrote some hacky test code that was able to control Aura from Windows and Linux. From there, OpenAuraSDK was born, and I then made a standard API for RGB control so that I could expand it to control all my hardware, then it just grew from there.
We've gotten quite good at reverse engineering all number of interfaces (USB HID, SMBus, NVIDIA GPU I2C, and more). I'd like to help!
reply
C4mp
i got an asrock taichi 7900xtx, msi motherboard, nzxt case and rgb fans, razer mouse and rgb mousepad, and an ROG keyboard. i have to have msi center, polychrome sync, armory crate, and razer synapse all running independantly to make it all work, ive tried open rgb as well as signal rgb, and neither of them support my GPU, even the standard polychrome sync download wont support it i had to go to the manufacturer website, get the specific download link to download a specific version of the software to get it working. and signal rgb is even worse because my razer mouse goes all wonkey when it disables razer synapse, and armory crate and msi center try to compete with each other on who gets to control my ram rgb, so every time i start up my pc i have to go into each program and make sure they are set the way i want. so yeah every single software (including supposed open source options) have issues on some level.
reply
i got an asrock taichi 7900xtx, msi motherboard, nzxt case and rgb fans, razer mouse and rgb mousepad, and an ROG keyboard. i have to have msi center, polychrome sync, armory crate, and razer synapse all running independantly to make it all work, ive tried open rgb as well as signal rgb, and neither of them support my GPU, even the standard polychrome sync download wont support it i had to go to the manufacturer website, get the specific download link to download a specific version of the software to get it working. and signal rgb is even worse because my razer mouse goes all wonkey when it disables razer synapse, and armory crate and msi center try to compete with each other on who gets to control my ram rgb, so every time i start up my pc i have to go into each program and make sure they are set the way i want. so yeah every single software (including supposed open source options) have issues on some level.
reply
itech
I hope this gets traction, but I think some of the larger companies are doing this precisely because there is not much competition to be had in the hardware (at least in their corporate minds). Vendor lock in on this kind of hardware and using software as differentiator happenes when the business model is to sell the hardware. Opening up the hardware interface and letting community software take all the role means the hardware vendors only have hardware to compete with, which is not where they want to be in.
If there are enough smaller companies + one major player who can get onboard and if you can make the situation of: being left out of the standard means you are lagging far behind on software support and thus your hardware is less valuable. then maybe this can force larger companies to change their business model altogether.
reply
I hope this gets traction, but I think some of the larger companies are doing this precisely because there is not much competition to be had in the hardware (at least in their corporate minds). Vendor lock in on this kind of hardware and using software as differentiator happenes when the business model is to sell the hardware. Opening up the hardware interface and letting community software take all the role means the hardware vendors only have hardware to compete with, which is not where they want to be in.
If there are enough smaller companies + one major player who can get onboard and if you can make the situation of: being left out of the standard means you are lagging far behind on software support and thus your hardware is less valuable. then maybe this can force larger companies to change their business model altogether.
reply
Michel
I just had the idea of a market place for fixes. Like, I don't have the skills nor the resources to solve any of the existing problems, even small ones, but I'd be happy to spend like 10 or 20 for someone else to fix it. Now if you create a platform on which people could donate an amount of their choice towards a specific problem, there would very rapidly be an increasing incentive for someone to take on that problem and take that cash. Be it 0.5 from a thousand different people who really want someone to fix some known software issue, or someone who pays 500 for a specific problem he really wants to be resolved.
More urgent issues will rise to the top more quickly, due to growing demand.
And if possible make the solutions open source by default, so that everyone in the community can benefit from it.
reply
I just had the idea of a market place for fixes. Like, I don't have the skills nor the resources to solve any of the existing problems, even small ones, but I'd be happy to spend like 10 or 20 for someone else to fix it. Now if you create a platform on which people could donate an amount of their choice towards a specific problem, there would very rapidly be an increasing incentive for someone to take on that problem and take that cash. Be it 0.5 from a thousand different people who really want someone to fix some known software issue, or someone who pays 500 for a specific problem he really wants to be resolved.
More urgent issues will rise to the top more quickly, due to growing demand.
And if possible make the solutions open source by default, so that everyone in the community can benefit from it.
reply
sr7olsniper
This is one of the issues I have. I have Razer peripherals so I have to use Synapse for those but then I had Corsair Fans, AIO, and RAM so i am stuck with Icue in that side. I cant get them to sync up. I cant go full corsair because Corsair does not make some peripherals I use and I cant go full razer because the fans they make are not my thing as well as i'm locked with the RAM or AIO. I have asked both Corsair and Razer in nicer terms separately if they could get their shit together for the consumer but I have only been given neutral PR responses. An open software/standard that allows me to manage all the RBG crap and get it to sync would be amazing. I will still purchase from both companies I just want to be able to control my visual vomit how I please.
reply
This is one of the issues I have. I have Razer peripherals so I have to use Synapse for those but then I had Corsair Fans, AIO, and RAM so i am stuck with Icue in that side. I cant get them to sync up. I cant go full corsair because Corsair does not make some peripherals I use and I cant go full razer because the fans they make are not my thing as well as i'm locked with the RAM or AIO. I have asked both Corsair and Razer in nicer terms separately if they could get their shit together for the consumer but I have only been given neutral PR responses. An open software/standard that allows me to manage all the RBG crap and get it to sync would be amazing. I will still purchase from both companies I just want to be able to control my visual vomit how I please.
reply
naughty
God, Steve's anecdote about the AX1600i/Corsair Link gave me flashbacks to dealing with Corsair AIOs, naming schemes and deprecated iCUE versions - a couple of years after I bought a new H100i, iCUE 4 came out and suddenly my AIO lost software support, I needed to have a H100i ELITE CAPELLIX, H100i RGB Pro XT, H100i v2 or a H100i Elite to read simple sensors and adjust simple controls.
I threw in the towel when I got a Corsair mouse that was iCUE 4 compatible - in order to change the settings on my AIO and mouse I needed to simultaneously have iCUE 3 and iCUE 4 on my machine, that was the recommendation. That's just my CPU cooler and mouse, how much system resources could I possibly need to have spare to do basic configuration of everything else as well?
reply
God, Steve's anecdote about the AX1600i/Corsair Link gave me flashbacks to dealing with Corsair AIOs, naming schemes and deprecated iCUE versions - a couple of years after I bought a new H100i, iCUE 4 came out and suddenly my AIO lost software support, I needed to have a H100i ELITE CAPELLIX, H100i RGB Pro XT, H100i v2 or a H100i Elite to read simple sensors and adjust simple controls.
I threw in the towel when I got a Corsair mouse that was iCUE 4 compatible - in order to change the settings on my AIO and mouse I needed to simultaneously have iCUE 3 and iCUE 4 on my machine, that was the recommendation. That's just my CPU cooler and mouse, how much system resources could I possibly need to have spare to do basic configuration of everything else as well?
reply
Entenkommando
I'm absolutely on Wendel's side here. There's no IP clash in standardised electronic communication. You agree on a standard pinout, you provide the commands and values that are sent on the data line and boom. Done.
You can have a situation where complicated commands require special sauce in the hardware to understand and that's a selling point for your product.
For example: if you want to make an LED screen you'd still need to create/buy a hardware controller that interprets the commands and puts them onto your LCD. Corsair shouldn't have to share their actual hardware IP for such a product.
But at least let us share common values like temperature, fan/pump speeds and RGB values that are literally the same for every piece of hardware.
reply
I'm absolutely on Wendel's side here. There's no IP clash in standardised electronic communication. You agree on a standard pinout, you provide the commands and values that are sent on the data line and boom. Done.
You can have a situation where complicated commands require special sauce in the hardware to understand and that's a selling point for your product.
For example: if you want to make an LED screen you'd still need to create/buy a hardware controller that interprets the commands and puts them onto your LCD. Corsair shouldn't have to share their actual hardware IP for such a product.
But at least let us share common values like temperature, fan/pump speeds and RGB values that are literally the same for every piece of hardware.
reply
Alex
Clearly Nvidia shills. Putting those ray traced reflections all over the table, smh. Jokes aside these interviews have been great content. I hope you can do more in the future. I don't think you talked about this, but this OpenPleb would still allow Corsair to make their proprietary hardware solutions. As long as they provide documentation: Here's how to use our patented proprietary stuff, this is the API, go figure would still be super beneficial for both them and users. Devs with too much time will go down the rabbi hole and support all these competing apis. Even if they don't there is someone out there who will be frustrated enough to just do it, if there is documentation. Although it's kind of already happening with the OpenRGB project.
reply
Clearly Nvidia shills. Putting those ray traced reflections all over the table, smh. Jokes aside these interviews have been great content. I hope you can do more in the future. I don't think you talked about this, but this OpenPleb would still allow Corsair to make their proprietary hardware solutions. As long as they provide documentation: Here's how to use our patented proprietary stuff, this is the API, go figure would still be super beneficial for both them and users. Devs with too much time will go down the rabbi hole and support all these competing apis. Even if they don't there is someone out there who will be frustrated enough to just do it, if there is documentation. Although it's kind of already happening with the OpenRGB project.
reply
Richard
I recently bought a second hand PC. It was a HP, and when I took it apart to do a full checkup on it before I trusted it, I noticed the motherboard was held to the case by the bolts that held on the CPU cooler...
Upon further examination, the power connector was proprietary, the power supply was a non-standard size, the motherboard didn't have standard connectors, in fact the only standard things about it were the SATA connectors, the RAM, the CPU, and the PCIE connector (as well as USB, HDMI etc). The PC works fine and is great for the job I need it to do, but as soon as even the most basic thing is faulty, the PC is destined for the bin.
I fully support the standardisation of any PC parts to stop this type of rubbish.
reply
I recently bought a second hand PC. It was a HP, and when I took it apart to do a full checkup on it before I trusted it, I noticed the motherboard was held to the case by the bolts that held on the CPU cooler...
Upon further examination, the power connector was proprietary, the power supply was a non-standard size, the motherboard didn't have standard connectors, in fact the only standard things about it were the SATA connectors, the RAM, the CPU, and the PCIE connector (as well as USB, HDMI etc). The PC works fine and is great for the job I need it to do, but as soon as even the most basic thing is faulty, the PC is destined for the bin.
I fully support the standardisation of any PC parts to stop this type of rubbish.
reply
Jenna
If RGB had a royalty-free standard I would actually use RGB. The balkanization of the RGB space is why the few LEDs I couldn't completely avoid in my PC are on the default rainbow barf because there is also little incentive to create streamlined software inside those walled gardens so my only choices in many cases are install Armoury Crate (for example) or GFY. Corsair et al. would shift their customer base by +1 in my case at the very least, and I can't be the only one who is eagerly awaiting the implementation and adoption of an open standard so I can comfortably invest in this aspect of the hobby.
(Literally the moment I hit Comment the video hit 22:50 and Steve commented on my exact situation.)
reply
If RGB had a royalty-free standard I would actually use RGB. The balkanization of the RGB space is why the few LEDs I couldn't completely avoid in my PC are on the default rainbow barf because there is also little incentive to create streamlined software inside those walled gardens so my only choices in many cases are install Armoury Crate (for example) or GFY. Corsair et al. would shift their customer base by +1 in my case at the very least, and I can't be the only one who is eagerly awaiting the implementation and adoption of an open standard so I can comfortably invest in this aspect of the hobby.
(Literally the moment I hit Comment the video hit 22:50 and Steve commented on my exact situation.)
reply
Matt
I want to thank both of you for bring this to the forefront. So I did start to use Corsair s fan control header/ rgb controller around 2016. Later in a upgrade around the Ryzen 3000 series timeline I again used Corsair s equipment again. I spent a lot of money on all those expensive accessories all to discover the massive cabling nightmare and buggy software issues. Corsair I sold all that crap and don t take this the wrong way because I do use your other products just not that proprietary mess of RGB crap anymore. Today I use analog based RGB equipment from EKWB. EKWB please don t not do what these other companies are doing.
reply
I want to thank both of you for bring this to the forefront. So I did start to use Corsair s fan control header/ rgb controller around 2016. Later in a upgrade around the Ryzen 3000 series timeline I again used Corsair s equipment again. I spent a lot of money on all those expensive accessories all to discover the massive cabling nightmare and buggy software issues. Corsair I sold all that crap and don t take this the wrong way because I do use your other products just not that proprietary mess of RGB crap anymore. Today I use analog based RGB equipment from EKWB. EKWB please don t not do what these other companies are doing.
reply
Raphael
For me (sorry for my bad englisch), the new Corsair Link is a branded marketing gag... You want the new ecosystem with few cables? Then all you have to do is throw out your other branded RGB hardware and buy ALL FROM US to be happy. All manufactures goes the same way to make everyone happy with RGB, not the softwares from them, but Corsair says buy from us or go away with your shit... That's anoying....
LianLi (not the rgb software), Phanteks made it right... Love my LianLi Fans (exchanged with Corsair) but this year, for me, Phantek with there new Cases NV 5/7/9, DaisyChain Fans, is the Winner after Computex 2023
reply
For me (sorry for my bad englisch), the new Corsair Link is a branded marketing gag... You want the new ecosystem with few cables? Then all you have to do is throw out your other branded RGB hardware and buy ALL FROM US to be happy. All manufactures goes the same way to make everyone happy with RGB, not the softwares from them, but Corsair says buy from us or go away with your shit... That's anoying....
LianLi (not the rgb software), Phanteks made it right... Love my LianLi Fans (exchanged with Corsair) but this year, for me, Phantek with there new Cases NV 5/7/9, DaisyChain Fans, is the Winner after Computex 2023
reply
Curtis
This would be amazing if made a reality. Steve made a great point that with an open hardware standard, manufacturers would only have to worry about drivers with other companies writing software (almost a sounds like most other hardware with Microsoft taking care of the software ). I could imagine some of the smaller companies and maybe a motherboard vendor along with a software company like the authors of OpenRGB could be a foundation. If successful (which it will be, given the community is crying out for it) then the bigger players will eventually have to relent and join the eco system, you would think.
reply
This would be amazing if made a reality. Steve made a great point that with an open hardware standard, manufacturers would only have to worry about drivers with other companies writing software (almost a sounds like most other hardware with Microsoft taking care of the software ). I could imagine some of the smaller companies and maybe a motherboard vendor along with a software company like the authors of OpenRGB could be a foundation. If successful (which it will be, given the community is crying out for it) then the bigger players will eventually have to relent and join the eco system, you would think.
reply
:fax:
I vote with my wallet by not buying into any of this rgb rainbow puke for every possible component. I want to look at what's on my screen, not the computer itself. I do have a glass side panel case (only because it was 5 dollars cheaper than the solid panel for some reason at the time of purchase), but the only lights I have are mobo and gpu. I do love this idea for anyone who is into the super flashy stuff, good luck. Meanwhile, I'll be more than happy with my grey Noctua redux fans for however many thousands and thousands of hours they will (probably) last.
reply
I vote with my wallet by not buying into any of this rgb rainbow puke for every possible component. I want to look at what's on my screen, not the computer itself. I do have a glass side panel case (only because it was 5 dollars cheaper than the solid panel for some reason at the time of purchase), but the only lights I have are mobo and gpu. I do love this idea for anyone who is into the super flashy stuff, good luck. Meanwhile, I'll be more than happy with my grey Noctua redux fans for however many thousands and thousands of hours they will (probably) last.
reply
Insanity
I buy 15 Upward and other no name, single color LED fans for two reasons. Okay three. 1, I'm old and the early 2000's were my introduction to PC gaming- we didn't have no fancy argeebee and gosh darnit that was fine. 2. I'm cheap 3. What you guys said. I'm not buying into an ecosystem I can only use for 3 years. Opening up the market to interoperability will inherently lower prices as consumers will have more options, and allow people to carry more parts over to new builds. Keep up the good fight, as niche as this one is!
reply
I buy 15 Upward and other no name, single color LED fans for two reasons. Okay three. 1, I'm old and the early 2000's were my introduction to PC gaming- we didn't have no fancy argeebee and gosh darnit that was fine. 2. I'm cheap 3. What you guys said. I'm not buying into an ecosystem I can only use for 3 years. Opening up the market to interoperability will inherently lower prices as consumers will have more options, and allow people to carry more parts over to new builds. Keep up the good fight, as niche as this one is!
reply
Spyridon
The problem is in the hands of the consumer to stop buying from Greedy companies , Corsair lost me cause when i tried to RMA a DDR2 ram with Lifetime Warranty the asking for proof of purchase (after 6-8 years of purchase) or a last 6-month pop from another Corsair product when i had send as an IT to Kingston about 15 dimms of ddr1 and ddr2 with RMA and replaced then no question asked and some where older than 10 years .Nowadays lifetime is the life of PC not of the component and they decide what this life is...
reply
The problem is in the hands of the consumer to stop buying from Greedy companies , Corsair lost me cause when i tried to RMA a DDR2 ram with Lifetime Warranty the asking for proof of purchase (after 6-8 years of purchase) or a last 6-month pop from another Corsair product when i had send as an IT to Kingston about 15 dimms of ddr1 and ddr2 with RMA and replaced then no question asked and some where older than 10 years .Nowadays lifetime is the life of PC not of the component and they decide what this life is...
reply
David
The good thing about RBG is you don't have to have it. But yes I agree I want it all to work together. OpenRBG tries Windows 11 is supposed to offer RGB support so we will see. Sensors would be so nice. As to the example of why Corsair would want to do it? Simple Corsair does make motherboards or video cards. Making them all work together would be a win. If I want to do that I would have to get an ASUS motherboard, Graphics card cooler, case, and mouse, not Corsair. So come on folks make this a standard work.
reply
The good thing about RBG is you don't have to have it. But yes I agree I want it all to work together. OpenRBG tries Windows 11 is supposed to offer RGB support so we will see. Sensors would be so nice. As to the example of why Corsair would want to do it? Simple Corsair does make motherboards or video cards. Making them all work together would be a win. If I want to do that I would have to get an ASUS motherboard, Graphics card cooler, case, and mouse, not Corsair. So come on folks make this a standard work.
reply
Lindsey
For hardware connection, wouldn't USB type C be good? It has data and power, and I'm sure you could incorporate tach/pwm. I do remember someone at computex reusing the connecter for this purpose?
Connecting fan to fan could be done with a little USB C bridge. Daisy chaining distant devices could be done with an off the shelf cable. You could either use a dedicated connector and controller off the motherboard, or a standalone external controller, that also connects though maybe a USB2 header.
reply
For hardware connection, wouldn't USB type C be good? It has data and power, and I'm sure you could incorporate tach/pwm. I do remember someone at computex reusing the connecter for this purpose?
Connecting fan to fan could be done with a little USB C bridge. Daisy chaining distant devices could be done with an off the shelf cable. You could either use a dedicated connector and controller off the motherboard, or a standalone external controller, that also connects though maybe a USB2 header.
reply
Add a review, comment
Other channel videos
