Jump to content
Corsair Community

Comet 1626864951

  • Posts

  • Joined

  • Days Won


Everything posted by Comet 1626864951

  1. Without iCUE installed, your profile functionality is greatly reduced, but your stored profiles will still work.
  2. The Corsair keyboards are programmable, so you can unplug the keyboard from your home computer and plug it in at a gaming competition machine. In order for this to work, the USB keyboards must follow the USB specification, specifically, Chapter 10 on Keyboard (page 253). There are 231 defined keys, and a total of 65535, if you include the reserved ones. iCUE lets you rebind different physical keys to act like different defined keyboard keys. Note that Unicode comprises 1.1 million code points -- there simply is no way to even specify that a keyboard key should be like a key labelled with an arbitrary glyph in Unicode. There are, however, workarounds. You can use iCUE to define each key in a profile to send a particular string, and that string can be copy/pasted from Character Map or BabelMap or any other source, and pasted into the TEXT definition for the key, which you would use in iCue in lieu of macro recording.
  3. I'd like to be able to DISABLE a button, so iCUE doesn't have it doing anything, but have the input still register. If a button is disabled, it shouldn't register input on the computer. If you want a button to register input on the computer, use iCUE to indicate what input to register.
  4. If you abort the macro at step 4, the computer will not receive a key up event or a mouse button release event, and your horse will gallop ever onward. This macro, if aborted, produces the result you saw, so asking how to abort this macro is like asking people to throw your horse into a ravine, and make your computer act like the key and mouse is never released. People avoid giving bad advice. Better would be to write two macros for assigning to the same thing. The first macro would do the key and mouse down and switch profile; the second macro would do the key and mouse up and switch profile back. This would perform the desirable result of allowing you to determine when you want the horse to stop running. As programmed, your macro is an excellent example of executing a sequence of timed events. Cancelling your macro's execution once it has begun is probably not what you really want. To see/practice macro cancellation, do not use macros with explicit key/button down and up events, unless you have already created a way to restore your system to a normal state.
  5. For Macros, try inserting separate events for keypresses, rather than recording macros.
  6. I put the items from the imported profile into the library, and then I edit the HW profile and take the items from the library, binding it to the proper keys.
  7. Create a batch file that opens your game AND executes your secondary file.
  8. I set my profiles so that there is a timer on my Enter key; every time I press the key, it restarts the timer. If the timer expires, then it calls a profile switch to my dark profile which disables the lighting. The dark profile has every key defined to switch back to my default profile, while retaining the original key.
  9. The URL has changed. See: https://www.corsair.com/us/en/blog/a-deeper-look-into-the-void
  10. Try using advanced mode and making a single wave that is red, purple, and yellow. Search the forums for "megarainbow"; you may find it helpful.
  11. You do not need to open and set CUE; it should remember your last profile settings. CUE does support accented characters.
  12. windows wont detect the headset as 7.1 This would be a bug in the Corsair driver, or incompatibility with some Windows software; keep on them to get it fixed, since Windows SHOULD detect the headset as 7.1. https://answers.microsoft.com/en-us/windows/forum/games_windows_10/problem-with-71-in-my-usb-headset-win10/10e85adc-b9ec-4bfa-bf2c-e8d14e6f3bd4 Did you ensure you have latest USB drivers, etc.?
  13. It would be helpful if somebody ( @CruelBobby @momorious @cokewithvanilla ) attached the buggy profiles to their post.
  14. Still no luck updating to this version either by the CUE update button or running the MSI from Corsair's download site. It hangs. :-P I guess I'll have to try uninstalling CUE first.
  15. Less chance of getting stuck if you use keystroke commands rather than separate keypress and keyrelease actions.
  16. If I recall correctly, there are various speed settings you can select (e.g. Slow, Medium, Fast), so take a look at your choices and see if you can get the quick color change you desire.
  17. I just manually switch profiles when I am doing rapid prototyping; it's a lot easier.
  18. My mouse HW profile supports mouse events, as expected. If you want your KEYBOARD to act like a mouse without having CUE or somehting on the OS prepared to do this conversion, how do you imagine that a USB keyboard device is, without such software, supposed to do that in firmware, given that the USB device protocol specification says that a keyboard should only ever send keyboard events, and Corsair's devices must past compatibility checks against the specification. Sending special USB events which the CUE software can interpret and then tell the OS that a mouse event should be emulated cannot be done just from a keyboard.
  19. You listen for key clicks exactly the same way you do for any other keyboard or mouse, by using your language's standard I/O functions. The CUE SDK extends this to allow to listen for the non-standard USB IO controls for G and M keys, but standard keys are handled just like your program would handle standard key input from any keyboard; this is not part of the Corsair SDK but part of your own computer language's library or native functionality. The purpose of the Corsair SDK is primarily to set lighting on the Corsair device. So your program could listen to the keystrokes, and then use Corsair SDK to enable lighting on keys you specify, which could be exactly the keys you've received, or perhaps some sequence of keys. The Corsair SDK has examples that would be used with Microsft Visual Studio, which knows how to interpret the various files found in the examples folder. The source code of the examples is written in C++ and can be found in the .cpp files.
  20. Dolby Atmos technology is different than surround sound, in that the encoding on the soundtrack allows for dynamic placement of various sound sources. The physical speaker placement in the theater is then calibrated with the playback equipment to ensure that the proper speaker and volume is used for a particular sound source. As you have noticed, however, your Corsair headset is a bit different than the speakers set up at a Dolby Atmos theater, in that you have only two speakers. This is okay, as you only have two ears! The way that humans can tell the directionality of sound based on this is that there is a slight phase difference in sound received from one ear to when the same sound reaches the other ear, for example. This helps one determine at what angular direction from a straight front/back axis from which a sound is arriving. In order to detect altitude, the shape of the human's external pinnae (ears) as well as some bone conduction and interference/resonance with the various densities of the head causes the soundwaves to take on a different character by the time they hit your eardrums. So for a two-speaker reproduction of the three-dimensional encoding of sound in Dolby Atmos, the decoder doesn't so much have to be told about speaker placement, but instead relies on modelling the Head-Related Impulse Response (HRIR). [The fourier transform of this is better known as the Head-Related Transfer Function (HRTF).] As you have observed, different people have different ear shapes and head sizes, and this influences their own HRTF. The difference you hear between using Corair's Atmos decoding and the in-game Atmos decoding is caused by Corsair and the game engineer having settled on using two distinct HRTF functions--the Dolby Atmos sound encoding protocol is the same in both cases, so both Corsair and the game audio software engineer have the information about the 3d location of the sound source and its volume and pitch--its just that there is no uniformly used HRTF to indicate how to play back this sound using only two speakers. Perhaps someday Corsair will allow us to modify the HRTF in use, to better fit our own ear shape and head size, but most people lack both the mathematical understanding andd the ability to physically measure their own HRIR, so it is a bit problematic to come up with a good way that a novice user can adequately use this type of control without risking overwhelming Corsair support with questions.
  21. No, Corsair is NOT kidding you. Consider this: The CUE (Corsair Utility Engine) is primarily designed to allow customization of the hardware functionality of the Corsair peripheral devices,both for lighting and for key functions. Unlike nearly everybody you will find on this forum, I bought the Corsair keyboard primarily for the keybinding functionalities--the lighting is not really important to me at all. If you read the USB peripheral interface specification, you will see that the keyboard is supposed to just send out, for a control key, just one keystroke. The state of the control key having been pressed is latched at the operating system, not in the keyboard itself (and if Corsair adds a hardware register to mirror the state of the control key, it would also have to use extra communication channels back and forth to the system to ensure that the state of control keys being pressed stored in the keyboard are the same as that which is held by the operating system, and there are myriad reasons why the system can discard this status, such as switching users, etc.) It is to my mind not at all difficult to define each of the control sequences (apart from CTRL/E) to act in the CONTROL profile exactly as they behaved otherwise--because this is a simple matter of defining a REMAP KEY for character A to the KEYSTROKE of CTRL/A and so on for all the ASCII control codes except for E, where you would put your custom function. The American Standard Code for Information Interchange (ASCII) defines exactly 32 control codes, so this is all the redefinitions one would need. If you are going to use this technique frequently (as opposed to, say, creating a specific profile or profile folder where you control binding would take effect only for a specified associated executable program), then you would find it good to create a single generic CONTROL profile that defines all 32 of these control sequences. You would then make copies of this profile for customization purposes, and not have to worry about ever needing to redefine the default control sequences ever again. This really is not too hard, although combining this with unshifted and other bucky-bits like META, HYPER and SUPER, and adding in SHIFT, TOP and FRONT modifier keys means you can define 128 combinations (including unmodified) for every single key on the keyboard--this is a very power technique indeed, allowing one to have Corsair act like a Space Cadet keyboard. So CUE is very powerful, but this power does come at a cost, of course. For this reason, many people rely on a program designed to act on the operating system, rather than device, level, and take the input received (which CUE can modify as indicated) and then perform further translations. People often like software such as AutoHotkey. As these programs are generic, they do not use or extend the power of the peripheral hardware--they would work as well well with a generic keyboard as they would with Corsair keyboards, and as they work on the computer, they must intercept every keystroke and determine whether any translation or actions are to be performed. Being generic and already widely available, why would Corsair reinvent the wheel adding bloat to their software instead of, say, working to allow for secondary actions a lighting effect to be able to start at the second key, instead of the middle of the keyboard? Or perhaps allowing us to program the keyboard to emit some of the USB sequences defined for additional keys that are not physically present? Like you, I am repulsed at the thought of not just using CUE to control what my keyboard emits. Besides, Corsair even provides hardware-programmable keyboards and mice that can be programmed by CUE within the device firmware, so that one can take the keyboard or mouse to other computers, and the peripheral will work the same way on them, as no special driver or software is needed on the computer--everything just works. This also means that one doesn't need to worry about computer security of such things, as key-logging debugging backdoors can steal your passwords, etc. But if you find the power of CUE to be overkill for your needs, then by all means, just go the host-based software route. Just realize that there is hardly much reason to complain about CUE's power.
  22. I have a timer action set on my ENTER key so that when it doesn't get pressed for some time, the profile switches to LIGHTS OUT profile turning off the lights from my Corsair devices. My LIGHTS OUT profile retains every key function and does a profile switch back to my "default" profile.
  23. Your stream deck makes a hotkey of a button on your keyboard. You would use CUE to make your specified key into a "button" by using the REMAP KEY feature. You must NOT use a Corsair macro on that key, because your stream deck is looking for something that looks like a hardware keystroke. This is precisely the functionality afforded in CUE by the REMAP KEY feature.
  24. https://news.microsoft.com/2008/06/02/microsoft-launches-licensed-contract-manufacturers-marketplace-for-hardware-technology/
  • Create New...