Audio & Music Lab Premium - start up problems

browj2 wrote on 3/23/2019, 10:43 AM

AML Premium 22.2.0.53

After the latest Windows patch (Window October upgrade? 1809 17763.379), AML ran fine, but it wouldn't close. I used Task Manager to shut it down. Then it wouldn't start again, even after a reboot. I uninstalled it twice, first the normal way, reinstalled, didn't work, then uninstalled using Revo. Reinstalled. Still didn't work.

Starting normally from the icon, the splash screen appears, AML shows up in the Task Manager Background Processes, but never starts. However, I can get it started using Run as Administrator.

ACL still starts up ok.

Has anyone had such a problem? Any solution?

I need to have it start normally as I use it from within MEP/VPX. Note, there is a bug with VPX (reported to Magix) as it doesn't start AML, ACL or VSCL at the moment, but that is another problem.

Thanks,

John CB

John C.B.

Desktop System - Windows 10 Home 1903; 16Gb RAM; i7 CPU 860@2.80Gz; ATI Radeon HD5770 w1GB; SSD 500GB, HD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB; dual monitors - 27" main, 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5, 8 GB RAM, 256 SSD, W10 Pro 1903

Comments

ralftaro wrote on 3/28/2019, 6:17 AM

Hi John,

I don't seem to have this problem on my Windows 10 machine, but something might be up. I had two support cases along these lines in the past coupple of days. That doesn't sound like much, but, given the relatively low number of overall support tickets that Cleaning Lab generates, we're talking about something that could be considered a noticeable tendency. :) They didn't seem to be about the usual Qt/graphics driver issue that we've come to expect with this product version either, at least not at first glance, since all of them were successfully running the software on their systems up until now. It's still something that I would potentially make part of the troubleshooting process, especially if Windows has done something like rolling back graphics drivers again.

One of those users has since reported back that they resolved the problem by performing a repair installation of Cleaning Lab. This seems to contradict your experience, as well as the experience of the other user, who tried the reinstallation as a first course of action. I'm now standing by for further feedback from that user to see whether my troubleshooting suggestions had any effect. Maybe you also want to check and make sure your graphics drivers are still intact and up-to-date, just to be on the safe side, and try to run the program in the more compatible rendering mode via this fix:

https://support2.magix.com/customer/en/download_do/251629

Also, try resetting the program properly by manually deleting the main program INI ("AMLab.ini"). For Cleaning Lab, this can be found under the "ProgramData" folder hierarchy (different from most other MAGIX programs).

Happy troubleshooting! :)

 

browj2 wrote on 3/28/2019, 11:30 AM

@ralftaro

Hi Ralf,

Thanks for the reply.

I tried deleting (renaming to .bak) the ini file. No success.

I ran the Qt fixer. No success.

I checked the graphics driver - up to date.

I checked Windows and it updated .Net Framework 3.5 and 4.7.2 for W10 version 1809 for x64.

I tried compatibility mode - W7 - no success. Back to no comp. mode.

I had Windows troubleshooter put AML to start in Admin mode. This now gives the following error message after exiting.

I'll try uninstall/reinstall again.

Note ACL 22.2.0.53 and VSCL 22.2.0.53 both start normally, but now give exactly the same error as above. The above is for my desktop.

AML still starts normally on my Surface Pro 4, but gives the same error message upon exiting as above. It has been doing this for a long time, I just ignored it.

FYI, and I think that I mentioned this before, VPX no longer opens and closes AML, ACL or VSCL properly with the updated file - the file is not updated. The new SF ACL works. This started with the latest VPX10, all patches. I have raised this issue with Magix but so far, after several months and several patches, nothing has been resolved.

John CB

John C.B.

Desktop System - Windows 10 Home 1903; 16Gb RAM; i7 CPU 860@2.80Gz; ATI Radeon HD5770 w1GB; SSD 500GB, HD 2TB; others 1.5TB, 3TB, 500GB, 4TB, 5TB, 6TB; dual monitors - 27" main, 25" secondary; Casio WK-225 piano keyboard; M-Audio M-Track USB mixer; Notebook - Microsoft Surface Pro 4, i5, 8 GB RAM, 256 SSD, W10 Pro 1903

ralftaro wrote on 4/2/2019, 7:13 AM

Hi John,

That error message from a Qt component (when terminating the program) is a known issue that seems to occur on some (many?) systems. It can be safely ignored and has no negative impact on the functionality of the program.

In the meantime, I talked to a few of my colleagues and our devs, but couldn't further substantiate that there's anything like a systematic problem with ACL/AML 22.x under Windows 10 now. No further support cases involving this problem have cropped up, and we couldn't replicate the issue here in our office. So, maybe it was just a coincidence after all, and the other support case is unrelated to what you're experiencing.

You said you'd be willing to try another re-installation, and maybe that's the best way to go. My suggestion would be the complete deletion of any contents (sub folders or files) that remain in the following two folders after the regular uninstallation of the program:

C:\ProgramData\MAGIX\Audio & Music Lab Premium\22\
C:\Program Files (x86)\MAGIX\Audio & Music Lab Premium\22\

After this is done, download and install the program again from the following link:

http://dl03.magix.net/aml2017premium_dlm.exe

Proceed by downloading and running the most up-to-date patch for the program:

https://support2.magix.com/customer/en/patch_download/223935/manual

Now try running Audio & Music Lab again. Good luck!