[Merlin Vandenbossche]

This is little information to go on, a lot depends on codec and the type of footage you use.

Performance is very buggy. Projects freeze up and crash

It helps to reset your preferences (SHIFT + ALT while launching the app) and completely delete the dreaded cache folder in your user library. Always try those first. And try to create a completely new project and re-import the old one completely, do this especially if you updated your projects from an older version.

folders get deleted from the project,

This is a bit vague, you mean bins are deleted?

little things like title safe windows are broke

This is a bug, I can replicate it. You’ll have to wait out for a bug fix.

workspaces won’t save properly

Make sure to disable the ‘import workspace from project’ option under the workspaces menu. If not you’ll always carry the workspace of the person who last saved the project. Maybe try deleting your old saved space and re-save it.

external video via Blackmagic card is broke, etc…

Make sure to install the latest ‘Desktop Video’ drivers from the download page of Blackmagic. PPro needs the drivers to send a signal through a blackmagic card (Resolve may have these built in?). And remember you can’t just send any timeline through every card / mini monitor. Some support 4K, some don’t. Sometimes the same footage placed in a 1080 timeline sends the signal when a 4K timeline doesn’t (again, Resolve maybe scales this automatically since it is designed by blackmagic?)

Good luck! It sucks to have stuff go wrong like this! 😡

[Merlin Vandenbossche]

Knowing what type of footage (resolution, codec) you are cutting and what storage you use, could tell me more. But since you seem to still have decent playback using CC 2018 on your setup (this is what I understand?), it’s not likely to be a problem in this area.

The change to CC 2019 did involve a number of performance related updates, so you could also try disabling those again to see if it helps to behave more like CC 18 again. These include:

– Disabling ‘Enable Display Color Management’ under Preferences – General
– Disabling ‘Enable Accelerated H.264 decoding’ under Preferences – Media
– Try switching back to OpenCL under the ‘Renderer’ setting found in your project settings (since CC 19 it is generally recommended to use ‘Metal’ as a renderer on Macs)

But also again: make sure to also try the preferences reset and cache delete I mentioned in my previous post.

On a closing note, there are two more things that tend to cause trouble after updates: Third-Party plugins and GPU drivers. Make sure to update any third party plugins to their latest versions as well (stuff like Red Giant plugins, etc.) and I assume you are not using an Nvidia GPU. Nvidia and CUDA drivers always need to be updated manually, but won’t work on Mojave anymore, since Apple no longer supports it.

[Merlin Vandenbossche]

Thanks for the tip. My nMacPro has Red Giant plugins, but my iMac system does not. The same shutdown occurs on both and not really when doing any specific task or when using a specific plugin. It can occur pretty much everywhere: scrubbing, when moving clips, even when idle. Sometimes I go a day without any, sometimes there are days when I get shutdown three or more times.

Luckily it hasnt cost me any lost work yet, but it is very very annoying to know it can just shutdown any time. It is not normal behaviour.

[Merlin Vandenbossche]

Hey Jim,

We once had a very persistent thing like this involving audio. Timeline would play fine, but every export this one file went missing (like ‘pending’). I believe our eventual workaround was to transcode the piece of media so it would become a new piece of media (in case of this audio just from WAV to WAV actually). Then re-import and re-edit it in (I believe we did manually re-edit, not relink).

Maybe premiere does not recognize the header/start of this clip (anymore) during exporting and thinks it pending/offline. So maybe another instance (re-encoded) would. Good luck!

Merlin

[Merlin Vandenbossche]

I’m not familiar with either Vegas or MPEG-TS files. Maybe the extra audio tracks are from separate streams in the MPEG, maybe a tool like MPEG-streamclip allows you to decode those tracks into regular AIFF/WAV? Just thinking out loud.

The above solution I mentioned works for me when I come across audio recordings or videoclips that have multiple audio channels that I need to have separate.

[Merlin Vandenbossche]

If you toggle the left most icon of this set of icons (the timeline icon that is crossed out) (to the left of your timeline), you can toggle whether to add sequences as nests or individual clips:

screenshot2014-12-11at18.38.35.png

[Merlin Vandenbossche]

Colin,

Under the preferences for audio you can change the way Premiere imports audio by default: under the tab ‘Audio’, change the ‘Default Audio tracks’ for stereo and/or multichannel to ‘Mono” instead of “use file” or “stereo”; and then try re-importing the clips. Hope this helps.

[Merlin Vandenbossche]

I’ve found in the past that changing the mode from Subspace warp to ‘Position, Scale, Rotation’ and/or reducing the smoothness to less than 15 percent helps to reduce the wobble. Maybe worth a try here as well?

[Merlin Vandenbossche]

Johan,

What you could do is add grain to only the background layer in AE, using the ‘add grain’ effect. If you lower the ‘intensity’ to something like 0,200-0,300 ; the grain will hardly be noticeable but it will help better preserve the color gradients in the final render of this clip. If you have used the ‘generate – gradient ramp’ effect to create the background gradient, you can also combine the above grain with an increase in ‘Ramp Scatter’ to 300+.

A combination of this has always helped me avoid banding in the past. Rendering in Animation codec should be fine. ProRes 444 or 422 (HQ) should also suffice.

Good luck!
Merlin