#3

I’ve added a number of questions and answers in the top post for this script (thanks to @Brennanib for the push to document a bit more by asking if he could use his nanoKONTROL version 1 with this). Hopefully that is helpful if you have some other sort of midi controller you want to control ER-301 (via crow via norns) with.

Happy to answer any questions here too if they arise.

2 Likes
#4

Thanks @jlmitch5 can’t wait to get this up and going!

2 Likes
#5

Hello there!
Maybe a noob question but:
I’m trying to use my 16n (leader mode) plugged into Fates to speak with Crow. Finally Crow is in a i2c bus with: JF, W/ and Er-301.
Er is rightly set to speak with Teletype/Crow.
Scripts like Animator works well with SC/TR units but N160 not🤔
What I am missing??
Thank you!

#6

hey @Alessio I believe @lilskullymane got this working with 16n so they might know.

just to check:

  • you have changed the CCs of 16n with the web config editor to what the nK2 has the faders and knobs set to (see image above in top post)
  • 16n is midi device 1 in the norns/fates settings
1 Like
#7

Thanks for the reply!
Wow: no, I must check the cc’s!
Which midi channel nanoK is configured on (by default)??
By now seems that the first faders cc are the same for both 16n and Nano😕

#8

@kasselvania this looks relevant to your interests

1 Like
#9

Channel 1. 20 charsssssss

1 Like
#10

When you are running the app and you move a fader you should see the ii commands that norns is sending in the bottom Right corner of the screen. If you are the issues is with norns -> crow or crow -> 301. If not the issues is with 16n -> norns

1 Like
#11

Solved! @jlmitch5 suggestions are correct :slight_smile:
You might simply map 16 faders with the correct cc’s and they works properly with Er-301 via i2c !!
Now I can put apart 12 patch cables, really nice.

Suggestions:

•if your controller have more than 8 faders (the 16n faderbank Eg.), you can map the values which correspond to Nanokontrol’s encoders.

1 Like
#12

I have updated the top post to more or less have this now (specifically how to set up 16n).

1 Like
#13

hey, just seeing this! glad you got it set up @Alessio. I went and added the n16o script to the other apps so I could use 16n alongside all the other good norns stuff. works like a dream with the er-301. do you know if there’s a way to bulk edit n16o in in maiden? took me a while to do every app individually and I’ve been hesitant to update apps where I’ll have to go back in and add it again.

1 Like
#14

Ah cool. Unfortunately no I don’t think there’s a way to do this cleanly at the script level…you could go in and commit your change then when you update scripts, unless there’s some really big changes around the init function, it will probably cleanly pull in

@tehn do you know if there is some base lua file or something that runs where you could hook an across-all-apps snippet of code in?

Norns: development
#15

I didn’t used Maiden: I‘ve simply copied the folder of the script that I want to modify from Cuberduck, and I’ve pasted it on a new version with n160 script integration.
For Eg. “Animator+n160”.
So put it in Dust etc🙂

#17

A post was merged into an existing topic: Norns: development

#18

Hi @jlmitch5

I’ve got everything set to go but I have 2 questions:

  1. Once I get it all hooked up (Norns>Crow>301) What do I have to do on the 301 to make it all work? The best I could tell from reading the er-301 post about connecting the 16n faderbank is that A. you have to enable Teletype control in the admin systems settings. And B. Once done you can then add a Teletype SV.CV unit and set it’s ports. Is this correct?

  2. You asked and answered this question above

Can you make the nanoKONTROL2 (or other midi controller) button led states line up with the current state of the 301 device it’s mapped to? No, I don’t think so…I don’t believe that norns supports bi-directional midi.

In the recent Cheat Codes 2 Beta I’ve been using Dan put in a Param for Midi Echo to be turned on (and I’m using it perfectly with a Midi Fighter Twister). Is this the same as Bi-directional comms? And if so then it may be possible which would be pretty awesome.

I can’t wait to hear your answers. So stoked you wrote this so a huge thank you! Also, I didn’t realize there was such a great i2c resource here! Thanks @okyeron for writing this up. It’s super helpful.

1 Like
#19

Hey!

  1. That sounds right!
  2. Honestly no idea on this one. It might be possible! I’ll have to take a look sometime. If you wanna get this in here I’d be happy to accept the PR
#20

Thanks for the reply! I’ll hit Dan up when he’s less busy with the imminent Cheat codes 2 release next week and see what he thinks about #2.

1 Like
#21

I forgot to ask, do you see any issue with this working on 301 firmware 0.5.03 or should I switch back to 0.4.27? I’m guessing nothing bad could happen to try the newer (though unstable) firmware except that N16o might not work?

#22

No it should work fine on 0.5.x which is basically just performance updates so far as I know

#23

Works perfectly! You’ve made this so easy to pop into any current script so I’ll try that in a few days. For now THANK YOU for your responses and all the work creating this.

1 Like