The Vowel filter is very cool. The linguistic sound symbols are part of the International Phonetic Alphabet (IPA for short). It is a language of symbols that represent sounds in various languages. It was invented in the late 19th century. I studied opera for 11 years in college (got doctorate), so I learned it then to sing in many languages. Now working on writing & recording rock/pop songs, singing, playing keys, drums, & guitar. Started working with Bitwig about 6 months ago. Thanks for all the info!
In the next Bitwig update where they work on devices I hope they will give some love to mixing and mastering devices. Give us a technical clipper, add a latency less mode to EQ+, and a loudness based limiter build in would be great. But before that I'm hoping on a workflow update to fix the piano roll, let us resize the device panel, add time segment markers behind clips, and add scales to the piano roll, I don't need it but then people can finally shut up about it just like with MSEG before haha
The Mixer resizes via drag, both height and width. Just FYI, for the comments or whoever. Edit: Oh, I forgot to say. I read over at KVR that EQ+'s latency may be compensated now. Haven't confirmed it myself. I have no access to betas. Plan ran out, so I'll be waiting until release.
Thank you for the video Alck! ✨ I'm so happy to see that now bitwig has a vowel filter and audio quantization is a killer feature for sure! can't wait for the stable release 😍
I agree with the pitching options addition. That's very needed. It takes unnecessarily long to pitch things and have them stay in key so that would change a lot! Thanks for mentioning that in the video. Hope Bitwig sees it
Its great they are adding more features, but what about fixing issues that still do not work properly. The native Faderport script doesn't allow you to control channels within a group channel. Making the "Officially Supported" script almost unusable!
I still havent bought x touch one because of this, at the same time im not willing to switch daws because bitwig is still so awesome, not to mention some BASIC functionality it still does not have. And thatbis a bit of a shame for a daw of its caliber.
Love this, really hoping they add some sort of beat mapping/groove pool feature to the quantization section. Just really suits my in logic/reason/ableton to be able to quantize things to other things easily.
The thing Im happy about the most is such a tiny thing: NORMALIZATION for audio clips. It's such a little thing but really felt like a basic DAW feature that was missing.
Yeah it’s really nice to have although most of my stuff is blasted anyway so it doesn’t make much of a difference lol. Would love repitching unwarped audio
All I need is a workflow to align the project tempo with the music. It doesn't even need to automatically detect the tempo of the music (although that would be great, too), anything that allows me to drag the beat markers where they belong would be sufficient to make Bitwig usable for me.
If you drag a clip in it will automatically warp to the tempo. If you look at the inspector panel while highlighting that clip it will tell you what the original tempo is
@@Alckemy Yeah that's the problem. Instead of adjusting the project tempo to the music, it warps the track tempo. The worst thing is it assumes that each clip has one straight tempo, which a natural performance will never have. Fluid tempo is technically possible, but you need to calculate the BPM numbers of the tempo changes by hand. Not a nice workflow, and unhandy enough to give up and switch DAW when working on a longer song.
as of the most recent beta update, the soft clippers actually function as intended, the version I reviewed here did not. Check the latest video I have on bitwig for coverage over it. I’m pretty happy with the fix :)
I keep watching bitwig update videos to see when they add see through gridlines. Then I might switch. They're doing amazing updates, I can't figure out why they don't just add it as an option. Seems like it would be simple to code compared to the other updates. Feels like they are ignoring it on purpose, makes no sense. It's a big deal for many users.
I was worried about the same and have to say it's not as big of a deal as I thought. If you group sections, you always have a guide above or below to reference.
New devices simply dangerous for hearing and for equipment. They didn’t bother so put some limiting precaution in them so I’ll avoid to use it. Audio quantisation is broken even at beta 6. I can not straighten up swinged loop. This is what it must do. But it is expected from bitwig to give to people broken feature and mark it as done. No surprises here. And the last but not least. I feel sorry for you not knowing bitwig number one feature: voice stacking. It’s been there since v2. And it is the one feature that part bitwig from other daws.
Any device is dangerous if you don’t have a limiter on your master. That being said 2 of the latest distortion types clip now. I covered voice stacking in my last beta review. It’s cool Bitwigs not perfect but it’s still in beta, it’s gonna have bugs. Here’s a pro tip. Put a limiter on your master.
@@AlckemyI have limited on master all the time. Not the point. Point is anyone can by accident disable plugin or if it crash and I don’t pay attention…. So those devices can be voice stacked up to 15 times. And sound will be louder 15 times. 15 times with no condensation of volume. This is ok in a grid as behaviour expected. Not in a separate plugin (I know it’s just a grid patch. Lazy job.) this is not only dangerous. This is also unpractical and unusable to some extent. As I want to feed “analog like” filter with specific ammount of volume. Not 15 times volume. Not possible. Whatever. Bitwig not perfect but recently also go sideways. IMO.
...looking forward to see u drop all ur neuro bass weapons of choice, once u really discover the potential of bite...since, once u really dive into it, u gonna realize, oops and holy shit, this damned "little" thing covers all ur favourite sonic trix at once....
Is it possible to create an instrument setlist for keyboard players like mainstage and ableton. In ableton i will create an empty clip and trigger the scene to activate the instrument tone and i will play in my midi keyboard. My need is, i need 24 different instruments in a single setlist. I tried bitwig instrument selector but since i used 24 instrument layers and each layer has 2 different vst like korg triton and kontakt, the daw is getting slow. Is there any other way in bitwig to create an instrument setlist with 24 instruments so that i can switch between these 24 instruments using my Arturia keylab 88 mk2??? My laptop configuration is macbook prom m2 8gb ram 512gb ssd. Thanks in advance
Regardless of how you organize it unless if you turn off every instrument other than one you’re using you’re going to run into that slow down. The selector is likely the best bet because it will make the other devices sleep. I think there’s a setting on there to make that happen
@@Alckemy thanks for you time and your reply. Can you please guide me in this?? How to turn off other instruments while playing one? Please send me some video tutorials.
@@calebdany5085 if you just deactivate devices it’ll save you cpu. So just turn one off and swap to the next. There’s an instrument selector settings when you click the device and look at the inspector panel.
@@Alckemy manually means do i need to turn off every time when i move to other instrument or is there any settings so that i can manually program to turn it off and when i switch to other instrument using a midi switch it will turn off others??
Kind of. You can do some pseudo fm in the grid and actually fm/pm filters just send a sampler into a filter and then use a wavetable or something on the purple into the filter
@@Alckemy I was trying your idea, but it seems like the filters in the grid do not have the purple in. I'm on BW 5.0.11: I'm not elligible for this new update as my plan expired.
Well that's how it works though. They rollout a beta first to get bug reports and when they fix them (in a couple months) they release it. Also each beta they work backwards compability issues if there are any and don't release it until sure which is why they always say don't work on important projects in the beta
@@Rannument Sure, i understand that, but i think it’s important to state it upfront because you may wonder why your version won’t show the update and so on.
“Usable” is also an ambiguous term. I don’t see how understanding an explanation equates to being unusable if it doesn’t yield a sound you’re expecting. It’s part of the update- here’s how it works. Go put it on whatever sound you want
The Vowel filter is very cool. The linguistic sound symbols are part of the International Phonetic Alphabet (IPA for short). It is a language of symbols that represent sounds in various languages. It was invented in the late 19th century. I studied opera for 11 years in college (got doctorate), so I learned it then to sing in many languages. Now working on writing & recording rock/pop songs, singing, playing keys, drums, & guitar. Started working with Bitwig about 6 months ago. Thanks for all the info!
Thank you for the info! That’s really cool. Please send me opera samples sometime lol
In the next Bitwig update where they work on devices I hope they will give some love to mixing and mastering devices. Give us a technical clipper, add a latency less mode to EQ+, and a loudness based limiter build in would be great.
But before that I'm hoping on a workflow update to fix the piano roll, let us resize the device panel, add time segment markers behind clips, and add scales to the piano roll, I don't need it but then people can finally shut up about it just like with MSEG before haha
I'd be down with these changes
The Mixer resizes via drag, both height and width. Just FYI, for the comments or whoever.
Edit: Oh, I forgot to say. I read over at KVR that EQ+'s latency may be compensated now. Haven't confirmed it myself. I have no access to betas. Plan ran out, so I'll be waiting until release.
wow that would be awesome to be honest, always wanted to use eq+ for being native but with that delay thing is a no
@@MIDNIGHTCVLTdelay shouldn't be an issue unless you use it in parallel
@@gdubzaudio i use a lot of parallel processing that's why :(
OOF@@MIDNIGHTCVLT
The changelog says, quote:
EQ+ (EQ) device: Is now latency compensated
Thank you for the video Alck! ✨ I'm so happy to see that now bitwig has a vowel filter and audio quantization is a killer feature for sure! can't wait for the stable release 😍
Yeah definitely beware for betas lol they can be ruthless
The stack stuff is similar to how "polyphonic" processing works in VCV Rack.
Yeah but this is all within a single note. Each unison has its own individual settings
Those new filters and distortions are killer ❤🎉
Yeah, of music.
Holy crap that filter+ is amazing
Great break down Alckemy, loving the new additions
I agree with the pitching options addition. That's very needed. It takes unnecessarily long to pitch things and have them stay in key so that would change a lot! Thanks for mentioning that in the video. Hope Bitwig sees it
Thanks for watching. Me too!
Its great they are adding more features, but what about fixing issues that still do not work properly. The native Faderport script doesn't allow you to control channels within a group channel. Making the "Officially Supported" script almost unusable!
They definitely March to their own beat. Working with controllers/hardware definitely has been hit or miss
I still havent bought x touch one because of this, at the same time im not willing to switch daws because bitwig is still so awesome, not to mention some BASIC functionality it still does not have. And thatbis a bit of a shame for a daw of its caliber.
you can drag the mixer now to your likeing, try
Love this, really hoping they add some sort of beat mapping/groove pool feature to the quantization section. Just really suits my in logic/reason/ableton to be able to quantize things to other things easily.
I just realized this is the best DAW
I must agree
The thing Im happy about the most is such a tiny thing:
NORMALIZATION for audio clips.
It's such a little thing but really felt like a basic DAW feature that was missing.
Yeah it’s really nice to have although most of my stuff is blasted anyway so it doesn’t make much of a difference lol. Would love repitching unwarped audio
All I need is a workflow to align the project tempo with the music. It doesn't even need to automatically detect the tempo of the music (although that would be great, too), anything that allows me to drag the beat markers where they belong would be sufficient to make Bitwig usable for me.
If you drag a clip in it will automatically warp to the tempo.
If you look at the inspector panel while highlighting that clip it will tell you what the original tempo is
@@Alckemy Yeah that's the problem. Instead of adjusting the project tempo to the music, it warps the track tempo.
The worst thing is it assumes that each clip has one straight tempo, which a natural performance will never have.
Fluid tempo is technically possible, but you need to calculate the BPM numbers of the tempo changes by hand. Not a nice workflow, and unhandy enough to give up and switch DAW when working on a longer song.
Of course my update plan ended yesterday. All good though, I'll renew on Black Friday.
Oof
you might try sending them an email with this unlucky event. they might be kind to you and update your latest version to this one
@@adrianpaul3749 that's not a bad idea. Thanks for taking the time :)
Did you try turning the filter off? I think filters can introduce some changes even if it is fully opened.
as of the most recent beta update, the soft clippers actually function as intended, the version I reviewed here did not. Check the latest video I have on bitwig for coverage over it. I’m pretty happy with the fix :)
BW rules quiet, my fav besides Renoise
I keep watching bitwig update videos to see when they add see through gridlines. Then I might switch. They're doing amazing updates, I can't figure out why they don't just add it as an option. Seems like it would be simple to code compared to the other updates. Feels like they are ignoring it on purpose, makes no sense. It's a big deal for many users.
I was worried about the same and have to say it's not as big of a deal as I thought. If you group sections, you always have a guide above or below to reference.
Fantastic video, thank you🤙🙂🏴
Thank you!
New devices simply dangerous for hearing and for equipment. They didn’t bother so put some limiting precaution in them so I’ll avoid to use it.
Audio quantisation is broken even at beta 6. I can not straighten up swinged loop. This is what it must do. But it is expected from bitwig to give to people broken feature and mark it as done. No surprises here.
And the last but not least. I feel sorry for you not knowing bitwig number one feature: voice stacking. It’s been there since v2. And it is the one feature that part bitwig from other daws.
Any device is dangerous if you don’t have a limiter on your master. That being said 2 of the latest distortion types clip now.
I covered voice stacking in my last beta review. It’s cool
Bitwigs not perfect but it’s still in beta, it’s gonna have bugs.
Here’s a pro tip. Put a limiter on your master.
@@AlckemyI have limited on master all the time. Not the point. Point is anyone can by accident disable plugin or if it crash and I don’t pay attention…. So those devices can be voice stacked up to 15 times. And sound will be louder 15 times. 15 times with no condensation of volume. This is ok in a grid as behaviour expected. Not in a separate plugin (I know it’s just a grid patch. Lazy job.) this is not only dangerous. This is also unpractical and unusable to some extent. As I want to feed “analog like” filter with specific ammount of volume. Not 15 times volume. Not possible. Whatever. Bitwig not perfect but recently also go sideways. IMO.
Does witbig have colorblind skins?
Too bad my license ran out at 5.9😂😂😂😂
They don’t but you can adjust the contrast and saturation. You can also upload images that turn into color swatches for tracks
💣
...looking forward to see u drop all ur neuro bass weapons of choice, once u really discover the potential of bite...since, once u really dive into it, u gonna realize, oops and holy shit, this damned "little" thing covers all ur favourite sonic trix at once....
I hope so! I’m honestly using very basic waveforms these days with one or two instances of fm. The magic has always been in the effects.
Is it possible to create an instrument setlist for keyboard players like mainstage and ableton. In ableton i will create an empty clip and trigger the scene to activate the instrument tone and i will play in my midi keyboard. My need is, i need 24 different instruments in a single setlist. I tried bitwig instrument selector but since i used 24 instrument layers and each layer has 2 different vst like korg triton and kontakt, the daw is getting slow. Is there any other way in bitwig to create an instrument setlist with 24 instruments so that i can switch between these 24 instruments using my Arturia keylab 88 mk2??? My laptop configuration is macbook prom m2 8gb ram 512gb ssd.
Thanks in advance
Regardless of how you organize it unless if you turn off every instrument other than one you’re using you’re going to run into that slow down. The selector is likely the best bet because it will make the other devices sleep. I think there’s a setting on there to make that happen
@@Alckemy thanks for you time and your reply. Can you please guide me in this?? How to turn off other instruments while playing one? Please send me some video tutorials.
@@calebdany5085 if you just deactivate devices it’ll save you cpu. So just turn one off and swap to the next. There’s an instrument selector settings when you click the device and look at the inspector panel.
You might have to manually deactivate them
@@Alckemy manually means do i need to turn off every time when i move to other instrument or is there any settings so that i can manually program to turn it off and when i switch to other instrument using a midi switch it will turn off others??
Random question, is there a way one can FM synthesize in Bitwig's sampler kinda like how you can with Ableton/Phase Plant Sampler?
Kind of. You can do some pseudo fm in the grid and actually fm/pm filters just send a sampler into a filter and then use a wavetable or something on the purple into the filter
@@Alckemy I was trying your idea, but it seems like the filters in the grid do not have the purple in. I'm on BW 5.0.11: I'm not elligible for this new update as my plan expired.
@@Noldy__ just attach it to the top band
@@Alckemy I don't think I quite understand you. Maybe its way over my head hahaha
@@Noldy__ TWO MUST TRY TRICKS IN #BITWIG’S FX GRID
ua-cam.com/video/-GO1iUyOt9I/v-deo.html
😮🔥🔥🔥
basic fuckn sample warping
Wha
It's in Beta only,.
Well that's how it works though. They rollout a beta first to get bug reports and when they fix them (in a couple months) they release it.
Also each beta they work backwards compability issues if there are any and don't release it until sure which is why they always say don't work on important projects in the beta
@@Rannument Sure, i understand that, but i think it’s important to state it upfront because you may wonder why your version won’t show the update and so on.
They say it on the website that it's currently in beta and they plan on releasing it before the end of the year@@Imperceptible_parachute
Beta is open and always has been. Just go on the website
fIrSt
I would have rather be able to listen to a NOT CLIPPED sound for demonstration. This is useless.
I talked about clipping for maybe two minutes of the video. Sounds kind that’s as far as you got
@Alckemy I heard. I got about to minute 11. The thing is mentioning it doesn't make the test any more usable, thus my comment.
“Usable” is also an ambiguous term. I don’t see how understanding an explanation equates to being unusable if it doesn’t yield a sound you’re expecting. It’s part of the update- here’s how it works. Go put it on whatever sound you want