Hi John. I had tried that already, but the message I get is that my product is too old, and there's no option of downloading.

The other 'humorous' thing, if you can call it that, is that when I inquire using my software serial number, I get a message that states the S/N hasn't yet been registered. But when I try to enter it in the registration section, it gives me a message saying that it's already registered. So Catch 22 it is. Sounds like these guys need a bit of organizational assistance.

@jeff-s

Did you log into your account or were you trying to log into Support. They are two different places. On the Magix.com site, you access through the person type button at the upper right, not through Support. When you log in, do you see a My Products button? I just checked my account and MEP17Plus is still there with a download link and the activation code.

@jeff-s

Hi Jeff.

Try loading the program in compatibility mode. I've had to do that with some of my older programs.

Cubase 4 and Capture-NX-2.

As long as Windows 10 can use the needed drivers within the program it may work.

If you went from a 32 bit version of Win 7 and then changed to a 64 bit version of Win 10 it probably won't work.

Sometimes you will get warning signs that things won't install. Just shut the warning boxes down by using the X button and not the Cancel button and nine times out of ten the programs continue to install.

Ray.

Hi Ray. No, my CD/DVD drive doesn't recognize the CD at all. I had hoped to do exactly what you said, and link it to W7 in compatibility mode, but with the software itself not being able to load at all from the disk, I can't get to that point. That's why I was hoping for a link to a downloadable version of the software, which would hopefully work, and then I'd try the compatibility mode option. Thanks though. Take care.

Hi Browj2. I did get into the appropriate site, but there were no shown products as being registered. So, I then thought to try and register, and got a message that it was already registered. Strange thing is that I bought this software brand new way back when, but don't recall ever registering it. But either someone did, or there is some sort of glitch at Magix. I'm betting on the latter. I'd even consider paying their stated upgrade charge, but when I enter my info in the Tech Support section, I get the following message: "Please enter the code from your support voucher". Then it says "Unfortunately your last registered product is too old". The it says "You can buy a support voucher in our shop". My responses to these 3 comments: I don't have a support voucher, nor can I even find anywhere on their site as to where to buy one. And as far as my reg product being too old, I can't even find confirmation that I actually HAVE a registered product with Magix ! You know, I've Googled this company, and there sure were a LOT of reviews, but to be honest, I could not find one that was favorable insofar as customer service goes, and the impossibility of being able to actually get technical support. I guess maybe what I'll need to do is try to find an on working PC for sale with Wdws 7, and go from there. Hopefully my disk will work in THAT drive ! I'll tell you, with this kind of support, I'll never be buying another product from this firm.

@jeff-s

If you try to raise a ticket about an existing product, then you get the message that you received because your product is very old. Try doing so on the sales side about purchasing a new product. Then you should be able to raise a ticket.

Could you perhaps have registered MEP17 with another email address?

John CB

@jeff-s

Hi Jeff.

Sorry, no it won't but you can find the DVD / CD drive and open the folder and look for the exe. program. Right click on it and select it to run in compatibility mode.

Early installers often don't work in Win 10 (sometimes not even in Win 7) but the programs sometimes can.

Ray.

@jeff-s

Hi

. . . . Movie Edit Pro 17 Plus . . . . Wdws 10 . . . .

You need to upgrade to a Windows 10 compatible version of Movie Edit Pro.

Movie Edit Pro 17 does not work on Windows 10 and even if you get it installed, which is unlikely as @CubeAce has commented, you may have many issues using it - mine stopped working altogether when I upgraded to Windows 10.

John EB
Forum Moderator

@johnebaker

Hi John.

Just out of interest John, did you try using compatibility mode when installing?

Was that version 32 bit only? If so it was probably the audio drivers or the vst implementation in the program that caused it to not work. Some programs can use ASIO4ALL that overcomes that (It allows input and output audio channels and MIDI commands to plugins to be rerouted and connected) but MEP does not have the ability to change or choose how drivers are implemented within the program.

Ray.

@CubeAce

Hi Ray

. . . . did you try using compatibility mode when installing . . . .

This does not come in to play when installing, Compatibility mode is for when the program is running.

It is the installers, which are not compatible with Windows 10, that can prevent installation.

If the program does manage to install there are other issues which arise - the most common one being unable to burn discs.

. . . . Was that version 32 bit only . . .

There was only a 32 bit version of MEP 17 - it was released in 2010.

MEP was not released as a 64 bit version until MEP 2015.

. . . . Some programs can use ASIO4ALL that overcomes that (It allows input and output audio channels and MIDI commands to plugins to be rerouted and connected) but MEP does not have the ability to change or choose how drivers are implemented within the program . . . .

This is OT for the issue here, you cannot compare video editors to audio editors when it comes to drivers they are very different programs in their communications needs.

John EB

@johnebaker

Hi John.

I think the plugins in the mixer and audio chain would be vst reliant. I can't think of another way for them to be communicating unless Magix programmers are willing to develop two sets of plugins, and some of them are the same as the ones found in the internal audio editor with a different looking interface as far as I can tell, so I think they are.

It's a bit of a moot point if MEP 17 was 32bit, then it is not going to work if the Win 10 version is 64 bit.

Ray.

@CubeAce

Hi Ray

if MEP 17 was 32bit, then it is not going to work if the Win 10 version is 64 bit

The implication of your statement is that 32 bit apps cannot work in a 64 bit OS. That statement, at face-value, is incorrect! 64 bit apps cannot run in a 32 bit OS but the reverse is not true. Otherwise, anything installed in Program Files (x86) is going to be a non-starter! 😇

Jeff

@CubeAce

Hi Ray

. . . . vst reliant. I can't think of another way for them to be communicating unless Magix programmers are willing to develop two sets of plugins . . . .

There is no need to develop multiple versions of the same VST for use in different programs.

VSTs, and other plug formats such as AAX, OFX and AU, are all built to a standard that defines how a program communicates and uses them with the proviso that they are part of the functionality of the said program ie you would not use a VST synth in MEP, however a VST limiter/Compander such as MDynamic EQ - a third party plugin I use this for setting final audio levels - can be used in both a video editor eg MEP and VPX and a music creation program eg Music Maker, Samplitude etc.

Windows 64 bit does support 32 bit programs as well as 64 bit - unlike the latest MAC OS which has rendered 32 bit software useless and has been causing issues for Sound Forge MAC users who have updated.

John EB

@emmrecs

Hi Jeff.

Maybe I'm getting cabin fever or just sleep deprivation. You are of course correct.

@johnebaker

I'm not saying that John.

I'm saying it's possible some newer vsts may not work in older vst environments or the other way around. That MEP may not have the latest implementation of the standard or a plugin may be too old.

I have a pile of effects and synths that will no longer work on my hard drives and on disks.

Ray.

@CubeAce

Hi Ray.

Given the amount of time you have been spending, first on your export experiments with MEP and second, the computer rebuild, I think you have every excuse for that mistake!

As commented elsewhere MEP cannot, yet, use VST3s but only VST2s. Is that what you are referring to when you comment on the fact that some VSTs may not work in older VST environments or the other way around? Speaking personally, I have a range of VST2s and VST3s, or varying vintage, both "effects" and "instruments" - some quite "old" - and I can't remember coming up against a situation where any of those "older" ones didn't work, at least the effects type. Not wholly sure about some of the instruments.

Jeff

@CubeAce

Hi Ray

. . . . I think the plugins in the mixer and audio chain would be vst reliant. I can't think of another way for them to be communicating unless Magix programmers are willing to develop two sets of plugins, and some of them are the same as the ones found in the internal audio editor with a different looking interface as far as I can tell, so I think they are. . . . .

To clarify - are you referring to VST2 vs VST3?

John EB

@emmrecs@emmrecs

I've not had problems with any soft synths as such but I have INTAKT Player that won't load and that is vst3 based I think as it was a new plugin after 2008.

I don't have any problems with vst3 but really early Steinberg vsts made for Cubase VST3.1 or earlier no longer work. That could be down to the earlier Steinberg authorization process that used a non USB activation dongle. Those ports that it plugged into no longer exist on modern motherboards. It was the old printer port I think. I started out using Cubase VST 2.0.

Ray.