Also, some other possibly relevant information: I'm running Ubuntu 8.04. My sound card is a pcmcia Audigy2 ZS Notebook. My Dell 600m's native resolution is 1400x1050, but I'm using an external monitor with 1680x1050 resolution.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Mind running that in a debugger for us? change CMAKE_BUILD_TYPE to "Debug" and do everything else as normal to install. Then run gdb projectM-test on the command line and dump the results to the forum.
- Carmelo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, the command "gdb projectM-test" didn't seem to do anything, so I'm not sure if I did this right:
digby@velvet:~/Programs/projectm/projectM-Trunk/src$ gdb -e projectM-test
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
(gdb) run projectM-test
Starting program: /usr/bin/projectM-test projectM-test
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
dir:/usr/share/projectM/config.inp
reading ~/.projectM/config.inp
[New Thread 0xb765fa70 (LWP 29469)]
[New Thread 0xb747db90 (LWP 29472)]
Screen Resolution: 1680 x 1050
MAX SAMPLES:2048
[New Thread 0xb0430b90 (LWP 29476)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb765fa70 (LWP 29469)]
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0xb7e5a593 in RenderTarget::lock (this=0x83c5508)
at /home/digby/Programs/projectm/projectM-Trunk/src/projectM-engine/FBO.cpp:236
#2 0xb7e95a33 in Renderer::RenderFrame (this=0x83b8e50,
presetOutputs=0x8365b08, presetInputs=0x8365a30)
at /home/digby/Programs/projectm/projectM-Trunk/src/projectM-engine/Renderer.cpp:136
#3 0xb7e54490 in projectM::renderFrame (this=0x83659b8)
at /home/digby/Programs/projectm/projectM-Trunk/src/projectM-engine/projectM.cpp:345
#4 0x0804d25d in ?? ()
#5 0x083659b8 in ?? ()
#6 0x00000000 in ?? ()
(gdb)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Excellent work posting the backtrace- that's exactly what I wanted to see. Without having Pete review this problem (he may later), I am going to guess your graphics card and/or driver does not support frame buffer object extensions, which boils down to one change in your build settings. Turn off "USE_FBO" in the cmake configuration screen. It's a shame that projectM isn't detecting this properly and turning FBO off at run time, but then again it could be a driver bug.
Good luck,
Carmelo
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The config file is located at ~/.projectM/config.inp
Most options are pretty obvious. In the wiki, on the FAQ page, there is some info about configuring the graphical settings for max performance/quality. Although, since you are not using FBO, the rendering quality is almost 100% linked to your window size. Ideally, you want to keep your window bigger than 512x512, as the texsize used for rendering can not be larger than your screen. If you have a huge monitor, 1024x1024 would be even better.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I installed projectM, first by following the instructions here: http://ubuntuforums.org/showthread.php?t=749793
When I ran projectM-test, it resulted in a segfault. The same thing happens when I run projectM-pulseaudio.
I removed all the files from the make install, then tried following these directions: http://www.ubuntu-unleashed.com/2008/04/howto-awesome-winamp-music.html. This resulted in the same problem.
For reference, I'm using an ATI Radeon Mobility 9000 on a Dell 600m.
projectM-test pops up a window, prints this in the terminal:
dir:/usr/share/projectM/config.inp
reading ~/.projectM/config.inp
Screen Resolution: 1680 x 1050
MAX SAMPLES:2048
Segmentation fault
then closes.
projectM-pulseaudio does the same, but prints this:
dir:/usr/share/projectM/config.inp
reading ~/.projectM/config.inp
MAX SAMPLES:2048
load config END
unconnected: connecting...
connectHelper: "alsa_output.pci_8086_24c5_sound_card_0_alsa_playback_0.monitor"
Segmentation fault
Any help would be greatly appreciated. ProjectM looks great, and I'd kill to get this to work.
Also, some other possibly relevant information: I'm running Ubuntu 8.04. My sound card is a pcmcia Audigy2 ZS Notebook. My Dell 600m's native resolution is 1400x1050, but I'm using an external monitor with 1680x1050 resolution.
Mind running that in a debugger for us? change CMAKE_BUILD_TYPE to "Debug" and do everything else as normal to install. Then run gdb projectM-test on the command line and dump the results to the forum.
- Carmelo
Hi, the command "gdb projectM-test" didn't seem to do anything, so I'm not sure if I did this right:
digby@velvet:~/Programs/projectm/projectM-Trunk/src$ gdb -e projectM-test
GNU gdb 6.8-debian
Copyright (C) 2008 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
(gdb) run projectM-test
Starting program: /usr/bin/projectM-test projectM-test
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
dir:/usr/share/projectM/config.inp
reading ~/.projectM/config.inp
[New Thread 0xb765fa70 (LWP 29469)]
[New Thread 0xb747db90 (LWP 29472)]
Screen Resolution: 1680 x 1050
MAX SAMPLES:2048
[New Thread 0xb0430b90 (LWP 29476)]
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb765fa70 (LWP 29469)]
0x00000000 in ?? ()
(gdb) bt
#0 0x00000000 in ?? ()
#1 0xb7e5a593 in RenderTarget::lock (this=0x83c5508)
at /home/digby/Programs/projectm/projectM-Trunk/src/projectM-engine/FBO.cpp:236
#2 0xb7e95a33 in Renderer::RenderFrame (this=0x83b8e50,
presetOutputs=0x8365b08, presetInputs=0x8365a30)
at /home/digby/Programs/projectm/projectM-Trunk/src/projectM-engine/Renderer.cpp:136
#3 0xb7e54490 in projectM::renderFrame (this=0x83659b8)
at /home/digby/Programs/projectm/projectM-Trunk/src/projectM-engine/projectM.cpp:345
#4 0x0804d25d in ?? ()
#5 0x083659b8 in ?? ()
#6 0x00000000 in ?? ()
(gdb)
Excellent work posting the backtrace- that's exactly what I wanted to see. Without having Pete review this problem (he may later), I am going to guess your graphics card and/or driver does not support frame buffer object extensions, which boils down to one change in your build settings. Turn off "USE_FBO" in the cmake configuration screen. It's a shame that projectM isn't detecting this properly and turning FBO off at run time, but then again it could be a driver bug.
Good luck,
Carmelo
Thanks! That fixed it. A quick question, where are the config files, and is there any documentation about configuring it?
The config file is located at ~/.projectM/config.inp
Most options are pretty obvious. In the wiki, on the FAQ page, there is some info about configuring the graphical settings for max performance/quality. Although, since you are not using FBO, the rendering quality is almost 100% linked to your window size. Ideally, you want to keep your window bigger than 512x512, as the texsize used for rendering can not be larger than your screen. If you have a huge monitor, 1024x1024 would be even better.
This is the same stack trace that I was getting when mine segfaulted as described here http://sourceforge.net/forum/forum.php?thread_id=2092411&forum_id=358774. But my card/driver does support FBO as it works in Amarok which I can confirm with the info pane, which shows Using FBO: Yes.