I have bmpcc and use PP CC 2014 as well as SpeedGrade CC 2014. I use dynamic link from Premiere to Speedgrade, create custom LOOKs, direct link back to Premiere and then apply the looks through Premiere Color Correction effect Lumetri
One way things started changing as for how Premiere viewed the bmpcc is when I started resetting Preferences.
Another way when things started changing with how premiere viewed the bmpcc files is how I was incorrectly importing the files and finally started correctly imported the files
I use the bmpcc compressed dng files, not the prores.
I have not noticed the applied looks being different results. I have seen weird things, but cannot remember specifics as done lots of looks with lots of projects.
I've had discovered that sometimes there are inconsistencies and bugs when using a third party plugins, but in the last versions of Speedgrade they dropped to the minimum. Maybe you could check that.
I'm not sure if I totally understand you guys' solution. What should I check for?
Could you two elaborate on your solutions? What is the correct way to import the files? Which plug-ins?
What have you reserved for other applications with RAM in Premiere's Preferences under memory?
Are you familiar with resetting your application (Premiere Pro and Speedgrade) Preferences while launching the programs?
What automatic Sequence setting is Premiere creating for you? The sequence setting it gives me is ARRI Cinema?
I shoot the RAW. What are you shooting with your camera - the DNG or the MOV?
I now import through the media browser with the RAW as importing through the Project Bin is wrong.
I have 3 GB reserved for other apps on both programs.
I am not familiar with resettings preferences.
I think mine was also on ARRI cinema but it doens't change the look for any of the Sequence settings presets.
And I use both but the particular project I'm working on only has RAW footage
I start my Windows 7 and check Task Manager Performance before launching any programs and have 3.83GB RAM used. After closing out Premiere I have seen my Task Manager Performance with over 4GB of RAM used. I used to reserve 3GB, then I stepped up to 5GB (now 10GB because I have lots).
I have never used the 'shipped' SpeedGrade LOOKs, always make my own and do not think I have had your problem.
With resetting Preferences I did see right away that the 'resetting' had initiated, but do not think I noticed a difference within the program because I was mid-project. I believe it was when I started a new project that things appeared 'reset'. All at once my RAW footage started appearing flat (as it should), it was like I had shut down the camera's apperature and not remembered. With the flat footage, I had to work the custom LOOKs way more in SpeedGrade.
Resetting Preferences is holding down two keys while launching the Premiere Pro and SpeedGrade (After Effects is different). Hold down SHIFT and ALT while launching PP and SG.
Well in the media browser it shows the clips in a folder. But the project bin just shows the file as nromal
My Media Browser in the tab beside the Project Bin shows the dng sequence as a 'pictured thumbnail'.
So I am not sure why you say your Media Browser shows the dng sequence in a folder.
Sorry I meant that the Media Browser shows the sequence as a thumbnail as well...just in it's own folder
My two screenshots above are of my Project bin and samples of how the bmpcc dng sequence (clip) should not look and how it should look
This screenshot is how my Media Browser (tab beside the Project bin) shows my bmpcc dng sequence
yes, the dng sequence is in its own folder. If you click on the 'triangle' nothing happens, just the triangle turns down as if the folder opened, but nothing happens. If you click on the folder itself the thumnail appears in the viewer window to the right. It is that thumbnail where I import from and could probably import from the folder, but do not import the dng sequence inside the Project bin.
Have you made any progress with resetting your Preferences?
Exactly that's how I've been doing it since I've been using the the programs. So about the color shift issue?
My thoughts with how to approach your issue is to see about getting the direct link from Premiere to Speedgrade working so that the two are properly linked and seeing apples to apples. Premiere and Speedgrade will not be 100% matched however as Premiere works with 8 bit color and Speedgrade as you have it set. With resetting your preferences and files imported properly and the direct link does not work, my approach to find a solution to your issue involves more paths to check. So, with the color shift issue - I will not be able to guess without looking into your machine. Maybe someone else has that ability.
My direct link works. Even when i direct link and use a custom .look i have created the footage doesn't match what it would look like if I had imported the clip into Speedgrade itself
I read another one stating that BM did not have their drivers for Premiere Pro CC and the person replied to the poster to ask BM when they would have drivers (or why not)
I have not been able to find that post regarding the BM drivers, but I did however see another one stating that BM had new drivers for Premiere Pro CC back in June 2013.
I believe I was able to achieve SpeedGrade and Premiere color match but that was when I was importing the dng sequences through the Project bin and was also in PP CC 2014 8.1. Now that I am in 8.2 I cannot replicate the same color match (as of yet). And I add I do not recommend importing dng through the Project bin.
A work around I was applying in PP CS6 was to open the dng sequence through Adobe Camera Raw, apply the color adjustment, batch apply to the rest of the sequence, then 'save as' chosen format. I was saving the dng frames as Photoshop documents, which turn a 2MB file into a 6MB file, that makes massive files with 29.97 frames a second. Then I would import the PSDs into Premiere already color corrected - skipping Speedgrade.
I have never used After Effects as it seems you have to work with individual frames and cannot 'batch apply'. I have seen people ask for a fix on that also.
edit here is the BM driver reference dated this year 2014