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

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

FWIW - amidiauto should be installed by default on Fates.

Norns/shield would need to install it manually

1 Like

When you install Sidekick/Orac, the blokas repository is installed as well, so with a simple ā€œapt-get install amidiautoā€ anyone can install amidiauto.

I’ll make mandatory amidiauto on nornsmother, so in the next updates, IĀ“ll ensure everyone has it installed. :stuck_out_tongue:

1 Like

let me know if you get all the patches i made for them there should be like 30

Ive been working a bit on NuiLite today…
at the lowest level Ive added most graphic primitives that exist on the organelle,
they will not be 100% the same/compatible a variety of reasons, e.g. I want to allow for multiple levels of brightness which the organelle does not have, dont see need for different character sizes etc.

im keeping current api calls, but they will be considered ā€˜legacy’ to be replaced with the new ones.

current plan is Im going to
a) add these to the PD api
b) add a new OSC layer to sidekick, so that apps can interact with the hardware that way rather than have to use C++.

we’ll see how it goes, but probably id suggest you move to using (b) ,
then norns mother won’t have to do much other than translate the organelle osc messages sent , into the corresponding sidekick ones.

btw: for performance purposes in either case, Id avoid using ā€˜pixel’ level drawing, and rather have higher level calls - that then NuiLite can translate into low level cario calls - this is much more efficient.

7 Likes

i am hoping someone saw this. Is someone successfully using pd with grids?

DO i need to install the serialosc stuff for sidekick?

I remember seeing some scripts for grid implementation in to PD and Organelle on Patchstorage a while back. I don’t know if that would be useful in this regard. I am a total supercollider newcomer and never had an organelle, so I have no idea if this is useful or not:

2 Likes

i located that too i just dont want to mess up serialosc if it’s already in there

we don’t use serialosc on norns, just serial interface via libmonome.

it’s also possible to interface directly with the grid as a serial device from other environments besides C applications.

here’s an example in supercollider
[ https://github.com/catfact/catfact_sc/blob/master/catfact_util/CfGridRaw.sc ]

puredata has comport

Thanks for sharing that info, I wasn’t aware of that. I’ll check it out

As said above, you don’t need to install serialosc.

The patches in that Monome Grid Apps package should maybe just work? There’s a grid object, etc.

( I don’t know enough about pd to say for sure and would need a bunch of time to get this all setup on a box here to test)

2 Likes

the script to install the serialosc wants to be root to install

Summary
    • i dont think i ever learned about the root password for this box
    • i just tried installing the script for it and i get
    • 192.168.1.197 ~/sidekick/patches/SerialOSC-Installer $ ./install.sh
    • ./install.sh: 3: ./install.sh: Bad substitution
    • Preparing
    • ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files ===
    • Authentication is required to manage system service or unit files.
    • Authenticating as: root
    • Password:
    • polkit-agent-helper-1: pam_authenticate failed: Authentication failure
    • ==== AUTHENTICATION FAILED ===
    • Failed to disable unit: Access denied
    • rm: cannot remove ā€˜/etc/systemd/system/serialosc.service’: No such file or directory
    • ./install.sh: 17: ./install.sh: /home/we/sidekick/patches/SerialOSC-Installer/killserialosc.sh: Permission denied
    • Copying Libs
    • cp: cannot create directory ā€˜/usr/local/lib/monome’: Permission denied
    • Copying Shared Objs
    • cp: cannot create regular file ā€˜/usr/local/lib/libmonome.so’: Permission denied
    • Linking Shared Objs
    • ln: failed to create symbolic link ā€˜/usr/local/lib/libmonome.so.1’: Permission denied
    • ln: failed to create symbolic link ā€˜/usr/local/lib/libmonome.so.1.4.0’: Permission denied
    • Setting Paths
    • ./install.sh: 39: ./install.sh: cannot create /etc/ld.so.conf.d/usrlocal.conf: Permission denied
    • ldconfig: Can’t create temporary cache file /etc/ld.so.cache~: Permission denied
    • Copying Binaries
    • cp: cannot create regular file ā€˜/usr/local/bin/monomeserial’: Permission denied
    • cp: cannot create regular file ā€˜/usr/local/bin/serialoscd’: Permission denied
    • cp: cannot create regular file ā€˜/usr/local/bin/serialosc-detector’: Permission denied
    • cp: cannot create regular file ā€˜/usr/local/bin/serialosc-device’: Permission denied
    • Adding Services
    • cp: cannot create regular file ā€˜/etc/systemd/system/serialosc.service’: Permission denied
    • chmod: cannot access ā€˜/etc/systemd/system/serialosc.service’: No such file or directory
    • ==== AUTHENTICATING FOR org.freedesktop.systemd1.manage-unit-files ===
    • Authentication is required to manage system service or unit files.
    • Authenticating as: root
    • Password:
    • polkit-agent-helper-1: pam_authenticate failed: Authentication failure
    • ==== AUTHENTICATION FAILED ===
    • Failed to enable unit: Access denied

So it wants root i assume. anyone know if there’s one even set for factory norns off the top of their heads?

root/sleep maybe? (or you can just use sudo?)

But - really - don’t install serialosc

OK - maybe I’m wrong, but I don’t think you need it.

EDIT EDIT - I installed it once on one of my pi’s and i think I compiled from source

the grid does not work with the patches that were sent. Zebra said that it wouldnt conflict i just never have had to become root on Nrns. It’s a pretty small lib and 4 or shared object libs so it would be nice if it worked

would still need to sudo
lets see what happens

1 Like

New Update v0.2.9

  1. Amidiauto now is always active by default in all platforms.
  2. Automatic connection/configuration for midi devices and Pd using amidiauto (complex configurations have to be managed using post-patch.sh file)
  3. Fixed sound glitches (buffer size is increased to 8 by default), no more sound glitches (at least in my tests).
  4. Minor system changes.
  5. Added a CPU monitor to mother.pd

Update via ā€œUpdate Motherā€ on Sidekick menu.

13 Likes

This is gold! Thanks so much!! I was pleasantly surprised to see just how many Organelle patches actually work very well here at this point.

Hoping someone may be able to help answer this. Yesterday I updated to the latest version of Mother (v0.2.8 at the time) on my Fates, and manually installed amidiauto as was generally recommended around here. I then configured it to connect all midi devices as you had explained (* <-> Pure Data). I also changed the midi channel to 2. I was then able to use my KMI QuNexus keyboard plugged directly into Fates via USB with no issue. It would even send midi data out, so the lights beneath the keys of the QuNexus would provide feedback on certain patches which feature arpeggiators. That was great, and I also had it providing this light feedback to the QuNexus via Bitwig…

The only issue is; since this latest update, I’m not getting the midi output for the light feedback on the QuNexus. I couldn’t seem to make this function the same once again by repeating the same steps as I had yesterday. I would love to have that working again if possible! Thanks either way!

1 Like

Hi @static
You could try the following command to know what’s doing amidiauto.

aconnect -l

This command shows a log of what’s devices/programs are interconnected.

Is NornsMother sending midi? Check the midi signal dot near ā€œOā€ on the infobar.

1 Like

Where is the source code for this?
Couldn’t find it on GitHub , only the built deb and install script.

Uploaded right now

3 Likes