Bitwig

mustgroove · Post by **mustgroove** » Thu Aug 20, 2015 5:04 pm

Happy to have just been added to the beta tester group!

One bug I've noticed - plugins that support retina GUIs are displaying non-retina GUIs in 1.2 beta 4... Valhalla and u-he plugin GUIs are rendering as the non-retina scaled-up versions, with heaps of pixelation etc.

qtheerearranger · Post by **qtheerearranger** » Thu Aug 20, 2015 5:05 pm

question idk to report this cause idk if its a bug or working as intended:

Create a marker on bar 4. Loop Bars 1-4. Enable Loop Cycle. When play marker passes bar 4 click the marker to have it play bar 4 again. It doesn't. It goes to bar 1 instead of recycling bar 4.

This doesn't happen when the loop cycle is turned off so its got to be a minor bug one way or the other right? The loop cycle shouldn't change the marker behavior, right?

jwise · Post by **jwise** » Thu Aug 20, 2015 5:08 pm

Removed

c-wave · Post by **c-wave** » Thu Aug 20, 2015 6:35 pm

Ogopogo wrote: One weird thing about using categories is that a category is supposed to be an exclusive thing but there are lots of overlaps with the Bitwig categories, eg. piano-keyboard-synth, bass-synth, lead-synth, pad-synth, drums-kick, and so on.

Besides being illogical it interferes with the functionality of the browser, to be able to view and search all your sounds easily. You may choose piano and miss out on a piano synth sound because you filed that under synth. You don't have that problem with tags. I think maybe the idea of categories should be dropped.

+1
I agree, tags biggest advantage is that an item can have multiple tags, so if it is the case that there are developers' made items, they can simply be automatically tagged by Bitwig with a "dev" tag rather than waste a column on that.. even if that's not the case, this tag solution still stands IMHO.

Although not a beta tester I can feel the "pain" of a cluttered dialog box. So I think yes:
1. needs to have it's own prefs with settings to: (a) show/hide columns, (b) keep/reset last state of everything in it (i.e. general box size, column size(s), etc..), (c) better visual feedback for items rather than relying on right-clicking empty spaces.. (i.e. more "+" at end of columns, more explanatory icons near target items.. a red and white circle target is self explanatory!)
Cheers..

NWSM · Post by **NWSM** » Fri Aug 21, 2015 8:40 am

Hi There,
when we will have a stable 1.2 ??

TeotiGraphix · Post by **TeotiGraphix** » Fri Aug 21, 2015 11:04 am

capracan wrote:Hi There,
when we will have a stable 1.2 ??

When it's officially released to the public, it will be stable.

Mike

TristanMendoza · Post by **TristanMendoza** » Sat Aug 22, 2015 1:43 am

Finally diving a little deeper into the beta. Its pretty sick.
I love being able to switch around audio interfaces now, before Bitwig wouldn't recognize it if it was plugged in after the program opened. It also looks like they're going back to the darker interface that was shown when Bitwig was just starting out, and the text looks different to me. I like it.
But I know that until the official 1.2 drops, we aren't here to marvel at its beauty, were here to find bugs and make it stable as hell!

Eta Carinae · Post by **Eta Carinae** » Sat Aug 22, 2015 1:47 am

How many premier badge holders are there? And has it been released to all of them? Just wondered what sort of scale the beta is on.

SoundGoddess · Post by **SoundGoddess** » Sat Aug 22, 2015 1:49 am

I really like it a lot so far

Going to have to spend some quality time really digging deep. Ran into a couple bugs but nothing too major.

TristanMendoza · Post by **TristanMendoza** » Sat Aug 22, 2015 1:58 am

Eta Carinae wrote:How many premier badge holders are there? And has it been released to all of them? Just wondered what sort of scale the beta is on.

Im number 538, and I have it. I want to say it goes up in to 1000...? I know theres people a little higher than me.

TristanMendoza · Post by **TristanMendoza** » Sat Aug 22, 2015 2:06 am

Just had a crash while connecting Push. I tried to recreate it a couple ways but no success.
I had the project playing and I connected, then powered Push on and thats when Bitwig crashed. Can anyone get this to happen?

svervs · Post by **svervs** » Sat Aug 22, 2015 8:16 am

TristanMendoza wrote:Just had a crash while connecting Push. I tried to recreate it a couple ways but no success.
I had the project playing and I connected, then powered Push on and thats when Bitwig crashed. Can anyone get this to happen?

Yep, had this one too, but couldn't reproduce as well ...

blu789 · Post by **blu789** » Sat Aug 22, 2015 9:39 am

Has this been discussed to death?

I'm an Ableton user, and I'm really wanting to try Bitwig 1.2, but given that 1.2 was shown at NAMM in January, and it's almost September, I'm beginning to think these monolithic feature upgrades are just too big for the Bitwig team to handle in a reasonable manner.

(BTW I used to be a device driver software engineer for 10+ years in another life working on Windows drivers and low level firmware), so I get that software engineering is complicated... I still dream in assembly language from time-to-time so I do have a good understanding of it.

Given that it's a tenth of a point upgrade (.1 to .2), maybe there are too many features crammed into a point release? Somehow I think smaller feature sets and more frequent upgrades is far better... Based upon the bugs remaining it's quite possible a 1.2 release is soon, but I don't have much faith in it.

The bottom line is that it's holding me off from a installation and potential buy.

Any thoughts?

tooneba · Post by **tooneba** » Sat Aug 22, 2015 10:11 am

don't worry we still have 4 years? to go 2.0

ThomasHelzle · Post by **ThomasHelzle** » Sat Aug 22, 2015 10:12 am

blu789 wrote:Has this been discussed to death?

I'm an Ableton user, and I'm really wanting to try Bitwig 1.2, but given that 1.2 was shown at NAMM in January, and it's almost September, I'm beginning to think these monolithic feature upgrades are just too big for the Bitwig team to handle in a reasonable manner.

(BTW I used to be a device driver software engineer for 10+ years in another life working on Windows drivers and low level firmware), so I get that software engineering is complicated... I still dream in assembly language from time-to-time so I do have a good understanding of it.

Given that it's a tenth of a point upgrade (.1 to .2), maybe there are too many features crammed into a point release? Somehow I think smaller feature sets and more frequent upgrades is far better... Based upon the bugs remaining it's quite possible a 1.2 release is soon, but I don't have much faith in it.

The bottom line is that it's holding me off from a installation and potential buy.

Any thoughts?

The main thing that made the 1.2 update take so long (AFAIK) is the rewriting of the audio core. Instead of using Port Audio it's now a self-written and self-maintainable solution. This had to be done since PA simply didn't work for many people/sound devices. And you can't really do that in "small steps"...

Since BWS is still quite young, the .x updates are quite massive compared to some older DAWs where updates on the scale of BWS 1.1 or 1.2 would probably be a full major version. I'm actually happy about this.

Between 1.0 and 1.1 and between 1.1 and 1.2 there were a huge number of small updates that fixed bugs and added smaller features.

So it's pretty much happening as you want it?

Not really getting the problem I fear - the 1.1 demo works just fine...

Cheers,

Tom

Bitwig

KVR Audio

Bitwig Studio 1.2 BETA 4