Jump to content

Zachchapel

Member
  • Posts

    29
  • Joined

  • Last visited

Recent Profile Visitors

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

Zachchapel's Achievements

Apprentice

Apprentice (3/14)

  • Reacting Well Rare
  • Conversation Starter Rare
  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare

Recent Badges

3

Reputation

  1. Still a problem to this very day. No solution other than just hitting "command, period" to stop recording and it automatically trashes the take you just did...and doesn't leave the whole track (or tracks if you're recording more than one that are all in a group together) highlighted.
  2. Man, I have searched high and low...and tried everything I know. Other than Logic fixing this on their end, I'd say you just have to edit in protools to avoid this issue. Unless someone has a solution that I'm not aware of, of course.
  3. Man, what a bummer. Thank you for your answer, though!
  4. So in Kontakt 7 with protools, let's say I want 30 outputs. I know the convoluted way in kontakt to route all my outputs, how many I want, save it as the AAX default format within kontakt, restart protools, etc.... However, in Logic, if you add 30 outs within Kontakt, everything above output number 25 in Kontakt is just defaulted to 25 for the output. And if you save that as your default AAX output setting in Kontakt, restart Logic, and open that particular multi instrument back up...not only is the option for how many outs for the multi-instrument still set to 25 mono/stereo max in the drop down menu when you're about to load the Kontakt software, but when I load that particular instrument, the sources above output 25 just have no designated outputs. I've scoured the Internet and have turned up empty handed. I might be wording my searches wrong, but any and all help is appreciated. Thank you.
  5. I know this is a super old post...but I'm running into issues as well. I used to just run a Focusrite Red8 with my setup but then I expanded with Native HD Thunderbolt (which I assume is just the PCI in a box) with 2 additional HD/IO's and the Red8 since it is protools compatible. However, my ping for hardware inserts in-and-out (with nothing in the chain, just from one out of a converter into one of it's inputs) always changes as well. So if I'm understanding what you're saying, putting the computer to sleep can change this due to the fact that I'd a PCI-based system? It would make sense because I never had to worry about it when I was just using the Red 8. It's pretty big differences, too...like right now it's +304 but before that it was -102...it's never consistent. Anyways, I appreciate any and all help.
  6. @polanoidThank you. What make and model machine were you running with there OS?
  7. Hey guys, sorry for the late reply. @David Nahmani I could share but as @polanoid stated, I think it's my version of Logic. I can't upgrade at the moment due to my OS not being new enough. I'm currently on Monterey 12.6.1 but upgrading OS's in the middle of a session is just too risky for me at the moment...even with Time Machine backups. In your all's experiences, which Mac OS has been very stable with logic following Monterey barring the most recent upgrade. I'd to still keep it on older OS's that are at LEAST one year behind...and not to mention my machine is super old but it's a 2018. Thanks for your all's help.
  8. No, they're not all in the same edit group as I like to edit my main rhythm left and right guitars separately. I'll break it down for you, yes. The Top two Yellow Tracks are the guitar DI's. The Very top one is guitar DI Left, and the one directly underneath it is guitar DI Right. Each one of those have their own designated group. Within those groups are all the mic audio tracks that pertain to that particular DI. So the Very top Yellow DI track is in the Left Guitar Group track along with the 4 additional tracks that highlight with it. Same thing pertains to guitar DI Right and the Right Guitar Group track. The project itself is pretty straight forward. Only 10 busses. No insane routing. Software instrument for drums and bass at the moment on a stereo tracks. I always make groups for every aspect of guitars because I'm usually always recording. more than one source at a time. So all rhythm guitars might have groups for guitar left, guitar right, and guitar center. Same with Lead guitars or Clean guitars (lead guitar left group, lead guitar right group, etc...). At the moment, there are L, R, and C groups for Rhythm and Lead guitars and one group for bass when it's actually tracked. Hope this helps and thank you!
  9. Has anyone else ran into this issue shown in the video? I've tried so hard to find a workaround but I can't. As you can see, I have a Left Guitars group and a Right Guitars group. Watch what happens when I try to highlight both groups to make an edit to both. The left side only keeps the yellow DI region highlighted but un-selects all of the left Mic regions. This makes editing a nightmare because I mainly edit using the GUITAR DI as a reference and just have the mics in a track stack because I usually never have to worry about it. So when I make a slip edit, cut, crossfade, etc...to the guitar DI and it doesn't apply to the rest of the tracks...well, you can imagine the nightmare scenario that can wind up being when you've edited for 30 minutes straight only to realize the glitch has been happening again. This glitch is random but when it shows up, I can't make it stop. I've tried deleting groups and creating new ones. Making new tracks and adding different groups, etc...any help or input is appreciated. System: Mac mini 2018 with Monterey 12.6.1 Logic Pro 10.7.8
  10. Thanks Des...you are a god amongst humanity as well.
  11. Hey have to weigh in on this because I was looking to see if logic had updated or improved this aspect of the DAW. Look, I have used logic since 2010 so I'll just come right out and say it. Logic's transient detection is just...not...good. I've been fighting with this for years and now I just do all my drum editing in protools. Logic is good for a lot of things, but that isn't one of them. That being transient detection starts for marker placements and tab-to-transient-type aspects (like placing the playhead at the beginning of a transient or taking a region start to the beginning of a transient). David, I truly do respect you and your input at all times. You are a wealth of knowledge and I've solved a lot of issues on here because of you and this forum. However, when it comes to drum editing and that transient detection is off, it causes all kinds of issues down the road with triggering, midi, slicing, any type of flex editing, etc...all sorts of things. And having to go into the transient editor and move almost every single transient by hand just isn't conducive to a great work flow. The only thing you can really rely on is slip editing and even then, it would be a lot more helpful to properly detect all the starts of transients on, lets say, kick, snare, and toms, to then use those markers to split the remainder of the drum set regions along with the kick snare and toms. Again, therein lies another problem. If the kick or snare transients start in the wrong place, you're back at square one and doing everything by hand. It honestly gets to the point where it's audible (especially with kick drums for some reason) when bad transient detection happens and you start moving things around using something like slicing on a kick drum you'll hear audible pops and clicks...it also cause triggering and midi detection to be off because it splits the beginning of the transient in half. If this only happened a few time here in there, sure...no software is perfect. That happens in any DAW and you just have to rely on your eyes and ears sometimes...but this ain't that. If you're doing a rock band that's all 4 on the floor beats, you'd think it would be pretty easy...but disregarding you that you would still have to move a lot of the transient start markers around by hand...so ok, whatever at that point...but then we get into extreme metal and blast beats or straight 16th's of double kick and my friend, after YEARS trying to find proper work around's in Logic for that, it just is what it is. I will never edit drums in Logic again until they (hopefully) address this issue. Much love and this is all said with no malicious intent towards David or Logic.
  12. Just the one I mentioned earlier that's the backup which is APFS Standby
  13. Yeah man, I only said that to confirm that there are a lot of other basic questions we could likely bypass so I'm not wasting everyone's time...which I tried to express with my comment, but I must not have conveyed that as much as I needed to. Ask any questions you like and I'll gladly answer. Regardless, all drives are SSD. Main is Mac OS Extended (journaled) and the other back-up is APFS. Behavior is consistent between running the project from either drive. I'm usually pretty good about deleting unused files and cleaning up the project afterwards to remove excess files from the audio folders. So I just did that and got rid of a bit (not a ton) of junk and the behavior seems a tiny bit better? But I could also be crazy. Regardless, thank again for the help.
  14. No, I am not. I should mention I do this for a living...and I don't mean that in a snobby way, but all the typical checklist questions I've likely considered. However, I'm always about a white-belt-mentality and ALWAYS willing to gratefully learn and take advice that I may not have considered. That being said, I've been going back and forth between protools and logic for years now...and it just seems like logic keeps on having more and more issues for me. This particular behavior makes work flow pretty crummy.
×
×
  • Create New...