Skip to content
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.

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

Fix libprojectm4 and ui-jack compiler errors #13

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

struktured
Copy link
Contributor

@struktured struktured commented Nov 23, 2023

This compiles with ui-jack and it crashed the first time I ran it, runs fine otherwise except for some weird artifacts on a few presets. Want to test it a bit more.

Screenshot_20231123_161918

@struktured struktured self-assigned this Nov 23, 2023
@struktured struktured changed the title Draft: Fix projectm 4 compiler errors Draft: Fix projectm and ui-jack 4 compiler errors Nov 23, 2023
@struktured
Copy link
Contributor Author

I also tested projectM-pulseaudio and it had the same rendering issues.

@struktured struktured changed the title Draft: Fix projectm and ui-jack 4 compiler errors Fix projectm and ui-jack 4 compiler errors Nov 24, 2023
@struktured struktured changed the title Fix projectm and ui-jack 4 compiler errors Fix libprojectm4 and ui-jack compiler errors Nov 24, 2023
@kblaschke
Copy link
Member

kblaschke commented Nov 25, 2023

When I last tested the Qt app, I also had rendering errors - like a quarter of the rendering area having a strange border.

I've also noticed that some OpenGL objects just vanished at random points, e.g. vertex buffer objects becoming invalid and thus causing weird/broken and invisible geometry being rendered. Didn't really spend much time to find out what was going wrong.

@revmischa
Copy link
Contributor

revmischa commented Nov 25, 2023

When I updated the macOS Music plugin i noticed weird screen effects in a quarter of the screen until I added a high DPI rendering flag to something (I forget exactly what)

(edit: in re: "When I last tested the Qt app, I also had rendering errors - like a quarter of the rendering area having a strange border.")

@@ -126,14 +126,14 @@ void QProjectMConfigDialog::saveConfig() {
// Will only keep data_dir.
auto settings = projectm_get_settings(_qprojectMWidget->qprojectM()->instance());
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hum... projectm_get_settings() didn't make it into the 4.0 release, the whole settings struct is gone and was replaced by get/set calls.

Better try compiling against the 4.0 release or current master of libprojectM.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe I am? See this output:

(base) carm@blackmage:~/projects/frontend-qt$ ldd src/ui-jack/projectM-jack |grep projectM
        libprojectM.so.4 => /usr/local/lib/libprojectM.so.4 (0x00007fce9bc00000)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The .so version is about misleading as it's just counted up, and not really related to the version number. The filename of projectM 4 is different though, it's named libprojectM-4.so. The include dirs also are prefixed with a projectM-4 path.

Just try to build the Qt app against latest projectM master, making sure no libs/headers of older versions are still in you system paths.

@struktured
Copy link
Contributor Author

struktured commented Nov 25, 2023

When I last tested the Qt app, I also had rendering errors - like a quarter of the rendering area having a strange border.

I've also noticed that some OpenGL objects just vanished at random points, e.g. vertex buffer objects becoming invalid and thus causing weird/broken and invisible geometry being rendered. Didn't really spend much time to find out what was going wrong.

I've seen that too, was going to look into that next. I still think this PR is better than what's in master now though.

@struktured
Copy link
Contributor Author

So I cleaned up some old projectm header files and now get a ton of compiler errors. Will try to fix them!!

@revmischa revmischa removed their request for review April 1, 2024 15:50
@kblaschke
Copy link
Member

Any progress with this PR or should we better convert it to a draft?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants