Korg Forums

[peter_schwartz]

Agreed, velocity is a much more difficult topic to resolve (pun intended) in terms of the practical application of having higher resolution (and editing those value - OMG!). In terms of control changes, MIDI already supports 14-bit CC messages, though few instruments respond to it. The fact that the Kronos provides parameter interpolation between "coarse" CC values is fantastic, and allows people to edit the more manageable number of 128 CC values than the 16384 that 14-bit MIDI affords. Anything that's going to reduce zipper noise or give controls a smoother feel is certainly a welcome thing. Increasing velocity resolution would be welcome too, but as I said, there's a limit to the practical application of it, at least at this time.

[StephenKay]

[peter_schwartz]

Hi Stephen!

Here's a linky where you can download a PDF about the HD velocity spec:

http://www.midi.org/techspecs/index.php

[maphill]

Rather than the resolution of MIDI velocity, the perceived problem is likely due to how that control is mapped to a sound. Obviously a piano program with 2 or 3 velocity layers will have very audible tone differences that don't smoothly vary.

Or if the physical velocity curves are mapped poorly for a given keyboard/performer, they may end up constantly playing at 127 or jumping between extremes.

However, if the control is set up well and the patch responds evenly, your ear will have a VERY hard time hearing ANY limitation due to the resolution of the velocity control.

I've written scripts that generated MIDI at all velocity levels and then play the notes sequentially. Or if you use an automated sampler like EmulatorX you can do something similar. The difference (on a good patch) between most incremental velocities is down around perceptual JND (just noticeable differences). Meaning, in a double-blind test on a program that is only scaling the volume and not switching layers, you will just barely hear the difference in volume between a velocity of 115 and 116.

The difference can be more pronounce on some synths at low velocity, but this is an implementation issue, not a velocity issue. (Running down to an unusable 0 amplitude with 0 velocity)

One other dimension to consider: How accurate is a player's velocity resolution? If a person can't consistently play at the same velocity level at the current resolution (can they play a 78 in velocity 3 times in a row?), then the current resolution is likely to be sufficient to capture a player's performance (the extra resolution isn't needed).

Food for thought.
Mark.
_________________
Korg KRONOS 73, Trinity Pro, Monotron,
Roland FA-06 and Fantom 6, Roland TDK-15
Big Knob, Sonar (Previously, OASYS 76)

[EvilDragon]

[synthjoe]

Some great discussion. I like most of it and agree with a lot of stuff, particularly with the velocity curves being cr@p.

And it also means, unfortunately, that the 127 values are not divided up in dB linear values, hence sometimes you get much less liberty than you _could_ control. Add to this all issues about samples, filters and envelope generators mentioned earlier and you got yourself quite a pretty mess.

So I agree that the biggest issue these days is probably not the 128 theoretical values you can have in MIDI (e.g. velocity), but saying that 128 would be sufficient for all purposes forever is about as bright a statement as 'No one will need more than 637 kb of memory for a personal computer' or that '320 kbps MP3 will satisfy even the most audiophile listeners'.

I think with most of today's digital keyboards these values are just fine, but for a realistic piano emulation, for example, I think we'll need to go beyond - and serious instruments demanding such solutions are coming up.

Finally, just for the record, 1 dB is an awfully bad granularity. When mixing, I'm often fiddling on .2 or .3 dB's on certain frequencies. Go and ask a mastering engineer about 1 dB granularity. You'll hear wonders...

Our ears are much more sensitive at certain frequencies and volume ranges than at others. If 1 dB was good enough, CD's would play scaled (velocity-curved) 7 bit data and not linear 16 bit.

[synthjoe]

[jemkeys25]

me too.

[SpIdErWeB]

[StephenKay]

[SpIdErWeB]

I agree and that's what I wrote Stephen... good enough for Keyboard.

I don't mean HD Midi is useless... I'm even curious to know more about it when it will be time. But for keyboard, I don't see lot of benefit for the velocity. (But I'm convinced there are other benefits somewhere else such channels, midi CC, etc...).

VSTs do use more than 128 steps internally and it doesn't make them more accurate, because the midi controller keyboard, even in USB, isn't good enough to transmit more steps... that's my point.

Phil

[Timo]

Bleh. 0-127 on a decent keybed with various curves is more than enough for me.

Something of more substance is the 0-127 resolution for filtering. That's where problems in resolution can really be heard.

On the Radias, the patented ultra-low aliasing algorithms and pristine high-frequency response captures the stepping artefacts perfectly.

http://www.infekted.org/korg/Rad-stepping.mp3

At least the Kronos/Oasys interpolates between MIDI/knob values, the Access Virus too. Great shame that the Radias didn't.
_________________
[Free Moss Set For All Workstations With Moss Expansion]
[Infekted.org - Original Access Virus Forum & Community]
Trinity V3 PBS | Radias KB | Virus TI Snow | Virus Indigo 1 | 505 Groovebox

[Shakil]

Somehow YAMAHA Motif series has 0-255 range for filter cut-off parameter.
_________________
Roland Fantom-G6 ARX1, Korg M3-m exb-Radias, Korg Z1-18v, Roland MC-808, Roland MC-909, Korg microKontrol.

[ozy]

[synthjoe]