I see you have seen this before :-)) The error code comes on while the new 2020 version is installing (the program has downloaded) at about the 75% way into the installation - it halts the installation then when I say Ok to the error code - the installation continues as normal - finally it says the installation was successful - lets get started - then the program try's to load and execute and the error 57 message comes back and it suggests you delete the program and reinstall again - and you know the rest - it does this again and again :-((( thanks for the response - Oh and the internet is avail and running at 100 Mbs DL - even though the Magix server doesn't go over 989 Kbs - quite slow :-((

@Richard-Schmitter

The stage at which the install or running the program first time fails would suggest that the registration servers cannot be contacted.

When you first installed 2019 did you register online OK?

Has anything changed on the PC since then eg different AntiVirus/Firewall.

Also check that the correct Internet protocols are still turned on:

1. open the Windows 7 Control Panel
2. select Internet Options
3. click the Advanced tab
4. scroll down to the Security section settings and ensure that all the SSL and TLS options are checked, if not check them and then click OK.
5. Restart the computer and try activating again.

HTH

John EB

Thanks for the suggestions - I tried them all and nothing worked - after extensive research I came to the conclusion that the problem had to be with Win 7 - Like many out there I rarely update Windows because the updates fix one issue and cause two new ones and run the OS behind a router/Firewall and off line 99% of the time - However out of desperation I went and put in all the updates and POOF - the problem went away - why only Magix software has this issue is beyond me but at least this fixed the issue and all the software runs smoothly - now if I can get Video Pro X to run as well as Video edit Pro Plus 2020 that would be doing something.

@Richard-Schmitter

I think you are looking at it from the wrong direction Richard.

Updates to products and operating systems are mainly keeping up with alterations made to new equipment and alterations to existing software to keep up with the changing face of technology. You choose not to update to your peril from a security perspective but also miss out in changes to drivers and improvements to codecs that other programs would find beneficial. Whether we like it or not, new equipment has to be accounted for and improvements happen on a regular basis. MEP is just a typical example of having to keep up with new tech. For instance, MEP now needs to use Direct X 11 and at some point will possibly need to use Direct X 12 which is a bit hobbled in Win 7. Don't get me wrong, I'm not over keen on having to update as I often lose a peripheral such as a sound card or printer that will no longer work, but unfortunately it is the nature of the beast and the more of a power user you are (Such as video editing) the more these things will effect you. As for specs for Pro X it does state "*An active, integrated graphics unit with installed, up-to-date drivers is required".

Hi, CubeAce

You're absolutely correct and I was aware of everything you mentioned - I have 4 workstations on their own Network (off line) and 4 TB of Samsung SSD Raid that they use for Temp Storage and rendering - each station has 2 TB of SSD dedicated storage and 1 TB for the OS - The tech is changing so fast like you inferred I'd have to spend a lot of time and money building new machines so I decided to hold off on that madness as long as possible because I would have a network of all different tech i.e. AMD vs Intel CPU's, Radeon vs Ge_Force video cards and Win7,8, and some variant of 10. This would be a Nightmare to trouble shoot given all the hardware and software updates from each Manufacturer. I primarily do 3D design using Newtek's Lightwave and parcel out the rendering over these 4 machines as the software Hub is designed for this. My only on line is a basic 16 GB 3.4 AMD running Ubuntu - simple as long as it works is better. NLE is rather creative inserting 3D renders and I now use external software to deal w the SONY Codecs and up-down scaling and formatting of video as it is much faster than in the NLE plus only one license is required. Video Pro X ver 17.0.1.32 used to read H265 but after last update does not support it - Movie edit Pro 2019 does. Once I get this operation running well I leave it alone and hate to upgrade/update anything as I have never had one that didn't cause issues or take away features I was using - 2020 just did that over 2019 - used to be able to create your own transitions from the time line in 2019 - in the recent 2020 this function is gone - loosing H265 in Pro X and this are few examples of why I don't like to upgrade/update :(( Thanks again for your response and advice! :-))

@Richard-Schmitter

Hi

. . . . 4 workstations on their own Network (off line) . . . software Hub . . . only on line is a basic 16 GB 3.4 AMD running Ubuntu . . .

This raises more questions:

1. Is this a multi user installation?
    
2. Is MEP installed on each workstation or on the software hub?
   
   If on the software hub, is MEP on the hub with the workstations accessing it remotely or does the hub server deliver the program to the appropriate workstation and it runs on that workstation.
    
3. In either case how is MEP supposed to get access to the Internet?

John EB
Forum Moderator

@Richard-Schmitter

I just lost uploading a detailed reply Richard so this version will be somewhat shorter.

I agree with John that further info may help some people here help you more. I can see your reluctance to upgrade but bewildered by so many machines using different hardware and operating systems unless you need them for specific programs. Integrating that can't be easy if indeed that possible.

VPX should support H265 both on import ant export. It says it does on the specs page so confused as to why it's not working for you. Do you have the paid codec?

They have changed how you can do transitions in MEP. I hadn't noticed as I've yet to start a new project but it would mean I can't now possibly load an old project and expect it to play back as I edited it. That is definitely not on and not what I would expect from a program defining itself as 'Pro'. I think it is still possible to make my own transitions using png masks along with using zoom, rotate, and movement functions but that would be long winded and a faff in general.

Really not happy about that as using any of the supplied or bought transitions would mean a commercial license if I wanted to monetize the video somewhere like YouTube or otherwise sell. Magix is not alone in this behavior though and becoming more prevalent across a lot of software.

@Richard-Schmitter, @CubeAce

Hi

. . . . 2020 just did that over 2019 - used to be able to create your own transitions from the time line in 2019 - in the recent 2020 this function is gone . . . .

The capability is still there - I suspect that when you upgraded you did not download and install all the extra functions, and features again - this you must do as they appear to be version specific or have been updated.

John EB

@johnebaker

Hi John.

No, it's no longer the same as it used to be John.

All I can get is this.

I used to get a box where I could select a curve for the transition and a choice of whether to apply the fade from top to bottom or from each corner to center or center outwards or wipe across the screen etc. Now they are all from the selected downloads only.

Hey Guys, John you are correct - in order to make your own Transitions from the Timeline Mode when updating to 2020 you have to load all the additional special features and then shut down and reboot then run MEPP 2020 software and the function is available as it was in 2019 - basically you won't find it with the basic installation and for some reason it takes 2x reboots to show up? but is there and works very well - this new 2020 is noticeably faster than the 2019. Sorry for the confusion on my Network Configuration I have 4 Intel I7's running at 4 GHz - they are identical with every respect hardware and software and run off the web for security and I have no reason to surf with them - they are used to run Newtek's current Lightwave 3D animation software - this function requires huge amounts of memory and CPU number processing capacity - built into the software is a HUB - it allows to switch from the Modeling to Rendering engines (2 separate programs) and move objects between them in real time - when you are ready to RENDER the scene - (animation) you can configure Lightwave to parcel out this work load over the 4 workstations err, like Parallel processing via the network - this arrangement makes old tech I7's faster than any new Intel or AMD CPU's out there for THIS function - it's a cheap power operation and if one goes down the system still runs just slower so I can take them down for maint etc. re: MEPP - I have it installed on only one of these I7's and that is my NLE machine - when I need to access the internet to activate software or what ever I literally run a RJ45 cable from this machine to a router/w firewall and access the internet with that machine only - the others have no access via any paths to that router. I do have another I7 4 G machine off line with MEPP and MVPX in another room - this is my backup machine in case the other fails - I can run this and do NLE - or if I am using the one of 4 for Lightwave and need that power - I just use this machine for NLE - since Magix allows me to install software on 2 machines this works for me and I can use either machine depending on what I'm doing - remember High Res Final animations can take hours to render in HD or 4K so during that time NLE is out of the question. With a setup like this I don't want my workstations anywhere near the internet cause if it was hacked I'd have one heck of a mess getting it cleaned up. Lightwave offers a dongle so it doesn't require internet to activate - buy stations and take the dongle with you :-)))

@CubeAce

Hi Ray

We appear to be talking at cross purposes here.

Richard and I are referring to . . . used to be able to create your own transitions from the time line in 2019 . . . . which is still there once you update all the extra content ie this option.

. . . select a curve for the transition . . .

IIRC there never was this option for transitions in the right click dialog - there is this option for Keyframes.

. . . . a box where I could select a curve for the transition and a choice of whether to apply the fade from top to bottom or from each corner to center or center outwards or wipe across the screen . . .

This is still there, not all transitions are 'adjustable', the transition you have selected in your image can only have its length changed.

Below is an example of the Door transition for MEP 2016 and 2020, as you can see in 2020 the transition length option missing - presumably because this is a separate option in the transition right click menu.

John EB

@johnebaker

Hi John.

Thank you very much.

Yes that is what I meant. I will try to see which can and can't be altered that way. I never realised that some could and some couldn't.

I do have the one you and Richard meant. I didn't realize you were talking exporting.

@Richard-Schmitter @johnebaker @CubeAce

Since this has morphed to transitions, there are a couple of problems.

But first, Ray, see below:

For a simple cross-fade and most other transitions, there are no parameters. For the one shown, there are parameters and you can tell because the parameter gear will show up at the bottom right so long as you are on one of the Transition Templates screens. Click on the gear or Settings in the menu and the parameter screen shows up. Depending on the transition selected the parameter screen may have more features/presets. Note also the button at the bottom right for the duration.

Third party transitions, like Pixelan, will open the third party interface when you click on settings.

Below shows a simple cross-fade - no parameters.

For John EB, there are 2 bugs:

1. For a simple cross-fade, the duration button at the lower right does not work in VPX11 (second image) and probably not in MEP2020. Please check. It didn't work in 2019 either.

2. As per the bug that I raised for VPX, in the first image above, there is no Save as Fade Template. This is not the same as File>Export>Export as transition. See below for the image showing Save as Fade Template in MEP2019.

We need this feature added back in.

John CB

Hey Guys, sorry I got this transition thing going as you are all aware that from update to update and new release to newer variants of VPX and MEP functions seem to come and go and bugs are resolved and newer ones introduced - this was my initial point as to why I am not big on updating my software - seems like the software gets stable and along comes a new release with issues - my fix for this is to do my special effects in Lightwave then render it to uncompressed 422 10 bit Raw files and insert into the VPX NLE material - this way I only use the NLE for the basic stuff and render it out as uncompressed 10 bit - from there I have 3rd party software that is real fast, and offers excellent quality and coding options that cover all the Apple Pro 422 even 444, and their new RAW in either 10-12 bit or even real fast HQ H265 for client previews plus tons of others. Doing this isolates me from the issues with the Magix NLE's having features coming and going - from my perspective as long as it works and doesn't crash I'm happy - well could be happier - ya know what I mean. The speed increase and overall smoother response with MEP 2020 is impressive - I haven't purchased the upgrade for my VPX 17.0.1.32 since it has 3 bugs I know of - one being no H265 input support (does export but even that is quite slow) so it is overall slower than the new MEP 2020 release - that does input/output H265 - wondering if I need VPX at all - I started using VPX with the optional license for SONY Proprietary Codecs but I now do that via 3rd party soft - it's much faster and with more options hence I haven't upgraded the VPX 11 and are thinking of dropping it. I have to say I stay with Magix NLE's because they are fast to edit with and they allow a lot of special functions that are not listed in the manuals - I suspect this is because of coding oversights - the downsides to doing this is Magix software developers eventually find these oversights and code out the capability with updates - so - another reason for me to not install patches/updates even though I have paid for the service - a catch 22 thing. Thanks Much to everyone for the help and information.

@browj2

Hi John

. . . . the duration button at the lower right does not work in VPX11 . . . .

Correction: It does work - for the Flexible crossfade however not for a standard crossfade!!!

Added: I have no standard crossfade available in the Templates, Transitions for MEP or VPX - are yours missing?

. . . . Save as Fade Template in MEP2019 . . . .

I believe we have had this discussion before and, IIRC, Save as Fade Template is not the same as using Export as transition - I could be wrong as I cannot find the original discussion.

HTH

John EB

. . . . the duration button at the lower right does not work in VPX11 . . . .

Correction: It does work - for the Flexible crossfade however not for a standard crossfade!!!

Added: I have no standard crossfade available in the Templates, Transitions for MEP or VPX - are yours missing?

. . . . Save as Fade Template in MEP2019 . . . .

I believe we have had this discussion before and, IIRC, Save as Fade Template is not the same as using Export as transition - I could be wrong as I cannot find the original discussion

@johnebaker

I created the cross-fade by dragging the right object over the left one, then by using the transition button menu at the beginning of the clip and selecting cross-fade. The duration button does not work with either.

I don't see a Cross-fade button in the transitions menu list, only Flexible Cross-fade and the duration button works with it.

Here is the link to the discussion about the difference between Exporting the transition and saving the fade.

@Richard-Schmitter

In VPX11 (17.0.3.68), I exported as HEVC for the first time. I was notified that the codec was then installed. I dragged the exported file back in to VPX, new movie, and I had no problem playing it back. Something is wrong somewhere with your set up or program. Perhaps if you were using the trial version of VPX11 and imported a H265 file that had been created by MEP or an older version of VPX, the trial would probably not be able to read it because the codec wasn't activated.

Anyone else have problems or ideas for this?

As for the bugs, VPX and MEP pretty much share the same ones. There is really nothing critical that I can find, only annoyances. Did you see my bug list? It needs updating after the last patch.

John CB

@browj2

Hi John

Thanks for the link to the other discussion.

Looking at my post, a sentence I put in initially describing making the crossfade as you have described and the button not working got deleted when adding a correction - more haste less speed (food was calling).

The missing crossfade in the templates is a mystery will have a deeper look when time allows.

John EB

@johnebaker

Hi John,

I just checked MEP2016 - no template for Crossfade. However, getting it from the menu or making it manually allowed me to use the duration button. As well, beside the button there was an indication of the duration in seconds.

John CB

Hey, petty stupid on my part for not asking but - as a general question - are you guys using Windows 7? - I ask because some of the discussions I relate to and others - I have to wonder why I'm not seeing the same issues and thinking maybe You're using Win 8 or 10 - also might find this interesting - got me thinking so I was messing with my VPx11 - that sucker has 4 issues I now have found so went back to VPx10 and found it is quite stable - err, much slower esp exporting H265 but it does work and reads H265 quite well whereas X11 does not read H265 but exports - any rate - came to the conclusion Magix has issues with coding on both MEP 2020 - the latest update 19.0.2.58 - stay away from this recent update it has issues - I went back to 19.0.1.23 and it is the best release for now and can't find any issues with it - VPx11 best release is 17.0.1.27 other than minor bugs and not reading H265 this is the most stable and best performing VPx11 release for Win 7 64 bit Intel I7 CPU based platforms - all others have serious issues in my findings so I'm staying at these levels of configuration - just a FYI if you don't want to mess around and just do NLE w/o being annoyed. Thanks again for the help and suggestions - best.

@Richard-Schmitter

Hi

. . . . came to the conclusion Magix has issues with coding on both MEP 2020 - the latest update 19.0.2.58 - . . . .

On your PC maybe, on mine - Windows 10 1903 up to date, MEP 2020 v19.0.2.58 and VPX 11 v17.0.3.68, both import HEVC video with no issues.

Check that both MEP and VPX are using the i7's integrated graphics chip in Program settings, Display options tab, Video Mode is set to the Intel GPU, as shown in the example below from my PC:

.

Have you done a full sfc check on your Windows installation?

John EB

@Richard-Schmitter

Hi Richard.

Personally I changed up to Win 10 before the end of support for Win 7. Never used Win 8. I think most of us here use our machines for a lot of things other than video editing including surfing the net. I was dreading upgrading to Windows 10 as in the past I had peripherals stop working or programs, but fingers crossed none of that happened this time. Even really old programs I have run well in compatibility mode and the Win 7 drivers have worked keeping my printer working in Win 10. When I first used Win 7 I had problems with blue screens of death as well as some configuration problems that I have not experienced with Win 10. It takes a bit of getting used to to navigate the basics for setting up. It's like having another two layers to dig through to get to the older core (which of course it isn't but seems that way) and the more familiar way of setting up things.

The only problems I had with the latest version of MEP over the older update was when I hadn't re-enabled the additional third party plugins but then I don't use all the various ways of using MEP. I'm not sure or certain but not keeping up with updates to graphics drivers, bios, and other bits and bobs may mean you aren't getting the benefit of some of the changes for stability or speed, but I can understand the 'If it isn't broke don't fix it' ideal. Particularly if like yourself you need it to work day in, day out. Let us know how it pans out for you.

Like John I have not had any issues with HEVC.

Ray.

Hi Guys, I asked the Win 7 question because I came to the conclusion you were all using Win 10 - Magix is coding for Win 10 and not really supporting Win 7 anymore they just aren't publishing this information - there are some major differences when coding for win 7. I used to go to their Tech support and started getting responses from them that made me realize they were not looking at Win 7 issues and knew at some point I was going to have to look for another NLE and OS like Ubuntu - many of the software products now are starting to support Ubuntu but I can't get a answer from Magix if they will do so - I figure when Lightwave supports Ubuntu I'll dump all my other software and go fully with UBUNTU and have stopped buying much Win software period. re: John I don't use the Intel Video instead use the NVIDIA GeForce factory OC video boards due to performance issues with 3D rendering - Now that I know you guys are using Win 10 it makes sense - Magix is using the integrated H265 support from Win 10 and Win 7 doesn't support H265 natively so again my point is they are not (fully) supporting Win 7 anymore. Thanks again for the time and information - best.