 |
|
|
|
|
|
 |
| ||||||||
 |
 
|
|
|
|
|
|
|
|
|
| ||||||||
|
|
| 
| User list | Rules | You are not logged in.
Nope: when disabled, the move pano tool is greyed out. It only works when the GPU is enabled.
Here is the log:
OGL Version: 3.2.0 NVIDIA 195.36.31
Render: GeForce 8400 GS/PCI/SSE2
Vendor: NVIDIA Corporation
Shader Version: 1.50 NVIDIA via Cg compiler
MaxTextureSize: 8192
MaxTextureUnits: 4
MaxColorAttachement: 8
MaxRenderBufferSize: 8192
Extentions:
GL_ARB_color_buffer_float
GL_ARB_compatibility
GL_ARB_copy_buffer
GL_ARB_depth_buffer_float
GL_ARB_depth_clamp
GL_ARB_depth_texture
GL_ARB_draw_buffers
GL_ARB_draw_elements_base_vertex
GL_ARB_draw_instanced
GL_ARB_fragment_coord_conventions
GL_ARB_fragment_program
GL_ARB_fragment_program_shadow
GL_ARB_fragment_shader
GL_ARB_framebuffer_object
GL_ARB_framebuffer_sRGB
GL_ARB_geometry_shader4
GL_ARB_half_float_pixel
GL_ARB_half_float_vertex
GL_ARB_imaging
GL_ARB_map_buffer_range
GL_ARB_multisample
GL_ARB_multitexture
GL_ARB_occlusion_query
GL_ARB_pixel_buffer_object
GL_ARB_point_parameters
GL_ARB_point_sprite
GL_ARB_provoking_vertex
GL_ARB_seamless_cube_map
GL_ARB_shader_objects
GL_ARB_shading_language_100
GL_ARB_shadow
GL_ARB_sync
GL_ARB_texture_border_clamp
GL_ARB_texture_buffer_object
GL_ARB_texture_compression
GL_ARB_texture_compression_rgtc
GL_ARB_texture_cube_map
GL_ARB_texture_env_add
GL_ARB_texture_env_combine
GL_ARB_texture_env_crossbar
GL_ARB_texture_env_dot3
GL_ARB_texture_float
GL_ARB_texture_mirrored_repeat
GL_ARB_texture_multisample
GL_ARB_texture_non_power_of_two
GL_ARB_texture_rectangle
GL_ARB_texture_rg
GL_ARB_transpose_matrix
GL_ARB_uniform_buffer_object
GL_ARB_vertex_array_bgra
GL_ARB_vertex_array_object
GL_ARB_vertex_buffer_object
GL_ARB_vertex_program
GL_ARB_vertex_shader
GL_ARB_window_pos
GL_ATI_draw_buffers
GL_ATI_texture_float
GL_ATI_texture_mirror_once
GL_EXTX_framebuffer_mixed_formats
GL_EXT_Cg_shader
GL_EXT_abgr
GL_EXT_bgra
GL_EXT_bindable_uniform
GL_EXT_blend_color
GL_EXT_blend_equation_separate
GL_EXT_blend_func_separate
GL_EXT_blend_minmax
GL_EXT_blend_subtract
GL_EXT_compiled_vertex_array
GL_EXT_depth_bounds_test
GL_EXT_direct_state_access
GL_EXT_draw_buffers2
GL_EXT_draw_instanced
GL_EXT_draw_range_elements
GL_EXT_fog_coord
GL_EXT_framebuffer_blit
GL_EXT_framebuffer_multisample
GL_EXT_framebuffer_object
GL_EXT_framebuffer_sRGB
GL_EXT_geometry_shader4
GL_EXT_gpu_program_parameters
GL_EXT_gpu_shader4
GL_EXT_multi_draw_arrays
GL_EXT_packed_depth_stencil
GL_EXT_packed_float
GL_EXT_packed_pixels
GL_EXT_pixel_buffer_object
GL_EXT_point_parameters
GL_EXT_provoking_vertex
GL_EXT_rescale_normal
GL_EXT_secondary_color
GL_EXT_separate_shader_objects
GL_EXT_separate_specular_color
GL_EXT_shadow_funcs
GL_EXT_stencil_two_side
GL_EXT_stencil_wrap
GL_EXT_texture3D
GL_EXT_texture_array
GL_EXT_texture_buffer_object
GL_EXT_texture_compression_latc
GL_EXT_texture_compression_rgtc
GL_EXT_texture_compression_s3tc
GL_EXT_texture_cube_map
GL_EXT_texture_edge_clamp
GL_EXT_texture_env_add
GL_EXT_texture_env_combine
GL_EXT_texture_env_dot3
GL_EXT_texture_filter_anisotropic
GL_EXT_texture_integer
GL_EXT_texture_lod
GL_EXT_texture_lod_bias
GL_EXT_texture_mirror_clamp
GL_EXT_texture_object
GL_EXT_texture_sRGB
GL_EXT_texture_shared_exponent
GL_EXT_texture_swizzle
GL_EXT_timer_query
GL_EXT_vertex_array
GL_EXT_vertex_array_bgra
GL_IBM_rasterpos_clip
GL_IBM_texture_mirrored_repeat
GL_KTX_buffer_region
GL_NVX_conditional_render
GL_NVX_gpu_memory_info
GL_NV_blend_square
GL_NV_conditional_render
GL_NV_copy_depth_to_color
GL_NV_copy_image
GL_NV_depth_buffer_float
GL_NV_depth_clamp
GL_NV_explicit_multisample
GL_NV_fence
GL_NV_float_buffer
GL_NV_fog_distance
GL_NV_fragment_program
GL_NV_fragment_program2
GL_NV_fragment_program_option
GL_NV_framebuffer_multisample_coverage
GL_NV_geometry_shader4
GL_NV_gpu_program4
GL_NV_half_float
GL_NV_light_max_exponent
GL_NV_multisample_coverage
GL_NV_multisample_filter_hint
GL_NV_occlusion_query
GL_NV_packed_depth_stencil
GL_NV_parameter_buffer_object
GL_NV_parameter_buffer_object2
GL_NV_pixel_data_range
GL_NV_point_sprite
GL_NV_primitive_restart
GL_NV_register_combiners
GL_NV_register_combiners2
GL_NV_shader_buffer_load
GL_NV_texgen_reflection
GL_NV_texture_barrier
GL_NV_texture_compression_vtc
GL_NV_texture_env_combine4
GL_NV_texture_expand_normal
GL_NV_texture_rectangle
GL_NV_texture_shader
GL_NV_texture_shader2
GL_NV_texture_shader3
GL_NV_transform_feedback
GL_NV_vertex_array_range
GL_NV_vertex_array_range2
GL_NV_vertex_buffer_unified_memory
GL_NV_vertex_program
GL_NV_vertex_program1_1
GL_NV_vertex_program2
GL_NV_vertex_program2_option
GL_NV_vertex_program3
GL_S3_s3tc
GL_SGIS_generate_mipmap
GL_SGIS_texture_lod
GL_SGIX_depth_texture
GL_SGIX_shadow
GL_SUN_slice_accumOffline
I can't test photoshop on wine any more for some reason, but does it do nothing with the mouse wheel except zoom? It does not make sense to me to have the wheel do nothing at all when used on its own. The normal intuition most people will have would be to scroll up and down. Annoyingly this is not the most useful thing in panoramas, but it's still more useful than doing nothing, which is what is currently happening in APP Linux.
Offline
Frédéric, can you please try to erase style sheets in APG 2.5 RC ? To do so, once application is started type Ctrl+U, erase content in all tabs and commit changes. All style content will be unloaded. Do the test once more in this configuration and tell me what happens.
Note that style will be restored at next APG start.
Offline
I just made your test: still slow. And the app froze again.
Offline
Here is the output of strace when it freezes (these lines repeat over and over):
[pid 18948] futex(0x7f7460363c30, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18948] futex(0x7f7460363c04, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1292950478, 61996000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
[pid 18948] futex(0x7f7460363c30, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18948] futex(0x7f7460363c04, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1292950478, 162255000}, ffffffff <unfinished ...>
[pid 18939] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 18939] futex(0x7f746cfa2700, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18939] futex(0x7f746cfa2784, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1681, {1292950478, 302113000}, ffffffff <unfinished ...>
[pid 18948] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 18948] futex(0x7f7460363c30, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18948] futex(0x7f7460363c04, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1292950478, 262444000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
[pid 18948] futex(0x7f7460363c30, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18948] futex(0x7f7460363c04, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1292950478, 362591000}, ffffffff <unfinished ...>
[pid 18939] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 18939] futex(0x7f746cfa2700, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18939] futex(0x7f746cfa2784, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1683, {1292950478, 502315000}, ffffffff <unfinished ...>
[pid 18948] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 18948] futex(0x7f7460363c30, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18948] futex(0x7f7460363c04, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1292950478, 462787000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
[pid 18948] futex(0x7f7460363c30, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18948] futex(0x7f7460363c04, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1292950478, 562939000}, ffffffff <unfinished ...>
[pid 18939] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 18939] futex(0x7f746cfa2700, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18939] futex(0x7f746cfa2784, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1685, {1292950478, 702525000}, ffffffff <unfinished ...>
[pid 18948] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 18948] futex(0x7f7460363c30, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18948] futex(0x7f7460363c04, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1292950478, 663099000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
[pid 18948] futex(0x7f7460363c30, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18948] futex(0x7f7460363c04, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1292950478, 763299000}, ffffffff <unfinished ...>
[pid 18939] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 18939] futex(0x7f746cfa2700, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18939] futex(0x7f746cfa2784, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1687, {1292950478, 902727000}, ffffffff <unfinished ...>
[pid 18948] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 18948] futex(0x7f7460363c30, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18948] futex(0x7f7460363c04, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1292950478, 863463000}, ffffffff) = -1 ETIMEDOUT (Connection timed out)
[pid 18948] futex(0x7f7460363c30, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18948] futex(0x7f7460363c04, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1292950478, 963598000}, ffffffff <unfinished ...>
[pid 18939] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 18939] futex(0x7f746cfa2700, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18939] futex(0x7f746cfa2784, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1689, {1292950479, 102951000}, ffffffff <unfinished ...>
[pid 18948] <... futex resumed> ) = -1 ETIMEDOUT (Connection timed out)
[pid 18948] futex(0x7f7460363c30, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 18948] futex(0x7f7460363c04, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME, 1, {1292950479, 63773000}, ffffffff <unfinished ...>Offline
futex ideom ? Man, that's just not used in our code.
After some research, I found this : http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=572162 which is also being blocked by futex issue. Solution was to change the theme of the software.
I have my gtk themes config set to "use my KDE styles". Of the
available widget themes on this machine, I can reproduce the bug using:
Cleanlooks
Oxygen (the default)
GTK+
Phase
but *not* when I use:
CDE
QTcurve
Motif
Plastique
Offline
!!! Je teste ça dans la soirée... Ça règle aussi le problème de lenteur du GUI ? Ou juste le freeze ?
Offline
Je pense aux deux qui m'ont l'air d'être liés. Le futex est une techno linux qui permet de faire un mutex rapide. Nous on utilise massivement des mutex. Si l'implementation sous linux fait que cela rame, alors on a un soucis global dans l'éditeur qui rame partout. L'explication me semble belle et très plausible. Le hic, c'est pourquoi le thème influence quelque chose de totalement non lié au thème ( ou alors, c'est le thème qui accède à certaines ressources sous forme mutexé et du coup ramage et problème ).
Note : on a installé une debian SID ici sous virtualbox et c'est aussi rapide que sur ubuntu ( pas de ralentissement notable ).
Question connexe : quel bureau ? KDE ? Gnome ? Autre ?
Offline
Je viens de faire plein de tests : aucun changement. J'ai testé d'autres Window Manager (à la place de KDE) : toujours pareil. Je pense que le soucis est plus au niveau du driver de la carte graphique.
Y'a déjà eu le problème, il y a quelques mois, et c'était retombé en marche suite à une mise à jour d'APG. Mais je ne me souviens plus de laquelle (pour retrouver le changement éventuel)...
Offline
After investigation, problem seems to come from the editor's grid using alpha blending, X11 being very CPU consuming to do that.
You can enable composite extensions on your machine to make it more efficient on X11 side, but this won't be possible in all cases (dual screen configuration for example).
Another solution is in Autopano to set editor's grid colors to have opacity = 100% (edit > settings), and see if performances are restored. Can you please try that and give me some feedback ?
Last edited by ygilquin (2011-01-07 15:05:43)
Offline
Ok, here are the results.
The Composite extension was already activated on my Xorg config. I added another param I found on a forum, but it didn't change anything.
Then I used 100% opacity for the grid: very little change with the RC installed from the deb package (still slow), but it improved the speed a little bit more on the debug version you sent me. With the same settings, this release is faster, even to startup...
But it is still slower than the Windows version (and remember that I tested in a virtual Windows, on the same machine! So, without any accelerated extensions...)
And in both cases, the yellow rectangle tool in the control point editor is still veeeeery slow.
Offline
Frédéric, can you please try to launch Autopano with option -graphicssystem opengl and report your impression on performance in control point editor ? Editor should be broken with this option, but CPE works.
Offline
No change, but the editor still work, so I think something didn't work. In fact, in the console, I get:
Unable to load graphicssystem "opengl"
Offline
Could you show me some strace output with same launching option ?
Offline
I'll test that tonight...
Offline
Ok, with the trace, I found that the graphicssystem dir was searched in the following paths:
/tmp/AutopanoGiga/graphicssystems/
/tmp/AutopanoGiga/graphicssystems/
/usr/lib/kde4/plugins/graphicssystems/
/usr/lib/kde4/plugins/graphicssystems/
but it is located in /usr/lib/qt4/plugins on my system. I made a symbolic link in /tmp/AutopanoGiga, and it worked.
The result is that the CP editor is much faster: same speed as other tools.
Offline
Can you also mention what Qt libs are loaded within Autopano process at runtime (from /tmp/AutopanoGiga/, /usr/lib/kde4/, /usr/lib/qt4/, other) ?
Offline
The ones from /tmp/Autopano. I tried to use the system ones, but it does not work (some dependent libs are not correct).
Offline