Re: [Rosegarden-user] Re: Metronome wont go away

[Chris C. <ca...@al...>]

On Friday 14 Oct 2005 16:57, Silvan wrote:
> This case might be a rosegardenrc issue after all.  Some kind of settings
> amnesia.  I'm not sure where the state of the transport metronome button is
> stored off hand.

When you load a file, the metronome button state is set in 
RosegardenGUIApp::initView based on the play-metronome flag in the 
composition.  It has nothing to do with the KDE settings that we've suffered 
so much from.

The state of the play metronome is a single boolean value in the Composition 
object, stored in the .rg file.

The communication with the sequencer to tell it to play the metronome is done 
by the MetronomeMmapper object in gui/mmapper.cpp which writes a set of 
events to an mmapped file (normally /tmp/kde-$USER/rosegarden_metronome -- 
perhaps check for weird permissions on an old copy of this or something?) 
based on the state of the metronome when playback starts.  That code is more 
complicated, so maybe that's what's going wrong.  You should be able to find 
out -- change the time signature to 3/4 or something and if the old file is 
still in use, you'll get the previous (presumably) 4/4 beat pattern still.

The mmapped file is read in sequencer/mmappedsegment.cpp; this is also complex 
but it's the same code as used for all events, not just metronome ones, so 
it's less likely to be the source of the error.

> Chris will have to rescue you when he finds time.

Well, those are the few thoughts that came to mind first.  Time is a bit short 
at the moment -- I'm actually going to be away for most of the weekend, and 
I'm aware there are various threads on rg-devel that I probably won't get a 
chance to follow up on before next week now.


Chris