Using XFer LFOTool as modulation source in Cubase 10

Поделиться
HTML-код
  • Опубликовано: 13 сен 2024
  • In this video, following up on my last one on side-chaining using Xfer LFOTool, I show you how to set up the routing to use LFOTool within Cubase Pro 10 as a modulation source for both external & native plugin FX.
    First I go over how to set it up natively using MIDI learn functionality within FabFilter Pro Q3 to automate a notch filter & then how to use it in conjunction with a MIDI loopback driver (LoopMIDI) to route it to modulate a native Cubase effect without MIDI learn (using Quadrafuzz) set to be triggered by a MIDI track in cubase in LFOTool's envelope mode.
    I also briefly touch on how to use the internal LFOTool filters which are identical to the filters that come included in XFer Serum.
    I hope this helps, as it took me a little while to get my head around setting up LFOTool to use in this way within Cubase. Please drop a sub to support the channel, and as always, thanks for watching!
    Matt

Комментарии • 40

  • @theauthor1000
    @theauthor1000 Год назад +1

    Wow, I was looking for something like that my whole life.... Thank you )

    • @hazmatproduction4562
      @hazmatproduction4562  Год назад +1

      Meanwhile I got fed up with having to do stuff like this & bought Bitwig 🤣
      If Steinberg ever add a native modulation system to cubase that rivals Bitwig’s I’d come back to cubase in a heartbeat, but I just don’t think it’s possible, and even if it was, I don’t get the impression it’s something that’s too badly wanted from the general Cubase user base of mix engineers & scoring composers.
      For electronica, Bitwig or Ableton have the market cornered & cubase has a lot of catching up to do on that front

    • @theauthor1000
      @theauthor1000 Год назад +1

      @@hazmatproduction4562 Hehe, can't agree more, learning Ableton at the moment after 13 years on cubase, altho I am emotionally connected to cubase, not sure I can make the transform.

    • @hazmatproduction4562
      @hazmatproduction4562  Год назад +1

      @@theauthor1000 yeah it’s a tough commitment to change DAWs. Having one of each (like a non linear, device based workflow like Ableton or Bitwig Studio, and a more standard linear DAW like Cubase or Logic can have its benefits though.
      Bitwig is my sound design playground really. Good for getting intial ideas off the ground or for playing with modulating insane racks of synths & FX, like it’s all one instrument. Cubase is a much better mixing environment, nicer to look at, has a better sound engine, ARA2 & basic video audio features.
      For anything involving modulation, synthesis, plugin layering or routing though… so sound design workflows especially… Bitwig has cubase looking like a dinosaur in a lot of ways. It basically has reaktor built right into it, but aside from that, there’s no better DAW out there for squeezing the most out of a varied 3rd party plugin library. I can use Diva’s oscillators & filter, using Saturn, or even decapitator in multiband as distortion, if you want to take it that far. And Fabfilter Pro R instead of Diva’s default reverb. Then modulate it all with Bitwig’s LFOs, add X/Y modulators… basically do whatever I want.
      It’s this level of freedom that Cubase is lacking to compete when it comes to sound design.
      You can do stuff like this with Reaper but it’s nowhere near as elegantly implemented as Bitwig. It was started by some of the original Ableton devs, specifically to break certain limitations that come with DAWs that were originally designed years ago when these limitations were just the norm. What they’ve done is sort of created a lot of what max4live can offer in Ableton, but made it all native to Bitwig’s core infrastructure so it’s all seamlessly integrated. They’re the new kid on the block so can’t compete with the huge libraries of native instruments & FX that you get in DAWs like cubase that have been around, tried & tested since the dawn of computers. So it seems more like they focused on creating a core DAW infrastructure that caters more towards squeezing new life out of a large selection of 3rd party tools. It has some very interesting FX though, don’t get me wrong. The sampler alone is crazy powerful compared to cubase sampler tracks

    • @theauthor1000
      @theauthor1000 Год назад

      @@hazmatproduction4562 Thank you for the invested replay brother, I will continue with my journey and hopefully will find the optimal workflow for me, and again.. Thanks for that video :)

  • @louisdubeau9193
    @louisdubeau9193 3 года назад +1

    Game changer for me. And with one instance of LFO Tool i can have 12 différents LFO using the 12 chancels of the LFO Tool. So Much thanks

  • @gatty.
    @gatty. 4 года назад +1

    My mind is blown. Will try this in FL Studio tomorrow, pretty sure it has the same capability.
    Game changer!

  • @RickMors
    @RickMors 4 года назад +2

    Recently found your Channel. Please keep doin your work. Really amazing watching you how you play around to get your samples right, and how you use Groove Agent. Master Class. Thanks.

  • @evodem
    @evodem 3 года назад +4

    - How much do you want to be complex?
    Cubase: YES.

    • @hazmatproduction4562
      @hazmatproduction4562  3 года назад +2

      IKR
      I’ve been hoping for some native LFOs & envelopes that can be assigned to anything in a project for ages. The midi inserts are so dated & clunky to use.

  • @zsozsonagy2182
    @zsozsonagy2182 2 года назад

    The Drum And Bass style is cool.

  • @gazmellen7881
    @gazmellen7881 4 года назад +1

    like your way of thinking sweet!

  • @kaceaudio6725
    @kaceaudio6725 4 года назад

    HOLY FFFFFF. I love LFO Tool, mostly cause I hate managing automation. I always wished I could modulate other FX the same way... and guess I can! TY!

  • @billyshakespeare1696
    @billyshakespeare1696 3 года назад

    Thank you for this awesome tutorial! I think I’ve got the Q3 technique down, but will probably pass on the rest lol. Above my pay grade!

  • @evodem
    @evodem 3 года назад

    Thank you man for these great infos!

  • @zweiklangmusic
    @zweiklangmusic 4 года назад

    Great video, thanks a lot!

  • @DrKaoliN
    @DrKaoliN 3 года назад

    Awesome! 🔥🔥🔥

  • @joshwilson2038
    @joshwilson2038 2 года назад

    this is super helpful - thank you so much! I'm using LFO tool to modulate panning in FabFilters Volcano, however, I noticed it only works if I have the midi track armed for recording. I'm following the first example you use. Do you happen to have any suggestions to keep the lfo tool working if I want to disarm the midi track?

  • @mtone2487
    @mtone2487 2 года назад +1

    I started watching this video not realizing that you were also the same account commenting my exact sentiments of disappointment concerning the new FX Modulator in Cubase 12 on another Steinberg video. Do you still use this setup with LFOTool for general plugin modulation? You also mentioned using Bitwig in your other comments and it has piqued my interest. Great video and thanks!

    • @hazmatproduction4562
      @hazmatproduction4562  2 года назад +1

      I use Bitwig exclusively in sound design sessions now. Also great for getting ideas down quickly.
      Cubase is a better environment for mixing, working with audio & is ARA2 enabled, with basic video audio features (which Bitwig is lacking)
      I love both. They are very different beasts and both have their strengths that fill voids in each other’s feature sets
      Now I updated cubase to 12 I will be doing a Bitwig vs cubase video on this channel very soon, highlighting the strengths each DAW has over the other for different workflows.
      Been wanting to do a head to head comparison video since I got Bitwig, but wanted to give Steinberg a chance to catch up on modulation or other areas. Unfortunately FX modulator doesn’t fit the bill. But I wanted it to be a fair comparison so I’ll be doing Cubase 12 vs Bitwig 4.2 Beta

    • @hazmatproduction4562
      @hazmatproduction4562  2 года назад +1

      Basically it’ll look like this
      Things I wish cubase had:
      Flexible modulation system
      Native Multiband crossover solution
      Flexible VST hosting
      Clip based automation
      Non linear sequencing
      Things I wish Bitwig had:
      Native MSEG mod source
      Better sample management (like mediabay)
      ARA2 extension compatibility
      Scale / chord features in MIDI editor
      Bitwig also has no pitch correction solution natively, but I have melodyne studio 5, which I always preferred to variaudio anyway

    • @mtone2487
      @mtone2487 2 года назад +1

      @@hazmatproduction4562 I see! Good to know you love and use both. I'll be looking forward to your comparison video. Thanks for responding!

    • @hazmatproduction4562
      @hazmatproduction4562  2 года назад

      @@mtone2487 the above list are basically the features either DAW would need to add, for me to use it exclusively and ditch the other.
      There are obviously more differences than I posted above, but those are the big ones each DAW is missing from the other.
      I should also add Mixer snapshots to the Bitwig list. It’s one of the main reasons I still prefer mixing in cubase. That and lack of experience in Bitwig. I’ve only been learning it 2 months and haven’t had as much time as I’d like to work on music lately, so I haven’t taken anything to final mixdown stage in Bitwig yet. But I’ve messed around with stems from older projects in there & it’s definitely not as nice a mixer to work with as Cubase mix console
      Overall Bitwig still comes out the winner for me just because of the modulation system & the grid (a native reaktor like environment for building modular instruments, FX or midi note trigger devices).
      Most of what Bitwig is missing is replaceable with 3rd party solutions. Everything but ARA2 & mixer snapshots really. But I can always use spectralayers or melodyne in standalone as audio editors (or within cubase as ARA2) and import to Bitwig & mixer snapshots would be easier to live without than such a flexible modulation system & the ease of using other tools like multiband fx containers, over the cubase method of bussing groups and making crossovers with EQs.
      I’m always finding cheeky workarounds from the community in Bitwig to do tasks that may seem missing as a cubase user, at first too.
      An example is that it doesn’t have a chord track, but you can get around that by adding a midi clip of your chord progression to the clip launcher & using it as a note trigger for other devices. You can lock it to a scale even. At first it seems Bitwig doesn’t have any chord & scale features but you can build them in the grid or use clever solutions just because Bitwig is so modular. You can set the audio from any point in an FX chain as an input or sidechain trigger. Say you want your sidechain to have the need of some overdrive, but not the dynamics you apply later? You just set the output if the distortion as the sidechain input. You can even do this stuff with audio rate modulators. It’s deep stuff but very rewarding. It’s like the kiloheaets ecosystem on crack. You’re not limited to just khs snap ins. You can do what you can do in their environment with any plugin you own.

    • @mtone2487
      @mtone2487 2 года назад +1

      @@hazmatproduction4562 Man that sounds crazy! I haven't even begun to get into it this deeply. Is there a ReWire configuration possible with Bitwig as a slave to Cubase? Forgive me if this is an obvious answer, I'm still just getting into this stuff and don't know much. One of the things I love about Cubase is how fluent and speedy my workflow is because I know it so well, so it would be nice to keep using it as much as possible. I've just started looking into kilohearts too, it seems pretty cool.

  • @detralaudio
    @detralaudio Год назад

    Thanks a lot! This helped me so munch. Plus, I have a question. Is there any chance to have capability of adjusting the speed of this notch's sweeping with automation of lfo tool. I mean, the upper automation goes the faster notch sweeping gets. This will solve my dilemma whether to switch to cubase or not. Bc I haven't found a feature of creating automation of any effect plugins in cubase, unlike other daws.

    • @hazmatproduction4562
      @hazmatproduction4562  Год назад +1

      Honestly man I barely use cubase anymore. I do all this stuff in Bitwig because it’s built to modulate all the things natively. Still prefer cubase as a mixing platform though by far.

  • @RamonCalvoMusic
    @RamonCalvoMusic 2 года назад

    Hey I have an issue with this, in the first half of the video I followed along everything works just like it does in your video... however this only works as long as your MIDI track is selected, as it is in your video. If you click on your instrument track, the midi information is no longer being sent to the plugin. How to make it so that this continues working even after selecting another instrument track?

    • @RamonCalvoMusic
      @RamonCalvoMusic 2 года назад

      Actually the problem seems to be even worse. Not only is it as I described, but it also only seems to work as long as Fabfilter plugin window is open and the frequency has been clicked. If you click on another part of the plugin, it stops working, making this trick not helpful for music production or recording. What am I missing?

    • @hazmatproduction4562
      @hazmatproduction4562  2 года назад

      @@RamonCalvoMusic I’ll look into it. I recently switched to Bitwig because it makes these kinds of modulations much easier. I’ll try & replicate this issue sometime & see if I can help you out.

    • @hazmatproduction4562
      @hazmatproduction4562  2 года назад

      @@RamonCalvoMusic first thing that may help is activating record enable on the midi track so it stays enabled when other tracks are active. Think there’s a setting somewhere that toggles activating record enable on selected tracks. If not that it may be the read automation that needs to stay on. I’ll try & test it later

    • @RamonCalvoMusic
      @RamonCalvoMusic 2 года назад

      @@hazmatproduction4562 Thank you! Yes that was it

  • @ma3boch
    @ma3boch 3 года назад

    loop midi for mac or just win ❓

    • @hazmatproduction4562
      @hazmatproduction4562  3 года назад

      No idea on that, I’m afraid, but if you Google Mac midi loopback driver, I’m sure there are probably options

    • @ma3boch
      @ma3boch 3 года назад

      @@hazmatproduction4562 thanx bro 🙏🏻

  • @jasoncruizer
    @jasoncruizer Год назад +1

    And this is why i prefer Ableton over Cubase to design inside of, i can whack the stock LFO tool in a chain and have 8 parameters be affected from 1 LFO instance in varying amounts. No need for new midi channel, no need to do anything complex just choose the Lfo tool and assign the parameters to be affected, why cant cubase rival it !!!

    • @hazmatproduction4562
      @hazmatproduction4562  Год назад +1

      It’s why I switched to Bitwig studio too. Love cubase for other things but it’s a chore to use for modulation

    • @jasoncruizer
      @jasoncruizer Год назад

      @@hazmatproduction4562 Yeagh its a shame, ive been a cubase user for years, but theres things within it workflow wise that are a real complex pain in the backside, Steinberg is owned by Yamaha I'm shocked they haven't overhauled the Lfo > midi situation and made it more like Ableton/Bigwig modulation tools.
      Cubase seems to be like a Rolls Royce unaware many drivers want a merc or an audi.

  • @KitKalvert
    @KitKalvert Год назад

    Helpful video but a ridiculous amount of work just to modulate a damn parameter (especially referring to the many non-midi learn plugins) - so off putting and making me think about getting Ableton tbh

    • @hazmatproduction4562
      @hazmatproduction4562  Год назад +1

      Understandable. It’s why I switched to Bitwig for my sound design workflow in particular