#126

Indeed, loved it as a kid :slight_smile:

1 Like
#127

Okay, so, I just found out that Orac 2.0 running on a FATES board would incorporate the Norns system as part of its whole.

I am, frankly, gobsmacked and trying to wrap my feeble mind around this concept. I guess the best way to do it is ask some questions about how it has functioned for @TheTechnobear in his time developing/using it…

  1. Have you tried running all of these on an early FATES board?

  2. When running Norns with Orac 2.0, where in the chain does Norns fit? Is it top level and ORAC runs like any other script on Norns (albeit one that allows multiple scripts to run)? Or does the Norns environment run much like a single patch environment on an Orac 1.0 setup would (basically one link in the script chains)? Can one run multiple Norns patches under one blanket environment and one instance of softcut?

  3. what’s the difference in performance of Orac 2.0 running Norns between RPi models? Is there examples of the 3b and 3b+ not keeping up? I remember there being a discussion about possible fan placement in between a FATES and a Pi4 not really being a viable option at the moment.

  4. this might be answered by question 1, but, where does softcut end up landing in all of this? How does audio get routed around internally? With the complexity of Norns being so much higher than an organelle, I could see this getting complicated but extremely mind bendy and fun!

I totally assumed that Norns and Orac on a FATES would be an ‘either/or’ kinda deal and now my head’s spinning!! I have a million and 1 more questions, but I feel those might get answered when my hands are on it.

#128

Sorry I think you misunderstood me…

In fates there will be a menu that will allow you to run orac or norns ( or potentially other apps) so you can start and stop each - but you won’t be able to run them at the same time.

Perhaps fates will encourage me to look into deeper integration within norns , but I’m not sure at this stage - so many different ideas and projects, all competing for time and attention :slight_smile:

2 Likes
#129

Okay. This makes much more sense. Wow, for a second I could barely see straight! It was a pretty shocking potential revelation. Haha. This is far more understandable. In this case, potentially building 2 FATES, one dedicated to Orac, one to Norns seems like my course of action.

1 Like
#130

hey yall
quick question

is there a list of existing orac modules (or compatible organelle patches)? cant seem to find it here or on patchstorage

#131

There used to be one on the C&G forum, but not sure if it has been kept up.

#132

found on the c&g forum
thanks!

2 Likes
#133

Is what you found different than https://patchstorage.com/platform/orac/ ?

#134

i saw that earlier but its a few releases for various platforms with only a handful of modules

initially when i read about orac i vaguely recall ~50 individual modules (plus whatever new custom patches folks make with orac in mind)

if true that seems like a great feature and expected to see a list somewhere but couldnt find it

the google doc list is kind of what i was searching for but it’s likely out of date

#135

Do you mind sharing that?

I’ve been tracking all things Organelle and Orac since early days, and had a pretty solid process of testing new things as they came up and organizing into different categories and usefulness to me, but like many things, as soon as you put it down for a few months and new developments happen, I’ve struggled to keep up. Plus new platforms all over the place and half finished projects abound…

I suspect that https://github.com/TheTechnobear/Orac/wiki will be an eventual home to more info, but it looks like it’s still in its infancy.

I’d love a “source of truth” also.

1 Like
#136

try this

it’s actually seems more comprehensive than the pdf i found earlier

2 Likes
#137

there are some here https://github.com/adbrant/orac_dev/tree/master/orac/modules

6 Likes
#138

ok FANTASTIC

exactly what i wanted dude
thanks

#139

Thanks @glia & @martindunne!

#140

@glia there are 50+ modules that I created and include in the ‘base install’ - I did put a list somewhere in the C&G forum but cannot find it at the moment.

The orac category in patchstorage is relatively new so some of the modules are in the organelle category.

#141

https://docs.google.com/spreadsheets/d/e/2PACX-1vTLKrgYphakK8n1iLfxryQRmW-TQw60K8kPnY1DJOHKEp3wZtHpyccbZtcg-9mQS_cA9HGiQtskr2CZ/pub?output=pdf

2 Likes
#142

We have now started a WIKI for Orac documentation, and Ive included the list of modules in that wiki

Orac Wiki

Early days, but I hope the community can help build it out, in particular to help new users, and also some of the more advanced features of Orac… which can take a bit of digging to find :wink:

5 Likes
#143

so this should be available soon…

IMG_0307
IMG_03074008×2903 2.26 MB

Thanks to @Gerald_Stevens providing me with a terminal tedium to make this possible… wouldn’t have happened without his support :beers:

9 Likes
#144

Holy crap!!! I can’t believe you did it with those darned I2C screens!

2 Likes
#145

and its up …
a little instagram tease : https://www.instagram.com/stories/highlights/17908256641403430/

download:

ORAC for Terminal Tedium

Status: Alpha release

Requirements
Terminal Tedium running FATES (though others should work fine)
2 x SH1106 OLED displays, using I2C on 0x60, and 0x61

Installation:
This has been tested on a terminal tedium running the FATES install.
it should work on others, but the idea is to have a base line install

(basically, the install assumes a user called ‘we’, so create that an should work on other distros )

defaults:
hostname: norns
username: we password:sleep

the general install of this should work, the only two modifications were made
a) disable encoders and screen in /boot/config.txt
just comment out the line that says something like
dtoverlay=fates-buttons-encoders
dtoverlay=fates-ssd1322,rotate=180

b) disable norns
sudo systemctl stop norns.target
sudo systemctl disable norns.target

c) i rename host to tt, but thats optional!
use raspi-config
(you can also setup wifi and expand fs whilst here)

then reboot

from here we can proceed to install orac
(note: you will need internet access to install things like PD which is a dependancy )

unzip orac.deb.zip , and copy orac.deb from your desktop to home directory of your TT.

then

sudo apt-get update
sudo apt-get install ./orac.deb

Running

once installed, it runs as a system service which is already enabled, you can stop with
systemctl stop orac
(use journalctl to check logs)

if all is installed correctly, you will hear a ‘demo’ patch, and see the display

(note: this guide does not cover Orac usage, see my videos for how to use orac :))

On the top display we have the ‘menu’
on the bottom display we have the paramters for the current module/page

the black buttons are up/down , the led button is ‘func’

when func is unlit, buttons are used to target parameters display
up/down change pages within module
func + up/down change module

hold func for 1 second, will light func, and we are not in menu display mode
up/down - selects menu item
func - selects item (either activating, or entering sub menu)

CV 1,2, 4 & 5 control parameters 1-4 respectively

tips:
cv clock module - allows you to input and output gate - replace normal clock in S2!
cv note module - can be used for cv/gate from spare cv and digital inputs
audio input - is disabled by default, go to the router (S1) and you will find a parameter to increase ‘gain’ for input on a chain.
midi is supported, you will need to setup alsa midi to connect to PD, using aconnect

have fun, happy patching

TheTechnobear

I think probably support all be on muffwiggler , given thats where I think most TT users hangout.

topic: https://www.muffwiggler.com/forum/viewtopic.php?f=17&t=104896&p=3199569#p3199569

3 Likes