Thank you for reaching out to us at Maxon! Here's their updated process for Windows: It's cheaper to inconvenience people than provide legitamate support. But because Adobe won't help and passes the buck, so hopefully the other companies have their work around fixes to deal with what's actually an Adobe issue. Although contacting the third party is probably the correct idea, but not because they did anything wrong. I would prefer to not roll back to a previous version or moment in time, and instead have this issue addressed.Īgreed, this is usually the case. Yes, I did try to restart, uninstall and reinstall, to no avail. Both Creative Cloud Desktop and Maxon App are their most recent versions. I am running Creative Cloud on a windows 10 pro 64 bit system that is incredibly up to date and fairly powerful. Through some trial and error, I concluded that I am able to hold and press the ENTER key to get past the error during program load and actually open a project with Universe effects already applied in the timeline (albeit it without any of them working), which is nice as for a few panicked moments I thought I had completely lost an edited sequence.
Given that, this feels like an Adobe issue to resolve and NOT a Red Giant /Maxon problem. Now, both pre-existing projects with Universe affects applied to the timeline are throwing the " Error connecting to Universe runtime" code, AND brand new projects are doing the same when trying to apply a Universe effect to a new sequence / clip.
My experience like I'm sure many others out there is that my Red Giant Universe, now under the Maxon App, was completely up to date and working perfectly as of this afternoon with the previous version of Premiere Pro until I updated through Creative Cloud. update, I am unable to access the Red Giant / Maxon Universe plugin.
I thought that starting a new, updated thread about this might be smart as it directly relates to the Premiere Pro v 22.1.1 update.īasically, as of about 4 hours ago and upon allowing Creative Cloud to install the 22.1.1.
0 kommentar(er)
