Jump to content

johnnybones

Member
  • Posts

    14
  • Joined

  • Last visited

johnnybones's Achievements

Newbie

Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Reacting Well Rare
  • Conversation Starter Rare
  • Week One Done

Recent Badges

1

Reputation

  1. OHHHH thanks Joe!!! I (DUMBLY) had the mono> stereo version of the plugin selected (I never paid attention to that and it completely escaped me when I was trying to find out why it wouldn't bounce to mono - like I forgot that that was ever even an option along the way.). My bad! Really appreciate the thorough explanation and pictures!! It will help as I go through & ensure everything else is in the correct mono/stereo configuration too. And yes haha got look out for the ol' mix engineer 😄 Cheers mate
  2. Hello! I have a guitar DI with logic amp and a pedal board on it. I want to bounce a copy with the amp / pedal tones to send to my mixing engineer, and include the DI's as well in case he decides to re-amp them. When I "Bounce in place" with the effects turned on (and not bypassed) it gives me a stereo file, which I don't want. I notice that if I disable the delay plugin (the "tru-tape delay" that comes with logic) then it will bounce to a mono track (the amp and distortion pedal are fine, it still bounces to a mono track even with those turned on). However I don't hear a difference between mono/stereo mode of the gain plugin placed last in the chain, so I don't think the delay is even supposed to be stereo (??) - and even if it is i just want to "collapse" it to MONO. I have already tried (based off of what I could find on here regarding stereo>mono bouncing) the gain plugin LAST in the FX chain, set to MONO mode, and it doesn't help. I have also already tried changing the output of the track to mono > output 1 (instead of stereo output). Also didn't help. Obviously its something to do with the delay pedal since otherwise it does what I want. Is there anything I can do? Something I'm doing wrong? Thank You
  3. THANK YOU KINDLY! This is what I was looking for, big help buddy! Much quicker this way, glad I hung on lol Cheers.
  4. Haha yes I did, I had already tried that long before making this post. And have since went and tried other methods of using flex from three different YouTube videos I watched. Like I mentioned I don’t like the result , too many artifacts. Do you know if there’s a way to do what I’m after? Again: just to snap transients to grid, (nothing else at all) Please let me know cheers. P.S. …No Flex!!
  5. Thanks for the response! "The thing is - you're not just using Flex to quantize the transients (which you seem to do in a quite complicated way, read on), you're using it to fill the gaps/double transients that occur when one snippet gets moved more than the next or previous, so switching off Flex after quantising would reveal those gaps/double transients." -Yes, thats exactly the problem. I just basically want to snap the transient markers to the grid. No stretching or doubling or gap filling, or anything else. Then I will go through and crossfade everything. Is this possible? (I'm glad people have success with flex but I have no success; constant artifacts, causes more problems than it solves. Unusable for my purposes.) If it's not possible please let me know. For now I am back to manually editing everything: cutting, dragging transients to grid, then crossfading. IF I could have some command to snap the transients to the grid (i.e. to the nearest 16th note, ideally without even touching flex time), that would save me a lot of time. Is there a way? And yes I will bounce it as soon as I'm done editing, before recording anything else. Thanks!
  6. Thanks for the reply! Okay, committing is exactly what I want to do. Only, can I somehow keep all the little regions separate? But without any flex? (but also without reverting back to unquantized?) As in, looking Like this: separate regions So that I can still edit crossfades? The whole reason being that the quantization is of course not perfect and I need to get rid of artifacts and such, so if it is all bounced in place into one big region, then I won't be able. In other words, I just need to utilize flex for 2 seconds to quantize, and then i want it gone forever haha (but still have all the little regions remain in their new quantized positions!). Is there a way? Cheers!
  7. Hello, I am editing multitrack drums. My workflow so far: -I have editied the transient markers on the relevant tracks -Sliced regions at transient markers -quantized -I am now going through and manually fixing up the cross-fades and any mistakes But flex time is still active and it is prdocuing lots of articfacts and constantly changing the waveform as I edit. BUT if I turn off flex-time, then everything becomes un-quantized. Is there some way I can quantize, and then "preserve" or "print" the new regions as quantized (WITHOUT Joining them all, since i still need to revise crossfades. That is, I still want it to be a bunch of little audio regions), and then just go through and edit the new audio regions as if they were "normal" audio regions (albeit in their slightly new positions on the grid) without any more flex time? Like such that I can turn flex time OFF (for good!). Any help is much appreciated! Let me know if anything requires further explanation. Cheers.
  8. BTW I just tried disabling Q-lock editing in the group, but when I make Marquee tool edits still the same thing happens: regions start and end in all different spots like in the second picture above. Now, I had already been using flex time before and made a bunch of edits with that, but Flex is currently disabled (so doesn't that mean my tracks should be completely unaffected by flex? or am I wrong in that?) and I just want to be able to edit the old fashioned way. Anybody know what has happened?
  9. Hello, I'm working on editing some multi-track drums (8 mics) and I want to just do it manually (that is, just using the Marquee tool, dragging based on the grid, and then extending the region a little bit to cover the gap, and fading appropriately). I am wondering if I should keep the Q lock function enabled for this? My understanding is that for quantizing or using Flex-Time you definitely want that ON for the kick, snare, and possibly toms... but is it needed for the "manual" way? Or is it something to do with when the audio is being warped by flex-time? I have started some edits and noticed that (despite my tracks being grouped and all) once I marquee a section, if I zoom in the regions are all starting / ending at slightly different times. I assumed that is because of the Q-lock? (If not please do tell me, as I may be more lost than I realize lol). Pics of pre-marquee edit and post-marquee edit to show what i mean: pre post Any help is much appreciated, as well as any tips for editing manually since its my first time doing this with multi-track drums (would like to avoid Flex and quantizing here, sorry to the fans of those!). P.S. I've seen posts from 9+ years ago asking for transparent audio regions for situations just like this... still no dice??? Can't find it anywhere! Cheers, Justin
  10. Hello, I have an 8 mic drum recording session going on, with several tracks recorded and comp'd as a group, according to plan. But in the most recent one, my kick track started misbehaving and no longer cooperates with the group. I searched and found this thread viewtopic.php?t=124977 as well as checked out this one viewtopic.php?t=54823 (which was linked in the above thread) and tried their solution of ensuring that the tracks have the same number of takes, same length, double checking the group settings, and tried making cuts at beginning and end of regions. Tried reimporting the files and tracks into a new project as well. No luck. The issue began towards the end of the song and at first I thought it was only affecting the new regions (from the bridge onwards) but now I have realized that I can't go back and change the comping of the previous sections either; the kick track still won't behave as a member of the group (even though it was before, and I comp'd them all before, and I haven't changed those take folders at all!). I CAN however drag from the right side of the whole take folder and shrink the whole thing, and change the take folder name, and all 8 including the kick behave. but I just can't comp. Weird? Is there anything else I can do? One other thing I saw was unpacking and repacking the take folders, any thoughts on that? I figured it shouldn't matter if the takes and their respective lengths are already the same anyway? A little hesitant to do that (8 tracks with 5+ takes and a new take folder for every section of the song... seems like a pain ) But if somebody vouches for this method it I can give it a go. ALSO, I am wondering If there is a workaround Thankfully we did some basic comping after recording each section; so I would only need to do a lot of work on like 2 sections of the song... so is there any way I can just edit 8 take folders simultaneously WITHOUT the grouping feature? For example, the way I can just highlight 8 regions and change the size of all of them, change the gain, etc... I tried highlighting them all and comping but it didn't work. Is this a bug? have I done something wrong? My best guess is at one point only the kick track was armed for recording by accident, and it recorded something to only that track. but then I would have immediately deleted (or more likely pressed undo), and as shown below the take folders all look the same. All 7 of the other tracks in the group still behave properly. Here are some screenshots of the situation: 1) group settings Look good: they are all on group 2: "?" (1) 2)kick take folder (2) 3) snare folder (for (2) the and (3) we are looking at the folders with 5 takes showing) (3) I just realized that the takes have different names now on the kick from the rest of the tracks; that would have happened when I was using the kick as my guide track to edit all 8 tracks, thinking they were still grouped. I will try changing them all back to just simple tack numbers and see if that does anything. BUT fwiw on the previous sections the names are still all matching and still the same problem persists! Also I just realized that the kick folder, if you look on the track panel on the left (pic 2) has a "B" written on it. I've seen that before but am not too familiar with it - its a different track version right? I've had that happen a few times and its always by accident since I've never set out to do that. Could that be the problem? I tried switching it back to "A" but the "A" version has completely the wrong audio information so there's no use to that. Anyways I hope that information is enough for somebody more knowledgeable to figure out what exactly is wrong and how to fix it. Do let me know if there is any other info I can provide that would help with a diagnosis / solution! For future songs (and the ending of this one) I have just made a new project, tracks, groups, etc. and it works fine. Its just this song that needs rescuing (no matter how I reimport or make copies the problem persists) - but like I mentioned above, even just a sub-optimal workaround that will let me edit all 8 comp folders as one, even if its less efficient (within reason lol) would be great to know as well! However I definitely want to ensure that I can prevent this problem from happening in the future. Also FYI its a brand new MacBook Pro running the latest Big Sur version 11.6 and Logic is also fully up to date, checked all that initially to see if it was a problem! Cheers!
  11. Okay thank you! Will try "File>Import>Logic Project..." later this week. I Appreciate the help!!! Cheers.
  12. YIKES I think this is it.. because in the mixer window I notice I now have 2 stereo output strips. (screenshot attached). This would only happen if something has gone wrong right? In this case, since it probably happened 2 weeks ago or so when I first encountered the bug in this particular project, reverting to the last save prior to the bug is not really an option. For future reference though, how would I do that? AND for salvaging this particular project, do I want to just copy the tracks I do need into a new blank project? Or does it even matter once I have manually reloaded all the correct patches? (in other words - the project still seemingly works fine now that I've switched the instruments back, should I be worried about the fact that there are 2 stereo output strips? Or just continue working and ignore?) Any advice is appreciated Thanks JakobP for bringing this bug to my attention!! Cheers.
  13. What you describe is a known bug when opening multiple Logic projects at once, which I recommend one never does when working in Logic Pro. Thanks David, good to know! Yes I never have 2 open at once unless I am copying, which I hadn't been doing for this project or really at all lately. After reading what JakobP linked, I think it is that, because I notice my project has 2 of the stereo out strips in the mixer And I have done a lot of unpackinging and repacking take folders, so I bet I did an undo or 2 right after and maybe that's what's been happening. Cheers!
  14. Hello, I've been having this problem for a few months now: When I am working on other parts of my song (ex. recording and comping/ editing vocals, or guitar) my existing software instrument/ MIDI tracks are getting completely screwed up - the instruments are all changing into other instruments, and sometimes not even an instrument at all, but some sort of reverb channel (?? screenshot attached: you can see the picture is of a synth, because the track was a synth before, but now it says 4.7s prison main floor). The worst part is it doesn't undo. I will be doing nothing different than what I had been doing for a session (just doing a 4th vocal take, say) and then all of a sudden I hear some weird synth where my drums should be sounding, and the same for my other 3-4 software instrument tracks active. The MIDI regions all stay as they are, so the performance is still there. I immediately start pressing undo and the tracks won't change back, but things I did before the tracks changed WILL get undone, so it seems Logic is not even tracking these as undo-able steps. I've learned to just save all my synth settings as new presets, whereas before I just expected them to save with the rest of the project. So at least now I can recover the exact sound with some effort, but it is still very frustrating. I am running macOS Catalina 10.15.6, and Logic Pro 10.6.0 Anybody else ever have this problem? Any suggestions or help is appreciated. Seems like a bug. I remember it happening before, several months ago, but now it seems to happen more often. Thank You!
×
×
  • Create New...