Acid Pro 8 x64 hang during beatmapper wizard

Comments

jocker-boy wrote on 8/20/2018, 3:09 AM

The beatmapper problem still has not been resolved.I tried to do it in various ways in Windows 10 and Windows 8.1 both 64 bit and no result. The only way is to use the beatmapper with Acid Pro 7 and then use such prepared files.

leninsaenz wrote on 8/21/2018, 2:41 AM

Still with the same problem, version 8.0.5 (build 226) 64-bit.
When will we have a solution?

sheppo wrote on 10/5/2018, 4:47 PM

This is now fully fixed in build 233

Shaquille-L wrote on 10/8/2018, 6:41 AM

This is now fully fixed in build 233

How do i update to build 233? Ive purchased acid pro 365.

My program crashes everytime i use the beatmapping wizard. need help urgently.

sheppo wrote on 10/8/2018, 8:52 AM

@Shaquille-L - Hi. I'm not personally a user of AP365, so I'm not 100% sure. Do the steps I outlined for normal licenses work? Let me know, if they do I will update the FAQ to include this information.

Shaquille-L wrote on 10/8/2018, 9:05 AM

@Shaquille-L - Hi. I'm not personally a user of AP365, so I'm not 100% sure. Do the steps I outlined for normal licenses work? Let me know, if they do I will update the FAQ to include this information.

Yeah so when i re-download the installation package it's only providing me with the 8.0.5.226 version and the not the updated 233 version :/

The same thing happened when the support team emailed me a link to download the 233 version, it wasn't there. So i don't know if the website just isn't providing the right download file or what.

sheppo wrote on 10/8/2018, 9:14 AM

@Shaquille-L sorry the link wasn't correct, i even had the wrong one in the FAQ - whoops.

Try this one

Shaquille-L wrote on 10/8/2018, 9:20 AM

@Shaquille-L sorry the link wasn't correct, i even had the wrong one in the FAQ - whoops.

Try this one

I run AP as administrator but when i click on 'check for news' nothing pops up?

Thanks for the help, i really appreciate it.

sheppo wrote on 10/10/2018, 3:05 AM

@Shaquille-L I have asked for this to be passed to the correct team within Magix. Hopefully a resolution for this will be incoming soon. :)