Jump to content

milk_meat

Member
  • Posts

    58
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

milk_meat's Achievements

  1. Thank you so much for your suggestions Atlas, the first one works well as a workaround. As for the second, I need to revisit folder packing. I looked at it when I first started using Logic many years ago but abandoned it because I didn't see it as very useful and confusing to work with but maybe I need to re-visit it.
  2. Hi guys, I'm predominantly a Logic user but recently I've had to learn ProTools and they have a few key commands that are incredibly useful and can't seem to find a way to replicate them in Logic. Perhaps I'm not using the Logic equivalent terminology when searching but hopefully someone here can bridge the gap. The Pro Tools commands and what they do are as follows. 1. Control + Click This allows you to align the start of a region to the start of another region. You simply select the region that has the desired start point and then hold Control and click on all the other regions you want aligned to it. 2. Command + Option + "G" This is what Pro Tools calls the "Group Regions" command. This will allow you to select all of the regions that you want grouped together, then when you execute the key command, it'll temporarily merge all of the regions you selected into one big region that you can move around. When you're done moving it where you need to, you can ungroup the merged region and all your original small regions are back and followed your move.
  3. I think I was able to solve the issue, the troubleshooting at the end of the thread seems to have solved it.
  4. I went ahead and purchased Metagrid Pro in case anyone has the same question. I was able to set up a custom template in a day and it was pretty easy. It's not perfect but overall, it's pretty great.
  5. Scenario : I'm in the Piano Roll and my playhead is off screen. I want to change the timing of a few notes that are in front of me and I go ahead and change the grid view from 8th notes to 32nd notes. Logic then goes away from the notes I wanted to change and jumps to wherever the playhead is. Is there a way to prevent Logic from doing this? I do like that I can grab the playhead and Logic catches it and plays wherever I move the playhead to. Ideally, I don't want to lose this ability to fix the issue above.
  6. Logic Remote is really great but I want to be able to customize the look of my buttons way further and create midi CC faders etc.
  7. Hi guys, I've been looking to utilize my ipad to speed up my composition workflow. I was inspired by Junkie XL's video (https://www.youtube.com/watch?v=RSl_unnPab0&t=57s )I bought the latest TouchOSC but it's got quite the learning curve, I was thinking of trying out Metagrid next. I was wondering what your experiences were.
  8. I do keep the tracks because I don't know when I will need something or when revisions come in (they always do). Having your palette readily available to work with is extremely helpful vs trying to gather up everything you need from prior projects. I also utilize hiding tracks whenever possible. I've heavily weighed out the pros and cons and my current workflow and what I'm doing is what's been working the best. It's just the damn region delay reset that's a thorn in my side. I wish you at least had the option to turn it off.
  9. I get it, it's not the workflow most Logic users use. It might be tough to picture without being in front of the computer. Film/TV/Games often require big bloated orchestra sessions where all the different sections are laid out by individual articulations. You always have to have orchestra sections from a few different developers depending on the sound that's required for that moment too which adds more tracks. Here is a screenshot of a portion of my session, perhaps it helps.
  10. I wonder how big Hollywood composers like John Powell make it work.
  11. Yeah I investigated this option when doing research before posting. All of my Midi tracks are multi-output (16 stereo) channels with different articulations of an instrument on each of the channels. So it's like Trumpet Legato (Ch 1), Trumpet 1/8 note (Ch 2), Trumpet 1/2 note (Ch 3), etc. It's one of the steps I had to take to keep these big sessions manageable. Using the track delay sets the same delay time for all 16 channels, however, each articulation often requires a different delay time and the one size fits all approach doesn't work.
  12. Thanks for taking the time to help guys. The folder stack idea might be feasible but still not ideal. However, I already have all tracks in various summing stacks in my best efforts to organize things and Logic doesn't allow sub folders.
  13. My orchestral projects are 300+ tracks already which is challenging to manage and keep track of things despite all my organization efforts. Adding duplicate tracks and ballooning the project even more is not a good solution.
  14. Perhaps I'm missing something. Are you suggesting I have both the original track and the duplicate track with the CC automation in the project and use both for different purposes?
  15. Thanks for your help guys. It's truly appreciated. It's too bad if that's just the way Logic works. Because unless I'm missing something, duplicating the track and doing my automation there and then copy/pasting the automation lane by lane back to the original track isn't saving me any time. It's quicker just to do it how I had been doing it, doing the automation and then moving the region/notes back on the grid and re-inputting the Region Delay. Also, doing any of these workarounds a couple of times is fine but doing it 60-70 times in a day really adds up. That's been my dilemma.
×
×
  • Create New...