Mike Molenda
Forum Replies Created
-
You can send an EDL from Premiere to SpeedGrade, conform that to your original media, grade, render your new graded clips, then reconnect to them in Premiere. Then you can send from Premiere to Encore as normal.
This way you don’t have to render your Premiere sequence out to a DPX image sequence. Saves a lot of disk space and time. And you can render your graded clips from SpeedGrade to the format of your choosing (ProRes, for instance).
This is basically how Color worked with XMLs from Final Cut. Except a lot of that process was automated: the conform in Color and reconnect in FCP were done automagically by the software.
The current SpeedGrade process works a lot more like bringing something into Resolve: load your media, load your EDL, conform said media to said EDL.
I’m still trying to come up with my own efficient PPro-SG roundtrip workflow using EDL. Haven’t set it to work on an actual project yet, so I’m doing this in my free time. The documentation from Adobe doesn’t seem to have been released yet, either. If I’m wrong about this, will someone please point me in the right direction?
-
I’m certainly no expert on this, just managed to successfully get it working with my Apple-supplied 5770. So I make no promises.
I don’t remember there being the “ATI” before the name of the card in the txt file. Like it just says “Radeon HD 6750M” and “Radeon HD 6770M,” and you’d add “Radeon HD 5770” at the end. Or maybe it’s got an “AMD” instead of the “ATI”? Don’t know, don’t have access to my CS6 machine at the moment. I do remember that what I put in matched the formatting of the cards that were already listed there.
Also, you have to be running 10.7 Lion for the OpenCL acceleration to work at all! Regardless of whether you’re on a supported or unsupported card.
That’s about all I can think of. Personally, I probably would have given up at this point, so best of luck to you!
-
[David Cherniack] “Dynamic Linking with PrPro is clearly high on their Todo list.”
I think that right there is the linchpin. Speedgrade needs a niche to fill.
If you’re working exclusively in SD/HD, it’s foolish not to at least have a copy of Resolve Lite installed on your system, if it can support it. And if you regularly work with 2K/4K source material, you’re getting your money’s worth out of a full Resolve setup (or Baselight, or Scratch, depending on the work you’re doing). And the process for getting a PPro sequence into Resolve is remarkably similar to getting it into Speedgrade.
If you only need functional color correction for quick-turnaround workflows, Colorista, Color Finesse, or even the built-in 3-way are going to have you covered. No external CC necessary.
Speedgrade will be most useful when roundtripping a sequence or group of clips is as painless as roundtripping to After Effects. I think that’s its niche, a full-functioning grading suite that integrates seamlessly into the Creative Suite “ecosystem.” And it’s not quite there yet.
Still, it’s probably my favorite addition to the CS6 suite so far. I’m glad Adobe took the route of adding an external grading application. There’s something very “Zen” about locking your picture and jumping into a dedicated grading suite. You’re totally focused on the task at hand, not thinking about whether you still need to trim a few frames off that clip, or if the levels on that music could stand to be brought down a bit.
And you avoid the “drag-drop-copy-paste” operation inherent to internal effect-based color correction. Something that I find speeds up my work quite significantly.
-
00 Sequences
01 Interviews / Sync Clips
02 B-Roll
03 Audio
04 Music
05 Graphics
06 Titles
07 Stills
99 Utility (color mattes and the like)Everything is always in the exact same place when I need it. It’s a beautiful thing. You could even take it a step further and assign an 01 to all video bins, 02 to all audio/music bins, etc, so they are always grouped together.
I’m glad this has become a “thing”. But I’ll settle for more people learning to use bins, period. Lately I’ve had to clean up far too many projects where all the media is just thrown into the top-level Browser bin!
-
I’ve successfully (i.e. nothing has broken so far) enabled OpenCL on my 5770 card, using a trial version of CS6 and OSX 10.7.3 Lion.
I’ve found that the software-only Mercury Playback in CS6 handles H.264 DSLR playback pretty well, when compared to CS5 and 5.5. Minimal latency in playback and scrubbing on the timeline. I also like to set playback to 1/2 resolution if I’m doing a lot of scrubbing, and this speeds things up even more.
So for straight up edits, you may not even need the hack. Especially on a beefy 12-core system (I’m on a 2x dual-core Mac Pro from 2006). Bear in mind that disk speed and RAM come into play here as well, so be sure to take that into account!
If you’re going for the full CS6 suite, you will get more mileage out of an NVidia card, since After Effects and SpeedGrade have additional enhancements for CUDA GPUs (NVidia) that are not available on OpenCL GPUs (ATI).
-
I would test going back and forth between CS5.5 and CS6 first, especially if you are mid-project! I know CS5 and CS5.5 projects are back-and-forth compatible without too many issues, but I’m not sure about CS5.5 and CS6. I’ve managed to open CS5.5 projects in CS6, but I haven’t tried going the other way around.
And remember, you’ve got EDL and XML output options, too, so I don’t think you could get too hopelessly stuck.
And yes, it should be possible to have both versions running on the same drive. If you’ve got an update installer for CS6, supposedly it searches for a previous install of CS5.5 so you don’t have to re-enter the serial number.
Performance reviews have been mixed, it seems like PC users are having an easier time with the upgrade. David Lawrence wrote a Creative Cow article on his first impressions. They seemed pretty positive, and it looks like he was on a Mac. An older MacBook Pro, at that. I haven’t run into much trouble on my Mac, even with my repeated tinkering, but I haven’t put it through any strenuous start-to-finish tests yet.
I think a problem people are running into is that the OpenCL acceleration still needs work, and they are reading that as a step backwards in performance. But the software-only Mercury Engine has definitely improved from CS5.5. And choppy OpenCL performance is a step up from absolutely no OpenCL support whatsoever, in my book.
-
It looks like the video Andrew linked in his original post walks you through it. Just substitute the name of your card for the Radeon 6970M the guy in the video is using.
I did mine through some trial and error. I could do this since I’m on a trial version on an expendable additional OS installation, and wasn’t too worried about screwing things up.
All told, you probably should avoid doing this if you have a paid version installed on your primary drive. But if you want to take the gamble, it’s better to follow the instructions of someone who appears to know what they’re doing than someone like me who basically stumbled through it.
-
It’s always a delight to see editors who number their bins. High fives, all around!
-
They EOLed OnLocation! Adobe doesn’t care about their pro users, they’re just interested in moving copies of Acrobat Reader!
All kidding aside, I started using Premiere CS4/CS5 alongside FCP at my day job about a year ago. Back then, I referred to it as Final Cut’s homely cousin. But then she grew up to be hot! After the FCPX release, I started integrating CS5.5 alongside FCP in freelance work, and now I find myself starting up projects in Premiere far more frequently than in FCP. So the upgrade for me was kind of a no-brainer, and I am eagerly awaiting my discs in the mail.
-
I have also heard that you need to be on Lion (10.7) for the OpenCL enhancements to work. So don’t crack open your machine unless your OS is up to date! I remember the 5770 is kind of a pain to get in and out of the slot.
I primarily use Snow Leopard, but I’m running the CS6 trials on a Lion HD that I have in Bay 2.