Team Projects and 2018 Update Issues
Hi there! First time poster on the forum.
My team and I are having some difficulties with Team Projects and we’re hoping @Ramesh_Encore might be able to help. We are currently cutting together a documentary on Premiere Pro, but we have unfortunately run into issue after issue. This project is a very large movie with many hours of footage that is being worked on by an award-winning filmmaker. If you are located in the Austin, TX area, we would be happy to exchange a movie credit for in-person assistance with our technical problems.
Get / Share changes
First, we have encountered some problems with getting and/or sharing changes with the Team Project on different devices. When attempting to “Get” changes on a device, the process will often stall and show no sign of ever completing -- forcing us to quit out of Premiere entirely. We know this problem to be unrelated to a lack of RAM or processing power (some of our machines are brand new). We have encountered similar issues when trying to “Share” changes as well.
Relinking the same media again and again
We have had an ongoing issue where we have been forced to repeatedly relink media. It appears to have something to do with older file formats / codecs. Specifically, we have a lot of P2 footage and we have noticed that individual clips will randomly go offline.
Recovered Files
This issue has to do with bringing in timelines from an old Team Project file that had been corrupted. When attempting to bring in a timeline from the corrupted project into our current Team Project, Premiere automatically creates a “Recovered Files” folder that contains copies of the clips used in the timeline from the corrupted project. This is problematic because (1) these files may be corrupted and (2) these “Recovered Files” folders are unnecessary since we already have the clips used in the timelines in our new project. We have tried to remap the timelines and attach the clips in our current show with the hope that this would allow us to delete the “Recovered Files” folder. When we deleted the “Recovered Files” folder, however, the clips that had existed in the folder would disappear from the timeline we had just remapped. Is there any way to avoid this?
Relink Media Automatically not working
When attempting to bring folders of clips back online in Premiere, we have been forced to relink each clip individually due to the failure of the “Relink Others Automatically” feature. The folders on our external drives mirror the folder structure in Premiere and contain the same number of clips. The failure of this feature has forced us to spend a massive amount of time relinking clips individually.
After Updating to Premiere Pro 2018:
System Memory Full
After updating to Premiere Pro 2018, we ran into the following issue. When attempting to open the Team Project on some of our devices, the process will stall during the “Loading Assets” phase. Eventually, an error message appears that reads “System Memory Full”, and the project will fail to open. This error is confusing because the devices we are using to open and edit the project have more than enough available hard drive space. We would greatly appreciate any thoughts as to why we might be encountering this error.
Playback Lag
Recently, after updating to Premiere Pro 2018, we started to experience some stuttering and lag during playback. This is odd because the video files are located on the device’s local drive. We are not sure what could be causing this.
Premiere not detecting .mov files going offline
After the update, when we attempted to play .mov files in our Team Project, the files failed to play. According to Premiere, the files appeared to be online, but we were forced make the media go offline and manually re-link it. We are unsure why the media failed to play and why Premiere failed to detect it.
Failure to Use Team Project on Small Project
Finally, we tried to convert a small project file that was unrelated to the documentary into a Team Project. Once the project was converted we attempted to add collaborators to the project but were told that this was not an available feature for us. It has never been a problem until this small project. Any ideas as to why we might have been denied this ability?
Most, if not all of these problems are occurring on two of our main computers. One of which is a 2017 MacBook Pro with 16GB memory and the other is a mid-2010 iMac with 12GB memory.
We would be extremely grateful for any advice you can offer on these matters. Thank you!
