but if you want the developers' attention, or to talk in detail, postings are better on the official forum for those products. I need the parties to get creative and aware of this and get some scraps of development news for MM tossed this way. Well, it's time for convergence of Effort and for the Scrum Masters of both "Camps"to start sharing with us. That explains much to me, and explains much to those ACID Heads who do want MM to be running again in AP8.
What else CAN I do that will receive communication with our Forum Chums here? Why else would I do it? Gary has often been here. Why? Because they've come here and made their profile clear to us, and maybe just maybe might offer a New Horizon of Media Manager clambering over the Fences to come to our rescue. Not sure why you singled out those 3, as the Vegas team is much bigger than them. Per the community rules, we're not supposed to mention names of Magix employees on the forum. To discuss Media Manager in relation to whether it works in Vegas Pro, I think it's best done on my thread, because that is the big issue with it as I see it. In my dreams, someone in Germany or Madison chucks in an up-to-date Sycfusion thingy, releases MM2.5, and we're all good. I'm interested to see what the reaction will be. I think it's OK to have the odd thread over here about Acid and Sound Forge, but if you want the developers' attention, or to talk in detail, postings are better on the official forum for those products.Īs for Media Manager, I think it's possible with AP8 that it was just sort of forgotten.
My guess, and it is a complete guess, is that Acid and Sound Forge software is now developed by developers in Germany who are also responsible for the other MAGIX audio software, while the VEGAS-branded products on this forum are still handled by Madison. I've never installed any Acid software so I don't know what works or doesn't in that. I do not, on my laptop, because holding it at version 1511 indefinitely was not an option, because it's Win 10 Home and not Pro. I do on my desktop, in all VP versions, because it's held at Win 10 version 1511. If not then I'll have to keep a legacy machine just for MM.
Going forward (to my next system), I'm hoping I will be able to run Win 7 or Win 10 version 1511 in a virtual machine on a current Windows PC. I just hope that if MM is replaced by something else, it will be able to import MM libraries. I begged exactly a year ago at the highest level I could, because MM is crucial for me, but no joy. I think Acid Pro is probably now developed by a team in Germany who are more likely to monitor that forum than this one. Yeah, need direction from you on what is Vegas AUDIO and then an ADD-ON as per a relevant Forum? So if I wanted to discuss here, on the options or issues over MM found found in VP I should rather do it there? The convergence continues, but - In a Galaxy Far Far Away. It would be more effective to discuss Acid Pro issues on that forum. From your post, it sounds like it remains a visible preference in Acid Pro 8?īut NOT, repeat NOT in the INTERNAL Preferences.
In Vegas Pro 15, "Enable Media Manager" has been moved to an internal preference. Well, Nickster, you can take it on my authority ? that it still does : So, Nick, do you have MM working in VP then?įrom what I've read, it might still work OK in Acid Pro 7.
This is why my PC is left at Win 10 version 1511 and Windows Update disabled. Oh really?! - Gary? Eric or Derek? Need to know. I have been told on good authority that basically there are no plans to do anything further with MM.