3.2 (Beta 1) is OUT!!!

Official support for: bitwig.com
Post Reply New Topic
RELATED
PRODUCTS

Post

Tj Shredder wrote: Sat Apr 18, 2020 3:49 pm
PsYAuM wrote: Sat Apr 18, 2020 3:35 pm Audio Engine crashed OS X 10.11.6
Neat new feature within the Beta the ability to send a crash report within the app.
Saves having to go to the website.
Officially the minimum requirement is OS X 10.13 High Sierra.
You probably have to live with it. I upgraded to Mojave and have no problems whatsoever... (Catalina has to wait for some years...)
WTF?
please Bitwig don't lose your soul and buy into Apple's finite model.
As much as i love Bitwig if you try to force me to update from a perfectly fully functioning OS then like i have done with NI i will ditch you like a bad habit.
We are all a unique vibration in a beautiful symphony of infinite creation

Post

I'm really happy with this update, especially the EQ, Saturator, and updated Arp.

Thanks, Bitwig. Very nice work.
Bitwig Certified Trainer

Post

Tj Shredder wrote: Sat Apr 18, 2020 3:45 pm
antic604 wrote: Sat Apr 18, 2020 3:32 pm It's much closer to EQ-5 than to Pro-Q3, so why separate it to yet another device?
Sometimes its easier to redo something from scratch than enhancing/fixing what is there. I guess that is one reason. The same is probably the reason why we have FM-4 and Phase-4. And that way they can throw the old versions into 8-track and 16-track and give those users one more argument to upgrade...
That's a fair point. Weirdly I like FM4 a lot more than Phase4 :)
Music tech enthusiast
DAW, VST & hardware hoarder
My "music": https://soundcloud.com/antic604

Post

SLiC wrote: Sat Apr 18, 2020 3:37 pm Here is some cool stuff I am just getting my head around….

The arpeggiator now has a pitch control for each step and tracks micro pitch changes and polyphonic aftertouch (for us minority MPE users :oops: !)
But it doesn't support pitch slides on the held notes. The PolyAt support is cool

I find the arp workflow annoying. You can only move a single velocity or gate slider at a time. You cannot swipe across. So with the Gate, say I want to set 1 gate step to 200%, I have to set Gate to 200% then drag each of the steps individually to 50% except the one I want to have the full amount. So tedious.

Post

I’m not going to use my renewal code.
How many ornaments can you add to a Christmas tree?
Reason - Reaktor

Post

antic604 wrote: Sat Apr 18, 2020 3:32 pm
brownerthanu wrote: Sat Apr 18, 2020 1:23 pmI can why it was very time consuming because good eq is nontrivial, but at the same time did we really need that? I do like the sound of the new grid filters though. They have a vaguely Zebra2 sound to me which I very much like. The resonance is nice and crisp.
The problem is everything they did with EQ+ could've been added to EQ-5 (other than 3 extra bands).

Also, why can't you just choose node types / slope steepness from the node itself? Or mute it from there? Or overlay sidechain signal from elsewhere to compare? It's much closer to EQ-5 than to Pro-Q3, so why separate it to yet another device?
In this case I think they made the right choice. The new eq has a much different sound than eq-5 so if they just changed eq-5 it would mess up old projects. Or it would be clumsy to change modes within eq-5. I put the new eq through it’s paces and it legitimately sounds much better than eq5 to my ears. I will definitely use it all over the place. But again, did I need this? Not really. I have a number of excellent eq VSTs. I do think it’s a win for Linux, though. It’s now my best Linux eq.

Post

After testing the last beta...
It seems to me that there are hardcore people in Bitwig who love Grid (and it is amazing tool, yes!)
and there are people who sells the product. And not enough people who represent an average daw user.

Propellerhead did simillar thing. It was all about sound and modular synthesis. People who were using Fruity loops 2 were not taken seriously. But one company listened average home producrers and the other did not but instead implemented authorization usb and special daw just for recording :-D.
Bitwig should easily take some things from fl studio, studio one, logic etc. and make it basic midi mouse / keyboard capabilities better.

But making MIDI better is not visible like new equalizer and six colours...
There is one flashy things almost every daw misses. It is automatization clips like fl studio or mulab have. bitwig seems like a great adept here as it can not duplicate gain envelope etc :cry:

Sorry for my english.

Post

ChrisDW wrote: Sat Apr 18, 2020 1:52 pm It would be great to have a shortcut to Toggle Audition Notes ON/OFF (nickallen & abique) :tu:

onoffnotes.png
Yes, or have the option to enable or disable it on all new clips from the settings page. This has been a requested feature for some time.

Post

Mmhh, mmhh, mmmmmh... that´s nasty!

Seeing peoples opinion phaseshifting 180°. Why is there always only this black and white thinking? I´m not the biggest fan of all Bitwig decisions they made since their initial release BUT there were some great decision/features aswell, which made Bitwig into a fairly good DAW. Nevertheless I´m in the Reaper camp for now... I bought a license for 60 EUR for myself on my birthday instead of the 3.1 update and donated the rest of the price-difference to a charity. And the Reaper updates will be coverd for the next few years without paying yearly fees to stay on top!!! (more money for charity :P ) Let´s see how it will develope in Bitwig camp... maybe 3.3 (or 3.4/3.5) will be something for me... who knows. I hope the "online collab thing" will be next... a feature I waited for since v1.0 came out.

And to Antic: Damn I feel with you, that you´re dissapointed by pre-buying until 2021. See it as life-lesson. I learned that aswell with Bitwig that it is just another software in my repertoire and I stopped fanboying and started to question and comparing the promises that were made and what followed. I was one of the first customers (within the first 30 customers) so I could follow the whole story. The main feature I was hopping for at v1.0 was the Grid... :lol: How long was I waiting for ... damn!!! When I look back to v3.03 and what have been added since then... I´m just happy I didn´t go with the updates from there on. Until then they got my money just because I wanted to support them.

There were many other things that started to bug me... (I think they are lost in the code and can´t fix some crutial problems in there). I reported some Bugs in the first year/months/weeks and they´re still in there... some really bad ones that are connected to the core things a DAW is doing. But they were only solved partly (probably only a workaround in the code... IDK... It sure feels that way...) and these aren´t super obvious Bugs like e.g. the open Plugin window behind already opened windows. Which is a good example for being lost in the code! When I reported it they seemed so helples about this and asked me all kind of questions. It´s hard for me to trust a software when the programmers seemed so lost in their code. :roll:

Conclusion: Bitwig is a great (or even amazing) tool for playing/fooling/patching around with audio --> but nothing very reliable when working on serious stuff. My opinion of course!!! There are plenty of great muscians who proof me wrong and create amazing music within Bitwig!

And as I was talking to some SpinTwist Artists a few years back and they told me they listen to each others songs to back-check for mistakes which were introduced by software bugs (e.g. Logic-->Automations) I realized that a software can be faulty and still can produce music that change a whole genre. (and there are songs out there with mistakes in there because of bugs... no biggy... that´s how it is.)

One needs to learn: it´s not the gear, it´s the ear. And the most important part is that the song always needs to be in the center of the attention! Not some software! These are just tools AND if one tool doesn´t meet the credentials, one needs to move on without regrets. One always can go back to use it, when such tool is needed. But limiting yourself because of software is the greatest mistake.

To be fair, remember:
This is only a Beta... if one doesn´t like some things, report them... this is the time it still can be changed. Later this probably won´t happen anymore.


When a knob-color or whatever goes through the spectrum of the colors a babies diaper don´t hate, rather report your opinion. The more people think the same way, the greater the chance it will be changed. That`s what a Public Beta is for!


Sorry for this textblock... I have too much time off these days (obvioulsy). SORRY.
Everyone knows more than I do...

Post

blablablerg wrote: Sat Apr 18, 2020 2:55 pm I like that they gave the option for the tool device to bottom out. But is no one bothered by the fact that the meter of the tool device yellows at -28 dB and not -18 dB like the small meters? It makes the big tool meter kinda useless and annoying tbf.
I have genuinely always been confused by this and would love it if someone could explain this behaviour.

Would also like to know the thought process behind the separate volume and gain controls, as opposed to just having one that went completely to zero. The two controls don't bother me I'm just confused.

Post

Kongru wrote: Sat Apr 18, 2020 3:10 pm Am I right in saying you can't normalize in Bitwig?
Yeah I use Audacity at the moment.

Since we are throwing around requests it wouldn't hurt to have the 'open with audio editor' option.

Post

operator wrote: Sat Apr 18, 2020 4:49 pm One needs to learn: it´s not the gear, it´s the ear. And the most important part is that the song always needs to be in the center of the attention! Not some software! These are just tools AND if one tool doesn´t meet the credentials, one needs to move on without regrets. One always can go back to use it, when such tool is needed. But limiting yourself because of software is the greatest mistake.
This.

Post

Yeah, this is the time, but i'm scared that someone come up with an fantastic! suggestion and end the whole thing with an insult or drama'thing.. i'll brake up with GF-speech.. :)
The devs are humans, so i've read.. 8)
Hey Santa! thx, but your clothes are wayyy! to red..
:D
Last edited by SmajjL on Sat Apr 18, 2020 5:00 pm, edited 1 time in total.

Post

antic604 wrote: Sat Apr 18, 2020 3:59 pm Weirdly I like FM4 a lot more than Phase4 :)
That's crazy haha. FM-4 is so dirty, mostly in an unpleasing way imo. That can be useful depending on the context of course. Want a pristine bell sound? Nope, you're getting a dirty bell. A nice clean slap bass? Here's a dirty almost broken sounding one. Everything FM is supposed to do great that thing does really dirty and not in a nice crunchy way like an 80s DX7 does. Phase-4 will get you there though, no problem. I also think P-4 is dead simple to use. Brilliant UI design imo. It's my favorite synth in Bitwg, well the only Bitwig synth I use.

You know, I didn't know FM-4 got a facelift, or I totally forgot. Come to think of it, does anyone use Organ? :D
-JH

Post

Randall P. McMurphy wrote: Sat Apr 18, 2020 4:50 pm
blablablerg wrote: Sat Apr 18, 2020 2:55 pm I like that they gave the option for the tool device to bottom out. But is no one bothered by the fact that the meter of the tool device yellows at -28 dB and not -18 dB like the small meters? It makes the big tool meter kinda useless and annoying tbf.
I have genuinely always been confused by this and would love it if someone could explain this behaviour.

Would also like to know the thought process behind the separate volume and gain controls, as opposed to just having one that went completely to zero. The two controls don't bother me I'm just confused.
I guess modulation purposes. They could have solved this a lot more elegantly imo. Something like a switch to activate go to -infinity.

Post Reply

Return to “Bitwig”