Or if that doesn't work, to reinstall the entire OS. I'm thinking about reinstalling Adobe Premiere on the systems which act weird. Which doesn't happen on the system we tested today. It did force each system to rebuild the cache, but they all still force color on some of the clips on some of the timelines. That didn't seem to do much for the 'affected' systems. Both on the local systems and on the server. Somehow the other systems (which worked within the Production project on multiple occasions before) seem to be 'bugged'? Yesterday, I already tried to clear all the cache. The sequences (inside multiple projects within Production) that hold various clips (which are being 'forced' with color on other systems within our network) are now shown 'flat' (ungraded). Today, I opened the Production project on a system (also connected to our server) which never opened the Production project before, and as it seems, it recognizes everything as 'flat' footage. To make things more complex: I've narrowed down the issue to 'just' several editing systems which opened the Premiere Production project at least once since it was made. Right now, besides the workaround mentioned before, my only chance is to import all footage again in a separate project within the Productions project, modify those clips the right way and than find back the exact same clips to drop them above the old clips. Unless I'm missing something and I'm still able to fix it in an easy way. 709 (so partially on 'people' to blame), but it would me things a lot easier when you're able to correct the color space afterwards (especially in case of Premiere Productions) or if you're able to just switch a button to 'classic mode' (or something like that). Yes, it's a matter of importing it the right way and modifying the color space override to Rec. A workaround that's really unnecessary in my opinion. For now it works, but in the end its a workaround. I had to make an export a couple of hours ago, and yet again, the only way is for me is to move the sequence from project to the project it was created in (so it sits right next to the raw footage). Right now, Adobe really makes it hard to just export the timeline, because there is no way to turn off this new color management. I get that the new color management within Adobe tries to reverse the color space on its own, but in our case (besides the fact that it looks awful in most cases) we need to send out the edit to our grader.
This footage by itself is ungraded, which later is send to a coloring house to be graded. Our footage comes from a Sony PXW-FX9 (Sony S-Log3/S-Gamut3 or S-Gamut3.Cine). I'm kind of thinking about reinstalling all sets that are affected by this, but I'm not sure if that will make any difference. You really have to move the sequence back to the project where it was created (in this case the Footage project), after which exports are back to normal. In both situations, there's no way to make an export from the sequence projects. Once opening a sequence on two different computers, the one which created the sequences shows all footage in a 'flat' way, but for another computer which is in the same project at the same time, some clips are colored (the ones being 'forgotten' while modifying the Interpret Footage option). This is being tested on several computers within the same network (all running the latest version) and there are several outcomes. Again, these sequences (containing synced footage on a timeline) where made within the Footage project and then moved. There is still color.ġ Footage project holding the source media (all MXF files)īesides these, there are also projects that hold single sequences (nothing else) so multiple editors can work on the same episode. Once I override the 'forgotten' clips in the Footage project and save it (even after restarting Premiere), the sequences in all separate projects (within Productions) aren't affected at all. "T he CM set in the Modify/Interpret Footage for the clip seems to follow to any sequences". From what I understand, you basically use the same workflow as I'm using, but for you it seems to work:
0 kommentar(er)
