Bitwig 6

[muzicxs]

In V6 you can also make a time selection in an automation lane and drag that as a curve into a Curves modulator. It also works the other way, you can drag any saved modulation Curves into an automation lane.

So that is one way to save a bunch of favorite automation curves and to swap back and forth between between modulation and automation.

Nice tip! This is why I appreciate Bitwig so much. Their holistic approach of software development integrates many concepts so smoothly that they speed up your workflow significantly.

[looploop87]

Previously, when dragging a sample into the track header area (not the arrangement view), Bitwig would automatically create a new track with a Sampler device loaded and the sample placed inside.
Now, regardless of where I drag the sample, it always ends up in the arranger timeline.
Is this a bug, or is this the new intended behavior?

[pdxindy]

Previously, when dragging a sample into the track header area (not the arrangement view), Bitwig would automatically create a new track with a Sampler device loaded and the sample placed inside.
Now, regardless of where I drag the sample, it always ends up in the arranger timeline.
Is this a bug, or is this the new intended behavior?

My assumption is it's a bug

[billinder33]

dedicated studio output busses to manage multiple studio monitoring scenarios

Isn't that there in the bottom right (since 5.3 the little speaker icon? You can choose different things)

The function I'm looking would be for bitwig to have an FX insert before each physical output which to accomodate different calibration tools/settings per output. So a user can have different calibration setups for each physical output, while also preventing calibration from affecting the renders that come from the master buss.

I figured out a way to dodge calibration on renders by 1) putting all tracks into a main folder, routed to the Master output 2) disconnecting the Master output from the Studio 3) using an audio receiver to route the Master audio to a FX 'listen' buss which is routed to the Studio. So the Master is just for render, Studio output through the FX buss. But I still have to manually switch calibration settings every time I switch outputs. It would be way more elegant if each output defined in the settings just had its own FX insert.

Unless there's some setup option I haven't figured out, today it seems like the choice is either having calibration on the master and just remembering to shut it off during every render, or remembering to change calibration settings when changing outputs.

[coroknight]

I bet this is why the 5.x series of updates were less impactful than people hoped. They’ve probably been working on this for awhile.

Not so sure
ARM support for the whingymac users
Sound Engine overhaul allowing multiple audio devices
UI graphics overhaul
CLAP plug in support

Were all probably very important in setting a solid foundation to now be able to build upon

Yes that’s partly what I meant by “working on this for awhile”

But realistically, how many users even noticed or cared about these things? That’s what I meant by less impactful.

I’m not going to get into another argument so I’ll leave it at that.

[questionaire]

Bitwig crashes my system once i have recorded midi inside a clip and right after hit (q) to quantize and Bitwig poof disappears.
Im on Linux it happens structural, so easy to replicate

[Ou_Tis]

Literally zero of the changes in the entire changelog are at all interesting to me this time.

I record everything live. I would say I never use clips, except I did once this year (for a very simple MIDI loop with wonky timing). I only use the timeline when mastering, and the automation was absolutely adequate for my purposes before.

Maybe the new look will be nice, if I want to really reach for something positive here.

This is not a complaint, but an observation. I am mostly happy with how Bitwig 5 works. There are a couple of features I'd like to have, but lacking them hasn't stopped me before and won't stop me now. And I'm happy for other people who wanted this stuff.

I don't see anything in the changelog ("release notes") about any improvement in the resolution of recorded automation, which is one of Bitwig's biggest limitations for me. The resolution is absurdly low.

[Edit: equivalently, the "reduction level" is extremely high, and can't be changed---curves are reduced to a few nodes. At least provide an option to change the reduction level.]

[pdxindy]

The resolution is absurdly low.

I don't believe that is correct.

[Ou_Tis]

The resolution is absurdly low.

I don't believe that is correct.

I tried it with external hardware and with the "write automation" option in Waves Vocal Rider... the amount of reduction is ridiculous. Curves get reduced to a few nodes. It's much worse than Ableton---or Cubase, which lets you set the reduction level to whatever you want (including 0). Of course as I indicated I haven't tried it in Bitwig 6 yet, but the release notes make no mention of any improvement in this, or any option to adjust the reduction level.

[foosnark]

I don't see anything in the changelog ("release notes") about any improvement in the resolution of recorded automation, which is one of Bitwig's biggest limitations for me. The resolution is absurdly low.

[Edit: equivalently, the "reduction level" is extremely high, and can't be changed---curves are reduced to a few nodes. At least provide an option to change the reduction level.]

I don't record automation -- I just literally hit the master audio record button, and keep just the master stereo output, with effects and everything baked in. It's a hybrid mishmash of Eurorack hardware, other hardware instruments/toys and software, so there's nothing else that really makes sense.

The few times I do use automation -- let's say for making EQ changes during mastering -- I just add it on the timeline and draw in linear changes. That all worked fine before for my purposes.

The actual limitations I run into in Bitwig:

- MIDI CC gets smoothed, so trying to convert Eurorack CV to CC for hybrid use doesn't always give me the results I want. It's great for faders and expression pedals, but it's horrible for stepped modulation sequences or trying to visualize signals.

- conflicts between MPE and Bitwig's own "expressions". For instance, if I want to use Note Grid to add slew limiting to pressure, while also trying to use Entonal Studio for microtuning.

[pdxindy]

The resolution is absurdly low.

I don't believe that is correct.

I tried it with external hardware and with the "write automation" option in Waves Vocal Rider... the amount of reduction is ridiculous. Curves get reduced to a few nodes. It's much worse than Ableton---or Cubase, which lets you set the reduction level to whatever you want (including 0). Of course as I indicated I haven't tried it in Bitwig 6 yet, but the release notes make no mention of any improvement in this, or any option to adjust the reduction level.

Ahh... now I understand. It seems unchanged in V6. There's no parameter for node reduction.

[tumface]

This might be kind of a cringe workaround, but the way I've dealt with Bitwig's excessive automation smoothing in the past -- both for point reduction, and also actual low-quality smoothing of the automation data as it's being sent to devices (only affects internal Bitwig devices, not plugins) -- is to record and edit it as audio CV and then use an audio rate modulator to read it Bypasses all of the smoothing problems.

(And before v6, this way used to also be easier to edit and manage than actual automation data...)

[muzicxs]

In the past I could edit the pitch of an audio file in the editor and add a bunch of points, but I can no longer find it. I can apply pitch to an entire audio event, but I cannot figure out how to gradually change pitch inside the audio event. Anyone any idea where they moved this to?

[tumface]

In the past I could edit the pitch of an audio file in the editor and add a bunch of points, but I can no longer find it. I can apply pitch to an entire audio event, but I cannot figure out how to gradually change pitch inside the audio event. Anyone any idea where they moved this to?

Right click (or click and hold) on this little menu here in the Detail Editor and choose Transpose.

BitwigStudioApp_R6uwHqNXaB.png

[Ou_Tis]

Bitwig 6 (latest beta) automation recording resolution (node reduction) vs Ableton, both using Waves Vocal Rider "Write Automation" on same audio with same settings: see attached.

I'm extremely disappointed. For me, this is Bitwig's biggest drawback, because fine-grained, expressive, manual automation with hardware controllers is a major part of my workflow, and I'd like to be able to edit that automation afterwards instead of only relying on live recorded audio.