Paul Neumann
20
COW Coins
Forum Replies Created
-
I don’t see that behavior on either of my machines. Macbook Pro (Early 2013) or 27″ iMac (Fall 2013).
-
And use the “set to frame size” and not “scale to frame size” on the broll. That way you can do some reframing on the 1080 footage without degrading it and stretch the amount of shots you get from it if you need to.
-
Yeah, well I have out of town guests, and a three word answer was all I had time for!
Seriously, think about software bugs as bad edits. So, how many times would you say, “I’ll wait til this airs before I do the revisions.” I’m hoping never. Stuff gets through sure, but you never intentionally let illegal color or clipped audio or misspelled graphics hit the air. And when they do you re-evaluate your processes ’cause something needs to change. And it costs more to fix because now you’re working for free (or eating into the next job) and you may have just lost a client. Put a value on that!
It ain’t a perfect world, but to knowingly release bad code that people are paying for is not acceptable. And don’t forget that a new update that’s kinda flakey to you may just be because you have a frame of reference having the last version to compare it to. To the first time buyer it’s just bad software.
So why should Apple care? I mean in both cases they’ve got your money, right? Well, I think they’re better than that. And I want to do business with companies that are better than that.
-
I’ve had some kinks in my audio over the years, but nothing like that.
-
It’s not the “new normal”, it’s really the “new unacceptable”. Apple does use Agile methdologies, but it’s foolish to let any bugs reach the consumer’s hands. The cost of fixing a bug that reaches production is generally agreed to be 10x cost to fix than what it would be to fix that bug before release. Factor in socialization/awareness factor of any bugs by the consumers (in this case Oliver) and the cost of that bug goes even higher. Agile methodology is there to prevent the very problems we’re talking about. There are “doneness” requirements of every team for every sprint or scrum. Agile demands that “doneness” include not just all dev, test and documentation, but that each team’s product (or part) COULD be released to the public with no problems.
So perhaps this is a case of what we call “scrumbut”, as in, “We did our scrum, but we didn’t cover everything.” And that’s where Product Managers get shown the door.
Apple uses Agile in their Order Management processes quite successfully. (Opinion Insert: this is obviously a VERY important part of what their development operations exist for.) Facebook, JP Morgan-Chase, AT&T, Google and yes, Adobe all use Agile and release often several times a week with no problems.
So, it’s not the “new normal”. And if you look at how Apple develops the software that fuels their actual business bottom line (Order Management), you can understand why my first response to Oliver was that this shouldn’t happen and that Apple is better than that.
-
Just because the Preview codec matches the source/output. I have presets for DNxHD workflows, P2 workflows and ProRes workflows.
-
Yeah, so when you’re done go ahead and render (shift + r) your timeline and then when you export check the “Use Previews” box and you’ll get super fast output.
-
Build a custom sequence where the preview codec is DNxHD matching your footage exactly. Then try using Ultra for your keying. It’s very good.
-
You’re very wrong.
-
Right click on the multicam clip in the project been and try Modify/Audio Channels. You should be able to change it there.