![]() Have you tried building anything (KCs or Macros) with the Logical Editor? That section is still waaay too complicated for me to figure out. So, I’m looking for every possible alternative. Having limitations on them (48 Layouts for Artist/S1 & 96 for S4/S6) is even more crippling, given the lack of universal hardware mirroring. KC’s and Layouts are THE critical components of Macro Building in maximizing the usefulness of these controllers. Do you know where the section is that accesses that menu, in order to write a KC? WITHOUT the visibility agent, I have to launch the configuration and then launch the matching layout from the hardware, which is very distracting. However, if you reach a point where you don’t think that a behavior requires a food reward, you can switch to intermittent reinforcement or less valuable reinforcers. ![]() WITH the visibility agent, I can build a macro that launches the agent with a matching layout in one button and closes back to the default setting. You are using the clicker as a conditioned stimulus that is predictive of food. But as we’re limited to just 8 of those (WHY?), I’ve been searching for a way to access 9 and above with a KC launch. Were you able to make KC’s that accessed the View Configuration section directly? It’s the same menu that holds the Visibility Agents. ![]() My workflow changed a bit recently so I haven’t done that much, but I think now that you brought it up I’ll go back to setting up visibility agents again and re-incorporate it. I have however done “spill” via a programmable keyboard pretty much the way you did. I haven’t used soft-keys on Avid controllers so personally, ‘no’. But that subject has been discussed into exhaustion! If the hardware mirrored the DAW, beyond the default setting, 90% of the developed workarounds wouldn’t be needed. If it spilled on the hardware, the workaround wouldn’t be necessary. You pick your track and use the attention fader. All you have on the hardware is the VCAs Layout. ![]() Then you use the Attention Fader to adjust the track inside the spilled group, which again is on the screen. It doesn’t spill onto the hardware surface. That’s pretty much how this is working with the controllers. You were “spilling” inside Nuendo on the DAW Screen. Back when I used that I was mostly using a single-fader Faderport so the actual spilling onto a controller wasn’t really the outcome I was looking for. Sorry, I just realized that I think I mislead you a bit: I haven’t done it so that a controller follows, I just meant that I used the “show connected” function to get only channels I wanted visible in Nuendo. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |