Forum Replies Created
-
Andrew Kimery
July 23, 2016 at 5:49 pm in reply to: Apple, FCPX and Secrecy – RedShark “Guest Author”[Noah Kadner] “So you’re saying 90 days from private demo to ship date is the industry standard timeframe. I’ll bet that’s news to a lot of developers.”
Wasn’t the meeting where the demo happened open to the public though? Does having to sign an NDA make it a private demo? I’m genuinely curious where the line is.
I think Oliver’s POV is based in what Tim talked about in his first post about publicly traded companies having to release w/in the quarter if they talk about an upgrade to an existing product or they could run afoul of SOX. This probably doesn’t apply to Apple in this case since I doubt they have to worry much about when they ‘recognize’ the revenue from FCP X given the boatloads of cash they make from other parts of the company.
-
Andrew Kimery
July 23, 2016 at 5:05 pm in reply to: Apple, FCPX and Secrecy – RedShark “Guest Author”[Oliver Peters] “The trouble is that the presentation has passed the 90-day mark. Obviously a release version wasn’t “just around the corner”, which is usually the case when Adobe does this. That begs the question: was what was shown simply a ginned up demo version that isn’t anywhere close to release? If so, that speaks pretty poorly of Apple’s development effects.”
People have said that it could have ties to Sierra and I think that’s probably a safe assumption so when Sierra drops so will the X update. That means a pretty long time from NAB to release, but I think Apple felt the need to reassure/placate its users. Saying something many months early at NAB vs not saying anything at all is probably the lesser of two evils. It also could help explain the NDA.
If Apple knew that the update to X wasn’t going to drop until Fall (to coincide with Sierra) then they probably didn’t want users, in general, talking about the new features and start pounding on the gates for it to be released (especially since Sierra wasn’t unveiled until two months after NAB) so every that got the sneak peek had to sign an NDA. Who knows, maybe some of the X team go pulled to work on Sierra and that’s why X hasn’t gotten much love lately.
-
Andrew Kimery
July 23, 2016 at 2:37 am in reply to: Apple, FCPX and Secrecy – RedShark “Guest Author”[Michael Gissing] “To the point of the article about whether secrecy is the winning strategy anymore, Apple’s secrecy is one of the reasons why I won’t trust my business model on their largess.”
I think the secrecy was tolerable when new hardware and software was released on a pretty reelable schedule. Pro users might not have known what new features were going to be in FCP or that Apple was dropping Moto for IBM (and later IBM for *gasp* Intel) but we knew that new things would roll out on a predictable basis.
-
[Tim Wilson] “This should go on a blurb somewhere I think!”
Didn’t mean to sound like a pitchman, but it’s the truth. Most of the time taking the performance hit for staying camera native (I’m talking HD here, not UHD or 4k) is the lesser of two evils for me vs taking the time plus, increased storage space, to transcode to a more edit-friendly codec.
-
[Tim Wilson] “Are you shooting it yourself?”
Rarely.
[Tim Wilson] “Are clients bringing it to you?”
Usually.
[Tim Wilson] “Are you part of an editorial team on the post side of a production, production company, etc? (This would cover episodics and features for sure, but also in-house corporate, worship, etc.)”
Yes.
[Tim Wilson] “What cameras/formats are you shooting/receiving?”
I generally have no idea. With MC and/or FCP Legend I’d have to know because I’d need to know which camera plugins to install, but since I switched to mainly using PPro a couple of years ago I typically just grab the footage and get to work.
-
Andrew Kimery
July 13, 2016 at 4:28 am in reply to: Izotope audio EFX in track mixer casuing problems in timelineI’ve done that before and it has helped, though w/my most recent experience the only solution was the one I mentioned a few posts up. Having the RX effects enable would mean PPro would take 10min (no kidding) to load the project. Disabling the RX effects and the projected opened up in 20 seconds or so.
-
Check out MacVidCards https://www.macvidcards.com/ and if you are on Facebook there is a group for people looking to upgrade their old Mac Pros, https://www.facebook.com/groups/Mac.Pro.Upgrade/ .
-
BM is giving away a 95% fully functioning version of a an industry leading color grading application for free. Hard to compete with that. I love the way Adobe has integrated PPro and SG (It’s what I always wanted when I used FCP and Color), but once the Lumetri Panel made an appearance in PPro (and SG didn’t get a mention) I had a feeling SG wasn’t long for this world.
-
[Steven Cohen] “I want to be a Premiere editor, not a Final Cut Pro editor working on Premier.”
From what I recall PPro’s default layout is pretty barren. It’s been a while since I used it though so maybe it’s gotten better. Don’t be afraid to create your own custom keyboard though, it’s why that feature is there. 😉
-
Andrew Kimery
July 5, 2016 at 6:54 pm in reply to: Izotope audio EFX in track mixer casuing problems in timelineUpdate.
Just heard by from iZotope and they basically said De-Noise (the only plugin I was using) is very CPU intensive and can quickly bog down a machine if used a lot (and I was using it a whole lot). There suggestion was to use it less or roundtrip through the stand alone RX 5 app. I wonder if rounding tripping with Audition (and using the RX plugins there) would gain me anything? Guess I need to block out some time for workflow experimentation.