Jump to content

MikeShapiro

Member
  • Posts

    648
  • Joined

  • Last visited

MikeShapiro's Achievements

Newbie

Newbie (1/15)

0

Reputation

  1. The missing Mac editor is unforgivable, but in my case it wasn't a problem. I just ran Parallels. But yeah.
  2. This seems to be my solution then. Since all I really want are sliders to send MIDI CC and buttons to trigger key commands, it looks like I can set this up by bypassing the entire control surface scheme.
  3. Actually... one more question. What about the other route? If I put the controller in non-MC, Dumb MIDI Thing Mode, which allows me to configure the knobs and fader to my heart's content, is there any way to get Logic to associate buttons with key commands? Can key commands be triggered by any MIDI data outside the control surface system?
  4. One thought though. My former controller keyboard was a Nektar, which Logic recognized directly as a control surface. I could assign the knobs to arbitrary MIDI CC values *and* map the buttons to Logic key commands. Any idea why this unit was able to handle both kinds of interaction, whereas my XTouch can't?
  5. Sweet. I'll check it out. Thanks so much!
  6. Thanks for the response! The XTmini actually can be toggled between MC mode and a default mode that I presume is what you're calling a generic MIDI fader box. The trick is trying to get both kinds of functionality, as you say. When in MC mode, the fader and knobs do *something*, just not what I want them to do. For example, the fader will control the Master Volume in Logic. Is there really no way to bend the rules here? I'm not above hacking configuration files and otherwise going under the hood.
  7. In case any of you tech geniuses have gotten an X-Touch Mini to work happily with Logic, help would be appreciated with the following dilemma: Per instructions, I've configured the thing in MC mode as a Mackie Control Surface. Assigning buttons to Logic Key Commands seems easy. Go to key commands, hit Learn, etc. What I can't figure out is how to assign knobs or the master fader to output a particular CC message. For example, I'd love to get the master fader to send CC1 (modulation). (I even tried bringing the thing to a PC so I could use the Windows-only editor software. It doesn't seem to allow the configuration of MC mode.) Any help would be appreciated! Mike
  8. BTW I really like Fisherking's trick of bouncing directly to replace the files used by the mastering app. This seems analogous to the trick that recent versions of Melodyne use, to overwrite the actual files that a DAW is using (while preserving the originals as a backup).
  9. Thanks everyone for the thoughtful responses. For me the issue here is efficiency. I've been trying to think of what the individual mixes have in common, and whether I can migrate those things to a shared mastering project. (This could easily be Ozone standalone, as in FisherKing's example, instead of a second Logic Project. In fact I see the advantage there, in being able to simultaneously keep Logic and the mastering environment open.) So for example, it seems like makes sense for all the cues to share a peak limiter, so I don't end up limiting them twice, once individually and once for the album. Likewise if I end up using the same saturation setting across the album, it might make sense to migrate that as well. I really wish that Logic had more elegant support for multiple content timelines in a single Project. (Call them multiple cues, multiple songs, whatever.) It seems like there would be a real opportunity for efficiency in albums, multi-cue scores, or similar projects with shared resources.
  10. Imagine that each track on my album, in its own Logic project file, has an identical set of plugins on the mix bus. Let's collectively call them $sharedmixbusplugins. If I render each Logic project individually with nothing on the mix bus (making sure there's no clipping because I removed the limiter), then load the resulting audio files into a new "entire album" Logic project, with each audio file on its own track, then load up $sharedmixbusplugins into the mix bus of this new project, then re-render each track one at a time... will I get the same result as if I had rendered them individually from their own Logic project? My motivation here is to be able to make a change to $sharedmixbusplugins and not have to load 20 Logic projects, one at a time, make the change, and re-render. This way it seems like I could easily experiment with different shared mix busses and render the entire album in one go. Thoughts? Best practices/better ideas? A multitude of thanks in advance.
  11. Big Sur. I've only had this problem with one project so far. It might be some interaction with Take Folders, since that project was very audio-and-Take-Folder heavy.
  12. Thanks David. I'm glad it's not something weirdly specific to me. I guess I'll wait for 10.7.0.1 and hope that this issue gets addressed. Mike
  13. On upgrading to 10.7 I tried loading a project that had a modicum of virtual instruments and a large number of vocal take folders. I found that Logic became incredibly sluggish, beach balling when I tried jumping between markers or hitting play. I reverted back to 10.6.3 and the project worked fine. Has anyone else encountered an issue along these lines?
  14. This may or may not help, but every audio region has numerical Fade In and Fade Out parameters. I don't know that they can be automated, but setting them is simpler than drawing fade curves.
×
×
  • Create New...