"It is not a hardware/OS related problem" ... "It is clearly a bug"
Whether or not it is related to the hardware or OS the user is using, has nothing to do with whether or not something is a bug. There have been numerous bugs over the last few years that were totally based in one OS, or type of GPU, all sorts of things. They weren't any less a bug because they only happened in Macs or PC's or with 1070's and not 1080's, pick your hardware.
Nothing in my post suggested that it's not a bug. However, the basic process to figure this sort of thing out always includes checking for the hardware used ... the media used ... any effects used ... any third party effects, plug-ins, or software used ... anything that could be part of the issue. Not to blame that item rather than the PrPro, but to establish how this situation can be happening within PrPro.
I am not having this issue on my Win10 Pro machine. I've frequently had issues migrating projects forward in the past, so I NEVER assume I will be doing so. I've always had several previous major versions up. However, I do test after upgrading. I'll make a duplicate of a project file, and typically create a new project in the new version, import the previous project file, and see how it does. This time, I got the typical ... meh, not so good. (Some things weren't imported properly or at all.)
But I also tried simply opening a duplicate project file (which is normally not the preferred practice for migrating projects) ... and the project came in perfectly. At that point, I duped all current projects, and in turn, opened them in PrPro. Without issue, rather to my surprise.
I rarely use any of the included LUTs or Looks, but have a fair number of ones I've created, both in PrPro and especially in SpeedGrade, and a few purchased. As I was one of the lucky ones attending the MediaMotionBall (MMB) at NAB this year, I got a full gratis license to EVERYTHING Red Giant sells ... so you better believe, I will soon have a ton more LUTs/Looks/Effects loaded on my rig.
Depending on how I use them, I have used the Technical folder to get a LUT placed so I can use the drop-down & get right to it, and also the same thing in the Creative folder. And some LUTs/Looks I store elsewhere.
All projects came in fine. All my projects use a number of LUTs. On my computer, again, Win10 Pro.
On some other user's systems, clearly including yours, this is a real freaking pain. So we all want the development team to nail this and fix it, right? From what I've seen of the posts here, this is probably more common on the Mac side, but not necessarily totally Mac-centric.
So ... again ... information on the OS, GPU, media type, effects used, plug-ins & third-party apps that have touched the media, including the origin of any LUTs/Looks affected by this, and the location on the computer of same, is all of use to puzzle this out.
One thing I have seen a couple users do that "fixed" this, was remove their own LUTs to a folder outside the Program files in the older version project, then migrate the project into the latest PrPro. Yea, that's a pain if you use many of them ... but it seems to indicate there's something that changed internally in the latest release of PrPro and how it relates to the LUTs/Looks in the Technical & Creative folders. How this was caught was when someone realized that some of the LUTs used in a project worked, some didn't ... and found that the ones the did work were stored in a folder on their desktop. Something added quick they hadn't taken the time to "place" in their normal fashion.
Others have gone through a project, and for every flipping clip, set to "none" then back to the proper LUT/Look, and voila, it was working. Again ... a royal pain workaround.
We'd all rather this just didn't happen again ... ever.
Neil
51
Replies
AdChoices