Encore une MAJ qui crée des problèmes au lieu de les régler

Thanks @JP-49 for the update. Glad it's working fine at your end. Do share if you face any problem in future.

Hi @JP-49 ,

Sorry for the problem. Have you tried creating a new project in Premiere 23 instead of opening the same project you created in Premiere 22, just assuming ?
Can you try resetting the plugin loading cache(Hold shift key and launch Premiere) and then use these effects in Premiere CC23 with a new project ?
If it still doesn't work, please share the Plugin loading text file from  *\Users\*\AppData\Roaming\Adobe\Premiere Pro\23.0 folder.
At last, you can try updating the Nvidia driver too.  The latest studio driver on this card seems 535.98. We have tried a few Nvidia GPU systems locally, and all effects seem to work just fine. We aren't aware of any such customer reports where many GPU effects won't work in Premiere like in your case. There seems something specific on your system. 
Let us know how it goes. We will continue to look at it and provide updates. 

Thanks,
Mayjain

Hi.

These three effects (at least) do not work:

1) Video Effects->Adjust->Levels->(RGB) Black Input Level,

2) Video Effects->Basic 3D-> Swivel,

3) Video Effects->Transformation->Crop->Left/Top/Right/Bottom

My hardware is the following:

-MoBo: Gigabyte X570 AORUS MASTER,

-CPU: AMD Ryzen 9 3950X, 16-Core, 3501 MHz, 32 logical processors

-GPU: NVIDIA GeForce RTX 3060, version pilot 528.49

-OS: Windows 11 family build 22621

Thank you for your thoughtfulness

Jean-Paul Guillois

To make this useful, please! ...

1) what effects aren't working,

2) what's you hardware (CPU and GPU and GPU driver number)

Neil

Hi everybody.

I've upgraded Premiere CC22 to Premiere CC23. I regret.

The reason is that with Premiere CC23 lots of Video Effects does not work. Mainly those using the Accelerated Effects.

So I went back to Premiere CC22 and again everything is OK with the same rig...!

Because of that I am not so confident with Adobe than I was.

All the best.

Correcting a few mis-assumptions there. The typical user expectations of how they use crash reports,  from what I've been told by staffers. As naturally, I made most of those assumptions also. And after that, my own experience. Which you also made some assumptions about.

1) crash reports ... they can't track YOU from any crash report, which is intentional. They don't want to have user-descriptive data in their system for those things. There are all sorts of international laws and regulations they could run into at some point if they did, so it is simpler and safer simply to not take the data to begin with.

So no, not even my crash reports over the years have been linked within their system to me.

Although one dev told me that, due to my practice of filling out the descriptive part with clearly bullet-pointed details, they had learned to recognize my crash reports. But the vast majority of posts don't have any added data.

So they don't know who any crash report filer is, unless you put in an email and click they can contact you. But even then, from what I've been told, that's just an email included for response in that report, and even then, used if they think it useful. It isn't linked to your user subscription.

2) As one would assume from reading the above, I've had my share of crashes and/or bugs. Daily user for a decade, well ... yea. And at times, I've been hit by one of the ones that took them MONTHS to fix, so I've had to wait as long as six months a time or two, before I could update.

I don't get as many as some users do though. Which is partly because of learning, through painful trial and error ...  some "clean practices" that seem to help.

First, I don't install ANY games past the old Windows 7 Solitaire on any machine I'll run the Adobe video apps on. Because gaming apps most of the time will add special video and audio "helper" apps and drivers to speed your play along. Which can cause all sorts of weird Hades with video editing/post apps.

Second, although I'm on a 24 core Ryzen for my main rig now, I stick with the Nvidia cards. Simply because they tend to work better with Premiere. And as I work Premiere, AfterEffects Audition, AND Resolve ... they work well with all those apps.

I have ALL my drivers on manual updates, and only update if I need to. If drivers are working fine, they stay that way. I'm often quite a few drivers "back" for a while before I update.

Third, I've got the OS/Programs on one Nvme drive, ALL video app cache files on a second internal Nvme for best operations. And all projects and media on fast internal large SSD drives. Exporting to large internal SSD drives. It ... just works better.

Fourth, the only 'network' stuff I need to deal with, is with my partner Mo in Cape Town SA. I'm in Oregon, and our joint projects are "housed" on Amazon S3 servers in London. We use LucidLink to provide their magical transport services. That is the only service I've personally used where online storage is actually ... magically ... useful for real video post production.

L-L creates a "virtual" drive on each machine, Macs or PCs, doesn't matter ... and you import the projects or media files from that virtual drive. Most media can work over the net if your speeds stay above 150Mbps, but if your speeds drop or too much latency occurs, you can "pin" a file, and it will be listed as on the virtual drive but actually loaded onto your physical machine.

I avoid OneDrive like the plague it is ... and only use DropBox and WeTransfer when I'm working with someone who wants to send me a file or ten for working on them. And I'll send them back after fixing/whatever. No folders hold any working media within those utility's grasp.

Fifth, because I'm monitoring this and the LGG and BlackMagic forums, I see the posts about current issues. Therefore, typically, able to avoid many of them.

Neil

Thank you Neil,
Adobe has all the info about my configuration due to the numerous crash reports sent.

And I'm sure that as an "expert" you've never had to complain about Première's stability. You're very lucky!

Personally, I think Adobe should put a lot more effort into delivering products that don't create problems where none existed before.

Ok, as another user, I understand the frustration.

But sadly, that is a totally useless post.

PLEASE ... give what's going wrong, and what your computer specs are and media/workflows. Without that information no one else on the planet has a clue what's happening.

Or what needs fixing.

Remember, there are several million daily users, most of whom are working away. So what's hammering you is not affecting the majority of other users. We all need that information to figure out what the hay is going wrong.

Neil