A compatible PD implementation of the Organelle UI for developing and testing patches without using the Organelle hardware.
Okay, I’m lazy. And sometimes I find it a bit tiring to always have my Organelle nearby, do the whole WIFI setup and then be able to work on my patches via VNC (which is sometimes a bit unstable).
With this Organelle UI (or simulator) it is relatively easy to work on patches without the Organelle. It’s even practical to use it on the Organelle because you don’t always have to look at the screen. Or even turn the buttons.
So it’s very comfortable. ;-) And of course I love to having attached all the buttons and knobs (don’t forget the screen) of a physical device to Pure Data.
However, it only works via the events sent by the hardware. So there is no MIDI support or anything like that. The notes are sent to “notes”, just like on the Organelle.
If something doesn’t work or is missing, just let me know.
Note: in the example patch there is an error in the initialization of the filter. As long as cutoff is set to zero, nothing can be heard.
Version 1.0 now supports MIDI to control the surface. Have a look to patch ‘midi-map’ for details. Just enter your control numbers into the route object. Check the print box to get informations when turnig your knobs.
In version 1.5 I added VST-objects for displaying a scope and a spectrum.
There is also a recorder now. Audio files (WAV) are placed in the OFD directory.
New to 1.6: I missed to send signals from [adc~] to inL and inR. Also I added a configuration file “analyzers.config” for scope and spectrum. Just put your preferred VST/LV2/etc. to that file. Line one is the scope, line two is the spectrum.
New to 1.7: Thanks to “another mother => [ltos]” (https://patchstorage.com/another-mother/) this Organelle now as a black screen.
/home/thomas/.vst/yabridge/JScope_x64.so
/home/thomas/.vst3/yabridge/SPAN.vst3
(Yes, my real name is Thomas)
Windows users might remove the current analyzers.config and rename analyzers-win.config to analyzers.config. I already put two VST to the directory. (Untested, but should work, if not let me know)
0.2: Expression is now working. Connection lost…
0.3: Damn, there was a spelling mistake in the demo
0.4: Encoder lost connection as well…
0.5: The display is shortened to 21 characters so that you can see whether the text fits on the organelle’s screen. The sliders for the knobs now have space for this.
0.6: Now Organelles notes sends value and velocity from external MIDI. Cleaned up some mess in the demo patch.
0.7: Corrected a misbehavior in the foodswitch handling. Now it should really be 100 percent compatible. Maybe next time I should test it better.
1.0: Added a MIDI map patch to control the surface.
1.1: Added toggle and bang for encoder, AUX and food switch. Added simple LED indication, so far without color…
1.2: LED now with color
1.3: VU for output
1.4: VU for input
1.5: Cleaned up all the mess, added VST for scope and spectrum (windows), added a recorder
1.5.1: Fixed initialization of cutoff frequency (dirty), record button now turns to red when recording, because red means recording…
1.6: Missed [s~ inL] and [s~ inR] from [adc~]; added config file “analyser.config” for analyser vst integration
1.7: Hurray, we have a black screen
If anyone has an idea regarding note on/off please let me know. There are only Bang and Toggle and neither are really suitable as keyboards.
Use a toggle and pass the toggle value (1 for note on, 0 for note off) with the note number. You’d need to change your default patch to do stuff with note velocity. Looks great!
Yes, that would be a possibility. But it would be a bit uncomfortable. My idea would have been to send note on when you click and note off when you release the mouse button. But that’s not possible because PD doesn’t provide anything like that.
On the other hand, who seriously plays with the Organelle’s keyboard? I have now simply added a “notein” which sends value and velocity to Organelles notes. Now you can simply connect a MIDI keyboard.
Been using this a lot, it really helps because i find it cumbersome to code directly on the organelle.
When i open a patch that has different graphics (like a mini keyboard with circles) instead of text lines, i get this message: “This patch requires OS version 2 or higher”.
Anyway to display the visuals properly ?
PD also knows graphic objects, but I decided not to simulate the Organelle OLED. That would have been a bit complex. The UI is therefore limited to the output of text. But I’m glad that you find it useful!