Pedro Lopez-Cabanillas wrote:
>
> About the RFE 630000 addition, my proposal was to allow two different pitches
> for bar and beat sounds, allowing the use of the two GM2/GS metronome sounds
> (34=metronome bell and 33=metronome click) or XG ones (21, 22). RG metronome
> can produce sub-beat signals too, so all sounds (bar, beat and sub-beat)
> should be adjustable by pitch and velocity.
Yes, it would be good to have a choice of the two GM2/GS metronome sounds
and the two XG metronome sounds. Do you have or know of a good XG soundfont?
> About the GUI, my initial proposal was to add only another pitch chooser for
> bar signal, but then Chris argued that it seems a little arbitrary to have
> two separate pitch choosers but not three, and it would seem excessive to
> have three: that suggests there may be a better solution out there than
> simply having multiple pitch choosers.
I think the simplest and most ergonomic GUI for choosing any number of
pitches would be a mini 300x50 notation-canvas.
> It should have also something like the
> instrument parameter box, to allow choosing a channel, bank and program for
> the metronome sounds. With those many controls together, it can be a big and
> ugly dialog box.
That doesn't sound too bad.
> And what about a new toggle button, or two, to start playing and
> stop the metronome inside the dialog, to give auditive feedback to the user?
Yes, that would be very useful.
> Talking about the metronome, what about a new control to increase or decrease
> the tempo, inside the transport toolbars? The control should be operable as a
> live playing or recording live adjustment.
Very useful.
> Visual metronome: I guess that a external program, as an ALSA client with a
> writeable port should be a better and more flexible solution. The big time
> window could be also an external program, but an internal one has some sense,
> too.
What is a "visual metronome"?
William

Hi,
Last week we talked about some RFEs regarding the metronome, like:
o 630000 RFE- metronome tick routing; different pitches for bar and beat
sounds.
o 932842 "big time" and/or visual metronome
o 965162 Metronome to be audible while changing speed, pitch, instrument
About the RFE 630000 addition, my proposal was to allow two different pitches
for bar and beat sounds, allowing the use of the two GM2/GS metronome sounds
(34=metronome bell and 33=metronome click) or XG ones (21, 22). RG metronome
can produce sub-beat signals too, so all sounds (bar, beat and sub-beat)
should be adjustable by pitch and velocity.
About the GUI, my initial proposal was to add only another pitch chooser for
bar signal, but then Chris argued that it seems a little arbitrary to have
two separate pitch choosers but not three, and it would seem excessive to
have three: that suggests there may be a better solution out there than
simply having multiple pitch choosers. It should have also something like the
instrument parameter box, to allow choosing a channel, bank and program for
the metronome sounds. With those many controls together, it can be a big and
ugly dialog box. And what about a new toggle button, or two, to start playing
and stop the metronome inside the dialog, to give auditive feedback to the
user?
Talking about the metronome, what about a new control to increase or decrease
the tempo, inside the transport toolbars? The control should be operable as a
live playing or recording live adjustment.
Visual metronome: I guess that a external program, as an ALSA client with a
writeable port should be a better and more flexible solution. The big time
window could be also an external program, but an internal one has some sense,
too.
I would be very glad to listen your smart ideas.
Regards,
Pedro

Hi all,
I have updated the Spanish translation, and found some issues.
The audio mixer has fixed sized widgets. It is hard to translate the strings
while fitting them into the widgets. For instance, the string "<none>" fits
into the lower buttons, but "<nada>" is a bit wider, and overflows. Worse are
the overflows for "In #", translated into "Entrada #". The smaller font size
doesn't help, and it makes this window unpleasant for people short sighted
like me.
Some new features are also new challenges for me as a translator ;-). I have
translated "triggered segments" into "segmentos activados", and "to trigger"
into "activar" in this context; I prefer that word instead the usual
"gatillo", or "disparador" with more warlike connotations. The "faders" are
translated into "deslizadores", but "fade in" and "fade out" are left
untranslated, because the original English words are well known for Spanish
musicians, and the translations into Spanish (fade out => desvanecimiento
gradual; fade in => subida gradual de volumen) are too wider for the
parameter box.
Finally, "Quantize" is now "Cuantificar" instead of "Cuantizar", as was
announced some time ago.
Regards,
Pedro

On Sunday 18 Jul 2004 3:24 pm, William wrote:
> RG will build with liblo 0.6 but presumably there is such a thing
> as liblo >= 0.7 otherwise RG wouldn't check for it.
> Where can one get liblo >= 0.7 ?
You can't, yet -- it hasn't been released. The test is just there
because when it is released, we'll be using a new function in it that
isn't in 0.6. It's not an important function for us: it's a thread
terminate function that could be called at any point we decided we no
longer needed the plugin GUI manager, but in practice will at the
moment only ever be called when RG exits -- a point at which it has
no practical effect anyway. But just for completeness I put the
function call in anyway, and that means we need to test for the
library.
Summary: don't worry about it.
Chris