Echoboy Vst Plugin Free Download
Shinyoung Gedris
Plugin Boutique is on a roll with its deals at the minute, and this week it has worked with effects plugin brand Soundtoys to offer up to 75 per cent off on a number of its popular products, including the EchoBoy, the SuperPlate and the PanMan.
Decapitator is one of the most popular saturation plugins around. A big reason for this is its extensive selection of analog saturation models. The appropriately named DrumFattener2 preset is among multiple drum-focused presets on offer and it works like magic on a drum bus!
Now this isn't happening, the breakdown is in the parameter name it's not being learned. So in the best if I was doing the above with let's say an Echoey plugin and controller assignment section would show that I'm about to learn for "Echoboy: Feedback", now all it reads is "Echoboy: -" without any parameter passed
The only things I am able to MIDI map and control successfully are in the core DAW (e.g send controls, volume, pans, key commands...etc) as well as the most basic logic plugins (e.g noise gate) but not others (e.g space designer)
Narrowed down a bit further, created a fresh bus, controls it fine, but only when the track is selected. My previous template had the association bound to a specific track through Fader Bank and a number. Still not sure how to pass the parameter in this case
controls it fine, but only when the track is selected. My previous template had the association bound to a specific track through Fader Bank and a number. Still not sure how to pass the parameter in this case
Bullet #2 is my intention, and my issue is that I had this mapped before as such. The problem now is when I try to map it that way (knob on a plugin from an unselected track) logic MIDI learn only recognizes the plugin but not the exact parameter, so the binding never actually works.
Probably because you are currently targetting a track with that assignment that doesn't have that plugin on it, therefore Logic isn't reading a parameter from it. It'll probably come back if you are targetting the correct track with the plugin on it.
Yes, exactly like I said, because as soon as you select "Fader Bank", the index of the track is likely changing so you are targeting a completely different track than the selected one, that hasn't got that plugin on it - which is why the parameter isn't showing up.
It is picking the right index though. I've confirmed this by changing the Faderbank number and tried several values to cover the whole tracks, it always automatically reverts to the original number it identifies whenever I click the plugin so it is picking the right one, just not the parameter
Ok, if you're sure you're targetting the correct audio object (which is a combination of the fader bank number, and whichever offset position in the current fader bank that track is), I'll try to replicate this and see what happens here...
So I can't replicate this here. I don't have the individual Echoboy plugin, but used their Little Plate as an example, and the displayed parameter in the learned message shows up both when the plugin is on the selected track, and also if I select another random track, and try to learn a plugin parameter from that plugin on a bus.
In the below example, I had an instrument track selected, with Little Plate on a bus fed by an unselected audio track. You can see the track is referenced by fader bank, and the parameter I was learning, "Decay", shows up...
Can you quit Logic, and temporarily remove your pref files (both your main prefs, and your control surface prefs - though that's the important one really - make sure you have backups! You can put them back afterwards.)
BTW as if that isn't vexing enough, if I put the launchpad in control surface group 2, no problem, in group 1 it causes the problem. Was able to get two groups by connecting a second controller (Nanokontrol)
Even though it controls everything correctly, the controls don't seem to be associated with it as a control group because the control bar extend past 8 tracks which is how many the Nanokontrol can handle at a time and also the bar control marker isn't the purple color it's supposed to be. Any thoughts on that please?
I don't really know the cause of this behaviour, certainly not enough to categorically explain it, it's just a hunch given on how much control surface stuff I've done with Logic, including developing software that takes to Logic pretending to be an MCU.
But in short, with a control surface active, the internal state of Logic depends to some degree on it's interaction with control surfaces, and sometimes it can get into modes or even states where things don't work as expected, and it's not obvious what to do to get things back to normal again (the usual procedure is to trash/restore working preferences, or rebuilt the defaults for that controller again.)
Like I say, I don't know exactly what is going on, as Logic's control surface handling is a bit of a black box in many regards, but the fact these issues go away without your control surfaces active is a good clue.
Note - for me, I have a ton of control surfaces in my Logic setup, including five Mackie Control devices (real, pretend, and virtual), a Mackie HUI, Korg Kontrol and Nanokontrol and other things too. So it's not like simply having a control surface present breaks things - as I say, I can't replicate this behaviour here, it works as expected.
Also, it's not uncommon that adding new devices can break assignments, again for reasons of MIDI port addressability and how Logic stores things in some regard. I take adding a new control surface as a delicate operation - I have backups of known good configurations, and when adding a new one, I will check anything has broken, and fix it, and once everything is verified good, will make new known good backups etc, but I have very specific custom setups and don't want Logic breaking them (which it does, on occasion, for no reason I can lock down, which is also why I have a script to just restore my control surfaces prefs back to that known good state if and when something stops working as it should).
Thank you so much for trying and also the educational and in-depth explanation above, I appreciate it. I think I'll have to revisit my c controller situation and see how I can create the workflow that doesn't impact basic things like MIDI learn but still utilizes controllers properly
Also keeping regular backups of last known good configs is a great idea especially before any changes. It's so odd how Logic manages these feels archaic especially compared to the level of sophistication and control the software has otherwise
c80f0f1006