Simon Ubsdell
6
COW Coins
Forum Replies Created
-
[Bret Williams] “It’s such a problem that LenoFX, MotionMasterTemplates, and also I think Stupid Raisins have videos on it to refer their customers to when”
One of the reasons we have studiously avoided releasing products based around drop zones except where the overwhelming likelihood is that the user will be loading a still rather than live action.
It’s not fair to inflict a broken system on your users …
Simon Ubsdell
tokyo productions
hawaiki -
[Bret Williams] “You didn’t even touch on the worst of it.”
Agreed.
It’s always been hopelessly bust since the very first iteration.
I keep coming back to it, year after after, thinking that surely, surely, surely by now they will have done something about it. But there are only so many man hours I am prepared to waste on trying to figure out what the problems might be this time around …
Because of course they are only to happy to change the way it works without actually documenting what they’ve done – always bearing in mind that they never actually fix it, only mess it with further.
It’s an absolute disgrace. And in the video I was being as polite as I could for a wider audience.
Simon Ubsdell
tokyo productions
hawaiki -
[Jeremy Garchow] “I don’t have hard evidence for this, it is just a hunch.”
It’s a good theory certainly.
However, to be pedantic, I don’t think it’s right to say that FCP X uses frames (or samples) to count with, at least not directly. Instead it uses seconds and fractions of seconds based on the timebase of the sequence.
Thus the duration of a clip that’s 37 frames long in a 25p sequence is expressed as: 3700/2500s. A clip that’s 45 frames long in a 30p timeline is expressed as 22500/15000s. And so on.
<asset-clip name="DZ Counter" offset="4s" ref="r2" duration="3700/2500s" tcFormat="NDF"/>Simon Ubsdell
tokyo productions
hawaiki -
[Oliver Peters] “However, I have seen this “less than 1 frame” timeline issue on and off with stills in FCPX since the very beginning.”
“Beware the zero length gap!”
https://forums.creativecow.net/readpost/344/2772
A post from seven years ago …
Simon Ubsdell
tokyo productions
hawaiki -
[Oliver Peters] “This gap issue of less than a frame has been with FCPX on and off since the beginning.”
See also my thread above.
https://forums.creativecow.net/readpost/335/101270
It’s my (unverified) feeling that timeline timing has been a weak point of the FCP X model since the beginning, showing up in a number of different issues.
Simon Ubsdell
tokyo productions
hawaiki -
[Jeremy Garchow] “This guy sounds like any mechanic.
My good buddy’s dad was a mechanic for nearly his entire life. Every single car, no matter the make, model, price, luxury, or practicality was a “shitbox”. Every. Car. “
Exactly.
I love all guys like this. I love their passion and their frustration and their perfectionism.
We don’t have to take everything they say as the definitive answer to the big picture, but it enriches us to listen to them once in a while.
Simon Ubsdell
tokyo productions
hawaiki -
[Bob Zelin] “Louis Rossmann is possibly the best Apple tech in the United States. He has all the facilities to repair Apple products at component level – to the dismay of Apple.”
For those of you who don’t have the time to watch the full video, here’s Louis’ list of talking points:
1:01 – A1226/A1260 2007-2008 Macbook GPU failures, warranty service refusal
2:21 – A1226/A1260 2007-2008 Macbook Pro hinge/frame problem
3:16 – A1286 Macbook Pro – the “Unibody” myth, glued together pieces fall apart
4:58 – A1286/A1297 MCP power circuit failure due to poor buck converter design: C7771 issue
6:01 – iPhone 4 cellular placement fail
7:12 – iPhone 5 power button problem
7:27 – A1286 2010 Macbook Pro GPU kernel panics due to same buck converter defect from 2008/2009(this gives you a hint that apple engineers doesn’t give a **** about engineering good products, same design flaw for three straight years)
10:04 – A1286 2011 Macbook Pro GPU failure, Apple gets sued over not addressing problem.
11:43 – Apple gives out badly refurbished boards as warranty replacements for 2011 GPU failures.
13:06 – 2012 Retina Macbook Pro: another motherboard issue (U8900), due to poor soldering/manufacturing method on the GPU buck converter.
14:46 – Mac Pro GPU failure (again).
16:27 – iPhone 6/6+ touchscreen issue due to structural issue.
18:23 – SSD soldered straight into the motherboard+ chip that would kill the macbook, because a power line would short out to ground when the chip dies.
20:18 – 2016 Macbook keyboard reliability issue.
21:52 – 2016 Macbook Battery failure issue.
22:50 – A1278 Macbook Pro SATA cable failures(yes, really).
Simon Ubsdell
tokyo productions
hawaiki -
You might find this Motion tutorial using on creating volumetric fog:
Simon Ubsdell
tokyo productions
hawaikiSome contents or functionalities here are not available due to your cookie preferences!This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.
-
[Bill Davis] “If Apple isn’t serving their customers in a way that meets those customers needs, another vendor will inevitably come along and out-compete them. “
So your argument seems to be that unless the market reins you in from producing shoddy goods, you should just go right ahead and keep on doing it.
It might be good business practice (and then again it might not) but it’s hardly admirable.
I thought you wanted us to admire Apple not hold them in contempt?
Simon Ubsdell
tokyo productions
hawaiki -
[Ronny Courtens] “As I said, really nothing special.”
I think you’re rather glossing over the detail of the case that Louis makes.
All hardware fails, but that’s not the point.
His contention, backed up with concrete examples, is that Apple hardware has failed specifically because of poor decisions in the components used and the methods of construction.
He goes on to argue that Apple have failed to address the specific issues involved and allowed the consequences of those poor decisions to persist for several years.
He argues that Apple’s warranty schemes are very unhelpful in terms of addressing these problems.
He contends that Apple have implemented seriously poor decisions in their “solutions” to the specific hardware failures.
He claims that Apple have had to face litigation before they do the right thing and fix these problems.
His view is that Apple have the resources to “do better” and that customers can reasonably expect that of them.
He makes the point that Apple charge premium prices for what are meant to be “premium products” while not adhering to the sort of quality manufacturing standards that justify that positioning.
(Specifically the “unibody” that was never a unibody but two badly glued sections is an egregious example where Apple tried to market something that they hadn’t in fact built and which was destined to failure from the design stage.)
His argument ultimately is that Apple are knowingly short-changing their customers and as someone who sees the consequences of that on a daily basis he is understandably angry about it on their behalf.
He may be right and he may be wrong but to dismiss his case with a wave of the hand would be unfair given the level of detail that he adduces.
Simon Ubsdell
tokyo productions
hawaiki