I'm not running any kind of surface ... just a Wacom tablet for the left hand (lefty here), Microsoft "Natural Ergonamic" keyboard with it's 10 or 15 extra configurable keys, and a Kensington Expert Mouse trackball with 2" ball, surround ring, & four large paddle/buttons. I'm thinking about how I've got them set and it could easily be improved. I've not been that encouraged to look at dedicated "surfaces" yet as the Adobe implementation for just PrPro & Sg seem perhaps not completely ... there, from the comments such as the above. It would be nice to see Adobe really go after getting these interfaces ... interfaceable? ... wouldn't it? Neil ... View more

If PrPro can edit a codec, it can normally transcode from it to something else. As Kevin notes that PrPro can as of that "ish" edit it, it will also be able to transcode also. Neil ... View more

It's always interesting for me to see how people like to work. So thanks for the workflow bit. SpeedGrade was originally designed by the Iridas folks as something they assumed was being used by experienced colorists who knew all the technical mumbo-jumbo, would use keyboard shorts or "surfaces" for all their work, and therefore ... UI "features" were just a waste of time and screen space. Hence the rather minimalist to non-existent UI ... This has even led to experienced and high-end people who do things like say edit/grade at Olympics for the evening's highlight show (think of the two biggest international "networks" who could be at an Olympics ... this dude worked for both) ... a rather professional and high-speed user? ... being totally unaware of either a couple things it could do or that some of the things he could do were also possible to get to completely differently. It means that for most people, even experienced users coming into Sg, many of it's capabilities aren't apparently there. For those like myself who've come into video production from 30+ years of professional stills image work (including building & operating a high-custom output pro portrait lab) ... that non-UI appearance is pretty stunningly opaque. In knowing hands, it can be an amazing and fast tool. But that UI doth to many of us, stand in the way of making it of obvious use to a larger audience. So there've been a lot of discussions here about that UI, and why it's still THAT UI, and the question is ... as it seems Adobe is moving to linking that more like a plug-in for PrPro than a separate single-entity grading program, how much work are they interested in putting into parts of the UI that are locked-out during a Direct LInk session anyway? No clear answer on that, other than ... they're thinking. Understandable really. The whole CC model though has made Sg of great use to me ... within my projects I can cut forth & back twixt PrPro & Sg within seconds, no transcoding, XML or EDL exports/conforming steps. I've actually found Sg (as I've come to use it better) to be the single most entrancing app on my computer. I tried a free bit of Resolve Lite ... and personally, preferred Sg. Which is natural ... I don't know two people who work in all these programs just alike. But I learn so much from other's patterns, choices, and capabilities. I shoot primarily H.264/mov and without transcoding work it through the process. But then there's not been a hack for the GH3 as there was for the GH2 and of course several of the Canon's. Those opened up other possibilities as you've chosen to utilize. Within my stuff, I'll start in PrPro and if there's something that I might think of using but wonder what it would really look like, I can in seconds put it on a sequence & take that into Sg for a minute or so of testing, and if I think it'll "fly" use it, if not, dump it. Most of the stuff I'll use of course just gets put on a timeline, adjusted, taken to Sg early on for the WB/general work before continuing in PrPro, then back to Sg a time or two later for style/feel. Simple processes for people with simpler skills? Neil ... View more

Would appreciate your thoughts on differences betwixt Resolve & SpeedGrade, and of course the PrPro->Resolve process you're using. Neil ... View more

Bill's first comment in his reply is really the key ... "it depends ... " Some effects are very GPU-intensive in their "math". Many aren't. Those that aren't typically don't get sent through the GPU when exporting to a new file, and so ... for many timelines, there may be a part of the timeline where the GPU suddenly gets involved ... and the rest of the time, mostly ... sits there. Having a hot GPU isn't any magic bullet, it's just part of the toolset. Having the world's greatest framing nail-gun isn't of any use when you're hanging drywall/sheet-rock ... very similar concept. Bill's PPBM testing will determine how well a system works in total ... and yes, part of that will rag out the GPU ... but other parts of that render won't. It's designed to test both the GPU-assisted work and the non-GPU-assisted work within PrPro, AE, & Sg. Neil ... View more

Especially on the Tweaker's Page, there's a lengthy page on current video cards ... they work on balancing systems, noting that the Adobe DVA's only use up to X amount of any one resource ... as it's all relative to what the OTHER hardware resources are. Putting a really hot video card in a system with a two-core CPU at 2.8Ghz and 6Gb RAM and everything, programs & all, on one hard-drive is a total waste of money. The Adobe apps might not even use any of that card if everything else is so limited. But building a heck of a system with an old v-card with 256Mb of v-ram is also not wise. It's a balancing act. They list quite a number of cards for comparison, and these are in operation in real systems, not from "Oh, the specs on this card are good ... ". You'll find more info than you might want over there ... Neil ... View more

Oopsies ... being an ol' Lit major, I sometimes idiomize my language too far ... the "twain" is the two choices I listed ... hardware forum & tweaker's page. Um, not obvious, I must admit ... Neil ... View more

You'll probably get some response here ... but still, the best choice is twain ... Adobe's Hardware Forum ...   https://forums.adobe.com/community/premiere/hardware_forum Tweaker's Page ... http://ppbm7.com/index.php/tweakers-page Neil ... View more

Well ... I wouldn't say they never listen to people's requests. They've responded to a couple I've howled about ... but not to a few others I've howled about. They do take the bug/feature request lists in part of the decision making project, but the unfortunate thing is the person making the Ultimate Decision doesn't take my personal views as Rule of Law. Wish it weren't so ... Neil ... View more

Thanks ... that's quite a good explanation so that I can understand it. Love learning things which is part of why I hang around here with all the work & missus & family and such ...   Neil ... View more

You were nearly a lifesaver, Jeff! Neil ... View more

Mele, I'm afraid I'm sitting right next to you "in the boat" and you just don't see me! Ha ... I've managed to pull off a few things in Ae with help from "lynda", shooternz, Jim Simon and others around here, and a few others elsewhere. Spinning graphics? Timing lower thirds to music? Haven't done those yet ... I've got some lower thirds to do that need scrolling text on a project "up" at the moment. I figure probably Tuesday I'll be doing that ... from a couple of the lynda tut's it doesn't seem too hard in PrPro really. Thankfully no need for Ae on it ... that program is mystifying to me. I do so love the members of the Ae forum that are sweet to "noobs" with that program and gently helpful to someone who's baffled & puzzled and needs explicit instructions as I DON'T even know what names for the 35 options for everything mean let alone what they do ... and "well, just try something for dang's sake ... " can mean spending a couple days punching buttons. With no progress made ... not good. Some of the old hands there can be testy with someone like me ... as in, "go play in some amateur sandbox & leave Ae to us pros". Yet my projects are also paid ... I'm just not a full-time for 30 years video person. Master at stills portraits for 35+ years, yes. Video ... fairly new. I can get around in Sg pretty good, love that program ... can survive in PrPro. Still rather intimidated by Ae. And then there's Audition & Encore ... oh my, the learning curve of the last two years ... Neil ... View more

Not yet ... we hope soon, and I think some of the staffers hope soon also so they don't keep getting the complaints about this!  Neil ... View more

Well, whaddaya know? I tried this with my laptop running Win7 "Home" and the legacy driver thing there didn't work. But with my desktop and the new Texas Instruments video card, installing the Legacy driver did allow use of the ol' Firewire400 6-pin port. Difference between computers, firewire hardware, Windows version ... ? Ah well. You are correct at least for Win7 Ultimate! Thanks ... Neil ... View more

As was noted on several of the posts I checked on this "here" and other places online, and my experience is likewise ... though I used to connect back with earlier software and WinXP using a 4-pin/6-pin cord cam/computer, that does not work now ... PrPro will not see the source as online. Switch to a 4-pin/9-pin cord camera/computer, and it sees it as online. Same card. And yes, the 6-pin sockets on the card are working for say external drives and things. Tried this on two different PC's, both Win7. Same result as posted here and elsewhere. Now, if you've got one currently "seeing" a camera through the Firewire 400 6-pin connection on Win7/8 and PrPro 8.2 ... I'd love to hear about your setup! Neil ... View more

I am curious if the 6-pin connector will work to PrPro in Mac, as it doesn't in Windows ... Neil ... View more

AME is basically the default engine for PrPro's exporting. Setting your export settings in PrPro uses presets from AME, so if you've made some for specific repeated jobs ... you would just choose that preset in PrPro and "go". Queuing over to AME allows you to use the full range of options for each format/codec, not just the presets. I'll let someone else answer about Ae ... Neil ... View more

Just got re-set to do this on PC running Win7 Ultimate ... and at least on the PC side, you have to use a 4-pin connector (small metal square-ish with a divot in one side) ... and can use the 9-pin (square shaped plug) plug out of the computer to a 9-pin to 4-pin cord but the 6-pin style connector, which is the one with one end in a V, will not work. My old cam was a Sony DCR TRV330. Maybe it's different on Mac ... but I had to get a firewire card with that 9-pin Firewire2 connector. Then PrPro can now "see" the cam in Capture mode. Neil ... View more

I've seen commercially produced LUT's available for this, you'd need to search for them. Within Sg, there's the "Looks" produced by the "Lumetri engine" which are in application exactly the same as a LUT ... though they don't export to other programs. I know a number of colorists who've made their own Looks for specific cameras by simply loading test footage of a set scene or test pattern, then working their controls until they get the correct result in scopes, then saving that as a named Look for that camera. Doesn't take much time to do once you've the hang of Sg's controls. And that can be applied either within another layer or or on a separate adjustment layer made in PrPro for a grading layer. Neil ... View more

PrPro has the library of effects in the effects panel ... and of course the ones that can be brought forward from CS6, but past that ... they expect that major "effects" are done in AfterEffects, and there's a TON of templates for that program available around the web. Or that one creates some things or acquires them around. Those coming from outside the fold so to speak oft complain of the lack of presets & templates. Those used to working within the PrPro framework tend to be either rather disdainful of "wimps" ...  or for many, simply puzzled that someone using a "professional" program expects the kind of hand-holding that amateur programs give. There are add-ons for PrPro out there ... you'll have to search for them, of course. But welcome ... we do have fun discussions here ...  Neil ... View more

In your CC Desktop applet, scroll down to the "Filters & Versions" highlighted line, and click on it ... then navigate to selecting PrPro CS6. I think actually you can unzip it and then copy the folders ... or does it actually unzip while installing ... brain freeze, sorry! And at any rate, after you've got the folders copied over you can uninstall or delete the rest of it unless you want to keep it. You can run CS6 & CC versions live on the same machine. Neil ... View more

That was a major update ... like going from say FCP8 to FCP9, perhaps? CC 2014 was by "build" series 7, and CC2014 is 8. CS6 was well, 6. I've no problem with Adobe's Cloud idea per se, but there are a few things about it that could be a little more ... user-wise? ... shall we say? In general, the cause seems to be ... humans being human. To them, within the system, how the system systematizes is well, rather obvious. For those of us outside the system but using it ... such details as when something is a bug-fix release or when it's a major update to a "new" serial number are not always so obvious. And considering there's no terminology in the project file names that tells anyone what release they are, opening something in the 'wrong' version is naturally going to happen. Which of course it could and would in FCP also, as to my knowledge there's nothing in that format's file-naming to list versions either. Now ... some people say "but I never EVER had a problem like this with a corrupted file from migrating in FCP!" and they are probably quite truthful. There are corresponding folk here in the Adobe realm who also note they've run thousands of complicated client projects and NEVER had a corrupted one. Also being quite truthful. It's just we all hate losing the lottery, don't we? Neil ... View more

With my gtx770 card, I got it because 1) I saw several comments from people using this within Adobe that it was so good they'd even replaced Quadro cards for better output and 2) it was a couple hundred less than other 'comparable' cards. I've had a couple private responses from people for whom this card is wondrous. GPUZ seems to find it quite accessible and uses it easily in testing. It's just that ... somehow ... on my machine, in my parallel universe, Adobe DVA's aren't mating up well with it. Why? Dunno. Monday or Tuesday I'll have the time at machine to run the benchmark, see if that gives any answers. Neil ... View more

Did you actually read the resource? The heading of that particular page is ... "XAVC 4K/HD and XAVC-S with ADOBE" That would seem to be inclusive of your footage? Neil ... View more

That looks like it helps encoding exports (outputs). I've got a GTX770/4Gb that neither PrPro nor any other DVA's are seeing ... at least as far as using at any time for any footage/effect/process ... max usage is 5-6% of GPU, 880Mb of the 4Gb of vRAM. The Gpuz little applet to test the GPU for running or not can instantly peg the GPU at 100% utilization, and vRAM to 3.8Gb. So for some reason, none of the Adobe apps want to actually use the GTX770. On-board video is disabled in BIOS, that card's been installed multiple times and has everything but the BETA driver for "latest" ... frustrating. Neil ... View more

Gee, did a quick google of this ... and whaddya know, over on the Sony site they've a nice long pdf on XAVC format, nature, using in-camera, and with various NLE's. https://www.sony.ru/res/attachment/file/62/1237492960962.pdf From page 25 of that pdf ... well, you can find it now and read it yourself I think ... Neil ... View more

I think you've proved the issue here was an update in CC and migrating the project file forward. And yes, since that was started on the other machine, there was an update.I wish this could simply be a painless process, but as Adobe staffer Kevin Monahan posts here quite a bit, it ain't. He's a long-time pro editor and was a member of one of the FCP design teams a number of years back, and was also a certified teacher of FCP back a decade ago or so. As he notes, he's always taught keeping any project on the software version it started on if at all possible. No matter the NLE, migrating a project forward has some possibilities of working fine ... BUT ... if anything does not work fine, this is BAD. Clients screaming & refusing to pay bills for late work, badmouthing one about the "hood" ... none of this any delight to anyone. In these days where an update can come every few months rather than say every 18 months, it's a pain in some ways. So he recommends keeping each major iteration (full number of PrPro, such as 6, 7, or 8) "live" on your machine as they can exist in parallel. New major upgrade, start new projects on it. Keep old projects on old versions. And for continuing projects, keep working in the old while migrating COPIES of assets into a new project, testing as you go along, this way moving everything forward while still working away. When the new project is fully functional, then archive the old one & move on. Some work ... but dang, having major shutdowns under multiple looming deadlines is past annoying. Well. Neil ... View more

Thanks ... nifty. Neil ... View more

"Clarity" across apps is basically a control on local contrast, in other words, similar to applying a small controlled set of Unsharp Masking. That's the Theory at least. As an accounting adviser we once had taught in his accounting clases, "There's Accounting in Heaven (holding the text book in hand, then setting it down) and accounting on earth (and you could easily hear the Initial Caps & then lack thereof when he spoke) ... and though we use The Book at times, I TEACH accounting on earth." The concept seems to apply here ... In Theory, clarity is just a bit of unsharp masking with a particular setting to the algorithms for a small effect. That said, I've been able to sort of come close with a bit of play in a full Unsharp Mask tool. After a LOT of work. When if there's a clarity control, I'm "there" in a half-second without thinking about anything. Yea, clarity could be a darn nice thing to have. Put in a Feature Request for it, probably one each for PrPro's controls & one for SpeedGrade ... I've done about 4 or 5 over time for this myself. Adobe - Feature Request/Bug Report Form Neil ... View more