Andreilien/Iterate - How I use "The Grid" in Bitwig

[@squ33dl3]

I'm so overwhelmed and excited to start playing with this stuff in BitWig, finally got studio this week and I'm going to spend a lot of time on your channel.

[@aneri72]

Wow! I loved this. Crazy advanced and cool sounding Grid patches. More vids like this please 😀

[@partyboeller]

Clicked like immediately, just for how great the patch looks :)

[@joncrandall2955]

Stoked to hear the new project and see more vids!

[@bezio_max]

awesome, thank you for sharing this! solid bitwig info in this arena is tough to find, this was super helpful / inspiring

[@briancase6180]

Great!. Another bitwig heavyweight! I started about a year ago and sheepishly choose bitwig against the common wisdom because it just seemed to make sense to my computer-science-trained mind. I've witnessed the evolution and problem-solving by the developers and I've been very happy. I'm using an M1 MacBook Pro 13 and it's fast even with Rosetta. I can't use my universal audio interface and native-instrument plugins, but maybe it's time to move on from them anyway. I could always use more cpu cycles, but I would never go back to an Intel processor. I would love to try an eight-core AMD-based laptop, for sure. Who is using an AMD-based machine with bitwig? You have built great patches. I'm sure you are aware of polarity and his KZbin channel.... Thanks for your efforts. Subscribed.

[@AndreiOlenev]

Thanks for the comment. I'm curious about how AMD laptops work with Bitwig too. My current computer has bad problems with dpc latencey, and in general isn't running well. So, I'm hoping to get a new computer sometime in the next year. These new AMD processors look great, but I don't know how they perform with music software. I hope AMD laptops come out with thunderbolt though, because I have an Apollo. Did you say your new M1 mac isn't working with your UAD interface? I'm considering getting an arm based macbbook pro when they come out, if they don't cost too much, but I'm not crazy about using Apple, because their constant os updates are a hassle. Windows has it's own set of problems, but I like that I can still run plugins from 15 years ago with no problems.

[@truthbydesign5146]

@@AndreiOlenev I was having latency issues with my prior intel computer and MOTU interface but it's been a complete game changer since I upgraded to an M1 Pro MacBook Pro and RME Babyface Pro FS -- best money I've spent on music production gear.

[@JosephDicasio]

Him: I am not an expert in Bitwig His Grid says otherwise 😂 Thanks for this video

[@drfluffy3983]

awesome stuff. interested to see more videos from you

[@vasilymilovidov]

Amazing stuff! Completely switched from Ableton to Bitwig and was hoping to get back some M4L functionality with the Grid. Looking forward to see more videos!

[@AndreiOlenev]

Thanks! Best of luck with it.

[@amuq_puma]

Hell yeah dude. Been loving bitwig myself - excited to see what other folks are doing.

[@DaKingof]

Glad to see you switched over. Really cool patches and dope music. I hope to see a lot more from you.

[@douglashill3008]

Bonkers! I look forward to your knowledge! Thanks for sharing!

[@Pspiralifemusicandedu]

Im grateful to have found some complex grid patch designs to make me feel inferior. Because unless I, simply not looking in the right places, finding tutorials on advanced polygrid modular patch design is really difficult. liked, Subscribed, notification bell on! Thank you!

[@truthbydesign5146]

Have you found anything in the last year that helped you progress? I'm in the same boat.

[@Pspiralifemusicandedu]

@@truthbydesign5146 not really no. I kind of took a break from the study side of it though and made some music with what knowledge I’d got so far

[@oddsphere]

been really digging your music and stumbled upon this gem, thank you

[@greggsonic]

Love to see how you built this! :)

[@soundfx68]

My brain just melted, it's in a puddle on my desk.😁

[@benw2751]

This is beautiful.

[@DaKingof]

You can use remotes instead of wires. I think it takes a little more cpu... but it keeps it clean looking.

[@DaKingof]

I sent a request when they first made the Grid to give us an option to hide cables and lower level devices when the interface is locked. Nothing yet.

[@AndreiOlenev]

@@DaKingof Thanks for the tip. I think they will probably add an option to hide wires, since it seems like many people want it. The Grid is still pretty new, and they seem to be coming out with many new features pretty quickly. I'm really hoping for something like macros in reaktor, so we can have all the stuff we don't need to see contained in one module, and just have the necessary ins and outs. I'm hoping down the road they might let people create custom modules as well. Even without all those things, it is still a really fun and flexible sound design tool. I feel like it's the easiest modular environment to use right now.

[@DaKingof]

Yes. Imo it should have been a first person feature, but I'm sure they must have something better in the works then our solution.

[@ccrawford1719]

Awesome! Looking forward to the series. The wavetable you have loaded at 10:45 - is that downloaded from somewhere, or did you create it, and if you created it what did you use?

[@thethirdball]

Bitwig 3.3 was released yesterday. That may have what you're looking for. :)

[@ccrawford1719]

@@thethirdballthanks, I'm looking to see where he may generate or source wavetables from since 'a_m_v1' isn't included in bitwig, but mostly I'm just curious, since he isn't even using it in the video :)

[@AndreiOlenev]

Hi, The wavetable wasn't actually active on the patch I was playing. I have a knob for the op2 phasemod input that blends between being fm'd by the wavetable or the grid's phase modifiers. On that patch, only the phase modifiers are active. The main ones that were running were the formant and sinemod. The wavetable still shows in the oscilloscope though. It is a wavetable I made in serum, combining several single cycle waveforms. I will have another video soon going into more details on this stuff.@@ccrawford1719

[@thethirdball]

@@ccrawford1719 Ah yes, my bad. :)

[@Artek604]

Those are the most bonkers Grid patches I've seen yet! :o Glad I found your channel! Subscribed!!! BTW, you have your music somewhere, ideally on Bandcamp? :)

[@AndreiOlenev]

Hi. Thanks alot! Here is my bandcamp page: andreilien1.bandcamp.com/, and here is my soundcloud: soundcloud.com/andreilien/ I'm working on a new project called "Iterate" now. I will probably make another bandcamp page for that as well.

[@nonebits]

Two tips: * Center Window evey time you open your grid patch: Put some module on far right, other on far left, top and bottom. Adjust this until when you open your Grid Patch the Window is centered on whatever you want. * Soften the Wire Hell: Put a >Deactivated< Attenuator (White) in the middle of connections and positione it. Thats not perfect, but is way better. (Obviously you will only do this at the end and when you are sure it is the final patch.)

[@AndreiOlenev]

Thanks for the tips. I did have these patches more centered earlier, but ended up moving a lot of things around to do some last minute tweaks, and never cleaned them back up. I didn't know about softening the wire hell. I'll definitely look into that. I'm still pretty new to using bitwig, so it's been a lot of trial and error figuring things out. Luckily, it is such an intuitive program, that is is pretty simple to apply techniques from other software without having to do too much tinkering to figure out how things work. Thanks again.

[@dubtube6691]

You are killing my loudspeakers

[@skorobagatko]

Keep it up! Subbed.

[@JSprayaEntertainment]

whoa , nice work

[@Lothar303]

Good work here especially with the FM/PM synth. We really need some way to create custom GUIs, the cable spaghetti is hard to read if you did not write the patch yourself. I've been thinking a lot lately about how to keep the layouts informative while not compromising on the ideas I want to achieve. Also personally, I noticed that I have sometimes trouble understanding the stuff I made just six months or one year ago :/

[@AndreiOlenev]

I totally agree. On top of it crowding the gui, I've noticed that when you're viewing a large patch, it uses a lot more cpu than if the grid window is closed, even through audio is still running. So, I assume the graphics are using extra cpu. My computer has cpu issues, so it might not be as much of a problem for most people. In Reaktor, they have a module called "stacked macro" that allows you to change the view when selecting different macros. I would love to see something like that in The Grid. Having any type of macro/container module, to simplify things would be great. I am hopeful that The grid will continue to evolve and add a lot of these features. It is still pretty new. Another great one would be the option to route audio to multiple different tracks, or to be able to route into multiple chains in the fx section.

[@Lothar303]

@@AndreiOlenev oh, don't even get started on the need for containers or/and some other way of reusing old builds and their parts. Altough I never used Reaktor that much so I probably haven't seen most of what's in the GUI, but I never liked the way how complicated builds easily ended up being level below level of sub-containers. And yes, on some patches with hundreds of modules my CPU use will double when a Grid Editor is open, and it will become very unrrspondive. I didn't yet see if 3.3 made it better, I've received reports that it runs faster than the old versions in general.

[@AndreiOlenev]

@@Lothar303 I think 3.3 might be running smoother. I noticed cpu improvement on the pm synth. Although, I was using a sampler module with a 128 of wavetables in the previous version, so I think that probably taxed the CPU. Having a dedicated wavetable module seems to run much smoother.

[@semyonboyk0]

FM patch sounds so fat. Great job, thanks for sharing

[@JosephDicasio]

How does one even begin to learn how to do these kinds of things? How to connect things to others and stuff

[@somedude4728]

Woah this guy GRIDS

[@Spankalicious_808]

Yes man! Yes yes yes yes! Much love and respect! ❤️🙏🏻🌿

[@mirrorme_portal]

amazing.subbed

[@KutAnimus]

Woah those are some SICK patches! Can I ask what kind of setup (workstation specs) you're rocking with?

[@AndreiOlenev]

Thank alot! I'm using a Lenovo Thinkpad. In honesty, it isn't a good computer for music production, because it has really bad dpc latency. I'm really hoping to get a different computer soon.

[@KutAnimus]

@@AndreiOlenev Which one of the Thinkpads though? There are... several :p I'm actually amazed that TPs can do so much processing.

[@AndreiOlenev]

@@KutAnimus It's a p71 from about 3 years ago. In honesty, it's cpu performance isn't very good. It is handling these patches ok though. I think the Grid is pretty cpu efficient, but I notice that the graphical side of it seems to slow things down, because the cpu meter goes up when the grid's window is open. I probably wouldn't get a Lenovo for music production, because they generally have problems with dpc latency.

[@KutAnimus]

@@AndreiOlenev Nah it's Bitwig Studio. They do graphical and audio processing on CPU. Obviously the audio processing takes priority here, hence the occasional slowdown on the graphical side. Btw, would be great to see a follow-up on this video :)

[@mølekule-l3d]

incredible! how did you initially learn all this stuff? did you do a synthesis course or something? please build patches from the ground up!

[@AndreiOlenev]

Hi. I have been using things like Reaktor, hardware modular synths, and VCV rack for years, so I found it pretty straight forward to apply a lot of the same ideas in the Grid. In my opinion, the grid seems to be the most intuitive modular environment to get a hang of, and probably the quickest to use. I haven't really been using the Grid for long, but when I got it, I just kind of went down the rabbit hole with experimenting with it. I feel like I'm still scratching the surface of what it can do. I will definitely make more tutorials building patches from the ground up.

[@mulqueen82]

so dope

[@charodeyjeddy5677]

wow! fire!

[@bci3937]

Do you uploaded some Stuff to Bitwiggers?

[@AndreiOlenev]

I'm planning on cleaning up some patches and putting them online soon. I'm a bit sidetracked with trying to finish up an ep right now. I'm hoping to get some grid patches and maybe a sample pack together in January.

[@bci3937]

@@AndreiOlenev yeah nice, these patches a pretty complex an messy for sure and i hope that Bitwig will give us options to clean up the mess...cheers

[@okoiful]

godamn son... whats that patch?

[@penroseconjecture5318]

are you sharing any of these patches?

[@AndreiOlenev]

I just found out about a couple pages where people share Bitwig patches. I didn't really know that was a thing. I think I will put some of them out. I will probably clean them up first and put notes on the patches, so that they will be easy to understand. I'll post on my youtube page when I get that together. I'm in the middle of trying to finish up a couple tracks right now, so I'll work on that after.

[@FredMurray]

Hello! Thanks for sharing your knowledge. Is this grid preset available now somewhere?

[@penroseconjecture5318]

Ya brother! Share the patch. IDE really like to dig into this to see how you did it. Really impressed

[@Paul-ui6in]

Why do you have Russian name and second name?)