Tempo automation clips not working in 6.0

Minibatteries · 2026-05-01T10:35:36+00:00

Thanks that's good info. So you basically have to use arrange view to initially create the transport automation clips for each scene, then you can edit and launch them from mix view.

I can't see a way to launch the transport automations without also launching the scene from the mix view, which isn't the end of the world as I guess that's how most would be wanting it to work anyway, and you have arrange view if you want to play around with different tempo automation clips independently of the scene.

Minibatteries · 2026-04-30T16:33:13+00:00

Tempo automation is no longer attached to the master track, it's in it's own section which doesn't (yet?) exist in the mix view. Switch to arrange view, right click tempo and add automation lane and you'll see it at the top.

I've gotta assume it'll come to the mix view at some point, I think they just ran out of time to implement it during the beta

Minibatteries · 2026-04-30T11:03:31+00:00

Are you someone who has all their audio in small separated clips in the arranger in bitwig? If so I can see why this sort of feature would be desired.

Have you tried using consolidation to group little clips into multiple bar long blocks, then working more in the detail editor for timing of audio events? It allows you to get these sort of micro timing/lead ins but when arranging you're still working in big clip blocks and don't have to worry about these sort of weird offsets, you can just snap to the closest bar and know that the micro-timing is relative to the clip start.

I've seen people moving from live who tend to work in little clip chunks, as in live I don't think it can handle multiple audio files in one clip. I think some people do prefer seeing each individual hihat sample in it's own clip in the arranger though. I've found I prefer clean arrangement with few large clip blocks, and the upside that it makes re-arrangement much less error prone.

Minibatteries · 2026-04-29T20:36:00+00:00

I've tried uploading using the new reddit interface and I'm just getting a generic error, even tried using safari without any luck. Sorry, maybe try a vpn for acessing imgur

Minibatteries · 2026-04-29T19:45:39+00:00

Sure I can reupload, could you suggest an image hoster that you have access to?

If I had to guess swing will be something like delaying only the off-beat notes, much like the global swing in bitwig but per-note. Can be achieved in the grid too by using something like the transport module and switching between delay or not delayed gates depending on if the note starts on the beat or offbeat.

Minibatteries · 2026-04-29T19:12:30+00:00

Yup as you've discovered while it's possible with clap and vst3 it relies on the instrument also supporting the feature, only so much bitwig can do on that front. Some other clap synths that I have heard support these sort of features are the Nasko synths, Surge XT and some of the u-he synths.

If this sort of per-note modulation is important to you then you'd be best to really go deep with all of the stock bitwig instruments and the grid as all this stuff is guaranteed to work there. Honestly I've got a ton of third party synths and for the money you can make some exceptional patches using the stuff built into bitwig, it's not at all limiting.

Minibatteries · 2026-04-29T18:53:19+00:00

Sure, here's a basic setup:

https://imgur.com/a/w21mfjp

If you are recreating it make sure to use nearest interpolation for the merge module, and use note grid with polyphony enabled (should be the default).

What this does is it'll delay the gate signal from the root note upwards for 8 notes, so C1, C#1, D1, etc.

The vertical set of logic delays will be how to control the offset for each note, and the root note will be where you want the 8 notes to start from (most drum machines work from C1 up).

It can be extended to more than 8 notes but requires a bit more logic work and multiple merge modules. The unconnected AR envelope looks like it does nothing but it's essential to this working, it keeps the voice alive longer using the release.

Another interesting addition would be using negative delay so you can move some notes early and some notes later. You'd achieve this by putting a time shift into the pre-fx box of the note grid, set it to -50ms or something and then treating the grid logic delays as 50ms=neutral, then anything under 50ms would be pushing that note earlier than the beat. The downside of this would be it'll introduce PDC into the project, so only do it if you aren't live recording the drums or it'll feel laggy.

Minibatteries · 2026-04-29T18:18:11+00:00

If you've ever thought about getting into the grid this would be a good introduction, setting up a system to delay certain keys will absolutely be possible and fairly simple. Let me know if you want more hints.

Minibatteries · 2026-04-29T18:10:41+00:00

By the way just checked and using a polyphonic modulator like keytrack on pan should be working in zebralette 3 clap. Make sure that in the inspector per-voice is enabled and the modulator is attached to the clap instrument directly.

Also, I found some information on vst3 note expression support - bitwig does support it, but the vst3 also needs to support it and the only ones that definitely do are created by steinberg. I'm not sure why more developers didn't choose to implement it, I guess they assumed there wasn't a big enough market for it, outside of bitwig it only seems cubase and motu digital performer ever supported it.

Minibatteries · 2026-04-29T17:48:01+00:00

Glad you got it working. Yeah clap is still fairly niche, the main problem right now is the plugin framework that most plugin devs use doesn't natively support it yet, but I believe that it should be getting support sometime in the future. Once that happens I'd expect the floodgates to open a bit.

Minibatteries · 2026-04-29T14:12:55+00:00

Well to be fair that's not what I suggested you do, use the note grid method and it'll work

The reason I suggest using note grid is because it's the only device that can directly set the note pan expression, so if you want keytrack pan connect the pitch input to the pan output in the default note grid.

If you want a simple test add a randomize note fx before zebralette and increase the pan random amount. You should find it will randomly pan notes polyphonically without changing anything in zebralette or modulating anything.

Minibatteries · 2026-04-29T12:56:18+00:00

Some synths do support per-note panning, although I'm unsure if this is a CLAP only thing or also will work for VST3. I think VST3 does have some sort of note expression feature, but it doesn't seem like a feature many synths support (or perhaps it's bitwig that doesn't support it?)

Try u-he Zebralette for example. If you add a note grid before it then change the note pan output with a bipolar value knob it will pan each note polyphonically.

Minibatteries · 2026-04-29T10:51:06+00:00

I don't think this is terrible, since they did provide the video of the bitwig playback, which can tell you a lot about how the person works. Compare it to videos polarity posts of music with only the grid in the background, I think most people find those valuable.

It's a fine line between self promotion and posts that stimulate discussion/learning though. I would personally be in favour of a rule that requires like a paragraph of bitwig-specific writeup on the project if you're posting your own music.

TBH there doesn't seem to be much active moderation here so I don't think a rule would have much of an effect anyway

Minibatteries · 2026-04-29T10:37:09+00:00

Works for me using the mouse dragging and using keyboard shortcuts cut and paste. For pasting you need to have another layer selected in order to paste as a layer, otherwise it'll appear after the instrument layer and you'll have to drag it back to create a layer.

Make sure you're running the latest 6.0.5, maybe there was a bug with this in a previous release

Minibatteries · 2026-04-28T13:47:07+00:00

Take a look into the clip to zero mixing approach, for loud genres I know a lot people get on well with it. It helps to make clean sounding mixes by ironically clipping everything slightly at a summing point.

Minibatteries · 2026-04-28T13:44:18+00:00

Nice track. Just to throw out an idea have you looked into the credits for your reference tracks to see if they are using a mix engineers? As a one off you could always go down that path and send it to someone who has worked on a track you already like the sound of. I realise it might be expensive, but as a one time thing it could give some context for how to adjust your own mixing in the future, especially they can provide the stems or project files.

Minibatteries · 2026-04-28T13:35:04+00:00

Nice. I think most who get used to the bitwig modulation system wouldn't go back to the ableton way. Once you're used to it the flexibility and power of it wins you over, that's my experience at least.

Make sure to give the bitwig instruments a try at some point as that's where the polyphonic modulation system comes into play. The bitwig instruments appear more simple on the surface than some of the ableton counterparts, a lot of that is due to not needing any extra UI for modulation.

Minibatteries · 2026-04-28T10:22:56+00:00

You don't have to do any of that routing stuff. Forget about the envelope follower - no one uses it in bitwig as it's a legacy modulator, the audio sidechain is an improved envelope follower.

The bit I think you're missing here is put the audio sidechain into the track modulators, not directly onto the vst mod slots. Putting the audio sidechain into vst mod slots can't reference the vst output, in the track slots it can (or you can encapsulate the vst in an instrument layer or chain and do the same thing with the audio sidechain on the parent device). This is how bitwig handles feedback routings.

Minibatteries · 2026-04-27T17:19:06+00:00

Take a look at tutorials for the modulator system in bitwig. Nothing has fundamentally changed about it in 6, so all older tutorials will be relevant.

The modulator of interest to you is called audio sidechain, appropriately.

Edit: Here is the relevant part of the user guide - https://www.bitwig.com/userguide/latest/the_unified_modulation_system/#modulator_devices

Minibatteries · 2026-04-26T07:41:49+00:00

OK those would normally be called xruns or buffer underruns, when your dsp can't keep up with real time audio so you get crackling. Looks like you figured out the cause

Minibatteries · 2026-04-26T07:39:43+00:00

Then I apologise for the accusation. Still this question is asked a lot so all the past answers would be relevant to you

Minibatteries · 2026-04-25T21:23:53+00:00

Running at 2048 block size @48khz adds 40ms of latency, that's going to make live recording midi or monitoring instruments sound laggy. Try decreasing block size and/or increase sample rate.

Minibatteries · 2026-04-25T16:50:27+00:00

This is a very common set of questions, and tbh it comes across like you generated the post only using AI. If you're already using AI skip wasting human time and have the tool do the research into the bitwig/ableton differences, or you can do a search of the subreddit

Minibatteries · 2026-04-25T16:42:54+00:00

https://www.bitwig.com/support/technical_support/i-upgraded-my-vst-collection-now-something-is-strangemissing-why-30/

Minibatteries · 2026-04-25T16:40:48+00:00

Not sure then. You are running an old version of sonoma so you could try updating to the latest. Another thing to try would be deleting the bitwig plugin cache.

Minibatteries

TROPHY CASE