Logic's Linear Phase EQ vs. Waves Renaissance EQ

Hi all, I was wondering what your opinions were in regard to these two EQ's. Which one seems to be the way to go, and what are the differences between the two?
Are there some things that one would be god for over another, or is one just flat out better than the other for all things?

I have never used renaissance so im not sure about the two, but in theory any linear phase eq is better than one that is not due to the mathematical algorithms that it use to process the audio.
The way it works is that most eq's are made to be processor friendly so they have a few downfalls which is a slight phase distortion , this can be heard most when moving a peak notch along the spectrum. Most of the time this won't really be noticed but linear phase eq's resolve this problem but will consume alot more CPU, as the maths is considerably larger.
My recommendations though are to use 2 eq's which i love by PSP. NEON (linear phase) NITRO (normal), plus another great plug is Vintage Warmer2. As me my friends say: if it moves Vintage warmer. Well there u are, a short answer to ur question.LOL Thanks Stu.

Similar Messages

  • Linear Phase EQ and Latency?

    So after reading up on all the positive tidbits of the Linear Phase EQ vs. the good old fashioned Channel EQ, I decided to start giving it a shot. I like the subtle nuances LPEQ has over CEQ and have been enjoying it.
    Tonight, however, I ran into a major issue. Every instance of the LPEQ introduced some nasty latency onto the track it was put into. I tried to EQ a kick drum and the thing became so far off that I couldn't believe it. Bypassing the plug immediately sent everything back to normal.
    Why does the LPEQ introduce so much latency when used? Is there any sort of workaround to lessen the effect? I bumped my buffer settings up to 512 and there wasn't a bit of difference. What's going on in the LPEQ that would make that drastic of a change? Am I missing something?

    Thanks for the input, noeq.
    You're weclome Brent
    For the record, the latency issue started before
    changing any settings. There's also no recorded
    audio in the session file, all of it is soft-synths
    and samplers.
    I am devising a test for the synths only...without any audio in the session.I'll keep you posted on what I find.
    Are you suggesting that PDC should be off to avoid
    the latency issue?
    At this point I am not suggesting ANYTHING.so please don't change your setup until you can find out exactly why the latency happens.By Sunday I'll have results of my tests for you to look at.
    I don't think it's just my issue or a myth,
    especially since tbird, iS and X all posted as having
    the exact same issue with the LPEQ.
    I'll be looking into this.So far with my only test,to determine default latency of Logic Plugins only,I have found it to be the case that the GuitarAmp Pro and the Space designer reverb DO have different latencies,after all other latencies have been accounted for.The Linear Phase EQ in this particular test,came out to have no latency.
    Perhaps it will be a different result when I do the synth-only test.
    But until I do the test,I cannot know.
    Here is one of my favorite quotes,from aristotle:
    "We suppose ourselves to possess unqualified scientific knowledge of a thing, as opposed to knowing it in the accidental way in which the sophist knows, when we think that we know the cause on which the fact depends, as the cause of that fact and of no other, and, further, that the fact could not be other than it is. Now that scientific knowing is something of this sort is evident-witness both those who falsely claim it and those who actually possess it, since the former merely imagine themselves to be, while the latter are also actually, in the condition described. Consequently the proper object of unqualified scientific knowledge is something which cannot be other than it is.”
    — Aristotle, Posterior Analytics (Book 1 Part 2)
    Cheers

  • Least square linear-phase FIR filter

    I need to geta second order derivative of an array based on 2 stage filtering with a least square linear phase FIR "differentiator " filter. Previously this was done using the matlab routine firls using the "differentiator" tag. Any ideas how this can be done in LabView?
    Thanks in advance.

    I don't believe that LabVIEW has any differentiation functions that use this algorithm. The only derivative function is located in the analyze, signal processing, time domain. You would probably have to build your own.

  • Linear Phase EQ

    Not hearing the difference at all to be honest.. ::: What is the use of this in Lemans terms?

    You'll hear, and notice the difference immediately if you are trying to EQ a stereo recorded sound, say, like a stereo mic's acoustic guitar.
    If one side of the stereo signal needs EQ's, such as if the two mics weren't the same make and model, and you try and add channel EQ to that track, the signal will become heavily out of phase. You'll hear the image shift drastically, and the timing will be off as well.
    The Linear Phase EQ will keep the signal in phase, using this example.

  • Logic Won't Let Me 'Drop' .Wav Files Into A Session??

    Hi all,
    Trying to simply drag and drop .wav files from a folder on an external hard drive into an empty Logic Pro 9 session.  The audio tracks are stereo (have also tried mono) and the input/outputs seem to be fine.  The session is also saved to the external.  I am not using an external audio interface.
    I have also tried importing using the 'File-->import' commands and this allows me to import one file at a time, but not in bulk.  This seems odd as I could've sworn I didn't have this problem in past attempts.
    Let me know your thoughts please!
    Ps. Logic rules, but I'm very tempted to get acquainted with Pro Tools!

    GTBannah wrote:
    Are you sure they are audio tracks, and not MIDI or Instrument tracks?
    Ha ha... Yes I am sure.  A good thought, though I did double checked this before posting the problem.
    Could it be something to do with the sample rate?  Ie. the audio files were recorded at a certain sample rate and now I need to make it match with the sample rate in Logic?

  • Logic Time Compression/Expansion vs. WAVES SoundShifter

    I'm considering upgrading my WAVES Platinum to the Diamond, largely because of the SoundShifter plug-in. Does anybody have any experience with the WAVES SoundShifter plug-in? Is it significantly better than what is already included in Logic 8?
    Thanks!
    M

    I used to be hard core Logic only, and then I noticed something (this may seem off topic but I'm getting around to the point). For the first time, probably about 2 or 3 years ago, Digidesign got off their laurels and realized that other software platforms were taking legitimate shots at their "industry standard."
    That's when you saw instrument tracks implemented - that's when you saw better (but still far from the quality of Logic) MIDI implementation. . . that's when the Digidesign AIR group was created. . . that's when Digi added the dynamic transport, flexible track resizing, screen sets, included software instruments.
    As a whole, Pro Tools still does not give you the abilities out of the box that Logic does. However, whatever gap Logic 8 closed between itself and Pro Tools with audio editing, Digi widened even further than before with the introduction of elastic time. That's when I finally realized that Pro Tools, a great editor, tracking, and mixing machine, finally realized that its throne was threatened and went to defend it. My work used to primarily take place in Logic, however, that has switched. I probably do 60-80% of my work now in PT and still use Logic for mixing and such. For whatever reason I just like it better. . . I"m sure that will change over too. All pro tools has to do is implement a Logic-esque MIDI editor and I'm not sure I'd have any reason to stay with Logic. Digi has really stepped up to the plate in a time where it has looked like Logic has stepped up, and then done nothing to stay up.
    All that to say if you want good timestretching, right now PT is just about the only way to go.

  • Logic 7.2 , UAD 1 and waves

    Does anyone know if waves plugins do work w/ Logic 7.2? I have an mac pro 3ghz 4 gigs of ram. I am using waves 5.2 for w/intel support. Cubase SX3, Spark XL and Logic LE see the waves and load correctly. Logic 7.2 does not see the waves folder at all niether does waveburner. But logic does see the uad 1 but Cubase and Logic LE cannot connect to the UAD 1 hardware. Any one else having this problem?
    G4 dual 867, G5 2.0 dual, imac G4 1.33, Mac Pro 3GHz   Mac OS X (10.4.8)  

    If LE sees the Waves plugs, but LP doesn't, then then only difference is probably the AU Manager. Start that (Logic -> Preferences -> Start AU Manager), and make sure that the Waves stuff is enabled and passes validation.
    As for the UAD, run the UAD meter application. Does that correctly report the UAD-1 card is running and working correctly?

  • Delay with Linear Phase EQ

    Hi!
    I woukd like to know .
    Why i have delay when i use LPEQ?
    There is no delay with other Logic's plugins .
    Thanks!

    It's required for the nature of the algorithm. You can use PlugIn Delay Compensation. Also, ChannelEQ's settings are interchangeable with LPEQ's - use Channel while tracking if you must.
    J

  • How do I get Logic to stop looking for a specific .wav file?

    I recently imported a project I started in GarageBand into Logic Pro.  Once in Logic, I edited and added to the project then saved it as a Logic project file.  I deleted the original project from GarageBand.  Now, when I open the Logic file, Logic is still looking for .wav files that were used in the original GarageBand file.  None of these files are actually needed in my project.  Is there a way that I can get Logic to stop looking for these .wav files?
    Thanks for any help!

    Do a cleanup.
    http://documentation.apple.com/en/logicpro/usermanual/index.html#chapter=7%26sec tion=9%26tasks=true

  • Difference betwwen phase linear eq and chan eq

    they look excatly the same. do they behave differently?
    thanks

    I don't really have much technical knowledge.. have just picked up stuff along the way.
    AFAIK:
    when it comes to mastering, any kind of linear phase EQ is by far the choice most engineers would go for... this is because a mixed track is a very complex beast, with a lot of very precisely sculpted and placed elements within it.. well, in theory at least..
    so, using an EQ that messes with phase risks to cause all sorts of unwanted shifting and artefacts all throughout the mix when all you are trying to do is EQ it. this manifests as blurring of stereo placement, and even things like transients and punch being affected badly. so linear phase is by far the choice for mastering cos it does not do this at all.
    when it comes to EQing individual sounds.. really, it's anyone's call. you should learn the sound of your EQs by imprinting their signature in your brain. treat yourself like an impulse response analyser, and learn the character of every EQ you have.
    sometimes, I even go for the fat EQ because I am looking for its particular kind of notchiness on a certain sound. other times, I'll go for a UAD cambridge because I like the way it helps reveal grain and harmonics without being brittle. also, right now I'm really liking the URS EQs.
    linear phase or otherwise, when you are equalising individual sounds in your mix, it's really about finding the frequency scuplting tool(s) that give the nuances you are after. if a certain EQ does it with a touch of pleasant personality that works, then great. if it unfocuses and disturbs your sound in unwanted ways, try something else.
    generally speaking though, linear phase EQs are a cleaner sounding EQ, which is useful when that is what you are after.

  • Logic 10.0.5 is out! Three new drummers, LOADS of fixes.

    I have not yet finished reading the release notes, it is almost 5,000 words...
    http://support.apple.com/kb/TS4498
    Logic Pro X 10.0.5: Release notes
    Symptoms
    Logic Pro X 10.0.5 is an update to Logic Pro X. Logic Pro X is a new paid version of Logic Pro.
    Resolution
    Logic Pro X 10.0.5 update
    New features and enhancements
    Includes 3 new Drummers and 11 new Drum Kit Designer patches.
    Significant enhancements to Channel EQ and Linear Phase EQ plug-ins, including:
    Redesigned, easier-to-use interface that's also accessible within the Smart Controls area
    Double Precision processing provides more accurate filtering, especially for low frequencies
    Oversampling option improves high-frequency clarity
    Option to apply EQ only to stereo left, right, middle, or side signals
    There is now an option to set the Piano Roll to a light background color.
    Selected notes in the Piano Roll are now highlighted by a selection frame.
    When Logic is stopped or in Play mode, the glyph on the Metronome button in the control bar now illuminates to indicate that “Click while recording” is enabled.
    The Shuffle commands are improved (see Logic Pro X Help for details).
    User interface
    There is now a command to assign region names to track names.
    The waveform size in an audio region now adapts to the value of the region gain parameter.
    Loops that belong to the same family can now be selected and changed using a new control in the region header.
    Logic Pro X now assigns region and Mixer channel colors that are closer to the original colors when opening a project created in an earlier version of Logic.
    Option-clicking a disclosure triangle in the Project Audio window now toggles all disclosure triangles in the window.
    The Windows menu again lists all currently open windows.
    The Mixer can now be reliably resized when in All mode.
    Renaming multiple selected Mixer channels now reliably renames all channel strips in the selection.
    When creating a duplicate track, the correct track icon and color are now assigned to the duplicate.
    The song title is now automatically populated in the Share to iTunes dialog when sharing a song created in Logic 9 or GarageBand for iOS.
    It's once again possible to browse or load patches onto the Output channel strip via the Library.
    The View menu items One Track and Selected Regions in the Piano Roll are now disabled when Link mode is disabled.
    Performance
    Improves processor balancing for multi-output software instrument configurations.
    Improves handling of multiple displays on OS X Mavericks v10.9.
    Resolves an issue that in some cases might cause audio clicks and pops when scrolling.
    Moving an automation line while playing no longer spikes in CPU usages, or clicks and pops in the audio output.
    Resolves an issue that could cause clicks and pops in the audio output when adjusting the gain or output level settings during playback in the various plug-ins.
    Logic's interface no longer freezes when using the Native Instruments Maschine controller to adjust two macro controls simultaneously.
    Fixes an issue in which a warning about not enough memory might be displayed when performing Undo after editing a protected track.
    Adjusting the frequency controls while playing audio through the Stereo Spread plug-in no longer causes audible zipper noise.
    Improves the performance of scrolling when dragging regions in the Tracks area beyond the currently visible section.
    Playing notes live into the Arpeggiator plug-in no longer sometimes leads to spikes in CPU usage.
    Fixes an issue that could cause a spike in CPU usage when recording near the end of a project.
    Logic 9 projects that contain a macro object in the Environment now behave more reliably when opened into Logic Pro X.
    Multiple instances of the Scripter plug-in no longer have the potential to cause stuck notes.
    The Scripter plug-in is no longer prone to causing stuck notes when using the Delay Note Until Next Beat preset.
    Switching between presets in the Space Designer plug-in no longer sometimes results in noise.
    General
    Regions copied from a Track Stack can now be muted as expected even when they are within a Track Stack that is muted.
    Deleting an audio Track Stack while it was soloed no longer leaves all the remaining tracks muted.
    Entering a new crossfade value in the Region inspector for multiple selected regions now works as expected.
    Region-based automation data beyond the end of a region is now chased properly even when playback is started after the last automation node within the bounds of the region.
    Logic now maintains the correct relative levels when automation on multiple tracks belonging to the same Group are copied by dragging.
    Resolves an issue in which track automation might be deleted when switching patches.
    The default display setting when showing automation on Track Stacks is now Volume, instead of Display Off.
    A track is now created as expected when using a control surface to set the automation mode of a channel strip not previously assigned to a track.
    Moving a SMPTE locked region can no longer  cause the automation on the track to  move.
    The position of the automation line no longer jumps unexpectedly when it is selected after creating 4 automation points with a Marquee selection.
    Adjacent automation points of the same value are no longer sometimes inadvertently deleted when moving automation points on a grouped track.
    The Repeat Section Between Locators command now includes automation on tracks that contain no regions in the repeated section.
    When using Touch mode, Logic no longer writes unneeded automation points at the held value when holding a fader at the same position where there is an existing automation ramp.
    Writing automation to an Aux not assigned to a track can no longer potentially cause tracks in a Track Stack to be rerouted to that Aux.
    Copying multiple regions where only some affected tracks contain automation no longer activates Automation Read mode on the channel strips that have no automation.
    Chase now works as expected for MIDI controllers on channels other than channel 1.
    Takes are now shortened as expected when the take folder containing them is shortened by an edit operation and No Overlap mode is enabled.
    Fixes an issue in which the visible area might jump unexpectedly when comping in a take folder that was not on the selected track.
    Fixes an issue that caused some audio regions to be immovable when duplicate regions are packed into a take folder.
    Packing regions with names containing non-ASCII characters into a take folder no longer creates garbled take names.
    Numbers assigned to MIDI takes now increment reliably.
    Expanding a take folder no longer potentially causes the playhead to fall out of sync with the audio output.
    When using OS X v10.9, the playhead in the Audio Editor now consistently maintains the correct position when switching from Flex Time to Flex Pitch mode.
    It's now possible to set a loop to a length of less than 1/16 note.
    The position of beat markers in the Global Beat Mapping track are now updated appropriately when using the various Cut/Insert Time commands.
    Inserting a beat marker in the Beat Mapping track no longer creates unexpected tempo events in some circumstances.
    Expanding a take folder no longer potentially causes the playhead to fall out of sync with the audio output.
    Resolves an issue in which some MIDI notes might unexpectedly change position when Beat Mapping.
    Adding a Beat Mapping marker no longer intermittently removes existing tempo events.
    Inserting a fade-in using Shift-Control and the Pointer tool now works consistently.
    Using the Fade tool to set fade-ins on multiple regions in a set of grouped tracks now works reliably.
    Dragging regions on multiple grouped tracks with the Drag Mode set to X-Fade  no longer potentially results in crossfades of varying lengths.
    The Delete command now works as expected on selected regions that are inside a collapsed Group in the Project Audio window.
    It's now possible to add a green Apple MIDI loop to the Tracks area as an audio loop by dragging it from the Loops browser while pressing the Option key.
    Logic Pro X no longer creates separate tracks for non-overlapping regions when unpacking folders in projects created by earlier versions of Logic.
    Using the  menu that appears when pressing the Metronome button in the Control Bar, it's now possible to set the metronome to sound only during count-in.
    Improves the reliability of Undo in several areas.
    The Mixer window  no longer intermittently moves when scrolling past the minimum or maximum value of the fader using a scroll wheel or gesture.
    It's now possible to select or open folder tracks in the Mixer.
    Right-clicking  an Aux or Output channel strip in the Mixer and selecting Create Track now behaves as expected even if the channel strip is not initially selected.
    Command-click again works reliably to  deselect a Mixer channel within a selected group of channels.
    The display of audio waveforms of regions in a track  no longer change unexpectedly when enabling or disabling the Groove status on a track.
    Looped regions inside a folder now update the point they are supposed to stop playing after extending the length of the folder.
    Overwriting an existing project  no longer potentially leaves assets from the original project in place.
    When creating a new project from a Logic 9 template, the default save path is no longer the location of the template.
    Improves the mapping of Smart Controls to channel strip settings created in Logic 9.
    The Follow Tempo parameter in the Region inspector is no longer incorrectly disabled for Apple Loops in songs last saved in GarageBand 6 or earlier.
    Clicking and holding down on the upper-right corner of a region no longer unexpectedly enables looping in the Region inspector, with a loop length of zero.
    The Region Inspector no longer displays a Loop checkbox for selected Track Stack folder regions.
    It's once again possible to disable Quantize in the Region Inspector for a region on a track slaved to a Groove Master track.
    Saving a song created from a template  no longer resets the tempo to 120 BPM.
    Text for alert messages now always displays correctly on control surfaces.
    Changing Region inspector parameters for MIDI regions on the main track of a Track Stack now behaves as expected.
    It's again possible to change the Transpose value in the Region Inspector using the + and - keys.
    Logic now consistently responds to Play or Stop key commands when a floating Region inspector window is open.
    It's no longer possible to give the same name to more than one project alternative.
    MIDI played from the Musical Typing Keyboard and Logic Remote is now routed through the Physical Input object in the Environment, which allows  Environment processing of MIDI as it is being played into Logic from these sources.
    Logic no longer adds 2 extra frames to the value when entering a SMPTE position in a project set to a non-drop frame rate.
    Regions copied by option-dragging in projects with a start position earlier than bar 1 now end  at the desired position.
    Moving the first arrangement marker in a project  no longer inadvertently moves other arrangement markers.
    Resolves a rare issue that could cause the timing of a track in a project with many tempo changes to be altered after turning Flex on and then off.
    Logic now asks the user to save the project when closing a project immediately after entering text into the Project Notes area.
    It's now possible to consistently add, remove, or edit plug-ins on tracks that were frozen in Source Only mode.
    Pressing the Control key while dragging a region with the Snap Mode set to Bar now moves the region by beats instead of ticks, as expected.
    Editing the left border of an audio region now behaves as expected when the Snap setting is set to “Snap Regions to Relative Value”.
    Resizing a region with the Snap setting set to “Snap Regions to Absolute Value” now behaves as expected.
    Resolves an issue that caused an event in the Event List to move later than expected when editing its position.
    The “Capture as Recording” command now works as expected when multiple MIDI tracks are record-enabled.
    It's now possible to preview sections of an audio file outside the current region borders by clicking the area in the Project Audio window.
    The tap-to-click option for trackpads now works reliably with all drop down menus.
    The “Discard Recording and Return to Last Play Position” key command now reliably discards the recording.
    It's again possible to use the Tab key to navigate to the next control while working with plug-ins in Controls view.
    The MIDI Activity display now shows chords as they are played when using Musical Typing.
    All currently found audio files are now reliably saved with a project when using Save As or Save a Copy As with a project in which one or more audio files are missing.
    The name of a project is now correctly updated after saving a  project created from a template.
    Fixes an issue in which clicking on the level LED in the track header did not select the track.
    Resolves an issue in which changes made to the setup for Mackie Control and other MCU-compatible control surfaces were not saved by Logic Pro X.
    Setting the Display Time preference to “SMPTE/EBU with Subframes”, “SMPTE/EBU without Subframes,” or “SMPTE/EBU with Quarter frames” can no longer  cause the time display to jump unexpectedly.
    Saving a project for the first time no longer resets the record path when it was previously set to an external path.
    Performing undo in the Piano Roll or after deleting a flex marker no longer has the potential to unfreeze currently frozen tracks in the project.
    Sample rate, tempo, and key information is now reliably stored within template files.
    Fixes an issue in which the Repeat Regions dialog did not have key focus when opened, making it necessary to click it with the mouse before pressing Return to confirm the operation.
    Individual MIDI Draw points in the Piano Roll are now  easier to grab.
    Deleting a track no longer has the potential to inadvertently delete regions on other tracks.
    Cut/Insert Time edits no longer add unexpected tempo changes.
    Scrubbing the SMPTE display in the LCD no longer moves the playhead to the wrong position.
    Copying an arrangement marker to a position between two other arrangement markers  now moves the end-of-song marker to accommodate the new section, as expected.
    Audio
    Audio regions now appear as expected in the Audio Editor, even when cycle is enabled and there are no audio regions within the cycle area.
    Flex Pitch now correctly detects notes for take regions that have manually inserted flex markers.
    The timing of notes played during the count-in on EXS24 or Drummer tracks is now more reliable.
    Pasting an audio region into a take folder now correctly places the region on the selected take lane.
    When saving an EXS instrument, the default save location is now ~/Music/Audio Music Apps/Sampler Instruments.
    Editing the start point and anchor in the EXS audio editor now consistently alters playback as expected.
    Logic no longer overwrites an existing audio file of the same name when performing a bounce with the option to create a split stereo file enabled.
    Audio tracks assigned to output to a bus now consistently maintain that assignment when imported into a different song.
    User-defined controller assignments now work as expected to control MIDI plug-in parameters.
    The Record Repeat command now deletes the previous recording when used after recording in Cycle mode.
    Quantize now operates reliably on takes that are displayed in the Audio Editor.
    The Tuner window is no longer affected by the Content Link setting of other plug-in windows.
    Audio now plays for multiple cycle iterations when using marquee selection to define the cycle area.
    When the Edit command “Analyze Audio for Flex Editing” is used, Logic now properly resets any existing pitch edits on the selected audio files.
    Command-clicking a selected note in Flex Pitch mode in the Audio Editor now deselects the note, as expected.
    Setting a track to Flex Edit mode with the Slicing algorithm no longer processes the track with Flex if no edits have been applied.
    It's again possible to set Software Instruments to mono.
    Logic no longer creates an extra audio file when merging or format-converting audio files.
    Resolves an issue in which the Mixer did not show the 8th bus send on a channel strip.
    Changing the input format of a stereo output channel strip to mono now creates a second mono output channel strip on the Mixer for the other channel in the stereo pair.
    Setting an external recording path now reliably resets the Audio Assets setting. Conversely, enabling the Audio Assets setting now disables an externally set recording path.
    The compressor meter in the channel strip is now in sync with the meter in the plug-in window.
    Drummer
    Improves the translation of articulations when an Ultrabeat-based patch is assigned to a Drummer track.
    When a project starts on an upbeat, a Drummer region at the project start now automatically creates a fill at the beginning.
    Changes to Drummer regions are now reliably applied when the regions are set to follow a flexed audio track.
    MIDI editors
    The Link mode button is now available for the Piano Roll editor.
    The “Limit Dragging to One Direction” setting now works  as expected in the Piano Roll.
    It's now possible to grab notes shorter than 15 ticks for editing in the Piano Roll.
    Double-clicking a region with MIDI Draw enabled now consistently opens or closes a MIDI editor.
    Resolves an issue in which recently recorded MIDI notes might disappear from view in the Piano Roll when recording with cycle engaged.
    It's again possible to alter the pitch of notes in the Piano Roll via MIDI input.
    Using  Option-Shift  to edit the end points of multiple selected notes to the same position in the Piano Roll Editor now works as expected.
    In the Piano Roll, it's again possible to use Option-Shift in conjunction with the Velocity tool to set all selected notes to the same velocity.
    An Event Float window that is linked no longer switches unexpectedly to the Region level when using arrow keys to move from note to note in the Piano Roll.
    Pasting events in the Piano Roll when the playhead is to the right of the region border will not trigger the error “Illegal Region number”.
    It's now possible to copy a note in the Piano Roll to a different pitch at the same position when the note starts before the left edge of the region.
    It’s now possible to move notes in the Piano Roll by increments smaller than 13 ticks when the “Limit Dragging to One Direction” setting is enabled.
    User-inserted rests no longer incorrectly appear as notes in the Piano Roll.
    Copying a muted note in the Piano Roll now creates a muted copy of the note, as expected.
    Fixes an issue in which some note events might not be selectable in the Step Editor.
    The contents of the Event List are now updated properly when deselecting a region from a multiple selection while Content Link mode is enabled.
    The Event List now displays the correct LSB values for 14-bit pitch bend events.
    Editing Release Velocity values in the Event List now behaves as expected.
    The “Copy selected events” option in the MIDI Transform window now behaves as expected.
    Score Editor
    Fixes an issue that could cause the menu option for switching between Parts and Score view in the Score Sets window to disappear.
    Double-clicking  a region with the All Instruments filter setting active now reliably reveals all regions on that track, rather than just the single region.
    The contents of the Event List editor are more consistently updated when changing the region selection from the Score window.
    Newly inserted key signatures no longer display “xx Major” in some circumstances.
    The Chord Grid Editor now correctly names Add 9 chords.
    The clef menu no longer disappears for a Mapped Instrument staff style set to “No Clef”.
    It's again possible to create a new Chord Grid library that uses an alternate tuning.
    It's  now possible to adjust the Velocity setting in the MIDI Meanings settings window by scrubbing the value with the mouse.
    The length adjustment in the MIDI Meanings settings window can now be adjusted via a pop-up menu.
    In the Staff Style window, the check marks indicating that a style is used in the current song now reliably update to reflect changes when Content Link mode is off.
    Grace notes now scale properly when the scale setting of a Score Set is  less than 100.
    Resolves an issue that prevented reassigning instruments assigned to a Score Set after performing certain other edits.
    Fixes an issue that prevented naming a floating score Part box set.
    Plug-ins
    Solo now works as expected on channel strips using an external I/O plug-in
    Ultrabeat can now find samples that have been relocated from the default install location.
    Ultrabeat now correctly applies the Fine Pitch adjustment to all triggered samples when trigger mode is set to Multi.
    It's now  possible to halve/double the current rate of the Arpeggiator plug-in by clicking the Slow/Fast buttons.
    The ES1 synth plug-in  can now be set to offer 32 and 64 voices per instance.
    The Scripter plug-in now allows System Realtime MIDI events to pass through.
    The Scripter plug-in now offers an option to keep current control values when recompiling a script, rather than resetting all values back to their defaults.
    The Scripter MIDI plug-in now includes a Set Parameter function.
    Switching between Vintage Electric Piano patches while holding notes no longer potentially results in momentary jumps in level.
    The Vintage Electric Piano no longer potentially creates audible pops when switching patches when the Drive is enabled and set to Type II.
    It's now possible to continue working with the Scripter editor window when Logic Pro X is not in focus.
    The Surround Compressor plug-in now properly shows all the new circuit types available in Logic Pro X.
    It's again possible to copy or paste settings in the Space Designer plug-in window.
    The order of controls in the Retrosynth Filter Envelope and Amp Envelope sections has been reorganized to improve usability.
    The plug-in window no longer appears empty for Waves plug-ins opened in projects created in Logic 9.
    Fixes an issue in which inserting a plug-in on multiple stereo Software Instrument channel strips would insert mono versions of the plug-in on some channel strips.
    EXS24 or Kontakt settings are no longer  removed from a song if the Audio Device buffer size is changed before saving the song.
    Resolves an issue in which adjusting parameters on the Channel EQ while playing back might cause minor clicks and pops in the audio signal.
    Moving an Amp Designer instance to a different plug-in slot no longer sometimes changes its sound.
    “Save as Default” for Audio Unit presets again works as expected.
    Video
    It's now possible to exchange movie files in a project by dragging a new movie file into the Movie window or the Movie inspector.
    Logic Pro X can now work with the following professional video codecs, if OS X Mavericks v10.9 and the codecs are installed: Apple Intermediate Codec, Apple ProRes, AVC-Intra, DVCPRO HD, HDV, XDCAM HD / EX / HD422, MPEG IMX, Uncompressed 4:2:2, XAVC.
    There is now a Show/Hide Movie Window command in the View menu when the current project contains a movie.
    Resolves an issue in which some movies that were compatible with QuickTime X did not play in Logic Pro X.
    Exporting audio to a movie with a portrait orientation no longer causes the movie to rotate 90 degrees.
    Logic is now  able to export surround AAC audio to a movie even if the original audio in the movie was originally kept.
    The visible frame of a movie now updates as note lengths in the Piano Roll are changed.
    Import/export fixes and improvements
    XML projects imported from Final Cut Pro X now contain volume and pan automation when opened in Logic Pro X.
    Exporting a project as an Final Cut Pro/XML file with the “Export as Final Cut Compound Clip” option enabled now behaves as expected.
    Includes several improvements to the way Logic handles audio sample-rate conversion when importing Final Cut Pro XML.
    Logic now shows a progress bar when importing large Final Cut Pro XML projects.
    32-bit float audio files in Final Cut Pro XML projects are now converted to 24-bit files during import so they play properly when imported into Logic.
    The start time of imported Final Cut Pro XML projects is now consistently correct.
    It's now possible to export Music XML when the Score window is in linear view mode.
    Logic no longer shows multiple alerts when importing a Final Cut Pro XML project containing videos in a format not supported by Logic.
    Songs created in GarageBand 6 no longer load in Logic Pro X with an extra channel in the Mixer.
    Fixes an issue in which audio in a song imported from GarageBand 6 might play back too fast in Logic Pro X.
    Logic now offers to include embedded tempo and marker information when using Track Import to bring an audio file into a project that contains no other audio regions.
    Simultaneously dragging multiple MIDI files into the Tracks area now behaves as expected when using No Overlap mode.
    The default destination path for exported MIDI files is now the project folder instead of ~/Music/Logic.
    When importing projects, there is now an Add All button in the Aux import dialog.
    The user settings in the Bounce window are now retained after sharing to iTunes.
    Split stereo SD2 files no longer incorrectly import as AIFF files when the WAV file option is enabled.
    The “Share Song to iTunes” command now creates a playlist with the name entered if there is not already an iTunes playlist with that name.
    MIDI events that precede the start point of a region are no longer included when the region is exported as a MIDI file.
    Stability and reliability
    Includes several fixes related to stability and reliability, including to resolve issues that could cause Logic to quit unexpectedly in these circumstances:
    When changing the length of a time-stretched region
    When importing tracks from another project
    When recording with the color palette open
    When bypassing an instance of the Maschine plug-in
    When exporting Music XML after applying Enharmonic Shift to some notes
    When changing the range on an Environment fader whose style was set to Text
    When quitting a project that has a Surround Compressor inserted on a channel strip
    When removing a control surface from the Control Surface setup window when the Logic Remote is also present
    When changing the range value of a Smart Control during playback.
    When reapplying a Time and Pitch operation after undoing a previous one
    When dragging an audio region from a take folder to a new song

    Thanks Erik,
    If nothing else, this huge list of updates and fixes, shows clearly that the Logic Dev team is working hard on fixing and improving LPX to a major degree.... and from the list of fixes done.. show they do read the bug reports submitted!
    As an aside....
    I recall how all the 'naysayers' prior to LPX (and in some cases, since...)  were proclaiming how Logic was dead, the team was being disbanded, we won't see any further development, the Dev team doesn't listen or care... and so on....... I wonder where those people are now?

  • Looking for a third party go to EQ plug to work with Logic.

    Hey folks, here's the deal: I'm looking for a great sounding, versatile, linear phase EQ. This will be used on a track by track basis, so low CPU overhead would be a plus, but I am running this on a dual 2.8 GHz eight core Mac Pro with currently 6 GB's of RAM, later to be expanded, so sound quality is more important to me than anything else. Cheaper, of course, is better, but I don't really want to miss out on quality to save a buck either. I already own two UAD-1 cards, and bought the Precision EQ, and while I like it, it's really mainly for mastering and not for finely tuned mixing work. I also own the DDMF EQ's, and enjoy them. I also own T-Racks 3, and use the linear phase EQ's with that, still, I am looking for something else for some reason. I am mainly using Logic Pro 8, and the linear phase EQ with it as my go-to channel EQ at the moment, but I also own Ableton Live 5, Digital Performer 5.13, and Pro Tools M-Powered 8, so I have access to the EQ's in those. But Pro Tools is only just for getting projects and audio out of Pro Tools, I can't use it well with the rest of my system, so that's that. Ableton is great, but not really what I use anymore, although I wish I had more time to get down with it.
    Anyway, here is what I'm mainly considering, although I could go with any other idea at this point, so please make any suggestion you feel fit.
    1) Ozone 4. (http://www.izotope.com/products/audio/ozone/)
    I like the company a lot, and it's going to be inexpensive for me due to a student discount. I probably will buy it sooner or later, my thoughts are though that it largely duplicates what I already have with T-Racks 3, and I can't see using it necessarily as a channel EQ for some reason, although I probably could. I don't know how it sounds really either, I imagine pretty good, though.
    2) Nugen Audio SEQ 2 Master Edition (http://www.nugenaudio.com/seq2.php)
    Again, not expensive. I do really like the 10 Hz-30kHz possibilites with this guy. I own their Visualizer and other plug ins and enjoy them. I've downloaded the demo and liked that too, but you can't really measure how much you like the sound in a week or whatever. I mainly didn't hear any sound, which is probably good. The interface is less than beautiful, but then again, I'm not buying art here.
    3) RNDigital Unique-lizer. (http://www.rndigitallabs.com/Plug-ins/U ... lizer.html)
    I have their D4 compressor and absolutely love it. I have demoed their Inspector XL and loved that. I think they've got some killer plug ins going, and again, will probably get this sooner or later, likely as part of a package with the Inspector XL and the other EQ (the FirEQ), and a limiter or something. I really like the visual aspect of this plug, it would probably be helpful in isolating a troubling frequency in a snare hit, say.
    4) The UAD Cambridge EQ. (http://www.uaudio.com/products/software ... index.html)
    By now you are noticing that I want a more graphically styled modern EQ, and not a vintage emulating plug in. I intend to add some of those at some point (I guess I have some already with T-Racks and whatnot) but for now I want a super clean and versatile modern plug in style EQ that I would feel comfortable using on every track for it's uncolored sound. This is probably my least consideration, I think I would get much more processing power out of my native processing rather than my two UAD-1 cards, frankly, especially if Snow Leopard performs as promised. I am thinking the UAD-1 cards will turn out to be more of a processing liability more than anything else, I'm new to them though, but that's what it's looking like to me. I am unlikely to want to go to UAD-2 at the moment either, and am suspicious of the limitations of it's processing power vs. native as well. And this seems like an older offering of UAD's, and seems to want to be a "classic" console style EQ as well as the more neutral style version I am looking for... but then again, I don't know much about it compared to most.
    That's the big ones- I have looked into URS, which seems like more vintage emulating stuff to me, as well as Sonalksis, which seems good. Waves is always there. TC Powercore and the Liquid Mix are possible (well TC Powercore unlikely, that's big time money) but I am sort of unwilling to add another Firewire bus PCIe card and am using a Firewire interface.
    If anyone is still awake after this, I'd love to hear your thoughts! I'll be posting this on a few forums so let me know what you think please, thanks, L

    For what it is worth, I am a fan of NuGen, I have both SEQ 1 and 2 and two stereo enhancing tools (stereoizer and stereoplacer I think they're called). Since I have the SEQ 1 it replaces all Channel EQ's. And the stereotools sound great and very lush, in stead of the more usual cheezy combfilterthingies that pass for stereo enhancing tools.
    And I actually like the interfaces. Simple, but stylish, functional and ergonomic (in this case meaning you can see all parameters in a quick glance, no guessing at settings).

  • Why Is There An Offset in Logic When Bouncing?

    I often send a stereo bounce of a file to a singer. I bounce from bar one, and include a click in the bounce.
    When he or she gets the bounce, they record (usually in PT or Cubase) their vocals, and send the vocal track back to me, WITH the click count off so I can make sure we are in sync.
    When I line their vocal up to BAR one in my file...which is where I bounced the ref track from....their click does not line up with mine. See the screenshot below and you'll see what should be a click on BAR ONE BEAT ONE is actually off. Any ideas on what could be causing this? Could it be frame rate differences?
    http://i271.photobucket.com/albums/jj143/oceantracks/ClickOffset2.jpg
    Thanks
    Tom

    MP3 compression issues aside, it needs to be noted Logic still adds an offset to WAV bounces as well. As far as I can tell, it's the length of the latency of the plugin chain in the session. Of course, the way plugin latency compensation works is by delaying everything, so apparently the delay is just still present in the bounce.
    This is very important to remember in case you're bouncing tracks for mixing elsewhere. If you're e.g. making synths for a track with live instruments and bouncing the synths down for importing into Pro Tools, it will be out of sync with the live tracks in Pro Tools unless you exported those other tracks through the same session as well.
    Interestingly, this drifting also happens with automation. You can test this by making a track with audio but no plugins and making an audible volume peak right on the beat. Then add a lot of latency-heavy plugins to the inserts (linear phase EQ etc.) and notice how the automation doesn't hit the beat exactly anymore.
    EDIT: Just to clarify, the automation drifts only in the audio side. Visually it still looks like it's in sync. It's just the playback doesn't match the visuals anymore.

  • Difference between Logic Express and Pro? ro

    Is the actual logic part the exact same? Is it that with the Pro you get all the extras? (soundtrack pro, qmaster, logic node, compressor, main stage, wave burner, jam packs). Is that what makes it the "pro" version? Or does the actual Logic app offer more abilities? If so, I can't seem to see much a difference. thanks

    The app itself is indeed the same, but the included content and plug-ins are different.
    This Apple support document details all the differences:
    http://support.apple.com/kb/HT4229
    * Effect plug-ins found only in Logic Studio
    Space Designer (convolution reverb)
    Delay Designer
    Match EQ
    Linear Phase EQ
    Adaptive Limiter
    Multimeter
    Multipressor (Logic Express includes a preset-only version)
    Loopback (Available only within MainStage)
    Binaural Post Processor
    Downmixer
    Multichannel Gain
    Surround Compressor
    ** Instrument plug-ins found only in Logic Studio
    Sculpture Modeling Synthesizer
    EVP88 Vintage Electric Piano
    EVB3 Vintage Tonewheel Organ
    EVD6 Vintage Clav
    Playback (Available only within MainStage)

  • Plugin settings not preserved from MacPro to G5 - Logic Pro

    Hi there,
    I have an annoying problem - I recently recorded some songs on my Macbook Pro using Logic Pro 7.2.3 and the Renaissance compressor and reverb from the Platinum bundle. I found when I transferred the song files back to my G5 that the Waves plugin settings were not preserved and reverted back to the defaults, and I have had to write down the settings for each track and reset them manually.
    I have the Waves 5.9.1 Platinum bundle on the Macbook Pro and the 5.2.1 bundle on the G5 both running OS X 10.4.9.
    Has you seen this problem before?
    Any comments would be most welcome!
    Regards
    Rick

    Hi there,
    I have done some experimentation on the different platforms, but I still have had no success in resolving this, even though I have installed the latest version of the Waves plugins on my PPC Mac. I do have some comments to make from the tests I made to try to track down the problem.
    Saving the settings in Logic as channel strips or using the down arrow on the Logic frame surrounding the plugin, and selecting 'Save As' do not transfer the settings saved on an Intel based mac to a PPC based one (.aupreset files are saved this way).
    What does work is saving the settings from the 'Save' button on the Waves plugin itself and transferring the .xps file from the Intel Mac to the PPC mac and loading the setting from that file.
    The reason for this may be because the Waves format file (.xps - XML format) stores the plugin settings in human-readable form in the file. The Logic format file (.aupreset - also XML) on the other hand saves the plugin settings as a block of mixed text characters representing the settings as binary data.
    Since this is the case, I think that the PPC Waves plugin can handle its own format files 'cos they are in readable text, but when presented with binary data (which presumably has byte swapped data words in it - Intel and PPC chips differ in this respect) it cannot understand what is being presented to it and fails to load the info.
    If that is the case, Waves need to change their plugins on the PPC platform to understand settings delivered in a binary form from Logic - I keep looking at the Waves site periodically to see if they have.
    Cheers
    Rick
      Mac OS X (10.4.10)  

Maybe you are looking for

  • Need the format for input file for standard program

    hi can any one please give me the format in which the file to be uploaded to program RFBIBL00 , must be in for example my excel file to be uploaded has the following columns. company code accounting doc line item fiscal year doc type doc date so is t

  • How to add xml data to an xml scheme

    Hi all, I am having a problem trying to add content to an XML schema file - I have a schema (xsd file) and i want to use it in order to create and validate new/other xml's. The issue is that i want to place some data in the original XML schema file t

  • Bilder von Kamera abrufen

    Hallo Freunde, möchte Fotos von meiner Nikon D40x in Bridge importieren. Nach dem Starten des Befehls "Bilder von Kamera abrufen" erhalte ich stets die Antwort "Das Programm Photo Downloader wurde unerwartet beendet" Kann mir da jemand weiterhelfen

  • Can't choose certificate for computer identification in VPN settings

    When I click on the "Choose" button in the dialog for computer identification in VPN settings, nothing happens. Is there any way to configure the certificate manually on the Terminal until this bug is fixed?

  • Collaborating in IMovie08

    Myself and a buddy are working on a movie project for work. We are trying to figure out the best way to collaborate. I imported all the events to my computer (saved them on an external hard drive). I also saved the project to the external hard drive.