Shawn Miller
1
COW Coin
Forum Replies Created
-
[Jeremy Garchow] “Yes, I agree completely about the loss of Ae. Luckily, Adobe is in good financial standing and doesn’t appear to be going anywhere.”
Agreed… but you never know. 🙂
[Jeremy Garchow] “But, even for 3 grand, Smoke is capable. It would take a lot of getting used to, but it’s good. You’d have to buy a lot less plug ins as well. ;)”
I can’t say I haven’t been curious about Smoke. I’ll be keeping an eye on how 2012 is received. Now, if I could just bring myself to trust Autodesk. 😉
[Jeremy Garchow] “I don’t know. This guy seems to think that you don’t want Apple to get serious about it: https://digitalcomposting.wordpress.com/2011/06/28/x-vs-pro/“
I have a lot of respect for Ron Brinkmann. I can only hope that his perspective will be proven wrong over time.
Shawn
-
[Jeremy Garchow] “And what if it did turn in to Alam DV? Would Apple go under?”
Obviously not, but it would be a shame if Motion didn’t gain any real traction outside of FCPX. I want to see Motion grow into a fully featured tool that can compete with AE. It might sound odd coming from me (a Windows based AE user), but AE needs more competition in this space, and currently, there just isn’t anything for less than $3k that does that… not good.
[Jeremy Garchow] “Would the post production community lose out? No, it wouldn’t.”
I disagree, where competition is thin, (generally) end users lose. I like having options, and I like to see competing products make each other better. I’ve been in the process of learning Nuke, but it’s not really a good option for me (motion graphics wise), if something should happen to AE. In the process of learning it (Nuke), I discovered something discomforting… nothing really does what AE does. It’s such a great multipurpose tool for VFX and a powerful mograph tool; I have virtually no options if anything happened to it… I really like AE, I don’t like the idea of it being the only serious mograph game in town. I would love to see another AE/Combustion dynamic, where you had two similarly priced applications that had lots of overlap in fierce competition… unfortunately, Autodesk didn’t see it that way.
[Jeremy Garchow] “I don’t think that Motion deserves, or even wants, a Cold Mountain moment. Well wait, this just came to mind: https://provideocoalition.com/index.php/mspencer/story/billy_fox_and_motion/.”
This is a good start, I hope to see more people using Motion for things like this, and I hope that a larger Motion user base sparks more utility and innovations from Apple. I feel like they gave up too quickly. Actually, I would be beyond jazzed if Autodesk jumped back into this space with a sub $1k version of Toxic… I want to see more heat in this market.
[Jeremy Garchow] “And that’s what Motion is good for. Editors doing some compositing. It’s not that sexy.”
Yes, agreed… I think it could be more though.
[Jeremy Garchow] “Motion is fine for a lot of things, but it is not Ae and probably never will be.”
No doubt… but wouldn’t it be great if Apple didn’t kill Shake for nothing? Wouldn’t it be fantastic if they actually got serious about VFX and Motion Graphics?
Shawn
-
[Chris Harlan] “I’ve done quite well with Motion. So I get peeved, a bit, when people speak ill of her, even when she probably deserves it.”
Completely understandable, lest anyone forget… AE was in the same position for years before anyone took it seriously as a tool for VFX artists. It wasn’t until post houses like The Orphanage started admitting to using it in their pipelines, that AE got ANY (grudging) respect or acknowledgement from high-end professionals. Honestly, you can still get poked at by Nuke, Fusion, Flame, Inferno and Shake (yes, Shake) artists for admitting to using AE for compositing. So you’re in good company, I think. 🙂
Shawn
-
[Jeremy Garchow] “Also, did After Effects ever have a “Cold Mountain” moment?”
Yes, I think AE has had several of these moments over the years, in high-end commercial work, music videos and feature film… otherwise, I don’t think the adoption would be nearly as wide.
[Jeremy Garchow] Does Motion? Does FCPX?
IMO, yes. FCPX may not need it as much as Motion. But I do think that Motion needs a “Cold Mountain moment” as well as a Mark Christiansen, a Stu Maschwitz, a VideoCopilot.net, an intensive course on FXPHD (or similar), and a post house like The Orphanage (R.I.P) to help drive its popularity. I might be wrong here, but I feel as if I haven’t seen Motion used to it’s fullest potential yet. If people were producing MoGraph or VFX work on par with what we normally associate the AE, then I think Motion would gain a lot more traction. Otherwise, it might as well be HitFilm (formerly Alam DV); a lot of great features… but relatively obscure and underpowered.
Just my opinion,
Shawn
-
[Shane Ross] ”
Hmmm…that sounds an awful like TRANSCODING to me. Not knocking it…I prefer it myself to the native processor intensive codecs.”Definitely, I like that you have the option to work this way if you want to. I would actually like to see Adobe invest in it’s own intermediate CODEC… perhaps based on CinemaDNG. Who knows, maybe one day.
[Shane Ross] “But that right there negates the speed difference of PPro over Avid in terms of not needing to transcode before you start editing.”
I don’t doubt that. If I didn’t depend so heavily on Dynamic Link between PPro and AE, I think there’s a fair chance that I would be on Avid now.
Shawn
-
[Frank Gothmann] “I’ll throw in my usually neglected and overseen new buddy Edius.”
I keep meaning to try Edius, given that I’ve heard so many good things about it. 🙂
Shawn
-
[Shane Ross] “Sure, you have to transcode to work in Media Composer, but that means that you don’t need GOBS of RAM or a fast processor or a big ass graphics card to edit smoothly.”
You can get by on modest resources in Premiere Pro, if you’re just editing. The gobs of RAM mostly comes in handy when you’re working between applications via Dynamic Link. For processor intensive formats and CODECS, a fast RAID array and transcoding to something like AVC-Intra, Cineform, DNxHD or Prores is probably ideal. This is where Prelude can help out immensely; once you’ve chosen your selects and your output/production folder, Prelude can then import those assets directly into Premiere.
Thanks,
Shawn
-
[John Davidson] ” Wasn’t CS4 32 bit on Mac and 64 bit on PC?”
Premiere Pro CS4 was 32 bit, but it would work on 64 bit systems. PPro didn’t go 64 bit until CS5. I think you may be thinking of Photoshop CS4.
https://www.macworld.com/article/1132810/photoshop64.html
“At WWDC 2007 Apple discontinued its Carbon 64-bit program, which left company’s like Adobe without an avenue to make its current codebase 64-bit.”
“Adobe said that they have been working on the Carbon 64-bit version of Photoshop for some time and had planned on releasing a version for Creative Suite 4 (CS4). However, with the changes at WWDC 2007, that is not going to happen.”
“Our feeling has been to deliver 64-bit on both platforms for this release,” said Nack. “We could hold back the Windows 64-bit version until we could catch up on the Mac, but that didn’t seem fair to those customers.”
Shawn
-
[John Davidson] “You can tell it from really simple things like cmd+, doesn’t open preferences. Standard mac shortcuts are ignored. There are conflicts with standard mac applications using the F# keys for things like easy ease in After Effects. On macs you have to choose between easy ease (F9) or muting your computer. I kept the mute on my computer as I use that more than easy ease.”
I had no idea
[John Davidson] “There are also less Adobe supported graphics cards on macs vs pc’s.”
Isn’t this more of an Apple issue though, since they support so few video cards to begin with? Not criticizing, just wondering aloud if Apple couldn’t be a bit better about offering more graphic/display card options.
[John Davidson] “Full-Screen isn’t supported, even though that feature was available for Adobe to implement since Feb of 2011 when Lion was first released to developers.”
Just bizarre, I wonder why this is. I wouldn’t be happy about it either.
Shawn
-
[John Davidson] “Not easily. Took quite a few hacks to get it to work (over a day of googling and trying to figure it out). Tried the same thing in FCPX and it just worked right of the gate. Premiere just didn’t want to see it.”
That’s disappointing, though I’m suprised Adobe didn’t fix it right away. They’re usually pretty good about things like that.
[John Davidson] “I’m not surprised it works easily on a PC. Adobe and macs are basically just staying together for the kids.”
I’m not a Mac user, but I can’t imagine this is a common feeling amongst Adobe users on the Mac. I haven’t heard anything like this from AE, Photoshop or Illustrator artists (for instance). Then again, I fully admit that I’m probably out of the loop here.
Shawn