Menu
▾
▴
#104 tempo from segment to ask how many bars long is segment
I think it likely that I will record four bars at a time. The feature that
sets tempo against an audio segment has a lot of potential to be
useful, but in its present state I have to try to cut my segment right
on a bar line, or else use the whole thing and then multiply the
proffered tempo to scale it to what it's really supposed to be.
I'm thinking a "how many bars is this segment supposed to be?"
dialog and let Rosegarden do the math for me.
Probably a 15 minute knock-out to throw in, and I plan to do it
shortly if nobody screams.
Logged In: YES
user_id=13489
Good idea.
I've also wanted to be able to specify that the audio fragment
is only part of a bar (one beat, or half a bar, or whatever) --
but that's trickier to do tidily in a dialog.
Logged In: YES
user_id=663564
Well, I've done it in five minutes, and it works, but...
I got here so fast using KInputDialog, which is a KDE 3.2 thing anyway,
and I don't guess I should actually be using it without at least ifdefing it.
(We're still supposed to build on 3.1, right?)
Plus it looks a tad crappy. I'm thinking it might be worth the trouble to do
up a proper dialog, and have something like
The selected segment contains:
[spinbox] [combobox beats/measures]
Then shuffle the math around suitably. All the elements are there, and the
logic isn't too complicated.
I think it's probably worth it, even though it's a lot harder.
Agree?
I'll hold off on what I've got for now.
Logged In: YES
user_id=663564
I had to use some hackery to get around some problem I just could not
see with the original implementation of the dialog, but the underlying
functionality seems to behave in all situations.
This seems like a reasonably tidy way to handle this from the interface
side, and it's useful.
(Too bad it was a far cry from a 15-minute knock-out to throw in. See the
code for details about the hackery. Corrections invited.)