Unsexy Plugins: Fruity Send

แชร์
ฝัง
  • เผยแพร่เมื่อ 28 ม.ค. 2025

ความคิดเห็น • 25

  • @TerryMeighan
    @TerryMeighan 2 หลายเดือนก่อน

    This is simply the best video I've seen explaining fruity send and its functionality. I've used FL for a very long time and this perfectly clears up the confusion. Liked and subscribed 😁

    • @steevmsteevm
      @steevmsteevm  2 หลายเดือนก่อน +1

      Thanks for the kind words!

  • @musicfan8867
    @musicfan8867 ปีที่แล้ว +1

    Thanks for this. I learned a basic thing in the start of the video that I've been searching for for years. 🙂

  • @Overxpossed
    @Overxpossed 3 ปีที่แล้ว +2

    Oh man I was also thinking how to hear only the resulting sound, the effect without the initial sound; Delay 3 has that option built-in. This send plugin allows to mix different groups of instances, let say, mix some drum's mixing qualities with pads mixing qualities without having to mess with, you know... a lot of virtual cables and buses xD Shame the Send cannot be automated; it would give the same rsult as the new automation sequence (sequential) of Layers but with the effects instead with instruments and synths. Probabbly it would take too much CPU usage or buffer. I'm just at 2:35 trying in FL and my mind is blown. So i's like you put all the master effects in some part of the mixer and send to them all what you already effected. Pretty much organised!!! Thanks a lot!!!

  • @knocky3659
    @knocky3659 3 ปีที่แล้ว +1

    This video is actually pretty amzing, great man!

  • @willia_music
    @willia_music 11 หลายเดือนก่อน

    ever have a problem when, later down the line, adding more sends onto a track.
    example: sending snare to drum verb. Then later sending snare to a parallel compressor.
    I've had this mess up the sends order. Meaning, the 'fruity send' that was originally pumping audio to the drum verb is now shifted to the next send
    wondering if there is a best practice or way around this

    • @steevmsteevm
      @steevmsteevm  11 หลายเดือนก่อน

      Yes, it's covered in the video around 12:58, and why I name all the instances.
      It's not just Fruity Send that has this problem btw, it's a bug in the programming to do with how sidechain tracks are indexed/selected. You get the same issues when using sidechain compressione etc. too. It can be very annoying.

  • @wicsiow
    @wicsiow ปีที่แล้ว

    Very informative, deserves far more views 👍

    • @steevmsteevm
      @steevmsteevm  ปีที่แล้ว

      Thanks! I think it's a bit of a niche plugin tbh that most people don't even know exists. Whenever I bring it up in discussions, it often seems to be the first time they've ever heard of it.

  • @happysinha
    @happysinha 5 หลายเดือนก่อน

    Fruity send act like prefader it means wtever m applying on main channel like eq compression to control dynamic fisrt
    Is my reverb signal flow received comoessi
    D signal?
    Don't know u get my point or not

    • @happysinha
      @happysinha 5 หลายเดือนก่อน

      What should I do u want my reverb as present but I want my main channel should be compressed first then go to reverb send
      If I apply send it will send my signal compressed to rever

    • @steevmsteevm
      @steevmsteevm  5 หลายเดือนก่อน

      Yes, it's pre fader (but you get a volume knob to determine the send amount), but you can choose where you want the send to be in the chain. Where exactly you want to put it depends on what you are using the various effects in your chain for.
      I'd definitely put the send after any compression if you are doing this on vocals, - the compression is there to level out the signal and make sure that the vocals are consistent throughout. You don't want your reverb to have big spikes on plosives or where you got excited and then disappear when you moved away from the mic. So it makes sense to level (compress) first, then send.
      As for EQ: you might well have 2 EQs on the channel: 1 to remove any low frequency rumble or room resonance at the start of the chain and before any compression, then one at the end of the chain to get the vocals sitting nicely in the mix. The send might want to be between the two of them - remove the rumble and resonances, but ignore the EQ at the end of the chain that is there to get that channel to sit nicely in the mix.
      On the other hand, if you are using the reverb send for drums, trying to emulate "drums in a room", you might want to send pre compression, as you are using the compression to bring out aspects of the dry sound ("close mics"), whereas you want the room to sound like there is a drum kit in the room - and that drum kit doesn't have any compressors built in.
      So, as with many things, how you want to set things up is a case of: it depends. I think a good question to ask yourself would be: what is this effect doing? Is it cleaning up the sound? Is it helping this particular channel sit well in the mix? If the effect is cleaning up the sound (removing rumble, leveling it etc.), then the send *probably* comes after it. If it's very channel-specific, then maybe the send comes beforehand. But you might get good results putting the send right at the end of the chain too - you can always try it out and see!

  • @Gloomer2000
    @Gloomer2000 3 ปีที่แล้ว +1

    Around 4 minutes you've lost me and it was getting too difficult to understand. But I do appreciate your tutorials. Happy ending of the year bro!

  • @timppaUT
    @timppaUT ปีที่แล้ว +1

    Easy fix to hear only solo channel on that fruity send channel might be to automate that send button on/off switch with channel solo/mute button so when channel is muted so would be its fruity send?
    PS: Ok nevermind! On that next "mute" video you said that you can't automate mute button, so: Back on a drawing board!

    • @steevmsteevm
      @steevmsteevm  ปีที่แล้ว +1

      If you only mute the channel in the mixer, the signal is still routed through Fruity Send. You could put Fruity Mute 2 *before* the Fruity Send to prevent the signal getting that far. But as you can tell, it gets convoluted.
      You can automate the on/off of the Fruity Send plugins themselves of course. But setting that up to work automagically also gets convoluted, especially as you route more and more stuff to the send channel. If you really need to, it's probably easiest to either just manually turn off the Fruity Send instances and/or turn off all FX on the channels that are routed to the same send channel.
      Most of the time, I find it's more useful to be able to balance everything being routed to the same send channel, rather than worrying about the dry/wet blend of an individual track. Once the balance on the send channel makes sense, you can just blend in the wet amount for the whole track by ear.
      At any rate, it's probably good to know what the limitations are, because that will allow you to make decisions based on what it is *you* want to achieve.

    • @timppaUT
      @timppaUT ปีที่แล้ว

      @@steevmsteevm So how about "easy fix"? :P First send signal to separate channel that has only fruity send! Would that work?

    • @steevmsteevm
      @steevmsteevm  ปีที่แล้ว

      It'll quickly eat up channels if you're sending multiple instruments to that bus (and if you aren't then just put the effect on the same channel as the instrument?). I'd take a step back though, and ask the question: what problem are you trying to solve where you want to hear just the dry and wet of one instrument? Because, chances are, that's not really something you need to worry about much in the cases where you are using a send this way. If you're using your reverb to "put things in a space", then it's less about how one instrument sound through the reverb, and more about how that reverb (with all the elements going through it) meshes with the rest of the song as a whole. In that case, getting the blend of instruments on the reverb channel is more important ("the sound of the room") IMO - and you can listen to the entire wet signal (without the dry channels) to do that - which you can't do without using Fruity Send.
      This isn't the same situation as when you are using the reverb as part of the sound of "an instrument" - be that a synth lead or a guitar solo. If the effect is a key part of that sound, then I'd just put it on the instrument channel, rather than using a send. Typically you'll only want that one instrument to get that effect anyway, so Fruity Send isn't the best choice IMO.
      Which isn't to say, that it wouldn't be nice if there were an easier way of just listening to one instrument going through the send. But I don't personally feel like it's a problem for the aforementioned use case - at least, I haven't found this a big issue from a practical point of view. It's still worth being aware of so you can make the right choices as to which approach to take when.

  • @thalia6550
    @thalia6550 3 ปีที่แล้ว

    Good video! Now make one on the most unsexy plugin... Fruity Mute 2

  • @deeplyaffected3520
    @deeplyaffected3520 3 ปีที่แล้ว

    You explian is very difficult.
    Unlike a bunch!👎👎👎

    • @steevmsteevm
      @steevmsteevm  3 ปีที่แล้ว +1

      I'm afraid I don't understand.

    • @mikesaintjulesmusic
      @mikesaintjulesmusic ปีที่แล้ว +1

      @@steevmsteevm He's saying your explanation is difficult to follow. I found it fine personally. I haven't used the fruity send all that much to be honest. I would just left click the sidechain knob and turn it on accordingly at times. Though I can see panning the effect on the send channel can give interesting results while the main audio source is centered.