Jump to content

nixtl

Member
  • Posts

    17
  • Joined

  • Last visited

nixtl's Achievements

Newbie

Newbie (1/14)

  • Reacting Well Rare
  • Week One Done
  • One Month Later Rare
  • One Year In Rare

Recent Badges

0

Reputation

  1. These are Take Folders, not traditional folders. Therefore, it is impossible to pack an empty track without regions.
  2. Is it possible to pack a take folder without Logic automatically adopting the top track/region's color for all the takes? Yes, I already know how to Auto-Colorize Takes during recording. I imported these files from another DAW/engineer and would like each take to remain easily identifiable by color.
  3. Using my song's markers as a guide, I regularly use the Marquee tool to "box out" a section of the song and adjust parameters up or down. Is there a shortcut to automatically generate automation nodes for a selected automation lane based on the current set of markers?
  4. When delivering individual tracks to a mix engineer, I like to give them volume automation from the rough mix so they have a decent starting levels and don't have to completely re-create all the work that I did. However, it is also helpful in many cases to leave that engineer the option to pan a track wherever they want in the stereo field. An added benefit of this would be preserving mono tracks that do not necessarily need to be stereo for any reason. This cuts down on DSP usage and file size. In summary, it would be cool if "Include Volume/Pan Automation" was separated into two check boxes upon Export/Bounce, like so: - Include Volume Automation - Include Pan Automation
  5. Bummer! I was hoping they'd fix that on the latest update. Thanks Eric!
  6. This issue is intermittent for me, but I was able to recreate it from a brand new empty session. 1) I select multiple tracks in the Logic Pro X mixer and use a Send slot. 2) With all these tracks still highlighted, I Option+Click one of the tracks to bring the Send Values to 0. 3) Only the track on which I am clicking sets the Send Value to 0.0. The rest all go to +6.0: Opt+Click Send on the first track sets the values like so. The same behavior occurs if the sends are for different busses. Is this a bug or did something change between LP9 and LPX? In Logic 9, all the highlighted tracks properly snap their send values to 0 when Option+Clicking. Now I have to individually Opt+Click to snap each send value. This especially causes issues with grouped tracks. I'm wondering if maybe it's a Magic Mouse issue. Sometimes the thing seems to have a mind of its own.
  7. I appreciate you taking the time to check out the template. Have not had a chance to test your file out yet, but I am interested in knowing more about why the routing phenomenon occurs. Would you be able to provide me with a link with more info regarding PLC and its behavior within Logic? I prefer to structure my busses in this seemingly convoluted way so that I can quickly adjust/automate submixes and groups (e.g. multi-layered background vox or stereo/doubled guitars). Perhaps I need to look more into utilizing Track Stacks more often if they don't cause as many problems under the hood. Please correct me if I am mistaken about what you are saying, but it confuses me that Bus 64 would causing issues. Is the fact that I am making full use of ALL the Aux tracks at once the problem? I used your method from another thread on this forum in creating all of those Aux Tracks in the first place (but with 64 Audio Tracks and Ascending Inputs): My previous LP9 template for the past 3 years has made use of Bus 64 as my Mix Bus without any issues there. And that template works fine in LPX too. That template does not use ALL 64 Aux Tracks, but it uses most of them. My projects and recording clients can vary greatly. I am hesitant to permanently relabel my Auxes because my routing setup needs to be flexible and tied to each template. Side note: Wish list item if any Logic developers are reading... If I could reorganize my Aux tracks within the mixer (a la Pro Tools) without having to Create Track in the Arrange Window, I wouldn't even think about attempting to create a huge routing template like this. Aux Track creation on the fly is awesome, but Apple is way behind Avid in the organization department. Also, the new color palette lacks proper contrast to easily distinguish between what is what. Why did they ditch functionality over form? /end rant Thanks again Eric!
  8. Heh, this was meant to be my template to end all templates, the idea being that I would never have to create any new Aux Busses because they are all there already. Then I just delete what I don't need. I changed the MIX bus from Bus 64 to Bus 62 and tried this again. Now I am getting a weird error that I have never seen before: Were you able to reproduce the bug on any of the audio tracks?
  9. Thanks Eric, I have attached the template in which the problem is occurring. It only seems to happen in this template. If I import session data from a track recorded in this template into a new session, the merge/glue/join command works fine. So there is a workaround for now, but I would love it if my template worked as-is. Songwriting.zip
  10. Anyone? Tried this in a brand new session and had no problems. With/without plugins, with/without folder track stacks enabled. The function worked as expected. But what confuses me is that this problem occurs in a brand new, from-scratch template that I have created. So I can't help but think there is some option within the template that needs to be disabled. I just can't figure out what that option is.
  11. Just hopped onto the LPX train from 9.1.8 and have been encountering quite a few issues trying to adjust my workflow. Forgive me if this is not a bug, but I cannot seem to figure out why Logic is doing what it is doing. In my session, I have a DI Electric Guitar with Amplitube as an Insert. It is inside of a (Folder style) Track Stack. I play on the track in one place, and then I stop and record on another section... Original Waveform When I attempt to "Join" or "Join per Track" I am prompted with the usual familiar dialog box from LP9, "Non-contiguous audio regions require the creation of a new audio file!" So I click Create. Instead of quickly joining/merging the regions, flattening fades, and retaining the exact waveform volumes, I start seeing the "Bouncing Regions" progress bar, as if I had selected "Bounce in Place" without the BIP dialog box. The resulting merged region is actually now a mixed down bounce instead of just merged regions: Another odd thing is that even when the plugins are bypassed, "Join" will merge the regions but add extra Gain to the waveform. I do not want extra Gain or Plug-ins! Attempting this same function outside of the Track Stack on a new track, the same thing happens where Gain is added, however the insert plug-ins do not seem to factor into the merged audio whether they are bypassed or not. Is there some hidden option I have selected that is causing this to happen? Please advise... this is driving me crazy. Thanks! *** UPDATE *** Insert Plug-ins are being applied with the same behavior on "Flatten and Merge." Super annoying.
  12. Yes, it seems that as I remove more and more plug-ins, the problem goes away little by little. Perhaps I need to reorganize my signal flow to compensate for the latency induced by the plug-ins. I've tried changing Plug-in Latency Compensation to "Audio and Software Instruments" but that definitely affects the playback to a point where it's impossible to play along with anything. Everything just goes out of time. If I change this setting and disable all the plug-ins on the busses, that seems to fix the MIDI issue, but then I am not able to hear the instruments as I have processed them. There's a lot of give and take.
  13. Here is the session. Please let me know if you can't re-create the issue. Cycle Jump.zip
  14. Start Marker is at 1.1.1.1, but I have changed the SMPTE 1:00:00:00:00 to 3.1.1.1 for the sake of being able to make my bounces the proper length for TV music. I never start projects on Bar 1.
×
×
  • Create New...