Bitwig 6

[n9research]

So many new features I sorely wanted. Step Entry?!

100% dropping a key on the beta when I swing by the studio later. Can't wait for this..

[koalaboy]

The new (better) way in 6 is to create an automation clip of a different length of the content clip, then set the automation clip to loop. When you resize the content clip, the automation clip will resize to match, but with different loop lengths. Perfect.

Apologies - the 'better way' we're looking for isn't actually the free-running (I understand how that works now) but how to reproduce the 'relative' automation clips from v5.

[chaocrator]

I suspect they will undo this. I've seen two other companies recently add AVX2 as a requirement, only to roll it back a single version later after realizing like 30% of their customers are on micoarchitectures that don't support it.

that would be nice.
actually, my 2012 Mac Mini (running Ubuntu) has decent specs even by todays standards and works perfectly, and i really dislike to replace something that isn't broken.

[coroknight]

According to the latest steam hardware survey, 95% of people have cpus that support AVX2. Sure, gamers probably have slightly better computers than music producers but it's not like gamers are all rich, they have to buy affordable hardware too.

What AVX2 support means is bitwig can squeeze out more performance for the rest of us instead of getting held back by the small percent of users who refuse to update their computers.

I'm not claiming bitwig will double in performance, it's a lot more complicated than that, but AVX2 can process 2x as much data at the same time compared to SSE which is the previous standard.

The steam hardware survey (click "other settings" to see instruction sets):
https://store.steampowered.com/hwsurvey ... e-to-Steam

[tumface]

Apologies - the 'better way' we're looking for isn't actually the free-running (I understand how that works now) but how to reproduce the 'relative' automation clips from v5.

Seems like it might be gone. It never worked properly for me in the past -- I filed several bugs about data getting messed up or becoming invisible/uninteractable with relative automation in the arrange view in Bitwig 5, but they were never fixed. The way I ended up doing it in the past, and will do now, is use macro modulator knobs and modulator adds as needed. It's an extra step, but it's also more flexible.

[tumface]

What AVX2 support means is bitwig can squeeze out more performance for the rest of us instead of getting held back by the small percent of users who refuse to update their computers.

I'm not claiming bitwig will double in performance, it's a lot more complicated than that, but AVX2 can process 2x as much data at the same time compared to SSE which is the previous standard.

It's not true. Many microarchitectures that support AVX2 do it only in a compatibility sense -- the microcode instructions are not any more efficient than the equivalent string of SSE4 or AVX instructions performing the same work. Some do it more efficiently, but not all. This includes CPUs released just this year. (I write SIMD assembly by hand in my day job, FWIW.)

[pdxindy]

Siiiick. I've been advocating for automation clips for a long time, and I've even suggested adding tools to give clips extra functionality like being able to use curves and modifiers like randomness. Feels like this update was made for me haha.

It's really sweet that in the Clip Launcher, Automation Clips can be triggered separately and they even work with their own Next Action commands!

[pdxindy]

So many new features I sorely wanted. Step Entry?!

Step Entry is working well so far... one of my main feature requests. I appreciate that even with scale enabled, I can still add notes off scale via Step Entry

[tumface]

According to the latest steam hardware survey, 95% of people have cpus that support AVX2. Sure, gamers probably have slightly better computers than music producers but it's not like gamers are all rich, they have to buy affordable hardware too.

So, I just checked, and according to the Steam Hardware Survey, only 1.88% of users are on Mac. That's fewer than users which have an NVIDIA GeForce RTX 4080. Bitwig should drop all of the Mac and Linux support, and make Windows require a GTX 4080 or higher

firefox_5D1beyYvWT.png

[pdxindy]

The new (better) way in 6 is to create an automation clip of a different length of the content clip, then set the automation clip to loop. When you resize the content clip, the automation clip will resize to match, but with different loop lengths. Perfect.

Apologies - the 'better way' we're looking for isn't actually the free-running (I understand how that works now) but how to reproduce the 'relative' automation clips from v5.

It looks like Add and Multiply relative options are gone and there's no way to do the same.

[tumface]

It looks like Add and Multiply relative options are gone and there's no way to do the same.

Personally, I won't be missing this one. It was fussy and complicated, and never worked properly once you started editing and moving stuff around. I will just automate a macro knob if I want to do it.

[koalaboy]

It looks like Add and Multiply relative options are gone and there's no way to do the same.

Personally, I won't be missing this one. It was fussy and complicated, and never worked properly once you started editing and moving stuff around. I will just automate a macro knob if I want to do it.

It would just be nice if things that are taken away are also noted as much as the 'new' things, ideally with suggestions on how best to migrate things. Especially for a release that is so (well) focused on 'workflow'.

[coroknight]

What AVX2 support means is bitwig can squeeze out more performance for the rest of us instead of getting held back by the small percent of users who refuse to update their computers.

I'm not claiming bitwig will double in performance, it's a lot more complicated than that, but AVX2 can process 2x as much data at the same time compared to SSE which is the previous standard.

It's not true. Many microarchitectures that support AVX2 do it only in a compatibility sense -- the microcode instructions are not any more efficient than the equivalent string of SSE4 or AVX instructions performing the same work. Some do it more efficiently, but not all. This includes CPUs released just this year. (I write SIMD assembly by hand in my day job, FWIW.)

So what? Those of us with computers that actually support AVX2 get a performance boost, while those that emulate it don't which is the same as today except now Bitwig only has to support one instruction set.

Can't wait to hear what other bullshit excuses people come up with.

[Stan Navi]

Is it possible to return white backround?

By the way when setting chances in notes, Bitwig now dims notes which are not active.

[psycha0s]

I suspect they will undo this. I've seen two other companies recently add AVX2 as a requirement, only to roll it back a single version later after realizing like 30% of their customers are on micoarchitectures that don't support it.

I think they just didn't include the SSE4-compiled binaries in the beta installer by mistake. Earlier, they bundled both SSE4 and AVX2 versions, but right now I see only the AVX2 ones. Judging by the additional legal information, they use the XSimd library to support vector instructions, so supporting a specific instruction set shouldn't be a problem for them.