Tried 5 times to update new Major Program Update 7 times!!

This is all I get! Yikes @sheppo

Wow

1st, Simon-W, HEAR HEAR !!! Before I download this, has anyone noticed the stability issues improve? I notice the fx bug wasn't addressed. Well, it's a start. Cheers...........

Update, I began the update down load. So here is the list of 'fixes' for this update (see pic) I now question the actual bug fixes in this update.in fact I question this update, There's nothing in this list that seems to improves the performance of AP10.

Update 2.0, Have run AP10 through a few(6) projects and it's only frozen up 5 times...I guess that's an improvement....to be continued....

Where can man download this 10.0.6.9?

Thx.

Where can man download this 10.0.6.9?

Thx.

If your computer is on-line then it should tell you that there is an up-date. However you may need to have 'Use Newsfeed...etc' checked in 'Preferences' for it to automatically inform you. Cheers

Online, checked since the installation - manually checked online update many times, nothing.

I even went to my account and downloaded the installer, but the newest is still 10.0.5 B38.

Confused - possible reason: Location Germany?

Thanks anyhow.

I installed this update and now neither AP 10 nor AMS 11 works. I try to open the project and the program freezes..

Online, checked since the installation - manually checked online update many times, nothing.

I even went to my account and downloaded the installer, but the newest is still 10.0.5 B38.

Confused - possible reason: Location Germany?

Thanks anyhow.

I'm sorry that my suggestion didn't work for you. I don't know of any other way to down-load this up-date. However, you may want to WAIT on this up-date till it is a REAL bug fix because this one is still a bit of a mess. All the best

Many thanks mystery-man for sharing the list of 'updates'. The most significant in terms of the program itself seems to be that the update process has been updated. Yippee Kay Yay!!!

So, there is not a single bug fix in this update, just some new bugs introduced into the update process. How sad.

The update presented itself automatically when I started the program earlier today. I was running 10.0.5. The other way have got updates in the past is to go to 'Help' and then select 'Update Program online...'

Many thanks mystery-man for sharing the list of 'updates'. The most significant in terms of the program itself seems to be that the update process has been updated. Yippee Kay Yay!!!

So, there is not a single bug fix in this update, just some new bugs introduced into the update process. How sad.

It's funny how so many other companies can get their DAWs to work in a reasonable manner but Magix can't. I do have an idea as to why....Now this is my theory....they took (bought) the code for AP01 thru 07 which was a 32bit program and converted it to 64bit which is where all the real problems began. AP needs to be completely rebuilt, no old 32bit bits lurking about, just rebuild this from zero. ..but alas I am neither an employee or a share holder in Magix...and barely a user at this point so any thing I think is worth......Oh, moderators, this is not a rant just an observation about the on going trials & tribulations of AP. and this current "up-date". Cheers and Carry On.

Thanks Simon, this fix was exactly what I came here to ask about.

I've used Acid since Sonic Foundry, Acid 3.0, and now... I can't believe how much grief has been injected into the current version. I only moved on from Pro 6 because it was crashing a lot; imagine my surprise when the MAGIX build started immediately crashing, in multiple ways.

Hi Xoc. I have also been using the program since the Sonic Foundry days. My understanding is that the 64-bit version had been largely worked on when the program was owned by Sony but not implemented. To their credit, MAGIX implemented the 64-bit version but there were a lot of quite silly bugs in it that really should have been spotted and fixed during testing. This sounded a lot of alarm bells. I'm grateful to MAGIX for keeping the program going and the implementation of ARA support is useful and the inclusion of useful plug-ins from Celemony and Izotope at least continues the tradition established under Sony's ownership. I wish I could share sheppo's optimism and I don't like to complain about the program. However, MAGIX has clearly not assigned sufficient developer/maintenance resources to properly look after the program and us. Leaving the FX bug unfixed for so long - such a basic and serious functionality problem for the end user - is proof, sadly, that the company doesn't really care that much about the product. Also, from what we have all experienced, the company does not appear to have an acceptable standard of testing and quality control. The faults are so basic that I suspect the company assigns trainees to do any work on the program. I mainly use Cubase these days but still also use Acid Pro for the strengths we all know the program has - strengths that have been in the program from the very beginning. Acid Pro deserves a more committed owner and we, the remaining band of loyal users, deserve more loyalty from the program owner in return. That means, as a minimum, fixing reported bugs promptly, issuing regular and true version updates with clear version control notes and not trying to fob us off with bloatware when many of us have already purchased that functionality in far superior products from other specialist software companies like, for example, Waves. I apologise for going on a bit, but I'm so disappointed with MAGIX. I'm very grateful for the comments on my post today and I'm sorry that I haven't contributed to the forum before.

so i accepted the upgrade and now regret it. i can totally here that new Planet advertising window every dam 3 seconds as it changes to a new advertisement and its bleeding into my tracks. i still hear it even though i closed that window. is there a fix for this?

1st, Simon-W, HEAR HEAR !!! Before I download this, has anyone noticed the stability issues improve? I notice the fx bug wasn't addressed. Well, it's a start. Cheers...........

Update, I began the update down load. So here is the list of 'fixes' for this update (see pic) I now question the actual bug fixes in this update.in fact I question this update, There's nothing in this list that seems to improves the performance of AP10.

Update 2.0, Have run AP10 through a few(6) projects and it's only frozen up 5 times...I guess that's an improvement....to be continued...

So they've improved their store conncetivity?

I've just found this forum and your post regarding the destroying FX bug... Unfortunately I was also tricked into upgrading to Acid 10 version, just to discover this bug. Now I see that it wasn't just me that had this annoying FX bug. It's like whenever I insert a new FX into the chain, all settings are reset with all the existing FXs. And I don't see how they couldn't see this during testing, so my guess is, they're doing it on purpose. Maybe they want Samplitude and Musicmaker to benefit from this, and Acid to die down. In the meantime I've been using Cakewalk instead of Acid, as most of what I do is mastering nowadays, having been using Acid Pro as the main DAW from 2003 onwards... I've seen it change and develop from version 3 up till now.... And this is just pathetic!

PS Sony actually did a great job at upgrading and adding new features, while keeping as close to the original as possible... Kinda in a traditional sense.

But with Magix it's totally the opposite, as soon as they bought it, they started to fool around with it or something...

@Simon-W I appreciate the reply! That actually cleared up a few things about MAGIX and Sony and who's to blame for the bugs... and I actually am grateful that someone kept the program going, even without the resources of a Sony size corporation behind them.

My original workaround for this issue was to add FX to a track, render that track and replace the original with it, then add the next instance of FX, etc. etc. - kinda like the equivalent to "bouncing down" tracks on analog multi-track recordings. It works, but it is time consuming.)

But I think I may have found a simpler workaround. It seems to be working for me so far. I don't know how everyone has their Acid work space arranged (i.e. which windows listed under View are open), but for me it's always been just the Explorer at the bottom left and part of the Mixing Console at bottom right - the Preview and Master meters. The Plug-In Manager is, I think, by default "under" the Explorer window in a separate tab.

Here's what I stumbled onto when experimenting with a new work space layout (I recently got a 2nd monitor):

If you drag an effect from the Plug-In Manager onto a track - as opposed to opening the Track FX dialog directly - it appears to keep any changes made to any previous FX's adjustments.

Once you drag-n-drop an effect onto a track, it immediately opens the Track FX dialog anyway - but I believe the culprit is the Plug-In Chooser dialog that comes up when you click on Edit Chain. Did you ever notice that you can't click anything else when the Plug-In Chooser window is active? And how it seems to reload each effect in the chain once you've added a new one? I'm obviously not a programmer but this is where my intuition is screaming, "THERE it is! THAT'S the issue!"

Hope this helps. Actually, I hope this just makes sense at all - I'll try to make a visual description with screenshots soon.

Many thanks Xoc, you are absolutely correct in your analysis and solution. I have amended my initial post and header having received that same advice from MAGIX Support. Thank you so much for your help!!!

So the major update is finaly just a number change as I can see... REASON rack still doesn't work, still loose your settings if you don't use the work around for the vsts.... seriously ! MAJOR UPDATE ?? MAJOR LET DOWN !!

Hi elbe63. Like you I was really disappointed with the latest releases. I contacted MAGIX support and was informed that the updates (Version 10.0.6 and Version 11.0.0) only address some changes related to the presentation of the MAGIX store in the programs. The problem here is one of communication. Having set an expectation that there would be a bug-fix release, it is not surprising that we were all expecting these new versions to be that release - but they are not. In fact, if I have understood correctly, a number of bugs have now been prioritized to be fixed but work has still not started in earnest on the bug fix versions due to the limited programmer resources currently available at MAGIX. There is no date set for the bug-fix release, but I was reassured that we can expect something in due course. It is extremely disappointing, but we can only wait and trust that MAGIX will deliver on their promise, hopefully later this year.

That assumption and deflation is entirely on us. There was never any expectation that there would be a patch when there was,in fact I think most of us were surprised to see there was one at all - working in Software development it would have been far too soon for us to start getting updates after the release of AP11 and the request for bugs thread (in my opinion). Speaking with redaktion I get the impression (this might not be true) that it is largely a new team coming to Acid development - so it will take time for things to ramp up. That's fine, if we know what to expect.

This isn't me saying you were wrong to get excited about a patch, or that Magix are wrong to release what they released.

My feelings are, not as a moderator, but as an end user of a purchased product that has bugs that the developer has committed to fixing, is that I would like to see some transparency about the future of the product. If bugs are being prioritised, and worked on for a release, or series of releases, then I want to see what that bugfix / development roadmap looks like. e.g. update1 - bug 1, bug 2, bug 3. Update 2 - bug 4. Update 3 - bug 5, bug 6, bug 7, bug 8, bug 9, etc. It's even okay for that to change over time - that's agile development.

And I also hope we get open betas running again for users that have purchased the software.

Being open, transparent, setting goals, and getting a feedback loop from the community is a great way to build trust, and I hope it's something we can collectively ask and push for with Acid development.

@Simon-W

Some beta testers in the Samplitude forum estimated that Magix has only about ten programmers working on that program and it is a much more important software for Magix than ACID, so the ACID team is probably much smaller or it is just a side gig. It will probably take some time until the first real bugfixes will appear. The real problem is, that Magix released the new version instead of waiting for, at least, another year.

I concur entirely with your post sheppo. I think that SP.'s comment about the number of programmers reinforces the more general impression I got from support earlier today. I have reset my expectations accordingly and hope we can build the kind of interaction that you outlined sheppo to get the best out of what we have. To end the week on a positive note, I have always found MAGIX support to respond promptly and to be very sympathetic and supportive regarding issues I have experienced, including the FX issue that started this thread. That is something to be grateful for.