Hi was using Mettle Skybox plugins with no problems in the older version of Premiere. Now, after the update I get the "this effect requires gpu acceleration" on screen. The GPU Acceleration (CUDA) is on.
If I open the old version of Premiere (17) the Mettle Plugins are gone.
GPU Drivers updated to latest driver
Windows 10 latest update
Ryzen 7 1700
GTX 650 Ti Boost 2GB VRAM
Please please please I'm halfway through a project
Sorry for the trouble with the effects. Please try with a new project & check if an error pops up.
The location of Skybox Plugins are Video Effects > Immersive Video > VR.
Also, try to import the old project file into new project & test.
This is so bizarre. I'm having the same problem here using the VR Rotate Sphere effect. But the thing is, I added a transparent png (and tried tif as well) of the nadir logo for the floormat on the video track above the video, as I have always done, and that's when the error came up. But when I remove the logo from the layer above the video track, the error disappears and the rotation is how I set it. Here's a before/after of when logo is placed, and when I remove it.
Adobe please help as I'm in the middle of several 360 video projects that I have depended on the Mettle Plugins for.
With that being said, thanks so much for being all-in on the VR video tools and focus!
i think the png never worked well well well i was using also .tiff mybe if its all psd or jpg goes faster but i was trying things fast ..
Thank you !!
Yeah, jpgs work fine, but they're also not transparent background, i might have to create a jpg at just the dimensions rather than a transparent overlay like i've been doing for the past few years. Hopefully this is just a bug and Adobe will squash it.
[UPDATE 11:00pm PST 10/20] So my bad...at least on Media Encoder. I had Media Encoder set to no GPU acceleration. I changed that and it output fine. Hope that helps anyone in the situation...
[UPDATE 10:45pm PST 10/20] Update to my post above...ok, someone from Adobe please address this.
So while editing, I was able to use a jpg instead of png or tif overlay for the nadir which removed the GPU acceleration band, and the edit looked great in Premiere, but when I output using Media Encoder, all the effects are missing (Rotate Sphere) and the GPU acceleration band is back on the video.
Please help. Please.
Attached is a screenshot of the player screen on Premiere (top), and then how it looks on the output (bottom).
Hi. I'm having the exact same issue. They worked fine when they were Mettle plugins in teh previous version, but when I try now, it gives me the same issues. Here's a screenshot using the VR Plane to Sphere effect. I've tried both with OpenCL and Metal GPU acceleration project settings. Not sure what to do here. And I don't have an NVIDIA as far as I can tell. It's an AMD as far as I can tell. The image is a 360 jpg from a Gear 360, and the overlays are both transparent pngs.
I am having this issue. I have tried every option in this thread and nothing works. Is there another known work around yet. This wasn't happening in 2017 version of Premiere.
Ok, the problem is solved when we import the new project after. But the operation is repeated each time we close after effect ... what is this shit.
What if you are in the middle of a project (or have to go back and fix some issues in a previous project) and you can't open it in an older version of PrP?
Also, in reference to the first answer gregsonfilm when I go into File/Project Settings that selection is grayed out and it won't allow me to make ANY changes.
Why does it always seem these updates (especially when you have to uninstall the older version) create more errors when working in projects created before this great new Adobe update?
You don't have to uninstall prior major versions (different build series like 12.x or 13.x). In fact, they have finally changed the default for installing new versions. Finally.
Keeping a previous major version was always an option if you knew where to look.
If the Mercury acceleration options are greyed out it is because you don't have a usable GPU in the computer. PrPro has higher demands for the GPU capabilities and vRAM than it once did.
And it is often better to work projects in the version they were created in. If you try a new build of the "current" build series, use a copy of the project file in the newer build, don't use your only recent project file.
That way you always have the project file to go back to where you were.
When migrating to new build series, use a copy of the old version project then instead of opening it, create a new project in the new version, then using the Media Browser navigate to the previous version project file, then import that project's assets. Seems more reliable than open/convert.
maybe , it is always a good idea to look at the new "benefits" called "requirements" of new versions first.
Really interesting for me , is, that folks , including adobe specialists , are discussing this issue here for days now.
Is there no one who ever has heard about/ read the GPU-V-RAM Requirements of AT LEAST 4GB on OSX computers ? (and if I'm remembering well, I have heard this as well about the win-machines)
I suppose, that this planned behaviour is internal common knowledge at adobe staff , isn't it ?
so there is no weakness of GPU , no age of nvidia series ... it is simply the programmed lack of V-Ram...
Adobe seems to have made a move away from midrange mass-software for self-made well equipped ps's , to professional top-range, expensive computers (unfortunately without keeping step with those requirements ... or , are we back in the good old days when I started with Mediacomposers on Apple 2FX computers ...pure offline system / steenbeck replacement (who ever remembers that) ...reminds me always if I see a recommendation like ...use proxies ... pure offline editing).
My current rig is a 6 core Intel based setup. 32GB of RAM, something like 6 internal SSDs and a couple large spinners, and a 1060/6GB. Total cost was around $1800.
Been using it almost 2 years, and looking at a new rig as I'm starting to work with some 6k/up RAW & log media.
Cost of doing business. And, 40 years of running our own business, I have to justify the cost. No finance officer to approve a budget, just us ... can the income from using it pay for it plus make a better bottom line?
Copy link to clipboard
If I open a new project I get the same error:
I have also tried importing the old project file into new project, same story
I've got the exact same error in After Effects.
Both with new and empty comps created from the VR panel, or importing old 360 comps. I can run them side by side and the Skybox Converter effect is happy, the new Adobe VR Conversion has the red bars.
MacBook Pro early 2013
well the only thing we have in common is the oldish GPU so I guess it's not supported anymore?
BTW I managed to get it working on Premiere old version by starting it with SHIFT pressed. Still not working on 2018
Exact same error in After Effects.
2x AMD FirePro D500 3072 MB
Same Error. I have a GTX 1080TI
Go to "File>Project Settings" and enable Use: Mercury GPU Acceleration
This fixed it for me, I think I turned it off because it was crashing when submitting to our Deadline render farm. Not sure if the new AE will fix that bug... but keep it in mind if you're going to a render farm, you may have to disable it before submission, so I guess that means no VR on the farm... Have to do some testing.
File>Project Settings>Mercury was set to software only. Changed to CUDA and problem is solved.
I have the same problem and Mercury GPU Acceleration is not working, AE tell me that i don't have enough GPU memory.
2x GTX 1080 Ti
64 GB Ram.
I have exactly the same problem with the new Skybox in 2018 ...