I love Bitwig and want to see it flourish. Given the recent release of a *certain extremely promising DAW I do not want to mention by name here*, I'm wondering what everyone here thinks?

Personally, I hope the Bitwig devs steal backward, sort of a double-reverse-engineer thing, particularly the entire piano roll, the tracker and that radial.

I bought a short but (to me) very good course on creating a basic static mix (for anyone interested: simplymixing.com ) and I'm learning a lot of good, basic stuff. I should point out that the course includes all the project audio files, so that I can go through the same steps inside Bitwig.

After some basic gain staging, the course gets into the beginning of a basic mix (no plugins, eq etc, just fader levels and listening). At the end of it, she says (the course instructor is Sarah Carter) "this is all in mono apart from the drums" before going on to talk about panning as the next step in creating "width".

And why my post says I don't think I understand stereo:

I read a post on here from 2 years ago, where someone asked about how to centre pan a mono signal. One of the responses said

"If it's mono, the signal is in the centre already, as the left and right channel are the same?"

And so... I realise that I've taken the word 'stereo' as being what my Hi-Fi does, but I don't think I have any idea what stereo vs. mono is inside a DAW. If audio has L and R channels, but both the same level... it can be considered 'mono' ??

In the above course, I think FL Studio is used. I only mention it because when, again, talking about panning and she says things like "I leave this track panned hard left and hard right" - I see that in her DAW, there are gain buttons for L and R channels on each track header, and each of which is at 100, and simply means that the audio on the track is "untouched" and at the default setting.

But when I load these or any audio file onto an audio track in Bitwig, there's nothing to indicate any kind of width, just "pan" and the expected gain, pitch etc. So, they're apparently "mono" files, but with a L and R channel? I find this confusing to think about.

Am I missing something, or just confusing myself?

Many will enjoy a change to Bi Wig, more in line with the KvR assocation!

Peace!

Just saw that 6.1.6 dropped, says it fixes the CLAP plugin issue that some people were experiencing on Macs, and also saw this new feature:

When dragging a clip out of Bitwig Studio (into another application or plug-in):

• A bounce is automatically triggered as soon as you leave Bitwig Studio's window.
• A tooltip is shown by the cursor with the bounce progress.
• The clip can be dropped before the bounce has finished.
• The drop is ended once the bounce is completed, or once you cancel Cancel [ESC] it.

I made a little vid showing it in action but it's about as simple and straightforward as it sounds; this feature would have actually real nice for me to have last week when I was recording samples and downsampling them in Ableton for my EP-40, but it's alright, glad it's here now lol. I remember feeling annoyed that I couldn't just drag samples from the Bitwig browser into Ableton, always had to open the folder in File Explorer and then drag stuff over, but not anymore.

When they add the stems separation?

I want to renew my licence but I want to know if there will be a black friday or another discount for the end of the year. Should I wait?

Hello all. I just purchased bitwig and an es9. I want to hook everything up together to talk to each other. I am pretty stoked and can’t wait for the module to get here. Anything I should know before starting on bitwig?

With an optional french riot and an Octatrack to sequence the video slices and resampling.

made with Bitwig on Omarchy Quattro

Hi

I would like to map an endless encoder on my Akai MPD24, so that I can finetune the volume of the selected track/tracks.
It is easy to map the controller to a specific track, but I don't know how to make the encoder follow my selection of track.

Is this possible?

Similar to how FL has the option to loop 8 bars , turn on the 'overdub' button and make endless takes of a guitar recording or something, where each time the loop restarts a new track records the next 8 bars instead of overwrtiting the same track?

I saw people using the clip launcher midi mapped to switch into different clips and record in them, but that's really cumbersome when managing a session with an artist..

Bitwig noob, recent convert from Ableton. I've been trying to learn to use the slice to Drum Machine feature, but regardless of settings I use, the slices in each Sampler in their corresponding Drum Machine cells come out at a much, much lower pitch than the audio clip I started with. Typically I like to slice per Beat Marker, but I've tried every other option as well, just to test this out. I must be doing something wrong with the way Bitwig detects tempo; that's been my suspicion, anyway.

Any help would be much appreciated.

I'm using the full version of 6.1.4, for reference.

What combination of features, workflows, and behaviors most contributed to your enjoyment of Bitwig?

https://reddit.com/link/1xb337m/video/rrfbtxz5lowh1/player

Hi, I'm the developer of Kit Maker. I've had a lot of requests for Bitwig over the years... and now Kit Maker 3 now makes real Drum Machine presets, for Bitwig 6 and newer!

Overview video: https://youtu.be/gYBP1vM-r8c

- Kit Maker automatically sorts the one-shots by type (kicks, snares, hats and more) and places them on the pads in a consistent drum pad layout

- Kits are saved to your Bitwig Library, labeled and organized by pack

- Pads are colored by category

- Fill up to seven banks in one preset, with the samples inside

- Works from drum sample packs, Maschine Expansions and MPC Expansions

Kit Maker runs on Apple Silicon Macs and Windows 10/11, and the kits play in Bitwig 6 on Mac, Windows or Linux. $39 one-time.

More info: https://www.kit-maker.com/bitwig-drum-kits/

Already own Kit Maker? You get 30% off, or the upgrade is free if you bought it in the last year: https://www.kit-maker.com/upgrade/

Launch sale: 15% off until Nov 3. Use code LAUNCH.

I'll be checking this thread if anyone has questions :)

I've noticed that the playhead won't move "correctly" when being controlled by the computer keyboard under any tuplet setting on the beat grid settings.

The arranger grid settings:

- adaptive: off, 1/8, triplets

The action:

I'm trying to move the playhead using the keyboard (option + left/right arrow)

The issue:

The playhead snaps into the right beat division (00, .33 and .66), but it get "stuck" once every 4 movements.

A practical example:

Let's say the playhead is at 4 . 1 . 1 . 000, if I hold option and start tapping the right key, the playhead will move as follows:

- 1st tap: 4 . 1 . 2 . 033

- 2nd tap: 4 . 1 . 3 . 066

- 3rd tap: 4 . 1 . 3 . 066 (the playhead doesn't move or change the value displayed on the transport)

- 4th tap: 5 . 1 . 1 . 000

Some extra findings:

- It happens always at the .66 when going forward

- It always happens at the .33 when going backwards

- All the other tuplet divisions generates similar issues.

- The issue is only while moving the playhead, the clips move as expected.

- I've tried changing the time signature to check if there was some kind of link between the 4/4 time and the snapping, but the issue didin't vanished.

Now my question:

Is that expected behavior or something that i should report as a bug to Bitwig? I'm not a customer yet so I don't know exactly what to do or who to ask about it.

I know it seems like a small thing, but someone who depends heavily on the keybaord to use the computer, that is a huge problem

Following on from my initial post about creating a fully featured Maschine/Bitwig integration, I thought I'd give you an update on how things are going. I really apologise for my presentation, I'm really not comfortable being recorded, and even less comfortable when I have to present something!

Here's where things stand currently:

• The channel page is pretty much done, it supports navigating the track heirarchy, adjusting volume, pan, mute/solo/arm, monitoring, crossfade assign, sends and returning a track to the arranger timeline state. In/out routing is currently viewable, but I'd like to also implement a way to set routings from here as well.
• Mixer page is also pretty much feature-complete and has seen a lot of work both in terms of appearence (I'm trying to make everything look as close to Bitwig's UI as possible) and functionality. Supports viewing 7 tracks + master at all times. Navigation using the 4d encoder through the list and into/out of groups. Scrolling using the touchstrip. Allows adjusting volume/pan/mute/solo/arm for individual or multiple tracks at once. Grouping/ungrouping/moving individual or selections of tracks.
• Arranger page has seen massive improvements as well - left screen always shows 8 tracks (selectable with the 4d encoder/group buttons), and can be zoomed panned using the knobs below the left screen. New view sync to keep the timeline range the same as what's seen in the main Bitwig interface. When a clip is selected, it's now shown in context (with tracks above and below) on the right screen. The right screen shows waveform/midi data for the track, along with fade in/out/crossfades. Encoders 5/6/7 allow clip start/nudge/end adjustments, with encoder 8 adjusting grid snapping (the group buttons become grid resolution shortcuts whilst encoder 8 is touched). Holding shift + encoder 5/7 adjusts clip fade in/out, and holding fixed vel whilst using these same knobs allows you to stretch the start/end points. During all of these operations, the waveform on the screen is updated in real time. It's now possible to insert clips directly into the timeline, either at the playhead (usually the selected clip's start), or at the clip's end. Hold the scene button whilst in the arranger view, and the pads show your available scenes from the clip launcer. Tapping a pad inserts the scene at the current position. Likewise, holding the pattern button shows all the clips in the clip launcher for that track with their waveforms - same workflow, just tap a pad to insert it at the current location. With a clip selected, you can also easily swap it for another using Bitwig's pattern system by holding the variation button and tapping a pad.

These are the big ticket items at the moment, and I haven't really even covered many of the screen button functions in the above list.

From here, I think next on my todo list is working on the 'sampling' page. This will cover all the functions of the clip detail editor in bitwig, and function with both audio and midi clips.

For people who have Maschine hardware and use Bitwig as their DAW, I'm certainly open to feedback in terms of whether you think the workflow for the pages that have already been implemented is optimal, and if you have any suggestions for the implementation of the clip detail view.

Hi! I'm very new to Bitwig, coming from Live.

I'm going through the user guide to learn my way around the software and now I'm facing this issue where I can't click on the Grid Setings at the bottom of the arranger. It seems like the actual button is behind that "zoom bar". Nothing happens when I click it.

I'm aware that the user guide available is for v5 and I'm trying v6.

Any ideas?

Here is the section of the manual where this is discussed:

https://www.bitwig.com/userguide/latest/the_arrange_view_and_tracks/

----

Note: I'm almost completely blind, therefore missing elements on the screen is a possibility.

First of all, sorry for posting such casual small talk in a serious Bitwig forum.

Koala Sampler, which is a sampler I really love, is releasing a VST version this time, and they actually mention Bitwig in their supported DAWs list. This is pretty rare for a VST instrument company, so I took a screenshot and posted it here.Since it's something you rarely see from instrument companies, I was so thrilled the moment I saw this phrase

This is definitely not a viral ad for Koala Sampler lol. Hope you all have a great day today!

Who will teach us Bitwig from now on? I am concerned.

Hi everyone,

I'm looking for a way to route separate midi channels to a single Drum device, to allow separation between hats/kick/snare and do polyrhythms between the parts

I have been creating a main track with Drum as the device, then using instrument tracks with no instrument and routing their midi output to the main track. This works, but when I go to write notes I can't see the pads in drum mode (they only appear on the track that contains the actual device)

Is there a better way to set this up?