Region automation Q

I'm using an m-audio oxygen 61 and have some knobs and faders assigned to interact with Vienna Instruments. I've been able to record MIDI data from these controllers, but I'm currently unable to find a way to edit one of them. With region automation open in the piano roll view, I click the arrow to open up the various options and go to "other." Here there's a list of various controller options, including some that simply give the controller number, but the number I'm looking for (controller 52) doesn't appear. Is there a way to edit a controller like this that doesn't appear in the list of options, i.e. can I tell the region automation editor to look for a specific MIDI controller number of my choosing?
I could change which number that MIDI controller points to on the keyboard, but I'd then have to change a whole bunch of Vienna Instruments templates I have set up. Any help would be greatly appreciated.

ummm... wow... could you give me a hint on how to control automation in Logic using the Oxygen61? I figured out how to assign the knobs to different parameters (ie Filter Cutoff), but why won't Logic control it as automation when recording?

Similar Messages

Region automation help

i can't figure out if i'm doing something wrong or if this is a limitation with region automation of plug in parameters.
when i automate a parameter within a plug in by grabbing the on screen control while "midi" recording automation, i am able to record that parameter's movement. i am then going to the "hyper edit" window to visually edit my moves.
the problem i am having is, if the parameter is past the number 128, it is not letting me add in automation moves in the hyper edit window with the pencil tool the way it lets me if the plug in parameter lands in the first 128 parameters. it is however playing back the moves as i recorded them in real time and allowing me to edit bars in the hyper edit window that i recorded in real time. its just not letting me add any, or if i erase some, it's not letting me replace them with the pencil tool.
basically, everything works fine and as expected, except when im trying to edit automation parameters allocated past "fader" 128.
i am new to this forum stuff, so please let me know if i left out some important information.
thank you
G5 Quad Mac OS X (10.4.6)

probably it's late here and i don't get your question right,
but if yes >read the following:
http://en.wikipedia.org/wiki/MIDI
this bit>>MIDI controllers in the data stream<<bottom of the page

Is it possible to automate software instrument parameters in a MIDI region? And alias the region with the automation?

I am trying to track down a detail about how automation works in Logic Pro X.
What I want to know is:
1. Can I draw control-point curves (and smoothly bend them) in a MIDI region to automate a software instrument parameter (and/or smart controls)?
2. Can a region containing this automation be aliased and reused around the timeline (without the automation points being duplicated)?
If this is possible, can someone please post a couple of screenshots - a MIDI region with MIDI Draw automating (for example) the cutoff of an ES M, and screenshots of aliases around the timeline?
thanks!!
H

First, I'd recommend going to Track>other>new with same instrument. This gives you a blank lane to make a region with no notes.
Now, there are two strategies: do some track automation and then convert it to region. You can go into the local view menu and find the option to view MIDI automation and still adjust it. Now you can make aliases of that region. You need to be careful of accidentally writing new track automation, which is easy to do and can happen if you have 'move automation with regions' on for instance. If you make sure and delete all the track auto for this parameter you should be good (the line should be barely visible black, if it is highlighted in color, that means there is at least one active node at the beginning). If the parameter freaks out, instead of following your curve, you can bet there is track automation fighting with the region automation, you might need to tell the automation menu in the track header to show the parameter in question. None of this is a big deal and after doing it once you'll see.
The other strategy is to assign a controller to a parameter (or use the quick MIDI things on certain instruments - you mentioned ES2, which has that) and you can use the hyper draw in the piano roll. The view tip from the first strategy still works so you can edit the automation in the arrange. I prefer the first strategy because the knob you are automating will still move.
If you go to audio tuts plus (something like that) you can find a tut on the first method that's a few years old, and from Logic 9. Basically the same, you just have to look through different menus for everything.

How to copy region, without copying region based automation.

Say I wanted to copy a region to another track, for instance the track below. If the region that was going to be copied had region based automation, say modualtion or pan region based automation. Is there a way to copy the region, but not the region automation on it?
Cheers

if the automation is MIDI data within the region, then no, you can't copy without the data. It is very easy to delete the info after moving it. Just select, for example, 1 instance of cc#1,Then "select similar" from the edit window, then delete. Repete as necesary for other controller types.

Region based automation could be better

Just want to put this out there...
Region based automation was one of the things which i thought Apple had finally changed for the better but after using it for a while I'm not so sure.
Its great to be able to put the automation within the region but i feel they really should have extended the idea to mean it doesnt affect the channel strip volume. What I'm suggesting is that there should be 2 lanes of volume automation, one for the region, and one for the channel.
This would mean having much greater control over volume changes of individual regions but not having to worry about the overall track/channel level.
Ill send the feedback to apple but first thought id see if anyone agrees or could add to it.

You want "convert track automation to region automation" and you can find it I think in the right-click menu and if not there then either in one of the arrange local menus or up in the global mix menu. Poke around and you'll find it.

Anyone else had this problem with automation?

Its quite basic... and there is nothing on this in the manual that i can find in the automation section at all... I have an FM8 track recorded via midi on an instrument track... I put the automation in touch... I press play and record automation in this case on the talk wah "size" and it functions properly (when i let go it resumes the position it was in, and it records the automation data=I can make it visible) The automation will play until i try to record another pass of automation using a different parameter on FM8 which was "mouth" rather than "size" this time... when i try to record the second pass of automation it appears to be playing the other parameter's automation i had just recorded until i actually start automating the new parameter... then it stops playing any previously recorded automation and wont play back ANY automation from there on out... is this a bug anyone has encountered? I just made the switch from pro-tools to logic cuz i hate digi design... but should i upgrade to logic 8 since i bought 7 after august 1st before 8 came out? any suggestions in the meantime would greatly help... i have a deadline for this song by this sunday and this effect really adds alot, it would be greatly appreciated if anyone has encountered this.. and if you cant answer my first question then maybe you know how to record an instrument track to an audio track to where i could perform the effects manually as its recording to an audio track... So far any bussing techniques i know have failed despite the level showing up as if there were signal.. any help would be greatly appreciated
Desperate Composer

I rarely record automation, and when I do I never do a second pass (usually hand draw automation in) but I have had problems with Logic 7 no longer playing back automation. I've been told its fixed in Logic 8, but in the mean time here is a work around.
Select the region where the automation is (if there is no region, create one using the pencil tool and expand it to cover all automation) and go OPTIONS menu -> TRACK AUTOMATION -> "Move current track data to region data." Now everything should play back as expected. If you want to edit the data, simply select "move current region data to track data" and edit away.
For some reason, Logic 7 will sometimes stop reading track automation data, but I have yet to have it stop reading region automation. This is a bug, and according to other users, has been fixed in Logic 8. Hope this helps until we eventually upgrade

Generate automation from Environment ?

Is it possible to generation automation from within the Environment ?
I've set up a rather extensive Environment for mapping MIDI footswitch commands into Logic, using cable switchers, transformers, and faders to bypass, mute, control faders, etc. This is for live use, so I need everything to happen in real-time.
It's all working great, but I'd like to control a few things in plug-ins that aren't accessible via MIDI--in particular, the stomp box bypasses in Amplitube2.
I could use controller assignments to perform these actions, but it wouldn't work well with the rest of my Environment, since I use cable switchers to route MIDI to different places--a controller assignment would intercept ALL messages from that controller, so I couldn't use the controller for other functions.
The controls I need are easily accessible via automation--is there any way to use the Environment to generate automation data ? Maybe with SysEx or Meta events ? What I'd like to do is create a transformer that turns a controller message into an automation event that I can route into a particular object (Amplitube on an insert).
Possible ?
Thanks for any help!
James
[email protected]

The other thing you could try is to record your
MIDI-based "automation" and then use the Options >
Automation function to convert region automation to
track automation. See how that works.
Cool! This worked. When I moved the controls in the plug-in, I didn't get any output from the fader, so I assumed there was no MIDI-like info related.
But... as you suggested... I created track automation, converted to region automation, copied the data from the Event Editor, and pasted into an Environment fader as SysEx... bingo! Works great!
That is, as long as I've got the Environment...
Thanks, again, iS!
James
[email protected]

Is there any way to COMPLETELY disable snapping automation?

I'm trying to create automation lines, specifically region automation using the pop up window below the piano roll in the single screen format. (so when I open up the piano roll and then click the icon in the lower left corner, and then select "Expression" from the pop up menu in the upper left corner of that panel)
It constantly wants to snap to some kind of grid when I first select a node to move. If I move it around a bit I can then position it exactly where I want to, but it won't just move to the exact position that it needs to be when I first start to grab the node. It's REALLY annoying!!!! I'm trying to create natural sounding expression, but this is making it unnecessarily difficult!
I've tried making sure "snap automation" is not checked, and that my snapping is set to ticks. But still it wants to snap when I first start to move the node. Bad Logic, no!
Hope you can help.
Keith

Yeah, that's even more restrictive - it only moves it up or down at a time. Not that it's not useful.
But what I really want to do is just precisely move my automation without a lot of fuss! Any ideas?

How to copy volume automation to expression in hyper draw?

I want to copy the volume automation I've drawn into a track and place it as expression data in hyper draw. Another way to accomplish this would be to create expression (controller 11) as another parameter in the automation parameter view then I could just copy the volume automation to expression automation. I'm missing a piece to the puzzle here somehow, I bet this can be done but haven't been able to find the way. Help for a neophyte if you please!

First go into Track>automation>convert track automation to region automation.
Then open the Hyper editor.
If your volume lane isn't there go into the Hyper menu and choose "create hyper set for current events" - or use the inspector.
Click the lane header, so the volume lane is selected, and in the same menu and choose "convert event definition" - change it to 11 in the right hand box that appears.

Automation lane freezing

On the song I have been working on lately, it freezing often whenever I click on an automation lane. Sometimes the track itself, sometimes when I click on a node, and sometimes when I click the automation button. I tried all of the usual steps, clearing cache, preferences, etc, but I have never seen this before, so it may be specific to this song (possible song file corruption?).
Has anyone had this problem before, or know how to fix it? Thanks in advance.
Dale

Is this an L7 song that you opened in L8?
One thing you could try in the meantime to try and clear out the (what seems like) corruption is to create a blank region that runs the length of your song for each audio track, audio instrument, and MIDI instrument in your arrangement. You don't need to create more than one region per instance. Then, use the "move all track automation to region" command for each track (you might be able to do this in one shot by selecting all of those regions and then invoking the command). At that point you will have essentially erased your automation tracks but retained of the data in MIDI form in those (formerly) blank regions.
But to be sure those automation tracks are cleaned out for sure, invoke the "delete all automation from all tracks" as well.
Save this song under a new name. Once saved, do the reverse --- select all of those "automation regions" and invoke the opposite procedure, "move region automation to track automation".
From there, try to do your automation editing. If your track still freezes up upon doing so, at least you'll have a version of the song where you have your automation in MIDI form, where it can still be edited.
(BTW, I'm doing this from memory, so the names of the automation/region moving procedures might not be exactly named as I described them).
I'll be curious to know how you make out with this.
Cheers!

Logic Pro X v10.0.7 is out

http://support.apple.com/kb/TS4498
this is a looooong list

...and the full list of changes and fixes .......
Logic Pro X 10.0.7 update
New Features and Enhancements
It is now possible to insert the current values of volume, pan, and all active sends of selected tracks as automation points at the playhead position. The new functions are accessible as a menu option or key command.
It is now possible to paste track automation data at the Playhead or Marquee selection location.
A new MIDI Project Setting allows MIDI CC 7 (volume) and MIDI CC 10 (pan) messages to control the instrument plug-in instead of the channel strip.
The output of Auxiliary channel strips assigned to Tracks will now generate audio files when using any of the following Export menu options: "Region as Audio File," "Track as Audio File," or "All Tracks as Audio Files."
Logic now supports up to 24 processing threads on computers with 12 cores.
All menu items related to Snap, Alignment Guides, and "Snap to Grid" settings have been consolidated into the Snap menu in the Main window.
It is now possible to activate/deactivate multiple plug-ins on a channel strip by vertically click-dragging the mouse over their power buttons.
An auto-saved version of a project now contains the Undo History of the project from which it was derived.
It is now possible to install the Logic content to an alternate system drive even if the Logic application is not installed there.
Activating Auto Punch with a key command or Marquee selection now automatically adds the Autopunch button to the Control Bar.
It is now possible to use modifiers with the Velocity Slider in the Piano Roll and Score Inspectors to change its behavior in the same way as the Velocity tool. Holding Option allows velocities for notes to continue to be changed even when other notes have reached there minimum or maximum MIDI velocity value. Option-Shift sets all notes to the same velocity value.
The Scissors tool now works on arrangement markers.
It is now possible to drag a Summing Stack into a Folder Stack.
It is now possible to use the Beat Map feature with a track that has Flex enabled.
Flex Transient Analysis can now be aborted by pressing Command-period.
When a Transient Marker is inserted near the position of a previously deleted transient in the Audio File window, the marker will now only snap to the position of the deleted marker if the Option key is pressed while inserting it.
It is now possible to create more than 32 Folder Track Stacks in a project.
It is now possible to adjust sliders in the Mixer when controlling Logic via screen sharing, Apple Remote Desktop, or other VNC clients.
It is now possible to access the Recent Projects menu while the Open Project dialog is active.
It is now possible to remove the Master Output track from the Tracks area.
The master track of a Track Stack can now be designated as Groove Master.
Audio waveforms are now visible under automation on the master track of a Track Stack.
The Track Import window now shows plug-in preset names.
When Logic imports Final Cut Pro X XML, it now organizes audio tracks according to their assigned roles in Final Cut Pro.
Audio is now exported as 24-bit in projects exported to Final Cut Pro X XML.
When importing XML files that contain multiple projects from Final Cut Pro X 10.1 or later, Logic Pro X now offers a dialog to pick a specific project to import.
The 1/2 Note head symbol is now available in the the Score Part Box.
The Catch Playhead button is now available in the Score when the Advanced Tools preference is disabled.
It is now possible to load ".caf" format files into Space Designer with the Load IR file selector.
There is now a new key command to trim the start of a region to the end of the previous region in the track.
There is now a dedicated Piano Roll section in the Key Commands window. This includes commands for "View Mode: One Track," "View Mode: Selected Regions," and Toggle View Mode.
There is now a key command for “Detect Tempo of Selected Region.”
There is now a key command for “Adjust Tempo using Beat Mapping Track.”
The timeline in Logic Remote now changes color to indicate Logic is in Sync mode.
It is now possible to use the Option key to insert a mono plug-in between two existing plug-ins on a stereo channel strip or vice-versa.
The Velocity Processor MIDI plug-in now displays note-on as orange dots and note-off events as blue dots in the compression curve window.
Command-click on a vector point can now be used to modify the times of all subsequent points in the ES2 Vector Envelope.
The Distortion II plug-in now offers a Distortion Output Level and Mix control.
Stability
Logic no longer sometimes quits unexpectedly when:
Using the Option key to toggle all the disclosure triangles in the Project Audio window.
Dragging audio from the Project Audio window to the Tracks area.
Defining custom bank messages for a Multi Instrument in the Environment.
You insert a blank recordable DVD while Logic is running.
Changing the audio buffer size while the Audio Editor is open in Flex Pitch mode.
Selecting a font in the Number & Names panel of the Score preferences.
Deleting a group in the Project Audio window.
Undoing a flex edit.
Using the Glue tool on flex pitched notes after having switched from the Audio File Editor to the Audio Track Editor.
Performing undo and then redo in quick succession on an EQ in the Smart Controls.
Performing Undo after deleting a comp or take.
Closing a song while importing a MIDI file.
Enabling phase-locked editing on a group.
Using the Pencil tool in the Audio File editor.
Importing a long MP4 (AAC) file.
Changing a channel strip input from stereo to mono.
Disabling Core Audio.
Playing a Drummer track while downloading and installing new content.
Performing undo after certain operations.
Pasting channel strip settings in the Mixer.
Dragging a MIDI region over the Score editor.
Hot-plugging an Apogee Duet to a computer running OS X Mavericks.
Importing a patch that includes a Track Stack.
Adding AAC files containing Audio Transport Stream Data (file type “.adts”).
Performance
The Channel EQ no longer causes unexpected CPU spikes in live track mode on MacBook Pro with Retina Display.
Logic no longer becomes less responsive after making several adjustments to the size and/or position of a floating Transport window.
There is no longer a delay opening the list when clicking in a Send or Output slot on a channel strip.
Logic no longer becomes less responsive when working for long periods with Flex Pitch.
The Drummer track now reliably maintains proper timing if it is selected with Low Latency mode enabled.
Control points in the Transposition track now move more fluidly when edited.
Scrolling a channel strip fader in the Inspector with a mouse wheel now adjusts its value at the correct resolution.
Comping takes is now more responsive when Flex Time is enabled.
Playing a Touch Instrument in Logic Remote no longer sometimes leads to hung notes in Logic Pro X.
Improves responsiveness when dragging tempo events in the Global tempo track.
Songs with a very large number of regions now play back as expected.
Logic’s performance has improved when previewing notes in the Score, Piano Roll, and Event List for regions on a track other than the one selected.
Multi output Software Instruments with complex routings no longer sometimes cause Logic to become briefly unresponsive when starting playback.
Logic now reliably creates thumbnails to the end of the video track with long movie files.
Selecting Channel Strips in very large projects is now faster.
Improves compatibility with ProRes movie files on OS X Mountain Lion v10.8.5.
When scrolling over an open Take folder at high zoom levels on OS X Mountain Lion v10.8.5, there are no longer unexpected spikes in CPU usage.
Automation
Clicking on an event in the Score no longer sometimes selects the wrong events.
It is now possible to paste automation at the playhead or marquee selection area rather than only at its original position.
All MIDI Draw data created by moving track based automation to a Region now appears on the Region and in Piano Roll as expected.
Volume automation moved from a track to a region is now displayed in the Tracks area MIDI Draw view as expected.
It is now possible to use MIDI Draw for an event type that does not yet exist in the region.
When track based automation is moved to a region, the region now immediately switches on MIDI Draw to show the automation in the Track area.
When region automation is moved to a track, the automation now starts at the beginning of the track.
MIDI Draw now reliably creates Surround Diversity and Surround Angle fader events in regions.
It is now possible to make a Marquee selection over region loops when automation is visible.
MIDI Draw data is no longer shown on additional automation lanes when the main automation lane is set to “Off.”
MIDI Draw no longer incorrectly displays a ramp between isolated Pitch Bend events.
When switching between MIDI takes, the MIDI Draw area now properly updates to show the currently selected take.
Option-clicking a MIDI Draw point again selects all following MIDI Draw points for the region.
MIDI Draw points inserted with the Pencil are now reliably placed at the clicked position.
Audio no longer glitches when editing automation while playing back.
Score
It is now possible to deselect a voice in the Staff Style window by Command-clicking it.
The floating Part Box window in the Score no longer shows overlapping elements when first opened.
Clefs in the Staff Style window now scale properly when viewed on a Retina display.
Rests in Mapped Drum styles are now correctly positioned with their associated drum groups on the staff.
When printing a score part with Advanced Tools disabled, Logic no longer prints the track name twice.
Changing the split point of one voice in a multi-stave Staff Style now properly affects the other voices assigned to the same channel.
Page view of scores in songs created in Logic 9 now retain their proper paper size when opened in Logic Pro X.
Scores printed as PDF files now render properly when viewed in Adobe Reader.
The cursor now reliably shows the correct tools when editing the score in linear display mode.
It is no longer possible to give a new Score Part Box a name that is already in use by another Part Box.
The font names for Jazz Cord and Swing Cord fonts now display correctly in the Root Font and Chord Extension Font display in the Chords & Grids panel of the Score settings.
The staff display in the Staff Style editor now shows the proper key signature for transposed styles.
It is now possible to change settings for multiple selected staves in the Staff Style edit window at the same time.
Pasting a compound time signature in the Signature track no longer corrupts the time signature display in the Score.
Filter buttons on floating part boxes in the Score now remain visible when the part box is resized.
Tap to click on a trackpad now works with the Pencil tool in the Score.
It is again possible to insert a bar line at the end of a region in the Score.
The pencil tool again works in the Score when assigned to the right mouse button.
In the Score, selected notes in loops now show the selection color.
The Part box is no longer empty when first opened in a stand-alone Score window after recording.
The print border no longer sometimes changes unexpectedly when printing to PDF from the Score.
When Select All is used within a Score Set, the selection is now properly limited to regions within the Score Set.
Tooltips no longer sometimes obscure the guidelines when inserting elements into the Score.
The bar positions of SMPTE locked notes now update properly in the Score after the tempo is changed.
Pressing the Control key now allows for finer granularity when editing Duration Bars in the Score.
Undo now works after pasting Staff Styles.
Undo now works after changing the Low or High note value in a Staff Style.
In page view, the Score now correctly updates to reflect a different paper size selected in the Page Setup window.
Track names are now reliably shown in Page View when the track contains overlapping regions.
Drag handles now remain visible at all zoom settings when dragging parts into the Score in linear view mode.
Adding special bar lines next to added clef or signature changes in linear view mode no longer causes the bar lines and clef or signatures to overlap.
The mouse cursor now reliably shows the currently active tool in the Score.
The Score now displays as expected after scrolling vertically at high zoom settings.
Copy/paste of notes across multiple staves in the Score now works properly.
Custom colors defined in the Score Layout window are now recalled properly when Logic is relaunched.
The text cursor is now easier to see in various fields in the Score window.
The Display Level button in the Score now follows the entire Score hierarchy when an Instrument Set is in use.
The cursor now displays the Length Change tool when held over the end of a Duration Bar in the Score.
It is again possible to assign no clef or a drum clef to non-mapped score styles.
Plug-Ins
Importing plug-ins to a track no longer unexpectedly changes the input source on the track.
The pitch of notes held when using Sculpture or ES2 are no longer sometimes shifted when using non-Equal Tempered tunings.
Moving the Delay slider in the Note Repeater MIDI plug-in while notes are repeating no longer results in hung notes.
The cycle length in the Arpeggiator plug-in now reliably updates when set to Grid mode.
Recall Default now works with the Delay Designer plug-in.
Recall Default now works properly with Audio Unit plug-ins.
It is now possible to activate bypass on plug-ins that are not currently available.
When the I/O configuration of a plug-in is changed, its editor no longer opens.
The timing of multi-output software instruments is now maintained when latency inducing plug-ins like the Ad-Limiter are used on the main output.
Audio files created by the "Export All Tracks as Audio Files" command now maintain proper sync in projects where high latency plug-ins are used in Summing Stacks.
The Expander plug-in no longer sometimes introduces audio crackles with certain source signals.
With Beat Sync disabled, the Course Rate control in the Auto Filter plug-in again behaves as expected.
Audio now plays reliably from tracks in which there are two Tube Burner pedals inserted in the Pedalboard plug-in.
VoiceOver now works reliably to activate Smart Controls for the Vintage Clav and Vintage B3 Organ plug-ins.
Improves the behavior of Smart Controls when used with Voiceover.
The stand-alone Smart Controls window now properly remembers its last state when reopened.
When editing vector points in ES2 in loop mode, all envelope values are now properly shown as percentages when the envelope is time-synced.
Shift-clicking can again be used to insert a vector point in the ES2 Vector Envelope.
In the ES2 Vector Envelope, the Delete Selected Point contextual menu item again works as expected.
EXS instruments created in EXS24 MK I no longer exhibit unexpected random velocities when played.
Logic no longer changes a user-assigned track color when swapping Software Instruments.
Space Designer’s Filter and Density controls now remain active when the plug-in window is opened more than one time in a session.
Projects with multiple Ultrabeat instances now play back with reliable timing when the Process Buffer Range is set to Small in the Audio > Devices preferences.
A plug-in inserted on the 16th slot of an audio channel strip or the 15th slot of a Software Instrument channel strip now remains visible.
The percussion controls in the Vintage B3 now respond as expected to knob movements from the Native Instruments B4d remote control.
The mapping of value to position for the Organ sliders in the Smart Controls window is now consistent with the sliders in the Vintage B3 Organ.
In the Mixer, it is now possible to drag a plug-in from one channel strip to another when there is an External MIDI channel strip between the source and target.
One shot samples triggered in EXS24 no longer play back with clicks when Rewire Live Mode for Rewire is disabled.
All plug-in windows now reliably open after changing the order of plug-ins in a channel strip.
The Scripter plug-in now reliably triggers notes when playing back outside of an active cycle zone.
The meters in stereo instances of the Adaptive Limiter plug-in now show independent levels for the left and right channels.
Tuned taps in the Delay Designer plug-in now reliably play in sync.
Flex
Flexed regions no longer sometimes show waveforms in the wrong positions.
Flex Markers no longer unexpectedly change positions when moving them in songs that contain tempo curves.
Logic no longer sometimes incorrectly shows that an audio region is flexed in songs that contain tempo changes.
If Flex is enabled, Logic now properly includes manually added transients when an audio region is converted to a sampler track.
Flex Pitch controls are now available in the Tracks area and Audio Editor immediately after Flex Pitch is enabled for a track and analysis is complete.
Setting a Flex Mode now applies to all selected tracks.
It is again possible to cancel flex analysis before it completes.
The Transposition Track now works with flex-pitched regions.
Flex mode now gets enabled for all tracks in a group even if Group Clutch enabled.
The Audio Track editor now reliably shows all notes when scrolling with Flex Pitch enabled.
Logic no longer sometimes hangs when adjusting notes in Flex Pitch.
The Flex Pitch grid is now displayed for all takes in the Track Editor even when a Software Instrument track is directly above the selected Audio track.
Logic now offers the option “Do not show again” in the alert dialog that reads "This region contains inactive flex markers, which will be deleted if you perform the edit."
If a Flex mode has already been set, clicking the Flex drop-down menu will correctly highlight the currently selected Flex mode.
When dragging a region from one track to another, the region "Flex and Follow Tempo & Pitch" checkbox settings are now maintained as expected.
Transient detection is improved with quieter source material.
When Flex is bypassed on a Take folder, the Follow Tempo checkbox is also now disabled.
General
Resolves several issues with Snap introduced in Logic Pro X v10.0.6.
"Snap to Relative Value" now reliably works at all zoom levels with Smart Snap enabled.
Adjustments to the left border of a region now use relative snap when that option is enabled.
When Alignment guides is enabled, Snap to Absolute value now works with Cycle.
Alignment Guides now work as expected when Snap is set to Off.
The track icon picker now activates with the first right-click or Control-click.
Toggling the Tracks Inspector no longer sometimes activates Alignment Guides.
Logic no longer incorrectly shows an alert that the content must be installed the first time it is launched on computers purchased with Logic pre-installed.
The Capture as Recording key command no longer creates odd length regions when used in songs with time signatures other than 4/4.
The Hide Step Input Keyboard key command again works as expected.
The Nudge Region to Nearest Beat option in the Adjust Tempo using Beat Detection dialog now works as expected.
The Snip at Playhead Position key command no longer sometimes causes notes in the new righthand region to shift to the beginning of the region.
Logic Pro X no longer displays the error “Could not open source file” when opening certain MP3 files.
Logic now properly includes time signature, key signature, and tempo events when moving Arrangement markers.
Undoing the repositioning of an Arrangement Marker now correctly moves affected automation back to its original position.
Command-dragging one arrangement marker over another now replaces the previous marker as expected.
Colors assigned to arrangement markers now take effect as soon as the color is clicked in the Color Box.
It is now possible to use the Marquee stripe to delete a section within the area encompassed by an Arrangement Marker.
Using the "Split at Playhead" command on the last arrangement Marker in a song now properly sizes the arrangement marker to the right of the Playhead.
When an arrangement marker is split, the new marker to the right now maintains the same color and name as the original.
Arrangement markers can no longer be inadvertently moved by mouse clicks in an empty area of the Arrangement track.
Copying Arrangement markers no longer creates extra tempo events.
The Beat Mapping track now continues to display properly when it is resized after other Global tracks have been resized.
The Beat Mapping Track no longer disappears if Global Tracks are shown while it is already visible.
Deleting a connection in the Beat Mapping track now correctly also deletes its associated tempo event.
Tempo events created in the Global Tempo track now reliably display in the Tempo list.
Setting one track of a phase-locked edit group as Groove Master or Groove Follower now reliably shows all members of the group as being enabled.
Time signature changes are now reliably displayed in the timeline.
Logic no longer re-downloads basic content that has already been downloaded by MainStage.
Arrange Folders now reliably display as expected in the Mixer.
Double-clicking on the icon for a folder channel strip in the Mixer now opens the folder.
Commas may now be used as decimal separators when typing values into controls on the Mixer.
It is now possible to drag regions vertically without an unexpected horizontal shift when "Snap to Grid" is enabled in the Tracks area.
Recording a new take over multiple existing regions again works as expected.
It is now possible to create an empty MIDI region on a track hosting an Auxiliary channel strip.
Shift-click to delete a take selection again works reliably.
Region Gain now works as expected when applied to comp segments in a Take folder.
When a take selection is disabled and then re-enabled, the change is now properly reflected in all tracks that are part of the same group.
Logic no longer unexpectedly re-extends a shortened Take folder when the folder is dragged vertically to a different track.
When recording in Cycle mode, Logic no longer creates an automatic comp when a take encompasses only part of the Cycle range.
When regions are packed into a Take folder, regions from the same track are now placed on the same sub-track in the Take folder.
Fixes an issue in which it was sometimes no longer possible to change the length of a Take folder after performing several other Take folder length edits.
Take regions no longer unexpectedly shift horizontally when dragged vertically from one sub-track to another when the "Limit Dragging to One Direction In: Tracks" preference is enabled.
Copied Take folders are no longer missing their contents in certain rare situations.
Regions on audio tracks inside a folder now are reliably placed on their proper tracks when the folder is unpacked.
The key command “Select Previous Section for Realtime Comping” now works correctly when used while recording multiple takes in Cycle mode.
When Bounce-in Place is used with a channel strip that contains a plug-in that performs a mono to stereo conversion, Logic now creates a mono file if the option to bypass plug-ins is selected.
Regions created with "Bounce in Place" are no longer sometimes given random names.
Addresses and rare issue that could cause some MIDI notes to play back at the wrong pitch.
In Link mode, the Piano Roll now reliably shows the contents of the selected region.
The Event Float window no longer loses focus after a selected note has been edited in the Piano Roll.
The "Split Events by Playhead" command now works reliably with multiple notes in the Piano Roll.
Editing notes in the Piano Roll with multiple regions selected no longer sometimes results in notes being inadvertently moved from one region to another.
Closing the local inspector in the Piano Roll editor no longer leaves a blank area on the right side of the editor.
Opening MIDI Draw in the Piano Roll no longer offsets the keyboard into the editing area.
When adding notes in the Piano Roll with the Pencil, newly created notes again have the same Velocity as the last edited note.
It is now possible to lasso notes in the Piano Roll editor using a Wacom tablet when Logic’s Right Mouse Button

On Logic Pro

Remplacement de la batterie ne fonctionne pas du tout c'est une honte !!!!!!!!!!!!!!Beat replacment, doesn't work it's a shame .
I'm a professional user
The same thing exist on Pro tools since 6 years ago

Lef Mak wrote:
... When I press LATCH to record live ...
Are you referring to the Automation Mode "Latch"? This is different from standard recording mode.
Record Mode
In standard recording mode, you record the MIDI signal from your external MIDI controller as MIDI Events to a MIDI Region on your Track and also controls the MIDI components on your Instrument Plugin of your Channel Strip. The incoming MIDI signal is played/recorded on all Record-enabled Tracks.
Automation Mode
In Automation Mode, the signal from your external MIDI controller can be used to record Automation Data (which are Fader Events, visualized as Automation Control Points) to control virtually any onscreen controls in Logic. These Events can be recorded as Track Automation or as Region Automation. The important part is the setup. You use either Automation Quick Access (one Automation Parameter at a time), or use the Controller Assignments Window to configure a more elaborate scenario.
Hope that helps
Edgar Rothermich
http://DingDingMusic.com/Manuals/
'I may receive some form of compensation, financial or otherwise, from my recommendation or link.'

ValuePattern.SetValue Throws ElementNotAvailableException (Inner Exception of InvalidOperationException)

I have a Wpf FrameworkElement derived control that offers a custom AutomationPeer:
using System;
using System.Collections.Generic;
using System.Text;
using System.Windows;
using System.Windows.Automation.Peers;
using System.Windows.Automation.Provider;
namespace TSystem.Content
internal class MarkTopicElementAutomationPeer : FrameworkElementAutomationPeer, IValueProvider
private static readonly Dictionary<string, TcsMarkStates> StringToStateMap = new Dictionary
<string, TcsMarkStates>
{"Positive", TcsMarkStates.Positive},
{"Negative", TcsMarkStates.Negative},
{"Neutral", TcsMarkStates.Neutral}
#region Constructors
public MarkTopicElementAutomationPeer(FrameworkElement owner) : base(owner)
if (!(owner is MarkTopicElement))
throw new ArgumentException("Owner must derive from MarkTopicElement");
#endregion
#region Automation Peer Overrides
protected override string GetNameCore()
StringBuilder name = new StringBuilder();
name.AppendFormat("MarkTopicElement:{0}:{1}", OwnerAsElement.Caption, OwnerAsElement.ElementID);
Topic parentTopic = OwnerAsElement.FindLogicalAncestorByType<Topic>();
if (null != parentTopic)
name.AppendFormat(":ParentTopic:{0}:{1}", parentTopic.GetType(), parentTopic.Instance);
return name.ToString();
public override object GetPattern(PatternInterface patternInterface)
return patternInterface == PatternInterface.Value ? this : base.GetPattern(patternInterface);
protected override AutomationControlType GetAutomationControlTypeCore()
return AutomationControlType.ComboBox;
protected override bool IsContentElementCore()
return true;
protected override bool IsControlElementCore()
return true;
#endregion
#region IValueProvider Implementation
public bool IsReadOnly
get { return OwnerAsElement.ReadOnly; }
public void SetValue(string value)
OwnerAsElement.ChangeMarkState(StateFromString(value));
public string Value
get { return OwnerAsElement.MarkState.ToString(); }
#endregion
#region Helper methods
private MarkTopicElement OwnerAsElement
get { return (MarkTopicElement) Owner; }
private static TcsMarkStates StateFromString(string value)
TcsMarkStates state;
return (StringToStateMap.TryGetValue(value, out state) ? state : TcsMarkStates.Neutral);
#endregion
However, when I try to access its implementation the ValuePattern:
WpfComboBox mark = HistoryPage.UIEVSite234Window.UIHostedPageWindow.UIItemCustom.UIItemCustom11.StartedTopic.StartedJustPTA;
var markElement = (AutomationElement) mark.NativeElement;
ValuePattern pattern = (ValuePattern) markElement.GetCurrentPattern(ValuePattern.Pattern);
pattern.SetValue("Positive");
It throws this exception:
Result Message:
Test method EVTCSTest.HistoryStartedTest.SetStartedToPositive threw exception:
System.Windows.Automation.ElementNotAvailableException: Element not available ---> System.InvalidOperationException: Operation is not valid due to the current state of the object.
Result StackTrace:
at UIAutomationClient.IUIAutomationValuePattern.SetValue(String val)
   at System.Windows.Automation.ValuePattern.SetValue(String value)
--- End of inner exception stack trace ---
    at System.Windows.Automation.ValuePattern.SetValue(String value)
   at EVTCSTest.HistoryStartedTest.SetStartedToPositive() in c:\Development\zTest\EVTCSTest\EVTCSTest\HistoryStartedTest.cs:line 46
Any ideas why this may be? I know that the element is enabled and is not read only.
One final update...I have confirmed that it is getting to my implementation of the read-only Value property of my automation peer. However it doesn't seem to even be reaching my implementation of SetValue.
Thanks,
Kelly Hilliard

Hi,
Based on your description, I don’t think that the issue is really related to Coded UI test itself. Your issue is mainly on setting a value using ValuePattern.SetValue. I think it is more related to accessibility and automation. I noticed that you post a
new thread on Windows Desktop Development for Accessibility and automation forum:
http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/8c8f4566-22df-4944-ba57-13898dcec6be/valuepatternsetvalue-throws-elementnotavailableexception-inner-exception-of?forum=windowsaccessibilityandautomation#8c8f4566-22df-4944-ba57-13898dcec6be
I am not an expert on accessibility and automation, I am sorry for that I can’t provide you something useful about ValuePattern.SetValue method’s usage. I think that community members on Windows Desktop Development for Accessibility and Automation forum
will help you resolve this issue better.
Thank you for your understanding and support.
Best regards,
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey.

Logic Crashes When I make a global Cut??

Anyone had this happen?
LOgic Crashes when i try and make a glbal arrange cut.

Logic crashes when I open a particular file...
As the old joke goes...
"Well, don't open it then..."
The first things to do is make some backups of what you have, just in case. Then try booting Logic without the audio drivers (or turn them off) and see if you can load the song.
Also, try deactivating your third-party plugs (a snap with AUManager, or move them temporarily out of your components folder), and seeing whether it will load then.
I would guess that the song is corrupted, so once you can get it to load, I would suggest you start copying all the necessary stuff (regions, automation, channel settings etc etc) into a new, uncorrupted song.
Also, you can try and go back through your auto-numbered backup files, assuming you have the function turned on - you might be able to open a version of the song before the corruption. And if you didn't have that autobackup feature turned on - well, I suggest you do from now on!
If you get no joy doing all that, post back and we'll go from there.

Logic crashes when I open a particular file

Hi, Logic just started crashing on me and usually I could reopen the file, undo a few levels and carry on...However I seem to have saved something just before a crash which actually caused the crash, so that now when I open that file Logic crashes immediately, leaving me no time to get in and undo. Until today it's been running nicely. The file has a 90-minute mpeg4 movie and some AU tracks running. I've already trashed the preferences file, and removed the video file to thre trash so it wouldn't be accessible, but still no go. Any suggestions? Thanks.
imac 4.1 Mac OS X (10.4.7) Logic Pro 7.2.1 / 1.5 GB of ram

Logic crashes when I open a particular file...
As the old joke goes...
"Well, don't open it then..."
The first things to do is make some backups of what you have, just in case. Then try booting Logic without the audio drivers (or turn them off) and see if you can load the song.
Also, try deactivating your third-party plugs (a snap with AUManager, or move them temporarily out of your components folder), and seeing whether it will load then.
I would guess that the song is corrupted, so once you can get it to load, I would suggest you start copying all the necessary stuff (regions, automation, channel settings etc etc) into a new, uncorrupted song.
Also, you can try and go back through your auto-numbered backup files, assuming you have the function turned on - you might be able to open a version of the song before the corruption. And if you didn't have that autobackup feature turned on - well, I suggest you do from now on!
If you get no joy doing all that, post back and we'll go from there.

Region automation Q

Similar Messages

Maybe you are looking for