It was just "released" within what, a couple hours? Yes, another hour or two of patience ... Neil ... View more

It happens that the CC app every once in a while is ... odd. Sign out of it (ignoring the Horrible Things! warning) and back in ... which will probably fix the issue. IF that doesn't, then ... this will. 1) download the Adobe CC Cleaner app: https://helpx.adobe.com/creative-suite/kb/cs5-cleaner-tool-installation-problems.html 2) ignore the "official" instructions ... they tell you to use your OS application uninstall utility to uninstall the offending app, then run the CC Cleaner tool to remove the preference & other files that are always left behind; instead, use the CC Cleaner app to do the uninstall/cleaning. I've never had it work right the 'official' way, and it always works this way ... 3) reboot your computer ... 4) go download a fresh copy of the CC app, install, and sign-in. Your problem should be solved. If it isn't, repeat the above ... uninstalling both PrPro 2015 AND the CC Desktop app. I had to do this one time when it insisted SpeedGrade was fine, and it was a release back ... so Direct Link from PrPro wouldn't work. Had to delete both CC App & SpeedGrade. Neil ... View more

It's hit & miss, but they do listen to users ... there were a few of us really "hollering" for better scopes in SpeedGrade, and that got the Lumetri scopes now used also in PrPro, a HUGE improvement from before. Many other such features. This bit about modifying audio tracks nature or output targeting after the start of a sequence is as you put it, so needed. So please, the way Adobe works is the senior level managers (well above the program teams) who decide budgetary things like what projects engineers get paid time to work on, work heavily from the bug/feature reports that are distilled and passed up to them. You won't get a reply, it feels a waste of time, but they are actually rather important. I've filled out several on this issue over time ... and hope you'll add yours also ... https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform Neil ... View more

What Kevin's answer didn't go into explaining, is that in the Adobe system, the bug reports are what get reported to the senior managers who determine budget levels for engineering time ... so those bug reports that seem annoying at times and are rarely acknowledged actually are rather more important than most users understand. While Kevin and some other staffers do wonderful help here, and do pass on what they can, the official in-house system is those bug reports filed in a database. So ... please, file away ... Neil ... View more

Upgrade or a clean disc-wipe/new OS installation? Those doing the simple upgrade process seem to have nothing but headaches dealing with video issues. Those doing clean installs seem to be able to run ok. Neil ... View more

What you do is: 1) apply a LUT or Look to a clip in PrPro's Lumetri window with NOTHING else done to that clip ... then 2) right-click on the 3-bar icon to the right of "Lumetri" on the tab at the top of that right-side panel 3) select "Save Preset" and name it. Your "preset" now appears on the Presets tab in the Effects panel, with any other saved presets you've made, and you can use those as you would the ones in the Lumetri panel. I haven't yet figured out how to get one into the Lumetri effects panel listing ... Neil ... View more

Here's a copy of the contents of another thread on this sometime ago ... and you can search the forum for such things, of course ... ----------------------- Hi, I discovered a solution.  It is frustrating because most of the posts I found are from kind people offering advice, but who are using PC's.  For this issue in Premiere Pro CC on a Mac, what PC computers see is not what we see on our Macs.  The LUTS simply don't populate when the "Select a Look/LUT" window comes up - they cannot be navigated to (without performing a little tweak).  As Vinay pointed out, they are contained in the "package contents" of the actual Premiere app on a Mac (as of this writing).  Package contents cannot be navigated to from Premiere Pro CC.  So, here is the solution: 1.  From a regular Finder window (not within Premeire), as Vinay described, "Go to Application folder>Premiere Pro CC. Right click on the Premiere Pro CC.app and select show package contents. Then go to Content>Lumetri." 2.  Double click on the Lumetri folder. 3.  Locate the LUTs folder. 4.  Half-click on the LUTs folder and select "Make Alias" 5.  Drag the new LUTs alias folder to a location where you can navigate to it from within Premeire (meaning anywhere but a package contents folder).  I put it in my Apllication folder>Premiere Pro CC folder.  Make sure you moved the alias, not the original folder. 6.  Open Premiere. 7.  Go through the process of adding the Lumetri effect to your clip. 8.  When the dialogue box comes up to "Select a Look/LUT", navigate to your new LUTs alias folder.  Boom. This worked for me.  Hope it works for others as well. ------------------- Also, here's another thread, with info on putting LUT's/Looks into folders so they appear on the 'pop-ups' within the Lumetri panel. Also, Adobe has a LOT of help/info/tutorial resources you might find useful, check their help & resources and of course, the AdobeTV stuff. Re: adding LUT's to Lumetri color? Neil ... View more

As Richard says sign out and back in. And if that doesn't show  9.1 update available you will need to use the Adobe CC Cleaner app to uninstall the CC app and PrPro and then download and install the CC app, then from that download PrPro again. The CC app can occasionally get wonky like that. Neil ... View more

Sg 2015.1 fixed a bunch of problems ... I wasn't using if for much Direct Link work as well, it didn't Di-L nearly as well as say 2014.2. So I was still doing some new projects in that. It seems to be working fine in most respects now. Neil ... View more

That last bit is something I didn't know ... thanks for the info, J ... Neil ... View more

There are a fair number here who definitely prefer it to ProRes & DNxHD (the comparable Mac & Pc codecs) as it does edit smoothly even with a lot of effects, it's less compressed & its manner of compression "fits" the computers quite well. It's so high-quality it is a good export codec also. J. Simon notes he transcodes all his mov/mp4 and other such stuff involving a rename that 'sticks' on both the original clips & the transcoded clips. The Cineform files are much bigger, so after editing he deletes those & puts the exact-named original clips in the folder in place of them for archiving. Neil ... View more

There are a ton of XAVC codec options, within XAVC-HD and XAVC-QFHD. I don't see an XAVC-S listed, in that you are correct. These are export options, of course ... you don't need to have XAVC-S  as an export option to be able to process in it ... similar to those of us on Windows systems, who can process ProRes files within PrPro et al, but can't export to that codec without buying a spendy license pack ... so we utilize DNxHD/HR. Neil ... View more

It's not showing any audio in the Source monitor panel ... note my grab here, there's two icons in the bottom of the Source monitor, one for video content, the other audio. In your grab, the audio icon is grayed out, PrPro isn't reading audio from that clip. Of course, wouldn't matter if it did ... as your patching setting for audio on that sequence is OFF ... note, you've got two blue V1 patches left side of your sequence area, but only one on the audio side, the A1? That far left gray block needs to be 'clicked' to turn on Audio patching (adding audio clips) to that sequence. Here's a grab from mine ... Note up top, in the Source monitor, BOTH the video icon (film strip) & audio icon (sound wave) are bright ... showing PrPro recognizes this clip has both video & audio. Also look at the clips listed in my Project panel down lower left ... the circled one shows both a film clip & audio wave over-lapped, meaning that clip has both. Video "without audio" doesn't have the sound wave, and audio without video doesn't have the film icon. Also note, my sequence area lower right ... see the blue matched set of V1 & A1 boxes? That sequence will take both video & audio content from Project panel or Source monitor. So ... I'd say how your clips were imported might be the issue. Standard procedure, navigate to media in Media browser panel, right-click, "Import", then add to project from the Project panel ... I presume that's your workflow? If so, then there's a possibility your cache is corrupted, and needs dumping. Also, a couple people have reported something like this and found if they simply changed the name of the folder, then changed it back, suddenly PrPro saw their media's sound properties again ... Neil ... View more

Please reply with a screen-grab of your clip in the project panel, and also maybe loaded into the source monitor ... and one of the controls-end (left end) of your sequence. Neil ... View more

I would NOT expect 422 10-bit to band like that ... hmmm. Neil ... View more

What video format settings did you use shooting in camera? That rig can do RAW with external recorders, and ProRes 422 internally besides 'smaller' color spaces ... that footage looks very 'flat' coming in, implying some sort of RAW or log settings perhaps ... Neil ... View more

Now ... banding ... Ok, you have an 8-bit file, it has only 255 discrete different levels between 0 (black) and 255 (pure white). If you change the lightness of an area, especially a lighter area, it doesn't have a lot of 'room' for change before you've spread the bits of data around so they can't 'cover' all 255 values, there are gaps. Say you pull the middle values down a bit, and where it might have had a complete full 'string' of values in the upper regions, you might now have data in say value 182 & 185 but nothing in the 183 & 184 spots. Get a few points where you're missing more than 2 values, you start seeing banding. 10-bit image files can be made to 'band' but you have to work at breaking them. So ... just a bit of info on what banding is. Which ... those wavy lines on that wall? That's banding. Neil ... View more

If you could post a screengrab of the clip in PrPro's program viewer with the scopes right beside it ... maybe both before & 'after' any work you've done ... that would be great. Seeing the scopes would give shooter & I a wealth of info ... Neil ... View more

Hope this doesn't "doublepost" as I just responded but it isn't showing ... The exported clip is a lot darker (which could easily be a gamma change) and has major banding issues ... across that wall area you circled. That's caused by spreading out 8-bit values too far so the 'edge' of the changes show. All of which leads me to ask ... did you view and screen-grab the exports from having re-imported them into PrPro, or from a media player on your computer such as Quicktime? Neil ... View more

Btw ... shooter is one of the better ones on here for handling projects through to deliverables. Use his brain/experience, he's good at this ... Neil ... View more

Apparently you didn't read down through the comments? There are some settings in the PrPro/AME export dialog he didn't mention that make huge differences in the output, so depending on how those were set you could easily have that as the issue. He doesn't say ... so basically, his 'test' is worthless. Now ... as to your issues, there are some folks that 'hang' around here that are pretty hot & experienced at pro level encoding of deliverables, having done that for years. How about working this through? Post a few screen grabs of your original footage, on the sequence, and exported including screengrabs of the export settings. Also ... include shots of the scopes especially RGB parade & waveform, as that can tell a lot about how the media was shot & also how it's been graded. Let's see if "we" can help you ... Neil ... View more

Is that H.264 "washed" when viewed in PrPro ... or when viewed in a freebie player like the Quicktime player? It may be that if you're not viewing it in PrPro after export, you might be looking at it through a gamma-challenged player. Which is often the case. Neil ... View more