I love the new operators, I feel like they fit bitwig's "modular" style environment very well. Just a week ago I was wishing I could do conditional triggers for midi notes it really helps to be able to say "play this note once every 4 cycles" rather than expanding out a loop 4x just to add one note to the timeline given all the modulators, and midi devices, this is just one more way you can do procedural generative melodies in bitwig, you can pretty much program out a whole track in a single messure clip now added to that the note repeat with curve editing will allow for amazing creative rolls and fills, I keep saying this, but I truly feel like the new operators will allow for some new and revolutionary music to come out from Bitwig users. I always enjoy seeing your insight on bitwig updates, keep up the great work
The randomization features of Bitwig are probably the main reason it's my home DAW! I use them for generative ambient composition. So to me, Operators are a huge huge thing, and fit in absolutely with why I love Bitwig. I also know many many people have been clamoring for comping for a long time. Each version of Bitwig seems like an incremental foundation, deceptively simple in the beginning. That's why Bitwig has so much depth built up within it over time.
Great communication! I really liked all the context for where the new features fit within the existing system. That helped me understand what "operators" actually are.
Great feature & great video! Thanks!! :) I'd love to see them adding some new stuff in 4.x to Operators: - one that randomly selects different take from available comp lanes - added probability to Repeats, so that the note/event sometimes will repeat, sometimes won't - one that would randomly generate additional notes in parallel or in sequence to selected note, to form a chord/strum
Ableton import is great for integration with some drum machines Eg. I think the Akai force and new MPC’s, some iOS apps and the current electribes can “export to ableton” You start a track on one of these units and as you get further along you can multi track export to ableton to polish the idea / finish the track. Without needing to manually render every piece to audio and line that all up. Now you can take that generated ableton project from these hardware devices and open it in bitwig!
I could imagine, this is very helpfull for beats..I am experimeting in getting more variatons into delay loops and mixing in small tripple steps etc..probably, this things here will contribute to that too, as long as I let it control from a midi track. Wonder if I can substitute some of the stutter vsts I have in use? Thanks again for this detailed tutorial, I like your slow, clear, precise tutorial style-the one on bitwigs page confused me completely and was fast extremely fast paced. Overall, with automatism I always feel a bit unconfortable about loosing transparency-very nice that this can be „printed out“, it brings back some of the control, when needed 🙂
Comping-0% (interest for me. great for others who want it) Operators-10% (was doing all of this anyway with devices and modulators) Ableton ALS-load-50% (lotta old .als to play with, makes collab with ableheads easier... but it only gets you half there-no device settings translation) Apple Silicon-20% (I have an macminiM1-bitwig runs perfect already non-natively) ----->chance of me renewing from 3.2 = 0% but I am still 100% bitwig. I guess (I hope) that features like comping are stuff that will attract more users/money to Bitwig so they can set more resources into developing things that I actually would want.
For me Comping is really awesome, I mean only two DAWs that have it :) and Bitwig has it in version 4, other than that, who knows what else it would add in the upcoming versions :))
Comping is available in far more than two DAWs. Pro Tools, Logic Pro X, Studio One, Bitwig, Reaper (These are just off the top of my head, I’m sure I’m missing a lot). Also Bitwig is only enabling Audio Comping. There’s not MIDI comping or even just Clip Comping (Like how a track can be a hybrid track)
1. no real input recording to save CPU using effects like autotune instead placing that hog on every track 2. no ARA or their own 3. export mp3 METADATA 4. detect chords or anything close
I love the new operators, I feel like they fit bitwig's "modular" style environment very well. Just a week ago I was wishing I could do conditional triggers for midi notes
it really helps to be able to say "play this note once every 4 cycles" rather than expanding out a loop 4x just to add one note to the timeline
given all the modulators, and midi devices, this is just one more way you can do procedural generative melodies in bitwig, you can pretty much program out a whole track in a single messure clip now
added to that the note repeat with curve editing will allow for amazing creative rolls and fills, I keep saying this, but I truly feel like the new operators will allow for some new and revolutionary music to come out from Bitwig users.
I always enjoy seeing your insight on bitwig updates, keep up the great work
Wow, if I'm getting this right, you can make an entire song with a four bar loop using operators, and it can get as complex as you're willing to go.
Thank you for taking the time to explain these new features. Bitwig is certainly going from strength to strength.
The randomization features of Bitwig are probably the main reason it's my home DAW! I use them for generative ambient composition. So to me, Operators are a huge huge thing, and fit in absolutely with why I love Bitwig.
I also know many many people have been clamoring for comping for a long time.
Each version of Bitwig seems like an incremental foundation, deceptively simple in the beginning. That's why Bitwig has so much depth built up within it over time.
Great to have you back, Kevin! 🐱👤
Great communication! I really liked all the context for where the new features fit within the existing system. That helped me understand what "operators" actually are.
Very clear run through - thanks!
Great feature & great video! Thanks!! :)
I'd love to see them adding some new stuff in 4.x to Operators:
- one that randomly selects different take from available comp lanes
- added probability to Repeats, so that the note/event sometimes will repeat, sometimes won't
- one that would randomly generate additional notes in parallel or in sequence to selected note, to form a chord/strum
Great video, it helped to reinforce some of the workflow with operators. Thanks!
Great video always love your content! I noticed at 15:08 when you sliced the notes by repeats it didn't preserve the velocities, I hope that's a bug.
Yes Looks like it is a bug, but that is to be expected with Beta software. Bitwig is good about fixing all that stuff before release.
Ableton import is great for integration with some drum machines
Eg. I think the Akai force and new MPC’s, some iOS apps and the current electribes can “export to ableton”
You start a track on one of these units and as you get further along you can multi track export to ableton to polish the idea / finish the track. Without needing to manually render every piece to audio and line that all up.
Now you can take that generated ableton project from these hardware devices and open it in bitwig!
Good point! Thanks for your comment!
Is there a way to modulate the operator features in the side window?
Bitwig is very innovative!!
I could imagine, this is very helpfull for beats..I am experimeting in getting more variatons into delay loops and mixing in small tripple steps etc..probably, this things here will contribute to that too, as long as I let it control from a midi track. Wonder if I can substitute some of the stutter vsts I have in use?
Thanks again for this detailed tutorial, I like your slow, clear, precise tutorial style-the one on bitwigs page confused me completely and was fast extremely fast paced.
Overall, with automatism I always feel a bit unconfortable about loosing transparency-very nice that this can be „printed out“, it brings back some of the control, when needed 🙂
Side note: Just seen in an video from Taché, the probability/repeatability operator also work with Samples- even better for anything around beats! :)
All we need is Digitakt import now :)
Comping-0% (interest for me. great for others who want it)
Operators-10% (was doing all of this anyway with devices and modulators)
Ableton ALS-load-50% (lotta old .als to play with, makes collab with ableheads easier... but it only gets you half there-no device settings translation)
Apple Silicon-20% (I have an macminiM1-bitwig runs perfect already non-natively)
----->chance of me renewing from 3.2 = 0% but I am still 100% bitwig.
I guess (I hope) that features like comping are stuff that will attract more users/money to Bitwig so they can set more resources into developing things that I actually would want.
Pretty much feel the same but... and it’s a big butttt... things might Change! U might end up recording them vocals etc. so see how things go
Is Bitwig 4 multi-touch capable?
Yep
For me Comping is really awesome, I mean only two DAWs that have it :) and Bitwig has it in version 4, other than that, who knows what else it would add in the upcoming versions :))
Comping is available in far more than two DAWs. Pro Tools, Logic Pro X, Studio One, Bitwig, Reaper (These are just off the top of my head, I’m sure I’m missing a lot). Also Bitwig is only enabling Audio Comping. There’s not MIDI comping or even just Clip Comping (Like how a track can be a hybrid track)
this shouldn't been a version 4
With the way their upgrade model works it doesn't matter too much
1. no real input recording to save CPU using effects like autotune instead placing that hog on every track
2. no ARA or their own
3. export mp3 METADATA
4. detect chords or anything close
they should of kept this as being a later version of Bitwig 3 then they should of had waited untill they have better things to introduce Bitwig 4
@@mello6468 exactly...bitwig dope but its seems they not trying to do important things for vocals....especially ARA. comping tool dope dow
@@mello6468 they did add export Mp3