jigsawlogic

Good to hear the issue is fixed in L9...and yet another reason for me to upgrade : )

I noticed on page 1 that you're also having issues with Logic trashing the CS prefs (for me it happens every time Logic crashes...which also seems to be only when I'm trying to map controller assignments). There's a script at OpusLocus.com that allows you to save and restore multiple CS prefs files. Saved my butt a few times already.

The CS plugin provided by Korg for the nanoKontrol offers users 2 options: 1) An extremely limited set of inflexible mappings 2) Overriding the mappings at the expense of visual feedback and the loss of the ability to record-arm tracks. I came across something that looks like a great solution: LC Xmu by Opus Locus, which apparently addresses the negative consequences of option 2. I'm going to give the demo a shot early next week.

Just checked. Yes, it does, so long as I'm using the CS plugin. No feedback of any kind without it.

Hi David. I know about the key command. Here's the situation I'm trying to make possible: Say I have a MIDI controller w/8 buttons. I wish to assign each button to arm a corresponding track in the currently selected bank of tracks. The only way I know of to accomplish this is to make the following settings in the parameter assignment window: Class: Channel Strip Channel Strip: Fader Bank (w/correct number in the following field) Parameter: Record Ready Key commands are not assignable on a channel strip/fader bank manner, as far as I can see, which limits its function to the currently selected track. So, as a workaround, I'd have to find a way to split an incoming message from a button into two separate messages, one which selects a track (is this even possible?), and then one which corresponds to the "toggle record enable" key command (can MIDI messages be mapped to key commands in the environment?). As other DAWS have succeeded in allowing generic MIDI control surfaces to work in this manner, but Logic hasn't, I posted this in what seemed to be the right subforum. If I haven't missed anything, could you be so kind as to move it back?

I'll answer that when I get to the studio later tonight. For now, I can say that using the CS plugin, the lights on the nanokontrol are all responsive to the status of mute/solo/record (the mutes even flash on other channels when solo is used), and also change to reflect the status of of the currently selected bank of tracks. Whether or not it maintains this responsiveness when a control is activated by mouse rather than by the nano remains to be seen. Along with the record ready parameter, feedback controls are all greyed out for user-made control assignments (although not so for the Korg default assignments). So the CS plugin is configured pretty as a peach, but confoundingly inflexible. In my own modes, I've tried ticking the "exclusive" tab, which according to the manual serves to override the function of non-ticked assignments of the same physical controls. But a slider assigned by Korg to "volume" will still maintain that assignment even when using a custom mode, in effect becoming a dual control, mapped both to stock and custom assignments simultaneously. I'd be fine if I could temporarily defeat the stock control assignments, but it looks like the only thing defeated is me : ) I'll write back when I'm in the studio later.

This would enable any MIDI surface with buttons to arm any track within a bank. Whatever you have is not really a "control surface" without it.

This would enable any MIDI surface with buttons to arm any track within a bank. Whatever you have is not really a "control surface" without it.

Unitor8 for MIDI, Digi 192 for audio. Straight USB for the nano2. I'd be surprised if a protocol designed specifically for control surfaces neglects to include one of the more basic functions control surfaces were designed to achieve. Rather, I suspect that the problem isn't HUI, but the range of mappings Logic makes available to the end user (as far as I've seen, only automatable parameters and key commands). Other mappings are internally existent, but I suppose I'd have to be a programmer to get to them. Like the ones at Korg. Now if only they hadn't assigned everything to "No Mode", leaving me no option but to kill their setup if I want to create custom modes.... According to the Internets, whose infallibility is unimpeachable, setting up a control surface to arm target tracks within a bank is not an issue in other DAWS. Maybe something for Logic to address in the next revision? Anyway, time to ditch the CS plugin and hit the environment with this little bad boy. Hmmm...wonder if the lights on the surface are activated via MIDI? That would make for a fun environment project...

Unitor8 for MIDI, Digi 192 for audio. Straight USB for the nano2. I'd be surprised if a protocol designed specifically for control surfaces neglects to include one of the more basic functions control surfaces were designed to achieve. Rather, I suspect that the problem isn't HUI, but the range of mappings Logic makes available to the end user (as far as I've seen, only automatable parameters and key commands). Other mappings are internally existent, but I suppose I'd have to be a programmer to get to them. Like the ones at Korg. Now if only they hadn't assigned everything to "No Mode", leaving me no option but to kill their setup if I want to create custom modes.... According to the Internets, whose infallibility is unimpeachable, setting up a control surface to arm target tracks within a bank is not an issue in other DAWS. Maybe something for Logic to address in the next revision? Anyway, time to ditch the CS plugin and hit the environment with this little bad boy. Hmmm...wonder if the lights on the surface are activated via MIDI? That would make for a fun environment project...

Thanks for the response! I guess I should clarify a bit... Doesn't the key command only function on the currently selected track? I'm trying to allow for typical control surface behavior--arming tracks such that the arming occurs on the correct track in the correct fader bank. To do so, at least within the control surface assignment window, I'd need to set the buttons up exactly as outlined in my first post (class:channel strip, Channel strip:fader bank, Parameter:record ready). Is Record Ready a parameter which is only available via programming a cs plugin, or is there some hidden method in Logic which makes this available to the end user?

Thanks for the response! I guess I should clarify a bit... Doesn't the key command only function on the currently selected track? I'm trying to allow for typical control surface behavior--arming tracks such that the arming occurs on the correct track in the correct fader bank. To do so, at least within the control surface assignment window, I'd need to set the buttons up exactly as outlined in my first post (class:channel strip, Channel strip:fader bank, Parameter:record ready). Is Record Ready a parameter which is only available via programming a cs plugin, or is there some hidden method in Logic which makes this available to the end user?

I'm using a new Korg nanoKONTROL2 with Logic 8. The MIDI driver and Logic CS plugin have been installed. However, the CS plugin is set up w/a hierarchy that always preserves the original functions of the knobs/sliders/buttons (for example, using learn mode to assign a slider initially assigned to "Volume" in "No Mode" to another parameter in a new mode will result in both being altered). So, I'm attempting to build my own set of custom modes in order to use the controller as flexibly as possible. But something has me completely stumped: in the default CS NanoKONTROL assignments, viewing the Controller Parameter Assignments pane, one can plainly see the following: Class: Channel Strip Channel Strip: Fader Bank Parameter: Record Ready RECORD READY!!!! And it works. But don't try this one with "Learn Mode", which only seems capable of assigning automatable parameters. What can a mere mortal do to assign "Record Ready" to a control surface element?????? I can't for the life of me figure this out. But the answer is staring me in the face every time I look at the nanokontrol CS plug parameter assign window. Any help would be tremendously appreciated!!

I'm using a new Korg nanoKONTROL2 with Logic 8. The MIDI driver and Logic CS plugin have been installed. However, the CS plugin is set up w/a hierarchy that always preserves the original functions of the knobs/sliders/buttons (for example, using learn mode to assign a slider initially assigned to "Volume" in "No Mode" to another parameter in a new mode will result in both being altered). So, I'm attempting to build my own set of custom modes in order to use the controller as flexibly as possible. But something has me completely stumped: in the default CS NanoKONTROL assignments, viewing the Controller Parameter Assignments pane, one can plainly see the following: Class: Channel Strip Channel Strip: Fader Bank Parameter: Record Ready RECORD READY!!!! And it works. But don't try this one with "Learn Mode", which only seems capable of assigning automatable parameters. What can a mere mortal do to assign "Record Ready" to a control surface element?????? I can't for the life of me figure this out. But the answer is staring me in the face every time I look at the nanokontrol CS plug parameter assign window. Any help would be tremendously appreciated!!

what type of .cst is it? instrument/audio channel/bus/aux/output? I want to know which folder to save it in. thx!