Bitwig 3.1 announcement

[stufflin]

Yes also really fun!
I really like the update.
I cant get the Micropitch to do anything though. I dont hear any difference. Haha. Maybe my ears arent finetuned enough.

It only works with bitwig synths and MPE synths with MPE enabled.
Also a lot of the scales are very subtle, if you want to check it’s working dual in some big nasty scale changes
[/quote]
A really? Will try! Thanks SLiC!

[Trancit]

Thanks for adding midi chase. That's one deal breaker crossed off the list.

You noticed that it only works if more than 50% of the note is left to play...

Tbh that´s a showstopper to me... for me, it´s not really crossed off the list... I do not know any DAW having any restrictions with chasing notes... well now I know one: Bitwig...

[stamp]

Thanks for adding midi chase. That's one deal breaker crossed off the list.

You noticed that it only works if more than 50% of the note is left to play...

Tbh that´s a showstopper to me... for me, it´s not really crossed off the list... I do not know any DAW having any restrictions with chasing notes... well now I know one: Bitwig...

It works if only half a measure is left to play and not 50% of the note.

[Broken]

Thanks for adding midi chase. That's one deal breaker crossed off the list.

You noticed that it only works if more than 50% of the note is left to play...

Tbh that´s a showstopper to me... for me, it´s not really crossed off the list... I do not know any DAW having any restrictions with chasing notes... well now I know one: Bitwig...

I haven't tried it. I still haven't registered my Bitwig license.

Bitwig still needs to sort a few deal breaker areas before I can use it as a main DAW. I thought they'd sort them out fairly quickly, but I was wrong.

[Broken]

Thanks for adding midi chase. That's one deal breaker crossed off the list.

You noticed that it only works if more than 50% of the note is left to play...

Tbh that´s a showstopper to me... for me, it´s not really crossed off the list... I do not know any DAW having any restrictions with chasing notes... well now I know one: Bitwig...

It works if only half a measure is left to play and not 50% of the note.

Seriously? That better be a bug.

[xx JPRacer xx]

Wrong, it's half of a whole note, not 50% of a note. I said it earlier. A 2-bar note will play at 2.3 but not 2.4. (or a 4-bar note will still play at 4.3 but not at 4.4).

edit: like stamp said.

[Trancit]

Ok, that I misunderstood... nevertheless why restricting it???

[Hez]

Ok, that I misunderstood... nevertheless why restricting it???

I assume it's so you don't get drum hits/rhythmic elements hitting out of time if you're editing a very rhythmic sound, rather than e.g. a pad or drone. I'm not sure I agree as an implementation but I can see what the rationale behind it is.

[u-u-u]

Ok, that I misunderstood... nevertheless why restricting it???

I assume it's so you don't get drum hits/rhythmic elements hitting out of time if you're editing a very rhythmic sound, rather than e.g. a pad or drone. I'm not sure I agree as an implementation but I can see what the rationale behind it is.

So if enabling this option one should keep in mind not to draw in long notes for percussive elements (e.g. a one-bar note for a crash on beat 1 would trigger the crash in the middle of the bar).

[M-Prod]

I played around with 3.1. I was really waiting for the note chase and so far it works good. Don't know what they mean with half note. It seems more like one beat threshold which is fine with me.

But for the rest it's super buggy. Have had several crashes with an existing project that was fine in 3.03 and now that I want to open my project (that I saved in 3.1) in 3.03 I can't because it said "invalid document version". Bummer: back to the backup (great function!).

I know it's beta, but I would expect issues with the new functions not with regular actions.

[M-Prod]

correction: I can't open ANY bitwig project in 3.03.. all of them state "invalid document version"...
Erasing the preferences file did not solve this.

Also there are issues with the VU meters not showing anything on some tracks within groups.. When I drag the track out and back in the meters work but the track seems a bit louder than before..

Oh and the ui is not sharp when it is not full screen (see screen shots)

This is the buggiest version I have experienced so far..

PS I always report my issues to bitwig and I'm very pleased by their level of support.

[Trancit]

Ok, that I misunderstood... nevertheless why restricting it???

I assume it's so you don't get drum hits/rhythmic elements hitting out of time if you're editing a very rhythmic sound, rather than e.g. a pad or drone. I'm not sure I agree as an implementation but I can see what the rationale behind it is.

So if enabling this option one should keep in mind not to draw in long notes for percussive elements (e.g. a one-bar note for a crash on beat 1 would trigger the crash in the middle of the bar).

I wonder why this was never an issue in all the other DAWs offering Note chasing since ages...

[Benutzername]

tucked into the 'Improvements' category:

"Mac: reduced GPU (graphics processing) load"

Hmmmmmm, could this be the fix to the 'always running fan' issue I've been complaining about for 3+ years?

I don't even own bitwig currently due, yes, to that issue (I can't work on mixing and sound design with my mac fan running at full blast, sorry) so if anybody on iMac can let me know, thanks!

I was plagued extremely by the fan problem on my MBP up to the point where Bitwig wouldn't even run an empty project without extreme fan noise.

This update has improved things a lot for me as far as I can tell. The fan noise seems to scale well with the CPU load in the projects that I've tried. It feels like it's now behaving like almost all other applications on my computer. I have to do some more testing in the next days but this first beta looks really promising.

[SLiC]

Ok, that I misunderstood... nevertheless why restricting it???

I assume it's so you don't get drum hits/rhythmic elements hitting out of time if you're editing a very rhythmic sound, rather than e.g. a pad or drone. I'm not sure I agree as an implementation but I can see what the rationale behind it is.

So if enabling this option one should keep in mind not to draw in long notes for percussive elements (e.g. a one-bar note for a crash on beat 1 would trigger the crash in the middle of the bar).

I wonder why this was never an issue in all the other DAWs offering Note chasing since ages...

Probably because most other DAWS are not deigned to be played live/improvised on like an instrument.

[Trancit]

Probably because most other DAWS are not deigned to be played live/improvised on like an instrument.

Therefore it´s an option... you can turn it off if you do not want it!!