Serious Bug Report:

For both Premiere Pro and After Effects I have found the same bug which has made it very difficult to use both programs. The Program monitor does not display the content it should be displaying unless it is set to a very large size (a larger size than I normally would set it to). What this has meant for me is that in order to accurately see what I am editing I need to use dual monitors and give the program monitor its own monitor and make it full screen. If I make it any smaller it will immediately stop playback and freeze, often instead displaying weird glitchy repeated borders of the program's interface.

I have checked that it is not a problem with my current hard or software and would love for adobe to update their programs and hopefully resolve this issue.

Thank you!

I am noticing that certain clips in out ranges in edited tirmeline do not match the marked in/out points on source clip when using match frame or on XML export. The XML export is then causing all clips to be off by 1 frame or more when conformed in an another application that reads the in/out from the xml. This appears to be something new in cc2018 and only seems to happen under certain situationsThe only fix i can find is to match frame the hit o to red in point and replace media in timeline. I think this is happening when extending or tirmming clips from the timeline rather than in the source monitor. This bug is causing us big problems. So any advice on how to fix this would be useful.

Some fx will impact render times 5 x when they're placed at the top of the fx stack (EG: neat video will be 5 times faster if applied first [top fx] in the effect control panel).

I suggest there will be an "analyze effects" or "Analyze Sequence for render performance". Once clicked the software will test a couple of frame renders of each clip and thus able to suggest effect stacking order for best performance.

Obviously with the help of community and ML the software can recommend some best practices on the fly based on it's knowledge.

User will be able to accept the suggestions, reject it, or test it (As on some cases the user will wish to preserve the original fx order because the order of fx can change the look).

12.1, and 12.1.1 have been an absolute nightmare to work with.

We've had more crashes, more slow-downs, and more truly frustrating issues with these two releases than I can remember. Unfortunately, we've been dragged up and locked into these versions, so it's not like we can just revert back to 12.0.1 and happily work away until this nightmare cycle is over.

From regular hard crashes when changing to custom workspaces (not to mention workspaces just no longer working), to other random hard crashes because...well...just because. To the excessive slowdowns after a period of time when generating proxies in the background (hello beach ball!), to audio effects randomly resetting when duplicating sequences (a truly frustrating, and in some cases, significantly time-consuming bug), to the solo/unsolo bug, to having your preferences randomly reset for no good reason (that one didn't even happen after a crash. I just exited the program, and when I went back to it, my preferences were all reset to factory) to any number of other frustrations (take a look around on the feedback forums, the problems are easy to find).

This has honestly been the worst release version of Premiere that I can remember in a long, long time.

I think the problem is made that much worse by the fact that we're locked into this version if projects are generated in it (hello projects that clients send in!). This time we can't just bury our heads in the sand and ignore it.

We have three full-time editors here, and all of us are regularly ******* our heads against the walls.

This version cycle is utterly horrendous. Can we please stop focusing on throwing in more features, and just make sure that the software is solid instead? When these issues started cropping up in beta (which I'm absolutely positive that they would have), should the priorities not have shifted from implementing new features to just making sure that this cycle wouldn't be a nightmare for the people being forced into using it? Or could you, at the absolute least, have made it that we weren't getting version-locked?

First and foremost, we need reliability from our NLE. Nothing screams professional more than having our software crashing regularly with clients in the suite or having to rebuild our audio effects while they're checking their watches.

It should be better than this.

I work for an in-house agency so many projects include reusing footage from previous projects. Having multiple projects open to hunt for footage is really helpful, however, when I find a great clip from a sequence is project B,C, or D and copy it into a sequence from project A, upon import it duplicates the whole folder structure that clip was in. I organize all my projects mostly the same way so I get a new "Video Media" folder for every clip I import from another project. It would be REALLY helpful from a project organization standpoint if I had the option to drop that clip into the same folder as the rest of the media already in the project, and have a sort of "parent project" attribute to let me know that clip came from another project.

Currently the options are a proxy folder next to the original source or a custom folder.
There is no control over the naming convention.

We have a workflow that would work better if we could store the Proxy in the same folder as the original (no sub-folder) and a naming convention that tags a "-Proxy" (as opposed to a "_Proxy") to the original name.

Overall what we're looking for is a more sophisticated Destinations system for PPro and AME.
Way back in the FCP-7 days they divided export presets into two types: Render and Destinations.

Perhaps Adobe's "Ingest" presets are related to FCP's "Destinations". What Adobe's lacking is the sophistication of the location and naming conventions -- an ability to control prefixes and suffixes, locations and dynamic options. Or is that already in there, and I'm somehow just not seeing it?

Discussion posted here: https://forums.adobe.com/thread/2510928

I have been working (since many years ago) with Adobe Premiere 4 version until now with CC. When the CC version started I ran into the fact that when sliding with clips the shifted clip could be placed over another clip. Only when using the Ctrl button it is possible to place a clip between the other clips without overwriting them. Overwriting was impossible in the past. For years now I have run into the problem that working with the Ctrl button does not always go well, so the adjacent clip is overwritten. Then I have to do it again and that takes time. I do not understand the value of working with the Ctrl button. In the past you moved a clip and could automatically place it between other clips. That always went right. If you like to push a clip over another clip, use the B button. That always works perfectly.

Is it possible to adjust the software in order to set the default value of certain effects yourself. With Warp Stabilizer the default value is always on Smooth Motion. This is useful if you work a lot with an action cam. I use No Motion in 95% of the application. Now I must always set it apart. It would be much more convenient for me if No Motion Default was set.
The same applies to Speed / Duration. I would like to see Optical Flow set there and not Free Sampling.