Hi Robert, hi Andrew,
Yes, the MusE installation I used to reproduce this behaviour is
a release build.
Today I did the following:
1. I recompiled and re-installed the latest clone as a release
build. Before that I deleted the target subdirectory path
muse/muse2 fort the git command, and applied the command "git
clone
https://github.com/muse- sequencer/muse.git". Then I applied
"cmake -i", "make" and "sudo make install". Before running "sudo
make install" I removed the content of the destination directory
of the command "sudo make install". (The other method, suggested
by you, via "git pull" and "make clean" did not work because
"make" resulted in an "Error 2": the file all.h was missing)
2. I ensured that there is no MusE folder in ~/.config
3. I started the build release of MusE.
4. I loaded the file test_song.med into MusE.
5. I again noticed that the file test_song.med does not have a
Out 1 track in the GUI of MusE. I reported this behaviour
before. This issue should be fixed. It is not possible to
properly creatre music with MusE without an Out 1 track.
6. I played this file, loop mode activated.
=> MusE does not crash anymore when the play cursor reaches the
end of the loop region. I let this file play several times
through the loop region: MusE does not crash. I played this song
again: MusE does not crash
=> Issue "Another MusE crash: MusE 2.2.1, loop mode, metronome
button activated" is fixed.
=> I guess that by the "git pull" command, then "make" and "sudo
make install" some files of an older build in my build directory
where copied to the destination directory of the "sudo make
install" command, so the directory where MusE was installed
contained both MusE programme files from an older and the latest
build, so it was messed up. So it is better not to use "git
pull", but instead start from a clean and empty directory where
one applies the command "git clone
https://github.com/muse-sequencer/muse.git";, then cmake -i, then
make, then make install.
do you use a standard distribution?
My distribution is Ubuntu Studio. This is the release information
about my Ubuntu Studio installation:
---
jrad@music:/etc$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.3 LTS
Release: 14.04
Codename: trusty
jrad@music:/etc$
----
what settings do you start jack with?
AS the issue is now fixed on my system, we do not need to look in
the Jack settings of my system anymore.
There is no need anymore for me to build a debug version of the
latest MusE clone or start MusE without plugins, as the issue is
fixed on my system.
Regards,
Jens
Am Donnerstag, 24. September 2015 schrieb Robert Jonsson:
Hi Jens,
2015-09-24 18:11 GMT+02:00 Jens Radloff <[email protected]>:
Hi Andrew, hi Robert,
To ensure that this behaviour is not caused by an "old" MusE
folder in ~/.config I removed the directory ~/.config/MusE and
started MusE again, so a new, fresh MusE folder in ~/.config
got created.
Background information: This "old" MusE folder in ~/.config is
from my installation of MusE 2.2.1, the last official release.
I think Andrew told me that, if I use a current clone version
of MusE, then I need to remove the old MusE folder in
~/.config to get a new version of this folder created that is
set up for the use of a current clone version of MusE.
Let me add at this point that now, with a new, fresh MusE
folder in ~/.config, I do not have a "Out 1" track in any MusE
song anymore which I created so far. I think I reported this
bug some months ago.
So, as I wrote, I ensured that my clone installation of MusE is
based on a fresh MusE folder in ~/.config.
But the behaviour can be still reproduced: MusE crashes when
the metronome button is activated at the moment when the play
cursor reaches the end of the loop region in this song
test_song.med .
So this behaviour does not seem to be caused by the content of
the MusE folder in ~/.config.
Ok, good so we can rule that out.
This is the output of gdb (I could only copy what is shown in
the
console):
I only took a brief look but it seems the amount of information
in the back trace is not much.
Is the muse binary still built for release? Building it for
debug may give more information.
Some additional questions, sorry if you already answered
before.. do you use a standard distribution? maybe we can
reproduce your problem. what settings do you start jack with?
The start of the printout below is what MusE outputs during
running with -D, right? And you are starting MusE from within
gdb?
Unless you already did so I would suggest that you recompile
MusE similar to the below:
cmake .. -DCMAKE_BUILD_TYPE=debug
make clean
make
make install
Another thing you could try is to start MusE without plugins.
and use MusEs own fluidsynth (under MESS) as audio output.
muse2 -pNI2
We had for instance an issue some years ago that some plugins
caused corruption in MusE memory space due to duplicated symbol
names.
/Robert
-----------------------------------------------------------------
-- -- --------- _______________________________________________
Lmuse-developer mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/lmuse-developer
