Bitwig 5 is up

[pdxindy]

Did anybody notice that the old browser preview desease is back: Previewing without the initial transient...
4.4.10 plays them correctly but beta 5 and 6 not...
Is that just me or does anybody else has got it?? Very noticeable when previewing Kicks with sharp transients...

Didn´t we have this topic some time ago with V2 or V3??

What block size do you use on your projects. People using 1024 or 2048 are having that issue. Doesn't seem to be a problem with smaller sizes. Like I run my projects at 128-256 and transients are fine.

You are right... it´s block size related...
Nonetheless it works fine on 4.4.10 with 1024 samples...it´s just V5 got this problem again...

Understood... I was checking to make sure it was the already known problem and not a different one that needs reporting.

[pdxindy]

Has anybody witnessed the weird macro knob behavior with project/track/other container macro knobs modulating midi cc knobs in the beta?
When I change a macro knob position to bind to a midi cc knob it flickers on the midi cc knob all the time and sends continuous midi cc to my synth...
It does not happen with the macro knob in the midi cc device itself. But if I map a macro knob to the macro knob again, the same behavior occurs:

I tried to duplicate this, but was not able to. Then I copied your setup as closely as I could (without setting up a hardware synth) and still was not able to duplicate it.

Do you have some sort of midi loopback going on?

[pdxindy]

Another Arp example... I'm finding a good workflow for controlling arps using MSEG's. Midi clip is 1 bar of a held chord... totally simple. 3 layered arps. Then I am using slow MSEG's to change the arps to different "snapshots" over multiple bars. Not as slick as an actual snapshot system, but for me anyway, quite workable. And of course it could be played realtime instead of just a single held chord. The new MSEG's are so useful!

https://dandelionaudio.com/sound/Multi-Arp-4.mp3

[Bjørnson]

Hej pdxindy,
thanks for checking on your side!
My standard template seems to be corrupted... if I start from scratch it does not happen.
But no midi loop - deactivated all midi input, external midipipes and control scripts and still had the problem.

[pdxindy]

Hej pdxindy,
thanks for checking on your side!
My standard template seems to be corrupted... if I start from scratch it does not happen.
But no midi loop - deactivated all midi input, external midipipes and control scripts and still had the problem.

You could send that standard template to Bitwig and explain the issue.

On your template, if you right click the CC74 knob, there are no other assignments besides that macro knob?

[pizzatime]

Another Arp example... I'm finding a good workflow for controlling arps using MSEG's. Midi clip is 1 bar of a held chord... totally simple. 3 layered arps. Then I am using slow MSEG's to change the arps to different "snapshots" over multiple bars. Not as slick as an actual snapshot system, but for me anyway, quite workable. And of course it could be played realtime instead of just a single held chord. The new MSEG's are so useful!

https://dandelionaudio.com/sound/Multi-Arp-4.mp3

Good stuff.

[pizzatime]

The keytrack + is nice but I really like the original key track too as you could modulate that but it seems to have disappeared? A little cramped looking relative key track is there I just saw - I am starting to think they are tweaking things that are easy to tweak just to have something new sometimes..

So you go to 'K' for key track but then 'R' for relative key track - that makes good sense.. why not call it keytrack relative..

[pdxindy]

Another Arp example... I'm finding a good workflow for controlling arps using MSEG's. Midi clip is 1 bar of a held chord... totally simple. 3 layered arps. Then I am using slow MSEG's to change the arps to different "snapshots" over multiple bars. Not as slick as an actual snapshot system, but for me anyway, quite workable. And of course it could be played realtime instead of just a single held chord. The new MSEG's are so useful!

https://dandelionaudio.com/sound/Multi-Arp-4.mp3

Good stuff.

[pdxindy]

The keytrack + is nice but I really like the original key track too as you could modulate that but it seems to have disappeared? A little cramped looking relative key track is there I just saw - I am starting to think they are tweaking things that are easy to tweak just to have something new sometimes..

So you go to 'K' for key track but then 'R' for relative key track - that makes good sense.. why not call it keytrack relative..

If you open the modulators browser and type "k", the two Keytrack modulators will both be at the top.

I like your suggestion of Keytrack Relative. Send it in to Bitwig!

Also, the Relative Keytrack doesn't have a pop-open GUI and it should.

[Bjørnson]

Hej pdxindy,
thanks for checking on your side!
My standard template seems to be corrupted... if I start from scratch it does not happen.
But no midi loop - deactivated all midi input, external midipipes and control scripts and still had the problem.

You could send that standard template to Bitwig and explain the issue.

On your template, if you right click the CC74 knob, there are no other assignments besides that macro knob?

Thanks again pdxindy
I deleted all MIDI mappings and tracks and the bug still is on every CC channel. I saved a project with just a MIDI CC device and a track macro knob changing these CCs. The CC knobs flicker all the time in my Bitwig 5 beta 6.
If you want to try: https://www.dropbox.com/s/cjquxqlx2i1jn ... r.zip?dl=0

I will send a ticket to the beta e-mail. I didn't know it exists and communicated through the normal support ticket system till now and got no answer.

Best,
Björn

[pdxindy]

I will send a ticket to the beta e-mail. I didn't know it exists and communicated through the normal support ticket system till now and got no answer.

Best,
Björn

Yeah, the beta email is only used during these beta testing periods and for issues specific to the betas. Otherwise the regular support email.

Please post the explanation here if Bitwig has one... now I'm curious

[Bjørnson]

I will send a ticket to the beta e-mail. I didn't know it exists and communicated through the normal support ticket system till now and got no answer.

Best,
Björn

Yeah, the beta email is only used during these beta testing periods and for issues specific to the betas. Otherwise the regular support email.

Please post the explanation here if Bitwig has one... now I'm curious

Will do!
And I found out that if create a new empty project and I map a project macro knob to the midi CC device knobs it also flickers - all midi controllers and mappings deleted in my setup...

[trostiflex]

What does it mean exactly : "This is a free update for all license holders with an active Upgrade Plan at time of announcement (April 11, 2023)." ?

If I buy Bitwig 4.4 tomorrow, I will have to pay for the upgrade to Bitwig 5 because I didn't have an active upgrade plan the day it was announced, the 11th of april ?

[pdxindy]

If I buy Bitwig 4.4 tomorrow, I will have to pay for the upgrade to Bitwig 5 because I didn't have an active upgrade plan the day it was announced, the 11th of april ?

If you buy Bitwig tomorrow, you will also get V5 (including trying the beta versions immediately) plus any other updates (5.1 and so on) that are announced within 12 months of your purchase date.

It used to be that someone could have an active account when a new update was announced, but by the time it was out of beta and officially released, their account was no longer active and then they wouldn't get it... which can obviously lead to frustrated feelings. So Bitwig just changed it the announcement date, not the release date... thus what you quoted.

[Tj Shredder]

It means,as far as I understood, if you have an active plan now, and it will run out before the official release of Bitwig 5, you still get a license for all versions of BW 5.0.x.
It is a way of saying thank you for testing... In the past often users had a ran out plan, and Bitwig would extend it by hand out of goodwill. Now that goodwill is official.
If you buy Biwig now, you get all updates which happen within the next year. Maybe to 5.3.x...