Forum Replies Created

Page 35 of 242
  • Aindreas Gallagher

    August 6, 2014 at 12:06 am in reply to: A Lazy Editor’s Audio Workflow

    [Charlie Austin] “My audio’s always expanded in the primary so… skim to edit point, 1 or 2 keystrokes (no clicking needed) to extend A/B handle(s) as needed, 2 fade handle adjustments (mouse click/drag). Done.”

    OK – but we’re not actually talking about audio adjustments to a primary storyline AV element?

    So the case is editing down a music track.
    when you are editing down the track:

    how are you “skimming to edit point, 1 or 2 keystrokes (no clicking needed) to extend A/B handle(s) as needed,

    I’m messing around with X right now. how are you doing this?

    https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics

  • Aindreas Gallagher

    August 5, 2014 at 10:42 pm in reply to: A Lazy Editor’s Audio Workflow

    [Charlie Austin] “Takes me 2-4, maybe a right click to change the curve for good measure. “

    No. I really did count it charlie. 😉 after the expand audio request, then clicking on the fade handle trims and adjusting for both overlapping clips – that’s no 2 to 4 keystrokes. It’s a mess of finnicky adjustment for what should be a basic decision mate. never any harm admitting it.

    I nearly think you’d feel better if you outright vocalise there’s a bit of a problem there.

    because well, some bits of FCPX are a little sickly, feverish even, and may need a cure?

    https://www.youtube.com/watch?v=fyV2cPLuFuA

    https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics

    Some contents or functionalities here are not available due to your cookie preferences!

    This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

  • Aindreas Gallagher

    August 5, 2014 at 9:42 pm in reply to: A Lazy Editor’s Audio Workflow

    [Charlie Austin] “an asymmetric dissolve transition option would be a good thing. And I missed them for the first few months I was getting into X. Not anymore.”

    hard to see how that goes away really?

    [Charlie Austin] “I bet some of it has to do with the fact that you need to think about what you’re doing.”

    no mate. In X I’m effectively doing around seven to eight very clicky things there – where I would be naturally doing one to two (if you count sliding the transition).

    That scenario in X is just flat out not very workable.

    https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics

  • Aindreas Gallagher

    August 5, 2014 at 9:06 pm in reply to: A Lazy Editor’s Audio Workflow

    [Charlie Austin] “And 99% of the time a centred dissolve works fine. It’s not a big deal at all.

    charlie – with mucho respect, cutting down a commercial or any other track to a usable thirty off the bars really does demand asymmetric dissolves. given people can be singing either end of the join, or say chords start ascending inconveniently, it’s basically critical to weight it left or right to fake it. It’s also really important you can do it massively fast because 4/5 attempts to join music sections don’t work? It’s one operation that has to happen like butter.

    You basically cannot be going through that X style rigamarole every time – it kills the flow of decision making. I’ve just tried it a few times there.

    I haven’t used a video dissolve in five years but a controllable audio dissolve would be critical my end – hard to see that as a one percent scenario?

    https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics

  • Aindreas Gallagher

    August 5, 2014 at 8:37 pm in reply to: A Lazy Editor’s Audio Workflow

    we should stop this David. Why are we hammering on this? Oh wait now I remember:

    https://i.imgur.com/574uWB1.jpg

    https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics

    View post on imgur.com

  • Aindreas Gallagher

    August 5, 2014 at 8:33 pm in reply to: A Lazy Editor’s Audio Workflow

    [Charlie Austin] ” If you have a custom head/tail fade handle fade combo you like on a component, just copy/paste attributes to your other selected components. Easy. “

    well no charlie.
    so let’s forget copying and pasting things after the fact and concentrate on the version of a custom dissolve:

    OK -so you have an audio music track you’re cutting down, you make a cut or a lift say, and then at the new edit point join in the music, where you might have placed a dissolve and slid it left or right to taste… instead:

    at the edit point, you are first expanding audio components, then you are selecting and modifying the fade on the outgoing clip, then selecting and modifying the fade on the incoming clip. I believe this is correct. and that is a quite serious amount of clicks.

    look at it this way – if apple read this, they might be minded to move on it, because that is a lot of work for every instance?

    https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics

  • Aindreas Gallagher

    August 5, 2014 at 8:20 pm in reply to: A Lazy Editor’s Audio Workflow

    [Steve Connor] “Aren’t people saying that the FCPX way is tolerable not more efficient?”

    no that’s bang on – I was just surprised at the way it ends up working. Charlie said people have been sending feature requests on the audio dissolve – no harm as it seems a bit of a headwreck. although messing with the fade gui and options is a fun town. Although I found it a bit finnicky to access the fade handles on the edge of the clip?

    https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics

  • Aindreas Gallagher

    August 5, 2014 at 7:25 pm in reply to: A Lazy Editor’s Audio Workflow

    Hey sure – it’s just that every time you want to re-construct a custom audio dissolve:

    after you make the blade edit, you’re first of all right clicking and expanding audio components,

    then you are selecting and modifying the fade on the outgoing clip, then selecting and modifying the fade on the incoming clip. I’ve done a few run throughs – that’s pretty much the process right? Jeremy seemed to be doing that in his demo on the thread below.

    Have I got this right?

    https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics

  • Aindreas Gallagher

    August 5, 2014 at 6:17 pm in reply to: A Lazy Editor’s Audio Workflow

    [David Lawrence] “On my current job, I’m doing this for hundreds and hundreds of individual short clips. So the difference between taking 4-seconds to manually perform a layered A/B transition and a millisecond key press to apply a dissolve adds up pretty fast. 😉 Maybe I’m missing something but I can’t imagine doing this as efficiently in FCPX. “

    that’s my thing too. It feels like one of those really basic things where if I had to do it the way the guys are doing it, again and again throughout the day – I’m pretty sure it would start to drive me gaga. I’m kind of surprised it hasn’t come up more often. Also the fact that the dissolve left and right edges can act as magnetically connected rolling trim points for the whole timeline is indescribably weird?

    https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics

  • Aindreas Gallagher

    August 5, 2014 at 12:07 pm in reply to: A Lazy Editor’s Audio Workflow

    I’ve got nothing to add really, I just wanted to get the microwave into the thread title.

    https://i.imgur.com/574uWB1.jpg

    https://vimeo.com/user1590967/videos http://www.ogallchoir.net promo producer/editor.grading/motion graphics

    View post on imgur.com

Page 35 of 242

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy