show first message show previous message Showing Logic-users Message 199699 of 246190 show next message show last message

Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search!

From: "John Pitcairn" <johnp@...>
Date: Sun, 31 Jul 2005 at 9:18:52 PM
Subject: Re: [LUG] LC host-switching, splitting & remapping (was: User button on LC)
Message #199699
This is a reply to #199691.
--- In logic-users@yahoogroups.com, Paul Najar <paulnajar@j...> wrote: > Ok. So do you mean that your thinking is that you should -switch- the LC/MC so it's controlling one or the other at one time? It reads that this is what you're looking at. That's my personal approach - I prefer to keep it very clear which app is the current target, rather than having to remember how the controller is split up. Switching is pretty fast, and doesn't require bringing the target app to the front. > To my way of thinking the ideal would be to have certain buttons & > faders on the LC/MC controlling Logic and other buttons & faders on > the same LC controlling Totalmix. All active at the same time. The > ideal way for this would be to be able to specify which program > (logic or Totalmix) each controller on the surface sends to. > Is this possible and do you see the value in this sort of approach? I can see that some will find this useful, epsecially for the master fader, a few buttons and jogwheel, and this will be possible using LC Xmu, with the following limitations (at least in the initial version): You must use the older LC module with Logic, and boot the surface in MC-mode, so Logic can't hog the surface. You should preferably specify that a single target app has control over writing to the LC's display, (LCD, assign, transport, LEDs and v-pot rings), because: While you can use LC Xmu to remap or split LC buttons, the corresponding button LED feedback is NOT remapped or split at present. So if you want to remap/split buttons, using buttons without LEDs is somewhat preferable. The LCD display can't be split. It's unlikely I'll ever support this, it would be an awful lot of work. It is possible to allow multiple apps to write to it, but the results can be a bit messy. You shouldn't currently remap a motorfader, ie fader 1 should stay mapped to fader 1 regardless of the target app, to ensure fader feedback goes to the correct motorfader. This does not preclude app-splitting however. Ditto for v-pots, if you want the appropriate led-ring to be lit for the correct v-pot. Reverse-mapping the feedback for remapped faders, vpots and LEDs is technically possible however, and this may occur as a later update. John Pitcairn -------------------------------------------------------------------------- LC Xmu Logic Control emulation, LC Xview software LC/MC display, Logic environments & stuff: http://www.opuslocus.com --------------------------------------------------------------------------
Viewed 1738 times, 1 reply, 13 messages in thread. Reply to this message. Read this thread.

Forum Index | Read LUG: Policy/Rules Messages Threads Digests | Post New Message | Search!


© 1994-2008, All Rights Reserved.