From: Robert J. <rj...@sp...> - 2005-01-10 12:48:32
|
Hi Shayne, > hi there! > > this is my first posting to this list, so apologies it's with a problem! > but first, i guess i'll point out what a great piece of software muse > is! having made the switch from windows only ... six months ago? ... i > have to say that muse is a program that i see as really close to > providing me with everything i had on windows and more (along with all > the other great open-source audio software out there - you know who you > are!) ... > > now, onto my problem, which is pretty easy to describe - > > i have compiled muse with these options: > /configure --enable-vst --enable-maintainer-mode > --disable-doxy-treeview --enable-optimize --prefix=/usr > > but when i start jack and start muse from the command line, this is what > i get: > > > [mrmachine@localhost mrmachine]$ muse no locale > > <muse_en_AU.UTF-8>/</usr/share/muse/locale> > > fst signal handler 11, thread = 0xb7fdd9a0 > > Segmentation fault > > i can run jack_fst fine on it's own, and muse runs fine if i disable vst > support when calling it. > > i am on a planet ccrma fedora core 2 box, with a 2.6.9 kernel with all > the patches (latest cvs jack, alsa) I think I get this behaviour also. I've only noted that if I start MusE from the directory where the VSTs are and do: export VST_PATH=. (not sure about the name of the variable) it works. I've not tried to debug this yet, I figured it was a problem with my wine configuration. Since you get the same but other fst apps work that might not be the case. I'll try to investigate tonight. Regards, Robert > > any ideas? > > shayne > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user |
From: Robert J. <rj...@sp...> - 2005-01-11 08:23:22
|
<...> > >If possible, try 2004-05-05. > > > >I tried to make sense of it but this far the only sensible solution is t> o use > >the 20040505 release of Wine (or run the synths through jack-fst since t> hat > >supposedly works ok). > > > > > hmm, i might give the built-in vst support a miss if it means > downgrading wine - i've found the latest release to be the most > generally successful for my purposes, whereas i could only justify the > 20040505 downgrade in the context of vst support :( > > yeah - i had been loading vst's into muse by running them with jack_fst, > so i'll just continue to do that ... > > one question though - if vst support is enabled and working, does that > mean vst plugins are saved and loaded with the project? Yep. Though it has never been particularily stable for me. This far I have blamed Wine. /Robert |
From: Shayne O'C. <fo...@ma...> - 2005-01-10 16:14:31
|
Robert Jonsson wrote: >Hi Shayne, > > > >>hi there! >> >>this is my first posting to this list, so apologies it's with a problem! >>but first, i guess i'll point out what a great piece of software muse >>is! having made the switch from windows only ... six months ago? ... i >>have to say that muse is a program that i see as really close to >>providing me with everything i had on windows and more (along with all >>the other great open-source audio software out there - you know who you >>are!) ... >> >>now, onto my problem, which is pretty easy to describe - >> >>i have compiled muse with these options: >>/configure --enable-vst --enable-maintainer-mode >>--disable-doxy-treeview --enable-optimize --prefix=/usr >> >>but when i start jack and start muse from the command line, this is what >>i get: >> >> >> >>>[mrmachine@localhost mrmachine]$ muse no locale >>><muse_en_AU.UTF-8>/</usr/share/muse/locale> >>>fst signal handler 11, thread = 0xb7fdd9a0 >>>Segmentation fault >>> >>> >>i can run jack_fst fine on it's own, and >> >> >muse runs fine if i disable vst > > >>support when calling it. >> >>i am on a planet ccrma fedora core 2 box, with a 2.6.9 kernel with all >>the patches (latest cvs jack, alsa) >> >> > >I think I get this behaviour also. > >I've only noted that if I start MusE from the directory where the VSTs are >and do: export VST_PATH=. (not sure about the name of the variable) it works. > this doesn't seem to work for me :( shayne |
From: Robert J. <rj...@sp...> - 2005-01-10 22:17:32
|
Hi, > >>now, onto my problem, which is pretty easy to describe - > >> > >>i have compiled muse with these options: > >>/configure --enable-vst --enable-maintainer-mode > >>--disable-doxy-treeview --enable-optimize --prefix=/usr > >> > >>but when i start jack and start muse from the command line, this is what > >> > >>i get: > >>>[mrmachine@localhost mrmachine]$ muse no locale > >>><muse_en_AU.UTF-8>/</usr/share/muse/locale> > >>>fst signal handler 11, thread = 0xb7fdd9a0 > >>>Segmentation fault > >> > >>i can run jack_fst fine on it's own, and > > > >muse runs fine if i disable vst > > > >>support when calling it. > >> > >>i am on a planet ccrma fedora core 2 box, with a 2.6.9 kernel with all > >>the patches (latest cvs jack, alsa) > > > >I think I get this behaviour also. > > > >I've only noted that if I start MusE from the directory where the VSTs are > >and do: export VST_PATH=. (not sure about the name of the variable) it > > works. > > this doesn't seem to work for me :( Right, it's a separate problem. I need to look into that... I think I have discovered the origins of your crash though. I've tried several versions of Wine and all crash like this except Wine-20040505. I think there is somekind of memory corruption, very hard to debug. /Robert > > shayne > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user -- http://spamatica.se/music/ |
From: Shayne O'C. <fo...@ma...> - 2005-01-10 22:37:26
|
Robert Jonsson wrote: >I've tried several >versions of Wine and all crash like this except Wine-20040505. I think there >is somekind of memory corruption, very hard to debug. > >/Robert > > > well, if there's any sort of testing i can do on my end, just let me know (i'm not really much of a hacker, but perhaps there's some command-line output that would be useful to you). shayne |
From: Robert J. <rj...@sp...> - 2005-01-10 22:44:47
|
m=E5ndagen den 10 januari 2005 23.41 skrev Shayne O'Connor: > Robert Jonsson wrote: > >I've tried several > >versions of Wine and all crash like this except Wine-20040505. I think > > there is somekind of memory corruption, very hard to debug. > > > >/Robert > > well, if there's any sort of testing i can do on my end, just let me > know (i'm not really much of a hacker, but perhaps there's some > command-line output that would be useful to you). I forgot to ask for the record, what version of Wine do you have installed? If possible, try 2004-05-05.=20 I tried to make sense of it but this far the only sensible solution is to u= se=20 the 20040505 release of Wine (or run the synths through jack-fst since that= =20 supposedly works ok). > > shayne > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user =2D-=20 http://spamatica.se/music/ |
From: Shayne O'C. <fo...@ma...> - 2005-01-11 00:27:48
|
Robert Jonsson wrote: >m=E5ndagen den 10 januari 2005 23.41 skrev Shayne O'Connor: > =20 > >>Robert Jonsson wrote: >> =20 >> >>>I've tried several >>>versions of Wine and all crash like this except Wine-20040505. I think >>>there is somekind of memory corruption, very hard to debug. >>> >>>/Robert >>> =20 >>> >>well, if there's any sort of testing i can do on my end, just let me >>know (i'm not really much of a hacker, but perhaps there's some >>command-line output that would be useful to you). >> =20 >> > >I forgot to ask for the record, what version of Wine do you have install= ed? > > =20 > i have the latest wine 20041201. >If possible, try 2004-05-05.=20 > >I tried to make sense of it but this far the only sensible solution is t= o use=20 >the 20040505 release of Wine (or run the synths through jack-fst since t= hat=20 >supposedly works ok). > =20 > hmm, i might give the built-in vst support a miss if it means downgrading wine - i've found the latest release to be the most generally successful for my purposes, whereas i could only justify the 20040505 downgrade in the context of vst support :( yeah - i had been loading vst's into muse by running them with jack_fst, so i'll just continue to do that ... one question though - if vst support is enabled and working, does that mean vst plugins are saved and loaded with the project? shayne |
From: Neil K. <nkl...@sb...> - 2005-01-11 06:34:18
|
Robert Jonsson wrote: >>If possible, try 2004-05-05. >> >>I tried to make sense of it but this far the only sensible solution is to use >>the 20040505 release of Wine (or run the synths through jack-fst since that >>supposedly works ok). FYI: On my FC1/planetCCRMA machine, jack_fst and muse0.7.1pre3 (with vst enabled) segfault using the latest version of wine (muse -V is fine). It's even worse with wine-20040505: the whole machine locks up (!). But dssi-vst works beautifully with every plugin I've tried. I'll do anything I can to help debug. --Neil |
From: Robert J. <rj...@sp...> - 2005-01-17 20:38:46
|
Hi Neil, m=E5ndagen den 10 januari 2005 23.36 skrev Neil Klepeis: > Robert Jonsson wrote: > >>If possible, try 2004-05-05. > >> > >>I tried to make sense of it but this far the only sensible solution is = to > >> use the 20040505 release of Wine (or run the synths through jack-fst > >> since that supposedly works ok). > > FYI: On my FC1/planetCCRMA machine, jack_fst and muse0.7.1pre3 (with > vst enabled) segfault using the latest version of wine (muse -V is > fine). It's even worse with wine-20040505: the whole machine locks up > (!). But dssi-vst works beautifully with every plugin I've tried. I'll > do anything I can to help debug. --Neil Would be great, no clues at the moment though. Please report back anything = you=20 might find out. /Robert > > > > > > ------------------------------------------------------- > The SF.Net email is sponsored by: Beat the post-holiday blues > Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. > It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user =2D-=20 http://spamatica.se/music/ |
From: Robert J. <rj...@sp...> - 2005-01-17 20:52:42
|
tisdagen den 11 januari 2005 01.31 skrev Shayne O'Connor: > one question though - if vst support is enabled and working, does that > mean vst plugins are saved and loaded with the project? > I'm sorry if I answered this already. But, yes, all settings are then stored in the songfile. And, ofcourse the same as to Neil goes to you, no clues from my part yet, but if you find something out, please let us know. /Robert -- http://spamatica.se/music/ |
From: Shayne O'C. <fo...@ma...> - 2005-01-20 01:42:58
|
Robert Jonsson wrote: >tisdagen den 11 januari 2005 01.31 skrev Shayne O'Connor: > > >>one question though - if vst support is enabled and working, does that >>mean vst plugins are saved and loaded with the project? >> >> >> >I'm sorry if I answered this already. But, yes, all settings are then stored >in the songfile. > > > that sounds great ... >And, ofcourse the same as to Neil goes to you, no clues from my part yet, but >if you find something out, please let us know. > > > well, i'm not much of a guru, but i've tried using wine20040505 wine 20041201 and the latest 2005 one - each time recompiling jack_fst - and none of these work (no matter if i launch from VST folder). the same segmentation fault. not sure if this could be a clue, but when i was originally trying to get jack_fst up and running (for stand-alone use), this is the same message i would get - it was very frustrating. but i found that checking the "no memory lock" box in qjackctl allowed me to use jack_fst. i don't check this box anymore, so obviously that problem was addressed, but i can't remember if it was an update of wine or jack or kernel which fixed the problem ... but anyway, maybe it's the same sort of thing happening here in a m-lock context (as you may have guessed, my technical linux knowledge is a bit ... whack ... i have no real idea what memory lock does, all i know is that previously that was what was causing similar jack_fst errors for me). just to help me better get my head around what's happening when muse is started with VST support - what is muse actually doing when it calls jack_fst? i don't understand how jack_fst can be "started" without calling a particular VST effect or instrument ... (i can't remember at the moment if a VST_PATH has to be exported before starting with VST support ... if so, is jack_fst trying to load *all* the plugins in VST directory into memory?). anyway, hope these haphazard thoughts may provide food for more able thoughts :) shayne |
From: Shayne O'C. <fo...@ma...> - 2005-01-20 22:59:55
|
al...@pa... wrote: >>well, i'm not much of a guru, but i've tried using wine20040505 wine >>20041201 and the latest 2005 one - each time recompiling jack_fst - and >>none of these work (no matter if i launch from VST folder). the same >>segmentation fault. >> >> >> > >Seems that fst has serious probz lately! Read somewhere that >20040505 release would be the best to use for it but fst had >probz with glibc in some manor. I couldnt sort it out myself >so I gave up on it. Instead I tried dssi-vst system and it worked >like a charm. I use the latest wine (20050111) and havent had >any probz so far! Thats what I recommend since jack-fst doesnt >seem stable enough yet! http://dssi.sf.net > >regards >/alx > > > i have no problems running jack_fst either on its own, or inside of muse - it's only when trying to run muse with vst-support (where, i guess, it loads jack-fst in the background or something) that it segfaults. dssi-vst is really good, although i've had just as much success with jack_fst ... it would just be a really good thing to have vst's saved and loaded with individual song projects without having to load them all by hand ... shayne |
From: Robert J. <rj...@sp...> - 2005-01-23 21:24:48
|
torsdagen den 20 januari 2005 13.53 skrev al...@pa...: > > well, i'm not much of a guru, but i've tried using wine20040505 wine > > 20041201 and the latest 2005 one - each time recompiling jack_fst - and > > none of these work (no matter if i launch from VST folder). the same > > segmentation fault. > > Seems that fst has serious probz lately! Read somewhere that > 20040505 release would be the best to use for it but fst had > probz with glibc in some manor. I couldnt sort it out myself > so I gave up on it. Do you know how these problems manifested themselves ? /Robert -- http://spamatica.se/music/ |
From: Robert J. <rj...@sp...> - 2005-01-23 21:32:14
|
Hi, torsdagen den 20 januari 2005 03.04 skrev Shayne O'Connor: > Robert Jonsson wrote: > >tisdagen den 11 januari 2005 01.31 skrev Shayne O'Connor: > >>one question though - if vst support is enabled and working, does that > >>mean vst plugins are saved and loaded with the project? > > > >I'm sorry if I answered this already. But, yes, all settings are then > > stored in the songfile. > > that sounds great ... > > >And, ofcourse the same as to Neil goes to you, no clues from my part yet, > > but if you find something out, please let us know. > > well, i'm not much of a guru, but i've tried using wine20040505 wine > 20041201 and the latest 2005 one - each time recompiling jack_fst - and > none of these work (no matter if i launch from VST folder). the same > segmentation fault. Mmmh, looks like the problem I'm seeing. If you could try one of these startups and get a backtrace it would be great. 1. run: "ulimit -c unlimited", in the terminal you launch muse. 2. run muse so that it crashes. a core-file will be produced. 3. run 'gdb muse <the name of the core file> 4. inside gdb run the command 'backtrace' If it prints anything of use please send it here. For me it prints almost nothing, which indicates that something has written garbage over the stack, not so good... This works best if MusE is compiled with debug but it can give some hints still. > > not sure if this could be a clue, but when i was originally trying to > get jack_fst up and running (for stand-alone use), this is the same > message i would get - it was very frustrating. but i found that checking > the "no memory lock" box in qjackctl allowed me to use jack_fst. i don't > check this box anymore, so obviously that problem was addressed, but i > can't remember if it was an update of wine or jack or kernel which fixed > the problem ... but anyway, maybe it's the same sort of thing happening > here in a m-lock context Possibly, though I have a feeling there are nastier fish at work here. > > (as you may have guessed, my technical linux knowledge is a bit ... > whack ... i have no real idea what memory lock does, all i know is that > previously that was what was causing similar jack_fst errors for me). > > just to help me better get my head around what's happening when muse is > started with VST support - what is muse actually doing when it calls > jack_fst? i don't understand how jack_fst can be "started" without > calling a particular VST effect or instrument ... (i can't remember at > the moment if a VST_PATH has to be exported before starting with VST > support ... if so, is jack_fst trying to load *all* the plugins in VST > directory into memory?). If you don't specify a VST_PATH muse will assume it is /usr/lib/vst or something like that, so you always have VST_PATH, though, if the synths are not in this path nothing will show up. For me MusE crashes even if there are no synths. To give a brief overview of how this works. When MusE starts fst is loaded as a library (libfst.so or something like that). After a while MusE calls a fst-function 'initVST()' which probably sets up the VST environment and possibly scans for synths (not sure). The synths are not loaded until later. What happens in my case is that the 'initVST()' works just fine but sometime after that 'jack_activate(...)' is being called. At this moment something nasty has happened that causes this to fail horribly and MusE dies and I'm fairly sure the problem is not with jack. That is all I know at the moment. I should add that Werner has added initial support for DSSI in the coming 0.8 so there is an alternate route to achieve this, though VST's currently don't work there either. And 0.8 is sometime into the future before it is finished. /Robert > > anyway, hope these haphazard thoughts may provide food for more able > thoughts :) > > shayne > > > ------------------------------------------------------- > This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting > Tool for open source databases. Create drag-&-drop reports. Save time > by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. > Download a FREE copy at http://www.intelliview.com/go/osdn_nl > _______________________________________________ > Lmuse-user mailing list > Lmu...@li... > https://lists.sourceforge.net/lists/listinfo/lmuse-user -- http://spamatica.se/music/ |
From: Neil K. <nkl...@sb...> - 2005-01-24 08:11:49
|
Robert Jonsson wrote: > 1. run: "ulimit -c unlimited", in the terminal you launch muse. > 2. run muse so that it crashes. a core-file will be produced. > 3. run 'gdb muse <the name of the core file> > 4. inside gdb run the command 'backtrace' After muse segfaults on startup, all I get from gdb is: (gdb) backtrace #0 0x410047d3 in jack_activate () from /usr/lib/libjack.so.0 Cannot access memory at address 0xbff0a154 --Neil |