Hey, I got an OG OPLab (not the OP-Z module) a while ago… mainly for reasons of connecting ext. Keyboard to OG OP1 as mobile solution. I never went into the other crazy stuff you can do with it, and it seams quite full of hidden possibilities. Would like to get deeper into that. To me it seams like a brain of interconnecting all your stuff, never did CV or anything before. What are it’s features and what cool things are possible?
Thanks☺️
i was fortunate to get the TS-3 motion sensor (like the G-force accelerometer in the OP-1/field/Z) with mine and did a concert in August with the motion sensor triggering visual effects via a M4L patch sending CCs to the OP-Z running Photomatic short video clips! The gate input puts out MIDI note ons so i remapped those in the M4L patch so that the flutist’s foot switch would change random parameters of the videos as well!
Tinkered with the CV/Gate I/O a bit too.
Be advised that if you have the original OP-1, you would have to downgrade its firmware to 242 or earlier as the USB audio in 243 and later doesn’t play nice with the OPLAB. Same issue on OPZ but i don’t remember which firmware worked (used it direct from laptop running Ableton, so nonissue for me at least in the concert)
(No experience with it on OP-1 Field or XY)
HTH,
psound74
That’s a nice drop:smiling_face:![]()
think I will dig deeper into this.
The 424 thing loosing USB is sad, but can’t have everything…
True! Part of the OP-1’s mystique is making it work in spite of all its “limitations breed creativity” ethos!
Thanks for watching, commenting, and complimenting!
Best,
psound74
My gotcha was that the unit I bought had never had its firmware upgraded, so some modes that are mentioned in the documentation weren’t working. Or at least Mode 5. There was info about the new features in the release notes.
i use the oplab occasionally as a cv to midi converter to record sequences from a detroit modular du-seq to whatever instrument i want in ableton live. the du-seq is basically an un-quantised version of the metropolis (slider based sequencer, but un-quantised pitch). it works very well for this. either the op-lab sends the cv with pitch bend or ableton interprets cv and applies pitch bend accordingly. i imagine you can use it for other types of cv signals as well – to me thats the only practical use i’ve found for the oplab, but its a good one (mode 7)
edit bad example, but its un-quantised pitch (warning, loud). du-seq → oplab → ableton wavetable: https://drive.google.com/file/d/1_W5rG5JRKMlzVGgtVRlgkO-S5Bfz1pwb/view?usp=sharing
its probably possible to do the same thing but with the op-1 as the destination, but would require downgrading the firmware of the op-1, not a big deal imo, the firmwares are so easy to up-down grade
Is it just me, or does this little gem deserve its own new firmware update, too ?
![]()
![]()
Second that…make it work with base firmware 246 on the OG OP1 and we could have it alongside Hundekraft and OPUS…
Hopefully,
psound74
i had my robot do some low effort research into getting the og-lab working with fw version 246.
the robot’s best guess at the time was that after the op1 introduced usb audio, the op1 reports it’s usb differently and broke compatibility with the oglab — i did some cursory digging but got distracted by other things like effects and instruments. its definitely on my radar to revisit it though. if anyone happens to have an old og oplab firmware (older than 861) or has an oplab that has an older fw on it that they can dump, it might be useful in some way (might not either)
im thinking that unless the og oplab firmware can be modified to be compatible (syx), it could be risky to mess around with usb on the op1 itself. if you brick usb functionality you might risk not being able to copy firmware over again if something went wrong. it might involve messing around in te-boot too. it might not though, i’m just thinking out loud. maybe there are some usb functions present that handle these things after the op1 has fully booted outside of te-boot. maybe even then it could be a fw option or preference to switch between 242+ usb and previous usb (oplab compatible). i think its def worth investigating
oplab firmware is encrypted so unless someone figures out the key we can’t do anything.
The difference between 242 and 246 is different usb device descriptor. In the next release of op1r there will be an option of enabling the legacy behavior. I do not own oplab but it would be great if anyone could confirm that it works.
edit: it’s up, update to #69, go to CLOCK>T2, set oplab mode with white encoder, reboot
Oplab OS 859 beta maybe…
![]()
![]()
![]()