Digital Performer and, I believe, Sonar have event-chasing options
too, that can be applied to any events, including notes, so when you
start in the middle of a note you hear the note (default is off
though). It's more useful than it sounds, when you use syncopation.=20
There's rarely a barline in my stuff that doesn't have at least one
note held over it. To play back a certain section and have part of
the harmony not there can be distracting. I wouldn't know how to
suggest this for csd though.
The event chasing feature is really important for patch changes, like
if you switch to pizzicato, and start playback a measure after that.=20
Probably not an issue for Blue. But tempo events could be sticky.
It would definitely be more accurate to have notes at the end
truncated than removed.
In my experience with MIDI, if you have some section of audio selected
when you go to export, only that section is included; but if nothing
is selected, all audio is exported. Most rewind buttons effect loops
by rewinding to the loop start, and if the pointer is at or before
loop start, to the beginning; rewind from the beginning goes back to
loop start. Also, if you start playback ahead of loop start, it will
play from wherever the cursor was, and start looping when it gets
A delay while rendering csd shouldn't be a problem. The ability to
alter things as it loops will definitely make compositions better; you
can slide a note half a beat later and make everything 10x as
My own composing process has always involved listening to passages
over and over and over. For Blue to do this would be awesome.
Speaking of tempo events, I wanted to ask, is there any way to
graphically adjust tempo? Maybe that's getting picky, but it is one
of those things that can be far more effective if you have more
intuitive control over it. If shifting tempo just a little bit is a
matter of typing in a bunch more numbers, most of us will say "it's
good enough how it is", but if you can try different tempos by
shifting a dot, you get finer with it. Maybe there's already
something in Blue that I'm missing, but since tempo comes from the
score I don't see how you could control it without changing the score.
Thanks for all the improvements. I'm going to be using Blue quite a bit.
On 5/16/05, Steven Yi <stevenyi@...> wrote:
> Hi All,
> I'm pretty excited over a new feature I had time to put in today, a
> new loop render mode as well as render stop time. My changeLog note I
> think mostly explains it:
> [new] - Loop Render and Render Stop Time - using right mouse button
> of left in setting the time on a root polyobject will set a
> line for when to stop rendering (green line is render start
> setting to loop mode before rendering will re-render the
> immediately after a render stops. This allows one to render =
> loop and while listening, make a small change, and hear the
> in the next loop (file is always recompiled to CSD between
> Now, while in loop mode, there is a bit of time between renders when
> blue goes to recompile a new temp CSD, but all in all, I think this
> will help make the composition experience a little more immediate.=20
> I've been wanting to put this in for a while but had never written
> down to do it, but now that it's in it's been really neat to have (one
> of those "of course that's a feature I'd like to have!" moments).
> Well, anyways, I thought I'd ask for some suggestions: in current
> release versions, and pretty much every version of blue to date,
> render start time would affect rendering of a CSD by taking every note
> that started before the render start time and removing it, then
> shifting over the score to start at time zero, giving the experience
> of starting rendering from the set time. WIth render end time now
> available, I am wondering is the expected behavior. The way it is now
> is if a note ends after the renderEndTime, it is not included in the
> exported CSD file. I think though that it might be more logical for
> notes that start after the renderStartTime but end after the
> renderEndTime should have their notes truncated in time to fit the
> renderEndTime. Does this sound more correct?
> Not having used a MIDI sequencer much in the past five years, I'm not
> sure what to expected. If I remember correctly from the last time I
> was over at my friend's studio running Logic Pro, for a user's set
> renderStartTime and renderEndTime, notes with startTimes >=3D
> renderStartTime and < renderEndTime were played, and if they were
> longer than the renderEndTime, they were truncated. In MIDI speak, I
> imagine the sequencer would do all note-on's and note-off's in between
> the user's renderStartTime and renderEndTIme, and when the
> renderEndTime was hit, an allNotesOff would be issued and then the
> loop restarted.
> I'm leaning in this direction, but if you have a better idea or even
> could confirm that this is more correct, please let me know!
> Also, when rendering a CSD to File (ctrl-g), blue currently asks where
> to start render from. I don't remember why I ever put that in, but I
> came across it today and thought I should just remove that and use
> whatever renderStartTime and renderStopTime is set. Any suggestions
> for or against or otherwise?
> Oh, and one last thing, I was thinking of having a rewind button next
> to the play button that would move the renderStart time to the
> beginning and clear the renderEndTime. Is that the behavior one would
> expect? (I guess the question I have is on the renderEndTIme clearing
> This SF.Net email is sponsored by Oracle Space Sweepstakes
> Want to be the first software developer in space?
> Enter now for the Oracle Space Sweepstakes!
> Bluemusic-users mailing list
"Some people got attitude,
Backed up with attitude."