I think 6 will come in the summer, while they might add a device / grid modules or two to pad the time between 5.3 and 6 for Superbooth.
They need to add something that’s standalone, without impacting the overall app that’s shifting underneath in the meantime. So device(s) - instrument, fx, grid module - would be ideal.
Are you talking about the OG Digitone ? How many parameters are you automating approximately ?
Asking because I use to experiment a hella lot of lags from DN while modulating 10+ parameters via direct MIDI, curious to know if it handle it better via OB.
Extra interrogation : did u use anything to accelerate the “printing” of the automations or did u writed them one by one ?
I don’t automate. I use static values in OB mode.
1 I choose a preset (A)
2.write arranger automation ON
3.turn some knobs on the DN
4.record audio and automation from OB.
When i find a nice ‘sound’ , I let the automation record for 1 bar, now I have static automation = A1 = variation on sound A.
I keep making variations on A.
I insert cue markers to know were to copy paste to the clips.
I copy and paste to the clips so I have A1, A2,A3,…
Now i can ‘launch’ the variations of the sound A via cliplauncher.
It’s like sound locking but with clips.
I can also alter the sound, or totaly destroy it, then choose another clip, press a *hotkey to ‘restore automation control’ → this way the altered sound and the path to the sound (the automation) is saved and can be used later. And the original sound is back to normal.
All this is without note or gate information, currently I’m sequencing via the grid.
The possibilities are endless, note and gate information, non-static automation/clip, extra envelopes,…
I cut the automation (the blue OB line) and give the sound a clip color (purple) Then copy the sound to the clips. A clip contains the OB static automation = sound.
Now you can play the clips and record in arranger.
This is all static. Much more is possible if you record OB automation live twisting the DN knobs, cut and copy to clips. With this the sound changes throughout the length of the clip.
There is a way to record BW automation automated via BW lfo’s and paste this in the clips but I need to streamline this or find another way (Button that activates LFO, LFO automates OB parameter, LFO ON is recorded,…)
Cv clip launching. Automation from BW recorded as audio.
Expert sleepers ES9 as audio interface. Sends CV = Audio.
The recorded modulation from BW is clip launched .
It is possible to apply all applications on audio to cv = audio.
I think I’ve been back in Ableton too long as forgetting some basics and struggling with MIDI Program Change.
I set program change for my synth for Scene one clip and all is fine, I change the program change for Scene Two to a different program change number (for a diff patch on my synth) However this also changes Scene Ones Program Change to the same number. I can’t give them unique PC number per clip?? Guess I am doing something very simple wrong.
Anybody here having luck with combined device (Audio interfaces) on the latest 5.3?
I have set it up in Bitwig (not tried it previously) but can’t get any inputs into Bitwig working on my TX-6 as the secondary device. If I choose the TX-6 as its own interface the signal inputs metres on Bitwig work fine so its not the device itself
Fixed it - I noticed in combination mode the Mac OS Microphone Mic icon was flashing like crazy in the top right tool bar. It was on Voice isolation and it didn’t like it. Switched to Standard and all is working. Not quite sure the logic of that is but hey ho
Glad you got it sorted. It’s a favourite feature of mine in this Bitwig update, I had already been using an aggregate setup but it gets messy when you have three or four different devices on there, this is much more elegant.