Nord User Forum

Alright guys, the NS3 is a new product and is obviously going to have some initial difficulties as it finds itself into its first users' hands. We're early adopters on a major product revision--it's what we signed up for. I thought it might be helpful to start a thread specifically for documenting which issues have come up and which ones have been addressed directly in contact with Clavia support. I figured this is a place we can keep notes and compile the results of our support tickets in one spot. I can start with:

ISSUE: Incoming MIDI velocity data is dramatically sensitive to make the Piano section almost unplayable with many external controllers.

RESPONSE: Nord USA and Pablo are aware of the issue, but it's taking a backseat to getting the NSMP3 Editor Released



ISSUE: Nord has missed its Oct 2017 release deadline by a modest week and a half of the Nord Sample Editor for NS3

RESPONSE: Nord has directly acknowledged they are working hard to get it out as soon as possible




ISSUE: C2D Organ engine behaves markedly different from NE5

RESPONSE: According to another thread, Nord is also aware of this and has sent an email indicating they are considering addressing it in a future firmware update.

You're welcome to add the bugs to the bug sheet, where the other ~40 issues have been documented. There is also a place to add feature requests.

You're also welcome to update the sheet when bugs are fixed; I'm trying to keep it tidy (from time to time, as time allows) or to reproduce known bugs if they are not already, but am not always able to keep up. In any case, the sheet is meant to be a collective effort.

As for shipping delays, let's maybe keep that out of the sheet. It's better to have focus on the actual bugs, I think, and make sure we document those in reproducible ways.

Nord is aware of the sheet too.

Oh no this isn't meant to be a bug tracker, but rather just a place where people can compile their responses from tech support in one place. There seems to be a lot of anxiety coming from people that Nord is not listening to them and I don't think that's the case so I thought it might be helpful to compile these responses so that people can be reassured that certain issues are definitely being acknowledged, that's all. I have already submitted my trouble tickets and I will try to add them to the sheet as well

Fallboard wrote:I thought it might be helpful to start a thread specifically for documenting which issues have come up and which ones have been addressed directly in contact with Clavia support. I figured this is a place we can keep notes and compile the results of our support tickets in one spot.

Good idea.
I'd propose to add an extra 'tab' to this sheet.

Than everything is close together and easy to see if something was resolved and when.

Update: I saw the other responses already. That's what I get for not refreshing on time

Fallboard wrote:Oh no this isn't meant to be a bug tracker, but rather just a place where people can compile their responses from tech support in one place. There seems to be a lot of anxiety coming from people that Nord is not listening to them and I don't think that's the case so I thought it might be helpful to compile these responses so that people can be reassured that certain issues are definitely being acknowledged, that's all. I have already submitted my trouble tickets and I will try to add them to the sheet as well

Very useful

Fallboard wrote:Oh no this isn't meant to be a bug tracker, but rather just a place where people can compile their responses from tech support in one place. There seems to be a lot of anxiety coming from people that Nord is not listening to them and I don't think that's the case so I thought it might be helpful to compile these responses so that people can be reassured that certain issues are definitely being acknowledged, that's all. I have already submitted my trouble tickets and I will try to add them to the sheet as well

You may consider adding an extra tab (as also proposed by @RIchardG) and/or another column to capture any responses from Nord, if it adds value and you think it's missing.

And by all means, you're of course more than welcome to maintain a thread on Nord responses.

It was just that your thread heading started with "Known Issues ..." and I wasn't sure you whether you were aware of the bug sheet?

WRT that sheet, I think it is not kept to date. For example, issue 15 seems t work fine now. It woud be great if people that have contributed to the sheet test the issues they've found when a new OS is available. This is what I found so far (using 1.24):

15 seems ok now (1.04)
25 I cannot reproduce this (1.04)
26 seems to work OK now (1.04)
29 seems to work ok now (1.04)

I think it is good custom that people that opened an issue will also close them.

Brilliant post!!

We should also prioritize these issues and I agree; the Sample Editor for the NS3 should be the #1 highest priority.

kbrkr wrote:
We should also prioritize these issues and I agree; the Sample Editor for the NS3 should be the #1 highest priority.

Yessss - totally agree!

The sheet is deliberately open to anyone that wants to contribute. It's a substantial effort to recreate and check all bugs and we all have varying amounts of time to pour into this, so let's try to do a collective effort also in closing the bugs.

As for closing the topics, I think the best way is that someone that 1) either knows or have been able to reproduce specific bugs originally and 2) can confirm they are fixed by testing it, then 3) proceeds to close them with a note in what release it was done.

Some bugs do not have easy reproduction steps, and those needs to be left to the original creator to close.

When I get time, I will try to close some more that I think has been fixed, but I'd like to verify that they are indeed fixed, which could involve some MIDI debugging etc. If you, @Streef (or others), were able to reproduce an original bug and now can confirm it works, please close those you discover and verify are closed, thanks.