The case for OP-Z expansion

Not satisfied with the OP-Z specs that TE has (partially) announced so far? Maybe there’s some hope in gaining extra functionality through its many forms of expansion—and I don’t just mean the modules. Let’s look at all the forms of expansion it has and what might be possible with each, starting with maybe least obvious but possibly the most promising one…

  1. The (iOS only, for now) app. When TE says the app contains “the OP-Z sound engine” and “dual-domain synthesis,” there’s nothing preventing the sound engine in the app from going beyond the OP-Z’s engine, right? Could TE permit it to take advantage of the phone’s hardware to overcome the processor and RAM limitations of the OP-Z? The three note polyphony limit on the synth tracks comes to mind. Speaking of, does anyone know if that limit also applies to the chords track on the OP-Z? What about the MIDI track? I assume that you should be able to sequence whatever you want on that track, no? Anyway, back to the app… On iOS, any audio that the app generates could be made routable (in separate tracks, hopefully) through Audiobus or inter-app audio and then could be made available to the multitude of music apps that support these standards for further processing. Same goes for MIDI data. And Ableton Link support for syncing and transport also seems like a no-brainer here. I’m surprised I haven’t seen anyone talking about this on the Audiobus forum.

  2. USB audio. Like a Roland Boutique device, it would be great if the OP-Z audio tracks could be sent down the USB cable and received by a computer. I guess there would have to be some kind of audio interface circuitry for this to work and space sure is limited in the OP-Z’s case. Going beyond what a Boutique offers would be iOS support for that audio interface, not just computer support. That would make it possible to do the routing described in 1) without the need for “dual-domain synthesis.” Perhaps latency might be an issue though?

  3. USB device access. It’s nice to know that samples can be loaded via a computer by copying files manually, but what if you could connect directly to an OP-1 and transfer samples through some kind of tight software integration? So far, I haven’t heard a lot from TE about what will be possible when connecting an OP-Z to an OP-1.

  4. Bluetooth. Given the limited number of ports on both the OP-Z and smartphones (I’m looking at you, Apple!), it’s nice to see TE using Bluetooth, not only for pairing it as a controller, but also for transferring the 12-second sample files through the app. The question for me is how reliable will that be? In my limited experience transferring files to my Apple Watch over Bluetooth, the user experience hasn’t been that great. And would it make sense to support Bluetooth headphones despite the latency, if only to go completely wireless?

  5. 4-pole 3.5 mm audio “out” jack. Presumably that fourth pole would support audio in, like with Apple’s wired EarPods. Even though the OP-Z won’t do onboard sampling (all the more reason why I’m hoping the OP-1 integration is really tight), what about mix in or PO connectivity? Or will you need that MIDI and CV module to do that?

  6. Modules. How much bandwidth will the port (for lack of a better word) that connects the modules be able to handle? I wouldn’t hold my breath for a full-blown screen module, but would a sampling module be possible? I’m thinking of something like a cut down PO-33. Could that record and transfer samples to the device over the module port What about a second battery or a RAM or storage boost?

  7. Software updates. If nothing else, we’ll see probably see a handful of requested features (probably starting with any highlighted in a Sonic Lab review) added via software update since TE has a great track record of updating the OP-1 over the long term. Here’s hoping they update the OP-1 soon too.

What capabilities would you like to see added to the OP-Z via these expansion methods? And does it have other forms of expansion that I’m missing? Forgive me if my questions have already been answered somewhere else. It’s been hard to piece together all the info that’s floating around about what this thing can and can’t do.

Looking at earlier prototype pictures, I did see a ribbon cable sticking out of the unit that could be the connection point to the cartridge. If that is the case than you have that to work with as far as data/power bandwidth sharing.

about item 4. I would not be surprised to see TE sell a mic stereo splitter like the op-1 antenna. Made it look a little more slick than anything available on amazon and sell it for a premium.

on the topic of software updates and the op-1 the version of the manual online now has a couple places where it talks about firmware updates for sequencer and synth engine.

Personally I am happy they are not talking about this stuff. Let the dam thing come out and let them publish a manual. I would rather not know what is coming and when than have a repeat of the 2016 op-1 firmware release.

@kingof9x said:
I would rather not know what is coming and when than have a repeat of the 2016 op-1 firmware release.

I have a theory the OP Z evolved from ideas that started in the 2016 os update.
Initially they talked of two new sequencer and two new synth engines. All we got was Arp and Voltage, very late, along with Z talk.

Excited about control and cross platform for both though.

@Spheric_El said:

@kingof9x said:
I would rather not know what is coming and when than have a repeat of the 2016 op-1 firmware release.

I have a theory the OP Z evolved from ideas that started in the 2016 os update.
Initially they talked of two new sequencer and two new synth engines. All we got was Arp and Voltage, very late, along with Z talk.

Excited about control and cross platform for both though.

That timing makes sense and would provide a good explanation for the os delay.