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

For the Creative tab, just figured a bit more out ... that list is compiled from the similar folder area above, but it's taking from the following two folders: Lumetri/Looks/Cine Looks Lumetri/Looks/Filmstock To be listed in the creative tab, your Look file must be in one of those two places, and MUST be a Look format file ... and will only show in PrPro if it's started up after you put the Look file in those folders. To make a LUT into a formal Look, open up a clip in SpeedGrade either via Direct to SpeedGrade link from PrPro or a new SpeedGrade project from within Sg. Use a clip with NO grading effects of any kind! Now ... click the "+" icon at the bottom of the lower left corner ... Then the little arrow left of the "Film option to bring down the list, selecting "LUT" option pointed at by #2 arrow here. That puts a LUT layer above the primary ... now go to the LUT navigational dot-dot-dot thing as shown here ... And find your way through your computer's files system to the LUT you want to convert to a Look file. Select it. You'll see your clip change. Now ... save that as a Look using the down-arrow-on-a-folder icon lower left ... so: And bring up the "Looks" bar by the little boxes on the far right bottom of the color-controls panel ... So you can see your Look thumbnail, click in it to rename it ... probably same as the LUT it's made from ... Then ... hovering over the ". settings/Looks" header directly above the thumbnail, a pop-up shows you the navigational directions to the folder it's in .... copy it out of there, and put it in the folder as discussed above for finding it in the Creative tab. Open PrPro, and voila ... it should now be in the Creative tab's dropdown list. Neil ... View more

In Windows, here's the location ... Neil ... View more

For most purposes, LUT's and even Looks (just an Adobe-named mini-variant of the cube format) from 'outside' the program need to be accessed by navigating to them. In both the Basic and Creative tabs, the second and third options ... " [Custom] " and " Browse " ... bring up a navigation/finder window, navigate to the folder where you store your created or acquired LUT's/Looks and select one. Some cube LUT's can ... if put in the "technical" LUT's folder ... show up in the drop-down lists. Many don't. And with many cube LUT's and Look's you can simply change the part after the dot to the other ... and they work fine. Not all do, however. A bit of advice on the use ... "tech" LUT's are designed to either bring a "flat" camera footage (shot in any of the Log formats) "back to normal" or to take a camera into say Rec709 or from Rec709 to some other color space by applying specially designed curves in their lookup tables for both luma & chroma. They are always built of course with the camera settings totally 'nailed' as far as white balance & exposure within the carefully setup lighting contrast. So ... for best utilization, it is good to 'feed' them a properly WB, exposed, and contrast clip. How? The ideal is to have the clip be in the second step of the process chain, and set 'in place' ... then you go back to the first step and correct the WB, exposure, & contrast as seen through the tech LUT in the monitor & scopes. So within PrPro, you'd invoke a Fast or Three-Way color corrector effect first ... then go to the Lumetri Basic tab, and apply your tech (corrective) LUT. Then go back to the earlier effect (which in the Effects Control panel will be above the Lumetri Effect control) and do your basic technical "grading" for again, white balance, exposure & contrast. Watch the Lumetri scopes while you're doing this along with your playback monitor ... though if you learn how to study the scopes, you'll do more in "tech" grading looking at scopes than the monitor. The idea is to get the program looking technically correct ... not stylized. After this, go back to the Lumetri panel and work away doing your style work. All the actions you do there are in the process after the LUT so they don't affect it at all. Now ... if you're also using a style LUT/Look, say a film-stock/print-stock combo ... let's say the "Kodak 5205 Fuji 3510" option on the built-in list. A film/print stock LUT is designed to give the "look" of a particularly camera film-stock (in this case, the Kodak 5205) which was then printed for release on the Fuji 3410 print stock. The print-stocks are transparent films with ... well, very similar to a color print's emulsion so it's a positive image ... sort of like an old slide film. They each had their own "feel" so to get a look like a particular film you need to mimic what that film was shot on and then printed on that particular release print looked like. But wait ... that specialized LUT/Look has the final curves for chroma & luma baked into it ... if you change anything after that LUT, you no longer have that precise look/feel ... so why bother using it in the first place? So ... very much like the tech LUT above, you need to feed it the right signal content in your styling work so that ... seen through that LUT/Look, your project looks like you want. To do this ... I suggest adding another Lumetri effect after the first one, as there's no other built-in way to apply LUT's in PrPro. Now ... using the controls from the Effects controls panel (not the Lumetri panel on the right side) ... add in your film/print or 'style' LUT/Look. Then ... go to that first instance of Lumetri in your Effects Control panel ... and use the controls there while watching your scopes (some) and your program monitor a LOT ... and make your project look ... "right". Sounds complicated ... but do it once, and it's not. Both steps are realistically the same. Neil ... View more

"Clearly One cannot import a mp4 in Premiere and have sound. Premiere fails to build both sound and video tracks from a mp4 video file. Import same mp4 file into Audition and it does build both tracks. So, why can't Premiere?" As I noted above, your situation is NOT usual ... PrPro imports mp4 files from thousands of users and all sorts of cameras daily ... including GoPro. I've seen a bunch of info-tutorials on using GoPro cameras that were based in PrPro even. Which is why we're trying to help figure out what the problem is with your files and setup. It isn't a general "Prpro" issue. Let's see that screendump (or screengrab) that Ann asked for ... Neil ... View more

Um ... I right-click on a clip in that build ... "Edit clip in Adobe Audition" ... do something, then save-as (to get a separate file rather than over-write the clip) from Audition, and um ... the work is now there in all its glory in PrPro ... with the green interior to show it's been "Auditioned". So yes, one CAN still go forth to Audition ... or SpeedGrade ... or AfterEffects ... and back ... in 2015. So again, it seems that it isn't an over-arching everyone is having this problem, because ... they aren't. There's too many people with GoPro's working away in PrPro daily. So ... rather than arguing about broken over-all Adobe software, let's get to solving your computer's problem? We'll see if I can rustle up some help ... Vinay Dwivedi‌ or RameezKhan‌, either of you able to jump in here? Neil ... View more

As there are a TON of GoPro users who are not having your issue, there's something about your setup that is causing this problem. Now, one thing that pops out to me is simply Win10 ... that OS started out as a complete disaster for video gear & software. It might not be your issue. So some troubleshooting is likely needed to nail this down. Answering and testing specific things the user-base here asks would be your best bet to get fastest resolution of the problem. To restate what it sounds like is the case ... you've done the appropriate process for importing into PrPro, which is ... 1) load the footage to a hard-drive on the computer; 2) navigate to the footage in the Media Browser panel tab in the lower left quadrant; 3) select your footage, right-click & choose "Import"; 4) switch to the Project panel tab lower left quadrant, select a clip and either move it up to the Source panel and from there drop it onto a blank timeline (so PrPro creates a sequence for that media) or drag it from the Project panel onto a blank timeline area ... that correct? And the result is a clip on a sequence with video but no audio ... it would be very handy if you could get a screen-grab of your sequence's left-end & controls & post it on a reply. I think in Win10 they have a version of the "Snipping Tool" ... a Windows mini-app that can make a quick png of any section of your screen you select. That works very well. Just use the icon of a picture in the formatting header atop your post to upload it ... or once I've saved a "snippet" I found I can often then just click in the reply area of the forum here, and then Ctrl-V to paste that image into my reply. As to Win10 ... Microsoft has been rather open that they started from scratch with this OS, trying to ditch as many "old" style bits of code & processing to get as new and streamlined as possible. In the process, when it came out, very few video softwares & gear worked with it. Not just Adobe ... a ton of the BlackMagic hardware bits, AJA, Kona, all those ... many plug-ins, all kinds of stuff from all kinds of vendors didn't work well or at ALL with the initial Win10. Ms has been doing their ittle-bitty patches & updates process and over time that OS has got to where some people who started with a clean install on a wiped disc and slowly added programs & gear onto the machine all with driver updates ... run fine. Others can mostly sort of run. And some just can't do squat on it. Jumping to an OS before knowing it is rock-solid with the programs gear one uses ... is problematic, leaving oneself open to such problems. Jumping to a new NLE before testing it yourself on your machine is also ... risky. A long-held "best practice" is to keep "full" previous versions of editing software "live" on one's machine, keep working in them and testing the "New & Improved!" release UNTIL one is certain that one's ability to work in it is assured. Even then, if you've got say a project done in CC2014.2, it might be wisest to keep that release "on" you machine so if you need to work it again, you can do so in that version. That project may or may not work right if brought forward into CC2015. And this isn't just for "Adobe" products ... as Kevin Monahan notes here, though he's an Adobe staffer now, for many years he was a pro editor and a teacher of Final Cut through several versions. He taught that back in the early 2000's to all his classes ... as he still suggests for anyone with ANY software. I'm still running Win7Pro ... it works fine, there was never any reason to upgrade our shop to Win8. When ... and IF ... Wind10 becomes notably stable for editing/grading apps, I may likely move forward as the parts of that OS that work are "fast & light". But too much of that OS sucks in video right now, especially with the programs I need. Neil ... View more

What is your OS? And how did you import your media into PrPro, and ... are the video AND audio track selectors showing blue ... so you know they're "targeted"? Neil ... View more

J. Simon's comments are dead-on. When I first started pro video work, I came from being a pro portrait studio photog of 35 years (at that time) and used to organizing my image files for best working AND best backup/archiving ... which are two different steps by the bye ... I found working in video very, very different ... and had to learn completely new organizational skills to get things so they both played smoothly during processing AND were easy to back up & to archive. Took some work, and trying one set of folder structures out, then another ... and finally ended up with the current setup. And most everyone does it a bit differently. But yes ... organize on disc before importing! Neil ... View more

There are still issues for a LOT of Win10 users ... the patches they put out seem to be helping some. Neil ... View more