solo lock will not go away
Tried everything I could think of and it comes back every time. How the **** can it be deleted from a track for good?
MacBook Pro 16″, macOS 10.15
Tried everything I could think of and it comes back every time. How the **** can it be deleted from a track for good?
MacBook Pro 16″, macOS 10.15
Logic reserves the last available track for sample playback from the edit window. Create another track and you should be able to release the solo lock on the offending track.
Logic reserves the last available track for sample playback from the edit window. Create another track and you should be able to release the solo lock on the offending track.
You’ve not got,
any inadvertent automation on the track?
a controller assignment issue sending a solo message?
I ask because you may have reassigned the click strip or the preview strip - but those have very high numbers, so that probably isn't it.
Can you see if the key command for "solo safe selected track" has a MIDI message assigned to it?
iaamusic, I checked everything I could think of. In the mixer window "read" is off so even if I had inadvertently applied that as an automation command it should be ignoring it, right? All have automation in the editing window off.
Well I had a bunch hidden so I just unhid those and there was one track in there that I set up but never put anything in. Or if I did I moved the region to another track which I sometimes do if I'm compiling a track. That's the only empty audio track. Does that count as unused?
So you have tried ctrl-click?
What is the channel strip number?
Eriksimon, I move tracks up and down as a project develops. Currently the offending track is number 2. Not sure where it started life. Curious as to why you ask? And yes, tried control click.
Okay, I wasn't sure if you meant create ANY track or create a duplicate track. I created a duplicate track , turned off solo via control click on solo button. Saved and closed project and reopened and that seems to have worked ! The old track comes up without the red bar in the solo button and the new (empty) track now has it. I'm not familiar with this concept. I have at least 20 tracks in this project, very many of which have been soloed at any given time. Everything from Apple Loops, drummer tracks, imported audio, recorded midi and software instruments, and recorded audio. The offending track was recorded pretty early on in the project. How did that end up being singled out for this solo lock? Is there something in the literature that would help explain it?
I have never run into this before and I have been doing a lot of work lately. It's nice to know a work around but is there a way to prevent this situation in the future? In any case thanks. It does work. Thanks.
had you used all the tracks that were available in the song?
solo lock will not go away