#122

Everyone should run this command.
(It makes the ‘check for updates’ available for future releases)

2 Likes
#123

Forgive me if I missed this somewhere but I’m having trouble with midi learn on my factory norns on Orac. Im using an op-1 for sending midi but Im not getting any activity.

What I did to try to get it working was go to the menu select learn midi, hit some keys and saved. This did not work though.

#124

I couldn’t get my op-1 to work for midi either. i’ve been using a native instruments keyboard instead. :slight_smile:

#125

Ahh thanks. Bummer im out of state for a few more weeks and that’s all I have for midi right now aside from an op-z that I could try but its not really very friendly for playing notes as we all know

#126

ok, so by default most midi devices connected on usb will come in on 20:0 on alsa.
it may be different for the op-1

no worries, this is all configurable :slight_smile:

so on the norns with op-1 connected… type

aconnect -l

this will list midi devices, look for the address of the op-1

now in ~/sidekick/post-patch.sh you will see the line

aconnect 20:0 128:0

so whats happening here is…
after any patch is run by sidekick, sidekick runs this script, to connect midi devices to 128:0 which is the virtual pure data port

so all you need to do, is to change the 20:0 to the address of your op-1 which is possibly not 20:0

note:
sorry, I don’t have an op-1 so I can only talk in general terms

note2:
first test with notes from the keyboard, as midi learn can be a bit tricky initially if you are not used to it :wink:

4 Likes
Norns Mother (Organelle Patches on Norns)
#127

oddly enough, it seems op-1 is connected to 20:0

09%20PM
Screen Shot 2019-10-17 at 5.25.09 PM.png910×406 48 KB

still no dice.

#128

hmm, id probably use amidi then to try to get it to dump the input…
check that your getting data coming thru.

the default orac patch (demo-1) is listening on midi channel 1 for input.
(actually you already know that, given you’re successfully using another controller… but useful into :wink: )

1 Like
#129

How do you like that keyboard? I don’t even have a dedicated midi surface like that at the moment. I use all kinds of sequencers and stuff over a number of different devices, but I keep wondering if I should get something strictly Piano based. If you don’t mind, can I ask a few questions about your experience with it DM?

#130

sure! don’t mind at all

#131

One last thing on the vncserver (which I have working well now!) I followed the instructions about making a startvnc.sh shell script to run vncserver, but it doesn’t seem to show up as a selectable item in sidekick’s menu. Was it supposed to? I made it executable with a chmod +x… any other ideas?

2 Likes
#132

Now the community has to join forces to create/port Puredata patches and make the Norns the best portable music device (if it wasn’t yet). The @thetechnobear has given us the right tools to make pretty nice things…

3 Likes
#133

rename it run.sh
place it in a directory ~/sidekick/system/startvnc

#134

hi there is it possible to connect to more than one midi device ie keyboard and monome is it just a case of adding another line to aconnect :-
aconnect 20:0 128:0
aconnect 24:0 128:0

1 Like
#135

yes, if you want the new controller on ch1-16 in pure data.

however, you can also do some other clever stuff…
e.g. map second to channels 17-32 in pd

you can also do ‘midi thru’ with alsa…

I’ve covered these topics in a post and video over at C&G forums

note: pd-opts.txt discussed in this post is also supported by sidekick :slight_smile:

also…

the number addressing scheme is only one mechanism,
you can also use

aconnect 'OP- M idi Device:0' 'PureData:0'

if you want to map devices regardless of how they are connected.

the reason i use the number format (20:0) is that it will connect any device on the usb port, so its a bit more flexible for a ‘generic’ setup.

btw: i don’t take any credit for this stuff… alsa is just a fantastically flexible system for midi, Im just leveraging whats made available by the cool alsa developers :slight_smile:

1 Like
#136

One suggestion.
Hei @TheTechnobear, is there any possibility to implement I/O audio indicators on the Norns screen like the Organelle?
IO_Audio
And another good idea is to add an icon or something similar to view the MIDI I/O presence.

1 Like
#137

yeah, its possible…

however, bare in mind the graphics are done in MEC and all audio/midi IO in PD.
basically MEC is the ‘client’ and PD (where orac is running) serves as an audio engine.
(note: currently on Organelle, its a bit different, for reasons I dont really have time to go into now :wink: )

so this requires a change to orac, for it to ‘broadcast’ the audio/midi IO levels to MEC, then I need to extend the NuiLite with some more graphics primitives.
both are things I want to do…
(and then these changes will mean other client UI will also get these ‘abilities’)

next change I want to do is extend Orac/MEC to support the ‘Aux Line’ , ‘Aux Button’ and ‘Aux State’, which means changes to the OSC Kontrol protocol, so I’ll look to see if it’s viable to do this at the same time (or at least put the fundamentals in place)

2 Likes
#138

How about amidiauto? The blokaslabs team deal with the interconnection of different MIDI devices with this application (background service).
https://blokas.io/patchbox-os/docs/amidiauto/

#139

yes, users can switch to using that if they prefer…
but I do not want Orac/Sidekick to be dependent on it, I want to keep my dependancies at a minimum.

Ive talked with @okyeron , and the idea is that the fates distro might include it.

I like amidiauto but its no ‘magic bullet’,
it solves the easy use-case, but actually can get in the way of more complex use cases …
e.g. it assumes you want all controllers mapped to the first 16 channels in PureData, but that’s not always the best way. also if you have something like a Push2 with multi channels it can get things wrong.

also you’ll be surprised, aconnect 20:0 128:0 works for 90% of use cases.
(even the OP-1 issue raised above, works for this… its a different issue)

all this does raise an interesting question…
things like VNC support, using amidiauto - I wonder where these are best discussed, (new topics?) since they are more general rPI topics than specific to Orac etc.

btw: anyone reading this… if you want excellent information on how to configure/setup raspberryPi, Id totally recommend the blokes forum - its an excellent source of information, and the support guys there are really helpful !

2 Likes
#140

In Orac, how do you change from a1 to a2 to… b1, c1 etc. from the fates front-panel? I can do it with the PD/OSC widget, but can’t find the magic key-combo…

#141

But 3 + enc 2 = switch module
But 3 + enc 3 = switch page

1 Like