How about--Individual Velocity Curve for each key?

[tkmh]

First of all..
A quick thanks to Brad for re-starting Cantabile. yay!!

Also thanks for the upcoming 3.0 with colored racks.!

One quick request: For Piano and Electric Piano lovers>

How about taking the velocity curve midi-filter utility, and adding a key range qualifier for it so we can, if desired, have a separate V-Curve for each Of 88 (or 76, 61 ect.....) keys? Or a range of keys?

Now, I know that there is the "Pitched Velocity Ramp" utility in Cantabile filters, however, that is more of an offset of the general V-curve, (if I understand correctly), and not a separate V-curve for each key.
A per-note, separate, V-curve could greatly help match some of these VST pianos (Ivory,TruePianos ect...) with their 88 key controllers.. (regardless if the
problem note is in the VST piano itself, or the controller)

I don't know how hard that would be to program into Cantabile. But I don't think there are any other apps
out there that let you have a separate Curve for each note.
Certainly Forte, or any of the other hosts don't have that functionality.

Any love for this idea?

tkmh

[TiUser]

A long time ago I've suggested 2 velocity curves... one for the black keys and another for the white keys.

The reason is simpls, many cheap keyboards respond different on black and white keys and I think such a simple split in 2 key sets would be a real helpful feature.

Calibrating each key manually seens to me to be a "loony" feature - sorry for this term. Instead I would much appreciate an automatic analysis for each key and automatic correction. But I am of course aware that this isn't an easy thing to implement.

[tkmh]

Well, you could very well adjust the Black vs White keys with the range qualifier
I proposed in th OP.
Yeah, it would be quite a bit tedious setting it all up.
But it would at least be do-able for those who could
benefit from individually adjustable curves.

And, if it didn't apply for your setup, (or thought it was Loony )
you simply wouldn't use it!

As for the Auto-Adjust thing, I know that Ivory II uses it, but it
is just for the overall curve.
You are right, that would probably be too hard to implement! (Thus
my manual suggestion.)

tkmh

[TiUser]

Well, you can do a lot of things - technically - in Cantabile.

But probably you have noticed that one of the things I really appreciate is to see features that make Cantabile easier to use for everyone.

At the end of the day I understand technical concepts and can use them - but if it is too much fiddling around I finally practically don't do.

I understand and appreaciate clear technical concepts but I also believe they are worth nothing if they are too hard to use from a musicians/musical point of view.

There are reasons why HW mixers, effects and instruments look like they do. Software should have tools to create traditional structures most musicians are familar with without too much overhead. Operation should also offer to use it the "traditional" way.

The benefit of software however can be that if the technical concept behind the scenes is clear you can do much more with that when you like to dive into it. But I clearly think that should not be a need.

It's probably that a product decides whom it is targeted to. But if something has just features and too much complexity that will for sure limit it's potential users. I don't believe Cantabile is meant that way.

I am also aware that's a challenge to make something like midi processing a no brainer for people who don't really know in detail what midi is about. I myself prefer solutions where I don't have to think about 3 byte channel chunks too much...

I don't want to offend - especially not technical enthusiam. I really appreciate discussing anything. But I have also learned over time that things should be finally put back on a somehow more "realistic" level.

[tkmh]

I think my OP suggestion is,(or could be), in line with "Keeping it simple".

If you want to fix just a few notes, or a range of notes, no problem-
especially with the "Learn" function. If you want to do a lot of keys,
or all 88, well yes that is a bigger job---but do-able!

Upon thinking about it, I think a separate Black/White utility with separate v-curves for each, is a good "one-shot" simple fix idea for a common problem.
Although I probably wouldn't use it with the keyboards I now have.
The problems I see with my keyboards (my Fatar 2001 in particular) are more
key to key.

My suggestion of a range qualifier on the v-curve app would be as simple or
as complex as you need it to be. I guess that is all I'm trying to say.


thanks for listening!

tkmh

[TiUser]

Probably you misunderstood - technically your idea is fine.

Just when I look at what happened 'til now we have a lot of "technical" features in Cantabile. But I believe what is missing most is having gui, macros whatever to simpler manage more common issues (like the black/white key thing). I am pretty sure that Brad will prefer implementing things technically the way you suggest but my fear is that he probably will not provide simpler to use gui, macro,...

A good example is the triggers feature. You can technically do things with that other hosts definitely lack - but it's hell to set that up - mabe just to select some sounds in external gear...

That's why I always try to look on a more practical side of features.

Your idea is great but it needs gui support to use it for simple common problems too.


BTW: I would appreciate HW keyboard controller makers to give us better keybeds for acceptable prices. Velocity keyboard curves on midi level always reduce velocity resolution and finally it's not the right place to do curve adjustments in the software. This can be implemented in the HW much better - and without loosing midi velocity values.

[Angelo]

I proposed, 7 years ago, a solution based on Midi-OX that worked quite well:
http://www.kvraudio.com/forum/viewtopic ... highlight=
Lengthy to implement but you can trim every aspect of the midi message.
Regards
Angelo

[TiUser]

...Lengthy to implement...

That's the main point I am about... ...make things easier to use, make it logical for musicians - not technicians.

I personally can deal with technical solutions - but I don't like it. I prefer easy to handle options.