lmuse-developer
|
From: Geoff King <gsking1@gm...> - 2010-08-21 18:27:15
|
Hello, I was trying to using the midi editors plugin "SwingQuantize1" today on a sample and it keeps giving Segmentation fault. All I have to do to crash muse is to select all (about 12 measures) and then click the SwingQuantize1 plugin. If nothing is selected there is no crash. I have never used this feature before. The "DoNothing" and "RemoveShortEvents" also crash. This is with SVN 439cd Hope this helps. Thanks, Geoff |
|
From: Geoff King <gsking1@gm...> - 2010-08-21 20:22:32
|
Sorry if this is the second time you've gotten this email.... Evolution is having problems recently... Hello, I was trying to using the midi editors plugin "SwingQuantize1" today to on a sample and it keeps giving Segmentation fault. All I have to do to crash muse is to select all (about 12 measures) and then click the SwingQuantize1 plugin. If nothing is selected there is no crash. The "DoMothing" and "RemoveShortEvents" also crash. This is with SVN 439cd Hope this helps. Thanks, Geoff Geoff |
|
From: Robert Jonsson <spamatica@gm...> - 2010-08-21 19:30:23
|
Hi Geoff, Ok, did the gui for the plugin show up? This particular one is based on PyQt4 so this needs to be installed. Though if it's not it should definitely NOT crash. I can't get it to crash myself... Does any of the other plugins work? For instance the DoNothing test plugin. Are you by any chance on a 64 bit system? Haven't tested that. - Last, a little plug for this feature. The plugin interface is extremely simple; if anyone feels like trying to process midi messages this should be a very easy way to give it a try. A file with all selected midi events are put into a file and this file is in turn read by the plugin program. The plugin does whatever it wants with the events and returns a processed list to MusE. There is a readme in the plugin dir under share/scripts Regards, Robert 2010/8/21 Geoff King <gsking1@...>: > Hello, > I was trying to using the midi editors plugin "SwingQuantize1" today on > a sample and it keeps giving Segmentation fault. All I have to do to > crash muse is to select all (about 12 measures) and then click the > SwingQuantize1 plugin. If nothing is selected there is no crash. I have > never used this feature before. > > The "DoNothing" and "RemoveShortEvents" also crash. > > This is with SVN 439cd > > Hope this helps. > > Thanks, Geoff > > > > > ------------------------------------------------------------------------------ > This SF.net email is sponsored by > > Make an app they can't live without > Enter the BlackBerry Developer Challenge > http://p.sf.net/sfu/RIM-dev2dev > _______________________________________________ > Lmuse-developer mailing list > Lmuse-developer@... > https://lists.sourceforge.net/lists/listinfo/lmuse-developer > |
|
From: Geoff King <gsking1@gm...> - 2010-08-22 01:33:32
|
Hi Robert,
I have PyQt4-4.7.3.1.fc13.i686 installed and it is a 32-bit system.
I did get lucky a few times and see the dialog, but 90% of the time it
crashes.
The "DoNothing" and "RemoveShortEvents" also crashed on a few tests.
I recompiled with debug option and ran in gdb to get this bt. Hope
this is helpful.
startSongInfo!!!!
script input filename=/tmp/fileR05um9
Program received signal SIGSEGV, Segmentation fault.
Event::Event (this=0xbfffe804, e=...) at event.cpp:103
103 ++(ev->refCount);
Missing separate debuginfos, use:.....
[cut these out, let me know if you need me to install more]
(gdb) bt
#0 Event::Event (this=0xbfffe804, e=...) at event.cpp:103
#1 0x080f2411 in Song::executeScript (this=0x84cf750, scriptfile=
0x8fab508 "/usr/local/share/muse/scripts/SwingQuantize1", parts=0x8ec7f08,
quant=1, onlyIfSelected=true) at song.cpp:3439
#2 0x08134e77 in PianoRoll::execDeliveredScript (this=0x8ec85c0, id=4)
at pianoroll.cpp:1091
#3 0x0814a9e0 in PianoRoll::qt_invoke (this=0x8ec85c0, _id=87, _o=0xbfffe950)
at moc_pianoroll.cpp:239
#4 0x50069ba2 in QObject::activate_signal(QConnectionList*, QUObject*) ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#5 0x5006b285 in QObject::activate_signal(int, int) ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#6 0x503b55b4 in QSignal::intSignal(int) ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#7 0x50085a32 in QSignal::activate() () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#8 0x50172e65 in QPopupMenu::mouseReleaseEvent(QMouseEvent*) ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#9 0x5009fe14 in QWidget::event(QEvent*) ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#10 0x5000afa5 in QApplication::internalNotify(QObject*, QEvent*) ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#11 0x5000cbcf in QApplication::notify(QObject*, QEvent*) ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
---Type <return> to continue, or q <return> to quit---
#12 0x080e717e in MuseApplication::notify (this=0xbffff204, receiver=
0x8ecfd60, event=0xbfffed48) at app.cpp:3004
#13 0x4ffab8ff in QApplication::sendSpontaneousEvent(QObject*, QEvent*) ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#14 0x4ffab68e in QETWidget::translateMouseEvent(_XEvent const*) ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#15 0x4ffaa13a in QApplication::x11ProcessEvent(_XEvent*) ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#16 0x4ffbb81b in QEventLoop::processEvents(unsigned int) ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#17 0x50022000 in QEventLoop::enterLoop() ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#18 0x50021ea7 in QEventLoop::exec() () from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#19 0x5000b670 in QApplication::exec() ()
from /usr/lib/qt-3.3/lib/libqt-mt.so.3
#20 0x080e626c in main (argc=135422942, argv=0x8125540) at app.cpp:3366
On Sat, Aug 21, 2010 at 3:30 PM, Robert Jonsson <spamatica@...> wrote:
> Hi Geoff,
>
> Ok, did the gui for the plugin show up? This particular one is based
> on PyQt4 so this needs to be installed.
> Though if it's not it should definitely NOT crash.
> I can't get it to crash myself...
>
> Does any of the other plugins work? For instance the DoNothing test plugin.
>
> Are you by any chance on a 64 bit system? Haven't tested that.
>
> -
> Last, a little plug for this feature.
> The plugin interface is extremely simple; if anyone feels like trying
> to process midi messages this should be a very easy way to give it a
> try.
>
> A file with all selected midi events are put into a file and this file
> is in turn read by the plugin program. The plugin does whatever it
> wants with the events and returns a processed list to MusE. There is a
> readme in the plugin dir under share/scripts
>
> Regards,
> Robert
>
>
>
> 2010/8/21 Geoff King <gsking1@...>:
>> Hello,
>> I was trying to using the midi editors plugin "SwingQuantize1" today on
>> a sample and it keeps giving Segmentation fault. All I have to do to
>> crash muse is to select all (about 12 measures) and then click the
>> SwingQuantize1 plugin. If nothing is selected there is no crash. I have
>> never used this feature before.
>>
>> The "DoNothing" and "RemoveShortEvents" also crash.
>>
>> This is with SVN 439cd
>>
>> Hope this helps.
>>
>> Thanks, Geoff
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Lmuse-developer mailing list
>> Lmuse-developer@...
>> https://lists.sourceforge.net/lists/listinfo/lmuse-developer
>>
>
|
|
From: Robert Jonsson <spamatica@gm...> - 2010-08-22 18:04:49
|
Hi Geoff, is this with a specific song or does it happen even if you make just a test ? Please try to it as simple as possible. I see where it is going wrong but I can not understand how, unless there is some special case it should just work. /Robert 2010/8/22 Geoff King <gsking1@...>: > Hi Robert, > I have PyQt4-4.7.3.1.fc13.i686 installed and it is a 32-bit system. > I did get lucky a few times and see the dialog, but 90% of the time it > crashes. > The "DoNothing" and "RemoveShortEvents" also crashed on a few tests. > > I recompiled with debug option and ran in gdb to get this bt. Hope > this is helpful. > > startSongInfo!!!! > script input filename=/tmp/fileR05um9 > > Program received signal SIGSEGV, Segmentation fault. > Event::Event (this=0xbfffe804, e=...) at event.cpp:103 > 103 ++(ev->refCount); > Missing separate debuginfos, use:..... > [cut these out, let me know if you need me to install more] > (gdb) bt > #0 Event::Event (this=0xbfffe804, e=...) at event.cpp:103 > #1 0x080f2411 in Song::executeScript (this=0x84cf750, scriptfile= > 0x8fab508 "/usr/local/share/muse/scripts/SwingQuantize1", parts=0x8ec7f08, > quant=1, onlyIfSelected=true) at song.cpp:3439 > #2 0x08134e77 in PianoRoll::execDeliveredScript (this=0x8ec85c0, id=4) > at pianoroll.cpp:1091 > #3 0x0814a9e0 in PianoRoll::qt_invoke (this=0x8ec85c0, _id=87, _o=0xbfffe950) > at moc_pianoroll.cpp:239 > #4 0x50069ba2 in QObject::activate_signal(QConnectionList*, QUObject*) () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #5 0x5006b285 in QObject::activate_signal(int, int) () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #6 0x503b55b4 in QSignal::intSignal(int) () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #7 0x50085a32 in QSignal::activate() () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #8 0x50172e65 in QPopupMenu::mouseReleaseEvent(QMouseEvent*) () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #9 0x5009fe14 in QWidget::event(QEvent*) () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #10 0x5000afa5 in QApplication::internalNotify(QObject*, QEvent*) () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #11 0x5000cbcf in QApplication::notify(QObject*, QEvent*) () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > ---Type <return> to continue, or q <return> to quit--- > #12 0x080e717e in MuseApplication::notify (this=0xbffff204, receiver= > 0x8ecfd60, event=0xbfffed48) at app.cpp:3004 > #13 0x4ffab8ff in QApplication::sendSpontaneousEvent(QObject*, QEvent*) () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #14 0x4ffab68e in QETWidget::translateMouseEvent(_XEvent const*) () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #15 0x4ffaa13a in QApplication::x11ProcessEvent(_XEvent*) () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #16 0x4ffbb81b in QEventLoop::processEvents(unsigned int) () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #17 0x50022000 in QEventLoop::enterLoop() () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #18 0x50021ea7 in QEventLoop::exec() () from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #19 0x5000b670 in QApplication::exec() () > from /usr/lib/qt-3.3/lib/libqt-mt.so.3 > #20 0x080e626c in main (argc=135422942, argv=0x8125540) at app.cpp:3366 > > > On Sat, Aug 21, 2010 at 3:30 PM, Robert Jonsson <spamatica@...> wrote: >> Hi Geoff, >> >> Ok, did the gui for the plugin show up? This particular one is based >> on PyQt4 so this needs to be installed. >> Though if it's not it should definitely NOT crash. >> I can't get it to crash myself... >> >> Does any of the other plugins work? For instance the DoNothing test plugin. >> >> Are you by any chance on a 64 bit system? Haven't tested that. >> >> - >> Last, a little plug for this feature. >> The plugin interface is extremely simple; if anyone feels like trying >> to process midi messages this should be a very easy way to give it a >> try. >> >> A file with all selected midi events are put into a file and this file >> is in turn read by the plugin program. The plugin does whatever it >> wants with the events and returns a processed list to MusE. There is a >> readme in the plugin dir under share/scripts >> >> Regards, >> Robert >> >> >> >> 2010/8/21 Geoff King <gsking1@...>: >>> Hello, >>> I was trying to using the midi editors plugin "SwingQuantize1" today on >>> a sample and it keeps giving Segmentation fault. All I have to do to >>> crash muse is to select all (about 12 measures) and then click the >>> SwingQuantize1 plugin. If nothing is selected there is no crash. I have >>> never used this feature before. >>> >>> The "DoNothing" and "RemoveShortEvents" also crash. >>> >>> This is with SVN 439cd >>> >>> Hope this helps. >>> >>> Thanks, Geoff >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> This SF.net email is sponsored by >>> >>> Make an app they can't live without >>> Enter the BlackBerry Developer Challenge >>> http://p.sf.net/sfu/RIM-dev2dev >>> _______________________________________________ >>> Lmuse-developer mailing list >>> Lmuse-developer@... >>> https://lists.sourceforge.net/lists/listinfo/lmuse-developer >>> >> > |
|
From: Geoff King <gsking1@gm...> - 2010-08-22 18:44:01
|
On Sun, 2010-08-22 at 20:04 +0200, Robert Jonsson wrote: > Hi Geoff, > > is this with a specific song or does it happen even if you make just a test ? > Please try to it as simple as possible. > I see where it is going wrong but I can not understand how, unless > there is some special case it should just work. > Okay a quick test was done and NO crash. I removed ALL audio related tracks (5 inputs, ~9 wavs, and 1 out) leaving only 5 midi tracks and saved this to a new file. I then had No problems or crashes using the plugins. I will mess around with this a little more this evening to see if I can narrow it down some more. |
|
From: Robert Jonsson <spamatica@gm...> - 2010-08-22 18:58:46
|
Alright, sounds good. /Robert 2010/8/22 Geoff King <gsking1@...>: > On Sun, 2010-08-22 at 20:04 +0200, Robert Jonsson wrote: >> Hi Geoff, >> >> is this with a specific song or does it happen even if you make just a test ? >> Please try to it as simple as possible. >> I see where it is going wrong but I can not understand how, unless >> there is some special case it should just work. >> > > Okay a quick test was done and NO crash. I removed ALL audio related > tracks (5 inputs, ~9 wavs, and 1 out) leaving only 5 midi tracks and > saved this to a new file. I then had No problems or crashes using the > plugins. > > I will mess around with this a little more this evening to see if I can > narrow it down some more. > > |