Nord User Forum

Just figured out something interesting (if not overly practical). It is possible to create a "multi" (read: 2) layered sample with the following steps:

1. Activate the synths on both panels A and B at the same time
2. Load the sample for the first velocity layer on panel A and the second on panel B
3. Turn the Nord's local midi control off
4. Set panel A to respond to channel 1 and B to 2
4. Using your choice of midi software, route any notes of a certain velocity or lower (say 63 and below) to channel 1 and any notes higher to channel 2


Again, not that practical but still interesting.

That's really creative @NordBoy. You can also use the Mod Envelope to modify the Osc Ctrl and Filter Cutoff Freq to change the sound based upon velocity.

NordBoy wrote:Again, not that practical but still interesting.

Yup, also discussed at nord-stage-forum-f3/touch-sensativity-o ... 13131.html

Nice.

But in the end still not interesting. Clavia should really start making an open sample format or a sample editor that allows to load multi samples into the Nord Stage / Electro / Piano etc. It's 2018 now and one-layer-samples was ~ 1985. Clavia should realize that we want to load our own rhodes / piano / dx piano / brass / string / what ever sound into the nord keyboards without too much compromises. That means: Multiple samples per key for different velocities. Possibility for round robin samples. Release samples (important for rhodes, clavinet, harpsichords).

Everybody needs that at some point. But most people don't know.

jazzundso wrote:Nice.

But in the end still not interesting. Clavia should really start making an open sample format or a sample editor that allows to load multi samples into the Nord Stage / Electro / Piano etc. It's 2018 now and one-layer-samples was ~ 1985. Clavia should realize that we want to load our own rhodes / piano / dx piano / brass / string / what ever sound into the nord keyboards without too much compromises. That means: Multiple samples per key for different velocities. Possibility for round robin samples. Release samples (important for rhodes, clavinet, harpsichords).

Everybody needs that at some point. But most people don't know.

What you describe is a different instrument, then, more a workstation than what the NS is designed to be, so far...

Why? the multi sample playing engine is already there! They need to provide a multi sample editor, which they must have, of course, otherwise how do they construct npno files?

What is exactly the advantage of not letting anybody else construct npno files?

Mr_-G- wrote:Why? the multi sample playing engine is already there! They need to provide a multi sample editor, which they must have, of course, otherwise how do they construct npno files?

Mr_-G- wrote:What is exactly the advantage of not letting anybody else construct npno files?

My suspicion: Very well thought through product evolution plans where memory additions, new functions, sample versions and edit possibilities are laid out over time and model evolutions so to get the most buck back from every added bang.
I cannot see any other explanation for some of the functions that would be super simple to "SW add" to existing models, but are not.
This in combination with a very non-active customer contact approach where there is no place to discuss functions and get reasons back why this or that is or isn't doable.

In my professional role (product pricing, but not in any music related business) it makes me all warm and tingly inside because they seem to succeed in making a lot of bucks for not that many bangs, and most customers are still devoted and pony up the bucks for the next model because they added just a couple of new things.
But as a customer it doesn't make me that happy... If I would try this approach on my "day job customers" they'd tell me to go to... well, someplace warm and unpleasant and we'd be out of business.

Don't get me wrong - I love the sounds and useability of my Nord. Wouldn't trade it for anything.
But in this day and age I expect more customer attentiveness from a manufacturer of such a high cost and high reputation brand.
Zoom, Presonus and others make me a lot happier post-purchase than Clavia does, by improving my purchased product with each firmware update.

It’s not easy to keep the balance right between continuous revenue streams from new products (which is essential for a company to survive and support future developments) and continuous support of existing/old products to fulfill the wishes of existing customers and keep them happy (which is usually expected to be free of charge because it’s “just” software). One way of making sure that support and new development of functions for existing products contributes to the profit and therefore survival of the company is to make this a service which customers pay for. I’m in software business and our customers pay a yearly fee for maintenance and update services for the software, thus making sure that fixing of errors as well as implementation of new functions are provided timely.

So one question to all of you: who of you is willing to pay a yearly fee and in turn will get the right to participate in future updates with new functionality for your existing product?

Hervshahn wrote:It’s not easy to keep the balance right between continuous revenue streams from new products (which is essential for a company to survive and support future developments) and continuous support of existing/old products to fulfill the wishes of existing customers and keep them happy (which is usually expected to be free of charge because it’s “just” software). One way of making sure that support and new development of functions for existing products contributes to the profit and therefore survival of the company is to make this a service which customers pay for. I’m in software business and our customers pay a yearly fee for maintenance and update services for the software, thus making sure that fixing of errors as well as implementation of new functions are provided timely.

So one question to all of you: who of you would be willing to pay a yearly fee and in turn will get the right to participate in future updates with new:added functionality your existing product?

I guess I seriously derailed the thread. Sorry for that.
Maybe we should make a dedicated thread (which I assume there are similar already...)