Fred Jean
Forum Replies Created
-
Let’s hope then.
I see some really great possibilities with the new version and it could really speed-up the workflow as well as make it more friendly and flexible.
It’s good news, even if the implementation takes time to be really good and we may not have it ideal at first, it’s an open motorway that engineers could improve easily.
Cheers.
Fred.
-
Let’s see if I got it because it seems that these watch folders are going to be a gaz.
Taking a practical example:
– Edit is done in log
– I want to apply a particular CDL and/or LUT corresponding to a serie of scenes that belong to the same color decision.
– All I’d have to do would be group the source footage corresponding to those scene into a Bin via custom metadatas where this CDL would be automatically applied to all the clips thanks to the watch folder
– refresh my timeline
and Bang, all the clips involved with the correct look in the timeline?Because that would mean that someone in Resolve could work independantly the source material at least for primary without the need to bring the sequence into Resolve.
Am I saying something stupid here?
If that is the case, that is what I’d call a flexible and friendly turnarround.
It’s in the idea of custom sift but automatized. I’d tell Avid: aplly this CDL (and not only CDL but any other posible action) to the clips that have this particular metadata.
(thinking here that my sequence has been conformed to the source material)Fred.
-
If we could have the possibilities to create loadable CCs done in Resolve, them apply those custom looks in MC bins, specially with the new watch folder, that would be a great accomplishment because the only thing involved would be a file, a file that can be sent by mail and contains the metadatas, exactly the same system as the RMDs. Looks created independently could be applied to some clips selection in the avid timeline. As resolve can do a lot more than rcx it would be a gaz.
Fred.
-
It would be sad if DS dies. Avid has the platform and IMO strategicaly good they compeat with Autodesk.
The Resolve “dependance” is not a very good news. In the end it’s different interface and not everybody colors in it. I do not for ex but use scratch, even sometimes Nuke, a friend of mine who cut mc uses nucoda etc…
Them, I don’t end to understand how resolve could replace the compositing capabilities of DS. DS Ian’t Nuke but at least a lot can be done before the need of specialized app is requiered.
It’s the wild west for now. My scratch license is old, same as my Nuke’ and I need to wait until the panorama clears up to take purchase decisions.
For us it would be an obligation then to dig into a new learning curve. Now, if they make the roundtrip a breeze, ok.
Fred.
-
Thanks for the precision Michael.
Yes, in the end I could find the 2 hours video and rewatch that part. Great tip to know and All very clear now.
My desire of not being dependant of Resolve is due to the fact that I don’t cc with it as I’m familiar with Assimilate and didn’t want to ad a new learning curve despite Resolve being probably more robust for cc.
IMO, the open nature of the dng is promissing in terms of support.
Fred.
-
Hey…yeah.
I supose that they want to reserve the big artillery for DS. And they know that everybody corrects on the cheap in Resolve anyway.
(except me maybe)But I agree, MC is ridiculously limited on that.
Fred.
-
For the name of the poster, it looks that she is in Pal land.
30p is strange choice.Yes, your Project should be 29.97
Fred.
-
Michael,
About watch folders and actions in AMA, are you thinking about metadatas and/or also transcodings?
Fred.
-
Some very good news here.
Even if the app is still hd, if I can crop some red footage without loosing reso, it’s already a change in the right direction.
Background transc-conso, it was time!
MC and Symphony needed to be merged. Now, it could be that DS will be cheaper, wich would really be logical as Smoke is 1/3 the Price of the previous version and puts DS in an embarassing situation. Avid needs to compeat with Autodesk. (not only with Adobe or
Lightworks)In my case for ex, I am a potential DS
Client as I’m looking for a specific
Workflow only DS can, but I’m
In a wait-and-see attitude because
Smoke is 4000 euros…too big gap
To be ignored.
For small people like me who aren’t
Hollywood, 6000 euros is not nothing.Fred.
-
My thoughts too. I find that the good old slate and manual sync is frankly faster, reliable
and is a breeze in MC.
The less peripherical apps involved, the better. Also, It’s not imposible that you’d have to fine tune again after the PluralEyes stage wich makes the all process somewhere annoying and “unstable”.
There is nothing more simple and reliable as a clapperboard.Fred.