Forum Replies Created

Page 1 of 7
  • Julian Bowman

    January 17, 2013 at 8:01 am in reply to: Strange crash lost 35 minutes work

    Is there any reason why we simply cannot have a save as?

    I just don’t get why not. Much like I don’t get why Apple removed the off button on their 24″ monitors. Does it hurt their ‘god we’re cool’ egos to give us Save As?

  • F*** yes! Right as stupid as it may seem I just didn’t click that bit. That’s the bit I need. Thank you. I just wouldn’t use shortcuts to activate the timeline. I use a mouse a lot. I like it. I like clicking things a lot to make me feel like I am back in a specific saddle.

    So ta 🙂

  • Julian Bowman

    January 6, 2013 at 7:01 pm in reply to: Opacity, Keyframes and dissolves

    ok, cheers, will experiment tomorrow. many thanks though

  • Julian Bowman

    January 6, 2013 at 6:44 pm in reply to: Opacity, Keyframes and dissolves

    Yes, that is what I am trying to do. I see you do it on a clip at the start of the timeline. I just tried that and it worked but if it is further in on the timeline it doesn’t so I guess this method only works at the start of the timeline, or am I just doing it wrong further in (though I think not as I get the yellow line just around the head of the clip and cmd+T but it just puts the transition over the previous clip too, even if it is a gap slug, probably because it is a gap slug rather than a gap).

    Cheers though, demystified the answer I got earlier but just couldn’t make work because I wasn’t at the start of the timeline.

  • Julian Bowman

    January 6, 2013 at 6:35 pm in reply to: zooming in on audio waveform in clip viewing area

    see, now that is a very reasoned reply. The waveform zoom isn’t something I use a lot, and to be honest in this case, and I guess in future cases, I used the sound more than I did in the past. The advantage with zooming in on the waveform was I had a visually representation of where the beat I was after was so it made it easier.

    Mostly I was asking if it wasn’t there. I get the film strip feature but I truly hate it. it gives me a headache. I can do the small amount of audio in points as it is but yep, it is something I would like to do. Let me zoom in on the scrubber.

    And I do get FCPX is different. I don’t really have a problem with that per se. It all seems quite logical in its difference. It does just feel like some of the design decisions haven’t been made sensibly or thought through fully, and when this is the same company that made FCP7 with a plethora of great design decisions implemented by the end, it begs the question why so many of them were thrown out with this new version.

  • Julian Bowman

    January 6, 2013 at 4:11 pm in reply to: Opacity, Keyframes and dissolves

    Ok, after zoom to fit I saw it didn’t fully work as it added a transition at each end, but deleting the uneeded one wasn’t so hard.

  • Julian Bowman

    January 6, 2013 at 3:48 pm in reply to: Opacity, Keyframes and dissolves

    what do you mean grab the top left corner? When I do and drag it just moves the clip length. Is there an opacity feature like the audio feature of grab and move to create a fade?

    right… whilst trying to figure out what Richard meant I tried moving the clip I wanted to add the dissolve to into a secondary track position and it created a grey roof clip and then I dropped the transition on the start of the clip and it did exactly what I wanted. So, that’s fine and dandy.

    Would still like to know what you meant though Richard. Cheers

  • Julian Bowman

    January 6, 2013 at 11:45 am in reply to: Opacity, Keyframes and dissolves

    I didn’t say you were wrong, but I did say I would do this when I had a gap in the timeline between clips. This is how I would use it. personally I have never gone from a clip to the next frame fading in from black. I’m someone has somewhere but not me. I do however go from black to 100% from a clip which has been preceded by space. So fading in after an extended pause I guess.

    I could choose the amount of seconds I wanted the gap to be using the +1 sec shortcut, nice and quickly, then put my clip there and add the dissolve transition to the start of the clip. Very easily achieving my aims.

    My frustration with FCPX is that this isn’t possible because of what appears to be an automated process of decision making on my behalf and a lack of gaps. The slugs it puts in the timeline are not gaps, they are active elements. And in this use of editing, they make things far more inconvenient.

    What frustrates me about this board, as I posted above, is that these things are accepted as being better simply because of a like of FCPX. I guess if the posts went, ‘yeah, but frustrating but try this workaround and hopefully Apple will make the change’ I may be a tad more ‘fine, ok, cheers’ but I’m being told that using 4 keystrokes instead of 1 is better and I should get a grip* (*not actual wordage used, but inferred obviously).

    So, there we have it. FCPX does it different. But in this case, its different is not better. In fact it is worse.

  • Julian Bowman

    January 6, 2013 at 11:23 am in reply to: Opacity, Keyframes and dissolves

    I beg to disagree as I would often drop the transition on the start of a clip, not making it span the previous clip because, lo and behold, I had a gap in my timeline and achieved exactly what I wanted.

    And no, it isn’t really difficult doing the FCPX method of moving forward one second but it is 4 keystrokes to one for something I do A LOT whilst editing so it has made things harder in the grand scheme of things simply because of an arbitrary design decision to alter something that worked, to something different.

    Particularly using PAL, can anyone hold their hand up and say a 10 frame jump forward is preferable and more useful than a 1 second jump forward on a day to day basis?

    I really appreciate your help Tom, and others who have piped up now and then, but there appears to be this blind acceptance that FCPX is the dogs bollocks as it is and ignoring stupid design flaws. Why on earth would you not be going ‘er, 4 clicks instead of 1, WTF?’ As I said, I have to use this software but i’ll be buggered if i am not going to bitch about its shortcomings out of some blinded adoration for Apple. it really isn’t a brave new paradigm, it is just a different way of doing things. I got it after a few hours and some tutorials. it doesn’t freak me out, doesn’t challenge my old ways, it just moves stuff around differently. Fine. Not a problem. But the design flaws of the basic functionality of it, and there are many flawed decisions, are genuinely frustrating and I kind of object to be chastised simply because I would prefer the ‘old way’ of a single goddam shortcut to the ‘new better way’ of multiple keystrokes.

  • Julian Bowman

    January 6, 2013 at 11:03 am in reply to: Opacity, Keyframes and dissolves

    Well, everything was in a single window. The zoom in / out was a pretty crap but apart from that I could do it all there.

    Just tried to move a keyframe from 1 second to 2 seconds in the Video Animation area on the timeline. Put my playhead at the 2 second mark, grabbed the keyframe. Playhead moved to the keyframe rather than allowing me to drag the keyframe to the playhead which was marking my spot.

    Don’t tell me, the old way was bad because it did what I want and I just need to learn to bow to the apps’ will rather than hoping the app would, you know, do things with a modicum of common sense.

    I’m having to use FCPX. I’ve accepted that. Doesn’t mean it has some pretty serious design flaws in it.

    Not being able to drop a transition on the start of this clip solely is a design flaw. Before we had choices. Now we have less (and despite some gentleman above trying to help me it doesn’t seem to be working).

    Having to go from Shift + -> to jump forward a second to Shift + + then 1 then . then Enter just because the arbitrary figure of 10 frames has now been deigned to be the only jump forward shortcut, is a design flaw.

    There is a long long list, and it is nothing to do with me ‘not knowing’ the software. These things are lacking. Full stop. (or rather as it may be in FCPX Shift + CTR + pirouette then \ \ then CMD + P then Full stop)

Page 1 of 7

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