Nord User Forum

Why can‘t I take two nord instrument sample files and use the editor to create an internal split having one sample to be played for 3 lover octaves and other for upper three?

If this is NOT possible and just by raw samples this is like disassembling two cars to park them in your double garage.

And yes there is sample robot but I have the data already, its in the files, thanks.

Dreamer wrote:Why can‘t I take two nord instrument sample files and use the editor to create an internal split having one sample to be played for 3 lover octaves and other for upper three?

If this is NOT possible and just by raw samples this is like disassembling two cars to park them in your double garage.

And yes there is sample robot but I have the data already, its in the files, thanks.

The answer to that question is as follows.

If two NSMP files are together, they would have to be created as a split on the instrument using panels on the stage.

I can see the issue here and agree that it's annoying that there should be the ability to grab 2 nsmp files to create either a split or merge, but unfortunately, once an nsmp file is created, it can't be decompiled. that's the issue.

lew

There have been a couple of lengthy discussions about this over the years which I understand very well. From my point of view Clavia as the creator and owner of the sample format should be able to “decompile” a sample with Sample Editor while at the same time keep it internal within the editor only. By this it’s avoided to get the sample out of Clavia’s ecosystem while at the same time Nord users can modify/adjust to their needs. That would give us and Clavia an added value, but since Clavia did not do anything up to now I doubt that we can expect something like this in the future

We should give Nord particular feature requests so they can understand our needs as users, if they don't know, they won't do. so, with both NSE and NSM we need to show nord what we need out of the software to make it more viable for us.

the .nsmp and .nsmp3 formats are a custom format and as such, to be able to extract data is not viable unless the right resources are available to do so. In order to open an .nsmp / .nsmp3 file, it should be made available to open the file in NSE and edit to fix issues, otherwise it's ridiculous. it's not like a .wav extension that's locked, you can grab that file import it in to an editor and fix any issues with the file with good tools and techniques.

I have nsmp files from a particular developer and unfortunately, some of the nsmp files have flaws and faults, I can't fix them so they're unused and I've lost good money buying these libraries. so with that, the ability to fix sample looping issues, normalisation points, etc would really help.

lew

Been playing around with NSE3 today, importing Fairlight samples into my Nord Stage 3 HA88. I noticed that I cannot have a sample run the entire range of the keyboard; it's limited to the 2nd to the last octave on the keyboard. I can't stretch the range any further, even though the keyboard range is wider than what appears on the screen. Feature or bug?

elsongs wrote:Been playing around with NSE3 today, importing Fairlight samples into my Nord Stage 3 HA88. I noticed that I cannot have a sample run the entire range of the keyboard; it's limited to the 2nd to the last octave on the keyboard. I can't stretch the range any further, even though the keyboard range is wider than what appears on the screen. Feature or bug?

that wouldn't be a bug.

that's a design implementation. if a single sample (not a recorded multisample) is used across the key range, the sample is being stretched to beyond it's technical sonic characteristics, therefore running a sample to it's uppermost octave as a single waveform is not a good thing as that would produce aliasing and would sound horrid.

you're best off creating a multisample waveform where you record from the lowest possible octave to highest the instrument provides in minor 3rd steps, saves memory and still provides what's needed. if you need any help, I'm happy to spare some time on it with you. I love this version, it's opening doors for me that version 2 couldn't do for me, it was hell trying to use it blind believe me. this version makes the job easier.

lew

LewTheKeysGuy wrote:We should give Nord particular feature requests so they can understand our needs as users, if they don't know, they won't do. so, with both NSE and NSM we need to show nord what we need out of the software to make it more viable for us.

the .nsmp and .nsmp3 formats are a custom format and as such, to be able to extract data is not viable unless the right resources are available to do so. In order to open an .nsmp / .nsmp3 file, it should be made available to open the file in NSE and edit to fix issues, otherwise it's ridiculous. it's not like a .wav extension that's locked, you can grab that file import it in to an editor and fix any issues with the file with good tools and techniques.

I have nsmp files from a particular developer and unfortunately, some of the nsmp files have flaws and faults, I can't fix them so they're unused and I've lost good money buying these libraries. so with that, the ability to fix sample looping issues, normalisation points, etc would really help.

lew

+1000