Jump to content

kgdukes

Member
  • Posts

    52
  • Joined

  • Last visited

kgdukes's Achievements

Rookie

Rookie (2/14)

  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done

Recent Badges

1

Reputation

  1. Thanks again to all that jumped in on this issue. Here's the update for anyone that's still playing along: I got both keyboards properly sending midi and controller data by deleting all the learned controller assignments, deleting the Nektar Controller modules in the Control Surface Setup, deselecting Auto in the Midi Controllers prefs window and selecting Midi 2.0 in the Midi General window. I added back one channel's worth of assignments which included 1 bank of EQ, one bank of Preset and 1 bank of Smart Control assignments on the LX controller. The problem returned, with only 1 LX controller wired into the system physically and virtually in the Environment. I deleted the Smart Control assignments on a hunch and the problem disappeared. I deleted all the other assignments and re-learned the Smart Control assignments and the problem returned. It's whatever is going on between the controller input and those particular assignments connected to the Smart Controls learned assignments. Any clues and suggestions are greatly appreciated. Thanks again, KD
  2. Thanks for all the input. Here's the current status: I tried the config with and without the Nektar control surface installed. Logic would only see one LX at a time which I presumed was part of the midi confusion and the results were always the same no matter any setting options I tried. I reinstalled the Nektar CS Software and forced Logic to see both LXs. I had to go into the Environment to reconnect them into the sequencer but when I did and when I selected Auto in the Controller Prefs, the problem went away. Logic had forgotten the connections after leaving it open all night, but I reconnected everything and all is perfect again. There's something weird going on with Logic obviously since it keeps reconfiguring things under the hood. And since both Nekatr and the Logic forums all say that these units should function as plug and play generic controllers. It's not a Prefs file issue either, I'm working from a fresh Preference rebuild. For the moment though, all is good. Thanks again for all the input. I'll update if things change for the better or worse. Thanks again, KD
  3. I thought the had uploaded with the last reply. Here's the Auto select option. And here's the full connection chain: Both LX 1and LX 2 plugged into a powered USB hub as is the Helix. I installed the LX software which has their control surface assignments, but I haven't used them as I'm trying to take full advantage of having 2 separate controllers to assign to different commands and parameters. They're all being used as generic controllers per Nectar's advice, therefor the Auto option is normally turned off. The issue happens whether I have the boxed ticked or not.
  4. Here's the Setup window after selecting Auto assign. It only shows one of the Controllers and these are its settings. As I said, I haven't been using them like this.
  5. I'm using them as generic controllers, not using the "Auto" selection to import their factory preset controls. In my experience the controllers only show up there if you have selected to use their Auto presets. If there's something I'm missing, direct me to the correct page and I'll happily send along anything you need. Appreciate the patience and help. KD
  6. I noticed making the screen shots that even though I have the Helix deselected in the Midi Device settings in Logic and that I have the Midi Outs of the LXs set to 1 and 2, In the Midi setup program it shows all devices on Channel 1 and shows the Helix as Active. With no apparent way to turn off the Helix or to set the Midi channels off the LXs to the appropriate channel.
  7. Right. I was just a little too excited that *anything* had worked. The Helix I use as an audio interface (and would like to use as a controller) shows up as a controller. It was never a problem in the past but I can def turn it off in the controllers menu.
  8. Well that was a quick turn around. I presumed because midi notes were going through with the Bypass checked that other data would as well. As I'm sure many of you knew, it does not, so the controls I've setup don't work with Bypass engaged. So current status, midi triggers are reliable on both keyboards when Bypass Controllers is selected, when Bypass is unchecked, the glitch/log jam returns.
  9. I just double checked the Bypass All Controllers setting and it had somehow gotten switched back to unchecked. I re-checked it and all is perfect again. I have no idea what the hell's going on with that, but as long as it stays checked, the problem seems solved. Thanks to you all for the suggestions. I'll update if anything changes.
  10. I switched it off and immediately the response was nearly perfect, then as I played more the log jam began again and proceeded to get worse. It seems there's some feedback loop going on or something else that's impeding processing from the weakest controller connection. I'm going to give that a shot now.
  11. gacki: yes. Same hub, same settings. Not enough USB inputs on the Mac mini for separate Ins. fr3q: yes, what's reflected in the recording is what you hear as you play into the plugin. I free handed it in, but I can def try a click locked performance and the arpeggiator for further debugging. It'll be later today before I can get to that. The mod wheels etc are all in 0 position. palonoid: Taking both controllers straight into the Sequencer Module from the Physical Input module doesn't make any difference.
  12. Here's an audio file of the issue. Just recorded it into Logic which confirms the Sequencer is seeing the issue as well. I used a kick sample triggered by 2 notes. It's just a test riff I use to adjust settings. The first is LX 1, the second is LX 2. You'll easily hear the difference. DRUMs Midi.aif
  13. Polanoid: Monitoring within Logic seems to reflect the mis triggered response, but due to the issue (jamming on faster performances) the notes are going by so fast it's hard to tell. It's only recording note on and off and that seems fine, but attack time may be accurately reflected as late. fr3Q: LX25 1 is set to Midi Send Channel 1, LX25 2 is set to Midi Send Channel 2. Both are reflected in Logic's monitor correctly. I just installed a Midi Montior and captured the output of each, playing the same drum fill at the same tempo. As best as I can tell without any audio feedback from the perforce, the glitch isn't occurring just playing into Midi Monitor. It recognizes each controller and verifies their midi channel. Here's a shot of the results of each:
  14. I haven't done any monitoring outside of Logic. That'll be the next step if no one has any experience with this syndrome here. The Glitch is delayed triggering of notes between the controller and plug in instrument and random mis-fires of velocity levels. Soft attacks triggering as hard attacks, faster and more complex performances triggering rhythmical randomness that has nothing to do with what was played in. So in general, random lateness and loudness. To the degree that makes the plugin unplayable.
  15. Hey all, I have a system using 2 Nektar Impact controllers going into Logic on Midi Channels 1 & 2. Both are connected to the Logic Sequencer module in the Environment via 1 cable each. Both are working as generic controllers. The issue is that with both connected, one will function perfectly with near zero latency input response and the other will produce a glitchy response playing into software plugins: Random velocity glitches and randomly delayed triggering of Midi On. If I turn one off or disconnect it, then plug it back in, it will be the one that will function perfectly and the other will display the glitchy behavior. It's impossible to get them both to function 100% at the same time. Anyone have an idea what's going on here? Other than the midi out channel settings, both controllers are set up identically and their connections into logic are exactly the same. The system is: 2 Nektar LX25+ controllers, an M1 Mac Mini, a Line 6 Helix I/O and the latest Mac OS, Logic and Logic plugins. Thanks, KD
×
×
  • Create New...