-
Photoshop CS6 Beta released, with magnetic timeline!
-
[David Lawrence] “There are thousands of reasons why an editor might want to export a range as new asset. That’s all we’re talking about. Save a new piece of media. The idea that it’s “removed from further revision and refinement” is a completely meaningless statement.”
To your first line, yes there are. And you can do that within X. The process is different, but every bit as easy. Remember, it’s all metadata. So duping a Project is just copying metadata code. No media or anything large and unwieldy. So what’s the problem?
I don’t imagine you have a problem copying a resume or script to make revisions. So why the reluctance to copy the pointers represented by a project?
[David Lawrence] “Bill, with all due respect, you’re way over thinking this. Range export is a very very simple production need. It has nothing to with delivery or distribution.”
Maybe. But maybe not.
If you can’t see how you can do the same thing in a new way that’s actually no more complex than the old way – then there’s probably little I can do to convince you.
But remember this when you see a menu without “save as” and similarly can’t understand why not cutting a document off from it’s revision stream in a world moving toward cloud based storage might be a change in thinking worth considering.
Versioning in document creation is real and is being coded into al sorts of modern software. And it requires us to adjust our thinking.
Perhaps you’ll never want those particular benefits. But I can see the usefulness. So I want it.
And if the trivial process of learning to “duplicate” rather than “save as” is the price in document management, I’m fine with it.
Similarly if Duplicate Project gets me the same result as “range export” and keeps, as a simple example, my access to change and undo available in both versions – (impossible in Legacy’s export) then that’s something I might find useful even if you don’t.
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
[Joseph W. Bourke] “I think you have it backwards, Daniel – the executives that are out of touch seem to be at Apple. Check out labs.adobe.com some time – they listen to their users, and they actually give us what they’re working on to see whether it works. With Adobe, it’s Design, Test, Ship – with Apple it’s Design, Ship, Test.
“Yeah.
I guess the Apple model of executive behaviors is so rife with fundamentally flawed thinking it’s no wonder they can’t make any significant progress against their competitors.
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
[Jim Giberti] “OK Joseph, you’ve inspired my analogy of the day.
I wasn’t looking for a new girlfriend, just the opposite, I was really happy with the way things were going – especially knowing that we were always working to make a better relationship.
Then I woke up one day and she dressed and acted completely different than she had in our ten year relationship…just so she could sleep with all the young guys with Macbooks. To make things worse, she tried to convince me that this change was best for both of us.
So here’s this cute Adobe. I’ve known her since I was a kid (I produced some of the earliest non-linear projects on PP1.0), but I’ve never thought of her “in that way”.
She may not be as sexy or fully compatible as my honey Seven was, but she’s so faithful, and she cares about me and listens to me, I’ll never have to worry about her dumping me for the young guy with the tight pants and tats.
In the movies, I always end up with Adobe.
“Yeah, yeah, (; ) the “wise intergenerational advice from the grizzled sage” gambit. But it’s been done to death.
Even in the same mode, here’s an equally resonant alternative…
Girlfriend? Marriages?
You’re not even six months old!
As I see you sleeping in your crib ready for the next day of adventures, here’s what I want to let you know as you grow and mature.
Never be afraid to dream. There will be a time, later in your life when the mortgage, braces for the kids, and a week in a theme part will likely all be a part of a perfectly satisfying life for you.
But you’re not there yet.
You’re young. This is your time to dream big.
Maybe you’ll never live up to your dreams. And that’s OK. But you don’t want to look back some day and regret that when you were young and had the chance, all you could imagine was to have a little bit better version of the lives your mom and dad lived.
Now there’s nothing wrong with that. And I’d be very proud if you decided to follow a path like that. But while every parent thinks their kids are special – I really do see in you a capacity for amazing things that I just didn’t have when I was your age.
Your times are different than mine. Your choices broader. You live in a new, more connected world where information, mobility, and social connections are different than they were back in my day.
So there will be new opportunities that your mom and I never imagined.
So I think for you, the best advice is to go out – at least for a while – and take some chances. While you’re young. Before it’s too late.
At the right point in time, I hope you stay up too damn late. Even all night if you’re having a great time. Go places you’ve never been. Talk to people from different places, different worlds, different thinking. Test what you think you know – and even what your mom and I have taught you about the traditions of life – against what you see in the real world.
Maybe you won’t do anything that’s much different than what we did.
But maybe you will.
And maybe if you don’t constrain your thinking to the way it’s always been done – maybe, just maybe – you’ll change the world a little bit for the better.”
“Before speaking out ask yourself whether your words are true, whether they are respectful and whether they are needed in our civil discussions.”-Justice O’Connor
-
[Bill Davis] “To your first line, yes there are. And you can do that within X. The process is different, but every bit as easy. Remember, it’s all metadata. So duping a Project is just copying metadata code. No media or anything large and unwieldy. So what’s the problem?”
The problem is when you duplicate a project (I assume you’re talking about command-D, if there’s another way please let me know) you’re making a copy of the entire project database. The duplicate CurrentVersion.fcpproject is the exact same size as the source. It’s not metadata at all. It’s a full copy of the entire project database and everything it contains.
If a project is 10MB, the duplicate CurrentVersion.fcpproject is 10MB. If your project bloats to 10GB, your duplicate project will be 10GB.
All to export a 5-second asset that might be thrown away after one quick viewing? I’m sorry, being forced to duplicate the entire project database isn’t “different” or “every bit as easy”. It’s mind numbingly stupid.
[Bill Davis] “I don’t imagine you have a problem copying a resume or script to make revisions. So why the reluctance to copy the pointers represented by a project?”
They’re not “just pointers”, Bill. You’re copying the entire database structure and content. It’s a bit more complex then you seem to realize. On top of that, FCPX’s database handling is currently a mess and seems to corrupt if you look at it the wrong way. Given the fragility of 10.0.3, the workflow you suggest sounds like an invitation for trouble.
[Bill Davis] “If you can’t see how you can do the same thing in a new way that’s actually no more complex than the old way – then there’s probably little I can do to convince you.”
The reason you can’t convince me is because you can’t do the same thing. In FCP7, mark in and out on the timeline, then export (in whatever format you want) from the file menu. Done. In FCPX, duplicate the entire project database (no matter how big, maybe it’s in the GBs), then open the duplicate, then trim the duplicate, then “share”. This is NOT the same thing. It’s a bunch of extra work and a bunch of extra file overhead.
[Bill Davis] “Versioning in document creation is real and is being coded into al sorts of modern software. And it requires us to adjust our thinking.
Perhaps you’ll never want those particular benefits. But I can see the usefulness. So I want it.”
You’re making a false assumption about why one might export a range. I’m not talking about versioning. I’m talking about saving an asset. Different intent. Different use. Maybe it’s a one-off that will be used and thrown away. Who knows? I export ranges all the time. Being forced to duplicate the entire project database just to spit out an asset is stupid and wasteful.
[Bill Davis] “Similarly if Duplicate Project gets me the same result as “range export” and keeps, as a simple example, my access to change and undo available in both versions – (impossible in Legacy’s export) then that’s something I might find useful even if you don’t.”
Glad you like it, hope you never have an experience like Jim Giberti’s. I don’t see value. All I see is extra work, a bloated project library, and risk of corruption. All because Apple forgot one the most basic features an NLE can have.
It’s a flaw. It has nothing to do with The Cloud, versioning, or anything else. It’s an easily fixable flaw. Apple just needs to fix it.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl -
David, there is a much easier way, I must say though, No range export is simply stupid, I fully expect it will be added in soon.
My workaround is to leave an empty “Scratch Project” on my drive and cut and paste the section I want to export to that. I then delete the section when I’m done, it’s very easy to do and it doesn’t take up any space, but it’s still a step that could be easily avoided with a simple command.
Steve Connor
“FCPX Professional”
Adrenalin Television -
[Steve Connor] “David, there is a much easier way, I must say though, No range export is simply stupid, I fully expect it will be added in soon. “
Thank you Steve, that’s all I’m trying to say.
[Steve Connor] “My workaround is to leave an empty “Scratch Project” on my drive and cut and paste the section I want to export to that. I then delete the section when I’m done, it’s very easy to do and it doesn’t take up any space, but it’s still a step that could be easily avoided with a simple command.”
This is a much smarter workaround. Hopefully, you won’t need it soon.
_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl
Reply to this Discussion! Login or Sign Up