Are there any Oxi One users present?
Is it possible to launch a clip with MIDI in Bitwig?
I am trying to trigger clips in Bitwig using the Oxi One MK2 sequencer.
I know that triggering clips is possible via Driven by Moss, but I want to be able to trigger the clips on a step-by-step basis of the sequencer.
@ 2.06
I don’t think so without a script as this was my main gripe but that was some time ago!
A launch clip mode with all those pads would be cool - maybe something for next week new OS? All those square pads would be ideal for it!!!
Yeah, if this is possible some how, I could have elektron parameter locks in an Oxi sequencer. 
Hypothetical :
I think it is possible if I can get LoopMidi to work in Bitwig.
With LoopMidi it should be possible to launch a clip with midi notes.
Oxi One MK2 can send cc value per step.
CC value sends midi note via poly grid.
Loopmidi uses midi note to launch clip with OB data.
The cc value on Oxi per step = OB clip in Bitwig = Preset on Digitone = Sound lock for elektrons on Oxi sequencer.
Sorry, maybe I’m misunderstanding something but I don’t get why you need all that fancy stuff to trigger a clip with a midi note from the Oxi one, you can just use the midi learn function.
(EDIT: @Zelio beat me to it as I was testing.) 
@Hosanna Activating the Mappings Panel on Bitwig (the “finger” icon in the bottom right corner), one can map clips and scenes to MIDI notes. It is also possible to map the stop clip button to a note. This allows to create a basic clip launcher with any controller capable of sending MIDI notes, including the Oxi One.
Out of curiosity, I have just tested this sequencing notes and playing notes from the keyboard. It isn’t as smooth and feature-rich as using a proper clip launcher, but it covers the basics of launching and stopping clips.
I really like that i can zoom into one group, and edit only this group - helps for the overall overview - but now i want to edit my synth around a drum loop which resides in my drum group.
Is there an option to show only “pinned” tracked?
Presumably it wouldn’t light up the DAW clips available on the Oxi pad LEDs like a launchpad / Push etc so guess needs some development if wanting it done nicely as hard to ID which clip is which
I want to trigger a clip with a certain step from the Oxi sequencer.
This way I can trigger the OB data and have sound locks per step in the OXI sequencer.
Can you link a step in the oxi sequencer to a clip ?
I tried this method and I can’t link a specific step in the oxi seq to a clip.
I have the Oxi on loan from a friend, testing the waters.
You can’t link a step of the oxi one to a clip, but you can link a note of the oxi one to a clip, via the midi learn/midi mapping function in Bitwig. Then you play that note on a specific step to launch that clip.
Thats why i needed the cc conversion to note. To trigger the clip with cc data on specific steps.
For now I use the oxi sequencer with a launchpad to trigger the sound-clips.
Thanks for the tips !
Solution :
Mapping (the finger icon in Bitwig) a clip to a cc value (x,y,…). Send midi cc (x,y,…) on the desired step in the mod lane the cc (x,y,…) triggers the clip(x,y,…). The clip triggers OB data = sound lock (x,y,…), ect
Old news but new to me. Bitwig has really nice TouchDesigner integration apparently.
I’m not super familiar with that software but it seems like a good answer to finally doing some rudamentary scoring in bitwig.
Obviously TD can go much further. Anyone use it with BW?
I’ve only done some amateur / hobbyist scoring and I’m not trying to scale into a pro workflow or anything.
A bit of trivial information: I finally upgraded to 6.0.5.
Overall impression: UI is significantly faster. CPU consumption did not change or even decreased a bit.
New interface is really something… But also it became a bit too complex. Some things did not change much (like finding automations in a clip). Standard library got a couple of new macroses/grid devices. Looks great, but also reminds me the period of quitting the DAWs
I just upgraded to 6.0.6 after not using Bitwig for more than a year. In the intervening time, I had a Universal Audio interface and a lot of its associated plugins on my system, but I don’t have that stuff anymore. I thought I’d removed all traces of UAD from my system, but now this upgraded Bitwig pops up an endless cycle of notifications that it can’t find the UAD plugins. I never used Bitwig with with the UA interface or plugins, and I have again check through the plugins directory and verified that there’s no UAD material there. How do I get Bitwig to stop looking for or ignore UAD stuff?
I’ve tried:
Try deleting index folder as well:
/Users/your_username/Library/Application Support/Bitwig/Bitwig Studio/index (folder)
Also check /Library/Audio/Plug-Ins/VST3/ and ~/Library/Audio/Plug-Ins/VST3/, /Library/Audio/Plug-Ins/VST/ and ~/Library/Audio/Plug-Ins/VST/ for any UAD plugins.
It wouldn’t hurt to check in Bitwig → Settings → Locations → Plug-in Locations which locations are listed.
Additive synthesis experimentation with the grid and voice stacking
Does anyone know how I can set Bitwig up to receive relative instead of absolute values from a MIDI controller? I have tried all of the options in the CC Value Mode drop down menu in the controllers setting, but it still reads the incoming values as absolute.
I’m using the Faderfox EC4, and have tried both the CCR1 and CCR2 modes…
i wanna say via settings > controller
last resort, tho i do think the above should solve it, there’s always using bitwig’s scripting to do things you can’t outta the box.
edit: ah, maybe it’s not a thing ? https://www.kvraudio.com/forum/viewtopic.php?t=488163
I did some more fiddling around, and it turns out that the CCAh highres mode on the EC4 is recognized by Bitwig, so the relative modes are not really needed.
