The Corsair User Forums

The Corsair User Forums (https://forum.corsair.com/forums/index.php)
-   CUE 1.x and 2.x SDK (https://forum.corsair.com/forums/forumdisplay.php?f=271)
-   -   Keyboard-Audio-Visualizer (https://forum.corsair.com/forums/showthread.php?t=170165)

Darth Affe 08-13-2017 11:49 AM

Keyboard-Audio-Visualizer
 
3 Attachment(s)
Hey Guys,

since there aren't already enough audio visualizers for keyboard out there, I decided to create a new one :p
The main reason for that is, that existing visualizers aren't able to show some relaxing random visualization like wmp and other software. Right now this isn't possible here too, but the current development progress is the base for something like that.

Currently only one visualization per device is implemented:
Keyboard: Highly configurable Frequency Bars (the well known thing)
Mouse/Headset: Beat detection (not really well working right now)
Mousepad/Lightbar (K95 Platinum): Level-Meter

All Corsair devices are supported, some logitech keyboard too.

For more information and a description of the configuration-possibilities check out the github homepage.

You need the .NET Framework 4.6.1 or newer and CUE with enabled SDK to run this!

Download: https://github.com/DarthAffe/Keyboar...lizer/releases (or in the attachment)
Source: https://github.com/DarthAffe/KeyboardAudioVisualizer

Changes:
V1.1
  • Lots of bugfixes regarding devices and support for more devices
  • Changeable Gradient/Color for all visualizations
  • Added a option to reverse-scale the audio input with the os-volume. This allows to reduce the impact of a change to the windows-volume if the driver of selected audio device links the loopback device volume to it.
  • Hopefully a final fix for the fake-suround-driver audio problems
  • Increased max update-rate (even if I won't recommend to go above 40)
  • Minor fixes to prevent crashes or weird behaviors on some edge-cases while opening closed windows or creating a configuration


V1.0.1
  • Tested and confirmed full support for Novation Launchpad S and Logitech G610 (EU layout).
  • Changed the style of the sliders in the config section to have a more obvious disabled-state and to show the current value on mouse over.
  • Added tooltips to the configuration.
  • Added support for different visualizations per device (no new visualizations so far) (which visualization is possible depends on the device).
  • Changed configuration-file (old ones should get converted automatically).
  • Fixed a bug which leads to useless error-logs.

Application Screenshot:
https://uploads.wyrez.org/KeyboardAudioVisualizer.png

Example-Video:

Halko Proude 08-22-2017 05:30 PM

Loving it so far. It's fun fiddling with the bar settings to find the right one that works for me. I currently use a STRAFE (plain red lighting, not RGB), Sabre 10k mouse, and Void USB headset. Few things I noticed that may could use some fine-tuning:

-Are there plans for the Beat Detection for mouse/headset to show RGB colors instead of just white?

-Noticed that Beat Detection doesn't affect the DPI indicator light on my Sabre. Is this intentional? Can there be an option to configure using that lighting zone too?

-Slight tweak to the UI to show that the Gamma bar can't be adjusted when not using the Gamma spectrum

-This is called "Keyboard Audio Visualizer" but you can configure the mouse/headset/mousepad/lightbar as well, so perhaps rename this to something like "Corsair Audio Visualizer"?

Darth Affe 08-23-2017 06:08 AM

Hey, great to hear that you like it :)

Quote:

Originally Posted by Halko Proude (Post 917161)
-Are there plans for the Beat Detection for mouse/headset to show RGB colors instead of just white?

Yes, in a future version (most likely not the next) all colors will be customizable.

Quote:

Originally Posted by Halko Proude (Post 917161)
-Noticed that Beat Detection doesn't affect the DPI indicator light on my Sabre. Is this intentional? Can there be an option to configure using that lighting zone too?

No. My last information about the DPI indicator is from 2016 (but as far as I know nothing has changed here), which says that it's intended, that the dpi indicator isn't changeable through the sdk.

Quote:

Originally Posted by Halko Proude (Post 917161)
-Slight tweak to the UI to show that the Gamma bar can't be adjusted when not using the Gamma spectrum

Sure, there a quite a lot things on the UI that aren't really intuitive right now. UI-improvements will be a part of the next version

Quote:

Originally Posted by Halko Proude (Post 917161)
-This is called "Keyboard Audio Visualizer" but you can configure the mouse/headset/mousepad/lightbar as well, so perhaps rename this to something like "Corsair Audio Visualizer"?

Well that's right, but it's not limited to Corsair either. I'll think about it ;-)

leonsajan 09-14-2017 02:29 PM

Hello, I am using the Corsair STRAFE RGB. However, i keep getting this error when i try to open the application.

I have checked that SDK has been enabled in CUE. Also, tried running in Administrator Mode, just incase the software isn't hooking properly.

This is whats in the error log:
Quote:

[15/9/2017 2:20:31 AM] Exception!

Message:


StackTrace:
at CSCore.SoundIn.WasapiCapture.InitializeInternal()
at CSCore.SoundIn.WasapiCapture.Initialize()
at KeyboardAudioVisualizer.AudioCapture.CSCoreAudioInput.Initialize()
at KeyboardAudioVisualizer.AudioProcessing.AudioProcessor.InitializeInstance()
at KeyboardAudioVisualizer.AudioProcessing.AudioProcessor.Initialize()
at KeyboardAudioVisualizer.App.OnStartup(StartupEventArgs e)


Darth Affe 09-15-2017 05:42 AM

Hey,
this problem is related to your audio-output. Are you using a somehow uncommon setup (multiple or external soundcards)?

leonsajan 09-15-2017 08:26 AM

hmm i'm not using any external soundcard, it's the on-board sound.

Motherboard: MSI Z270 Gaming Pro Carbon

Darth Affe 09-15-2017 12:27 PM

Ok the problem right now is, that the current version has a bug which prevents the error-message from being shown correctly (that's why there's nothing under message in the log) and without this, it's difficult to track down such a issue.

I'm afraid you need to wait for the next version which either fix the problem or will tell us more about what exactly the problem is.
I planned this version for this week but i introduced a huge memory leak which i wasn't able to resolve until now. I'm pretty sure I'm not able to do it until the end of the week - hopefully next week - sorry for that.

leonsajan 09-16-2017 02:05 AM

Hey, yeah its alright, ill wait for the next version.

Just tested the one made by AterialDawn (CUEAudioVisualizer v1.3.0) and it works. Meanwhile, I'll try to diagnose the error while waiting for the new release.

Halko Proude 09-25-2017 01:21 PM

Update on when the next version will be out?

Darth Affe 09-25-2017 02:16 PM

Hey,
today I found the cause of the memory-leak I mentioned above and started looking for a solution just now.
I want to finish tooltips and some small ui-problems too for this release. Since it needs a bit of testing afterwards I think it will be the end of the week. But definitely this week.
Even though I don't want to raise any high expectations - all the background work took me way longer than expected so there are far less visible changes than I initially planned (for example changeable colors are still missing).

Darth Affe 09-30-2017 02:43 PM

Hey,
I just pushed the new version 1.0.1. Changes are in the start post, but there aren't to many directly visible things.
@leonsajan: You could try again now, and if not there should be a better error-message in the log

leonsajan 09-30-2017 03:02 PM

Hey Darth, couldn't find the error myself, tried drivers, uninstalling software that could conflict but nothing. Just tried the new version.

Driver: Realtek ALC1220, Nahimic 2+

Here's the error log:
Quote:

[1/10/2017 3:00:07 AM] Exception!

Message:
IAudioClient::Initialize caused an error: 0x88890008, "Unknown HRESULT".

StackTrace:
at CSCore.SoundIn.WasapiCapture.InitializeInternal()
at CSCore.SoundIn.WasapiCapture.Initialize()
at KeyboardAudioVisualizer.AudioCapture.CSCoreAudioInput.Initialize()
at KeyboardAudioVisualizer.AudioProcessing.AudioVisualizationFactory.InitializeInstance()
at KeyboardAudioVisualizer.AudioProcessing.AudioVisualizationFactory.Initialize()
at KeyboardAudioVisualizer.App.OnStartup(StartupEventArgs e)
UPDATE:
It appears to only work when i change my audio settings to 7.1 (2.1, 4.0, 5.1 doesn't work)

Darth Affe 09-30-2017 03:41 PM

Well, searching for the error message only leads to two results.
Even it's told that the error is fixed I tried what one of the guys is saying there.
It would be great if you could replace the exe with http://uploads.wyrez.org/KeyboardAudioVisualizer.exe and try again.

leonsajan 09-30-2017 03:55 PM

Quote:

Originally Posted by Darth Affe (Post 921726)
Well, searching for the error message only leads to two results.
Even it's told that the error is fixed I tried what one of the guys is saying there.
It would be great if you could replace the exe with http://uploads.wyrez.org/KeyboardAudioVisualizer.exe and try again.

That exe fixed the issue. It's working now. :D:

Darth Affe 09-30-2017 04:04 PM

Quote:

Originally Posted by leonsajan (Post 921727)
That exe fixed the issue. It's working now. :D:

Weird stuff. But thanks for all the input :)


All times are GMT -4. The time now is 03:46 PM.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2019, vBulletin Solutions, Inc.