#104

hmmm not working for me for some reason :thinking:

#105

Unfortunately i couldn’t get this to work - just the dry volume increases. Not sure why, maybe its a firmware thing as i am not on the latest on Fates

#106

This made me smile - thank you

Heres CA-Additive https://patchstorage.com/ca-additive/

6 Likes
#107

Are you using a raspberry 4?

#108

Sill getting a noticeable latency and some audio glitches running on my Fates RPI4. Is this normal?

#109

Blokas amidiauto
It’s not perfect but they say that it works in most of the cases…

Amidiauto has a config file, for complex devices like Launchpad should be made a rule.

You can try this:

  1. Log in to Norns via ssh.
  2. Edit de amidiauto config file:

sudo nano /etc/amidiauto.conf

  1. Paste the following code (ensure that is the exact name of your device, in your case “Launchpad Pro”):

[allow]
Launchpad Pro <-> Pure Data

Captura de pantalla 2020-03-26 a las 11.44.56
Captura de pantalla 2020-03-26 a las 11.44.56801×335 50.4 KB

4. Save and exit. Use ctrl+X --> yes
5. Reload amidiauto service using the following code:

sudo systemctl restart amidiauto

Try this configuration opening a patch…

  1. Check the connection using the following command

aconnect -l

Captura de pantalla 2020-03-26 a las 12.03.35
Captura de pantalla 2020-03-26 a las 12.03.35808×419 81.4 KB

Post your results (works for me with my “Arturia BeatStep Pro”)

EXTRA:
There is a way to connect all midi devices automatically to Pure Data using amidiauto.
Put like this:

Captura de pantalla 2020-03-26 a las 12.20.50
Captura de pantalla 2020-03-26 a las 12.20.50794×335 51.8 KB

More info here

2 Likes
#110

I’d highly recommend amidiauto.

the reason I didn’t ship it with sidekick, is I thought it was more something that should be installed as part of the FATES ‘os’ , rather than a 3rd party tool… as it obviously has quite ‘sweeping’ effects for any app that uses alsa midi

3 Likes
#111

Yes, i’m using a Raspberry Pi4.
One issue causing the glitches are the levels in some of these patches is very high and it’s clipping but there are also glitches I think related to buffers which I haven’t changed

1 Like
#112

Untitled
Untitled979×512 13.7 KB

trying automidi in a second. thanks for the help

1 Like
#113

Try it with a PD patch opened!! :stuck_out_tongue:

#114

oh whoops. ok but it seems like automidi worked, at least from aconnect -I

2
2979×512 12.4 KB

ok got it while i had a patch opened, you were right. thanks man
:+1:

3
3979×512 13 KB

it’s not actually working for midi note in though. I might have to mess with it. right now, its connected from the launchpad via usb. there is a regular midi din out which i might have to use instead. this shouldn’t have anything to do with my norns midi device slots, correct? and i should not have to re-edit the sidekick>post-patch.sh to reflect the aconnect settings?

this is progress though. furthest i’ve gotten since i installed orac or nornsmother. props to blockas & oxbown & technobear. you guys rule

UPDATE: This worked. thanks to Oxbown
aconnect 28:1 129:1
aconnect 129:0 28:1

3 Likes
#115

Is your hardware (Launchpad, nanoKontrol2…) working with Pd?

#116

a quick shout out to blokas is perhaps in order :slight_smile:
They are providing so much for the open source community - not only amidiauto, but PatchboxOS and also patchstorage.com.

So if you need an audio interface for your rPI , or an intelligent midi router - please consider pisound and their ‘midihub’ , to help support them.

6 Likes
#117

no, just the nanokontrol, but that was working before. sorry, edited the previous post to elaborate

re: the discussion below on amidiauto;
I have been aware of it and been using it to detect the launchpad pro ports for editing the post-patch,sh file; i just never got the right settings until today. I also never knew how to access the config menu. but yes, there is already plenty of info on it in the sidekick thread, it’s just scattered and esoteric like most things here. takes a little work to decipher/put pieces together

#118

With amidiauto you should not need post-patch.sh , the main thing to check is that it does not contain
aconnect -x , as this disconnects devices

As for testing, does midi clock get thru? If so it could be midi channel related.
Some organelle patches have their own logic for midi channel ( rather than use mother.pd handling)

Also this discussion is perhaps better in the sidekick thread, as this is all specific to sidekick not the norns
mother patch

Eg you’ll see in that thread amidiauto has already been previously discussed

2 Likes
#119

i am wondering and i’d love to hear ideas about using the grids with Pd norns. Is this working for anyone?

#120

when you transfer files to Norns you have to DOUBLE CHECK that when you transfer the files that the *.pd_linux gets transferred as well. I HAVE to every single time that i transfer something also make sure that i transfer the external. If you are getting ANY sound its working. Delay Volume is the effect volume but the patch is ONLY dependent upon vanilla AND the bubbler~.pd_linux

2 Likes
#121

You can transfer the .ZIP file in ./patches folder and next extract it with sidekick functionality.
Or you can modify the Samba server to gain access to ./patches folder, with samba is difficult to miss files on transmission.

2 Likes
#122

I was getting no sound from wet signal, but double checking those .pd_linux files were there did it for me.
Thank you for sharing these patches!

2 Likes
#123

I knew it because the same darn thing happened to me and i was freaking ahaha.
Oxbown posted a solution already for that-- this thread delivers :slight_smile:

1 Like