MAGIX Music Maker 28.0.0.12

ParadoxMM wrote on 7/8/2019, 8:56 AM

So recently I updated MAGIX Music Maker to version 28.0.0.12 and I have been experiencing some issues with settings not saving.

  • Whenever I open the program, it automatically uses the ASIO driver (Magix Low Latency 2016) for audio, which makes it so only Music Maker has functioning audio and prevents any other program open to produce sound. If I have a YouTube video open when this happens, the video goes black and displays a message saying "Audio renderer error. Please restart your computer." I then have to go in every time and set the driver to Direct Sound.

    Or at least I did until typing this post, which is strange. I have the program open and the issue is not occurring.

 

  • Every time I open the program, it signs me out of the store, which while not a a big deal, is still annoying and somewhat inconvenient since it will not allow me to use purchased content until I sign in.

 

  • Several times now, when I open the program, it will ask me to re-download Soundpools, Features, etc. despite having done so before. This is completely ridiculous and and should not be a regular occurrence.

Has anyone else experienced these same issues or others that have arisen with the update? Does anyone know how to fix these issues?

Comments

johnebaker wrote on 7/8/2019, 9:40 AM

@ParadoxMM

Hi

. . . . . it automatically uses the ASIO driver (Magix Low Latency 2016) for audio . . . .

Music Maker using the ASIO drivers is not an issue, that is how the program is designed to minimise latency, which is a big issue for many users. It does mean that other programs cannot access the sound card when MMM is using it.

. . . . when I open the program, it will ask me to re-download Soundpools, Features, etc . . . .

See this comment.

John EB

 

VPX 16, Movie Studio 2025, and earlier versions 2015 and 2016, Music Maker Premium 2024.

PC - running Windows 11 23H2 Professional on Intel i7-8700K 3.2 GHz, 16GB RAM, RTX 2060 6GB 192-bit GDDR6, 1 x 1Tb Sabrent NVME SSD (OS and programs), 2 x 4TB (Data) internal HDD + 1TB internal SSD (Work disc), + 6 ext backup HDDs.

Laptop - Lenovo Legion 5i Phantom - running Windows 11 23H2 on Intel Core i7-10750H, 16GB DDR4-SDRAM, 512GB SSD, 43.9 cm screen Full HD 1920 x 1080, Intel UHD 630 iGPU and NVIDIA GeForce RTX 2060 (6GB GDDR6)

Sony FDR-AX53e Video camera, DJI Osmo Action 3 and Sony HDR-AS30V Sports cams.

ParadoxMM wrote on 7/8/2019, 11:05 AM

Music Maker using the ASIO drivers is not an issue, that is how the program is designed to minimise latency, which is a big issue for many users. It does mean that other programs cannot access the sound card when MMM is using it.

I didn't say the program using the driver was an issue, rather that it defaulting to the driver was an issue. In previous versions, if I changed the driver, Music Maker would remember that change and use the same driver the next time I opened the program. This is not the case with the current version, wherein lies the problem.

As far as the Soundpool problem, I am trying the method you linked right now.