OP
OP
Vik
Vi-k
That doesn't happen here. How do you click the playhead to the beginning?
OP
OP
Vik
Vi-k
Here's some info about the solo function in Logic. Please skip this post if everything works as expected for you.
For some years now, Logic hasn't had dedicated track solo – it has region solo and channel strip solo. This causes some confusion, like eg situations where you solo one track and two tracks are being soloed. The implementation of Solo Lock is also confusing, because there's no dedicated Solo Unlock command.
The Solo button in the Control Bar controls Region Solo, and the same is true for the key command called Solo Mode (⌃S ). "Set Solo Lock Mode" (⌥S) also controls Region Solo. This is the Control Bar, with the solo button currently in Solo Lock mode:
Clear/Recall Solo above the track list controls Channel Strip solo:
The key command "Toggle Track Solo" actually toggles channel strip solo, and must exist only to help users find some kind of track solo function. In other words: "Toggle Channel Strip Solo" (S) and "Toggle Track Solo does the same thing".
Important: If nothing is mentioned about what kind of solo mode a command is about, it's about region solo.
Even more important: if you by mistake enable Solo Lock when a track is selected but no regions are selected, you won't hear anything. Logic has soloed no regions, because none were selected.
So - what's the difference between track and channel strip solo? You'll understand the difference if you create a new track with "New Track with Same Channel Strip/Instrument" (⌃⇧↩ ) – a function that can be very useful. It creates new tracks in a way that's different from when you use 'New Track with Duplicate Settings', because it uses that same channel strip (eg Instrument 3 or Audio 2) on another track. If you use the function, you'll find that using the command controlling track solo actually controls both these tracks, even if only one of them are selected because they use the same channel strip.
You can enable region solo with 'Set Solo Lock Mode', but the same command cannot remove that solo lock again – it is, as its same suggest, not a toggling command. You can also enable solo lock mode (which is about regions) by alt-clicking on the Solo button (in the control bar), but performing the same action again won't unlock it. This is maybe confusing, but there is some logic behind this: you disable solo lock by activating solo again. The problem is only that that's not an intuitive solution.
Also, if you use Solo to unlock the Solo Locked regions, then you also disable solo. That means that if you have selected a number ion regions before you enabled solo lock for them, you may forget which regions that just were soloed. That's where "Reselect Solo-Locked Regions" (⌥⇧S) comes in handy.
IMO there's certainly room for improvement in this area. One function I miss is a key command which simply unlock solo lock but keeps the solo mode, which could be implemented by combining "Solo" (which unlocks currently selected solo locked regions, but also removes solo mode) with "Reselect Solo-Locked Regions".
For some years now, Logic hasn't had dedicated track solo – it has region solo and channel strip solo. This causes some confusion, like eg situations where you solo one track and two tracks are being soloed. The implementation of Solo Lock is also confusing, because there's no dedicated Solo Unlock command.
The Solo button in the Control Bar controls Region Solo, and the same is true for the key command called Solo Mode (⌃S ). "Set Solo Lock Mode" (⌥S) also controls Region Solo. This is the Control Bar, with the solo button currently in Solo Lock mode:
Clear/Recall Solo above the track list controls Channel Strip solo:
The key command "Toggle Track Solo" actually toggles channel strip solo, and must exist only to help users find some kind of track solo function. In other words: "Toggle Channel Strip Solo" (S) and "Toggle Track Solo does the same thing".
Important: If nothing is mentioned about what kind of solo mode a command is about, it's about region solo.
Even more important: if you by mistake enable Solo Lock when a track is selected but no regions are selected, you won't hear anything. Logic has soloed no regions, because none were selected.
So - what's the difference between track and channel strip solo? You'll understand the difference if you create a new track with "New Track with Same Channel Strip/Instrument" (⌃⇧↩ ) – a function that can be very useful. It creates new tracks in a way that's different from when you use 'New Track with Duplicate Settings', because it uses that same channel strip (eg Instrument 3 or Audio 2) on another track. If you use the function, you'll find that using the command controlling track solo actually controls both these tracks, even if only one of them are selected because they use the same channel strip.
You can enable region solo with 'Set Solo Lock Mode', but the same command cannot remove that solo lock again – it is, as its same suggest, not a toggling command. You can also enable solo lock mode (which is about regions) by alt-clicking on the Solo button (in the control bar), but performing the same action again won't unlock it. This is maybe confusing, but there is some logic behind this: you disable solo lock by activating solo again. The problem is only that that's not an intuitive solution.
Also, if you use Solo to unlock the Solo Locked regions, then you also disable solo. That means that if you have selected a number ion regions before you enabled solo lock for them, you may forget which regions that just were soloed. That's where "Reselect Solo-Locked Regions" (⌥⇧S) comes in handy.
IMO there's certainly room for improvement in this area. One function I miss is a key command which simply unlock solo lock but keeps the solo mode, which could be implemented by combining "Solo" (which unlocks currently selected solo locked regions, but also removes solo mode) with "Reselect Solo-Locked Regions".
Last edited:
For this, in the piano roll, I just click to the beginning of the region, and it does that... (see first picture, when I click the playhead there, it automatically goes into the second picture. If I wanted to do the first picture again, I would have to drag the playhead to the beginning, or else it would become the second picture.)
And thanks for the explanation!
jcrosby
Senior Member
Yup, clicking the icon on the clip behaves this way. There's no way to change the behavior that I know of, you just use the space bar, or assign your control surface instead... I rarely use this. I also have key commands set so my MIDI editor is a floating window instead docked at the bottom of the screen. For some reason this helps me avoid quirky things like this that I'm not crazy about...
You can also define how the playhead behaves by holding down the play icon, you'll then see a list of behaviors you define. You can select as many of these simultaneously, or none. You have the following options:
Play from marquee selection: Playback will begin wherever/whenever the marquee tool is used to select a region.
Play from cycle: Beings playback at the beginning of the loop region.
Play from selected region: Should be self explanatory, the playhead follows selected clips.
Play from last locate position: This will rewind the playhead to the last place you started playback.
Hierarchic Conditions:
With none selected the playhead pauses when you hit stop, playback resumes where you stopped - "tape machine style"...
Once you select one or more you start to define the playhead behavior. Having more than one selected can be really useful, ex-Cubase users would probably use play from selected region frequently since this is a popular way to navigate Cubase.
The hierarchy follows the list displayed. Marquee selection supersedes all, if no marquee selection is made loop points will take over (if a loop is enabled). If a loop is not enabled playback will follow any selected clips, if none of the conditions above are met playback will default to last locate position...
I typically use play from cycle and last locate position by default. If I'm in a project where I need to navigate a lot of clips I can enable from regions... Although it's probably Logic blasphemy I rarely use the marquee tool so I tend to leave this off.. Key commands tend to get me around without the marquee for the most part...
The Stop/Rewind Icon also has a list of behaviors:
These also follow the displayed hierarchy. Plus you have jump behaviors, which happen when you hit return. (I've highlighted my defaults with bold...)
Stop
Stop and go to left locator
Stop and go to last locate position
Jump behaviors (I have all of these enabled. I want to say these are enabled by default but it's been a long time since I had to mess with these so I may be wrong..)
Jump between marquee and project start
Jump between cycle and project start
Jump between selected region and project start
Jump between last locate and project start
Looping also has behavior choices:
(Same deal, dropdown menu when click-and-holding the icon... It follows the hierarchy, or you can choose to select nothing...)
Auto Set Locators - The cycle region will set itself based on the following behaviors.
Marquee selection
Region Selection - (Also very Cubase-esque...)
Note Selection
Save As Defaults:
Once you have a transport behavior profile you like select save as defaults in each dropdown.
ALSO: The metronome has menus too!
Last edited:
jcrosby
Senior Member
Setting your transport up the way you like should solve that for you... Last locate position's a big one if you don't have it enabled, and selected regions might be useful for you as well..
OP
OP
Vik
Vi-k
Last edited:
OP
OP
Vik
Vi-k
Bounce slower than real time
Here's a tip about handling tracks that requires more computing power than your Mac can deliver. When bouncing, there's an option between real time bounce and offline bounce. People generally think that offline bounce can be a big time saver, because it can bounce a track/project faster than a real time bounce can.
But there's another, maybe more useful function built into offline bounce(and freeze): Logic will user long time than needed if that's what it takes to bounce a project/track without hiccups or artefacts. This means that if you have tracks that don't play well when playing back the project in real time, they'll most likely play well if you bounce them offline (or freeze them). So if you have a demanding track with several layers of CPU/memory hungry material, the same tracks will sound great once the Mac is allowed to use as much time as it needs to process all the data - which of course often is difficult in real time.
Here's a tip about handling tracks that requires more computing power than your Mac can deliver. When bouncing, there's an option between real time bounce and offline bounce. People generally think that offline bounce can be a big time saver, because it can bounce a track/project faster than a real time bounce can.
But there's another, maybe more useful function built into offline bounce(and freeze): Logic will user long time than needed if that's what it takes to bounce a project/track without hiccups or artefacts. This means that if you have tracks that don't play well when playing back the project in real time, they'll most likely play well if you bounce them offline (or freeze them). So if you have a demanding track with several layers of CPU/memory hungry material, the same tracks will sound great once the Mac is allowed to use as much time as it needs to process all the data - which of course often is difficult in real time.
OP
OP
Vik
Vi-k
Sorry, Tav, I don't know.
Here's a tip about measuring average performance in Logic:
First, double click the performance meter:
Next, Control-Option-Command-doubleclick inside the window that pops up.
This will show you peak values. A click inside this window will toggle between peak and average (preceded by a little tilde*) values.
* ~
OP
OP
Vik
Vi-k
"t is now possible to capture MIDI performances played while Logic is stopped."
From the list of news/changes in Logic Pro 10.5.
From the list of news/changes in Logic Pro 10.5.
blinkofani
Member
Hi, have another question!
When I make a multi-timbral instrument for Kontakt, it seems like only the 1st track can record automation, and the rest (2-16), will follow the master track. Is it possible to record automation for all of the tracks? Also, can I set those tracks to different buses? Thanks!
When I make a multi-timbral instrument for Kontakt, it seems like only the 1st track can record automation, and the rest (2-16), will follow the master track. Is it possible to record automation for all of the tracks? Also, can I set those tracks to different buses? Thanks!
Living Fossil
Senior Member
With a single output instrument you have only one Volume lane.
(however, of course you can address every controller individually per midi channel).
If you want to tweak the main volume individually, you have to open Kontakt with multiple outs.
Ok thanks!
And also, I have a very stupid question (sorry), so when I go to the score editor, every track has both treble and bass clefs, and was wondering how to remove one of the staves, so for violins there is only treble, while basses only have bass, thanks!
