Michael Phillips
1
COW Coin
Forum Replies Created
-
Once you lose your spot, it’s very hard to get back. Grass Valley is not going to give it up unless they feel they have a better spot elsewhere.
Michael
-
The answer is the same… no settings to change the way dates are stord and displayed other than what you see.
Michael
-
Imported LUTs are stored in the project folder in which the LUT was imported. Removing LUTs from a project is done by deleting them from this folder on a per project basis. There is currently no UI to differentiate LUTs intended for all projects versus LUTs that are project specific. Currently importing a LUT will be for the project in which it was imported.
There is, however, a workaround for this which is done by manually copying the contents of the LUTs folder, found in the project folder to:
• OS X: Library/Application Support/Avid/ColorManagement/LUTs folder
• Windows: /ProgramData/Avid/ColorManagement/LUTs folderYou will need to copy the LUT as well as the XML file of the same name.
Now your LUTs will show up in any new or existing project.Michael
-
Go to properties in MoviPlayer, and change display from portrait to landscape and save. AMA link, then apply a DVE to make it portrait again.
Michael
-
But I agree with you that overall it was a copy of other editors and not a fully implemented direct interaction trim tool. The basic fact that Media Composer does not have a notion of “selection” makes a lot of the interaction design difficult and unpleasing from a user perspective.
Michael
-
Then you have a short memory. The complaining was for versions 6.0 through the next two dot releases that fixed SmartTool to not turn itself on when unexpected. When it first came out, turning it off did not keep it off and activated itself again after coming out of a trim mode causing havoc on the next click in the timeline. The “loud feedback” got SmartTool to be what it is now. But all of that could have been avoided with an implementation that:
1. Was defaulted active for new users.
2. Allow users who did not want it to not only turn it off and keep it off, but not have it in the UI.This would have allowed the cranky editors to discover new trimming interactions on their own time and not in the heat of the moment when it may or may not work for their needs. Make it a user setting. And having it on for first time users would let them have expectations closer in line with other editing paradigms.
Michael
-
And I would add that old time, film editors would have no issue with a well designed, high performing UI design and interaction provided it did not interrupt the creative process. Storytelling is across many layers, versions, and screens. If you’ve ever seen a timeline from The Hobbit, or the project/bin management of a single project having over 5000 bins, that is the bar for performance expectation. They would welcome new approaches and version management of editorial.
For example, SmartTools got a lot of kickback because it did interrupt that process and with a bit more clever design could have pleased both old cranky editors as well as all those “FCP” style editors who like to work differently. There were a lot of “design choices” in v6 that changed things not for the better but in some cases worse and many were just a wash adding no additional value other than a different look.
Michael
-
That’s what we’re all here for, learning by our mistakes!
Michael
-
Have you tried with AMA linking and looking at the histogram to see if it matches up to anything you see in AE?
Michael
-
If importing, are you importing with RGB setting or 601/709? If too hot, I suspect 709. Importing with RGB will scaled full range to video levels.
If you use AMA rather than import, in v7 you can go to source settings and do the same thing on the fly and will play in real time. Or apply a LUT if needed.
Michael