Looking for:
Ableton Live vs Logic Pro: which DAW is best for you? | MusicRadar
There’s more to the new release of Logic Pro When making long recordings into Quick Sampler. When stepping through ChromaVerb presets. Occasionally when setting color display options in the Piano Roll. Logic Pro no longer hangs: When the Paste Multiple command is applied in the Score editor if the clipboard is empty. Resolves an issue where Logic Pro could unexpectedly quit when reversing the direction of a Live Loops cell during playback. Fixes an issue where Logic Pro occasionally quits unexpectedly when moving plug-ins to different positions in the Mixer while using VoiceOver.
Resolves an issue where Logic Pro sometimes quits unexpectedly when clicking in the patch library immediately after saving a project. Resolves an issue where Logic Pro could occasionally quit when selecting the Additive tab in Alchemy after creating a new track from a sample. Resolves an issue were Logic Pro could quit unexpectedly when multiple projects are open.
Logic Pro no longer shows an error when trying to create a Template in certain rare cases. Resolves an issue where Logic Pro could quit unexpectedly when dragging a repeat symbol to the score. Performance Creating a Drum Machine Designer instance from an audio file containing multiple slices is now much faster. UI performance when editing Flex Pitch on long audio files is improved.
Projects named with the file extension in uppercase now open as expected. Opening and closing Logic Pro plug-in windows no longer causes memory usage to increase. Resolves an issue where Logic Pro occasionally hangs when certain video files are open in the project.
Studio Strings now play back smoothly in cycle mode when there are large tempo changes. The Audio Cell Editor is no longer empty after joining two cells containing audio regions. Fixes an issue where audio regions transferred from the Tracks area to cells in the Live Loops grid are occasionally transposed unexpectedly.
Deleting the last Live Loops cell on a track now causes playback to automatically switch to the Tracks area. The Slip and Rotate commands in the Live Loops cell Piano Roll editor now work as expected when the cell is not selected. Dragging a Marquee selection from a Live Loops cell Audio editor to the Tracks area now correctly sets the editor view to the Audio Track editor.
Stopping recording of a Live Loops cell no longer stops playback of all other cells when the playhead has reached the end of the project timeline. The Repeat Once command now correctly overwrites content in the Live Loops cell to the right of the currently selected cell.
Dragging a scene in the Live Loops grid no longer causes the view to scroll to the bottom. Live Loops cell editors no longer display the Global Tracks area in cases where Global Tracks are not functional. Step Sequencer pattern cells now take on the color of the track. Select by Transient in the Audio Cell Editor now reliably selects all transients in the cell. The Copy to Live Loops command now populates the currently focused, or first following empty scene rather than the first empty scene in the grid.
Live Loops grids now play and respond as expected after saving as part of an untitled project on systems using UAD Apollo interfaces. Copying selected Markers to the Live Loops grid now sets Cell lengths to the distances between Markers in cases where the Marker lengths are 1 clock tick.
A cell moved to a different track and then back while playing no longer speeds up briefly. Pasting a Marquee selection into a Live Loops cell now includes any blank space that is part of the selection. Fixes an issue where copying multiple contiguous regions from the Audio Cell Editor to the Tracks Area sometimes results in unexpected overlaps between regions.
Changing the tempo of a cell now consistently works with audio files that have had the original recording tempo removed. Option-clicking Live Loops cells now toggles their queue status. The Live Loops Cell contextual menu now includes recording settings. It is no longer possible to inadvertently select a cell in the Live Loops grid and a region on the same track in the Tracks area.
Audio files added to the Audio Cell editor are no longer placed one bar to the left of the position clicked with the pencil tool. Cells containing flattened take folders now play back reliably at the correct tempo.
Cutting a portion of the start of Take region in the Audio Cell editor no longer removes the same section from other takes in the Take folder. Fixes an issue where edits applied to individual Takes in the Live Loops Cell editor are occasionally applied to the Take folder. Pattern cells in the Live Loops grid can now be reliably deleted after performing Undo in the Step Editor. Live Loops cell recording behavior is no longer affected by the cell playback mode.
Live Loops cells created by dragging a marquee selection of audio regions to the grid now play back in sync and at the correct tempo. When a flexed cell is copied to an empty track, the track now reliably switches to the flex mode of the copied cell. Cell or scenes in the Live Loops grid can no longer be inadvertently dragged when tools other than the pointer are assigned. Pattern cells in the Live Loops grid now reliably continue to respond to automation after a cycle jump.
When non-crossfaded regions overlap in a Live Loops cell, the first region now stops playing when the second begins. The Live Loops grid now automatically scrolls to show scenes selected using the Previous or Next Scene key commands. Fades on reversed cells are now rendered properly when a Performance recording is created. It is now possible to stop and retrigger an individual cell without stopping playback entirely.
Scrubbing in the Sampler zone editor is now possible when the Loop Range encompasses the entire sample. In Sampler or Quick Sampler a Mod Matrix slot can now be created by right- or Control-clicking a target parameter and choosing a source. Sampler now retains the view of modules configured by the user when re-opening the plug-in window.
An audio file dragged to a Zone in an empty instance of Sampler is now immediately displayed in the Zone editor. Sampler now reliably loads the correct settings for bundled instruments. Performing Undo after inserting a Slice marker in Quick Sampler while zoomed in no longer causes the view to unexpectedly zoom out.
Exchanging a sample in a gain-optimized Zone now optimizes the gain for the newly added sample. The maximum zoom in the Sampler Zone Key editor has been increased. When working in Slice mode in Quick Sampler, the active slice marker is now displayed on top of the sample start marker. Multiple clicks in an empty zone panel in Sampler no longer triggers multiple file load dialogs. There is now a Preview audio button in all modes in the Quick Sampler window. There is now a command in the Sampler Zone edit panel to add a new zone.
Selections made in the Zone list are now maintained when the cursor is moved into the Waveform display area. The waveform in the Sampler Zones panel now updates when switching zones with the keyboard while in Round Robin mode. Dragging a stereo file to the Track Header to create a Quick Sampler instrument no longer creates a mono instance. Automatic pitch detection for Sampler and Quick Sampler now consistently detects the correct pitch.
Sampler now sorts Zones numerically as well as alphabetically. It is now possible to edit the Velocity settings of multiple zones that belong to different groups in Sampler. The Command key can now be used to temporarily override the snap value in the Quick Sampler grid.
File names are now visible in the Sampler Zone Editor. Sampler now retains changes to the Waveform Zoom setting when the plug-in window is closed and then reopened.
Double-clicking a Zone in the mapping area now opens the Zone Panel. Round Robins created from a selection of Groups now play in the same order as the Groups.
Saved patches in Sampler that use the default sine wave now play back correctly when recalled. Performing undo after exchanging a kit piece or loading a patch in Quick Sampler now immediately updates the waveform display. Audio file names can now be edited in Sampler. The accuracy of slice positions in Quick Sampler is improved. Edit Key Labels in Sampler now works as expected.
Resolves an issue in which it was sometimes not possible to drag an audio file to a position between two existing Zones, even if there was room. The Save As command in Sampler no longer overwrites the original instrument preset.
Sampler now plays audio files on which Undo has been performed after editing in the Audio File editor. Sampler now successfully loads EXS instruments with filenames longer than 57 characters. I’ll spare you my current thoughts and feelings about the ‘developers’ working on Logic at Apple Park in Cupertino. I really hope the software I depend on will continue working on Mojave for still many, many years, before I have to switch to the catastrophe that are the later OS releases….
Its part of why I am moving on to Digital Performer. Too many tricky hassles with LogicPro and I don’t want to move to Big Sur or Monterey for at least a couple more years I can only say that in the past there have been some weird problems associated with older versions of LogicPro project files being opened in newer versions of Logic Pro.
But the fact that you said your old projects opened in LogicPro I suspect it has something to do with opening I was rather hoping that Apple would have made AU3 more solid with newer versions of LogicPro on newer versions of MacOS, but from the sounds of it, AU3 has become more buggy, perhaps related to the input port changes they did Anyway, for me this is just one more news story about LogicPro that leads me away to DP or Cubase from here forward.
Originally Posted by: Macker. This sounds just horrible, sorry to hear you are having such trouble.. Can you elaborate a bit what exactly got corrupted in the environment and does not work anymore.
I am using the environment extensively and fortunately did not experience problems in However, I had plenty of similar problems with previous versions of Logic where for years things just would not work anymore after an update. It unfortunately seems the environment is some legacy part of their code that hasn’t really been maintained for far more than a decade and that they just carry around. Yet, every once in a while they break parts of it when they port it to a new framework, since no-one really understands anymore how the code works in detail.
Originally Posted by: Kai. That has been my observation also. Actually I suspect it was done in assembly language or something of this nature. In my mind it’s a miracle that the environment even still works at all.
My experience with AU3 in LogicPro up until This is how multi-timbral scenarios are handled in LogicPro For example if the instrument holding VePro. AU3 is “Inst1”, then each time you add a new track with new channel, an additional channel strip is created in the environment, referring to that Inst1 object. However, you can only create of them. This is true in older versions of LogicPro and perhaps latest version too.
Lots of things in LogicPro are limited to values even though they should not be. For example, in the articulation set editor, if you try to use PitchBend as an output switch.. The AU2 environment macro approach for using VSL with multi-ports has always been running into bugs in LogicPro’s environment and did not work properly ever in the templates that were provided by VSL There are work arounds, but the VSL templates did not have those work arounds and never worked right.
Paolo, previously, for as long as possible I too held onto versions of MacOS and Logic that worked just fine. But more recently I’ve needed to know if the latest Logic and macOS would help, hinder or not affect my Situater subsystem, given that I was getting it close to release. But now I’m thinking it could turn out that I just keep Situater for myself.
In which case I’d lobby the Dorico team to do it for everyone else. I think it was Logic I sent a new bug report about it to Apple for every new release of Logic in which the Transformer was still not fixed.
Meanwhile I’d redesigned the relevant parts of Situater to use the Transformer in its broken state, although this meant Situater could no longer use 53 pitch classes per octave. But lo and behold! Ironically, in Logic I’d say version 9 was the the most recent good Logic. It seems Apple’s constantly replenished army of young noob proggies and coders just can’t help rushing to demonstrate the truth of the “Peter Principle” i.
Also, perhaps Apple management are busy proving the truth of one of the corollaries of C. Northcote Parkinson’s Law, under the chapter “Plans and Plants”, in which Parkinson points out many historical examples of the perfectly purpose-built new building being a portent of the organisation’s terminal decline and ultimate demise! Not knowing anyone working at Apple and not knowing a thing about how Apple employees actually work, these are of course merely the images I conjure to try to make sense of the often baffling outcomes of Logic and MacOS updates, Lol.
Kai, the worst example of corruption I saw in the Environment was a small, simple numerical fader in use as a buffer, originally with one in and one out, changed radically into an absurdly tall thing, almost the height of the screen, and with dozens and dozens of output terminals, several of which had mysterious off-page connections but the context menu didn’t offer the option of selecting the destination object of any selected output cable.
With that kind of horror happening, I dread to think what else might have changed but not be visible. It’s simply not worth the risk of trying to fix it up in a multi-page Environment subsystem as big and complex as my Situater.
Just in case the problem is that my Situater build is now too old – in the sense that it has already been through too many major updates of Logic – I might have to do a total clean rebuild from scratch, to see if that gets treated any better by the latest Logic. Dewdman, that’s an interesting observation with the 8bit limitation.
As you write, underneath the fancy surface everything in Logic is still built on the old environment code even in the most recent version. They try to hide it as much as possible, but they simply need it. I guess this is unfortunately the only reason why the environment and all its nice Midi capabilities still exist. But it is indeed basically a miracle that all this still works to some extent , taking into account what changes the architecture went through since the code was created PPC, Intel, Apple silicon.
OK – I am very grateful for the expertise, knowledge and help which turns up here after a question is posed. Long live the Forum creators, moderators etc! He did not create that Layer he says – it was just there! He says he has a mixer in it which he put together. I have an Environment Layer called “Mixer” which he does not! I did not create my “Mixer” layer either. We both have identical versions of Logic Pro 9.
It is a mystery to me. Anyone care to explain? If so – how will it interact with the original Mixer I just mentioned above? Will it compete, replace or ignore it? Do I need only to have one mixer Layer in the environment? Should I delete the original after I made a new one? Can I make a new on within and existing Logic song? It is impossible as far as I can see.
I always have the pigging input signal and output signal blasting in my ear no matter what I do on the Logic mixer. I even tried switching off the FF TotalMix but it merely remembers the last TotalMix fader settings so is always effectively ‘on’. Its driving me insane. There’s no “Audio” layer that’s part of the environment by default.
If it’s there, someone must have created it. On the other hand, there is a “Mixer” layer for channel strip objects.
That one’s there by default. Yes you can create your own layer and no, it will not interfere with whatever is there already. They’re all layers of the same onion. Mac mini 3. You can post now and register later. If you have an account, sign in now to post with your account.
Paste as plain text instead. Only 75 emoji are allowed. Display as a link instead. Clear editor. Upload or insert images from URL. By sjasz , 30 minutes ago in Logic Pro. By 88keys , 1 hour ago in Logic Pro. By Music Spirit , 1 hour ago in Logic Pro. Need help signing in? Click here! Is the Logic ‘Environment’ actually necessary? Share More sharing options Followers 0. Reply to this topic Start new topic. Recommended Posts. Cobalt19 Posted November 26, Posted November 26, This question will no doubt reveal or confirm my endless stupidity about Logic.
Link to comment Share on other sites More sharing options HTH drb. It is almost like having an Ozzy experience. When I first met you, you didn’t realize I can’t forget you or your surprise You introduced me to my mind And left me wanting, you and your kind My life was empty, forever on a down Until you took me, showed me around My life is free now, my life is clear Come on now, try it out.
Logic Pro X This is going back when Logic was owned by eMagic, by the way. I was using it on the PC side, by the way. Still have the disks and dongle. Since I am now using software instruments that exist all in the computer, I rarely go into the Environment window except to gaze at it for old time’s sake. I am certain that, for many, the Environment still has its uses especially when using MIDI devices outside of their computer.
Logic’s “Environment” is a pretty powerful tool, though, and one that’s worth learning at some point in time.
Final Cut Pro – Technical Specifications – Apple.Logic Pro X review: Pro audio Mac app gets useful new features | Macworld
Cells containing flattened take folders now play back reliably at the correct tempo. Will it compete, replace or ignore it? Pro Tools is a must-have DAW for any composer who plans to work with live audio. The Logic interface now remains fully responsive when track level meters are displayed.