OP-1 Update 2016

@jim I was too quick to post earlier, now I like your life strategy!

Ooo yah cuckoo’s videos are always great! looking forward to it.

Hey Operators

I was playing around with the beta the last couple weeks but now all presets in synth mode are gone. Drum presets are fine but in synth mode you only see the blue synth engines … the green presets are gone. Anyone experienced this?

do not press shift+T1.


try shift+1-8.

…how much more pleasures do we get @cuckoo buddy?
just the number of changes you recently discovered!
Software is a tricky thing.

Its hard to say when something will be done because there is an infinite amount of ways to do anything and some ways are better than others.

I imagine either TE isn't interested in keeping a strict release schedule and/or they are fighting some tricky development issues.

Additionally, new code can make something that worked fine previously, fail. You can spend ages reading each line to find out the mistake. That mistake might be a comma or a carriage return

do not press shift+T1.

try shift+1-8.

Aaarrrggh ... yep ... thanks. My fault. :D
Additionally, new code can make something that worked fine previously, fail. You can spend ages reading each line to find out the mistake. That mistake might be a comma or a carriage return

Coding is almost AI-assisted these days: the IDE will spot syntax errors immediately, autocomplete helps you pick variables and functions from lists rather than type them out; code may compile as you write, preventing errors only revealed at compile-time, some IDEs also train on patterns in your code and flag things that look suspicious; linting flags up known bad or messy coding patterns; templates spare you having to type boilerplate code over and over; automated tests catch things broken behind your back; that’s before you look at debuggers or simulators which are incredibly powerful. Give no company an easy pass just because coding is complex.


Coding is almost AI-assisted these days [ … rant … ] Give no company an easy pass just because coding is complex.

I don’t think you get the difference between syntax and semantics :slight_smile: But, if you are in possession of the legendary “do what I want” programming key on your keyboard, please don’t hesitate to press it all day long for the benefit of humanity in general. Or even have it press itself if it has that much of AI built into it.

Long story short: Non-standard software is difficult and DSP programming is pretty much as difficult as it can get these days. Especially since most “programmers” [1] have lost touch with the physical world. Unless you can prove it mathematically your code is also always prone to have bugs (again, syntax vs semantics). TINSTAFL and AI is still a long way from solving arbitrary problems.

Btw: I like your critical stance on the OP-1 and am happy that you sound the voice of reason in a few threads. I just feel this rant was a bit ill founded.

[1] If you want to we can discuss about this in great lengths but maybe on a separate thread?

Coding is almost AI-assisted these days [ ... rant ... ] Give no company an easy pass just because coding is complex.
I don't think you get the difference between syntax and semantics :)

Long story short: Non-standard software is difficult and DSP programming is pretty much as difficult as it can get these days. Especially since most "programmers" [1] have lost touch with the physical world. Unless you can prove it mathematically your code is also always prone to have bugs (again, syntax vs semantics).

To generalise about "most programmers" is a little harsh but so be it. I didn't mean for this to come through as a rant. I meant that code analysis tools, far beyond syntax, leave enough headspace to focus on the actual problems. I did not mean that code somehow mysteriously writes itself. A few code assist complaints of the kind I speak about: "inefficient usage", "X is redundant", "X is defined but never used.", "confusing syntax", "weird construction, is [keyword] necessary?", "undocumented parameter", "don't make functions within a loop", "possible [bug], probably missing [check]", and my favourite - "Y should probably not be assigned to X". Programming is hard, but TE's OP1 doesn't have to land on Mars, sequence your genome, or predict the weather.


Coding is almost AI-assisted these days [ ... rant ... ] Give no company an easy pass just because coding is complex.

I don’t think you get the difference between syntax and semantics :slight_smile: But, if you are in possession of the legendary “do what I want” programming key on your keyboard, please don’t hesitate to press it all day long for the benefit of humanity in general. Or even have it press itself if it has that much of AI built into it.

Long story short: Non-standard software is difficult and DSP programming is pretty much as difficult as it can get these days. Especially since most “programmers” [1] have lost touch with the physical world. Unless you can prove it mathematically your code is also always prone to have bugs (again, syntax vs semantics). TINSTAFL and AI is still a long way from solving arbitrary problems.

Btw: I like your critical stance on the OP-1 and am happy that you sound the voice of reason in a few threads. I just feel this rant was a bit ill founded.

[1] If you want to we can discuss about this in great lengths but maybe on a separate thread?

I quite like that “separate thread” idea.

please put in a mode for Audio-Out while in midi control mode! please.


would love to control for instance Analog Heat via midi from the OP-1 + listening to the OP’s massive engines. (same time)

https://www.youtube.com/watch?v=UX5oAZ1wsGE


…and i want to control the Organelle effects via midi mode while running op1 thru the Pi 3.

cheap cheap.

Coding is almost AI-assisted these days [ ... rant ... ] Give no company an easy pass just because coding is complex.

I don’t think you get the difference between syntax and semantics :slight_smile: But, if you are in possession of the legendary “do what I want” programming key on your keyboard, please don’t hesitate to press it all day long for the benefit of humanity in general. Or even have it press itself if it has that much of AI built into it.

Long story short: Non-standard software is difficult and DSP programming is pretty much as difficult as it can get these days. Especially since most “programmers” [1] have lost touch with the physical world. Unless you can prove it mathematically your code is also always prone to have bugs (again, syntax vs semantics). TINSTAFL and AI is still a long way from solving arbitrary problems.

Btw: I like your critical stance on the OP-1 and am happy that you sound the voice of reason in a few threads. I just feel this rant was a bit ill founded.

[1] If you want to we can discuss about this in great lengths but maybe on a separate thread?

I quite like that “separate thread” idea.

You two are more on topic than people’s feature requests/questions, Coukoo’s “paid by TE response”, or my tongue in cheek smart ass comments. You have provided more info about why TE delayed their firmware than they have.

You have provided more info about why TE delayed their firmware than they have.

I don’t really consider nearly groundless speculation “info”. Also not sure why feature questions would be considering off topic in a thread about the features of the update.


The update will be done when it is done. Haggling over why it’s not done yet doesn’t really have a point.

Constructive conversation about what we’d like to be in the update (some of which we know already from the leaked beta) seems a lot more pleasent a way to pass the time than bickering.

You have provided more info about why TE delayed their firmware than they have.

I don’t really consider nearly groundless speculation “info”. Also not sure why feature questions would be considering off topic in a thread about the features of the update.


The update will be done when it is done. Haggling over why it’s not done yet doesn’t really have a point.

Constructive conversation about what we’d like to be in the update (some of which we know already from the leaked beta) seems a lot more pleasent a way to pass the time than bickering.

This.

Yes I would like the OP1 to send midi CC from the knobs - would be great for using sequencer in OP1 to output midi note while controlling iOS synth knobs via OP1 knob MIDI CC

…with endless you can!! @dialecticsines

if you put a nice melody into endless seq. you are able to switch to midi mode by pressing shift + com and then T2 for ctrl.

sequencer is still running in this mode. but i think it’s just endless that works.

unfortunately you can’t change the CC number inside OP1 but they are sending straight 1-4 as CC. easy map it.


Wanted mono envelope for drum mode since the beginning, added to the already great drum envelope of course. I know lots of people don’t like the drum envelope as it is but I think it’s effing brilliant.

...with endless you can!! @dialecticsines
if you put a nice melody into endless seq. you are able to switch to midi mode by pressing shift + com and then T2 for ctrl.

sequencer is still running in this mode. but i think it's just endless that works.

unfortunately you can't change the CC number inside OP1 but they are sending straight 1-4 as CC. easy map it.


I think I’m in the minority, but I can’t get my head around endless. Without a visual grid (or the natural motion of playing to a live rhythm), I never can type in something w/ appropriate rests, using shift / arrows. Just can’t visualize it.

me neither but it makes it kind of fun not knowing what you’re gonna get