Beat Sensitivity

[Sleeperservice]

This looks great but the amount the beat sensitivity changes with UP & DOWN seems too high. Could we have finer control? It seems to change by .25 at the moment which for a lot of presets goes from almost no reaction to far too much.

[projectM Team]

I agree! I decreased the granularity from .25 to .01. Which is a big change, but reasonable as it gives you the control you should expect.

This change (and others) will come in the next release at the end of the month.

[Sleeperservice]

Thanks, good to know. I've missed milkdrop since I moved to Spotify.

[sculptus.poe]

Originally posted by projectM Team:

I agree! I decreased the granularity from .25 to .01. Which is a big change, but reasonable as it gives you the control you should expect.

This change (and others) will come in the next release at the end of the month.

It doesn't seem like this changed unless I missed a setting.

[numinex]

Originally posted by projectM Team:

I agree! I decreased the granularity from .25 to .01. Which is a big change, but reasonable as it gives you the control you should expect.

This change (and others) will come in the next release at the end of the month.

Has this update gone out yet? The sensitivity steps still seem really large.

[Prototheist]

Hey projectM heads and devs,

I just recently installed this app and found the same complaint of granularity for beat sensitivity being too high as well as not being able to set the default value. Fear not, for I have found a solution for those seeking answers on this. Read for more info or skip to "What worked for me" section to see how the fix is applied.

The granularity for beat sensitivity is nice, but would be better if we could configure the resolution and initial value.

I know this thread is old, but I just wanted to comment on how you can change this with little effort. Thanks to the developers following a good variable naming convention, I was able to adjust the initial value by using this class.member setting "projectM.beatSensitivity." Steps are listed below and I am curious what the devs have to say if there are more useful configuration members available not listed in the default config file. Do these correlate with the OSS standalone projectM? Maybe I will take a closer look at the source and check back here.

WHAT WORKED FOR ME:
1) In your local steam files installation, you should be able to locate the projectM folder under common. Open the projectMSDL.properties file with your preferred text editor (VS code for me). EXAMPLE: <installDriveLetter>:\SteamLibrary\steamapps\common\projectM\projectMSDL.properties

where installDriveLetter is C or wherever you chose to install your Steam files for projectM.

2) Edit the file by adding this line in the config file. I placed this at line 75 just before the Logging settings.
# PROTOTHEIST 1/14/23
# Controls the initial value for beatSensitivity.
projectM.beatSensitivity = 5

Maybe a dumb tip for those are not code savy, but make sure you save these changes to your local file!

3) You can confirm the change works by restarting the app with different settings.

Thanks for reading, and I'm curious if anybody has more information to share on this and audio related config settings for the projectM steam app.

- PROTOTHEIST