Solo function in Logic 10.1.1 not working

Hi Alexander,

In reply to your original post I found that I had the same problem. I have the feeling that in your thread various aspects of the solo function were discussed, yet I'd like to chip in on the problem mentioned in the original post.

Pressing the S button on a track did draw a yellow frame around its regions but it did not really solo the track. This occurred when I upgraded from Logic Pro 9 to Logic Pro X. I discovered that in keyboard assignments the S key was assigned to "Channelstrip Solo ein/ausschalten" (toggle channelstrip solo). This needs to be changed to "Spur Solo ein/ausschalten" in "Spuren im Hauptfenster" section. If you do that, soloing a track works as expected.

See the attached screenshot. Hope the German language is clear to folks with other languages.

Best,

Sven

PS: sorry for posting on a 2y old thread but I got the impression the original problem was not addressed.

Dont know if it's an ASC related issue or a User error but your screenshot isn't displaying........

Can you try again please?

Having said that... this sounds like the mute problem will be something you have done as this is not normal behavior... Solo/Mute works normally here as exopected and has done so throughout the lifetime of LPX.

but when you press the M on the channel strip it should mute all regions in that track.

Ah, thats a slightly different description compared to earlier, of your problem.... and is easily fixed... as it seems you have a different Key Command Assignment...

This maybe because of the Key Command Preset you are currently using

Check the Key Command Edit screen.... below

Assign the key commands as shown ... with Shift and M to mute selected regions and M to mute tracks,... or however you wish to set it up yourself.. Some people reverse the key combination and use Shift & M to mute tracks and use M to mute selected regions.. Your choice.

Additional:

If you prefer the older LP9 Key Command Assignments and you still have LP9 installed... you should be able to choose the LP9 Key Command preset from the drop down menu.... and all your key commands will stay the same in LPX as they were with LP9.

Something is certainly not right... as I have never come across such behavior.....

First thing to try would be...

Click any channel strip's solo button to solo it, then option-click the same solo button to turn off all solo buttons.

Now test..

Next up would be to check automation to make sure you haven't got anything accidentally recorded that could be causing this..

Finally....

Have you tried the true and tested 'fix all' for weird issues such as this?

You can resolve many issues by restoring Logic Pro X back to its original settings. This will not impact your media files. To reset your Logic Pro X user preference settings to their original state, do the following:

1. Quit Logic Pro
2. In the Finder, choose Go to Folder from the Go menu.
3. Type ~/Library/Preferences in the "Go to the folder" field.
4. Press the Go button.
5. Remove the "com.apple.logic10.plist" file from the Preferences folder. Note that if you've programmed any custom key commands, this will reset them to the defaults. You might want to export your custom key commands before performing this step.
6. Remove the com.apple.logic.pro.cs file from the preferences folder. (Note this is the control surface settings file. You may need to set up your control surfaces again after deleting this)
7. Restart the computer.

Note: If you cannot find any of the files listed, you did not follow the instructions exactly as written! 🙂

Im not aware of any specific settings for Solo that could cause such behavior.....

If I understand you correctly... Please try this..

1) Create a new project

2) Create a multi-timbral (MT) Software instrument in the Create Track Dialog Box (I set the number of tracks to 4)

3) Click on the Solo button of the first track of the MT instrument. When I do so all 4 tracks solo...

4) Click on the Mute button of the first track of the MT instrument. When I do so all 4 tracks Mute as expected..

Is this not what happens for you?

Or...

Are you describing something else?

If so, can you create a new project and list your exact steps one by one so i can try and recreate what you are seeing..

Thanks..

Nigel

Note: I'm in the studio for the next few hours but Ill check back later....

Ah yes, indeed I agree... now I understand what you mean... (My apologies for being a little slow)

My workaround in Omnisphere for example.. is to use the solo/mute buttons in Omni's Multi interface rather than use Logic's... Same applies for Kontakt....

It's not the most elegant solution/workaround I agree..... but it does work.

Having said that i tend to stick to the one track - one instance method.... so i rarely have to use the workaround..

The upside of using one instance per track is while it does add a degree of extra CPU for each instance, you then get a better spread of load across multiple available cores so that can work as a benefit rather than a detriment..... and overall you can get equal if not better performance using the one instance per track method compared to the multi method.

You are welcome Alexander

Glad i could help point you in a slightly different direction 🙂

Cheers..

Nigel