bitwig 2 is here

[Aleatoriac]

It's rubbish.

If it can't manage my music career (BWA HA HA HA HA WTF IS THAT SUPPOSED TO BE?) and make me a superstar, I don't want it.

[CTStump]

my apologies, I did indeed overlook something and did find hard evidence of the sockpuppet...he is gone...please forgive my still learning process when it comes to the ip addresses

Kind of a shame to go to such lengths but necessary. Thanks for your efforts my friend.

Back on topic, I guess when the release finally does come there will be some that will change their minds and bite the bullit, I don't think I will but hopefully it all works for those that do.

[Daags]

my apologies, I did indeed overlook something and did find hard evidence of the sockpuppet...he is gone...please forgive my still learning process when it comes to the ip addresses

better late than never

curious: the sock-puppeteers other accounts get banned too, right ?

[Hink]

my apologies, I did indeed overlook something and did find hard evidence of the sockpuppet...he is gone...please forgive my still learning process when it comes to the ip addresses

better late than never

curious: the sock-puppeteers other accounts get banned too, right ?

it already was

[Daags]

So what? If you don't think it's worth it don't upgrade or buy it.
Can we talk about the new features, not the cost, it's getting really dull.

I've been playing with the new HW CV Output, HW CV Instrument and HW Clock Output devices quite a bit over the last few days and so far I'm very pleased.
The HW CV Output is a lot of fun, it's just a knob and and a list of available outputs. Turning the knob results in a DC voltage at the output. You can then modulate that knob with any of the Mod devices. I've had a lot of fun setting up a bunch of these devices in a layer and then using macros to control the CV output directly or the parameters of the Mod devices.
The Clock Output is a big deal for me because I use a lot of hardware sequencers. It has two outputs, one which is used to actually clock the sequencer and another which can be used to reset the sequencer. The reset is normally used to set the sequencer back to 1 when you press stop in the transport but it can also be used to define a step at which the sequence should restart, so you can have sequences which run at different lengths. Of course you can modulate the clock divisions for all sorts of madness. It has options for 1/96, 1/48 and 1/24 which are useful if you have drum machines which are expecting DinSync clock.

The CV Instrument has a Pitch output and a Gate output and can also be a container for other CV devices. The Pitch output has a range setting where you define the voltage range of the outputs on your DC coupled audio interface, so that you can get a signal which is scaled to 1v/oct. There is also a roote key setting so you can define which key is associated with 0v. The audio input works like the audio input on the normal HW Instrument device and it has a latency compensation setting. This is very nice as I had to create a HW FX device when using the Silent Way voice controller, anyway. With this configuration I don't need as many devices in the chain.

I'm also very happy with all the visual feedback improvements. For example, it's nice to have frequency analyzers on all of the EQ devices.

The New note processing devices are also a lot of fun.

The Bitwig 2.0 Alphas have been very stable in my opinion. I was able to complete a project without encountering any crashes. I have high hopes that once people get their hands on 2.0, they will be very happy with the new features and improvements.

thanks for the details. in practise, how does it compare to Expert Sleeper's 'Silent Way' cv plugin suite ?

[Daags]

my apologies, I did indeed overlook something and did find hard evidence of the sockpuppet...he is gone...please forgive my still learning process when it comes to the ip addresses

better late than never

curious: the sock-puppeteers other accounts get banned too, right ?

it already was

hmm, interesting! anyway, thanks for the clean-up

[incubus]

Geez. Isn't Bitwig supposed to be the best daw ever? The daw to end all daws. The saviour of daw world. The miracle daw. At least according to all hype preceding the release of it.

Can't believe what I'm reading. Instead of celebrating the second coming there's over 30 pages of complaining about petty things like price and features.

It's probably people that are upset that it's legal to have pot here in kalifoenia, but it's illegal to buy it. And now bitwig has the audacity to charge for an upgrade.

[incubus]

So what? If you don't think it's worth it don't upgrade or buy it.
Can we talk about the new features, not the cost, it's getting really dull.

For me, fades and xfades are huge, but not 169 bucks huge. It's going to be a couple of weeks before I can wrap my head around all the new features. It's funny though, I had been meaning to demo it again (after 2 years) and for some reason this thread got me to do with that.

(edit, I'm sorry I'm so bad at typing mistakes)

[justin3am]

in practise, how does it compare to Expert Sleeper's 'Silent Way' cv plugin suite ?

Quite well. With Silent Way, if I wanted to combine an envelope, an LFO and a sequencer to one output, I would need three different plug-ins on the same track. With the HW CV Output, I can combine many modulation sources within the same device, so it's very flexible.

There are some Silent Way plug-ins which don't have an equivalent in Bitwig but most of the bases are covered. For example, if you are using an ES-4 or ES-40, the signals need to be encoded in a certain way in order to be compatible with those modules. I have an ES-3/ES-6 combo as well as a MOTU interface with DC coupled outputs. This gives me a total of 16 CV outputs from Bitwig and each output can have several modulation sources.

The guys at Bitwig seem pretty receptive to new ideas when it comes to controlling hardware/modular synths. I'm pretty excited about that.

[incubus]

I wish someone could fix whatever is causing my nektar to disconnect having to turn it off/on with bitwig.

[justin3am]

I wish someone could fix whatever is causing my nektar to disconnect having to turn it off/on with bitwig.

Please create a support case. We'd be happy to help.

[incubus]

I wish someone could fix whatever is causing my nektar to disconnect having to turn it off/on with bitwig.

Please create a support case. We'd be happy to help.

Pretty sure it's bitwig specific as people have complained about losing controllers that are not nektar as well. Off/on, and it's fine. But I'm really happy that you posted here and PM'ed so we can double check w/o needing to open a ticket right now.

[pdxindy]

I am using bitwig 1.3 demo for a week now and discovered a new bug .

1.create lfo mod .
2. create synth nested in lfo mod .
3 . record some notes and ' Bounce in place ' = Silence ( same as bounce with pre fx enabled )
4. insert reverb (post )
5. Bounce in place : now works .
6.Delete reverb
7.Bounce in place : works.

So I am gonna have to shell out a lot of money to see this bug fixed

I have yet to see a host that one did not end up having to pay for upgrades to get existing bugs fixed.

[pdxindy]

If they just rolled back on the daft 12 month license thing and just committed like a Steinberg to release significant yearly point and full updates ( going on the assumption according to BW that they have all of these great features ready to roll, nobody minds waiting a year for something significant ) then this whole PR nightmare would subside. Or use a S1/Reason model whatever, why as a software company they can't see this is a subscription model by another name is beyond me.

They are trying to reinvent a pricing structure to something that is really obviously defective for the users.

I don't mind paying for a major upgrade at all going on the assumption, and let's face it BW past track record is a bit shaky, that it will be supported until its relatively bug free.

I think $170 per year is somewhat on the high side, but I just don't see any reason to scream and moan as if the sky is falling. Time will decide things and peoples choices regarding upgrading. Purchase v2 and if over the course of 12 months Bitwig has not provided enough to make you happy to upgrade again, then don't. If enough people don't, then the price will fall. It will all get decided without all the yelling anyway.

It is not a subscription model cause when the time runs out I can keep using the software as long as I want without paying. If I keep my audio computer as is and do not do OS updates, I could run Bitwig for years without any additional cost. As long as I have that option, I do not care so much about the manner in which I am asked to pay for improvements... cause the choice of when to do so is in my hands.

[pdxindy]

Yup- As a eurorack user the CV out stuff looks interesting, there is already the ES-8 but also rumours of other USB- CV output devices for use with software like Reactor and BWS

also curious about the CV stuff, but with Expert Sleepers 'Silent Way' available to use with all VST hosts, it's not a 'killer feature' that is going to lure me into wearing the gimp suit I'd be expected to wear when signing up to this new 12-month-subscription-fees-for-bug-fixes scheme of theirs. Nevertheless, I'll be keeping tabs on this feature out of curiosity and of course relevance to my hardware setup.

Personally I will just upgrade as soon as its available, its 160 bucks, cheap as far as I am concerned and I don't care what happens after a year, I will decide if its worth paying again then. For now, the upgrade is worth the money for me, cant wait.

Yeah... it is a small amount of money... and maybe in a year, Bitwig will have reached a point that I feel no need to update.

Over the course of close to 20 years I updated Photoshop every 2-3 paid upgrade cycles.