tl;dr I'm ok with new, but Adobe's issues for me are piling up and negatively impacting my productivity. Neil, thank you for the response. I understand that new methods and ideas take time to properly introduce and enhance (ie the EGP). That's a step forward imo, and understandable (albeit annoying) when issues arise with new pieces. I don't feel that's what's happening here. /rant You mention inter-operability, and software interacting "more naturally". Correct me if I'm wrong, but Libraries is a core concept of inter-operability and working more naturally: create an element in one place, pick it up in another. And Libraries (color themes as a specific), were working in Premiere Pro, exactly as described. I could create colors in one place, then, say I needed to create a quick one off title, I could quickly - without bouncing between programs - create simple shapes, correctly choose the color within the palette, and be done with it. It worked. The above thread doesn't mention any "inadvertent behavior", just that they didn't expect it to be used like that. But it was, and it was working correctly! Now, that functionality is greyed out (not removed, but disabled). I either have to use a work around to do the same thing, and duplicate content in Libraries for the same process, or bounce between whole different programs. I didn't have to do that before. That's a step back, and if the posts in this thread tell the whole story, it's a needless step back. Something was working, Adobe took it out, and didn't replace it with anything better. Concerning dumb/slick/thank Heavens! what I'm describing I think would be a universal response; how would you feel if a feature you were "thank Heavens!" for was inadvertently turned off because - despite it having been working - they realized it was functioning properly without them realizing it? (Again, that seems to be the going story here. If it surfaces that this specific Library functionality was breaking more important features I'll grumpily admit they were right to turn it off.) So I think Ihear you say that I should trust them. But they've been losing my trust, turning things off that were working, making me find workarounds, discover that certain bits that are available in one place aren't in another, and overall just fogging up the user space. Example: Did you know that the lens distortion removal isn't in After Effects? So if I want to properly track motion in a corrected GoPro shot, I have to first render it out via Premiere Pro, then send it over After Effects? Not the end of the world, but the lens distortion effect is new, gpu accelerated and all that, but it's not in both effects libraries. It's these odd little details that just grind against efficiency. OR, that I have an older GPU that needs replacing. It's no longer supported. I get this, it's on me. But instead of telling me anything that would lead me to that conclusion, I'm instead given a 10 digit error code with only the vaguest of details after scrounging the forums. It doesn't need to be like this does it? Adobe can easily check what my gpu has in the way of latest driver update, code support, what version of Cuda, etc. and say: "hey, this card won't do this. It's old. Turn it off." Inter-operability: how about being able to direct all Adobe software to use a certain drive as the cache drive? Instead, every project, across all their software, every time, I have to hold it's hand to tell where to put it's files. It's exhausting, and takes away from me being able to do my job. OR; it seems I have an MT-Extra that is invalid. Problem is, I have not fon anywhere with that font name. But premiere pro is pointing to it and saying it's invalid. And I'd love to clear it properly to remove the invalid font. But I can't, because ppro isn't telling me where it's pointing. Not in my system fonts. Not in TypeKit, or any other font library of mine. So instead, I have to see a "!" all the time in premiere pro. And it pops back up when I switch into different workspaces. Personally, I despise seeing a blinking "!" that I can't clear. OR heaven forbid I don't update all my projects when there is a new release that requires the .prproj to be updated for them to work properly. Because if I need to get a certain bin of files from one of my other projects, but don't know that, and instead it takes *forever* to make the dynamic link to see the sequences, it doesn't alert me that it's not able to read it. It just spins, and spins, and spins... no alert. No reason. But it looks like it's working. (And, why does the "Import Premiere Pro project" start conforming files while I'm trying to select the specific sequences I want? The program doesn't even know if i'm going to use those files, but it's more than happy to take potentially needless cycles instead of just letting me pick what I need? And, what about warp stabilizer requiring that the sequence be the same resolution as the clip? Either 1) what does it even matter, or 2) please create the correct sequence and nest it for me! OR, somehow allow me to create a nest of the clip that doesn't inherit the properties of the sequence it is coming from. But none of those options exist, and I have to do it manually every.single.time. Development: perhaps development is par for the course, maybe I'm just following it closer, but they've had some significant issues in the last couple years. 2016, it was reported that the Apple CC2016 install was inadvertently deleting users folder that was closest to "A" in their system folder. That could have some significant repercussions; why would that even be part of an install process, to "find folder closest to A. Delete."? And 2017, if the media cache was cleaned/purged, it would delete/corrupt related project files? A significant issue, how or why would a cache file "reach up" to delete something like that? (I really don't know, but I think a "first do no harm" philosophy is a good starting point.) And that doesn't include odd, simple gaffe's like somehow renaming Hue for Saturation (and vice versa) in the Lumetri panel - which is harmless, but again, it just leaves me scratching my head, and wondering how and why did such a mistake get in before going out to ther very sizable user pool? I'd be okay if Adobe went to an open beta approach to their releases, or maybe somehow modular (don't get me started on VR/360). The above issues are exactly what betas are for: find and squash the bugs and odd glitches that happen when big updates occur. There is nothing wrong with betas! And with the last 2 years of releases, it would seem that Adobe could've used additional QC and beta work done so it isn't errantly deleting it's users' content. But instead, by releasing it as the next version, they're implying, "This is stable. This is the one to use as a daily driver." Well, CC2016 wasn't for Apple users, and CC2017 wasn't for Window users... and two releases year after year, people could infer that 2018 won't be either. 😕 /rant. Sorry man for dumping all this. I'm just... tired that nearly every time I step into Adobe's programs, I have to do so much work to do anything. It didn't used to be like this. I could reliably bounce between each of the programs, and with the flip of a toggle or two, know how it was going to respond. Now, I'm just relieved if my project opens without having to reconform, relink, update, reset, purge, or toggle something. It's really, really tiring.
... View more