From: Mathias L. <mat...@br...> - 2004-08-25 17:54:58
|
Another one. When adding a freeverb MusE segfaults as soon as one changes any of the values. gdb gives this error: 0x432848af in QRect::height() const (this=0x7309c0bb) at /usr/local/qt/include/qrect.h:251 251 { return y2 - y1 + 1; } My guess is it's because Freeverb hasn't caught up with the awl widgets (all the usual plugins seem to work ok, err at least those I tested). /Mathias |
From: Werner S. <ws...@se...> - 2004-08-25 18:24:59
|
On Wednesday 25 August 2004 19:58, Mathias Lundgren wrote: > Another one. When adding a freeverb MusE segfaults as soon as one > changes any of the values. gdb gives this error: > > 0x432848af in QRect::height() const (this=0x7309c0bb) at > /usr/local/qt/include/qrect.h:251 > 251 { return y2 - y1 + 1; } > > My guess is it's because Freeverb hasn't caught up with the awl widgets > (all the usual plugins seem to work ok, err at least those I tested). exactly; qt-designer generated *ui files for plugins currently do not work. /werner |
From: Mathias L. <mat...@br...> - 2004-08-25 18:40:54
|
ons 2004-08-25 klockan 20.27 skrev Werner Schweer: > On Wednesday 25 August 2004 19:58, Mathias Lundgren wrote: > > Another one. When adding a freeverb MusE segfaults as soon as one > > changes any of the values. gdb gives this error: > > > > 0x432848af in QRect::height() const (this=0x7309c0bb) at > > /usr/local/qt/include/qrect.h:251 > > 251 { return y2 - y1 + 1; } > > > > My guess is it's because Freeverb hasn't caught up with the awl widgets > > (all the usual plugins seem to work ok, err at least those I tested). > > exactly; qt-designer generated *ui files for plugins currently do not > work. > Noticed that removing the two pluginfiles in $INST_PREFIX/share/muse/plugins is a workaround that makes freeverb use the default gui instead. To be honest, I'm not sure if I can see that this workaround differ that much. Are those .ui just a proof of concept? /Mathias |
From: Werner S. <ws...@se...> - 2004-08-25 18:54:45
|
On Wednesday 25 August 2004 20:43, Mathias Lundgren wrote: > ons 2004-08-25 klockan 20.27 skrev Werner Schweer: > > On Wednesday 25 August 2004 19:58, Mathias Lundgren wrote: > > > Another one. When adding a freeverb MusE segfaults as soon as one > > > changes any of the values. gdb gives this error: > > > > > > 0x432848af in QRect::height() const (this=0x7309c0bb) at > > > /usr/local/qt/include/qrect.h:251 > > > 251 { return y2 - y1 + 1; } > > > > > > My guess is it's because Freeverb hasn't caught up with the awl widgets > > > (all the usual plugins seem to work ok, err at least those I tested). > > > > exactly; qt-designer generated *ui files for plugins currently do not > > work. > > Noticed that removing the two pluginfiles in > $INST_PREFIX/share/muse/plugins is a workaround that makes freeverb use > the default gui instead. To be honest, I'm not sure if I can see that > this workaround differ that much. Are those .ui just a proof of concept? yes its essentially a proof of concept. I will extend the concept with the new awl library somewhat. Goal is to enable a user to construct some more complex custom guis for plugins without compiling any code. /werner |
From: Mathias L. <mat...@br...> - 2004-08-25 19:11:31
|
ons 2004-08-25 klockan 20.57 skrev Werner Schweer: > On Wednesday 25 August 2004 20:43, Mathias Lundgren wrote: > > ons 2004-08-25 klockan 20.27 skrev Werner Schweer: > > > On Wednesday 25 August 2004 19:58, Mathias Lundgren wrote: > > > > Another one. When adding a freeverb MusE segfaults as soon as one > > > > changes any of the values. gdb gives this error: > > > > > > > > 0x432848af in QRect::height() const (this=0x7309c0bb) at > > > > /usr/local/qt/include/qrect.h:251 > > > > 251 { return y2 - y1 + 1; } > > > > > > > > My guess is it's because Freeverb hasn't caught up with the awl widgets > > > > (all the usual plugins seem to work ok, err at least those I tested). > > > > > > exactly; qt-designer generated *ui files for plugins currently do not > > > work. > > > > Noticed that removing the two pluginfiles in > > $INST_PREFIX/share/muse/plugins is a workaround that makes freeverb use > > the default gui instead. To be honest, I'm not sure if I can see that > > this workaround differ that much. Are those .ui just a proof of concept? > > yes its essentially a proof of concept. > I will extend the concept with the new awl library somewhat. > Goal is to enable a user to construct some more complex custom guis > for plugins without compiling any code. > > /werner I didn't even know that feature existed. Joachim, are you listening to this? ;-) In case this is supposed to be supported in the future, it seems like a good spot for eye-candy. /Mathias |
From: Werner S. <ws...@se...> - 2004-08-25 21:24:40
|
On Wednesday 25 August 2004 21:14, Mathias Lundgren wrote: > ons 2004-08-25 klockan 20.57 skrev Werner Schweer: > > On Wednesday 25 August 2004 20:43, Mathias Lundgren wrote: > > > ons 2004-08-25 klockan 20.27 skrev Werner Schweer: > > > > On Wednesday 25 August 2004 19:58, Mathias Lundgren wrote: > > > > > Another one. When adding a freeverb MusE segfaults as soon as one > > > > > changes any of the values. gdb gives this error: > > > > > > > > > > 0x432848af in QRect::height() const (this=0x7309c0bb) at > > > > > /usr/local/qt/include/qrect.h:251 > > > > > 251 { return y2 - y1 + 1; } > > > > > > > > > > My guess is it's because Freeverb hasn't caught up with the awl > > > > > widgets (all the usual plugins seem to work ok, err at least those > > > > > I tested). > > > > > > > > exactly; qt-designer generated *ui files for plugins currently do not > > > > work. > > > > > > Noticed that removing the two pluginfiles in > > > $INST_PREFIX/share/muse/plugins is a workaround that makes freeverb use > > > the default gui instead. To be honest, I'm not sure if I can see that > > > this workaround differ that much. Are those .ui just a proof of > > > concept? > > > > yes its essentially a proof of concept. > > I will extend the concept with the new awl library somewhat. > > Goal is to enable a user to construct some more complex custom guis > > for plugins without compiling any code. > > > > /werner > > I didn't even know that feature existed. Joachim, are you listening to > this? ;-) In case this is supposed to be supported in the future, it > seems like a good spot for eye-candy. it's even documented! see README.ladspaguis /werner |
From: Mathias L. <mat...@br...> - 2004-08-25 21:39:14
|
ons 2004-08-25 klockan 23.27 skrev Werner Schweer: > On Wednesday 25 August 2004 21:14, Mathias Lundgren wrote: > > ons 2004-08-25 klockan 20.57 skrev Werner Schweer: > > > On Wednesday 25 August 2004 20:43, Mathias Lundgren wrote: > > > > ons 2004-08-25 klockan 20.27 skrev Werner Schweer: > > > > > On Wednesday 25 August 2004 19:58, Mathias Lundgren wrote: > > > > > > Another one. When adding a freeverb MusE segfaults as soon as one > > > > > > changes any of the values. gdb gives this error: > > > > > > > > > > > > 0x432848af in QRect::height() const (this=0x7309c0bb) at > > > > > > /usr/local/qt/include/qrect.h:251 > > > > > > 251 { return y2 - y1 + 1; } > > > > > > > > > > > > My guess is it's because Freeverb hasn't caught up with the awl > > > > > > widgets (all the usual plugins seem to work ok, err at least those > > > > > > I tested). > > > > > > > > > > exactly; qt-designer generated *ui files for plugins currently do not > > > > > work. > > > > > > > > Noticed that removing the two pluginfiles in > > > > $INST_PREFIX/share/muse/plugins is a workaround that makes freeverb use > > > > the default gui instead. To be honest, I'm not sure if I can see that > > > > this workaround differ that much. Are those .ui just a proof of > > > > concept? > > > > > > yes its essentially a proof of concept. > > > I will extend the concept with the new awl library somewhat. > > > Goal is to enable a user to construct some more complex custom guis > > > for plugins without compiling any code. > > > > > > /werner > > > > I didn't even know that feature existed. Joachim, are you listening to > > this? ;-) In case this is supposed to be supported in the future, it > > seems like a good spot for eye-candy. > > it's even documented! see README.ladspaguis > > /werner I'm sure it's been there all the time, it's just that... Well, erhm... I'm one of those people who only read README:s when something goes wrong or when I really have to. I've probably read it sometime long ago, since I've known there was some special deal about the freeverb gui. Just not exactly what. BTW, you forgot to say "RTFM!". ;-) /Mathias |