Hello Julie
On Tue, May 11, 2010 at 11:29 PM, Julie S wrote:
> Hello Lars,
>
> Glad to hear step recording is working for you.
>
- well, now I started to actually USE the step recording feature, and
I found a bug :)
It must have appeared at some point since RG 10.02. When I step record
in that
Hello Julie
It works! Thanks a lot for doing this. Now matrix step recording is
actually usefull :)
However, the 11904 revision, as well as the currently newest: 11929,
seems to suffer from very poor performance? It maxes out one of my
CPU's to 100% when playing back, and the blue marker stutters
Hello Lars,
Concerning:
> It must have appeared at some point since RG 10.02. When I
> step record
> in that version I can get multiple notes at the same time
> instant.
> Only when all keys are lifted does the marker move
> forward.
I created this bug about 11 days ago, when I fixed a different
Hello All,
Oh, that last message went to the dev list...
Glad I didn't say anything I'd regret.
Anyhow, Just to confirm, I'm having CPU usage issues, Lars, is and I thought I
heard another user complain.
Any thoughts, about what is going on?
Sincerely,
Julie S.
Hello Lars,
Glad to hear step recording is working for you.
I;m suffering from high CPU usage as well. I've seen other reports as well.
I'll post to the dev. board and see if anybody can help.
Sincerely,
Julie S.
--
Hello Lars,
I just added step record velocity capture to notation view and matrix view.
commit revision 11904.
It is not everything we talked about, concerning consistenct across views, drop
down box, etc. That will involve coding in a branch for a bit.
But notation view and matrix view do in
On Saturday 01 May 2010, Julie S wrote:
> I'm having trouble justifying disabling the box.
No longer under consideration.
> I think users do expect to preselect the velocity, unfortunately that only
> works creating notes using the draw tool. Step record notes are set with
> a velocity of 100
Hello Michael,
> Isn't step record pretty much local to the specific view
> anyway?
I've looked at the code and tried this out a bit.
Which ever step record button gets pressed (assuming multiple editors open),
its window receives the events.
The code handles this switching very elegantly via
On Saturday 01 May 2010, Julie S wrote:
> I also noticed that the step record icon state was not propagated across to
> the other views. I have not untangled the complexities involved in our
> current design. This will require further investigation before any final
> decisions concerning the
Hello Michael,
Concerning my last message:
> Since you use it, you may be more familiar with how this
> works. When I get a bit of time, I'll have to
> experiment with it and see how it reacts to different data
> sets.
>
> If using humanize is a typical work flow step for users
> than we want to
Hello Michael,
Concerning:
> I'm just not liking "use MIDI note velocity, if available"
> as a velocity combo
> box entry. It's long and hard to translate
> succinctly, and it's potentially
> confusing.
I hadn't pinned it down exactly. You are correct theat there is potential for
confusion.
On Friday 30 April 2010, Julie S wrote:
> Future State of MIDI recording:
> ---
> * The Matrix, Percussion and Notation views will have a Velocity combo box.
That would be consistent, but the absence of a velocity combo in notation has
never bothered me. (When I'm ha
Hello All,
On the RG users list Lars and I had several exchanges concerning step
recording. I've cc'd him so he can participate further. The dev list is the
more appropriate forum for this discussion.
I would like to propose some changes to our current handling of velocity during
step recordi
13 matches
Mail list logo
