Overtweaked a FX device, etc. ... Dang. Clean.
Bitwig 2.0 - Functionality Discussion!
-
- KVRian
- 911 posts since 10 Dec, 2013
My favourite observations so far:
- 3rd party arpeggiators seem to be ridiculously tight now (like 48th notes at 140 bpm are bang on the grid) which bodes well for the midi engine in general!
- Realtime bounce, with choice of sample rate. This is awesome for stuff like bouncing down synths to create wavetables etc. where a specific sample rate is desired, without having to change project sample rate.
- Lots more keyboard shortcuts available (duplicate content, scale 50%, scale 100% etc.), though I still can't seem to insert new device at the end of the current track's plugin chain without using a mouse
- Timbre etc. seem to react instantly now. I used to have issues where I'd use e.g. timbre to modulate E-Hats decay but it always affected the next note, rather than the note I wanted. On that note, automation also seems tighter but not sure if I'm just imagining it.
- Have only had one crash on beta so far (been playing with it all day), which was 3rd party VST related. A couple of minor bugs here and there but the guys are responding extremely quickly on the beta bug group.
- GUI seems a lot faster with heavy projects now. I've loaded up a couple that are pretty much maxing the CPU and even though the audio breaks up sometimes, navigating the project is much smoother and there's less visible lag.
Plus of course all the stuff that's actually been announced!
- 3rd party arpeggiators seem to be ridiculously tight now (like 48th notes at 140 bpm are bang on the grid) which bodes well for the midi engine in general!
- Realtime bounce, with choice of sample rate. This is awesome for stuff like bouncing down synths to create wavetables etc. where a specific sample rate is desired, without having to change project sample rate.
- Lots more keyboard shortcuts available (duplicate content, scale 50%, scale 100% etc.), though I still can't seem to insert new device at the end of the current track's plugin chain without using a mouse
- Timbre etc. seem to react instantly now. I used to have issues where I'd use e.g. timbre to modulate E-Hats decay but it always affected the next note, rather than the note I wanted. On that note, automation also seems tighter but not sure if I'm just imagining it.
- Have only had one crash on beta so far (been playing with it all day), which was 3rd party VST related. A couple of minor bugs here and there but the guys are responding extremely quickly on the beta bug group.
- GUI seems a lot faster with heavy projects now. I've loaded up a couple that are pretty much maxing the CPU and even though the audio breaks up sometimes, navigating the project is much smoother and there's less visible lag.
Plus of course all the stuff that's actually been announced!
-
- KVRAF
- 1551 posts since 14 Feb, 2010
Ah man!!! Cant wait to feel/try this one... For me version1 feels not smooth at all.Hez wrote: - GUI seems a lot faster with heavy projects now. I've loaded up a couple that are pretty much maxing the CPU and even though the audio breaks up sometimes, navigating the project is much smoother and there's less visible lag.
It s so nice when a application is snappy and fast as lighting.
- KVRAF
- 37389 posts since 14 Sep, 2002 from In teh net
-
- KVRist
- 269 posts since 5 Sep, 2015
Is that part of track bounce / BIP or only on export?Hez wrote:- Realtime bounce, with choice of sample rate. This is awesome for stuff like bouncing down synths to create wavetables etc. where a specific sample rate is desired, without having to change project sample rate.
-
- KVRian
- 911 posts since 10 Dec, 2013
Track bounce!digitalfix wrote:Is that part of track bounce / BIP or only on export?Hez wrote:- Realtime bounce, with choice of sample rate. This is awesome for stuff like bouncing down synths to create wavetables etc. where a specific sample rate is desired, without having to change project sample rate.
-
- KVRist
- 138 posts since 10 May, 2015
They did make a point of mentioning at NAMM that automation is sample accurate now, doesn't seem like you're imagining it.Hez wrote:- Timbre etc. seem to react instantly now. I used to have issues where I'd use e.g. timbre to modulate E-Hats decay but it always affected the next note, rather than the note I wanted. On that note, automation also seems tighter but not sure if I'm just imagining it.
Man, it really needs to be the 28th already.
-
- KVRian
- 911 posts since 10 Dec, 2013
Haha don't get your hopes up too much, I've only played around for a day and maybe I'm imagining things. It certainly does seem to be the case though...codec17 wrote:Ah man!!! Cant wait to feel/try this one... For me version1 feels not smooth at all.Hez wrote: - GUI seems a lot faster with heavy projects now. I've loaded up a couple that are pretty much maxing the CPU and even though the audio breaks up sometimes, navigating the project is much smoother and there's less visible lag.
It s so nice when a application is snappy and fast as lighting.
-
- KVRian
- 1107 posts since 30 Jun, 2015
Bitwig fades finally!
However its still not as good as i thought it will be, also fades dont work for looping. Kinda disopointment but it wasnt in feature request either. It doesnt feel like bitwig thought through of to implement fades. Its tidious to work with.
Getting Track height awesome but also here bitwig didnt think through. Would love some option to set back to default etc. Check studio one reference for this. Much better.
Right click to remove is kinda ok but wished it worked as to remove multiple note by holding in the mouse button. Like this 'rightclick empty area, hold drag over notes to be removed. if notes not removed open up right click meny, if notes removed dont. If holding on note it can work as it does now have no issue with that. Combine both methods and it will be better then fl studios.
What i like Polysynth has saturations now and noise fm, drive, widthcontroll for oscillator detune, classic lfo offers per voise retrigg love it.
The modulators ofc.
I like the idea of cv but have no hardware with cv so for me its not something i will use.
The gui is better and smarter and i see it only as intial stage, will hope they add more to it, its smart, the toolbar offering up at right to transportbar can be customized depending if its a track selected, clip selected etc. that is really nice.
Flangers is ofc nice and its really easy to use but misses control for how many notch peak filters it have.
The visual for distortion plugin really makes eat easier to program same for blur. The eq could have had some more work.
Overall...
its small upgrade which i think could have some more thought through implements of functions. Some ideas dont look finnished. I think we might see better more ready implementation along the road
However its still not as good as i thought it will be, also fades dont work for looping. Kinda disopointment but it wasnt in feature request either. It doesnt feel like bitwig thought through of to implement fades. Its tidious to work with.
Getting Track height awesome but also here bitwig didnt think through. Would love some option to set back to default etc. Check studio one reference for this. Much better.
Right click to remove is kinda ok but wished it worked as to remove multiple note by holding in the mouse button. Like this 'rightclick empty area, hold drag over notes to be removed. if notes not removed open up right click meny, if notes removed dont. If holding on note it can work as it does now have no issue with that. Combine both methods and it will be better then fl studios.
What i like Polysynth has saturations now and noise fm, drive, widthcontroll for oscillator detune, classic lfo offers per voise retrigg love it.
The modulators ofc.
I like the idea of cv but have no hardware with cv so for me its not something i will use.
The gui is better and smarter and i see it only as intial stage, will hope they add more to it, its smart, the toolbar offering up at right to transportbar can be customized depending if its a track selected, clip selected etc. that is really nice.
Flangers is ofc nice and its really easy to use but misses control for how many notch peak filters it have.
The visual for distortion plugin really makes eat easier to program same for blur. The eq could have had some more work.
Overall...
its small upgrade which i think could have some more thought through implements of functions. Some ideas dont look finnished. I think we might see better more ready implementation along the road
-
- KVRist
- 269 posts since 5 Sep, 2015
Very cool .. ThanksHez wrote:Track bounce!digitalfix wrote:Is that part of track bounce / BIP or only on export?Hez wrote:- Realtime bounce, with choice of sample rate. This is awesome for stuff like bouncing down synths to create wavetables etc. where a specific sample rate is desired, without having to change project sample rate.
- KVRist
- 217 posts since 26 Apr, 2014
I,m really loving 2.0 man. I have already finished and mastered 2 tracks for release on 2.0. It's alot smoother than i expected. I have only had 2 crashes since I've been using it with tons of 3rd party plug ins on quite a bit of tracks. Good job BITWIG team !!!!!! I also ported a few projects from 1.3.1over to 2.0 it seemed to work ok with just a few hiccups but they were minor !!!!!!!!
