So, after the new update, still no changing midi channels???

Raz Koller

I have to start a new thread, because the website has some kind of bug and won't post in my old thread.

Let me explain again:

If I'm using Kontakt 7 and I have created a few sounds, I like to place them on different midi channels. That way when playing live, it's easy for me to jump quickly between the different sounds.

I can do that easily with any other keyboard I own, because they all just have a knob to change the midi channel on the fly.

But this "premium" £700 "midi" keyboard does not have that.

So when playing live using Native Instruments software, I can't use their keyboard.

And no, to my understanding the new update does not solve it, when you're using an NI product, you're still stuck on their product screen without any control over your midi channel.

I'd be delighted to be proven wrong, because I've been using cheaper keyboards live and it would make me feel less like a sucker to be able to do on my premium keyboard what I'm doing on my cheap ones.

So - anyone has an answer?

Kymeia

You don't have to stay on the NKS screen - you can flip into the MIDI screen (shift/MIDI) and move between templates set to different channels with just a touch of the Next/Previous buttons, or create key maps and play on different channels that way - and you can also alternate between the NKS and MIDI screens on the fly. Neither are they mutually exclusive modes, once you have set the template being used even if you go back into the NKS screen (say to move knobs) you still stay in the channel set in the template loaded (along with any other changes made such as touchstrip cc or pedals)

Matthew_NI

@Raz Koller this is the answer ^

Sunborn

https://community.native-instruments.com/discussion/34567/so-after-the-new-update-still-no-changing-midi-channels

@Raz Koller the site does not have any bug. It was your post (which was attempted 6-7 times to be posted) that ended up in the spam folder because you insisted to to start it with the phrase "Holly ******", every time…. 🙄

Raz Koller

Kymeia Thanks. I'll give it a try.

Raz Koller

Sunborn, ok then. Problem is what I saw was a php error saying that a string was passed instead of an object. Every time.

At some point I suspected it was the 'bad word' (by the way, very mature of you guys), and removed it and I got the same error.

I can imagine what the codebase looks like. I also think I know which framework you guys used to build this.

My advice? Showing a front-end message and disabling the back-end error messages in production is always better. You can probably do this in the .env file.

For the scenario you are describing, however, a better UX would be the Steam approach - you accept the post as is and just remove the 'bad words' (again, can't express how mature that is) and replace them with stars or hearts or whatever.

Just a thought.

Sunborn

https://community.native-instruments.com/discussion/comment/170862#Comment_170862

• I am not aware about the .php error but, anyway, it is not on our hands, but on the developers of our forum provider.
• the "spam identification" process is automatic, suspected messages go there instantly… only after that we can see them… and honestly this is the best way, since the forum was under heavy spam attack for a long time… so massive that it was impossible for the moderators to deal with it…
• i assume that you got the same error even after you removed the "bad phrase", because you already had more than 3 comments in the spam folder… 😉

Raz Koller

@Sunborn I mean, I think it's probably an easy scenario to repeat. Just write some 'bad words' in a comment and see if you're getting the same php error that I got.

The 'spam identification process' is not 'automatic'. I mean, I'm sure it supposed to look like it is from the user perspective, but nothing is 'automatic' as in 'can't be changed'.

It's a simple if condition with probably a function that looks for a hardcoded array of words or phrases in the incoming input. The way it handles what it finds can be easily altered.

And about why I got the same error, even if there were already messages in the 'spam folder', it doesn't matter. The end user should get a proper message to explain what is wrong, and the ability to fix it.

Also, why would bad words send messages to a SPAM folder??? Why not just remove them or as the user to remove them? 😕 A very strange UX decision.

You should have some kind of warranty with the company that built the website, and if I were you I'd raise these issues with them, but hey - you guys do you.

Also, if you don't have a warranty, you can probably get some freelancer to fix this issue. This website is pretty basic, so you should be able to find a kid that would do it for cheap.

Matthew_NI

@Sunborn is a user, not an employee of Native Instruments.

@Sunborn also graciously acts as a moderator within the community, helping thousands of other users, whilst simultaneously and constructively holding us to account.

In other words - they are on your side, and the side of all users, and only trying to help here. Please try not to argue with someone so helpful about the use of inappropriate language and how or why it would have been flagged.

The facts of the matter are:

• We use a Community Forum tool made by Higher Logic
• It worked as intended, in that it automatically flagged repetitive posts containing inappropriate language
• Those posts then landed in a Spam Queue and/or a Moderation Queue for Moderator Review (see image)
• They were appropriately dealt with
• Whether through reading release notes in Native Access 2, watching the launch video on Youtube, receiving the announcement email, or seeing a multitude of posts on this forum, you were also able to obtain the answer to the question you sought to ask: that MIDI Template Editing has now shipped