A bug reported several times (e.g. EZ Drummer 3 - here) whereby VST3 plugins installed into the default VST3 folder that have a .DLL extension, instead of .VST3 extension are not detected by Acid.
Good afternoon, everyone! Like many participants of this forum thread, I ask you to fix a bug related to zeroing effects. I didn't get to the point of identifying other errors, because it's simply impossible to create anything with this bug. I have to use Acid Music Studio 11, although it has fewer functions, but it works much more stable. And in general, I think it would be fair if Magix provided the opportunity to upgrade to version 11 for free for those who have already bought Acid Pro 10 from them.
I also think it would be nice to add midi effects for midi tracks to the new version.
The downloader / installer never completes if you cancel installation of a component. E.g. If i cancel the installer for a particular plugin I already have or don't want because I have the full version.
The Acid Guide still errors on step 9 of the "an overview of Acid Pro Software" interactive guide
settings for an FX chain are still reset if an additional FX is added to the chain through the "FX" icon
With the store open the application refreshes slower - e.g. when playing a project, the "time at cursor" and any meters refresh slower than with the store open.
it looks a lot like the application for Acid Pro 11 is the exact same as Acid Pro 10 - with slight rebranding. I am not able to see a change log, or any functional change to the application. My assumption is every bug and issue previously reported in Acid Pro 10 will exist here.
The two most important issues that require resolution:
VST server fails to load/has an error
Acid Pro is unstable and crashes
Former user
wrote on 6/13/2022, 1:56 PM
I down loaded AP11 and tested it as well. I too found the same issues as 'Sheppo' plus the random crashes are still to be found haunting you at every turn. I do have more to say on this new release however it can't be printed here.
As long as your comments/feedback is constructive that is fine, but please do not make any insults or outbursts to Magix, See Community rules, speak your mind but constructively and respectably.
Stephen
Forum Moderator
Former user
wrote on 6/13/2022, 2:39 PM
@Former user
Hi
As long as your comments/feedback is constructive that is fine, but please do not make any insults or outbursts to Magix, See Community rules, speak your mind but constructively and respectably.
Stephen
Forum Moderator
All my comments were spot on regarding the new AP11, I said nothing that wasn't true or factual. So, thank you for the Warning regarding what I didn't say or write.
So ive just seen a facebook post that ap11 is released...
Well...it is obvious that the Magix staff dont give a Removed by Moderator about us unsatisfied customers who feel like we have been litterally SCREWED! Magix took our money for ap10 and ap10suite, they didnt fix the bugs and they release version 11 without offering us a FREE UPDATE?
WELL....COCKOS REAPER IS DEFINITELY BETTER ... Removed by Moderator !!!
Magix! Some nerve asking for more money for an update. What an insult for those of us who waited and waited. I saw the release with a price tag and came right to forum to see who was nice enough to test the release for the rest of us. And sure enough, bugs still exist! Come on! You guys really don't care, do you? Just end this product already or sell the code to someone else. What a disappointment.
@MAGIX_Redaktion I think we're all very disappointed at the news of the AP11 release, being a PAID upgrade and looking like it has zero change from the previous versions. How can you justify paying for such a buggy, outdated DAW now when you can get Cakewalk and Studio One for free and from what I've read they're very solid. The whole idea behind coming on here and asking us what we want from the future of AP, was surely to listen and implement change and bring the DAW we all love up to a level of its competitors. This is massively disappointing, If you can't manage to implement what you've been asked to by the community, then I dont know where we go from here.
NOTE: This is a stickied thread to get feedback on bugs, not for posting opinions on the upgrade strategy or monetisation of the product. Those subjects are still fine - just in the correct place, an existing or new thread on the matter.
As always, please adhere to the community rules linked at the bottom of each post
I will wait for a patch for version 10 before even considering the furthest possibility of buying version 11, tired of paying for bug fixes. FIX 10, then we'll see... I'm looking at ***what's new*** in version 11, just VSTs and nothing really new but gadgets from third parties providers... FIX 10 before "proudly" releasing 11 !!!!
Add the functionality to open and import (and possibly export) polywav / multichannel wav files. That way you would open up the Acid application to a whole lot of other uses and workflows.
As we just announced, we want to include you in the further development of ACID Pro 11. We're counting on you!
Feel free to comment how ACID can be better and what bugs needs to be prioritized.
Thank you very much! MAGIX Team
Yup, I have found the biggest error in the whole of the ACID PRO 11 release .
Who is in charge of this Product? Sorry I won’t rant on, I got told off for that
The manual, which is the most important part of the product if you never used the product before ,Same for anyone who upgrades from previous versions.
Press f1 to load Acid Pro 11 help manual loads perfect . The front page says Acid Pro 10 help last changed April 2021.
School Boy error how embarrassing it must be to find your product that was on show at NAMM2022 to find out the thing was released with the front page help manual reading see below.
Jak właśnie ogłosiliśmy, chcemy dać nam się rozwijać ACID Pro 11. Liczymy na Ciebie!
Zachęcamy do komentowania, w jaki sposób ACID może być lepszy i jakie błędy należy traktować priorytetowo.
Dziękuję Ci bardzo! Zespół MAGIX
Today it such a thing happened to me. This is the second such error that leads to the crash and closure of the program. My computer is an i5 8200U, 16 GB RAM, 512 GB SSD plus 1TB HDD.Audio driver: ASIO 4 All .Feedback sent again.
Here are my top 5 bugs that are either in with the current build, or have been long-standing (as in going back pre Acid Pro 7) bugs with the application.
FX settings wiped out when adding a new FX to an existing FX chain
OH MY GOODNESS!!! THIS problem is major! how on earth is this happening? and why hasn't it been solved yet? We can't work like this