Was the velocity issue fixed on Version 3? Sometimes on the initial strike on the low velocity part of the key a high velocity signal is sent.
Your site is looking much nicer!
Hey Kalamata Kid, I wish I had responded sooner. I probably missed the KVR post reply notification. To answer your question, no such specific issue has been reported. What specific instrument or section of nChord was sending such high velocity signal? Ie., was that from ChordBank, from the ChordLibrary, from PadBoard, from etc.? I will be more than happy to check this out if you can give me more info on it.Kalamata Kid wrote:Hello Avantgarde Sound,
Was the velocity issue fixed on Version 3? Sometimes on the initial strike on the low velocity part of the key a high velocity signal is sent.
Your site is looking much nicer!
Short version:Igor Amos wrote:Can someone talk about how this compares to Chord track's chord assistant in Cubase? Would be great to hear from someone who has used both! I own Artist which has chord track, but not chord assistant and am looking for that functionality.
many thanks...
Sure. I am not going to explain nChord's algorithms or inner concepts, but yes, it is algos driving nChord's smarts, hence "A harmony modular super algorithm" is its 'slogan' kinda. Nonetheless, it is its conceptual approach what's most valuable about nChord. Like, it is commonly accepted that 1 + 1= 2 everywhere, that's stupid easy and we all take this info/data/math for granted; however, creating something that is beatiful and useful and thus desirable with that very basic info is where it's at. Therefore if people were to try to "desciphre" nChord's algos, in reality, they will still be nowhere even if they are handed the algos on a tray along with the morning paper and some orange juice... so to speak. Math and code are bricks and wood at most, imho.Igor Amos wrote:Thanks for much for the comparison. I'm mainly interested to hear how it makes chord progression suggestions. I don't know much about it all but I know Chord Assistant uses some algorithm that people seem to like that can recommend next chords based on what has gone before. And that it does it with most harmonic to most dissonant? Not sure exactly how it does this but can you talk about how nChords figures out its recommendations? is it based on a similar algorithm?
nChord is better, far more flexible and multiple times faster. But more importantly, nChord is more fun. It can also be as easy as you want, or as complex as you are willing to go. Plus, as mentioned before, with their solution, you are forced to make your entire project around their chordtracks, which is like a Big Momma track, and you only do what Big Momma says. nChord doesn't get in your way.Igor Amos wrote:I think I know what you are saying. I'm interested to know what options you have for determining what kind of chords it suggests?
Is it comparable to Chord Assistant in terms of different modes and "complexity" like chord assistant?

The criteria is set by the user himself when he choses a root note and a scale (which takes only a couple of finger taps [edit: there's *also* a scale audition sequence generator, to help you decide whether any scale fits your current composing mood, ain't it cool?Igor Amos wrote:what kind of criteria can you use to generate chords suggestions?
Kinda, yeah, almost right, because so far no nChord user has paid the full price amount. I try to mantain at least a minimal discount going on for everybody. Currently, new users can get nChord with a 30% discount, for instance.el-bo (formerly ebow) wrote:so, finally the puzzle is solved.....this is a $70 app, that is nearly 3 times as expensive as lemur (which is also needed). further to this, you recommend the use of another hardware device that adds another $100 to the cost
is that about right ??
I did not forget to reply.Avantgarde Sound wrote:Hey Kalamata Kid, I wish I had responded sooner. I probably missed the KVR post reply notification. To answer your question, no such specific issue has been reported. What specific instrument or section of nChord was sending such high velocity signal? Ie., was that from ChordBank, from the ChordLibrary, from PadBoard, from etc.? I will be more than happy to check this out if you can give me more info on it.Kalamata Kid wrote:Hello Avantgarde Sound,
Was the velocity issue fixed on Version 3? Sometimes on the initial strike on the low velocity part of the key a high velocity signal is sent.
Your site is looking much nicer!
For what is worth, in case you were experiencing this from ChordBank, as of v3, ChordBank features a so called Particle Mixer, ie, a per-note velocity slider for every note in any user-stored chord. This gives you plenty of micro-control to ensure your external sound generator sounds the way you want when receiving chords. As an addict to synth patch programming myself, I often enjoy making sure the velocity parameter interacts with or generates nuances in my patches, so it is very nice to have such detailed control level for ChordBank.
Thanks for the positive comment on the site. A couple other friends also mentioned that this same week. I just hope the powers that be are letting everybody get the same version...![]()
Cheers,
Avantgarde Sound*
*For the love of the machine
http://www.avantgardesound.com/
Twitter: @TweetAvantgarde (http://www.twitter.com/TweetAvantgarde)
--
Submit: News, Plugins, Hosts & Apps | Advertise @ KVR | Developer Account | About KVR / Contact Us | Privacy Statement
© KVR Audio, Inc. 2000-2026