From: linux_chaos <lin...@ya...> - 2004-01-22 09:12:13
|
hello, i really have a big problem: i am using redhat9 with alsa, jack and muse from planet.ccrma@stanford (via apt-get) and everything worked fine. i think problem started the evening BEFORE i updated muse to 0.6.3, but i am not sure, it also could have been after... when i try to save, it often happens, that there comes a "speicherzugriffsfehler" (what means as far as i know: "segmentation fault") and muse breaks down... it does not happen with every file and there are files, which work ok, but after a while it comes again, even with the files that worked before. i did not find any rule, at what times it happens and when not. because i always wanted to, i buld up a new system now (on my second hd - with the same stuff) and there i have the same problem. so i think it could be: a) a problem of some of my *.med-files ( in this case i could mail a broken file as example) b) or a problem with muse 0.6.3. (in case i updated BEFORE the problem started) i hope i gave you enough information - otherwise tell me what you need.. i really don t know. waht to do... thanks for reading and perhaps some help greetings linuxchaos -- _________________________________________________________________ http://www.audio4linux.de - musikmachen mit offenen quellen ! |
From: Robert J. <rob...@da...> - 2004-01-22 09:53:45
|
On Thursday 22 January 2004 10.20, linux_chaos wrote: > hello, > > i really have a big problem: > i am using redhat9 with alsa, jack and muse from planet.ccrma@stanford > (via apt-get) and everything worked fine. > i think problem started the evening BEFORE i updated muse to 0.6.3, but > i am not sure, it also could have been after... > when i try to save, it often happens, that there comes a > "speicherzugriffsfehler" (what means as far as i know: "segmentation > fault") and muse breaks down... > it does not happen with every file and there are files, which work ok, > but after a while it comes again, even with the files that worked > before. i did not find any rule, at what times it happens and when not. > because i always wanted to, i buld up a new system now (on my second hd > - with the same stuff) and there i have the same problem. so i think it > could be: > a) a problem of some of my *.med-files ( in this case i could mail a > broken file as example) > b) or a problem with muse 0.6.3. (in case i updated BEFORE the problem > started) > > i hope i gave you enough information - otherwise tell me what you need.. > i really don t know. waht to do... > > thanks for reading and perhaps some help > > greetings > linuxchaos Hi linuxchaos, Standard answer: If you have a .MusE file do try to remove it, it could very well be the problem. If that doesn't work you could try mailing me one of the files if the are not too big (e.g. require external audio files and what not). /Robert |
From: linux_chaos <lin...@ya...> - 2004-01-22 12:00:04
|
Am Don, 2004-01-22 um 10.51 schrieb Robert Jonsson: > On Thursday 22 January 2004 10.20, linux_chaos wrote: > > hello, > > > > i really have a big problem: > > i am using redhat9 with alsa, jack and muse from planet.ccrma@stanford > > (via apt-get) and everything worked fine. > > i think problem started the evening BEFORE i updated muse to 0.6.3, but > > i am not sure, it also could have been after... > > when i try to save, it often happens, that there comes a > > "speicherzugriffsfehler" (what means as far as i know: "segmentation > > fault") and muse breaks down... > > it does not happen with every file and there are files, which work ok, > > but after a while it comes again, even with the files that worked > > before. i did not find any rule, at what times it happens and when not. > > because i always wanted to, i buld up a new system now (on my second hd > > - with the same stuff) and there i have the same problem. so i think it > > could be: > > a) a problem of some of my *.med-files ( in this case i could mail a > > broken file as example) > > b) or a problem with muse 0.6.3. (in case i updated BEFORE the problem > > started) > > > > i hope i gave you enough information - otherwise tell me what you need.. > > i really don t know. waht to do... > > > > thanks for reading and perhaps some help > > > > greetings > > linuxchaos > > Hi linuxchaos, > > Standard answer: If you have a .MusE file do try to remove it, it could very > well be the problem. good idea, but i already tried that - it doesn t help > > If that doesn't work you could try mailing me one of the files if the are not > too big (e.g. require external audio files and what not). > you mean a file without audio (or just a file (that coult use audio, but without the wave-files)? i will have to look for one, cause almost all my files use audio... thanks for helping and greetings linuxchaos |
From: Crispin <cc...@oh...> - 2004-01-23 11:04:10
|
> i really have a big problem: Me too. Hello to this list - those of you who read planetccrma have probably seen me mention this already! Apart from this issue I'd like to say I really appreciate Muse and am finding it a fantastic cubase-replacement... I've been having similar segfault on load/save problems with muse 0.6.1. I haven't been able to update to 6.2 yet[1] but maybe this problem still exists in that. The bug can be reproduced by: 1. start Jack 2. start ladccad 3. modprobe snd-serialmidi (as root) 4. run muse 5. create a midi track 6. set the port to "5 - Serial Midi #0" (or whichever numbering it gets in your setup) 7. save Crashes every time, for me. Can anyone help with this? thanks [1] I don't have an internet connection at home so can't use the online repositories with apt-get. I downloaded the rpm for muse 6.2 (on a cd), but it requires a later version of ladccad (according to rpm -ihv). So I upgraded ladccad, but this breaks fluidsynth, of which there isn't a later version. Presumably this conflict would be resolved by apt but how can one install an rpm with that? any help appreciated! -- Crispin |
From: Robert J. <rob...@da...> - 2004-01-23 11:39:05
|
Hi Chrispin, On Friday 23 January 2004 12.01, Crispin wrote: > > i really have a big problem: > > Me too. > > Hello to this list - those of you who read planetccrma have probably > seen me mention this already! Apart from this issue I'd like to say I > really appreciate Muse and am finding it a fantastic > cubase-replacement... So do I :) I'm doing some testing of the upcoming 0.7 now and then... it will be a great release once it's finised, might be a while though ;). > > I've been having similar segfault on load/save problems with muse 0.6.1. > I haven't been able to update to 6.2 yet[1] but maybe this problem still > exists in that. Thought I'd mention that current is 0.6.3, I guess ccrma hasn't added it yet. > > The bug can be reproduced by: > 1. start Jack > 2. start ladccad > 3. modprobe snd-serialmidi (as root) > 4. run muse > 5. create a midi track > 6. set the port to "5 - Serial Midi #0" (or whichever numbering it gets > in your setup) > 7. save > > Crashes every time, for me. Okay, I will try to test this in the near future. I don't think I've seen this earlier... For the record: Neither jack or ladcca are strictly necessary to run the setup you suggest. If one of them is the perpetrator you could try to omitt one of them and see if the problem persists. (You don't have to uninstall them, just don't start them) As for serial-midi. What type of midi equipment do you have that requires this module? I don't have any such, I guess the problem could be in this area also... > > Can anyone help with this? > > thanks > > [1] I don't have an internet connection at home so can't use the online > repositories with apt-get. I downloaded the rpm for muse 6.2 (on a cd), > but it requires a later version of ladccad (according to rpm -ihv). So > I upgraded ladccad, but this breaks fluidsynth, of which there isn't a > later version. Presumably this conflict would be resolved by apt but > how can one install an rpm with that? any help appreciated! Sorry, I don't use redhat so I have no idea. /Robert |
From: Crispin <cc...@oh...> - 2004-01-23 11:47:32
|
> For the record: > Neither jack or ladcca are strictly necessary to run the > setup you suggest. Um, good point. I think serialmidi is the problem though. > As for serial-midi. What type of midi equipment do you have > that requires this > module? A Yamaha MU50. But it's switched off and disconnected throughout the above procedure (and yes it still crashes with the MU50 switched on and connected :)) It doesn't strictly require serialmidi, but it does have a to-host connector, which gives me a second midi port. This means I can wire up my two keyboards to one port each without a midi merge unit for input - MU50 and digipiano on the serial port; Korg on the joystick port. Nice management of inputs and lower latency - I don't think you can even do that on windows any more! :) -- Crispin |
From: Emiliano G. <emi...@po...> - 2004-01-23 14:19:49
|
venerd=EC, 23 gennaio 2004 alle 12:37:21, Robert Jonsson ha scritto: > So do I :) I'm doing some testing of the upcoming 0.7 now and then... i= t > will be a great release once it's finised, might be a while though ;). Cool :) Can you give some highlights on the new features? (apart from jack-transport implementation :P=B0=B0=B0) > Thought I'd mention that current is 0.6.3, I guess ccrma hasn't added i= t > yet. No, 0.6.3 is already on the repository: $ muse -version $ muse: Linux Music Editor; Version 0.6.3 Bye --=20 Emiliano Grilli Linux user #209089=20 http://www.emillo.net |
From: Robert J. <rob...@da...> - 2004-01-23 14:58:25
|
Hi Emiliano, On Friday 23 January 2004 15.19, Emiliano Grilli wrote: > venerd=EC, 23 gennaio 2004 alle 12:37:21, Robert Jonsson ha scritto: > > So do I :) I'm doing some testing of the upcoming 0.7 now and then... it > > will be a great release once it's finised, might be a while though ;). > > Cool :) > Can you give some highlights on the new features? (apart from > jack-transport implementation :P=B0=B0=B0) Sure! Werner has been busy, there are lots of new stuff (some parts are=20 Mathias also). Disclaimer: This is taken from memory, and I didn't implement any of it, I= =20 might have misunderstood the reasons for the changes. =46irst, the bad news: =2D MusE can no longer be run without jack, I think this was made to simpli= fy=20 the architecture. For me this isn't a problem, but it might be to some peop= le=20 who haven't gotten jack running very well yet. New features: =2D New softsynth architecture (this will probably only show on the inside,= but=20 it means that softsynths should perform better when under high load) =2D Keyboard shortcuts editor: most (all?) shortcuts can now be changed in= =20 runtime. =2D More color configurability =2D Redesigned audio-mixer with much improved routing capabilities towards = jack. =2D Track types extended, input, output, aux, audiotrack, miditrack, drumtr= ack =2D The beginings of automation, only volume at the moment. =2D Improved RT performance, xruns should be a thing of the past. :) =2D And, of course jack-transport. And... that's all I can remember right now, most things are work in progres= s=20 and not usable in a production environment. /Robert > > > Thought I'd mention that current is 0.6.3, I guess ccrma hasn't added it > > yet. > > No, 0.6.3 is already on the repository: > $ muse -version > $ muse: Linux Music Editor; Version 0.6.3 > > Bye |
From: Robert J. <rob...@da...> - 2004-01-23 11:31:06
|
On Thursday 22 January 2004 13.08, linux_chaos wrote: > Am Don, 2004-01-22 um 10.51 schrieb Robert Jonsson: > > Standard answer: If you have a .MusE file do try to remove it, it could > > very well be the problem. > > good idea, but i already tried that - it doesn t help > > > If that doesn't work you could try mailing me one of the files if the are > > not too big (e.g. require external audio files and what not). > > you mean a file without audio (or just a file (that coult use audio, but > without the wave-files)? i will have to look for one, cause almost all > my files use audio... I guess it's okay if there are audio-files as long as the package isn't too big :). /R |
From: linux_chaos <lin...@ya...> - 2004-01-23 13:58:53
|
Am Fre, 2004-01-23 um 12.29 schrieb Robert Jonsson: > On Thursday 22 January 2004 13.08, linux_chaos wrote: > > Am Don, 2004-01-22 um 10.51 schrieb Robert Jonsson: > > > > Standard answer: If you have a .MusE file do try to remove it, it could > > > very well be the problem. > > > > good idea, but i already tried that - it doesn t help > > > > > If that doesn't work you could try mailing me one of the files if the are > > > not too big (e.g. require external audio files and what not). > > > > you mean a file without audio (or just a file (that coult use audio, but > > without the wave-files)? i will have to look for one, cause almost all > > my files use audio... > > I guess it's okay if there are audio-files as long as the package isn't too > big :). the files i am working with at the moment are all bigger than 100mb... but when i was looking for a file without audio i found out, that ALL the files i have problems with are with audio. so the problem seems to be there... i thougt i found a broken file without audio, but the i recognized, that this file used to have audio, but not anymore.... according to that now my question for better understanding: when i record audio, i record a lot of tracks and afterward, i delete the bad ones of them (the tracks in muse). if i want to have more space on my hd, can i just go to the directory and delete the not used rec*.wav or does that make problems ? and second question according to the above: what happens, if i delete a rec*.wav, that is still "in use in muse" (not deleted in the track-manager in muse). does muse still start and just "mute" this part/track ? perhaps thats part of my problem, so i hope for better understanding. thanks and greetings linuxchaos > > /R |
From: Robert J. <rob...@da...> - 2004-01-29 09:43:00
|
> > I guess it's okay if there are audio-files as long as the package isn't > > too big :). > > the files i am working with at the moment are all bigger than 100mb... That's a bit big to send ;) Cool that it works for you with projects of that size though :) (when it doesn't crash...that is...;) > but when i was looking for a file without audio i found out, that ALL the > files i have problems with are with audio. so the problem seems to be > there... > i thougt i found a broken file without audio, but the i recognized, that > this file used to have audio, but not anymore.... > > according to that now my question for better understanding: > when i record audio, i record a lot of tracks and afterward, i delete > the bad ones of them (the tracks in muse). if i want to have more space > on my hd, can i just go to the directory and delete the not used > rec*.wav or does that make problems ? This could very well be part of the problem. Current muse has some problems with wave files. It doesn't forget old files, even though they may be unused. This sometimes means that the song-files contain lots of redundant data which nobody is using. Since the song files are textfiles it is possible to edit them in an text-editor and remove this information. I have tried that successfully in the past. (Remember to always keep a backup copy of the song-file though!) > > and second question according to the above: what happens, if i delete a > rec*.wav, that is still "in use in muse" (not deleted in the > track-manager in muse). does muse still start and just "mute" this > part/track ? If muse is still running it's probably a bad idea to remove the file. Better wav-file-handling should be added inside muse. One of these days... /Robert > perhaps thats part of my problem, so i hope for better understanding. > > thanks and greetings > > linuxchaos > > > /R |
From: linux_chaos <lin...@ya...> - 2004-01-26 20:27:54
|
Am Fre, 2004-01-23 um 15.40 schrieb Robert Jonsson: > > > I guess it's okay if there are audio-files as long as the package isn't > > > too big :). > > > > the files i am working with at the moment are all bigger than 100mb... > That's a bit big to send ;) > > Cool that it works for you with projects of that size though :) (when it > doesn't crash...that is...;) yes, it works very good (exept saving ;-) - i am really happy with muse! (i mean, there are a lot of things i am waiting for, but its good enough for me for the moment (and cause its very fast getting better, i think, i will keep on working with it)) > > > but when i was looking for a file without audio i found out, that ALL the > > files i have problems with are with audio. so the problem seems to be > > there... > > i thougt i found a broken file without audio, but the i recognized, that > > this file used to have audio, but not anymore.... > > > > according to that now my question for better understanding: > > when i record audio, i record a lot of tracks and afterward, i delete > > the bad ones of them (the tracks in muse). if i want to have more space > > on my hd, can i just go to the directory and delete the not used > > rec*.wav or does that make problems ? > > This could very well be part of the problem. Current muse has some problems > with wave files. It doesn't forget old files, even though they may be unused. > This sometimes means that the song-files contain lots of redundant data which > nobody is using. ok, then we got the problem ! duiring one of my last recording-sessions (should have been the last) my hd was full. so it could have happened, that i recorded a new audio, but there was not enough space to save the rec*.wav-file and according to that muse has a problem... > Since the song files are textfiles it is possible to edit them in an > text-editor and remove this information. I have tried that successfully in > the past. (Remember to always keep a backup copy of the song-file though!) that sounds good! i will try with a copy (hope i find out how)... > > > > > and second question according to the above: what happens, if i delete a > > rec*.wav, that is still "in use in muse" (not deleted in the > > track-manager in muse). does muse still start and just "mute" this > > part/track ? > > If muse is still running it's probably a bad idea to remove the file. > > Better wav-file-handling should be added inside muse. One of these days... yes, that would be very important! ok, thats it - robert thanks for the help and greetings to everyone using muse linuxchaos > > /Robert > > > perhaps thats part of my problem, so i hope for better understanding. > > > > thanks and greetings > > > > linuxchaos > > > > > /R -- _____________________________ http://www.audio4linux.de |