Jump to content

Joe Lonsdale

Member
  • Posts

    361
  • Joined

  • Last visited

  • Days Won

    1

Joe Lonsdale last won the day on July 15 2023

Joe Lonsdale had the most liked content!

About Joe Lonsdale

  • Birthday 07/27/1974

Personal Information

Recent Profile Visitors

280 profile views

Joe Lonsdale's Achievements

  1. I think it must be a bug, I got this behaviour too and posted. But no luck. Finger's crossed they fix it quick and update Logic as drum editing just became my worst nightmare (again)! Mine wasn't even cutting at transients, it was incorrectly identifying kick transients and who knows what it was doing with the rest!
  2. Okay, this is day-2 of fixing a live drum performance (admittedly it's a complex 6-minute prog thing). It should have been a 3-hour job, but my new version of Logic (10.7.9) just won't play ball and I am back to manual editing like it's the year 2000 again. 1) The transient detection function is simply broken: it misses each kick hits by a predictable millisecond or two and I have to manually go in and move each detection. It recognises the snare transients much better but not perfectly and I still need to go through and check/correct each transient. Either way, it is easier to just manually cut each transient myself directly on the region, like in the "old days". 2) If I do correct the transient recognition, I cannot right-click and select Slice-At-Transient-Marker without selecting Flex & Follow on the track inspector: I do not want this option selected as the tempo changes on this project are complex and this function seems to visually move the audio files around making it hard to tell what I am actually cutting (I also think changing this setting is responsible for issue 3, below). 3) After finally getting some sort of workflow going yesterday, I noticed Logic had inserted hundreds of cuts in the edited regions that I had to manually fix-up (3-hours): these cuts didn't fall on a transient but weren't totally random either, they seemed to appear somewhat near every edit and were not time-aligned aligned across the regions, despite the regions being grouped and Edit/Quantize-Locked together. It would have been easier to just start again, but the drums are a complex comp and I no longer am able to find out where each part is from, which is my bad, I will have to build this safety net back into my workflow. (image above, this is after manually correcting the transient-detections on the kick and snare, engaging Flex & Follow to reveal the Slice At Transient function and then letting Logic do just that: luckily I have undo). 4) Forward playhead to next transient doesn't work - it just send me to another part of the song. I have been working in Logic FOREVER and whilst I won't pretend I am an expert on Flex, it has always been helpful in identifying transients and cutting the regions on those transients, allowing me to quantize the regions from the Event List and then quickly deal with the gaps and overlaps. I have never liked the sound of Flex's own quantize-audio function and can always hear it working, although I do occasionally try it again incase the algorithm has improved. A lot of my projects involve drums being added LAST in the process, which is super-common these days and Flex should make this simple, but it doesn't seem to be helping me at all at the moment, in fact quite the opposite. Has something about Flex substantially changed since my old Logic system 10.3 (which worked perfectly for my workflow)? I will have to spend time finding a new workflow which is frustrating, but it would be DOUBLE frustrating if this is actually a bug in the software version and is fixed in a future release. Oh, the snap-to-zero thing (above) does now mean I can manually move transient detection lines around, thanks! I wonder if this being a project started on Logic 10.3 and continued in 10.7 has anything to do with it? I will create fresh 10.7.9 projects for my drum recording sessions next week. Rant complete. Back to drum editing 😉
  3. I'll experiment with that tomorrow, I've had a very long day editing drums and am cross eyed now!
  4. Oh, that's my bad, I left it checked... I only seem to be able to fix SOME of the transient markers manually, many remain stubbornly unable to recognise the transient and simply move to estimated transients around the one I want. I cannot seem to manually pencil one in either. I'll continue to experiment and update the thread if I find a solution.
  5. I am also getting weird behaviour when I manually cut the region or use Split at Playhead, it doesn't keep my position: And places the resultant cut to the left of where I placed it.
  6. The Transient Marker is wrong in the Audio Window too:
  7. I've tried both options... Exactly same behaviour.
  8. Hi David, yes I do. See attached: And you see by this Snare drum track that it has no problem there!
  9. Hi. I have never found Flex very good at fixing the timing multitrack drum sessions: the Slicing / Quantise thing always seems to leave artefacts. However, I had found a method I liked by using "Slice at Transient Markers" then quantising the resultant regions in the Event list and manually cleaning up afterwards. However, Logic 10.7.9 seems to be reading the markers late, resulting in this slice that has obviously misread the transient position of a very well recorded kick drum track horribly! It seems okay with the snare drum track. Now my method has returned to the dark ages and I am sad ;( Thoughts anyone?
  10. What a strange behaviour. I wonder in what scenario this would be helpful?
  11. It's reassuring that I am not doing anything out of the ordinary! I'll leave the post open for a couple of days to see if there any interesting alternative solutions... 😀
  12. I think rather than insert hidden CC messages that could wreak havoc with another producers workflow, I am better off sticking with an obviously erroneous note that is visible and therefore harmless 😉
  13. When exporting MIDI tracks from Logic I always put a dummy-note at the start to force Logic to export a MIDI file that starts at the true song start-point. This always seems like such a silly workaround and I suspect there is a more "professional" way to achieve the same thing: a MIDI file that starts at the start of the song, not from the first MIDI note. Perhaps there is a setting?
  14. Perhaps stick to a bigger company for longevity. Addictive drums are great, I sometimes use BFD3 (although it is horribly user-un-friendly). Most of the time I can get Logic's Drum Designer to sound great, using samples to enhance to stock sounds... Dare I suggest you experiment with booking a REAL drummer through a service such as Airgigs? I often use this for live drums and normally pay between $100 - 200 for a session and the results have been incredible...
  15. And now you could find that patch file and save it in the project folder if you wanted...
×
×
  • Create New...