Jump to content

TimeForMusic

Member
  • Posts

    322
  • Joined

  • Last visited

Recent Profile Visitors

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

TimeForMusic's Achievements

  1. I use "Singe view" quite a bit for a manageable view of my signal flow. I am playing around with the feature of reassigning aux channels to see how much I can achieve. It would be nice to have everything assigned in an order that makes sense (and having it consistently reflected in all mix views is a nice bonus).
  2. This is only true in the "tracks" view mode, not the "single" or "all" view modes.
  3. I recognize that this may be a bit complex, but I'm eager to gain a better understanding for organizational purposes. Currently, we're aware that dragging the order of aux tracks in the mixer's "single" and "all" view is not possible. However, what we can do is reassign the aux channel that an aux track is linked to using the MIDI environment. For example, if we take an aux track situated at the far right end of the mixer, examining this track will likely reveal that it's assigned to a high aux number. By reassigning it to "aux 1", the track will be moved to the first slot in the mixer. The challenge arises because this reassignment seems to erase the plugins and corresponding signal flow. In the context of a template, this reordering means that everything related to buses must be reconstructed, including all routing and plugins. I'm curious if there are any workarounds to reassigning aux channels within the MIDI environment while preserving their original aux track state. Any insights into how this process works would be greatly appreciated.
  4. Just out of curiosity, what specific computer specs are gonna matter most when it comes to this? Is it RAM? Cores? Curious what upgradable factor would influence bounce speeds the most.
  5. Hi all, pretty simple question but I can't figure this out? Is it possible to assign MIDI CC to controllers via the Controller Assignments page? (i.e, MIDI CC such as "Modulation", "Breath", "Sustain", etc.)
  6. Just want to bump this as I've been having this problem as well with no idea how to fix it. It is becoming a real pain for me as I want to update all of my patches, yet dragging in 50 or more patches just produces a line of "Untitled", "Untitled", "Untitled" etc. I have to rename every single one manually before re-saving them and hope I don't need to tweak or update them again any time soon. Has anyone found a workaround to this since?
  7. David, thank you so much and so cool to have figured this out. This is exactly the fix I was looking for! I was also digging through the package contents but wasn't able to get much further, so thank you for this! Now it's just a matter of finding a way to apply to this to all my custom patches (and I guess I'd have to re-do this each time I update them), but hey, I guess that's what Keyboard Maestro is for 😁
  8. I created a PDF to hopefully better explain the issue: Custom Library Patches - Colors not Adapting on Load.pdf
  9. These instructions appear to be about making custom tintable icons, but that's not what I'm currently trying to accomplish.
  10. Hi all, hoping this is relevant here (I started a thread on the issue here): I have a question regarding saving patches with track tinting. When I save a user patch with a factory tinting icon and load it onto a new track, my custom patch doesn't adapt to the new track color. Instead, it loads with the color it was initially saved with. Can someone help me understand why this happens? Loading factory patches with tinted icons does not behave this way; it only occurs with custom user patches.
  11. Really cool stuff. Unfortunately, it doesn't seem to address the problem of custom user patches saved with tinted icons not adapting to the color of tracks they're loaded onto. It's like we need a "none" color option to save onto tracks first. I've been saving my user patches with the default green, but when I load the patch onto a purple track, the track (and tinted icon) color gets reverted to green when the patch loads in. Again this doesn't happen with the factory patches; only custom user ones. If it's okay, I might bring up the issue into that thread!
  12. Hey everyone, I've observed that in the Logic library patches, many have gray factory icons that automatically match the color of the track you're loading the patch onto. However, when I attempt to save my own patches with these 'gray' factory icons and load them onto new tracks, my custom patches unfortunately load with the color they were saved with, not adapting to the color of the track they're being loaded onto, like the factory patches do. Can anyone help me understand why this is happening?
  13. Certainly willing to. Do you know how to include videos in feedback submissions?
  14. One thing I noticed, if those here could help me pinpoint this: I noticed that beyond Logic 10.5.1, when you select a new track, the library browser will 'refresh' for a split second (see the above video: the 10.8 library window will all turn blank and empty for a split second before displaying the patches again), whereas in Logic 10.5.1, this does not occur. I wonder if within this rework lies the origin of the lag. Does anyone know what is going on with the quick reset we see? I know beyond Logic 10.5.1, they changed it so that "Enable Patch Merging" also resets when you select a new track.
×
×
  • Create New...