you’re correct— thanks for catching that (i was testing extensively with live input, forgot to test sample loading). will get a fix right away.
Looks like this problem persists after i updated norns to 181002. I suspect it might have something to do with the Push 1 using two ports. See the attached screenshots of max and pd’s midi connection screens vs the norns midi screen. Is there a way to specify “Port” in norns?
no, it’s a known issue:
though, it’s weird (to me) that you can’t see port 1 on the norns.
I think I can see port 1, but its name has been truncated to “Ableton Push” from “Ableton Push Live Port” the live port is for Ableton Live. The second port “Ableton Push User Port” is the one that is useful in all other applications.
Thanks for the help!
how do i integrate my Touche with norns, as in the video by @tehn ?
oh goodness, i suspect we don’t have documentation for param midi learn anywhere? ah, i apologize.
this method will change slightly in the future as i’m redesigning the parameter menu system with @markeats presently.
thanks, is there any configuration needed? I bought the nub you linked to but it is failing on both hotspot and network.
ha ha - didn’t even realise there is a midi mapping mode. Nice!
Have you inserted it before powering up? That’s the key for making it work.
@spinos it would be very perplexing for that wifi nub to not “just work”. did you boot norns with the nub inserted? have you connected via serial before? (i could walk you through some further debugging). or depending on where you are, i can just send a replacement wifi nub (it’ll take awhile if not in the US).
@tehn yeah I booted Norns with the nub inserted. I’ve connected via serial before and could try debugging it that way if you tell me how. I’m in LA but I can try debugging before you send a replacement since it should work, thank you though
good first start would be to serial in and type lsusb for the wifi chipset. mine says:
lsusb
we@norns:~$ lsusb Bus 001 Device 003: ID 0bda:8176 Realtek Semiconductor Corp. RTL8188CUS 802.11n WLAN Adapter Bus 001 Device 002: ID 04b4:6570 Cypress Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Is it possible to connect midi out from Norns to Ansible using a standard usb cable? or do i need a hub between - like an iconnectmidi2+?
Ansible and Norns expect to be USB hosts so you’d need something like the iconnectmidi2+ which can bridge between two hosts.
ok thanks, i’ll give it a go.
I tried with an iconnectmidi2+. There is midi info lights going through the iconnect ok, but nothing being picked up on Ansible side.
we’ve been using this with Organelle http://compasflamenco.com/midi-c-3/midi-usbusb-p-4.html
its really cheap, 39 euro, and fast delivery in europe.(not sure about US delivery)
just a guess, iconnect thing could be acting as a hub, which ansible/TT doesn’t support (but norns should)
USB MIDI-USB thing on the other hand claims to be simply a class-compliant device on both ends
Just a quick question because I’m not at home and I’m pondering taking Norns at a gig next Saturday: does Norns remember midi controller assignments between power-offs and when switching scripts?
yes. midi assignments are stored per script.
