The spectrum status is abnormal in version 1.1.0-rc

[HEIHUAa]

The audio visualization differs significantly from what was previously presented, and its visual quality is poor.

Version: 1.1.0-rc

Windows

As shown in the figures above, Figure 1 shows the normal behavior in version 1.0.1, while Figure 2 (version 1.1.0) clearly shows that the spectrum has become very flat, with almost no visual appeal. If I remember correctly, a normal spectrum should have lower energy at low frequencies and higher energy at high frequencies. Is this the intended/expected behavior?

[r6915ee]

Both screenshots show different songs being selected, so I'm not sure if it's a mod issue or not. That being said, if it's not an issue with the mod, then does the waveform use CharterWaveformHandler?

The first idea that comes to mind is that there's a problem with the lower level waveform shaders, as CharterWaveformHandler is responsible for the shaders involved. Since shaders were updated to use a newer GLSL version and CharterWaveformHandler still uses CustomShader, I'd imagine that there'd be some complications.

If it isn't a shader problem, then it might be a good idea to look into what Lime is doing there, but I don't exactly know if the release candidate uses the internal-merge branch or not considering there do seem to be huge differences in how audio works over there.

[HEIHUAa]

Both screenshots show different songs being selected, so I'm not sure if it's a mod issue or not. That being said, if it's not an issue with the mod, then does the waveform use CharterWaveformHandler?

The first idea that comes to mind is that there's a problem with the lower level waveform shaders, as CharterWaveformHandler is responsible for the shaders involved. Since shaders were updated to use a newer GLSL version and CharterWaveformHandler still uses CustomShader, I'd imagine that there'd be some complications.

If it isn't a shader problem, then it might be a good idea to look into what Lime is doing there, but I don't exactly know if the release candidate uses the internal-merge branch or not considering there do seem to be huge differences in how audio works over there.

In my opinion, the release build definitely uses the internal-merge option, since it supports unlimited frame rate – which proves that the song inconsistency issue is not a major concern. For any song, the spectrum displayed in version 1.1.0-rc looks almost the same, with very little variation.

I am not using CharterWaveformHandler; instead, I manually create the waveform display via code. Here is the code:

samples = analyzer.getLevels(
    FlxG.sound.music.time, 
    0.1,
    halfLength,
    samples,
    10 * elapsed,
    -90,
    0,
    80,
    22000
);

#if (NDLLS_SUPPORTED && (windows || mac || linux))
updateAudioVisualizer(samples, audioMembers, scaleMultiplier, halfLength);
#else
var sample, scaleValue, sprite, sprite_2;
for (i in 0...halfLength) {
    sample = samples[i];
    scaleValue = sample * scaleMultiplier;

    sprite = audioMembers[i];
    sprite_2 = audioMembers[audioLengths - i];

    sprite.scale.y = sprite_2.scale.y = scaleValue;
    sprite.alpha = sprite_2.alpha = sample;
}
#end

updateAudioVisualizer uses .NDLL and the code from another path is identical. Since I am using CPU-based processing, I can completely rule out any other factors. This points directly to the output of analyzer.getLevels being the actual problem.

[HEIHUAa]

Actually, I also tried to investigate the issue, but I didn't seem to find anything wrong. The problem might point to Lime.

[r6915ee]

I decided to take a look at the internal-merge branch, and apparently the last notable commit over there to AudioAnalyzer (c20c292) included a huge overhaul to that class. I think it would be a good idea to take a look at the implementation details over there as well.

[HEIHUAa]

I decided to take a look at the internal-merge branch, and apparently the last notable commit over there to AudioAnalyzer (c20c292) included a huge overhaul to that class. I think it would be a good idea to take a look at the implementation details over there as well.

Good luck with that. At least from what I can see in AudioAnalyzer, I don’t notice any issues. I even found that compared to 1.0.1, it fixed a channel misalignment problem – you can check that. Also, it seems that the volume setting is not working anymore.

[HEIHUAa]

"Also, the song preview feature in FreeplayState was already removed back in March on the internal‑merge branch. So the song shown in that screenshot from internal‑merge is actually the menu music, not a preview song. Checking the git history shows that it was a temporary removal, but it hasn't been re‑added yet.