Re: [Lmuse-user] Re: regular crashing with eraser tool

[Mathias L. <ga...@sp...>]

fre 2005-06-17 klockan 11.13 skrev Jens Radloff:
> Jens Radloff wrote:
> 
> > I will soon compile MusE 0.7.2pre1 again, with --enable-debug, 
> > and will  check if the eraser tool crashes or not.
> 
> I have now re-compiled MusE 0.7.2pre with --enable-debug, but the 
> behaviour is still noticable (MusE crashes, when using the eraser 
> tool), but I think I know when MusE crashes: 
> 
> When you use the eraser tool while playing a song, MuSe crashes when you 
> try to erase a note while the cursor is at the same position as the 
> note that you want to erase. I have noticed this several times in the 
> piano roll editor. I did not check the drum roll editor.
> 

Ah, k - I played around with the thing and didn't manage to reproduce it
.There are mem-leaks, but they're linked to the undo functions and qt
events and it's not that easy to delete only the things that are unused.
This is much more specific - will give it a try. BTW, which Qt version
are you using?

> Some other remarks:
> 
> 1. When I try to log what MusE is doing, trying to pipe log information 
> into a file, and I load a song in MusE, then inside MusE an error 
> message is displayed: "Initialization created with different version of 
> FluidSynth Mess, will be ignorded". And I cannot hear anything, all 
> sound fonts linked to the fluid synth tracks are gone. This message is 
> displayed, no matter if I use the log options that MusE offers, or not. 
> The background for this message is obviously the fact, that when I 
> created that song, I had Fluidsynth version 1.0.5 running, and I 
> created some Fluidsynth instances inside MusE (according to what is 
> displayed inside MusE, the fluid synth version within MusE is a 
> different one than the version of Fluidsynth which I installed on my 
> system). Maybe the eraser tool causing MusE to crash and the different 
> versions of Fluidsynth (installed on my system and Fluidsynth used in 
> MusE) are connected to each other (?!).
> 

The message you get about initialization created with another fluidsynth
version has to do with the project file being created with an older
version of MusE. The initialization data changed dramatically between
0.6.3 and 0.7 (I think), and was not backwards compatible. THis means
that the softsynth state saved together with the project will simply be
ignored - no soundfonts are loaded etc... It doesn't have anything to do
with what version of fluidsynth you're using, and shouldn't have
anything to do with the eraser tool

> 2. Yesterday I replaced Jack 0.99.0 with a CVS version of Jack 
> (0.100.0). The eraser tool causes MusE to crash under both versions of 
> Jack.
> 

THanks, I doubt it has anything to do with jack.

> 3. Another possible reason for these crashes can be certain soundfonts, 
> but I did not test this yet.

I think it has to do with Qt event handling causing some kind of race
condition or other timing problem . I'll give it another try reproducing
it.

> 
> 
> Regards,
> 
> Jens
> 
> 	
> 
> 	
> 		
> ___________________________________________________________ 
> Gesendet von Yahoo! Mail - Jetzt mit 1GB Speicher kostenlos - Hier anmelden: http://mail.yahoo.de
> 
> 
> 
> -------------------------------------------------------
> SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
> from IBM. Find simple to follow Roadmaps, straightforward articles,
> informative Webcasts and more! Get everything you need to get up to
> speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
> _______________________________________________
> Lmuse-user mailing list
> Lmu...@li...
> https://lists.sourceforge.net/lists/listinfo/lmuse-user
> 
>