Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

Forum Jump  
VE PRO Logic automation?
Last post Fri, Feb 12 2010 by stevesong, 4 replies.
Options
Go to last post
Posted on Wed, Feb 10 2010 12:00
by christof
Joined on Tue, Jun 19 2007, Vienna/Austria, Posts 195

Hello,

the following problem appears in Logic 9:

I have VE Pro server 64 Bit connected to Logic, now I want to draw volume automations for each midi channel in Logic.So I select e.g. track 2 volume and draw the automation curve.What happens now is that Logic does not trigger the volume of VE Pro's track 2, it triggers the master volume ( master bus).

Any chance to trigger just the selected midi channel?

Posted on Thu, Feb 11 2010 18:45
by cgernaey
Joined on Mon, Apr 04 2005, Detroit-Michigan, Posts 1062

I have seen this talked about, asked etc in about every possible choice of wording.  I myself don't do it so I can't tell you how but I do know if you do a search for "Logic Automation" all of those threads will give you an idea of what you can do.

Maestro2be

Windows 10 Pro 64-bit, 128GB RAM, AMD 3970X 32-core
Gigabyte TRX40 Aorus Xtreme, Radeon RX 5500 XT
Studio One 5.1.1, Cubase 10.5, Nuendo 10
RME Multiface 2, All NVMe SSD Drives (OS & Samples)
Posted on Thu, Feb 11 2010 22:17
by plowman
Joined on Sat, Dec 13 2003, Posts 1126

Yet another realm where I see things dimly. But it's possible that all CC#7's are grabbed as overall volume and not sent through, no matter what channel. 

Try this. Create a fader object. Assign Output: Control. Channel (whichever channel you need). -1- 3 (that is, it sends the first MIDI byte as a 3). The fader's input is not relevant for this exercise. 

Connect the fader to the VE Pro plug-in channel strip. To verify that your channel is being read within the VE Pro plug-in, move the fader and confirm the little green MIDI activity light on the far left of the instrument within VE Pro.  

Now right-click on the volume slider of that channel's pane (far lower right of the big blue window with the big eye). It will blink red, waiting to be assigned. Move the fader again. The volume slider should see it and stop blinking.   

So now a specific instrument within your plug-in will adjust volume to CC#3 of its assigned channel. Why not CC#7? I don't know. The volume slider doesn't accept it as assigned. In fact, it may not accept any of the dedicated CC's, from what I can see. Perhaps this is hard-wired, to avoid confusion.

Work backwards from here. Figure out some automation class that can drive SOMEthing that can be assigned per channel to the volume sliders. From my poking about, it seems that Fader and Meta classes cannot be assigned to an instrument's volume slider, only a CC not dedicated already. 

Posted on Fri, Feb 12 2010 14:36
by stevesong
Joined on Mon, Oct 18 2004, NYC, Posts 714

The simple solution is to use Controller 11 (Expression) rather than CC7 (Volume) as a controller for dynamics. In Logic, automation of CC 11 can be set independently for every channel of a multi-channel instrument whereas CC7 automation of any one channel affects all channels of a multi-channel instrument simultaneously. Why CC7 should have this un-useful characteristic in Logic seems lost in the annals of MIDI history, but it is so.

Stephen Siegel
New York City

MacPro (4.1) dual-quad Xeon @ 2.9.3 Ghz
24GB RAM; OS 10.8.5
2 960 GB OWC E2 Mercury Accelsior SSDs one dedicated to samples and the other partitioned into a partition for samples and a part ion for apps and files.
MOTU 2408 MK III (PCIe)

MacBook Pro with 2.5Ghz Core 2 Duo
4GB RAM; OS 10.8.5
MOTU 828
Firmtek/Seritek 2SM2-E Express Card SATA adapter.

Logic 9.1.6.; Finale 2011
You cannot post new threads in this forum.
You cannot reply to threads in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.