Skip to content

[v4.1.x] Additional fixes for 4.1.6 #927

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 10 commits into
base: v4.1.x
Choose a base branch
from
Open

[v4.1.x] Additional fixes for 4.1.6 #927

wants to merge 10 commits into from

Conversation

@kblaschke
Copy link
Member

@kblaschke kblaschke commented Nov 10, 2025 •
edited
Loading

Cherry-picked Boost-/build-related fixes and workflow improvements from master. Also bumped the projectm-eval submodule to v1.0.5. The version was already set to 4.1.6 for immediate release after merge.

  • Fixed an issue with blur textures, as projectM previously used the warped image, and not the previous frame plus motion vectors as it should be. This may positively affect quite a few presets, so I've included the fix in this release.
  • Fixed an issue with the decay value being clamped to [0, 0.9375] instead of [0, 1].
  • Updated projecmt-eval submodule to 1.0.5
  • Updated vcpkg baseline commit to include projectm-eval 1.0.5
  • Added more workflows to check different build configurations
@kblaschke
Add missing <chrono> include in Playlist.cpp
e9572b3
@kblaschke
Use Boost's own CMake configuration file instead of CMake's module
cc8a3f6 
Otherwise, breaks builds with newer Boost versions. Also set policy CMP0167 to NEW and forcing CMake to use the Config package and not the built-in module. Will now require Boost 1.70, but this should be available everywhere.
@kblaschke kblaschke added this to the 4.1.6 milestone Nov 10, 2025
@kblaschke kblaschke self-assigned this Nov 10, 2025
@kblaschke kblaschke added the bug The issue is (potentially) a bug. label Nov 10, 2025
@kblaschke kblaschke added important Important bugs or features which should be fixed/implemented ASAP. cmake The issue is about the CMake build code or an issue with CMake itself in regards to projectM. labels Nov 10, 2025
@kblaschke kblaschke force-pushed the v4.1.x-cherry-picked-fixes-for-4.1.6 branch from 4866888 to 148d180 Compare November 10, 2025 11:25
@yoyofr @kblaschke
Use previous frame's image (plus motion vectors) in blur textures
e3f19db 
Signed-off-by: Kai Blaschke <kai.blaschke@kb-dev.net>
@kblaschke kblaschke force-pushed the v4.1.x-cherry-picked-fixes-for-4.1.6 branch from 148d180 to e36ad01 Compare November 10, 2025 11:27
mbaetgen-wup
mbaetgen-wup reviewed Nov 11, 2025
View reviewed changes
@kblaschke kblaschke force-pushed the v4.1.x-cherry-picked-fixes-for-4.1.6 branch from e36ad01 to 0c71b10 Compare November 11, 2025 08:40
@kblaschke kblaschke changed the title [v4.1.x] Cherry-picked fixes for 4.1.6 [v4.1.x] Additional fixes for 4.1.6 Nov 11, 2025
@kblaschke kblaschke force-pushed the v4.1.x-cherry-picked-fixes-for-4.1.6 branch from 0c71b10 to d957272 Compare November 11, 2025 09:09
@kblaschke kblaschke linked an issue Nov 11, 2025 that may be closed by this pull request
[DEV BUG] Incorrect rendering of certain pre-2.0 presets possibly due to default warp shader #930
Open
2 tasks
@kblaschke kblaschke moved this to In Review in libprojectM Release 4.1 Nov 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug The issue is (potentially) a bug. cmake The issue is about the CMake build code or an issue with CMake itself in regards to projectM. important Important bugs or features which should be fixed/implemented ASAP.

3 participants

@kblaschke @mbaetgen-wup @yoyofr