Tags: posts polarity-music Bitwig Tutorial

Bitwig Studio External Audio Editor Workflow for Sampler

Tutorial | Jun 22, 2026

Edit Bitwig Studio 6.1 samples live in Ocenaudio and update Sampler instantly; use Collect and Save to avoid changing original files.

Quick Answer

Short Overview

Bitwig Studio external audio editor workflow lets WAV files update live inside Sampler and audio clips after saving changes in a third-party editor such as Ocenaudio. This matters because it removes the usual bounce-and-reimport cycle for simple sample edits like trimming, normalization, and fade-ins or fade-outs, making sample preparation much faster inside a project.

The method works especially well for recordings stored in the project folder, while imported library samples should be copied first with Collect and Save to avoid overwriting originals. It also highlights a practical gap in Bitwig 6.1: external file updates are recognized in Sampler and audio tracks, but not consistently in Convolution, even though drag-and-drop now allows audio files to become convolution impulses automatically.

Key Takeaways

Bitwig Studio 6.1: Editing Sample Files Externally and Updating Devices in Real Time

Bitwig Studio 6.1 supports a practical workflow that makes external sample editing much easier than before: audio files used inside a project can be edited directly in a separate wave editor, saved, and then updated automatically inside Bitwig.

This works especially well for samples used in Sampler and for audio clips that reference files stored in the project. It reduces the usual bounce-and-reimport cycle and makes quick destructive edits, such as trimming, fades, or normalization, much faster.

What It Does

When a sample file is used in Bitwig and that same file is opened in an external audio editor, saving changes to the file can cause Bitwig to detect the update and refresh all places where that file is referenced.

That means a single edited WAV file can update:

This is useful because Bitwig itself does not always provide the fastest path for destructive sample editing. Normally, a sample may need to be placed on an audio track, edited indirectly, bounced or normalized into a new file, and then dragged back into Sampler. External editing avoids much of that friction.

How It Works

A simple example starts with a recording made inside the project:

  1. Record a sound, for example with Polymer.
  2. Locate the resulting file in the project’s master recordings folder.
  3. Drag that file either:

At that point, the sample exists as a file on disk inside the project folder.

If the file name shown in Bitwig is dragged into an external editor such as Ocenaudio, the audio file opens directly. After making edits and pressing Save, Bitwig detects that the file changed and refreshes the sample in place.

Typical edits include:

Because the original file itself is being modified, every Bitwig reference to that file updates together.

Workflow

Edit project recordings directly

This workflow is safest and most convenient when the audio file already lives inside the current Bitwig project.

Typical process:

  1. Record audio into the project.
  2. Load the recorded WAV into Sampler or place it on an audio track.
  3. Drag the file into an external editor.
  4. Edit the waveform.
  5. Save the file.
  6. Let Bitwig refresh the sample automatically.

This makes external editing feel almost integrated into Bitwig, especially if the editor is kept visible with an always-on-top utility.

Use Collect and Save for library samples

Extra care is required when the source file comes from a general sample library rather than from the project folder.

If a drum loop or other sample is dragged into Bitwig from a samples directory and then opened in an external editor, editing and saving that file will modify the original file in the library. That is usually undesirable.

To avoid that, first use:

File → Collect and Save
with the option to collect files outside the project folder.

This copies external samples into the Bitwig project folder. After that, the copied version can be edited safely without changing the original library asset.

In the project panel’s Files section, the copied file can then be confirmed as part of the project.

Practical Uses

This workflow is especially useful for:

A good example is loading a long drum loop into Sampler and deciding only the first transient or first few hits are needed. Instead of creating a new bounced file inside Bitwig, the project copy of the loop can be opened externally, cut down, saved, and immediately updated in Sampler.

Convolution drag-and-drop in 6.1

Bitwig Studio 6.1 also adds another useful behavior: dragging an audio file after an instrument can create a Convolution device automatically instead of a Sampler.

This is a convenient way to turn an audio file into an impulse response workflow. For example, a recorded burst of noise or synthetic sound can be dragged into the effects chain after an instrument, and Bitwig interprets it as material for convolution.

However, there appears to be an inconsistency here.

The same external-edit-and-save approach does not currently update the loaded file inside Convolution in the same way it updates Sampler or audio-track references. The source file can be edited and saved, but Convolution may not refresh automatically. That behavior looks incomplete and would benefit from improvement.

Limits and caveats

External files can be overwritten

The main risk is editing original files from a sample library. If the file has not been copied into the project folder first, saving from the external editor changes the source asset permanently.

Using Collect and Save is the safe solution.

Some file metadata or naming behavior appears inconsistent

There are cases where Bitwig seems to retain stale metadata or display outdated information after files are edited or renamed. Renaming the copied file inside the project can help clarify which file is being used, but some display behavior appears imperfect.

Convolution does not refresh reliably

As noted above, Convolution does not currently seem to update in real time from external edits the way Sampler does.

No built-in “Edit in External Editor” command

The workflow works, but only indirectly. The current method is to drag the file into a separate application manually. A built-in command would make this much more efficient.

Renaming samples correctly in Bitwig

Bitwig’s renaming behavior can be confusing because not every visible label refers to the actual file on disk.

Important distinction:

Renaming from the clip level may only rename the clip object. Renaming the actual audio event can propagate the name more broadly across project references.

This is useful in larger projects where locating the correct file in the file list becomes tedious. If the waveform itself is selected from inside the clip, renaming there can update the relevant sample name across the project.

Sampler also reflects renamed sample files more clearly in many cases, which helps when building multi-sample patches and cleaning up file names.

Suggested improvements

Several additions would make this workflow much more discoverable and reliable:

Bitwig already includes commands such as revealing files in Explorer, so adding an external-editor action would fit naturally into the existing workflow.

Why this matters

For sound design and sample preparation, destructive editing is sometimes the fastest option. A lightweight external wave editor can be better suited for quick fades, normalization, trimming, or direct waveform cleanup than staying entirely inside the DAW.

With Bitwig 6.1, project-based sample editing through an external editor is now viable enough to feel like a legitimate production workflow rather than a workaround. It is especially effective when working with recorded material stored in the project itself, and it becomes safe for library material once Collect and Save is used first.

The result is a faster loop between recording, editing, and reusing samples inside Sampler and audio tracks, while keeping Bitwig updated in near real time.

Transcript

This is the transcript of the video. The text was generated automatically and may contain small mistakes. The timestamps jump to the matching part of the video.

Click to expand transcript

[00:00:00] So, I want to show you something in Bitfig Studio I recently discovered by accident and
[00:00:04] maybe this is already common knowledge, so sorry for that if it is.
[00:00:08] But I just accidentally discovered this and I remember trying this before in earlier versions
[00:00:14] and it never worked but now it does.
[00:00:17] So at some point I implemented this feature, maybe it isn't a feature at all but it kind
[00:00:24] of is a legit workflow I would say.
[00:00:27] So let's record something here with Polymer first so I can show you what I mean.
[00:00:33] I use maybe here this, let's use this one.
[00:00:40] So we record something here with the master recording, I just play a note.
[00:00:52] That's enough, I just hit stop.
[00:00:54] And you know we can find this now here inside of the master recordings folder inside of
[00:01:00] the current project so it doesn't show up for some reason, we have to double click here.
[00:01:06] So now what we can do is we can drag this into Bitwig here as an audio file and we can
[00:01:11] also drag it here to the left side so it creates a new sampler with a sample inside of it.
[00:01:19] So the problem now is we want to edit this file here, maybe we want to make it shorter
[00:01:25] or we want to add here some kind of fade out at the end and it's not really possible.
[00:01:31] What we have to do is we have to use this audio clip or we have to drag it into an audio
[00:01:36] track here and then we make some edits to it and then we have to right click and normalize
[00:01:42] it or maybe bounce it to audio or whatever to receive actually a new audio file.
[00:01:48] And then this new audio file we can drag back into the sampler so it's a bit tedious
[00:01:53] to do.
[00:01:54] So what I found out is that we can actually open up an external audio editor and I'm using
[00:02:01] here Ocin Audio, I'm using this for a very long time now and it's completely free and
[00:02:07] it remembers or it reminds me of cool edit from back in the days.
[00:02:12] Anyway, so what we can do now is we can just click on this name here on this WAV file and
[00:02:19] just drag it into Ocin Audio and it shows up in here.
[00:02:24] So we can also make this here on top, always on top on Windows, I use Power Tools, we use
[00:02:30] Control Windows and T as always on top.
[00:02:34] So even when I click here into Bitwig in the back.
[00:02:39] So yeah, so what we can do now is we can say we want to select everything and normalize
[00:02:45] it or maybe want to add here and fade out or maybe also fade in.
[00:02:54] So now how do we get this back into Bitwig?
[00:02:56] Very easy, we just hit save because we edit here this file directly.
[00:03:01] So all I have to do is just hit save and you can see in the back end here on the background
[00:03:06] Bitwig updates the file inside of the sampler instantaneously and also the file on the audio
[00:03:13] track.
[00:03:14] So what this means is we can actually have these files open inside of Ocin Audio and
[00:03:21] then hit save and when the file is updated Bitwig recognizes that the file actually changed
[00:03:27] and they update all these individual instances.
[00:03:31] And I remember trying this back in the day or maybe a few versions ago and it never really
[00:03:37] worked but at some point they implemented this.
[00:03:41] So try this out, this is a very powerful technique because it allows you to edit actually files
[00:03:47] on the fly.
[00:03:48] So here we have now, let's say, yeah, fade in and fade out and we can use this of course
[00:03:57] and play it or maybe we think this is way too long, right, so we can just cut it short
[00:04:09] then hit save and we have a new file that's much shorter.
[00:04:14] And this is very important because I showed you in my live stream about 6.1 when I sometimes
[00:04:21] use the sampler for, let's say, I have here drum loops or these drum loops are actually
[00:04:28] in my sample directory.
[00:04:31] So these are not inside of the project here, that's very important.
[00:04:36] So let's drag in some samples or drum loop here from my samples directory into Bitwig
[00:04:41] and I have this now inside of the sampler and now I see, oh, this is actually way too
[00:04:48] long, I only need to hear maybe the first parts or the first hits of this drum loop.
[00:04:53] So you think, well, let's open up here, Ozone Audio, drag this in and then edit the stuff
[00:05:01] and then maybe just delete the rest of it.
[00:05:03] The problem now is that you edit actually the original sample inside of my samples directory
[00:05:12] which is not what I want because I want to keep the original drum loop intact.
[00:05:16] I don't want to change it at all.
[00:05:18] So what you need to do is you need to, let's say, go to Bitwig here and save your project,
[00:05:27] test project and you need to do a collect and save.
[00:05:33] So with this here, collect files outside of the project folder.
[00:05:38] With this you copy or clone or yeah, it's copy.
[00:05:41] You copy the original sample into the project folder of this Bitwig project here.
[00:05:49] So now you can see here when you go to files, project panel files, you can see this file
[00:05:56] now is a copy of the original and is located inside of my project folder.
[00:06:03] So we can edit this now, which is which, I don't know, just close this here.
[00:06:12] So here we can now just delete this stuff, hit play, something like this.
[00:06:20] And then we hit save and it updates this stuff here without actually updating my original
[00:06:28] file here, which is not really recognized there.
[00:06:35] But you don't change the actual file or the original file, right?
[00:06:43] It stays with the same length.
[00:06:46] I think this is here, this is here just a bug they need to fix.
[00:06:49] They probably take the metadata because it's the same name here, right?
[00:06:54] And what we can do is probably just to rename this here with control and R and say my drum
[00:07:00] loop and then move this out, drag this in, now it's still remembering the old metadata.
[00:07:14] So this is probably a bug they have to fix, but you can do it in this way.
[00:07:18] You have to make sure that you copy actually the files from our original directory into
[00:07:23] your project folder by using collect and save instead of then editing the original file,
[00:07:31] which is not what you want because you can mess up your original files, right?
[00:07:35] This is all you have to keep in mind.
[00:07:38] But if you just use samples from within the project like I did here, right?
[00:07:44] I recorded this into Bitwig into the project directory and then I create my own files and
[00:07:50] then I want to quickly edit them.
[00:07:53] It's much easier this way by using an external editor with Ozone Audio here.
[00:08:02] What you also can do is if you use multiple files, you can see we have some kind of tabs.
[00:08:08] You can have all the files in your project open inside of Ozone Audio and edit all the
[00:08:13] time or just listen to them.
[00:08:16] So it's basically a really nice way of editing files in your project with an external application
[00:08:25] and feels like it's actually part of Bitwig Studio, because every time you hit save, all
[00:08:31] the audio files inside of the Bitwig project are updated in real time.
[00:08:36] What's also pretty new in Bitwig 6.1 is that you can drag in audio files and it becomes
[00:08:42] a convolution reverb.
[00:08:44] This is very new and I can show you this here maybe with a test, maybe make the smaller
[00:08:49] here test tone.
[00:08:53] Let's say we have here white noise, bit of white noise, maybe a bit of e-queuing, something
[00:09:07] like this and record this, or maybe use an FX grid, because inside of the FX grid the
[00:09:21] noise is stereo, which is much more interesting.
[00:09:37] Okay, cool.
[00:09:45] So now we have here at least some kind of, where is it?
[00:09:57] Yeah, that's that.
[00:10:01] So we can say, oh, we have here this kind of audio thing or synthesizer thing and we
[00:10:06] drag this in here and it says insert convolution.
[00:10:11] It sees that we have here actually already an instrument and we drag this sample after
[00:10:16] this instrument so it can only become some kind of convolution reverb.
[00:10:20] And you have the same problem here, we have this convolution sample in here, but we want
[00:10:27] to edit this.
[00:10:28] So we can do the same thing here, we can open up our editor and drag this in, which is not
[00:10:35] working, which should work in my opinion, but we can drag this in here and then say,
[00:10:40] make your very long fade out or make it even shorter, make it something like this, then
[00:10:48] hit save, control + S. Updates, it doesn't update here the convolution reverb, but also
[00:10:56] should work in my opinion, so maybe they can fix this.
[00:11:01] So now we have here a reverb or another reverb, maybe it was maybe a dry polymer and some
[00:11:14] overtones, so yeah, in my opinion they should add this here also to the convolution reverb
[00:11:33] so it updates when I update the file outside of Bitwig Studio and in my opinion maybe at
[00:11:39] everywhere you have these names, these waveform or wave file names, some kind of right click
[00:11:47] and then edit an external editor and you can define inside of the settings maybe an external
[00:11:52] editor here in the audio or maybe behavior or whatever, maybe locations, you can define
[00:11:59] oh here, this is the editor I want to use, so I don't have to drag and drop all the time,
[00:12:05] so I can just right click and say edit or maybe a small little button or icon here,
[00:12:12] so I click on it and then it opens up the file inside of my external editor, this would
[00:12:17] be really nice to have also here of course in the files tab and here in this tab, so
[00:12:24] everywhere you have more or less these files, you can just press a button or use right click,
[00:12:31] so an explorer is already here, so why not add an external editor, it's probably not
[00:12:36] a big thing for Bitwig to implement these changes in my opinion, so yeah, this is also
[00:12:43] new in Bitwig 6.1 that you can drag in a sample after the instrument and it becomes automatically
[00:12:50] a convolution reverb instead of adding a new sampler, you know, after an instrument which
[00:12:56] makes no sense, so yeah, pretty cool to have.
[00:13:02] Also important to know in my opinion is renaming, I already showed you that you can rename on
[00:13:08] the right side here by using control and R just to rename something, so here you can
[00:13:15] see we have the sample inside of convolution and you want to rename it, we say convolution
[00:13:24] to test, right, and then it should update you actually the name because it does for
[00:13:29] the sampler, let's use this here inside of the sampler, contest and we want to rename
[00:13:33] this to my sample and it shows you here the name, because sometimes you create a sampler
[00:13:40] patch with multiple samples or multi-sample patch and then you want to rename some of
[00:13:47] the samples because there is, I don't know, something in there you don't want to have
[00:13:50] in there maybe minus bounds what Bitwig creates automatically all the time and you want to
[00:13:56] rename this, you can do this on the right hand side here and it updates all the names
[00:14:02] inside of the project.
[00:14:05] Also when you have here an audio clip and you have to know that this is actually not
[00:14:11] the audio file, this is the audio clip, you have to click into or go into the sample or
[00:14:17] into the audio clip and then you can see here the audio event and this is actually the sample
[00:14:23] itself, the waveform itself and also here you can use control and R and you can say
[00:14:32] this is my sample and then rename it and then it renames here, it renames it here and if
[00:14:40] you go back out I think it also renames it here.
[00:14:44] So just changing this here, it doesn't change the file name or the file name itself, you
[00:14:54] just rename more or less the audio clip.
[00:14:57] You have to go into the audio clip and then you can see the audio event inside of the
[00:15:03] audio clip and this is the real waveform that you have to rename.
[00:15:09] So I do this also sometimes if I'm too lazy to find actually the file inside of the list,
[00:15:16] I have a big project, a lot of files, audio files in there and I just want to rename this
[00:15:22] audio clip here, how do I find it in here?
[00:15:25] There's no right click and show me inside of the file list, it's not there.
[00:15:31] So what I have to do then is I have to go into the audio clip here and rename it at this
[00:15:36] position and then every other instance is also renamed.
[00:15:40] So this is also something not everyone knows but it's pretty important, it's a bit quirky
[00:15:46] inside of Bitwig to work with files but that's how it is.
[00:15:53] You can work around it and I wish this would be much more clearer.
[00:15:59] So yeah the only thing I probably want to have from the developers in 6.1 is that we
[00:16:05] have here maybe additional button and you can press on the button and it opens this
[00:16:09] up then in an external editor.
[00:16:11] You can define an external editor in the settings with just the basic path, very simple or maybe
[00:16:20] if this is too much right click here on the file name everywhere you see a file name just
[00:16:25] right click and say edit in external editor, maybe also in here right click edit in external
[00:16:31] editor.
[00:16:32] And then you hit save in Ozen Audio and everything updates.
[00:16:36] This would be a very nice workflow.
[00:16:40] And also I want to make some tutorials on the sampler here in the future on this channel
[00:16:46] but I feel like the sampler needs a bit of work or some of the stuff is not really finished.
[00:16:54] So for instance here the tuner, I saw the tuner looks completely different on macOS and
[00:17:00] Linux than on Windows so it's missing here some pieces.
[00:17:04] So I don't want to make some tutorials on stuff that it's probably going to change in
[00:17:09] the near future and also here the sampler I showed you this in the stream already some
[00:17:16] of the pitch detection is not 100% correct so I'm waiting a bit until this is fixed because
[00:17:24] I have some ideas how to use this you know how to incorporate this into workflows and
[00:17:29] I want to show this and of course when I show it I want to have it correct.
[00:17:34] So I'm waiting a bit until they maybe bring some updates to it and then I make some tutorials
[00:17:41] on this stuff.
[00:17:42] But besides that I really like the sampler I really like what they added to 6.1 it's
[00:17:49] a really nice update.
[00:17:51] I wish we had this a bit earlier but you know it's a small team we know all the things so
[00:17:58] I'm not mad or anything it's just you know cool that we have it now and I'll probably
[00:18:03] gonna release a lot of presets for the sampler yeah just watch the space.
[00:18:11] Okay that's it let me know what you think in the comments down below about these things
[00:18:15] here with the files and some of your ideas maybe feedback maybe I'm probably the last
[00:18:22] one discovering this.
[00:18:24] But yeah I remember trying this in earlier versions a bit bigger and never worked for
[00:18:31] me.
[00:18:32] Anyway thanks for watching see you next time bye.

Related reading

Bitwig Studio 6.1 Sampler Live Select for Smooth Crossfades Tutorial

Bitwig Studio 6.1 Sampler Live Select for Smooth Crossfades

Learn how Bitwig Studio 6.1 Sampler Live Select Updating enables smooth multisample crossfades for strings, pads, and expressive custom libraries.

 Bitwig Multi-Sampling Workflow - Create Reusable Multi-Sample Patches from Plugins Bitwig Guide

Bitwig Multi-Sampling Workflow - Create Reusable Multi-Sample Patches from Plugins

To create a multi-sampler patch in Bitwig Studio, set up clips for each key and velocity layer you want to sample, then bounce these clips to audio files with clear naming conventions for easy organization. Once all samples are exported, drag them into Bitwig’s sampler, sort by file name, and manually assign velocity and key ranges for accurate mapping. Save this project as a reusable template, making it quick and efficient to sample any device or instrument in the future.

 Sampler Power Tips Slicing, Stretching Production Techniques Tutorial

Sampler Power Tips Slicing, Stretching Production Techniques

The sampler in Bitwig is a highly versatile tool that allows users to create a wide range of sounds by slicing, stretching, and creatively modulating samples, making it possible to produce entire tracks with just a few devices and effects. The guide demonstrates practical techniques for syncing drum loops to project tempo, slicing samples, and turning any audio into instruments or pads using modulation and filtering, offering endless creative possibilities without the need for additional plugins. By experimenting with simple recordings and leveraging Bitwig’s modulation system, users can achieve unique and professional results, illustrating the sampler’s power for music production.

 Bitwig Studio 6 Features Overview: What's New in Version 6 Talk

Bitwig Studio 6 Features Overview: What's New in Version 6

Explore the main new features in Bitwig Studio 6, including alias clips, automation upgrades, scale tools, editing changes, and workflow improvements.

 Bitwig 6 Release Date and New Features: Beta Timeline, Piano Roll, and Arranger Talk

Bitwig 6 Release Date and New Features: Beta Timeline, Piano Roll, and Arranger

Looking for the Bitwig 6 release date and what changed in the update? This page covers the August 27, 2025 beta announcement, the expected rollout pattern, and the main Bitwig 6 focus areas like piano roll and arranger improvements.

 Discovering a New Way to Browse and Export Samples with XO in Bitwig Studio Tutorial

Discovering a New Way to Browse and Export Samples with XO in Bitwig Studio

I recently discovered that you can use XO as a sample browser in Bitwig Studio. By holding control and dragging samples out of XO, you can put them in samplots, drum machines, tracks and clips. You can also use a drum sequencer with the same mapping as XO and export the entire drum hit or individual samples. This makes it easier to review samples, select the right sample and quickly drag them into Bitwig. It's the missing sample browser I always wanted and makes for an efficient workflow.