Oberheim TEO-5 Editor
TEO-5 Edit V2
I have added a 3rd Tab to the editor which gives access to some of the sequencer and a simpler editing page based on the SEM called the Semulator:
V2 includes the original V1 editor
 |
| Main Editor Page |
 |
| Matrix Mod and File Page |
 |
| New editor page giving you a simple 16 Step Sequencer and a SEM editor - the Semulator |
The sequencer is useful for recording and editing monophonic lines - might do a full polyphonic version but not sure I would ever use it. The Semulator is just a bit of fun and just gives you access to the same controls and modulators of the original SEM. It's best to start with a basic program and use it like a soft synth. Note that VCO1 and 2 are swapped around because on the original SEM VCO2 synced to VCO1 - on the TEO it's the other way around.
I got the idea for the SEMulator from my own Custom SEM - the SEMi Modular, another terrible pun! Sadly all that is left from FVS that I had back in 1978! Yes I am that old!!! I'm saving that story for another post.
TEO-5 Edit V1
Here is a basic editor for the TEO. Covers all the stuff that is under the hood. Built using CTRLR on a Mac running Catalina but should run on newer Macs as my other editors do. The PC Editor has been tested on Windows 7 and 10
The stand alone editor should work on newer M1 macs but the plugins are not compatible.
Latest news and info are in the comments section
 |
| Running on Windows 10 |
Setup
Once the Editor is loaded set up your MIDI devices
The editor uses NRPNs and Sysex to transmit and receive data so those these must be enabled in the TEO-5 Global Menu. Click on a Bank Number to load a bank.
I have added a Load Speed box in the Bank Loading section as the Mac and PC handle the messages in the MIDI Buffer differently. A load speed of 100 works fine with the Mac but you will need to set it to 200 on the PC. 500 slows the MIDI message transmission to 500ms which is very slow - but there just in case. When you load a bank the editor sends out 16 patch requests and then loads the patches. On the Mac I noticed the 16 messages went sent sequentially as a block then 16 patch messages were returned. On the PC with no delay only the first or second patch was received. The delay ensures that the TEO has time to send the patch data before it gets another request.
Comments