Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
when recording midi using latest rosegarden, i run into some issues:
1) what's the best way to do multiple takes? If I do multiple takes on
1 track, I have to mute the track, otherwise i hear the (older) takes
all at once. But if i mute the track I don't hear the current take.
Same thing happens when I want to listen to all takes afterwards: there
seems to be no way to listen to only 1 take on a track?
My current solution is to make a new track for each take, but it gets
cumbersome to redo the needed settings for each new track.
2) I had to set the track's playback device to 'synth plugin' (and then
have no synth selected) for recording, instead of the usual "general
midi device". I don't exactly remember why (i scrabbled this remark on
a piece of paper weeks ago). probably related to monitoring or getting
the input midi signal. if it does not ring a bell, that's ok.
From: D. Michael McIntyre <michael.mcintyre@ro...> - 2010-06-20 22:46:23
On Sunday, June 20, 2010, Dieter Plaetinck wrote:
> Same thing happens when I want to listen to all takes afterwards: there
> seems to be no way to listen to only 1 take on a track?
This is a good argument for per-segment mute. This is an idea that's been
tossed around for years, but it remains elusive. I don't remember the whole
checkered history, and can't explain exactly why we don't have this feature
yet. All I can say is my quick impression of the situation is that it must be
a real pain in the ass to get right, or someone would have long before now,
due to the level of interest that has been expressed over the years.
> My current solution is to make a new track for each take, but it gets
> cumbersome to redo the needed settings for each new track.
My usual workaround to this is to have a muted storage track, and drag the
candidate takes there. Then I plunk the one(s) I want to evaluate on the
track that's configured correctly for playback. A bit tedious now that I
think about it, but it gets the job done well enough I've never considered
this a crippling limitation.
> the input midi signal. if it does not ring a bell, that's ok.
No bell, sorry.
D. Michael McIntyre