shortshorts

Thanks for all the info, des99. I think all of your points are great. For my use, though, I'm thinking that this is a good choice for me. The other options are either too feature-rich at the expense of poor integration (my Keylab seems to integrate like junk), too piano oriented (trying to be a piano), or cheap or just plain ugly to me (to each his/her/their own). It seems that if someone is looking for a solid keybed, with smooth DAW integration for the basics, and then deep integration for branded plugs (NI, in this case) then this is a good bet. I'll just be kind of pissed if they release another version soon after purchase. For deep global hands-on or performance integration, I would agree that either this is not the one, or perhaps there isn't one, and the user will have to dev or hack their way to a solution.

Makes sense. I would still call that a performance perspective, but tomato tomato, etc. Since I am currently using mostly the mouse to shape sounds, I don't think this would be much different. You say you have a custom dev'd solution, which I can in fact imagine. Is that because you couldn't find a controller that does what you describe/want natively?

Fair and true - and I think you're responding with a "yes" // that downgrading my expectations on integration with AUs is a good idea, and that It would be a generic/dumb controller for the most part with AUs. I'm not really asking how comprehensive a physical controller it is, as I already have faders and knobs and pads that mostly collect dust. It seems that you're coming from a performance perspective? In which case I totally agree - not much physical control on offer with the S or A series, whether integrated or not.

Thanks for the quick response. So for AU's then I would be going in just expecting to use it in midi-mode. Do you think that is a good approach to avoid some frustration or disappointment?

I've been waiting for an MK3 announcement but not hearing anything, so I will probably buy one of these before the year's end. A few questions for users: 1. Do you find that the midi-mode works as well as any other controller for standard control of VI's? 2. It looks like when using NI VIs, you use the Kontrol plugin as a kind of control-wrapper for the NI plugs, which connects all of the native features of the controller to the plugs. Is that an accurate interpretation? Can you still tweak the plugs on screen? 3. Can you use the Komplete wrapper to control non NI VIs? Is there a benefit to that, when you can just use the controller in midi-mode instead? 4. It appears that the controller has some global navigation features - like toggling between tracks, transport, quantize, etc. Is that correct? Meaning you could in theory never use the Kontrol wrapper and still use these features to cruise around the interface and control the Logic somewhat? I am mainly purchasing for the keybed quality and german HW engineering and aesthetics. I don't use fader controllers or pads and don't need my controller to generate sounds. I just want a solid controller that's not fugly, will last a long time, and doesn't have gimmicky features, and integrates smoothly. I do have NI Komplete but don't use their VIs exclusively. Lastly - if anyone has any info on NI company status and/or if there will be a MK3 announced soon, please let me know! Thanks!

TAKE MY MONEY! No really - anybody have experience with this? Seems almost perfect - if it works like the demo vids. Only thing I would ask for (pipe dream) is for it to be integrated into the DAW more closely. I'll finish my current project manually, meanwhile wait for anymore input. Then probably buy it and report back. Thanks FF!

I've searched around and found a few tidbits of info but thought I'd put this one out more specifically: I'm getting a lot more (mostly basic) dialogue editing asks from clients that use multiple remote sources for recording interviews or conversational dialogue. Most clients have solid hardware but their guests (in the case of podcasts) usually are just using their phones or zoom/voip. I know most of us are experienced diagnosing drift (and the reasons for it) but I'm getting tired of fixing drift manually - especially when it changes throughout 1hr+ long tracks. The type of drift I'm talking about is not progressive, but instead moves late or early at random. Is there a function in Logic or a 3rd party tool that can identify drift dynamically and re-sync portions to as phase-accurate as possible? I would think iZotope would be on this one, but even in my last upgrade (RX8 Adv) I don't see it there. Even something within logic that would just do all of these cuts and nudges for me would be great. I don't need it to look like one clean file(s). I heard somebody mention using Flex, but wouldn't that still require granularly/manually identifying each drift and playing with each one a la cart?

Holy WHAT? Can you undo sections of the history only, or does it revert all the way back? Asking before I try it so I don't hose myself...

[Continued questions on large mix project] Is there a way to have undo-history on selection based processing, rather than have it buried in the main undo-history? I know that you can create takes from the selection-based processing and therefore remove or start over, but can I set Logic to recall the selection-based processing settings, in case I just want to tweak the settings later on?

[Continued questions on large mixing project] I've noticed in larger projects that when I use an external editor (RX in my case) to do clip cleanup, that Logic re-renders waveforms on previously rendered (and saved/closed from the external editor) again. After a while this takes a long time - you can't begin playback until they all are re-rendered. Is there a way to stop Logic from re-rendering the waveforms on previously edited and saved clips from earlier in the session?

Actually - can I at least link faders permanently? And ideally be able to write automation on one fader that the other one follows - or equivalent? Can I link these two faders permanentaly?

Blast! I figured there was no easy button for this. Re-learning PT isn't really an option in this situation - it's probably been 10y since I used PT. I wonder if there is a way to flip the project in PT to get the results, but then getting it back in to Logic is probably another headache alone. I haven't used "name changer" or "myriad" - is that a Logic feature? I use "rename-it" often, but I'm looking at about 1000 audio files with cryptic Adobe names. In the past I've renamed files to .L and .R but this project is way too big - or maybe I'm just a weenie? Thanks for the advice though - diving back in....

When I receive OMF files I usually just deal with this. Stereo (or 2ch interleaved) tracks come in as separate mono tracks, and I usually just pan them and forget about it. Let me know if there's a way to bring them in as ST tracks - or here's my present question: Once the OMF is imported, is there a way to have two mono tracks fold together or appear as a stereo track, and retain all of the editability? I can create stacks but then the editability goes away. Here's a screen shot of what I'm looking at - each pair of tracks is a ST pair represented as two mono tracks panned. It's usually not an issue with smaller projects but thought I'd see if I can clean this up going forward. Screenshot of project with a lot of mono pairs meant to be stereo

Blast! Oh well. Thanks for the reply, David - hope you're well!

Heyoooo! Can't find any info on this, and I would be very useful for me these days. I select a bunch of regions (say 100 regions) in the main tracks window. Then they are highlighted/selected in the Project Media window. I want to right click, and go "show files in finder," tag them all with one stroke, sort by tag and then do a backend batch process (usually in RX). Problem is, right click and "show files in finder" only seems to allow for one single file. Is there a way to show all selected files in the finder - even if not using the Project Media browser? Any secrets, or even obvious ways I've overlooked? Thanks!