Unless they created a new kind of NKS kind of NI style. But I hate wrappers for VSTs. Which there was some wrapperless standard.
2 Likes
The two Show & Tell videos on the Fors channel are great deep dives into Opal. Lengthy, yes, but if you want you can easily skip to sections you want to learn about.
Have fun!
3 Likes
Even NKS is far from perfect, and I am a huge fan.
I think Ableton should concentrate on perfecting the Push interfaces for their own instruments. For example, adding the modulation shortcuts Wavetable uses to the other instruments would be welcome.
And full support for M4L, including custom graphics. We know nice graphical additions are possible (see, e.g. Wavetable!)
3 Likes
It would be huge if Ableton opened up the APIs for graphics on Push. Imagine any of the Fors devices with Push-native UIs!
The other thing that would be transformative for Push as a platform would be a framework for utilizing the pads. This is what could theoretically enable a “hardware Opal” – native waveform graphics and controls on the screen, and native step-sequencing on the pads, complete with p-locks.
6 Likes
Dare to dream - I am right there with you. 
5 Likes
I bet that this is coming. Giving that fors is concentrating on Live as a Platform(for now) they must consider Push. And as far as I combine bits and pieces from what they are saying I would bet they are on it. It just lends itself to be put on the pads. You can just translate all the functions to the mpe x y z pads.
1 Like
Agree. Maybe we should start a fund to purchase a Push 3 for Fors to support the process! 
2 Likes
If they not already got one.
Ableton is just nuts to not open up the M4L Api in Time for UI stuff and graphics. Do it now for gods sake😂 your product will explode…
2 Likes
I’m waiting to see if / when Ableton open up the push for full FORS. 
2 Likes
Any workaround for the midi mapping issue?
Can you map the controls to a M4L device like Multimap/pro etc then midi map that?
For Opal’s case, you can map the numerical values of all the separate standalone devices (Gem, Mass, Dust, Slate, & Void) to Ableton macros. From then, you can map the macros to your preferred midi controller.
I haven’t find any ways to map the Opal-Ctrl, but it’s still pretty handy to use it to save patterns, sound + modulators presets.
The only mappable objects in the main 5-tracks Opal device is the mixer’s track on/off.
Hope this helps 
6 Likes
If we could control Opal in Push like we do with Probability Pack included in Live it would be game over.
5 Likes
Made another Fors Opal Tactile video. It’s an experiment in progress I made to bring Opal into a more tactile environment. I do hope this experiment can shed a light to the knowledge on how to use Opal in a stable condition with midi controllers. Still going through trials & hiccups in maintaining a good balance of mapped macros and also CPU power. Might find more stuff to fix in the future. Also hoping it’ll get easier through future updates. Meanwhile, hope you guys enjoy this video.
4 Likes
Hi Anak, Thanks for showing how you use Opal. I notice that you have set up OPal Ctl and Mass in the same instrument rack. When I do that, I can’t map the Opal Ctl macros to any of the Mass Parameters, but the ableton macros do work.
If I put opal ctl outside the instrument rack containing mass, I can map opal ctl to the ableton macros and the ableton macros to mass and that let’s me sequence the mass macros using opal ctl.
Interested in your additional thoughts about the workflow.
You’re welcome, ktips.
Interesting, I actually did the same thing as you when I first started. In my case, the Opal-Ctl mapping do just fine inside the same instrument rack. I’m not sure if this can answer your issue. But maybe, try to drag Opal-Ctl inside the same instrument rack after you’ve finished mapping & see if it works. I did find tiny little issues when mapping things to Opal-Ctl. Sometimes the control name changed to a selected parameter, but did nothing at all when dialed.
Part of the reason why I mapped some parameters to my Opal-Ctl is actually to access the LFO capabilities. I like the fact that I can adjust different LFO parameters for each new pattern. I’ve tried using all 16 macros to map any of Opal’s device and used ableton’s LFO to modulate. It’s just doesn’t have the same flexibility as Opal-Ctl’s.
Hope this helps
1 Like
Hi Anak,
Thank you or your help and I worked it out. I needed to map the opal ctl macros to the instrument rack macros, and not map the opal ctl macros directly to the opal instrument macros, The order is a bit odd but appears to work fine now.
Much appreciated 
3 Likes
Oh cool. Kinda forgetting the fact that Opal-Ctl can map to anything other than Opal’s devices. Happy to know you’ve worked it out 
1 Like
Pardon me for sharing things out of the blue. I just found out something that I think is interesting. If you saved Opal as an ableton instrument rack preset, all the steps made inside Opal will also be saved. From then, you can carry over the pattern you’ve made to another live set project by simply dragging and dropping your saved rack preset to a track. It’s pretty convenient in a way that, you don’t need to always create new pattern every time you start a new project.
Hope this info is useful
16 Likes
Is there a way to sequence midi selected parameters with the CTRL app without having to input a trigger. I want to modulate stuff like a filter cutoff and delay time without actually triggering my vst to play a note. The way I currently get around it is to set the probability of a note to 0, but I’m lazy and was looking to take some steps out of the routine.
Does anyone know if it is possible to reset Opal-Ctrl’s (or Opal) sequencer while it’s running? I often have an odd number of pages so the sequences is not always aligned with my clips, but I’d like to be able to ‘reset/retrig’ the sequence when switching scenes.