Hey! I’m not sure what I did wrong but I keep getting stuck on the ETC screen then the OLED either gets stuck on the mother loading screen or the HDMI switches back to the main edit screen you get when you normally plug in the organelle. I uploaded the install log on dropbox but I’m downloading the 2.1 file to flash to the SD card and see if that works. Also I think I installed the mother file before the OTC install (misread instructions, not sure how to undo install) if that makes a difference? If that’s the case would I need to format my usbdrive then reload all the system data/patches/etc or can I uninstall/reinstall OTC another way? Thanks for any help!!
in dropbox you need to create a link for others to access… (see share link)
it shouldn’t matter too much which order you install things in. but make sure you install everything as per original post
Hey All,
New to the forum! I was wondering what would need to happen to get this working on Organelle M?
Ive had a few questions about when this might be available on the organelle-m.
so its two stages for me to do this:
- get it working on my organelle-m, resolve any issues
- make installer, and test
given number of requests, I started having a look at step 1
OTC_Web seems to work ok,
OTC_Install needs rewriting (as per step 2), and Im collecting together info on this as I do step 1
OTC_Mother… Im hoping for minimal changes in this
current status: I can get OTC starting in an xwindow, some modes seem to work fine, others are crashing (due to free type?)
there are 3 technical issues I need to resolve.
a) move to using console , setup boot env (?)
b) freetype2 - seems not to initialise.
c) sound capture - cannot set sample rate
so still needs a bit of investigation to complete step 1…
step 2, is straightforward, but a bit time consuming.
Im away for next week or so, and then I have a another project i need to work on.
if that goes ok, I’ll take a look at the beginning of feb.
5 Likes
Dear @thetechnobear
I can not get my OTC to work on my Organelle. It just worked fine, but when I now start OTC I am stuck on Organelle screen:
running OTC
modes: /usbdrive
On monitor: ETC logo
mother.log says:
start otc mother
init fb0
start splash
start python
Traceback (most recent call last):
File “otc.py”, line 3, in
import pygame
ImportError: No module named pygame
What´s also strange is, that the video output of the organelle always seems 1080p60. I thought OTC needs 720p to run? Can I change the video output somewhere?
What can I do?
Thanks.
Andre.
EDIT:
wiped the card and installed everything from scratch. Works now again. Organelle now runs in 720p again. Not sure why, but it worked to reinstall.
1 Like
Hey everyone, I’ve been really enjoing OTC. I have a couple of questions regarding MIDI functionality, this is coming from someone with a very shallow understanding of MIDI in general so sorry in advance if this is all a bit too obvious or has been explained before.
My main issue is how to get the organelle (OTC) and my computer connected, do i need a Host-to-host MIDI interface? I would want to use ableton live to automate different parameters of otc with CC messages. What’s the simplest way of doing that?
@nthirteen - odd that error means pygame was not installed.
yes, its 720p…
this is ‘fixed’ in the boot config
BUT the reason is because all the modes and so etc code are pretty much hard-coded to 720.
theoretically you could change it, but then none of the ETC modes would work - so not really worth it - imho
@asosawelford - so this is not an OTC specific issue.
if you search on the forum for how to connect the Organelle to a DAW then you’ll find some topics 
your are correct both Organelle and a computer are usb hosts,
there are a few ‘host to host’ midi interfaces out there
Ive used this one as its cheap and simple.
however, if you have more midi devices and also after a midi router - look at iConnectivity they have some great routers that include multiple usb host support.
as for automating OTC, so it accepts the same CC and note messages as the ETC , so check out the ETC manual on the C&G website.
I also made it possible for modes to be coded to respond to arbitrary CC messages. using the etc.midi_cc array.
(also notes status can also be read from etc.midi_notes)
2 Likes
Clear as day! Thanks Mark, youre a genius
Hi Mark, does the OTC 1.5 work with OS4? Is it still the same described process?
- copy install files (zop): OTC_Install.zop + OTC_Mother.zop to patches directory
- install OTC_Install.zop first
- install OTC_Mother.zop
Currently I’m using all my patches on the SD card + the USB stick as a backup. That way, if I need to use one USB port, I can uplug the USB stick and still being able to use the patches? Can I install the OTC ETC only on the USB stick? or on the SD or on both?
What if I need to uninstall it then on either the SD or the USB?
Many thanks,
Nicolas
hmm, should work… nothing has really changed in this area.
the ‘core’ of OTC is installed on the SD card (from OTC_install), as it installs things like pygame, and various other dependent software.
OTC_mother could be installed on both, as could modes (iirc).
that said, i only ever use the sdcard these days,
if i wanted to ‘back things up’, id keep backups on my desktop computer - much more reliable than a usb stick 
(and frankly, in the very unlikely case the sdcard fails - your organelle probably wont boot, so your usb stick is not going to help you )
if you really wanted to be very safe e.g. for gigs, i think id be tempted to have a spare sdcard… but I dont think ive heard of any tales of sdcards failing on the organelle.
Been experimenting lately with OTC - I’m trying to get stereo working with it and some confusion here. I see this in the etc_system.py so am thinking I have version 1.5 installed, but I was confused on where to check this officially.
etc.audio_in
etc.audio_left
etc.audio_right
In any case I have a stereo signal going in, while running otc, but both input level bars on the organelle screen are moving equally with any sound from either channel.
I’m also wondering if only certain modes work with stereo, and if so, is there a place to find these “stereo modes” on patch storage?
If anyone can help, Thank You! 
so etc.audio_in is what the ETC has, since it has a mono input.
I added audio_left/right as ‘extras’ , but there are no modes from c&g using it, since it would be incompatible with the ETC.
theorectically, the eyesy could have these added, since it also has stereo input.
however, the code base for eyesy currently does not have these, it still has just audio_in.
so for now, if you created a mode using these it would only be compatible with OTC.
note: its possible in python to check to see if a variable exists (dynamically), so you could code a mode to use these ONLY if they exist… and so make compatible with eyesy/etc
1 Like
Ok - but the fact that I’m seeing both L and R signals as affecting both input meters equally on organelle screen is not an indication of a problem, correct? So if I created a mode that used the stereo input, then I would see the meters moving independently? Surprising there are no stereo modes on patch storage! Thanks again
1 Like
no - its just UI - the vumeter is just because I only calculate the peak once… I should do it for left/right independent.
yeah, stereo is a very useful dynamic for graphics
1 Like
I am curious if anyone else has experienced latency between audio input and the response on OTC. I’m seeing over 100ms delay and wondering if there is a problem with mine or if this is normal and it’s just not meant to work for things where one wants low latency response.
Just want to be clear that this is not meant as a complaint - I still love it and use it for things that are less time sensitive, but if this isn’t normal maybe I should reinstall or look into what could be causing the problem.
I can’t say I measured the response time
(how did you measure it … your measuring may add some overhead, if its using something like a LDR)
technically there are two parameters that control this… (well max latency)
audio input is read at a sample rate of 8000 with period (buffer) of 300 samples,
max latency = 37.5ms
then the image generation is capped at 30 fps,
max latency = 30.3 ms
(note: you may not get 30fps depending on mode, you can see this in the info screen)
so thats 70.8 ms, then whatever hardware latency we have on top of that…
Id only expect a few mSecs…
so Id think it’d be around the 75-80mS,
but thats just looking at the code…
you could edit the above :
sound.py has the sample rate and period size for the audio settings.
otc.py (or etc.py on etc) has maxfps for screen refresh rate.
of course, these values were chosen so that cpu load could cope with graphics generation.
upping maxfps won’t harm anything, it’ll just allow it to go faster if possible - but won’t in itself reduce latency. (so if fps on info screen is not fixed firmly at 30fps, its not going to help 
)
changing sample rate/period will have quite a large effect - but it will also hit cpu, and so if you end up dropping fps… then you wont have gained anything
Hey thanks! Glad to know it seems like there’s not a problem.
I’ll admit my measurement wasn’t extremely technical so could be 75-80ms yeah.
I came to the conclusion that I should just get analog video synths if latency is bothering me. I seem to be extremely sensitive to this stuff - I have the same issue with video games and can’t bear to play on an emulator even if the latency is as low as 5-10ms haha.
Hi all! Just got an Organelle M and am wondering if there is any way to use this on my device? I’m aware that the Eyesy can be set up with a sd card which is great there’s a work around to get visuals on the M. But I find switching sd cards to be a bit clunky. I tried installing the OTC through following the instructions, and my Organelle gives me an error stating that the OTC is only available on the Organelle 1. Thanks!