Jump to content

10.0.7 track stacks lose smart controls external assignments


JJHP3
 Share

Recommended Posts

I'm having trouble using an external controller (Oxygen 88) with smart controls. Logic appears to learn the assignment, but nothing happens when I push the fader on the Oxygen 88. However, I set up a new user account with nothing else running and it works just fine in this account, but I would really like to get it working on my regular account. So, there appears to be some kind of conflict - but how would I go about resolving it?

 

Edit:

I'm not sure what I did, but it seems to be working now - though as others have pointed out, not inside a stack. 

Logic Pro X 10.6.1

macOS Catalina 10.15.7

iMac Pro

Processor 14-Core Intel Xeon W Processor Speed: 2.5 GHz

Memory 64Gb

Apogee Duet

Link to comment
Share on other sites

  • 3 months later...
  • 2 weeks later...
  • 4 months later...
Smart Control external assignments in track stacks still not working in 10.4. I put in a bug report to Apple. Even if it still worked, not sure that I would use the workaround in the Controller Asssingment settings of choosing "software instrument" and it's #, instead of "selected track". I WANT to use "selected track". That's the way I have my template setup, with my 8 external control knobs mapped to 1-8 in smart controls for any and every track.
Logic 10.5.1, OS 10.14.6, MBP 15" 2016 2.7 Ghz i7, 16gb ram, UAD Apollo/Twin, LaCie 1TB SSD.
Link to comment
Share on other sites

  • 2 years later...
The issue persists in 10.5...

can confirm.

 

The more i try to get away from working in the box, the more i find i cannot for some silly reason.

2019 MBP 16", Logic pro 10.5.1, Mac OS Monterey 12.4, 2.6GHz 6-core Intel Core i7, 16GB memory 2667 MHz DDR4

Link to comment
Share on other sites

  • 2 weeks later...
  • 2 weeks later...
  • 5 weeks later...
Still here! I hope they solve this for 10.5.2

Yea, I’m pretty sure they’ll get around to it after more than half a decade of complaints and several updates already:-)

2019 MBP 16", Logic pro 10.5.1, Mac OS Monterey 12.4, 2.6GHz 6-core Intel Core i7, 16GB memory 2667 MHz DDR4

Link to comment
Share on other sites

  • 5 months later...
  • 2 weeks later...
  • 2 weeks later...

Hi all

 

It seems that this issue doesn't effect everyone!

 

I just saw footage of Spitfire Audios, Christian Henson adjusting the parameters of a cello in a stack, contained in a Spitfire Audio (SFA) template.

 

 

It's not so clear form the video, but I have the template and the track he's automating is in a stack.

 

Perhaps if this issue is only affecting some users, it explains why such a major issue has been ignored for so many years and updates..?

 

I'm wondering if it might be some kind of settings issue..?

 

Cheers

Joey Dolezal

Link to comment
Share on other sites

  • 2 months later...
Hi all

 

It seems that this issue doesn't effect everyone!

 

I just saw footage of Spitfire Audios, Christian Henson adjusting the parameters of a cello in a stack, contained in a Spitfire Audio (SFA) template...

 

He's not using Smart Controls though, he's just mapped the controller directly to the parameter (CC value), which works fine.

 

I've just found the same issue with Smart Controls and am almost resigned to the fact I can't really use folders/stacks anymore if I want to do this, surely this issue should be fixed?

 

Thanks,

Mike

Edited by mikerolls
Link to comment
Share on other sites

  • 1 month later...

What i don't understand is:

why using smart controls at all? what is the advantage of having to map smart controls rather than controlling your vst instruments directly from you hardware controllers?

Maybe i'm doing it wrong but the way i use Logic is i control any selected track's (even inside track stacks) expression, dynamics, vibrato etc of any vst instrument i want (once i set it up one time in the controller assignment expert view it's always gonna remember it).

So as an example, i have my nanokontrol studio with 8 faders, the first fader controls expression, second dynamics and third vibrato.

If I create a new file in logic, load a vst (like synchron strings pro or opus), load any preset, I can control the automation of expression, dynamics and vibrato right away from the nanokontrol.

I also filter out midi CC in the preferences so that it doesn't write any CC on the midi regions, as i just want to use automation curves in the arrangement view, where i can overwrite with latch or touch my automation curves.

What would smart controls add to my workflow?

Link to comment
Share on other sites

Hey ravez :)

 

I suspect they won't add anything to your workflow because by the sounds of it you are manually mapping your hardware to your software.

 

I like using smart controls because I don't have to do any mapping. They are pre assigned to my hardware. It's just a shame they stop working when in stacks.

Link to comment
Share on other sites

What i don't understand is:

why using smart controls at all? what is the advantage of having to map smart controls rather than controlling your vst instruments directly from you hardware controllers?

Maybe i'm doing it wrong but the way i use Logic is i control any selected track's (even inside track stacks) expression, dynamics, vibrato etc of any vst instrument i want (once i set it up one time in the controller assignment expert view it's always gonna remember it).

 

What would smart controls add to my workflow?

It wouldn't necessarily add anything to your workflow, but it would offer a different workflow. Once smart control knobs are assigned hardware physical knobs, those are global. On the other hand, the mapping of the Smart Control knobs to plugin/channel parameters is individual to each patch.

 

Smart Controls offer great flexibility as to what they can control. You can map them to more than 1 parameter, and scale each parameter individually. You could for example have one Smart Control knob affect the low-cut of a filter throughout its entire range, but mapped only between 20 Hz and 135 Hz. Then only the upper 1/3 range of the knob a hi-bell kicks in around the 3.5 kHz this time increasing in gain, and a distortion plug-in is switched on when the Smart Control knob passes the '8' mark.

 

So you have:

 

Assignment (Global)

Controller knob 1 = Smart Control 1

Controller knob 2 = Smart Control 2

.

.

.

Controller knob 8 = Smart Control 8

 

Mapping (individual to each patch)

Mapping (Vocal Patch)

Smart Control 1 = Low-cut (full range), Hi-cut (7—10 range), Distortion on/off (8)

Smart Control 2 = Compressor ratio

Smart Control 3 = Compressor attack

etc...

 

Mapping (Guitar Patch)

Smart Control 1 = Distortion Gain

Smart Control 2 = Phaser

Smart Control 3 = Flanger

etc....

 

Mapping (Lead Synth)

Smart Control 1 = Osc 1 Tuning

Smart Control 2 = LFO rate

Smart Control 3 = LFO to Ptich routing depth

etc....

My new book on Logic Pro is out!

Link to comment
Share on other sites

  • 7 months later...
New Logic Pro user here, and I came across this issue when using Spitfire Audio's BBCSO, and their Logic Pro template which puts the orchestra sections into stacks. So surprised this is still an issue. Just commenting to keep the thread alive, and register my hope that it gets resolved soon!
Link to comment
Share on other sites

  • 3 weeks later...
Yep just run into this issue once again, thinking that just possibly it's been fixed in a recent version. Of course not. Has this really been an issue for 7 years now? Clearly they're never going to fix it. Yours, disappointed..
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...