David Lawrence
2
COW Coins
Forum Replies Created
-
[Jeremy Garchow] “I will gladly take a higher res iPhone camera as many times it’s the only cam I have with me. “
So true that the best camera is the one you have with you at the time. Here’s a couple articles from the New York Times that speaks to that. In this case, award winning war photos shot with an iPhone. Their candidness only possible because the soldiers were comfortable being photographed with a camera phone:
https://lens.blogs.nytimes.com/2010/11/21/finding-the-right-tool-to-tell-a-war-story/?ref=asia
https://lens.blogs.nytimes.com/2011/02/11/through-my-eye-not-hipstamatics/
I won’t complain when my iPhone shoots 1080p video but I wouldn’t expect to use it as a substitute for a real camera on a job. It’s about appropriateness to the job at hand. I think we all agree on that.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Bill Davis] “From the un-retouched stills Apple posted today and the exemplar video shown at the same time- it’s clear you cannot do with the iPhone 4s what a person can accomplish with a six figure video configuration and a crew of 10. Further, having some enhanced video capabilities like better image resolution, better lens performance in low light, and iOS 5’s faster “in the moment” camera access capabilities are all nice, but I guess Herb is correct, they don’t really make the iPhone a mini Thompson Viper for $299, now do they? “
LOL, no you’re absolutely right, Bill. Apple’s obviously given us 4K videography in our pocket for as low as $199. I guess Jim Jannard should just throw in the towel. 😉
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Chris Kenny] “Err… these are absolutely implementation details. Neither of these behaviors is in any way required by the process of editing in the abstract.”
Chris, the problem with that argument is that the process of editing never happens in the abstract. Editors work in the real world. Lots ideas are fantastic in the abstract, but quickly hit a wall in actual use. FCPX is filled with them. Implementation reflects design intention.
[Chris Kenny] “I imagine the debate is over whether to allow the main timecode viewer to be switched to show source timecode, something that would be useful, but potentially confusing, thus the debate.”
Confusing to whom? This is supposed to be professional software for professional editors. I think we can handle it. Just sayin’ 😉
[Chris Kenny] “As far as persistent in/out points, I suspect the ‘con’ argument is that explicitly marking favorites is better practice and not very hard to adapt to.”
In/Out points and favorites have different uses in a typical editorial workflow. I think of favorites as virtual sub-clips. In/Out marks are something entirely different. The hypothetical ‘con’ argument just doesn’t make sense. As far as In/Out marks go, it’s a no-brainer. I expect we’ll see them an update eventually.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Walter Soyka] “I’m trying to think a little more like Jeremy here — not what we’re doing now, but what we could do if we were going to eliminate prior assumptions about how an NLE should work (although when cutting film, only showing unused footage on the source side is the default).”
I’m with both of you on this, but also I think they serve different purposes — ranges behaving like sub-clips, while In/Out points indicating a specific range I’m only interested in right now. Maybe because this is a section I want to cut into my sequence or a section of my timeline I want to export as a discreet file (something I do constantly).
Conceptually, it’s like the difference between global and local. Why not simply allow for both? I see no reason why global metadata ranges and local In/Out points couldn’t happily co-exist.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Jeremy Garchow] “[Walter Soyka] “But what about a project that uses multiple ranges within the same clip? ”
How would you have that? You can’t have more than one selected range on a clip. It would just store the last range, just like FCP7.”
Walter, by range are you referring to multiple tagged regions?
I agree with Jeremy — why not have a special flavor or metadata for In/Out that persists in the UI until it’s redefined by the user?
The other thing that really bugs me in the browser is the way that if you click anywhere inside a selected range, the time indicator sticks, allowing you to set an In/Out point, but if you click anywhere outside the range, it selects the entire clip. That’s just sloppy. Command-A for “select all” makes much more sense as an explicit expression of user intent and has been the Mac OS standard since 1984.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Jeremy Garchow] “Well, isn’t it just that simple? The project uses it, the in/out gets cached to that project? Every project already has event references.
New project, new cache?”
Exactly. Seems like caching at a project level would be the way to go. Unless event references are stored at the event level?
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Jeremy Garchow] “That’s weird. Using almost any tool but the selection tool displays source tc. Wonder what they are still debating?”
Weird is right. But the one that really gets me is persistent In and Outs. I mean seriously, what on earth is there to debate???
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Steve Connor] “Yes I have and I’m still interested in exactly what constraints are making the process inefficient, is it the lack of tracks? is it connected clips?”
Fair question, Steve. Some of the constraints have to do with issues Aindreas raised in his example regarding the fixed screen layout and wanting more flexibility with how bins and multiple sequences can be arranged. Others have to do with the nature of the timeline itself. I’ll explain in more detail when I answer Jeremy.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Jeremy Garchow] “Supposedly soon.
Or here:
https://forums.creativecow.net/readpost/335/602“
lol! How did I miss that thread?
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Chris Kenny] “People keep accusing Apple of not understanding what editors do.”
According to Larry Jordan: “Retaining In and Out points for clips in the Event Browser is undergoing a debate in Apple. So is the ability to read source timecode for clips in the Timeline.”
If the geniuses in Cupertino really are debating persistent In and Out points and reading source timecode, I think the case of Apple of not understanding what editors do makes itself.
[Chris Kenny] “Some critics have confused the mechanics of how these tasks are performed in current NLEs with the tasks themselves.”
Let’s say there’s a bathtub filled with water in front of us. Our task is to empty the bathtub with the tools we’ve been given. I get to use a five-gallon bucket. You get to use a spoon. Same task, different mechanics. One of us is gonna be a lot more efficient than the other. Task and mechanics are intrinsically related when it comes to efficiency. That’s what UI design is all about.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl