Personal View site logo
Make sure to join PV on Telegram or Facebook! Perfect to keep up with community on your smartphone.
Please, support PV!
It allows to keep PV going, with more focus towards AI, but keeping be one of the few truly independent places.
SpeedGrade
  • 95 Replies sorted by
  • I trying Speedgrade right now. Has anyone used the Macbeth Color checker feature that is built in? I'm thinking it would be nice to use it to create color matching profiles for the GH2 to use with other cams, like the Canon models.

  • Well, having a spent a day with it, the program is good but buggy and does not integrate with Premiere. If they fix a few things, it will be a "wow" item. Lots of BSODs :) You basically have to render out lossless to SG, then re-import the footage and add titles, etc. So if you want to tweak a fade, forget it. Also, you can't import MP4 or mts files. Hello? But the grading is very nice.

  • Any advantage over DaVinci Resolve?

  • "Any advantage over DaVinci Resolve?" that´s what I would like to know too.. any colorists here who use both resolve and speedgrade?

  • @DrDave I had a go with Speedgrade for a recent music project. Nice (particularly for creating masks to track grading onto objects in a scene) but wow, you need a lot of storage for stuff going in and stuff it spits out afterwards. And yes, for mixes I've had to do separate graded sections to cover both "ends" so I have an overlap of graded material.

    I love the multiple-play-head feature so you can compare two (or more) parts of the timeline side by side. Very useful. While SG is quick to use, I find the total workflow of NLE - SG - NLE a bit clunky and inflexible and very heavy on storage.

    Because of this I decided for my recent project to go back to using my NLE's basic colour correction. Of course ideally I should have left the grading until the edit was finalised but that didn't quite work out in this particular project.

  • Thanks Mark--I tried a small test project and ran into all sorts of problems. The main issue was that exporting a project to DPX files (which, as you say, were ginormous) created tiny little cross fade patches between clips that had to be independently graded or the graded clip would "jump" when it hit the CF area. Did you find a way of dealing with this problem? I guess if there was a way to use Cineform files instead of DPX files that would be a possibility.

  • Cineform files works fine.

  • @DrDave I'm using Vegas pro 11 but since the integration is probably just about as nonexistent as it is for any other NLE, I'm sure my experience will be similar to using Speedgrade with any other editing software.

    I tried using it on a series of six videos for a project about young children working with orchestral players because I wanted to make footage captured in difficult conditions, look as good as possible. The camera skills for this sort of observational footage are quite different from normal - they require a knowledge of which aspects of children's development you want to shot, and also of course there are child protection issues. The camera person used Canon XHA1 cameras because she had used them before, and I was happy to lend them the XHA1 and not my GH2. To make a story out of this (shot in quite difficult circumstances in a room full of toddlers and babies) each resulting video had a largish number of quite complex edits, which are a mix of split audio / video edits as well as non-sync sound and sync sound from an H4n and from an on-camera Sennheiser gun mic. The finished videos were between 1 minute and 4 minutes in length, and some of them also incorporated some SD footage which was captured by the client along with HD (ish) footage from an XHA1 camcorder. So a bit of a potpourri - and then it all has to be vetted by the client and by an academic expert in child's musical play.

    Having chosen, synced and then edited the footage in Vegas, for cases where it was just cuts, I then exported my edited timeline to DNxHD. Imported that into Speedgrade, ran scene detection and did the grading, then exported the graded version, again in DNxHD, and put that back into Vegas to add final titles and fades at the beginning and end of the entire piece.

    For cases where there were crossfades, it was a bit more complex because I was worried about the footage getting out of sync as well as about the issue you mentioned at the CF region. So to make it easy, at each crossfade I moved that clip up one track in the Vegas timeline so I had an overlap of a few seconds between the outgoing and incoming video. At each subsequent crossfade I did the same, so ending up with a chequerboard of two tracks. Then I essentially exported two video-only timelines of identical length, one for each of the two tracks. Of course there were lots of "holes" in each one. I put these two one after the other on the SG timeline so I could compare all the grades I applied (copying and pasting those which were similar). Then I exported them as two separate files and put them onto two new tracks in Vegas, synced them up with the original material (as they were two complete timelines, I just needed to sync each one once) then cut them up so they replicated the original edit and reconstruced the crossfades (except of course now they were all the graded versions). I'm hugely hoping that someone on here will point out a much better, more automated way of doing this but the sound edit was so complex I really didn't want to run into sync problems and this was a simple way of avoiding that happening.

    Although I liked using Speedgrade, it was quite easy to lose track of this project and going back and altering something could have been easier if I'd known my way around Speedgrade a bit more. I am a ColorGHear member but as I'm not very familiar with AE and because Speedgrade seems pretty intuitive, I thought I'd use that on this project. It was worth it as a learning experience, but probably for this project it absorbed far too many hours of extra playing around given I was only being paid for 2 days editing. With better integration into the editing workflow it would be amazing - and Speedy!

  • Whoa--that is very clever. So you had overlaps of known lengths on different tracks, and as long as the final CF is shorter than the overlap, you are OK. Also, the program will not render the CFs since the file "stops" before the gap. Man, that is a lot of extra work--plus double the file size--but I will try that if all else fails. Reminds me of when we used to line up two pieces of audio tape and then cut the crossfade.

  • Speedgrade definitely lives up to its name, as a very fast method of grading. My only gripe is that it's not as tightly integrated with Premiere as I would like. Surprised that they didn't include in Dynamic Link support, with per-clip grading. Until they add support for Dynamic Link, I'm sticking to Magic Bullet.

  • They just didn't have enough time to fully integrate it for CS6

  • @DrDave Yes, that's it exactly. You don't have to render two complete tracks back out of Speedgrade and break it back up into clips once back in the NLE, but if you do then everything is back where it belongs. And yes if you allow as much overlap as possible in your graded files, you have flexibility of CF duration when reconstructing the crossfades in your NLE.

    You are absolutely right - it's how you did audio and video mixes back in the days of tape: crossfading two replay sources into the record machine, and that's what gave me the idea.

  • I know this is an old thread, but I recently installed CS6 and finally had a hands-on session with SpeedGrade. All I can say is I'm absolutely appalled at Adobe's decision to shoehorn this atrocity into CS6 so prematurely. SpeedGrade is not only incapable of working with H.264 streams (regardless of the file wrapper), it is completely disintegrated with Premiere Pro. Unlike the synergy between Premiere and After Effects, there is no Dynamic Link support built into SpeedGrade, it operates entirely within its own idiosyncratic world, alien to both Windows and Mac users alike.

    As @DrDave pointed out above, when you hit the Send to Adobe SpeedGrade command, Premiere has to first transcode your entire Sequence into a massive collection of DPX file folders. Each folder contains a separate 8MB DPX file for each frame in your timeline. Not only is this intolerably time consuming and unwieldy, it forces you to use SpeedGrade for the final render of your video. And if you need to make any edits after SpeedGrading your footage? Yep, you get to transcode your entire timeline all over again for yet another SpeedGrade session.

    As if that wasn't bad enough, it's painfully obvious that no real effort has been made to adopt common Adobe user interface standards into SpeedGrade. If you think Premiere and After Effects have cluttered interfaces, you'll really want to take a deep breath before tackling SpeedGrade. Since it doesn't even provide a menu bar, you'll need to memorize a number of keyboard commands just to navigate around its screen windows. And if you don't have a second monitor, I'd sincerely advise you not to waste your time.

    While I'm sure there are good reasons why Adobe couldn't do a better job on SpeedGrade in the short time since they acquired it, I think that's an awfully lame excuse. Adobe should have learned a serious lesson from the recent fallout over the poor integration and lack of control surface support of Audition's introduction to CS5.5. Now that Adobe is selling CS6 by monthly subscription via their Creative Cloud, I don't see any justifiable reason for releasing products before they're ready for prime time.

    In short, there is nothing "speedy" about Adobe's current SpeedGrade workflow. Thank goodness they didn't drop Color Finesse from After Effects, I would've reverted immediately back to CS5.5.

  • Gosh, @LPowell, that sounds more clunky than using Speedgrade as a stand-alone application (as I do, with Sony Vegas). Since I've started using the Canopus HQX codec, moving files seems to work well between AE / Vegas / Speedgrade. The DPX thing sounds like a bit of a nightmare, not to mention being a resource hog. It's still a pain incorporating Speedgrade into my workflow - my preferred way is to grade the overlapping sections then do mixes in Vegas but it's not ideal. The things I like about Speedgrade are the multiple play heads (for comparing adjacent shots) and the tracking masks.

    I've only recently started using AE (5.5) so haven't really explored what's on offer but Color Finesse looks really good - had a play yesterday and it's quite nice to go back to using curves.

  • @LPowell & @Mark_the_Harp

    Definitely agree with your criticisms and worries about Speedgrade. However, I look at it as more of a Beta program than anything else. Sadly it's a beta release that people have to pay for one way or another. I'm confident Adobe will integrate Speedgrade into the Premiere and AE workflow well enough in the coming updates, but it is something they should have considered especially after acquiring the program so close to CS6's release.

  • When used in the proper setting, SG is quite awesome. But this iteration is just not ready for integration into the full CS. When they have it fully integrated, you'll really begin to love it. Once you get used to using it, you'll begin to see why I began transforming AE into a grading machine with a primitive version of ColorGHear. Because back when it was prohibitively expensive to own a Davinci system or SG; AE was the only real alternative for professional grading at home in 2003.

  • @Shian What do feel are the benefits of using After Effects(and ColorGhears) over Premiere for color correcting/grading? I'm new to grading so all advice is much appreciated.

  • @matt_gh2 so as to not hijack this thread; part of the explanation is located

    here

    http://www.personal-view.com/talks/discussion/comment/55779#Comment_55779

    and here

    http://www.personal-view.com/talks/discussion/comment/55553#Comment_55553

    ...but mostly Power, Speed, and Flexibility. NLEs should never be used for grading. They are really just there to make your rough cut not look so jarring.

  • @Lpowell, I think appalled is the right word. What they could have done was to modify the engine so you can work within the Premiere and AE formats and timelines, use the mercury engine for playback and layer on effects from different sources. But they did not do that. Epic fail.

  • The new release of the Adobe CC software (ver. 7.1) contains some vastly improved workflows betwixt P-Pro and Speedgrade. All in all, a wondrous up-take in capability/ease of use. Not, mind you, a perfected one ... but as this article from Adobe points out, the first "generation?" of the new linked workflow.

    http://blogs.adobe.com/movingcolors/2013/11/07/getting-to-know-direct-link/

    For much of my work, the new workflow is stunning in both ease and time-saving. Work something in P-Pro, 'send' to Sg for a bit, save ... right back to P-Pro with the grades right there. I've sent in a few feature requests because of either different choices by the developers than I'd make ... or STOOPID ones, like ... still no skin-line or color boxes in the vectorscopes. Dumb.

    Still, it's vastly easier and quicker to work in now.

    Neil

  • Wow ... I've been getting better at this whole NLE/grading thing ... using the CC versions of Adobe's stuff. Still no speed demon, but betting better results and learning how to work the system better.

    Took a 'b' roll sequence direct send-to-Sg, about 15 clips. Five adjustment layers between the several sets of clips, working through the whole thing ... next to last clip, putting a static mask in to lighten a face a bit, went to click off the mask to check my work, about the 4th time ... gone.

    Everything I'd done was simply GONE. The workspace went from the 4-scopes to the left, monitor to the right layout to a single mid-upper-screen monitor. The "view" was WAY yellow-green, and yet ... all controls showed centered ... as if untouched. Anywhere I scrubbed in the timeline, no matter whether I clicked on a clip or adjustment layer ... all controls zeroed but the monitor image way yellow-green.

    Tried a few "undo" Ctrl-Z's, nothing. Clicked the undo icon on the bar ... nothing. I'd seen I don't know how many auto-saves, so ... I closed without saving, re-opened ... well, the funny yellow-green was gone, but the monitor still "solo'd" without scopes ... and the footage was back to original un-varnished anything.

    Closed, went back to P-Pro ... no grading showing. Direct send to Speedgrade again ... still no scopes in view, and ... "naked" footage.

    I am a little bummed at the moment.

    Neil

  • @rNeil Did you look for the files that were autosaved? Maybe your grading work was saved there.

  • That's another odd thing ... it's currently set for 15 minute auto-saves, and yes, whilst working I had the little pop-up that another auto-save had occurred. However, after this blip ... when I went to the auto-save folder ... the LAST auto-save showing had been almost two hours earlier, right after first looking at a new folder of "b roll" stuff for this project. After going through the clips from media browser and choosing what I wanted to actually use, I imported clips and still into the project, set another sequence to hold b-roll clips, one for stills, set rough in/out for all the possible b-clips into that sequence, and sent them over to Speedgrade ... for an hour-plus of work there.

    None of that was in an auto-save. Around two hours of continuous work, not actually saved. Since Speedgrade was working a P-Pro "proj" file, it supposedly saves back to that file ... just ... weird. All of it.

    Neil

  • @rNeil Maybe try posting this issue as a topic on the adobe forums both in Premiere section and Speedgrade section. Maybe also email and call Adobe for help, if they have help lines.

    Sucks - sorry to hear of this trouble you're having. Hope you recover work and solve issue.