Is v.225 still available?

Jayessarr wrote on 1/4/2019, 12:53 PM

Hi, I just plucked up courage to upgrade to v.225 (after having had problems upgrading from v.209 to v.213 earlier in November) but the upgrade notification I get (when starting MEP now) mentions v.213, but not v.225 any more. This is what I see:

 

Is v.225 still available and if so, is there a link I can download it from please?

 

Thanks!

Jon

Comments

johnebaker wrote on 1/4/2019, 1:13 PM

@Jayessarr

Hi

What is the program version number as found under Help, About...?

John EB

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 24H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

Jayessarr wrote on 1/4/2019, 1:15 PM

Hi John, it's v209. I upgrade to v.213 earlier but it kept crashing, so I reverted back to v.209.

emmrecs wrote on 1/5/2019, 4:23 AM

Hi.

I think you need to update to .213 first and then update again to. 225.

 

Last changed by emmrecs on 1/5/2019, 4:25 AM, changed a total of 1 times.

Win 11 Pro 64 bit, Intel i7 14700, 32 GB RAM, NVidia RTX 4060 and Intel UHD770 Graphics, Audient EVO 16 audio interface, VPX, MEP, Music Maker, Vegas Pro, PhotoStory Deluxe, Xara 3D Maker 7, Samplitude Pro X7 Suite, Reaper, Adobe Audition CC, 2 x Canon HG10 cameras, 1 x Canon EOS 600D, Akaso EK7000 Pro Action Cam

Jayessarr wrote on 1/5/2019, 4:45 AM

Thank you, @emmrecs, will try that.

Jayessarr wrote on 1/16/2019, 6:12 AM

Hi, just reporting back in case anyone else is wondering about upgrading to v.225.

I had 209; I just upgraded to 213 (via the dialog box), then a further upgrade box appeared and I then immediately upgraded to 225.

So - it works that way. I'm happy!! Thanks, @emmrecs for advice.

Jayessarr wrote on 1/16/2019, 6:20 AM

Also, information for anyone else curious, I went to help > download My Store content ...... and all my purchased transitions downloaded into MEP automatically. COOL!!! 😄😁😁 Nice one, Magix!

shgrude wrote on 1/17/2019, 6:23 AM

FYI

I observed that when upgrading you get offered the latest version for each minor version.
So for 18.0.1.x you get offered .213 (latest)
for 18.0.2.x you get offered 225 (current latest)

If there was a 18.0.2.x patch that was before 18.0.2.225, this would not be offered again. Or once Magix releases a new upgrade, if this is still under 18.0.2.x an reinstall will offer 18.0.1.213 upgrade and then skip straight to 18.0.2.x

I have several Magix product, and I am not sure which one(s) I did a reinstall (from initial release), but that was the observation. I think it might have been VPX.

From the NEWS sections, there are these releases for MEP:
18.0.2.225
18.0.1.207
18.0.1.205
18.0.1.204
18.0.1.203
(strangely enough neither 18.0.1.209 nor 18.0.1.213 is listed)
So if you have any of the 18.0.1.x versions (except latest 18.0.1.213) you will be offered the 18.0.1.213 version.

For VPX:
16.0.2.306
16.0.2.304
16.0.2.301
16.0.2.291
16.0.2.288
16.0.1.268
16.0.1.255
16.0.1.242
16.0.1.236
First upgrade after reinstall will offer 16.0.1.268, the next will be 16.0.2.306.

Processor: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz
Operating system: Microsoft Windows 10 Home (64-bits) OS 19041.450 (2004)
Memory: 64GB
Sound Card: NVIDIA High Definition Audio
Realtek High Definition Audio
NVIDIA Virtual Audio Device (Wave Extensible) (WDM)
Graphics Card: NVIDIA GeForce GTX 1060 1920x1080 6GB

Jayessarr wrote on 1/17/2019, 7:11 AM

Thanks for the info @shgrude.

(strangely enough neither 18.0.1.209 nor 18.0.1.213 is listed)

I did have stability problems when upgrading to .213 a few months ago so maybe that could be a factor. Haven't had time to try .225 yet - has anyone encountered any bugs/problems with it so far?