it’s working for me here… what are you trying to do?

automatonism works on organelle, so I see no reason why it should not work on Norns.

you’ll just need to ensure you use the version built for the rPI, so that you get the correct externals.

note: the orac/sidekick install, installs PureData 0.49, so pretty up to date :slight_smile:

…still haven’t found my way to record using nori sampler…:slight_smile: cc 69 not working for me. Do I need to add something before nori in order to work?

where do i find this version?

sorry, my mistake i assume it had externals… but it seems to be just plain pure data,
so the main download will work ‘as is’ , its not different for different platforms.

also interestingly, it has some organelle sub patches - these could probably be quite easily adapted to work on the norns - as I’ve show with the ‘organelle converted demo patch’

1 Like

@thopa Not sure if you ever got this resolved; it’s a little buried in here.
The actual script name/location is ‘~/sidekick/system/startvnc/run.sh’ (the script must be executable; i.e. chmod u+x run.sh)
NOTE carefully the directory name “system” vs. “System” - it is case sensitive.
then, inside ‘run.sh’ you have the vncserver command
e.g. personally, mine contains vncserver -randr=1600x900 to give me a slightly large desktop than normal.

1 Like

@thetechnobear
Installed on a still smoking Fates DIY (j/k). Everything is working beautifully (I’ve never seen a simpler install of such a complex system); the norns stack is amazing (very latest version 191201), having lots of fun with even just “awake”, BUT I hear no drums when ORAC starts up (I have a fresh install of sidekick which I updated using the SK menu straight away), and neither of the demo patches produce any sound (do they require an external clock?)

I tried to do a little troubleshooting…

On 4-encoder fates (tbh, 4th enc is untested as norns stack doesn’t use it, and I get no
sound from ORAC):

  1. Three button salute brings up SK
  2. select startvnc from SK menu

On laptop:

  1. connect vnc viewer
  2. open terminal (from vnc desktop)
  3. stop SK service: sudo systemctl stop sidekick (in terminal, on vnc desktop)
  4. start SK manually: cd ~/sidekick; /usr/local/sidekick/sidekick (in terminal, on vnc desktop)

At this point, I get

starting sidekick
using framebuffer /dev/fb1
load startup patch: Orac
launch : Orac
exec : cd "./patches/Orac"; ./run.sh &
exec : "./post-patch.sh"
starting orac
Connection failed (Invalid argument)
  1. open PD patch… (from terminal in vnc session? ¯_(ツ)_/¯)

Anyway, if I run pd from the terminal on the VNC desktop, and then try to turn on the PD DSP,
I get

ALSA input error (snd_pcm_open): No such file or directory
ALSA output error (snd_pcm_open): No such device

So maybe ALSA has a config problem? PD…? Some service is being killed inadvertently…?

@ground_state Thanks a lot for that :slight_smile:
I have not been too active on the forum as of late (work | family | soldering) so i had forgotten about this!
Thanks for letting me know, much appreciated!
Cheers

1 Like

Total guess - but check and see if jack is still running maybe?

ps aux | grep jack

And/or post results from this:
aplay -l

@okyeron Random data points:

  • Oh, hello, smoking gun…

    ~ $ ps aux | grep jack | grep -v grep
    * crickets *
    
  • Argh aplay -l I’ve been trying to remember that all morning

    ~ $ aplay -l
    **** List of PLAYBACK Hardware Devices ****
    card 0: sndrpiproto [snd_rpi_proto], device 0: WM8731 HiFi wm8731-hifi-0 []
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    card 1: vc4hdmi [vc4-hdmi], device 0: MAI PCM vc4-hdmi-hifi-0 []
      Subdevices: 1/1
      Subdevice #0: subdevice #0
    
  • Using @TheTechnobear’s instructions for using VNC et al. to do Pd work - I got noise out of e.g. the recent “port” of Aquarius, but I had to manually change Pd’s audio out to the WM8731 from HDMI (not sure why it would default to that).

Side note; I’ve had absolutely zero issues with fates itself or on the norns side of things

EDIT: Meanwhile, after restarting Norns (“awake” specifically) via SK, I see

~ $ ps aux | grep jack | grep -v grep
we        3192  6.5  9.6  98416 91648 ?        SLsl 15:30   0:02 /usr/bin/jackd -R -P 95 -d alsa -d hw:0 -r 48000 -n 3 -p 128 -S -s

Actually not really. Norns uses Jack. Orac uses alsa. With sk/Orac your results are “correct”. If Jack was still running it would block the audio from working.

What’s vc4hdmi? Do you have a display hooked up on hdmi? If so I wonder if that’s hogging or defaulting the audio from alsa

Ohhh. I see.
I assume that “vc4hdmi” is the HDMI audio. Nothing’s plugged in there, although I did set up the OS with the 3b+ connected to an HDMI monitor w/ USB keyboard/mouse (I got bored waiting on Mouser :}). Maybe there’s some stale state hanging around somewhere?

Yeah you don’t want jack running if running pd.

Does the PD GUI - test audio work?

I did not specifically do the Pd audio test. As I mentioned above, I loaded up Aquarius-5, and it worked wonderfully after I changed Pd’s audio out setting to use card 0: sndrpiproto (the WM8731) instead of card 1: vc4hdmi, which it had defaulted to.

tldr; jack is not running (under SK), but alsa’s default output device might be wrong - I don’t know how to check.

Self-inflicted. At some point, I installed something which added dtoverlay=vc4-kms-v3d to /boot/config.txt, which apparently confuses ALSA’s idea of what the default card is. Removing that line fixed the world :slight_smile:

2 Likes

I’m exploring Orac on the Fates I built last weekend on a Raspberry Pi 4, and I’m starting to feel a bit stupid. When I boot into Orac I hear the euclidian drums, but no matter what synth I load into a1 or c1 seems to react to MIDI. I’m using a class compliant USB-MIDI cable and I’m seeing the light flash, indicating it is receiving MIDI. MIDI works fine on the Norns side. Is there anything I can do to see if Orac is getting MIDI?

Blockquote
127.0.0.1 ~/media/orac/usermodules $ aconnect -l
client 0: ‘System’ [type=kernel]
0 'Timer ’
1 'Announce ’
Connecting To: 128:0
client 14: ‘Midi Through’ [type=kernel]
0 ‘Midi Through Port-0’
client 20: ‘MIDIMATE II’ [type=kernel,card=1]
0 ‘MIDIMATE II MIDI 1’
Connecting To: 129:0
Connected From: 129:1
1 ‘MIDIMATE II MIDI 2’
client 129: ‘Pure Data’ [type=user,pid=5920]
0 ‘Pure Data Midi-In 1’
Connected From: 20:0
1 ‘Pure Data Midi-Out 1’
Connecting To: 20:0

Blockquote

Hi all
I am finally getting around to truly scoping out ORAC 2.0 on my FATES, and I was curious about where one gets the scripts and which kinds of scripts work best.

My question is this: what kind of PD scripts can I put on ORAC 2 that would work without any alteration on my part? Would this be most PD scripts? Do they all automatically format to the screen? I look up ORAC scripts on PatchStorage and they’re all for the organelle, making me fear that I will need to do extra work to fix the audio/input out.

Any direction on that would help, thanks!

1 Like

Patchstorage and maybe https://forum.critterandguitari.com/t/modules-for-the-orac/2823

I just tried to install orac and sidekick on my fresh built Fate but got a few error messages in the end and a suggestion I sadly don’t understand:

E: Failed to fetch http://ftp.halifax.rwth-aachen.de/raspbian/raspbian/pool/main/libd/libde265/libde265-0_1.0.3-1+rpi1+b9_armhf.deb  Connection failed [IP: 2a00:8a60:e012:a00::21 80]
E: Failed to fetch http://ftp.halifax.rwth-aachen.de/raspbian/raspbian/pool/main/libx/libxcb/libxcb-sync1_1.13.1-2_armhf.deb  Connection failed [IP: 2a00:8a60:e012:a00::21 80]
E: Failed to fetch http://ftp.halifax.rwth-aachen.de/raspbian/raspbian/pool/main/g/gem/gem_0.94-1_armhf.deb  Connection failed [IP: 2a00:8a60:e012:a00::21 80]
E: Failed to fetch http://ftp.halifax.rwth-aachen.de/raspbian/raspbian/pool/main/a/assimp/libassimp4_4.1.0~dfsg-5_armhf.deb  Connection failed [IP: 2a00:8a60:e012:a00::21 80]
E: Failed to fetch http://ftp.halifax.rwth-aachen.de/raspbian/raspbian/pool/main/g/game-music-emu/libgme0_0.6.2-1_armhf.deb  Connection failed [IP: 2a00:8a60:e012:a00::21 80]
E: Failed to fetch http://ftp.halifax.rwth-aachen.de/raspbian/raspbian/pool/main/libd/libdca/libdca0_0.0.6-1_armhf.deb  Connection failed [IP: 2a00:8a60:e012:a00::21 80]
E: Failed to fetch http://ftp.halifax.rwth-aachen.de/raspbian/raspbian/pool/main/g/ghostscript/libgs9_9.27~dfsg-2+deb10u3_armhf.deb  Connection failed [IP: 2a00:8a60:e012:a00::21 80]
E: Failed to fetch http://ftp.halifax.rwth-aachen.de/raspbian/raspbian/pool/main/libb/libbdplus/libbdplus0_0.1.2-3_armhf.deb  Connection failed [IP: 2a00:8a60:e012:a00::21 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?

Any hints what I could do now would be great… :slight_smile:

Try:
sudo apt-get update

If that works then you should be able to install as above. If not, looks like you are having issues connecting to the raspberry pi packages. Internet connection issue?

Yes, it turned out that my provider had issues yesterday. Rebooted the router this morning and the installation was quick and easy now. What a great experience!

:slight_smile:

1 Like