Right now, save only saves the currently active project. If the Production window is highlighted, it should save all projects. An issue I've run into is if sources are added to a project (i.e. sources) and it doesn't get saved, the next time a sequence project opens that uses those sources, the files will be created in a "recovered files" folder. Which is fine, but now the clips are linked to that.
Secondly, if you open a project that contains sequences, and Premiere has to locate media, it will have to locate the same media again when you open another project that contains those same files.

We use Streampix to capture 2k, 4k and 8k 12bit RGB file sequences on a film scanner. Streampix recording software is good, but their color correction software is weak. So we need Premiere Pro or similar color correction software to correct and export these film scans to other mezzanine codecs.

If this codec was only supported in the Premiere Pro I can imagine that many scientific camera users would be interested
https://www.norpix.com/support/cameras/supported_cameras.phpleast

Here is a sample of 16mm film that has been digitized to this .SEQ file(apologies for the large file size): https://1drv.ms/u/s!Ak6HT6WNfRoS_QagTD6Yr3is5TuR?e=drgd3u
d
There are at least 1000 Streampix camera capture users with the same problem as discerned from this page of supported cameras: https://www.norpix.com/support/cameras/ ... ameras.php
We don't want to render the .SEQ file before color correction, we just want to do simple color correction of the .SEQ file, then deliver to other formats.

I tried searching for this, and didn't find a post, though there must be one. Please update the use Icons for all Adobe applications, not just Premiere Pro so they show the year in the icon instead of just Pr as it shows for Premiere. Sure I can hover my cursor over the app and it will tell me if it is 2019 or 2020, and I can hack each version to put my own custom icon with the info, though every update kills it. Why should 2019 and 2020 have the same icon? I often have to use different versions depending on the job, so the iCon for the app in the dock should be different. Please consider adding the year to the letters for the application to the application icon!

The option to export a FCPXML file for project work sharing between FCPX (because captioning is trash right now in PPro not so good in FCPX either but Scenarist works with FCPX) This option NEVER works. Always errors out, I have never gotten it to work with any project, not once. You might think the xml files are written properly and I just need to change the extension, but nope, Final Cut doesn't recognize it as proper FCPXML file. Please fix this issue, I was pleasantly surprised to see this kind of interoperability only to be sorely disappointed when I could not use it.

Because of rampant bugs in the latest updates Premiere will sometimes close out of nowhere and you lose work (and time and money). When you reopen Premiere, selecting a specific project at launch, rather than load the specified project, it asks if you want to reopen the last one. Why? Why not just open the project I selected to open? This window is a waste of time. Again, we could walk away waiting for our project to reopen only to come back and see it's not open as requested, and instead we have a window that asks if you want to open the last project. Can you add a feature where this changes? It's frustrating enough that a project crashes so at least let us open a specific project without seeing any bologna like a window asking to reopen something else.

Thanks.

I think that the full upgrades are released to often. One .0-verison each year is too often and has proved to be a very problematic procedure each year. Pr CC 2018 was problematic when it was released fall 2017 but today it has received several patches and works fine today.

Approx three months after the last update to Pr CC 2018 it is time for the brand new full release of Pr CC 2019 and we are back to square one once again with crashes, sometimes it won´t even launch, new bugs, etc.

We don´t need a full version each year, it would be enough to have a full version alive for two to three years and during that time release patches to fix bugs and stability issues and maybe new featrures along that path. The applications are so mature today so there is no need for "exciting versions with revolutionary features" releases of not-ready-for-prime-time-software.

During the Creative Suite years each full version had to be really good, otherwise it wouldn´t sell as good and it got consequences if it did not sell as expected. This was good since the goal to release a good version was high. Today the money flows in to Adobe no matter what, so the goal to release a good stable version is not as important anymore and that certainly reflects what we see today, new versions that are not near ready for prime time. It dosen´t simply matter anymore since Adobe could always recommend user to downgrade.

I think all software companies do the same thing, release new versions too often and everytime there are issues in the new version that should have been sorted out in the beta stage. But it seems more important to release "something" than to wait until the software is ready and really release something good and usable out of the box.

No one demands brand new versions every year. No one demands new and exiting features that don´t work as expected at launch.

What people demand is stable software that has been thoroughly beta tested for a long time before release.

Bottom line:
Just don´t release new buggy versions each year since there are no need to do it. A new verison every two years is enough, if it has been thoroughly beta tested that is.

<end>

Entering file metadata on multiple clips at once seems to cause Premiere to crash for some of us. (See this issue reported almost a year ago: https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/36933751-bug-entering-xmp-metadata-in-batches-causes-crash)

It seems that one way to resolve this issue might be to create a setting that forces Premiere Pro to write XMP metadata to sidecar files even if a given file format supports embedding it within the file.

Even if this issue were to be fixed, it seems like sidecar files would be less error prone and I personally would feel more at ease if Premiere wasn't altering my video files in any way, even if just for metadata.

The option to export a FCPXML file for project work sharing between FCPX (because captioning is trash right now in PPro not so good in FCPX either but Scenarist works with FCPX) This option NEVER works. Always errors out, I have never gotten it to work with any project, not once. You might think the xml files are written properly and I just need to change the extension, but nope, Final Cut doesn't recognize it as proper FCPXML file. Please fix this issue, I was pleasantly surprised to see this kind of interoperability only to be sorely disappointed when I could not use it.