Coming from Ableton, I find the Grid to be much more accessible than something like MaxForLive (althoughM4L can probably do a lot more than just emulate a modular synth). I also played with VCV Rack/Cardinal and compared to those environments, I love the way everything clips together in The Grid instead of having to run wires from module to module (i'll probably never have a Eurorack system). I like the Grid's color coding and I like the way all input and output signals are shown in real-time in the inspector window. Ableton Live 12 has a few features over Bitwig right now (scale awareness, improved MIDI editing with Transform and Generate) but the list of things that I prefer in Bitwig over Ableton Live is a loooooonnnnnnnnngggggg list.
I basically never use the grid. It's complicated to make something useful with it and often times the modularity is majorly overkill. also you can just use bitwig's superior routing features in normal effect chains to accomplish most of the grid stuff. and you can even put chains into chains, but not grid patches into grid patches. and you don't have to leave the arrangement view to make your chains when you don't use the grid
I would disagree. Grid feels super accessible to me. Quite intuitive and easy to build useful stuff. Super strong feature of BW which I hope they continue to focus on. I spend more time in Grid than anything else. Love it!
I use grid quite often for simple sound design tasks, but for some very specific things I much prefer plug data (as a vst), max msp or vcv rack. Lately then I find it faster to work with the kilohearts suite (phaseplants+snapheap+multipass)...I think the grid needs a bit of improvement to make it more convenient.
Agree on that Phase Plant is the best modular/software synth, in the sense it takes the best of non-modular while giving enough freedom to build anything
Im still trying to learn the grid ,and everything else in bitwig, but im really enjoying it! Been using it for a year, i just wish i had more knowledge on music production
Patching synths and sound design is a bit addictive. You feel like an explorer, or maybe both an artist and an engineer simultaneously. _...To boldly go where no oscillator has gone before!_ Therefore the Grid is for me! It's everything I enjoyed about Reaktor, but I like it better in spite of the fact that it is arguably less powerful than Reaktor due to having fewer low-level modules (which I never really grasped Reatkor well anyways). I do not expect you to answer every question you receive, but do you have any tips on hard-sync patching? I like the BITE module a lot, but I'm also wondering if there is a way to setup hard sync (or even soft sync) between ANY two oscillator sources. I haven't had much luck, and the "sync" modules only seem to force hard-sync to happen against a sawtooth wave instead of the follower's oscillator type. I also cannot find any presets that demonstrate hard-sync from scratch, nor any modules that have the low level logic (such as a phase-locked loop algorithm).
Hey thanks for this comment and yes, you can hard sync. Every oscillator has a trigger input, it's yellow with a small upwards arrow icon, top left. If you connect the output of an oscillator to it, you'll have sync. Hope that helps! :)
@@AlexReidStudios I got it to work, but after a few experiments I realized that I needed to have the master OSC output connected to a SYNC module and then connect the sync module to the trigger input of the follower OSC for this to work. This now will work with ANY form of oscillator -- tubular! Thank you very much! [edit] While I am enjoying this technique, it does have one critical flaw. It introduces a lot of aliasing in the upper registers. Prebuilt modules for sync do not seem to have this problem. Another solution for high notes is to set the ratio at a higher level (such as 2:1) and this also removes some of the aliasing (if you still wish to drive sync from scratch).
I have experience with Max (long ago), and currently use eurorack and VCV Rack, and I use computer programming in my work, but I have not gotten in to The Grid. The phase based sequencing and general lack of "triggers" requires a whole different mindset that I'm still developing. I'm working on it, but in the meantime, I still love Bitwig and dabble in the grid when I find I want to expand a polymer patch. Don't be intimidated. If you want to get started, building on polymer is a great place to start.
@@AlexReidStudios i should amend the adove: triggers are not entirely absent, but there are way fewer trigger inputs for things like "reset sequence" or sequential switches and so on.
Coming from Live, usually racks make much more sense to me but sometimes stock envelopes get in the way, and then I tend to switch to grid. Especially this can happen with the stock sampler so you can do same as with Phase Plant in grid, i.e. use a curve-only envelope,.
I've also used FX Grid to listen the compressed portion of a signal similar to TDR plugins. I implemented it by putting Tool before the Compressor device and used Audio Receiver to bring dry signal to the grid for subtraction. I've been thinking could the similar idea use to convert feed-forward compressor to a glue feed-back compressor but have not yet gotten into experimenting with that idea. Bitwig lacks a good bus compressor so this would be a workaround to have something with the stock plugins (I did buy Cytomic's Glue because of this).
I use the grid for a bunch of stuff. Modulation with FX grid, quick patches with poly, and and endless amount of midi shenanigans with note grid. I agree that I’d really like to have more of the stock FX in the grid, that would be awesome.
@@AlexReidStudios yeah that’s reasonable, but it’s confusing why they’d do any of the effects at all then. I get the waveshapers and filter, but not so much the chorus, phaser, and flanger.
To be absolutely honest the exact one of the most wonky problems with bitwig is its uneasy compatibility and relations between grid devices and first party devices that dev team definitely should work on. If the workflow off Grid (pun intended) merges with the Grid itself it would double the amount of possibilities. Yet still there are so much techniques for music making and especially sound design already to explore.
I wanted to switch to a more modular DAW and I chose FL Studio. It has a modular system that focuses more on your vst instruments. It's basically the same as bitwig but you can drop vsts straight into it.
No, you can't. I believe it's pretty different from Patcher. Still, the visual feedback you get with all the knobs and values is something Patcher could have
You can modulate any third party devices with anything in the grid as long as they are in a nested chain. Either both inside a container, or the third party device nested in the grids post FX. I use it for the dice module, for generating random patches.
I hope you are still monitoring comments on this video 9 months later. Question: which is better / or comparable? I would like a direct comparison with Bitwig grid and Phase Plant with all modules. Thx in advance
@@3DevilDog The workflow is very different. To me Phase plant is synth oriented, while the grid is modular environment oriented. That doesn't mean you cannot create synths with the latter, but it does have a steeper learning curve. With that said, I believe you can create equally complex patches in both
@@AlexReidStudios I ended up getting the full version of Bitwig. I'll have to split my time between Pigments, Phase Plant and Bitwig for a while. So much fun to be had, so little time.
The grid is a way of being. A state of mind. I am the grid. The grid is me. 😂 But joking aside, I can't even wrap my head around why anyone using Bitwig doesn't want to use the grid. The modulation, operators and the Grid. That is Bitwig. the clips are almost an afterthought to me, even though I tend to use them exclusively for making them 4/8 bar loops that I get stuck in for a long time until I go "AH HA". But I have a launchpad pro mkiii so I'm trying to use it as a performance instrument as well
There's this unique sound that the grid provides that is different than with 3rd party synths..I know if doesn't have all of the synth engines out there, which other 3rd party ones can provide, but it makes a sound that I've grown so fond of and is hard to replicate in other synths @@AlexReidStudios
On my case the full version still comes with devices I use regularly, as the Amp, Phase 4, Convolution and Sweep. I suggest you look at the feature list, depends on the tools you already have and the workflow you need
@@AlexReidStudios Thanks, I'm too new to using a computer to play and record music to really understand, I'm nearly starting from scratch on Windows, it sounds like getting the full version makes even more sense because I won't need to buy as many other plugins
Un buen y relevante tema y video, amigo! The grid is fascinating but I find it to be a gateway drug to loads of wasted hours just messing around. It really isn’t that practical imo (unless you’re a Jedi at it a la Polarity). The main selling point of Bitwig for me is the modulation system. It’s incredible - and it really helps breath modulating life into 3rd party synths, especially those with limited modulation - like Diva! And in the end - feel free to fight me on this - the grid will never sound as good as S-tier 3rd party synths like Diva.
@@ht3k I have ears and my subjective sensibilities. None of the myriad of grid presets I have - made presumably by experts who “know” the grid, unlike me - sound nearly as good as those in Diva or other top-notched 3rd part synths or modular analog emulations (like those of G-force or Softube).
Muchas gracias! Modulators are amazing, specially for third party plugins. I believe Diva is a very different beast, but I get your point. Still there are many people that use the grid in crazy ways.
Coming from Ableton, I find the Grid to be much more accessible than something like MaxForLive (althoughM4L can probably do a lot more than just emulate a modular synth). I also played with VCV Rack/Cardinal and compared to those environments, I love the way everything clips together in The Grid instead of having to run wires from module to module (i'll probably never have a Eurorack system). I like the Grid's color coding and I like the way all input and output signals are shown in real-time in the inspector window. Ableton Live 12 has a few features over Bitwig right now (scale awareness, improved MIDI editing with Transform and Generate) but the list of things that I prefer in Bitwig over Ableton Live is a loooooonnnnnnnnngggggg list.
Yep, I use the grid quite often, together with VCV rack (as a plugin). Powerful tool which suits my geeky mind.
I use voltage 2 , but effectively same thing. For me, note grid us da bomb!
I basically never use the grid. It's complicated to make something useful with it and often times the modularity is majorly overkill. also you can just use bitwig's superior routing features in normal effect chains to accomplish most of the grid stuff. and you can even put chains into chains, but not grid patches into grid patches. and you don't have to leave the arrangement view to make your chains when you don't use the grid
That's true! Containers are really amazing for complex stuff
I would disagree. Grid feels super accessible to me. Quite intuitive and easy to build useful stuff. Super strong feature of BW which I hope they continue to focus on. I spend more time in Grid than anything else. Love it!
A GUI builder for Grid would be seriously next level!
@@googleuser318 I'd love that! It would be amazing
I use grid quite often for simple sound design tasks, but for some very specific things I much prefer plug data (as a vst), max msp or vcv rack. Lately then I find it faster to work with the kilohearts suite (phaseplants+snapheap+multipass)...I think the grid needs a bit of improvement to make it more convenient.
Agree on that Phase Plant is the best modular/software synth, in the sense it takes the best of non-modular while giving enough freedom to build anything
Im still trying to learn the grid ,and everything else in bitwig, but im really enjoying it! Been using it for a year, i just wish i had more knowledge on music production
You're in a journey! you'll get betterand gain knowledge each day
@@AlexReidStudios 🤙
Bitcrusher is available with quantize. But yes I miss some more things in there
There's got to be a quantizer in the grid that can be pressed into service as a bit crusher. Certainly sample rate reduction is trivial with S&H.
I haven't diven into the grid so deep but i found it useful in some cases.
Patching synths and sound design is a bit addictive. You feel like an explorer, or maybe both an artist and an engineer simultaneously. _...To boldly go where no oscillator has gone before!_ Therefore the Grid is for me! It's everything I enjoyed about Reaktor, but I like it better in spite of the fact that it is arguably less powerful than Reaktor due to having fewer low-level modules (which I never really grasped Reatkor well anyways).
I do not expect you to answer every question you receive, but do you have any tips on hard-sync patching? I like the BITE module a lot, but I'm also wondering if there is a way to setup hard sync (or even soft sync) between ANY two oscillator sources. I haven't had much luck, and the "sync" modules only seem to force hard-sync to happen against a sawtooth wave instead of the follower's oscillator type. I also cannot find any presets that demonstrate hard-sync from scratch, nor any modules that have the low level logic (such as a phase-locked loop algorithm).
Hey thanks for this comment and yes, you can hard sync. Every oscillator has a trigger input, it's yellow with a small upwards arrow icon, top left. If you connect the output of an oscillator to it, you'll have sync. Hope that helps! :)
@@AlexReidStudios I got it to work, but after a few experiments I realized that I needed to have the master OSC output connected to a SYNC module and then connect the sync module to the trigger input of the follower OSC for this to work. This now will work with ANY form of oscillator -- tubular! Thank you very much!
[edit] While I am enjoying this technique, it does have one critical flaw. It introduces a lot of aliasing in the upper registers. Prebuilt modules for sync do not seem to have this problem. Another solution for high notes is to set the ratio at a higher level (such as 2:1) and this also removes some of the aliasing (if you still wish to drive sync from scratch).
The Grid was one of the big things that drew me to Bitwig but the entire DAW itself is so seemlessly modular that I rarely end up opening it.
Honestly is that hard, I found it really easy to learn
@@AlexReidStudios the grid you mean?
@@JC20XX I meant Bitwig
@@AlexReidStudios oh yeah, it was very intuitive for how my brain works. If only I hadn't tried FL first.
@@JC20XX for me was the opposite, I felt FL was too much lol
I have experience with Max (long ago), and currently use eurorack and VCV Rack, and I use computer programming in my work, but I have not gotten in to The Grid. The phase based sequencing and general lack of "triggers" requires a whole different mindset that I'm still developing. I'm working on it, but in the meantime, I still love Bitwig and dabble in the grid when I find I want to expand a polymer patch.
Don't be intimidated. If you want to get started, building on polymer is a great place to start.
That's true, you need a different mindset, is not your regular modular environment like VCV
@@AlexReidStudios i should amend the adove: triggers are not entirely absent, but there are way fewer trigger inputs for things like "reset sequence" or sequential switches and so on.
Coming from Live, usually racks make much more sense to me but sometimes stock envelopes get in the way, and then I tend to switch to grid. Especially this can happen with the stock sampler so you can do same as with Phase Plant in grid, i.e. use a curve-only envelope,.
I've also used FX Grid to listen the compressed portion of a signal similar to TDR plugins. I implemented it by putting Tool before the Compressor device and used Audio Receiver to bring dry signal to the grid for subtraction. I've been thinking could the similar idea use to convert feed-forward compressor to a glue feed-back compressor but have not yet gotten into experimenting with that idea. Bitwig lacks a good bus compressor so this would be a workaround to have something with the stock plugins (I did buy Cytomic's Glue because of this).
@@jarkkojs Nice, it would be great to have a more straightforward signal path splitter inside the grid
I use the grid for a bunch of stuff. Modulation with FX grid, quick patches with poly, and and endless amount of midi shenanigans with note grid. I agree that I’d really like to have more of the stock FX in the grid, that would be awesome.
My guess is the developers want to avoid making the grid too independent from other features
@@AlexReidStudios yeah that’s reasonable, but it’s confusing why they’d do any of the effects at all then. I get the waveshapers and filter, but not so much the chorus, phaser, and flanger.
To be absolutely honest the exact one of the most wonky problems with bitwig is its uneasy compatibility and relations between grid devices and first party devices that dev team definitely should work on. If the workflow off Grid (pun intended) merges with the Grid itself it would double the amount of possibilities. Yet still there are so much techniques for music making and especially sound design already to explore.
It would make it more similar to FL Studio Patcher, which could be really cool tbh
I use to built favourite fx, and instruments inspired by hw or software. Eventide, classic synths with sequensers. Love it.
Nice! That's a great way to use it
I wanted to switch to a more modular DAW and I chose FL Studio. It has a modular system that focuses more on your vst instruments. It's basically the same as bitwig but you can drop vsts straight into it.
You mean Patcher?That's a beast. Honestly I didn't used it as much because of routing modifications and such.
The grid has a nice UI in my opinion. better than Patcher from imageline. it doesnt let you use third party pugins inside it though does it?
No, you can't. I believe it's pretty different from Patcher. Still, the visual feedback you get with all the knobs and values is something Patcher could have
@@AlexReidStudios yeah is there a free trial so i could fiddle with it? i dont think i would switch daws but i am curious about the differences
I would like to know the possibilities of The Grid to control and modulate third-party plugins, as well as advanced midi routing, etc...
Gonna check what I can do :)
You can modulate any third party devices with anything in the grid as long as they are in a nested chain. Either both inside a container, or the third party device nested in the grids post FX. I use it for the dice module, for generating random patches.
I hope you are still monitoring comments on this video 9 months later. Question: which is better / or comparable? I would like a direct comparison with Bitwig grid and Phase Plant with all modules. Thx in advance
@@3DevilDog The workflow is very different. To me Phase plant is synth oriented, while the grid is modular environment oriented. That doesn't mean you cannot create synths with the latter, but it does have a steeper learning curve. With that said, I believe you can create equally complex patches in both
@@AlexReidStudios thx so much man. You rock
@@AlexReidStudios I ended up getting the full version of Bitwig. I'll have to split my time between Pigments, Phase Plant and Bitwig for a while. So much fun to be had, so little time.
I just need the grid to have multi-out without a workaround, the ability to host vsts (like voltage modular/ fl studio's patcher), and more triggers.
Multi out would be amazing
I am lost in the grid...and Bitwig
You are not alone 🙄
Using third party plugins makes it less locked in and more modular if need to switch DAW for some reason.
The grid sounds cool tho.
i have Bitwig Producer edition, which means i don't have access to the Grid.
but i feel that stuff would be way too complicated for me.
Honestly I don't use it as much, because all the containers and modulators are pretty powerful on their own
The grid is a way of being. A state of mind. I am the grid. The grid is me. 😂 But joking aside, I can't even wrap my head around why anyone using Bitwig doesn't want to use the grid. The modulation, operators and the Grid. That is Bitwig. the clips are almost an afterthought to me, even though I tend to use them exclusively for making them 4/8 bar loops that I get stuck in for a long time until I go "AH HA". But I have a launchpad pro mkiii so I'm trying to use it as a performance instrument as well
The Grid is dope, but so are the other features, still the Grid will give you more freedom
There's this unique sound that the grid provides that is different than with 3rd party synths..I know if doesn't have all of the synth engines out there, which other 3rd party ones can provide, but it makes a sound that I've grown so fond of and is hard to replicate in other synths @@AlexReidStudios
@@buckycore Agree, it's its own unique system
If I don't use the grid, is it still worth paying for the full version?
On my case the full version still comes with devices I use regularly, as the Amp, Phase 4, Convolution and Sweep. I suggest you look at the feature list, depends on the tools you already have and the workflow you need
@@AlexReidStudios Thanks, I'm too new to using a computer to play and record music to really understand, I'm nearly starting from scratch on Windows, it sounds like getting the full version makes even more sense because I won't need to buy as many other plugins
@@CookinBeatloaf That's a really nice way to start, avoid getting in the trap of buying plugins until you understand the ones that come with your DAW
Yes.
Un buen y relevante tema y video, amigo!
The grid is fascinating but I find it to be a gateway drug to loads of wasted hours just messing around. It really isn’t that practical imo (unless you’re a Jedi at it a la Polarity).
The main selling point of Bitwig for me is the modulation system. It’s incredible - and it really helps breath modulating life into 3rd party synths, especially those with limited modulation - like Diva!
And in the end - feel free to fight me on this - the grid will never sound as good as S-tier 3rd party synths like Diva.
the last point is debatable. the Grid is only limited by your sound design knowledge. Just because you don't know it doesn't mean it isn't possible
@@ht3k I have ears and my subjective sensibilities. None of the myriad of grid presets I have - made presumably by experts who “know” the grid, unlike me - sound nearly as good as those in Diva or other top-notched 3rd part synths or modular analog emulations (like those of G-force or Softube).
Muchas gracias! Modulators are amazing, specially for third party plugins. I believe Diva is a very different beast, but I get your point. Still there are many people that use the grid in crazy ways.
@@AlexReidStudios I hear you. Perhaps a better comparative 3rd party example would be softube’s modular synth - which is a beast! (You familiar…?)
@@jeffreyhanc1711 I know that one but never played with it. I have used VCV and Voltage Modular
I enjoy the grid but lately I've been messing with Pure Data and Plug Data.
That's nice, just today I downloaded it
We don't need it. But I waaaaaaant it.
You have a rabbit head
What?!