David Lawrence
2
COW Coins
Forum Replies Created
-
Well said, Walter and Michael.
Happy Thanksgiving and best wishes to all this holiday season!
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Andy Neil] “Please. If that were called ‘editing’, then I wouldn’t have to clean up 70 percent of the sequences I get handed on a weekly basis. :-)”
LOL, sounds like you need to find better assistants! 😉
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Andy Neil] “Of course you are forgetting to calculate all the cumulative time you spent placing SFX and music and other audio elements on dedicated tracks and rearranging them”
You mean the part called “editing”? 😉
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Jeremy Garchow] “You need another B A, and then hit “start”!”
Oh yeah, forgot! Good catch!
[Jeremy Garchow] “While FCP7 may provide more than one way to work and has certain flexibilities, there’s still methods we have to employ and “rules” to follow and learn.”
Agreed, but there’s a huge difference in the kind of rules found in an open system like FCP Legacy and the kind of rules that the designers chose for FCPX.
I was writing a third article comparing the rules between the two systems but I never published it because the main points of that piece needed to be broken into smaller chunks and those workflow conversations you and I were getting into last month covered them in much better detail.
In regard to the rules themselves, this statement from Michael says it well:
[Michael Gissing] “If experienced editors need to learn it, that suggests it isn’t simple or intuitive.”
I believe the reason for this is has to do with the nature of the rules in FCPX. Even if you ignore the current bugs and inconsistencies, it’s clear that the rules the designers chose for FCPX are primarily drawn from a data model. While this may be elegant from an engineering standpoint, from a usability standpoint it often falls flat.
In FCP Legacy, there are many rules too, but at least you never had to consider an object container model when making a dissolve.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Craig Seeman] “There’s some irony in that. Given that nobody has been using FCPX for more than a few months, there’s a whole slew of workflows that people may be overlooking and therefore calling the program inadequate.”
I hear if you type:
↑ ↑ ↓ ↓ ← → ← → B A
you get tracks.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Chris Harlan] “Not quite true. It’s Black. And, frankly, the fact that I didn’t have to generate slug every time I wanted black was a godsend. It was always fun to watch someone coming from MC to FCP as they were just starting out, generating slug after slug to be used for black. I, personally, was thrilled to have a timeline smart enough to hold your place in time and auto-generate black.”
Amen!!!
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Bill Davis] “When it’s nothing – nothing is possible except that it sits there. “
Another way to look at it is if it’s nothing, I don’t have to think about it. One less thing to deal with.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Bill Davis] “Clearly Apple believes that there are more people who will eventually understand and appreciate “their way” via FCP-X than there are in the class of customers whom they will lose due to the change.
And so far, history has shown their thinking to be right much more than wrong.”
In the consumer space, absolutely true. In the enterprise/professional space, not much.
The big irony of course is that if they had followed the path suggested by DRW, not only would they have likely regained industry leadership in the existing pro market, they would have set the stage to transition with that leadership intact. Instead, because of the botched nature of this release, they’ve not only dumped ten years of code legacy, they’ve also dumped ten years of earned trust and respect in the professional/ enterprise-class market. It will be very difficult for them to regain that trust.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
[Craig Seeman] “Of course they could have started from scratch but worked to maintain a “traditional” NLE interface. This though, was a design decision.”
In fact that’s exactly what they did. The evidence is in the program itself:
My hunch is the design decision to scrap legacy UI/compatibility was driven primarily by marketing and finance and that the fork happened around the time the mass firing of the Pro Apps team was announced in the press.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
WE GOT THAT B-ROLL!!!
https://www.youtube.com/watch?v=SItFvB0Upb8
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhlSome 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.