Hi Nick.
I'm not sure who is responsible for why the plugins don't work Nick but I'm trying to find out which individual titles within the package in case they are different to the ones I'm using have the red cross on them. If those plugins are working in earlier versions of MS / VPX it would feel like it is something Magix has changed rather than New Blue. If the effects are different effects then it could possibly be down to New Blue.
Ray.
Hi
From a prevoius topic on a similar issue the problem could be related to the NewBlue 'Magix bug' - see this comment
John EB
Hi Nick.
I'm not sure who is responsible for why the plugins don't work Nick but I'm trying to find out which individual titles within the package in case they are different to the ones I'm using have the red cross on them. If those plugins are working in earlier versions of MS / VPX it would feel like it is something Magix has changed rather than New Blue. If the effects are different effects then it could possibly be down to New Blue.
Ray.
Well here is my experience in a nutshell, should it help. In that post you refer to, Newblue said 8 months ago they were working on it. I had the same problems 3-4 years ago, in what was possibly even Vegas MS days and with different Newblue plugins altogether.
What worked and not? For me the Essentials usually did not show at all. The one time they did show, the cross and watermark was there and I could not get them to install without, even though my Newblue account said they were activated OK. The other part, the, Stylisers, installed and worked fine from the get-go. I have never seen the Newblue Application Mangler agree with the site, or the site agree with what I should be experiencing and am not.
I plump, in my case, for Newblue.
EDIT: The only way I got ND's plugins to install was to disable my firewall and other security arrangements temporarily. When the Essentials kept watermarking I tried turning of security, but the watermark stayed
Nick
Hi.
I have checked and got both NB Stylizers ultimate pack with an enabling coupon code along with the NB Total effects package which I installed in late February 2022.
The new Blue Filters 5 Ultimate was downloaded earlier in May 2021.
Both have been working without problems since installation.
So I'm stumped.
I am not sure why no-one else has said they have not had problems as this type of problem where some people can get something to work where others can't normally ends up either being a driver problem or a hardware incompatibility problem. If you didn't supply your computer setup information with your correspondence with New Blue or Magix they may assume you have read and made sure your system is fully compliant with the programs needs. Of that I'm not sure but I would bet the first people who read your emails to those companies are not software engineers and may just give a scripted response if it matches similar complaints.
The reply from NB to Andy was.
Yes, unfortunately it looks like this is related to the MAGIX bug that some of our users are experiencing.
So not all users. What confuses me is Andie's system, going by his machine specs, complies with the specs on NB's website. The only real difference as far as I can see is Andy is on Win 11 and I'm on Win 10.
Do you have any of them installed and working?
Ray.
Hi Ray
. . . . Do you have any of them installed and working . . . .
Yes - working plugins are:
Filters 5 OFX: all GPU settings
Elements (3?) OFX: all GPU settings
I also have many old style NB plugins (own interface), Essentials, Filters (3?), Action Cam Package and Stylizers, none of which work correctly with any GPU settings.
. . . . I have never seen the Newblue Application Mangler agree with the site . . . .
Same here, older registered versions (old style independent interface) are not even listed.
HTH
John EB
@johnebaker @CubeAce @OldNick1
I have loads of Newblue effects - Filters, Stylizers, Essentials III, Essentials IV and Elements - all of which work as they they should with no watermarks at all GPU or otherwise settings.
The only ones I've had trouble with, and the ones I emailed NewBlue about, is Essentials 5 for Magix which came with my upgrade to MS2023 Suite.
So now I'm also confused.
AndyW
@me_again @johnebaker @OldNick1
Hi Andy.
I have had a look at the New Blue site and the Essentials 5 effects pack to see what effects were included.
Although Essentials 5 is not a pack I have listed, the effects are on my system and working within the New Blue Ultimate package (mine initially came with MEP 2022). I even just got VPX 14 in case the installer was at fault and installed my packages from there.
They all work. I'm not sure what that means but I wonder if the installer is at fault?
Ray.
@OldNick1 @CubeAce @johnebaker
Greetings Ray,
There are indeed some effects within "Essentials 5 for Magix" that are duplicated in other NewBlue packs I have installed. I don't use most of the effects I already have but, as Sod's Law predicts, there are a few within this pack that look to be of interest.
I wonder if the installer is at fault
That's exactly what was going through my mind especially after NewBlue said they were looking into it. This essentials 5 pack does seem to be a bespoke version for Magix judging by the title.
These are the effects included in the Essentials 5 for Magix pack (note the watermark):
Nick, have you raised a ticket with Magix and NewBlue about this? The more that do etc...
AndyW
Hi Andy.
From my copy of VPX 14 installed last night. 28 effects all working.
You chose one of the most subtle effects to try to show working.
They are also in my copy of MEP 2022 and working there as well. In fact none of those effects are new to me as they were already working in MEP 2022 before I got this copy of VPX 14. The only difference is I now have NB Titler 7 instead of 6. Looks anfd behaves exactly the same as 6 but with additional title layouts added.
This is the plugins registered at my account.
I will look through each individually and see if anything is missing because the packs and their associated effects often get blended under a single title heading.
I will try later today.
Ray.
Gretings Ray,
You chose one of the most subtle effects to try to show working
It wasn't really to show if the effect works, which it does with all of them, it was to show the watermark.
From my copy of VPX 14 installed last night. 28 effects all working
I think that's the key. They work without a watermark in VPX14. Therefore they work in your copy of MS2023 because they're already registered correctly at NewBlue.
I don't have VPX in any form and my Essentials work but retain the watermark.
The NewBlue Application Manager shows it's registered correctly:
as does the NewBlue website:
so I'm even more confused now than I was before.
AndyW
Hi Andy.
I had all of those plugins with MEP 2022 except the new version of NB Titler 7 before I bought VPX 14 last night.
They all worked, are still working in MEP 2022 as well.
Have you tried selection the Options box at the top of any non working effect when applied and made sure the plugins are set to use a GPU and not the CPU?
Ray.
Greetings Ray, I rest my case.
The Essentials were registered with MEP 2022 on your system, so any registration info required by the effects is already on your computer.
I didn't have that luxury for Essentials 5 but all the others were registered and they work perfectly.
Something within MS2023 is corrupting something somewhere and is not accepting the registration flag sent by NewBlue. If that flag is already on the system, an install of a new Magix editor will pick it up.
I may try installing MEP 2022 or earlier to try out this theory.
AndyW
ps MS2023 wiped MEP2022 from the system when it installed. Does that mean I can't have different versions on the system?
Hi Andy.
ps MS2023 wiped MEP2022 from the system when it installed. Does that mean I can't have different versions on the system?
It would appear so with newer versions of the program.
The other problem with upgrading over buying the programs outright seems to be a version of the program you had registered with Magix will be removed.
I bought MEP 2018.
Later I bought MEP 2020. Late I 'upgraded' to MEP 2022 and my MEP 2020 version was removed but I kept my copy of MEP 2018. ??? So it appears Magix accepted the upgrade from MEP 2020 but not from the 2018 version. Too old a version maybe?
Through Humble Bundle, I 'bought' both VPX 11 and VPX 12. Both of which showed in my account.
Now I have 'upgraded' to VPX 14 and my copy of VPX 11 has been removed. In both cases I had no options as to which versions to keep but in that instance the older version was removed. The logic of which escapes me as to the difference.
Did you check to see if the affected effects were set to use a GPU or the CPU?
Ray.
Greetings Ray,
Did you check to see if the affected effects were set to use a GPU or the CPU?Yes
I've tried it and no difference. it's not that the effects don't work, they do. It's the watermark even though registered that's the problem.
When I contacted NewBlue anout this, he asked me to delete everything NewBlue and clean out the Registry of anything NewBlue to test if it was the Application Manager manager that was corrupt. Obviously I was reluctant to do that but after a couple of strong teas I decided to try it.
I did it, and reinstalled Elements, the smallest file. This installed and registered with no problem and no watermark, so I installed everything else except Essentials.
These installed and registered with no watermark as well. I then installed Essentials 5 for Magix. It installed and registered but retained the watermark.
AndyW
Hi Andy.
My apologies. I would term a plugin with a watermark as non working because it is effectively unusable.
You are correct of course. It works but you can't remove the watermark.
This is curious and annoying for those with this problem for sure.
It would make me think twice about rebuilding a C: drive.
Ray.
I am still following this, even though I am waiting on Magix to refund me the cost of the upgrade to the suite. I have reported this to Newblue, who also gave me the "tear it all down and start again" idea. I also was reluctant to do that, with my limited data allocation. I see that my decision is vindicated, at the expense of others, in that me_again gave it a go and pretty much ended up dud anyway.
I am even having trouble with the Magix offers with the suite! I was offered to install Soundforge (lite I'll bet) and started to do it, but then thought fergit it, as I had enough on my plate. Magix's installer seems to think that because I started, I had succeeded: I have not been offered that oppo again.
I really wonder if this is all about paranoia over people having two copies or whatever. Seems to me just because I left Soundforge ticked and the download even just started, it was flagged as done.
Nick
Hi Andy
. . . . Something within MS2023 is corrupting something somewhere and is not accepting the registration flag sent by NewBlue. If that flag is already on the system, an install of a new Magix editor will pick it up. . . . .
When you use a plug-in like the NB video effects, the video is in effect passed from MMS through the plugin for processing and then 'handed back' to MMS, it is at this processing stage in the plug-in that the watermark is added. MMS does not know whether the plugi-in is activated or not.
. . . . this installed and registered with no problem and no watermark, so I installed everything else except Essentials. . . .
Is this the version that opens a separate Window to use the effect or is it the OFX version that is internal to MMS ?
OR
Greetings John,
When you use a plug-in like the NB video effects, the video is in effect passed from MMS through the plugin for processing and then 'handed back' to MMS
Aha, so that puts the ball back into Magix' court?
Is this the version that opens a separate Window to use the effect ...
No separate window opened - it has the horizontal sliders, the same as your second picture (the black one) which presumably is the OFX version - which puts the ball in both courts?
AndyW
i Andy
. . . . Aha, so that puts the ball back into Magix' court? . . .
Nope - the processing stage I mentioned above may not have been clear - it is when the plugin is processing the video that the watermark is added before handing the video back to the program.
The plug-in does not seem to know it is registered, those details are, AFAIK, held in the NB Application Manager which handles the activation/registration.
You have the OFX version of the plugins.
John EB
I think I might have found the solution to this issue
I have Essential 5 Volume 1 and Essential 5 Ultimate for Magix. The only effects that are without the watermark are those that are also in Essential 5 Volume 1. And this is only in MS2023 Suite.
I also have VPX12, but all of the Essential 5 Ultimate for Magix effects work in there without the watermark.
I did the "tear down and rebuild" of the all NB effects ...... No change. Still has watermark in MS2023 Suite.
This was a real long shot, but I even tried using the serial number I have for Essential 5 Ultimate for Magix with the standard Essential 5 Ultimate. No go.
What I ended up doing is this:
With Movie Studio 2023 Suite closed, opened up NewBlueFX App Manager and deactivated all NewBlue Effects (by logging off).
Downloaded Titler Pro 7 Ultimate from here (although I reckon any Titler Pro 7 will do)
https://dl.newbluefx.com/download/Win/NewBlueTitlerPro7Ultimate.exe
Installed but not activate (I don't own this so it would have gone to trial mode)
Once that install completed, reran the NewBlueFX App Manager to log on (effectively reactivating all NewBlue Effects)
Started Movie Studio 2023 Suite and applied an affect from Essential 5 Ultimate for Magix (In my case, Aspect Ratio) to an object. No watermark! I tried others, still no watermark.
I uninstalled Titler Pro 7 Ultimate and reinstalled Titler Pro 6 (This version I had previously)
My suspicion as to what happened is that Titler Pro 7 Ultimate contained an updated version of the NewBlueFX App Manager.
Something else to try.
If this is the solution then I reckon NewBlue should make the NewBlueFX App Manager available as a separate download (unless they have and I could not find it)
Excellent, works a treat. Thanks
In my excitement I forgot to deactivate all the NewBlue effects, it didn't matter though, it still worked.
You're correct about the Application Manager, initially the version was 1.10.3.24405 now it's 1.10.0.221111
Thanks again.
AndyW
Hi Andy,
You're correct about the Application Manager, initially the version was 1.10.3.24405 now it's 1.10.0.221111
Assuming you've quoted those build numbers in the correct order (!), the later one actually appears to be "older", I think. So, maybe, rather than needing an "updated" version of the Application Manager you actually needed an older version?
As a matter of interest, where did you find the information on the build number? I've just opened the NB Application Manager on my computer and can't find that information!
Jeff
As a matter of interest, where did you find the information on the build number? I've just opened the NB Application Manager on my computer and can't find that information!Jeff
I was able to find this information by right clicking on “ApplicationManager64.exe” file itself, then clicking properties, then heading to the “Details” tab.
On mine, the File version is 1.10.3.24503 and the product version is 1.10.0.221111