State of Bitwig Studio

Tutorial | Jan 14, 2025

In this video, I discuss my thoughts on the recent updates to Bitwig Studio, including the release of Bitwig Studio 5.2 and the upcoming 5.3. I express my frustrations with certain features that seem disconnected and my wish for a more modular and integrated approach, especially in the areas of interface design and note handling. Lastly, I invite viewers to share their thoughts and desires for future Bitwig updates in the comments.

You can watch the Video on Youtube

• support me on Patreon

Summary #

Maybe you don't watch the video, here are some important takeaways:

In this video, I address a comment accusing me of being paid by Bitwig Studio and decided to create a "State of Bitwig" video. I discuss the developments, features, and issues surrounding Bitwig Studio, specifically highlighting changes from 2024, including the release of Bitwig Studio 5.2 and the anticipation of 5.3.

I start by explaining my mixed feelings towards the new devices introduced in 5.2, acknowledging their great sounds and enhancements, yet questioning their necessity for my workflow. For example, I find some devices overly complex, like the compressor, which makes me prefer older, simpler versions. Additionally, I point out the advantages of the precision editing and improved GUI system, which now utilizes the GPU for smoother performance and frees up CPU resources.

Despite these improvements, I express frustration over some aspects of Bitwig Studio, particularly the lack of integration between different sections, like the Stepwise sequencer and the Grid, which seem disconnected. Similarly, the Recorder in the Grid can record audio but lacks playback features, unlike the feature-rich Sampler that can't record. I highlight the need for a unified approach that merges these functionalities.

I further delve into issues I face with audio and note handling in Bitwig Studio. For instance, there's no way to import note signals into the Grid from different channels, and the note grid's voice handling and voice stacking capabilities feel limited. I lament the absence of a modular and customizable interface for the Grid, which would greatly enhance usability and creativity.

I also discuss the absence of essential features, such as a pitch adjustment in raw or re-pitch modes for audio clips, a hinderance for creating beats and loops directly in the arranger. The unwanted comping feature while recording is another annoyance, as it complicates the audio editing process that was simpler in earlier versions.

Looking to the future, I hope for improvements and modularity in the piano roll and note grid, suggesting the implementation of customizable features, scriptability, or even visual guides to aid in music composition and theory.

Ultimately, I convey my appreciation for Bitwig Studio's progression but also voice my hopes for enhanced integration and creative freedom in forthcoming updates. I invite viewers to share their thoughts and desires for Bitwig's future versions in the comments. Thank you for watching, and I’ll see you in the next video!

Transcription #

This is what im talking about in this video. The text is transcribed by AI, so it might not be perfect. If you find any mistakes, please let me know.
You can also click on the timestamps to jump to the right part of the video, which should be helpful.

[00:00:00] Hey folks, welcome back to another video and I got one comment that
[00:00:05] accused me of being paid by Bitwig Studio, right? So
[00:00:08] maybe it's time to do another state of Bitwig video
[00:00:13] to talk about some problems, maybe the future and
[00:00:17] what happened and what I don't like, what I like and so on.
[00:00:20] So they also sent out or Bitwig Studio sent out
[00:00:24] last year some kind of newsletter, looks like this here.
[00:00:31] What changed in 2024? Look back at Bitwig's milestones.
[00:00:34] In 2024 was a big year for us and so on. So
[00:00:38] they released Bitwig Studio 5.2 and it's interesting to me, maybe write this in
[00:00:44] the comments down below. Do you like actually these devices? Do you
[00:00:48] use these devices? Do you prefer these devices or something
[00:00:52] else like VSTs or so on? Let me know in the comments down below.
[00:00:56] Would be interesting. So for me it's like they are great.
[00:01:00] They sound great. I think they are great additions
[00:01:03] but it's not like something I really needed, if you know what I mean. It's not
[00:01:08] like, you know, that's important to me.
[00:01:11] So for instance I prefer the usual or the normal compressor over this one here
[00:01:16] because for me it's a bit overly complex in a way
[00:01:22] and I also have sometimes no idea what this thing is doing to my sound.
[00:01:29] So I usually go back to the old one because it has just three knobs
[00:01:35] and I know what they're doing and I can move on.
[00:01:39] Also here this sculpt, focus and tilt and over and so on.
[00:01:44] So over is great. It's a nice clipper. It's a nice addition
[00:01:49] but sometimes I just prefer my old hard clip preset because of the CPU usage.
[00:01:55] Then here these EQs. I guess they are great. They sound great.
[00:02:00] Probably I have no idea. I never used an original
[00:02:04] EQ analog EQ and I prefer normal EQs over that so I can dial in
[00:02:12] at a certain position, you know, a certain EQ boost and so on.
[00:02:17] So I never actually really used these.
[00:02:22] It's probably more interesting for mastering engineers and mixing engineers
[00:02:26] and so on but at the same time I guess no mastering engineer is using Bitwig
[00:02:31] Studio. I have no idea. Maybe they do.
[00:02:35] And then again they're probably using their own VSTs.
[00:02:41] I have no idea. It's just me. It's just a subjective opinion, a subjective
[00:02:47] view on this. Let me know in the comments down below what you think.
[00:02:52] So they're also just highlighted here only the big devices basically
[00:02:56] but if you go into this here you can see it's not just only the compressor on
[00:03:04] these devices but they're also here introduced some
[00:03:09] precision editing for the arranger which was a big thing. You can now use
[00:03:14] here a lot of key commands for that. Then they're also completely
[00:03:21] change the GUI system, the rendering system.
[00:03:24] Bring everything here to the GPU which makes it much, much faster and
[00:03:30] yeah, I guess high FPS. It's more smooth now, everything.
[00:03:35] And you, yeah, it frees up your CPU for processing, for audio processing
[00:03:41] which is a big deal and it was probably not an easy task
[00:03:44] like I said because they are releasing on
[00:03:48] different platforms on Linux, Mac OS X and Windows. So it's probably not an
[00:03:55] easy task. Undo for plug-ins pretty great actually.
[00:04:01] So there was a lot of changes here underlying systems that are revamped or
[00:04:08] made better or, you know, fixing bugs and so on. So it's not just these devices.
[00:04:14] It may be look like it's not much here from this picture but there was a lot of
[00:04:18] work involved, right? So they only released actually 5.2
[00:04:25] in 2024 and they announced Bitwig Studio 5.3. So it's not released yet.
[00:04:32] It's coming probably in the next days, next weeks, I don't know.
[00:04:36] Maybe this week, maybe next week. But here they announced Bitwig Studio 5.3.
[00:04:43] So again, this release here is for me like it's nice to have
[00:04:47] but it's not something I really needed. So these
[00:04:52] drum devices here are really great but if I need an 808, I just use the sample
[00:04:58] and move on. Maybe there are others that like to use
[00:05:02] these devices more over some samples. I tried to make them,
[00:05:07] I tried to use them here from project to project
[00:05:12] and they are sounding great. But it's again, it's not like I needed them in my
[00:05:17] life but they are great. They sound great and they work great.
[00:05:21] But then here's the stepwise and the stepwise, I was a bit puzzled
[00:05:26] or I don't know why they did this because this is like this typical
[00:05:30] Bitwig thing where they have like two words inside of Bitwig Studio and
[00:05:36] these two words never connect in a way. They are completely separate.
[00:05:42] So here's the stepwise. The stepwise is a step sequencer
[00:05:46] with a nice interface but it lacks features. It's just a simple step
[00:05:51] sequencer with just some rudimentary features.
[00:05:56] But then we have the grid. We could do everything that you can do
[00:06:00] inside of stepwise. You can do inside of the grid
[00:06:04] and add features on top of it. You can make it better
[00:06:07] and more feature rich. But the grid misses this interface.
[00:06:12] So you have these two words. You have the grid
[00:06:16] where you can do basically everything but it misses the nice interface.
[00:06:22] And here you have a device that has a nice interface but it misses the features.
[00:06:27] And you can't connect basically these two words.
[00:06:32] So this is kind of a problem in multiple areas.
[00:06:39] There's just the drums here. So yeah these two words and they never
[00:06:45] kind of connect. And this is also the case for
[00:06:49] let's go here into Bitwig Studio. If you have here the pulley grid.
[00:06:56] So inside of the pulley grid we have the recorder and I always
[00:07:00] kind of rant about the recorder all the time.
[00:07:04] Because the recorder just can record six seconds of audio
[00:07:10] and you can only play it back. There's no position.
[00:07:14] You can't change the position of the playback. You can't change the
[00:07:18] playback speed or the playback directions. Okay.
[00:07:22] So it misses a lot of features but you can record audio on the fly just with
[00:07:26] triggering here this input. So pretty dope. It's actually a
[00:07:30] playback buffer but it misses features. But then we have the sampler.
[00:07:34] The sampler is all the features we need or I need
[00:07:38] to make great sounding granular reverbs or granular effects.
[00:07:43] Right. Everything is in there. Cycles mode, textures mode.
[00:07:47] You can change the grain size, the position, the playback position.
[00:07:51] Everything. But it can't record.
[00:07:55] Okay. So this one can record. It misses all the features.
[00:07:58] This one can't record but it has all the features.
[00:08:02] There's no way to combine these two worlds. It's the same thing with the
[00:08:06] stepwise and the grid. Two worlds and you can't connect it.
[00:08:11] It's super frustrating because the solution is so close.
[00:08:14] You are so close to the you know but you can't connect it.
[00:08:18] It's just not just make it work. Right.
[00:08:22] What's the problem? And they released this this grid here a few years ago
[00:08:27] and it's like this for years and it's so frustrating.
[00:08:31] It's unbelievable. Just just connect it. Right. Make it make it work.
[00:08:38] What's the problem? I want to make some nice
[00:08:42] granular effects. I want to make granular reverbs
[00:08:45] and it would sound so nice really. But anyway that's
[00:08:52] that's how it is. Right. Then there are some other things here
[00:08:57] inside the grid. The trigger problem. Right. We have here a
[00:09:02] trigger module and we have a button.
[00:09:07] And let's take an oscilloscope here. Sorry.
[00:09:12] So yeah trigger sends out short bursts of a gate.
[00:09:19] Very short. Pretty easy. So you push it once and you
[00:09:23] make two things at once. You switch on and switch off.
[00:09:28] And then you have a button where you can switch on
[00:09:31] and switch off with two button presses here.
[00:09:35] And this is great inside of the grid but if you want to make an interface here
[00:09:39] right the button works of course only for the button.
[00:09:46] Switch on switch off. So if you want to make it work for the trigger
[00:09:52] first you can't actually modulate this here. It's not a modulation target
[00:09:56] for whatever reason. So you have to create some kind of
[00:10:02] logical system here to make it work. I posted something like this got
[00:10:07] lately which is super short. But why do we need this? Right.
[00:10:12] Why do we need to do this? Just make the trigger here maybe
[00:10:15] a modulator inside of the modulation matrix.
[00:10:21] Just make it happen. Trigger would be also nice in here to actually
[00:10:26] send out for the segments for instance a trigger signal. So how do we trigger
[00:10:33] these segments shapes here without using nodes? It's not possible. We can't use
[00:10:40] a modulator to trigger actually segments or maybe here the ADSR.
[00:10:48] Yeah why it's not possible. You always have to use a node input
[00:10:52] to actually trigger these modulators. It would be nice to have here
[00:10:56] a trigger input the gate input or just make the grid
[00:11:00] part of the modulation system. I have no idea. So it's also like we have this world
[00:11:05] of modulators that have a different ecosystem
[00:11:08] then we have the grid which is a different ecosystem.
[00:11:12] Then we have here if you have like an audio file. Let me put here something in
[00:11:19] there. You have an audio file right? You have here at the left side you have these
[00:11:24] pitch things you can't modulate or it's like you have different small little
[00:11:29] ecosystems inside of Bitwig studio and they don't connect for some reason.
[00:11:35] And sometimes it's frustrating and sometimes it's yeah I can't understand
[00:11:41] it because there are technical limitations of course and sometimes you
[00:11:44] need to pre-calculate something and you can't change it on the fly and it's
[00:11:48] you know real time is always something different than
[00:11:51] pre-calculated and so on. I get it but sometimes it's a bit
[00:11:57] frustrating. So away here inside of the modulation
[00:12:01] system to trigger actually ADSR or these segments here these envelopes
[00:12:07] would be nice to have. Also here a trigger modulator
[00:12:11] to actually send out the trigger inside of the grid. Speaking of the grid and I
[00:12:18] talked about this I think in the last video
[00:12:21] is we have here an audio sidechain to bring external audio signals into
[00:12:26] Bitwig or into the grid of the Bitwig grid.
[00:12:31] Into the grid of the Bitwig grid makes no sense. Into the grid of Bitwig studio
[00:12:34] sorry. So we can bring an audio signal but
[00:12:37] there's no way of bringing in a note signal from a different
[00:12:42] channel. I can select audio here that's possible but no notes.
[00:12:46] Why? Why is this missing? I have no idea. Probably also not the
[00:12:53] big thing to make this happen I guess. Just make it work Bitwig right?
[00:13:00] Make it work. Give me here note inputs from different channels
[00:13:04] so I can combine multiple notes into one stream of flow
[00:13:09] into one flow of notes and then here set it out with
[00:13:15] with multiple note outs right and then create chords or whatever I want to
[00:13:21] create with this. Not possible. Speaking of notes and
[00:13:28] and the note grid. The voice handling of the grid is
[00:13:35] not good. Of course we have voice stacking which is limited to 16 voices.
[00:13:40] I also have no idea why it's limited to 16 voices I guess.
[00:13:44] I guess it's because of CPU limitations or CPU load or whatever.
[00:13:54] Would be nice to have your 32 or more until your CPU dies out.
[00:14:00] Or maybe make inside of the grid here bring in some
[00:14:05] signal types. At the moment everything here is basically an audio signal which
[00:14:09] is probably the reason why we have so high CPU loads sometimes if you just
[00:14:13] want to connect some data or triggers or logical
[00:14:18] modules it's always audio right? It's an audio signal over sampled three
[00:14:24] times or whatever or four times and yeah it gives you a high
[00:14:28] CPU load just for some on/off data points. So in plug
[00:14:32] data we have different types of signals.
[00:14:38] Maybe make it so you can switch off the over sampling
[00:14:42] would be enough maybe for certain signals because you don't need for
[00:14:46] a gate signal over sampling I guess. Maybe make a small little
[00:14:53] button here on the left side in the inspector or global on the grid here
[00:14:57] just disable over sampling for certain type of signals.
[00:15:01] Yeah it would be nice to have this. I was speaking about voice handling so
[00:15:07] if you want to use this here in polyphonic mode and you have multiple
[00:15:11] nodes or quads going into the node grid
[00:15:16] there's no way of telling where you are with the grid patch on which
[00:15:23] node you are right? You can separate this here maybe with the
[00:15:27] what's the name? Hitch in right and then you go into a merge
[00:15:34] and then you can separate these voices here a bit
[00:15:39] but there is here this for the voice stacking there's a
[00:15:43] voice talk and voice info right. So this would be nice to have voice info
[00:15:48] also for polyphonic voices here not only for the voice stacking.
[00:15:53] So I can decide what I want to do with the lowest node with the
[00:15:59] you know with the second node the third node and so on maybe give me an index
[00:16:03] on which node I am currently and then index it from the bottom maybe the
[00:16:10] lowest node and the next highest node and the third node the fourth node and so
[00:16:14] on. So I know exactly all the time on which
[00:16:17] node I am so I can separate it maybe build some
[00:16:21] appreciators with it or some change the quads on the fly.
[00:16:26] Would be nice to have just this voice stack info here for polyphony would be
[00:16:33] nice. And then of course the big elephant
[00:16:36] what I'm talking about all the time but this is not a small change this is a
[00:16:40] big big change make it so that you can actually build
[00:16:44] interfaces for the grid. Sometimes I have here very big grid
[00:16:50] patches here my generator fonts um maybe let's let's use this one here
[00:16:59] takes a bit to load but you can see here
[00:17:03] it's a bigger patch and you can change all these knobs
[00:17:08] easily but it's a bit overwhelming right so sometimes I just want to have this
[00:17:13] button this button and this button and the rest I want to hide away
[00:17:19] just from the user so it's not overwhelming anymore I just want to
[00:17:22] highlight certain things here and then make it visible inside here
[00:17:28] of the modulation matrix or maybe make a
[00:17:32] different matrix here interface matrix or something like this
[00:17:36] where I can make certain devices here visible in here
[00:17:40] so I don't need to open up here this big grid patch
[00:17:43] and people need to go in and see all these modules
[00:17:47] and oh god I don't know what to do and they close it down right
[00:17:51] so I want to make a small little abstracted interface here
[00:17:55] in the front of the device so an interface designer
[00:17:59] and like I said or told multiple times I thought they're going this way with
[00:18:04] the polymer synthesizer here when they introduced polymer last year or
[00:18:08] two years ago you can see these modules or sections here are
[00:18:14] basically grid devices or they look at least like grid
[00:18:19] devices there are small little differences here and there
[00:18:22] but I thought well this goes in the right direction this is actually
[00:18:25] exactly what I want I want to have grid modules
[00:18:29] in the chain down here and the rest of the patch is abstracted
[00:18:36] away right you can open this up here really great it's exactly how
[00:18:42] it could be so you don't need to design you know
[00:18:46] you need to don't need to design a completely new interface designer you
[00:18:50] can just rely on these on the design of these modules
[00:18:54] and just make them available here in a certain kind of grid
[00:18:58] so you can drag this down here put this here
[00:19:01] and then the rest of the patch is just abstracted or hidden away
[00:19:05] inside of this bigger window here so I thought they'd do this in the next
[00:19:10] update back then but again it's two years ago and
[00:19:14] nothing happened so far and it would be so great
[00:19:18] to create devices and presets this way it would be easy and fun
[00:19:25] and probably a lot of people would be happy to use
[00:19:28] more grid devices and not having to go into these big views and overly
[00:19:34] complex patches here so maybe we get this in the
[00:19:39] future would be great to see actually so here's also again
[00:19:44] here this kind of bipolar thing in Bitwig Studio
[00:19:49] you have the interface which is nice you can use it
[00:19:54] and you can open up here this grid patch but if you want to change this grid
[00:19:59] patch right you can do this by right clicking here
[00:20:02] and say convert to poly-grid and boom you have now a grid
[00:20:06] and the interface is gone it's like they don't want you
[00:20:10] to have these two worlds connected they always
[00:20:14] bring this wall in between right it's always this world or this world
[00:20:19] you don't get the features here but the other features you have to go to this
[00:20:23] world and then you miss all these features right so it's always like this
[00:20:29] they make this on purpose to frustrate me
[00:20:33] i have no idea so now the interface is gone right
[00:20:36] and now we are back here on the grid we can change everything
[00:20:40] but the interface is gone so yeah that's
[00:20:43] two worlds basically in Bitwig Studio no idea why
[00:20:49] um yeah i'm also having here this snare sample already in there
[00:20:55] um the problem here is um let's put this here to raw so we have
[00:21:00] we have the snare sample here in raw mode and i know a lot of
[00:21:04] electronic music producers when i watch the reels
[00:21:08] they use audios audio samples or audio files
[00:21:13] on the arranger itself they drag this in here and they create beats with this
[00:21:17] right so here the snare there and so on
[00:21:22] and then they want to pitch it of course right so here in raw mode you can't
[00:21:26] actually pitch so you can change the gain you can change the
[00:21:30] panning but pitch is grayed out so you have to put this
[00:21:34] into a different mode so re-pitch mode
[00:21:39] uh is perfect for that so here the pitch is still grayed out for some reason
[00:21:45] so maybe bring this back i mean it should work in re-pitch mode
[00:21:52] you can change the pitch of these snare samples here
[00:21:56] kind of indirectly you can change the tempo
[00:22:02] so the feature is there but the pitch
[00:22:08] buttons are grayed out for some reason i have no idea why
[00:22:13] um so it shouldn't be that much
[00:22:17] work to implement as in my opinion because the feature is already working
[00:22:21] here with the tempo indirectly right you can pitch it up or down
[00:22:25] without artifacts i think the closest thing you can get to this
[00:22:32] is to use here the slice mode um that uses here basically the first
[00:22:38] transient as a yeah slice marker and then if you pitch this up or down
[00:22:47] it's actually pitched
[00:22:50] i don't i'm not sure how the algorithm works but it uses here for the tail when
[00:23:00] it's too short it uses here um ping pong delay
[00:23:06] or you can use then here granular at some point
[00:23:11] probably if i put it down
[00:23:13] maybe it doesn't work here with just one um beat marker uh with one transient
[00:23:21] but i think that's the closest you can get to this uh feature
[00:23:25] but sometimes you have longer samples with multiple um
[00:23:29] markers in there and you want to just pitch it up or down like you have it in
[00:23:33] the sampler and it's not possible so i don't
[00:23:36] don't see a reason why this shouldn't be here in re-pitch mode in my opinion
[00:23:43] so just enable this here and re-pitch and yeah
[00:23:47] in slice mode it kind of works here with some drum samples
[00:23:52] or in most cases so that's that's kind of a workaround
[00:23:56] but i have no idea how the um slice algorithm actually works i think they
[00:24:00] just re-pitch the tail and the transient stays the
[00:24:03] same it's not re-pitched or something like this i have no idea
[00:24:07] maybe someone can enlighten me in the comments down below
[00:24:11] so that's that's that um that's the audio system
[00:24:15] and speaking of the audio system i usually when i created or when i create
[00:24:21] drum and bass sometimes i make some sound design sessions right
[00:24:26] and i just you affect this here with a test tone
[00:24:31] and that's maybe here let's say a saw you can see
[00:24:36] really great bass sounds and then i have another audio track here
[00:24:39] and i record stuff coming from the sound design channel here
[00:24:46] and then i hit record more or less
[00:24:50] maybe from the beginning bring this up
[00:24:57] so i record and record inside of a loop right in a ranger loop
[00:25:04] and back before or back then when they before they introduced the
[00:25:11] comp system comping system you could do something like this here
[00:25:16] and you ended up with a audio clip and inside of this audio clip there was like
[00:25:21] an audio event with infinite length so we had a
[00:25:26] very long audio event inside of this short clip here
[00:25:30] so i'll stop here for a moment and then i recorded here some sound design
[00:25:36] sessions maybe bass lines fiddling around with eqs and compression
[00:25:39] and distortion and so on and then i ended up here with this
[00:25:44] clip and then i could just go in and move this around right and go
[00:25:48] into a certain range here where i did something different with the sound
[00:25:52] design but now i'm always ending up with these
[00:25:55] lanes with comping lanes and there's no way for me to
[00:26:00] actually disable comping it's it's always like this
[00:26:04] and i just wanted to disable comping because i never use it i never wanted i
[00:26:09] i just wanted completely removed for my daily life
[00:26:12] i don't need it okay so make a button inside of the settings to disable this
[00:26:17] completely and restore the old behavior
[00:26:20] where i could just record your inside of a loop into a
[00:26:24] very long audio event and my workaround for this is nowadays
[00:26:30] um to record into the clip launcher so this is what i need to do
[00:26:38] um let's record here
[00:26:46] i can show you here um how this looks like then on the
[00:26:51] on the arranger because it was so nice i was designing sounds
[00:26:54] all day just recording into a loop for maybe five minutes
[00:26:59] and then i could swipe through the audio events
[00:27:02] and find certain positions inside of this audio file
[00:27:07] um that fits my groove my drums
[00:27:12] oh that's enough um so now i record into the launcher and then i have to move
[00:27:17] this here then i need to enable this here
[00:27:21] and then i cut this here and then i can again
[00:27:25] move through this audio file and find certain positions here with a
[00:27:30] drum loop on top right and then you dial it in
[00:27:33] and then you find some sweet sweet sweet grooves
[00:27:37] or maybe make this shorter use a different one and find another position
[00:27:42] duplicate this find another position then you could create nice little
[00:27:46] um yeah grooves with this so i have to always use the clip
[00:27:51] launcher for this record in the clip launcher move it over
[00:27:54] here cut it and then i can do this and
[00:27:59] it would be nice to have this here back inside of the ranger because i never
[00:28:03] need comping i never needed it i never wanted i hate it
[00:28:09] no i don't hate it i i know a lot of people use this but i i don't want to
[00:28:13] um so yeah that's the that's the comping feature
[00:28:16] um yeah these are just a few things from the top of my head i asked probably
[00:28:22] a longer list of things i haven't written it down
[00:28:25] probably or i've written it down probably somewhere
[00:28:28] but these are just things from from the top of my head to describe
[00:28:32] some things here and there um so for the future
[00:28:37] i know a lot of people want to have here like
[00:28:41] piano roll improvements and they already wrote about this right in the
[00:28:45] in the thing here when they announced Bitwig studio
[00:28:49] 5.3 i think there's here this
[00:28:53] um what comes next right we are working on some fundamental warfare
[00:28:56] improvements to how how you work on the ranger and in the piano roll
[00:29:02] so a lot of people want to have scale highly highlighting i guess it's not a
[00:29:06] big deal for them to make actually here an overlay a graphical overlay to show
[00:29:10] you which notes you need to play to actually play inside of scale
[00:29:13] i find it a bit boring and too simple um i just want to have maybe something
[00:29:19] more modular because that's why i love Bitwig studio
[00:29:22] it's modular so maybe make the piano roll modular would be the first piano
[00:29:27] roll actually on the market that is yeah customizable
[00:29:31] so make me tweak things or just reorder some notes here
[00:29:37] remove notes add notes maybe add buttons
[00:29:40] or let me create my own overlays or maybe use a scripting language i have no
[00:29:46] idea um so for chords and notes and melodies
[00:29:51] i think it's probably better to have like a guide system so you can see
[00:29:55] when i have a c here in the g that you can see
[00:29:58] instantaneously that these notes are actually a fifth apart
[00:30:04] um that this note here is now a fourth down right so this is maybe not that
[00:30:10] easy to see for beginners and for myself
[00:30:14] or maybe if you have like here a minor chord
[00:30:20] maybe something like this yeah a minor chord and you have like a different
[00:30:24] inversion that you can see oh this is actually a c minor chord but
[00:30:28] it's inversion one right because sometimes you have
[00:30:31] chord progressions and you nudge these notes around here
[00:30:36] different inversions and it's not clear to see that this is a c minor chord
[00:30:40] what it actually it is it's just a c minor chord in a different inversion
[00:30:45] so systems that helps help help you with this kind of
[00:30:49] visualize what you are actually looking at and then you can
[00:30:53] treat chord progressions better i would say than just using a simple
[00:31:00] scale highlighters to see a minor scale or major scale or phrygian scale or
[00:31:05] whatever um in my opinion i can add this too
[00:31:10] but it's probably not not a big of a task for them
[00:31:15] to make an overlay here a graphical overlay
[00:31:18] to make it visible but which kind of scale you are
[00:31:22] so these are some some ideas even more ideas here for the piano
[00:31:26] so in my opinion make it customizable maybe maybe scriptable
[00:31:30] maybe make something for the note grid here
[00:31:34] because in the note grid you can do a lot of interesting things but it's not
[00:31:38] clearly visible what happens to the notes when you
[00:31:42] add processes here right processes and you can hear it then of course because
[00:31:49] you have your note out and you have your synthesizer here playing the notes but
[00:31:52] you can't see it so many people or visual
[00:31:57] you know they need some visuals me too so it would be nice to see then
[00:32:03] when you apply third processes here to the note grid
[00:32:07] what happens actually to the notes on the piano so you can see it more clearly
[00:32:12] maybe a device in here like an oscilloscope but for notes
[00:32:16] so you see a piano roll and then the changes
[00:32:19] before and after or something like this
[00:32:23] or maybe make it so the piano roll actually
[00:32:27] tells you what happens to the notes without actually playing the notes
[00:32:31] right so you can preview inside of the piano roll what happens
[00:32:36] when you apply here an invert or an amp or
[00:32:40] you know some different processes this could be nice i could imagine something
[00:32:45] like this so yeah this is something i want
[00:32:50] from the future and of course all these things i mentioned in the video
[00:32:56] and yeah let me let me know in the comments down below what you
[00:33:00] want from from the next bitwig version from the next big bitwig version
[00:33:07] i guess 5.3 is releasing the next weeks the next next days and then they
[00:33:14] probably work on the next version maybe they announced it already
[00:33:18] directly after releasing 5.3 i have no idea so let me let me know down in the
[00:33:26] comments what you think what you wish for the for the bitwig future maybe some
[00:33:30] things that annoy you and also write it down if you use
[00:33:33] some of the features that are released in the last year in 5.2
[00:33:37] okay thanks for watching and i'll see you in the next video
[00:33:40] Bye.