[Jeremy Garchow] “but not having audio only dissolve don’t bother me.”
I appreciate the helping advice to clear up the situation. It’s quite easy to see how this works for you. If I were to adopt FCPX I would clearly quit fighting this and simply “do it that way.”
I find that many of my secondary elements (as well as audio elements) end on the same frame as the primary story counterpart. This makes the trim functions frustrating because they don’t come with a way to choose whether I want the choose the primary, secondary, or other audio elements. Every trim command defaults to the primary story elements — often not what I want. Eventually you just habitually grab the mouse and click on the element that you want to invoke trim functions on. For a number of wrist and creative reasons, that is just not the way I choose to work.
For me and my habits, this is feels like … by the time we’ve accounted mouse-driven point-and-click of secondary and audio elements, I might as well have just rather had a “track” bound to my keyboard and “done it that way instead.” The FCPX trim commands work well if there is only 1 cut near your playhead, but that means as your edits gets more complex, the work gets harder (and yes it also gets harder with the other NLEs, but not to the same degree in my humble opinion).
If I am to work in a way that is complimentary to FCPX’s design, should I be relying less on trimming? Or is mouse-driven interaction just designed into the process of complex trim’s via FCPX?