

shivermetimbers wrote:ski wrote:BTW, your "figure 2" is missing.
It's always been there on my comp screen, sometimes they don't show up like the avatars.
Ski,
New idea. What about SYSEX (not sex) to do some of these things?
[i]"...Note: SysEx faders can actually be used for any kind of MIDI event, making them handy
for sending ordered batches of messages, such as mixer or control panel snapshots—
with one click of the mouse."
Oh the possibilities... Quick, someone tell me this won't work before I get a boner.
Snowdon wrote:Hello,
Is there a enviroment 'creating a macro tute' anywhere on this forum.
I am trying to duplicate both Ronnie eggs and Davids ' effects by pass templates', but i cant seem to work out the 'creating a macro' stage.
If someone could give the time to jot a down a step by step way of by-passing one channel strip having 5 effects on it ,I would greatly appreciate this.
This is driving me crazy and making feel stupid at the same time,not a good combination for productivity.
This is what I am doing as a basic template:
1 Create a new project.
2 Create a new track [1] and add 5 plugins on it.
3 Open the enviroment window showing the 'mixer'
4 Create a new monitor in the "New' pull down options list
5 Cable from the channel strip [1] into the monitor
6 'Option/Click on each plugin which mutes it and send the relevant information to the monitor.
7 Where to now? If I create a macro logic crashes.
Any advice would be gold.
Thanks


jordito wrote:trozombo, you need to open the environment window first (Command+8 ).
J.
trozombo wrote:is there anyway I kind import david's template to a project fully developed?


jordito wrote:trozombo wrote:is there anyway I kind import david's template to a project fully developed?
Yes. There are several ways to do it, you can import the layer, drag and drop between to projects, copy/paste....Check the manual for details.
J.
fader8 wrote:Here's a more efficient macro I did for myself that's designed to companion to its own channel strip. Rather than have all the transformers, it just has a single sysex fader that spits out all the bypass/unbypass messages for all 16 slots.
Just cable the macro's output to a channel strip. Check the Inst box if you're using it on an instrument channel.

David wrote:Sure: first I inserted plug-ins on the channel strip, cabled the channel strip into a monitor and looked at the events created by bypassing the plug-ins. I know if I send those same events to the channel strip, it will bypass the plug-ins.
The button you're looking at is actually inside a macro. Open the environment and resize the macro a bit, then double-click it to unpack it.
You'll see a button cabled into 3 transformers, then into the channel strip.
The button generates one event: Fader #56, which is the insert bypass for the first slot.
The first transformer duplicates that event and adds 1 to the Fader #, bypassing the second slot.
The second transformer duplicates both events and adds 2, bypassing the third and forth slot.
The third transformer duplicates all 4 events and adds 4, bypassing slots 5 through 8.
And ... voila!!!
noisecontrol wrote:Just wanted to say what a great post. This methodology can be applied to so many aspects of Logic


Return to Logic & MainStage Templates and Environments
Users browsing this forum: No registered users and 0 guests