Marcus Moore
Forum Replies Created
-
Szymon is great, and they produce great products and templates. Anyone who doubts that Motion can satisfy a great deal of the graphics needs of most editors just need to browse the Motion templates pages. Sometimes I’ll just scroll thru them looking for ideas- and I’ll admit to having even bought a couple if I can’t figure out how the heck they’ve done something.
There’s another update to mObject coming soon, I think- bringing a bunch of great new features including Ambient Occlusion. The product still has a ways to go- I don’t think it’s quite as strong as Element, but it does what I need it to do, and it’s getting better all the time.
-
Well, in that specific instance you’re best and fastest option is to use the FADE IN/FADE OUT Behaviour, which can be very easily copied and pasted to different layers. I’m still fighting 10 years of key-framing habits from my days of AE (which I know has Expressions) and getting used to how great Behaviours are.
My big secret is my two 27″ ACDs. Then throw the timeline over to the second display. That way I never have to close the Keyframe Editor at all.
I would definitely like to see AE’s quick shortcuts to position, scale, etc… ported to Motion. Even if it’s still in the existing Keyframe Editor, a quick key to “solo” parameters so you don’t have to manually turn them all on/off would be great.
Sounds like a feature request!
-
[Bret Williams] “Now if Motion could feel as native to me as After Effects. As I make the switch I’m still looking for ways to do things that are so simple in AE and seem like a million clicks in Motion.”
Examples? I switched from AE to Motion for graphics work about 5 years ago- I love it. Especially now that some good 3rd party support is coming in like Mocha and MotionVFX. Now if only guys like RedGiant would get onboard.
-
At NAB, Apple told Larry Jordan “over 1 million”. Later I found out that was distinct purchases, not just installs from a single AppleID.
I’ve always had the mental number in my mind that meant around 1.2 million. Over a million, but not close enough to 1.5 to let them say that, though they could be at that number now, or over. I imagine we’ll hear again when they cross 2million, cause it would match sales of Legacy FCP.
After the thread below, I was wondering about the adoption curve, and if there was any way to get closer to that. There are 3rd parties that use different metrics to figure out individual apps downloads and revenue- one I found is AppAnnie. If you had a Pro account, we could get their estimates on FCP X sales. I haven’t emailed to see how much that would be.
-
I wonder what AVIDs growth looks like at this stage? As the most mature product in the most mature markets, I’d certainly expect their growth to be far less than FCP X or Pr.
With Larry Jordan recently mentioning that you can still buy FCP7 licenses, I think the really interesting point will be when we get to a MacOS release that DOESN’T support FCP7. When this happens, how Apple manages that message, and where FCP X’s feature set is at will be very important. It will certainly be the major motivator for which way all those customers will go when they finally migrate.
-
I think the first thing we need to admit is that we don’t know what exactly the APERTURE to PHOTOS will mean, and I think we need to distinguish a difference between Apple EOL’ing APERTURE and walking away from the Pro photography market, cause they’re not necessarily the same thing.
It could be that Aperture as a brand, or a codebase, or a feature set were just too outdated- and a fresh start (like FCP X) was needed. Since they’re combining iPhoto and Aperture into a single app, a new name and brand was probably the best way to go.
It could well be hobbled, absolutely. Thankfully my photographic editing needs are pretty light. So I’m happy to wait on the sidelines until the product is released and see how the cards shake out.
-
[Jamie Franklin] “Serious question. Screen layout in X. Can I customize it? Bin aka *cough hack* “libraries” on one screen. Sequence pancake and source viewer on another monitor and playback monitor out. “
Bins have no relation to Libraries. Bins are related to keyword/smart collections.
You can throw either the Viewers (Source/Record Windows) or the Event Library to a second computer display, and have a monitor out if you have an I/O box or HDMI out on the machine.
I used Legacy FCP for a decade, and while different, the FCP X timeline construction in my experience saves way more time than it burns in futzing, once you know how to use it.
My opinion on it is the polar opposite of yours- I think the foundation of the timeline is incredibly strong- it’s the details that need work.
-
I’ve been wary about suggestions of trying to turn it into a “manual” selection tool; but yes I suppose if you could use a command key to go up or down the stack it would save you having to move your mouse from the keyboard. Though depending on what is it you want to select, let’s say an audio clip 20 layers down, a mouse move and manual selection would be just as efficient.
Sounds like a feature request!
Honestly, after having it since 10.1, I’m STILL training myself that I no longer need to manually select clips to bring them up in the inspector anymore- so most of the inefficiency is still on my part at this point.
What I would like to see is the white dots capabilities expanded. You still need to manually select a clip to do a copy/paste or paste attributes- that’s one I’d like to see.
-
What’s wrong with the white dot? I love that thing! 70% of the time what I want in the inspector is automatically there whiteout having to manually select a clip. If you need to select something else then you do, but law of averages for me is that it’s saved LOADS of manual selection clicks and mouse moves.
-
You mean the number I said I was making up?
When Franz said FCP X’s “over 1 million users” meant an average of 300K per year, I agreed with him. That’s some pretty straight math. But it didn’t jive with the info presented in the original article.
I’m trying to imagine what I’ve suggested that’s so outlandish.
With FCP X (like CC Premier) being relatively early in it’s life, I wondered if it was an escalating curve. Whether it’s new users, or some legacy users not migrating until recent feature additions, a growing adoption curve was one idea I was positing to try and square the data presented in the chart. The one that comes from TWO external sources, neither of them me.
As it turns out it didn’t add up, even with very backloaded sales.
I posited, argued against, and ultimately disproved erroneous info by fact checking.
Yup, my blinders are firmly on…