Sandeep Sajeev
Forum Replies Created
-
Charlie,
That’s what I thought as well. So not sure what Bill means. I use X almost exclusively for offline now, and I find that Skimming, Ranges, Keywording and Smart Collections are what make the biggest difference in speed for me.
Not having to patch Audio Tracks is also great, when I sit on Smoke to finish, this drives me up the wall now.
But the actual process of constructing a scene/montage/film is pretty much the same, with some random terminology thrown in.
Sandeep.
-
Bill,
Can you expand on your contention that editing in the event browser is more efficient?
How do you cut together complex scenes with foley, location audio, music etc without going into the timeline?Thanks,
Sandeep. -
And lower your overall contrast.
-
Why not look into Resolve Lite? It’s free and far more powerful than Colorista.
-
The OP has a concern. As a working editor, it is a valid concern. I’m struggling to see anything in his post that is deserving of such a condescending reply.
This forum used to be a relevant resource, when I started putting X through it’s paces I found the discussions on both the merits and drawbacks of the software really helpful. Now it seems like people who post here questioning the slightest thing get flamed.
-
Oh and FCPX timelines conform flawlessly. At-least, I haven’t had any issues on 6 spots.
-
I recently finished a spot in which I had to Paint out a couple of background elements, swap out the sky, turn on a couple of street lights, Denoise and add in a lens flare all on one shot. Usually in situations like this, we just use the shot as-is in the offline, then it gets fixed on the Flame during the online.
But I was able to do all this on my timeline and it’s great for the client to see it happen this early in editorial. This is where Smoke becomes more than just the sum of its feature set…it really extends the dialog between the editor and the agency creatives in a tangible, meaningful way. Especially when dealing with younger inexperienced agency creatives who are still learning the ropes – it cuts out the whole, “you’ll see it on the online” runaround.
Of course Smoke has always done this, and it’s probably accurate to say that it has done it better and faster in earlier iterations, but that’s a whole different argument I guess. As someone who couldn’t figure out how to get material into the system in the 2012 trial, I’m glad that this sort of thing has been made friendlier.
-
Jamie,
Smoke 2013 does offer support for Red Rocket. As well as ProRes, as I mentioned earlier. But it has nowhere near the speed of the Linux boxes.
Sandeep.
-
Lol.
All the stuff that’s missing in 2013 is in Flame. They probably just need to activate the code for it to show up in Smoke, but it’s unlikely to happen – especially if 2013 sells well.
Is Flame selling for 40k these days? Remember when it was close to a million, all told?
I love love the Flame, but we don’t do enough business for it to be anywhere on the horizon as a purchase.
Sandeep.
-
I’ve been using it since the first Pre-Release. Will definitely pick up a license. At this price point (even without the discount) it’s a no-brainer.
Things I love: Paint, Tracking, Stabilization, CFX and Action on one machine. Having all of this accessible without having to switch away from my timeline in the offline process is very satisfying.
Things I dislike: having to render constantly, and the fact that you don’t have playback while rendering. This can be a killer if you’ve got a client in the room, especially one who is accustomed to the speed of the FFI boxes.
Things I can’t fathom: the lack of the following- 3D tracker, Particles, Projections.
It’s no longer as fast as the Linux boxes, but the feature set is tremendous. It requires a lot of time to get really proficient with CFX and Action, despite how simple things appear in the demos – if you want to be able to give clients everything they want, it’ll take a few months of dedicated effort to reach that point. I’ve seen it mentioned somewhere that all it takes is a couple of days to get up to speed with Batch (CFX) and Action – but this is simply not true.
So in my opinion, if you’re willing to put in the time, accept the holes in it’s feature set, and adapt some of your existing workflows, then Smoke is a good addition to an editors skillset.
Oh and unlike the Flame box (mentioned by James) it deals very well with ProRes – infact you can set your Intermediates to various flavours of ProRes if you don’t need to work in DPX…
Sandeep.