Multiman2

It depends what you mean. If you just want to have your volume fader information in the region itself as opposed to the track then yes, it seems like you already have this. If however you want to actually convert the volume fader information to MIDI data (ie. you want to automate the instrument's volume control rather than the fader on your channel) - first make sure your volume fader automation is showing, then Option Click the Automation Parameter in the track header and select 'MIDI Control 0-63' then select 7=Volume. A dialog box will come up and ask if you want to copy and convert or just convert the data. Click 'convert'.

I think this only happens with the GarageBand legacy instruments. The Logic ones seem to load directly into the EXS24 instrument.

In the modulation section of EXS24 where 'Velocity' and 'S.Select' are set up - if you change 'Velocity' to 'Key' it will remap any sample layers across the length of the keyboard. To remap the actual loudness across the keys you can set up a second modulation in EXS24 with 'key' as your source and 'relative volume (auto adjust)' as your destination.

I agree - drawing in automation by hand can be tedious. Have you tried recording the Pitch Bend live with a controller of some kind? I sometimes use my phone with an OSC/MIDI app. such as TouchOSC for this kind of thing.

"Oboe Solo" has a layer with no vibrato. Better sounding samples too in my opinion.

I'm guessing it is being assigned to a fader somewhere in Logic. Check your controller assignments. Controller assignments will hijack a controller's MIDI function.

Firstly apologies if this doesn't make any sense. I find it quite hard to explain. Someone else might be able to do a better job. The Transformer can transform note on/off events to controller events but I've found it a bit buggy. I've also only used it to transform sequenced MIDI data (ie. not in the environment for events 'on the fly'). Essentially, in the top row, you set up the Status to = NOTE then below choose 'Fix' and 'Control'. This will transform any incoming note events into controller events. The Transformer doesn't seem to give you options for NoteOn and NoteOff so it tends to create events for both. The Pitch parameter is the 'first data byte' (which for a control change event corresponds to the CC number) so under 'Pitch' you'd set your condition to 'Fix' and the number to 43. This will assign any incoming pitch number to 43 (the first data byte of the CC event you want to send) You'll also want to use the original Pitch numbers to determine the CC values (CC value is the 'second data byte') so you need to click the blue line under the Velocity (data byte 2 for a Note event) parameter until it connects to the data byte 1 parameter. This will route the original Pitch number to your CC value. Once this is set up you will have to work out the operation on the pitch data to get it to map to your CC values in order to get the pitches you want. It will be probably some sort of scaling/adding I imagine - or you could choose 'Use Map' and just draw your own map in the blue bars at the bottom of the Transformer window. Unfortunately Transformer is not the most intuitive tool in Logic. It hasn't been updated in a long long time and it takes quite a bit of getting used to. I also don't know how buggy this will be. It always seems to take a bit of messing around before it works properly for me. Overlapping notes seem to cause a bit of chaos because of it creating CC events for both NoteOn and NoteOff. Edit: After having written all that it occurs to me that to transform MIDI on the fly it might be a lot easier setting up an External Instrument and using the 'Modifier' MIDI plugin.

You can create a 'master expression' MIDI track and patch it into multiple instruments in the environment.

I don't think the 'Export to Movie' function in Logic can deal with more than a stereo file. (Not 100% sure though) But.. you can easily bounce 8 interlaced channels from Logic in 7.1 then import your bounced audio file into a movie within in QuickTime or the editing app of your choice.

The ES2 and the EXS24 can use a side chain as a modulation source (envelope following). You can get some nice effects having an audio track affect various parameters - pitch filter cutoff etc.. Its not exactly what you want but its a start.

To start with this was using Logic 9 and Reaktor 5. I don't know if anything has changed on the updates but I'd assume it would work the same. Reaktor can be opened as a 5.1 or 7.1 insert plugin on a surround channel within Logic which means that you have up to 8 inputs and 8 outputs available within it to play with. You just open the plugin, create a new ensemble then create 8 in ports and 8 out ports. They now represent the 8 insert lines from Logic's channel strip. You can wire any input to any output and place any effect, panning device or whatever you want to build, in between. A nice thing about Logic's surround tracks is that you can drag mono or stereo audio files onto them (or any audio files containing anything up to 8 channels) If its a mono file the audio will appear at the first Reaktor input. If its stereo it will appear at inputs 1 and 2... and so on. Another nice thing is that there are inserts available on the Master surround output channel. This can be used, for example, to decode a b-format signal for an octagonal loudspeaker array. I don't know of any websites that explain it. I just figured it out by messing around. Surround channels in Logic are quite flexible if you use Reaktor to access the i/o.

If you just want to change the CC number then do it in the Event list editor. If you want to make a copy then Option-Click the Automation Parameter box, select the CC you want to copy the current CC automation to. It will come up with a box asking if you want to convert or copy and convert. Select 'copy and convert'.

If you have Reaktor it can work very nicely with Logic as a 5.1 or 7.1 plugin. You have access to up to 8 discrete channels to do whatever you want with including things like B-Format ambisonics.