Oh yeah, in Logic I have Z set to zoom in on a selected item, and then zoom back out, but I can’t do that in Bitwig. Trying to think if there’s anything else that comes to mind, but drawing a blank. I like having a one-bar advance key ( in Logic), a slice at playhead key (I have it set to / in Logic), and a slice at transients (called offsets in Bitwig) key, which is basically a quick and dirty break slicing technique I use in Logic. Sounding that out though, I probably would just do extra tracks.Īs for Logic stuff I’m missing in Bitwig, it’s mostly key commands and short cuts. I don’t use it too much, but could see doing something like putting in a fill/edit/turn around as an audio file so it cuts from the instrument’s MIDI to the audio, and still processing through the same additional plug-ins. The instrument doesn’t affect the audio, but any additional plugins are applied to the output of the track. So a hybrid track will allow you to have a plugin instrument on it, as well as an audio file on the actual track. Could you tell me more details about that “hybrid track” feature? I haven’t heard of it. Trying to think of other cons, will post more if I think of any. Version 2.4 has stuff I’m interested in, but now that Bitwig 3 has been announced for Q2, I will just wait for that. I waited a few months to update, did the 12-month sub, got updates up to 2.3.5, and I haven’t resubbed. Bitwig 2 introduced a subscription model for the updates. I do cause it to crash a fair bit with 3rd party plugins. Turning an instrument track in to a hybrid track is cool, lets you retain your synth settings, but you have the audio bounce on the track.Īt times I feel like you have a limited number of tools, compared to Logic, and sometimes I find myself trying to use a Logic key command, but for the most part I get along well in Bitwig. I think the programmer for the Surge synth is part of Bitwig, so one of the native synths has aspects of Surge in it. You get a good size library of sounds and presets. Add movement to different parameters and hopefully generate cool sounds. I think the modulators are a cool feature, seem to do many of the things possible with Max4Live. I have very limited Ableton experience, so I can’t really speak to that aspect of it. I still write in Logic occasionally, but most of the time I’m in Bitwig.įrom what I understand, some Ableton programmers left, started Bitwig, and created a new DAW that did not carry over a lot of the bloat from Ableton.
I was a Logic user, Bitwig 1 was bundled with an Arturia controller I bought, and eventually I tried it out, picked it up very quickly. Yup, I mainly use Bitwig, for the past three years. It punches well above its weight, and Live users will feel right at home. But if it were wiped off the face of the earth, I think I’d have very little problem switching to bitwig. It’s very much personal preference, but for some reason Live just feels more like “home” to me right now. AFAIK there is no other daw that does this straight out of the box. If I get a 24 out interface,I then have 24 different cv control outputs to send to the hardware.
I’m going to try this soon, after I get another audio interface. If you have any hardware synths, like, say,a modular even, that use cv, BW will actually send cv data out. The other thing that it has going for it is the unique cv control. The synths are strong, as are the rest of the effects, and it’s much cheaper than live suite. The skins and colors are different, but the workflow is virtually identical, right down to the arrangement/session views, and the way that you can chain and stack devices. Other than that, it is kind of a bizarro world clone of Live.
It outpaces Live in that regard: the modulation system is so easy and useful, and so many fun crazy modulators that can instantly be assigned to any property of any plug. I use it, sometimes, but mostly for sound design, cuz the modulators are truly out of this world.
0 kommentar(er)
