Hi Ralf. Thanks for this update, and for correcting my errors in understanding the "update model" for MM! 😀
Is there anywhere on any Magix web page where this difference in approach to updating between MM and other Magix products is clear set out? If not, would it be possible to create such a page, or forum sticky, or similar?
Jeff
Hi Jeff,
There's an info page and an additional MAGIX magazine/blog entry on our website regarding the "update service" model
https://www.magix.com/int/support/update-service/
https://www.magix.com/int/magazine/common/update-service/
As far as the current Music Maker concept goes, our department was always hoping for our CEO to get on stage and deliver a Steve Jobs style keynote speech on the merits of the "freemium" concept in front of a large audience. 😎 Alas, this never happened. However, I don't even think our head office is using the term "freemium" in our external communication. I just tend to use it to explain the concept, as many people have come to know this concept, especially via mobile apps and games, over the past few years.
Cheers!
Cheers! thank you
@ralftaroHi Ralf,
Could you please get the programmers to fix this? Soon? It should have been taken care of quickly. (27.0.3.34)
John CB
Hi John,
It's already being worked on. I would think that it's a rather quick fix, but the development team only just switched over from ACID development to Music Maker again, and naturally has a pretty big pile of development tasks to get through. The work that is being done now is already on the generation 28.x code basis. So, it's pretty safe to say that there's not going to be another patch for 27.x. The bug fixes will see the light of day in the form of a major update, when Music Maker 2020 is released in the beginning of July. I'll make sure the Music Editor fix will be part of that.
Cheers!
Hi Ralf,
It's been broken for a long time, it seems. Like the problems with MEP and especially VPX, why does it take 11 months to get fairly important bugs - things that were broken from one version to another - still not fixed?
We should not have to wait for bug fixes in the next version, which will most likely include more new bugs itself.
John CB
Hi John,
I can't really comment much on the whole MEP/VPX situation at the moment. Generally speaking, I don't know whether it's still productive to think in terms of "this version" and "next version", when Music Maker fixes will always be received as free updates. To a certain degree, due to the "update service" concept, this is even true for the MEP/VPX side of things. So, in the end, this just boils down to the question of how many weeks or months any given bugfix should take, which is something I don't have an authoritative answer to. For my personal taste, these Music Maker bugfixes are certainly taking a little longer than I would want them to take, to say the least. I do think that there will probably be consequences from this current situation, and the current concept of having the whole team work on one product (i.e. ACID), while the development for the other one is completely on halt, will be subject to some serious questioning.
Cheers!
I am having an issue, with sound crackling oftentimes I need to change the audio driver to WAVE to clean up the sound and then later on change it back to ASIO. Sometimes Music Maker crashes on me, when what seems like I am loading things too much too quickly -just when starting up or even during prolonged sessions. Honestly I believe it due to using an older model Core Duo laptop. I will be utilizing my more powerful and newer desktop pretty soon.