Your computer is the problem.

If something only works with a specific set of computers, I wouldn't blame the computers but the software itself.

And no, my pc is not some low end laptop from bestbuy, it's a custom built tower for goodness sake.

X99A Raider Motherboard (Realtek ALC892 Codec), i7-6800k (6 cores, 12 threads), 16gb of ram, and with the software installed on an SSD.

There is no reason for the program to act like way it is, but it is acting all f**cked up.

There can be many reasons your computer has problems with real-time audio processing. For example your Realtek drivers could be out of date or some antivirus software is causing latency or Windows is running in energy saving mode or it's caused by network activity.

I already linked to Latencymon in an earlier comment. This tool tests your computer and tells you if your configuration will work for audio processing.

The system requirements for real-time audio processing are much different from other softwares like games or video editing. If your computer has only a cheap Realtek Audio Chipset it doesn't matter what all other specs are.

In the past I had problems too until I bought an external audio interface. No more problems after I got it.

Really helpful program..... not sarcastic at all...............😒

Here's what the DirectSound Advanced menu looks like in MX:

Note the tickmarks on pretty much everything?

Now look at the same menu in MMM21:

It's all unticked.

Here are the ASIO settings:

And here are the WASAPI settings:

WASAPI works the best but seems to set it's target to either nothing at each launch, or might not even produce sound until I set to and from a different driver beforehand.

Oh and BTW, I can use any setting in MX and it will work just fine, but in MMM21 they've all got their own bugs and annoyances.

Somewhere between MX and MMM21 they messed up the support, otherwise it would still work now wouldn't it.

And don't give me that "oH bUt It'S 64bIt" nonsense. 64Bit is only about allowing more memory usage.

They rewrote something in the audio engine, and it broke support for some users (I know I'm not the only one).

MX works fine, and I can have as much complex stuff as I want, without it sh*tting the bed before I've even made one 4bar midi object.

50 euro well spent...

Hey look at that, I was correct. They did rewrite something and it broke DirectSound and Wave Driver support.

https://www.magix.info/us/forum/music-maker-27-direct-sound-not-working-with-midi-controller--1208382/#ca1402522

Did you already try to install new, up-to-date drivers for your Realtek Audio Chipset, your mainboard and maybe your bios?

I also read a little while ago, that failing RAM can also cause problems in audio processing.

Did you already try to install new, up-to-date drivers for your Realtek Audio Chipset, your mainboard and maybe your bios?

I also read a little while ago, that failing RAM can also cause problems in audio processing.

Audio drivers, chipset drivers, BIOS, are all up-to-date.

Okay, that sounds good. What are the settings in your Realtek Audio Manager? Could you also make screenshots of them?

It's all stock settings:

• 24bit, 48000hz
• No effects
• No virtualization/spacial sounds

Ok, another idea, do you use wireless LAN? Try disabling "Automatic Network Discovery".

Control Panel->Network and Internet->Network and Sharing Center->Advanced sharing settings and select "Turn off network discovery" in both the Private and Public sections. 

Ok, another idea, do you use wireless LAN? Try disabling "Automatic Network Discovery".

Control Panel->Network and Internet->Network and Sharing Center->Advanced sharing settings and select "Turn off network discovery" in both the Private and Public sections. 

What? Why would that help?

When it's activated Windows tries to check for new wireless networks in every couple of seconds, which can cause a load on your network and your CPU.

@SP.

We're not running Athlon XP or Pentium 4's here, you can afford to run background tasks and multitask with several apps without it being a problem. Though even an Athlon XP can run some older version of music maker without it crashing, I should know; I've done so.

You keep alluding to it being my system, but it isn't. As the comment I posted above ( https://www.magix.info/us/forum/music-maker-27-direct-sound-not-working-with-midi-controller--1208382/#ca1402522 ), I just proved they screwed the pooch on compatibility: Wave Driver and DirectSound does not have midi monitoring while in "stop" mode anymore.

Those two meant having legacy support and a fallback that would always work, but they screwed it up when they moved their audio engine to a Samplitude-based engine. And instead of developing it to have the same support as their previous engine had, they worked on 64bit and multicore support instead.

Not saying 64bit and multicore isn't a bad thing, but I'd rather have the old engine that supports all the stuff we're used to.

This is like Unity Engine developing a new render pipeline resulting in older graphics plugins not working anymore... Oh wait, that's exactly what they're doing, but at least they still have their legacy pipeline for those that still use that. MMM does not have that.

I only wished I knew this before buying MMM21, perhaps I'd went for a different DAW.

There was a forum user with a problem like you experience now some month ago. It was not a problem with Music Maker but Samplitude. The computer also only had a Realtek Audio Chipset and the problems just appeared out of nowhere.

We tried different things to solve the situation. I recommended to buy an external audio interface instead of using the Realtek Audio Chipset. The user also reinstalled an up-to-date Windows version completely from scratch. And the audio problems were there from the start on this freshly installed Windows system. So Microsoft changed something in the past through it's automatic updates that caused the problems.

Some days later the user wrote that he was able to solve the problem but he couldn't remember what exactly he changed that solved the issue. He changed many settings and drivers and then it worked again without flaws.

This showed me that Microsoft updates likes to f**k things up. It doesn't matter if something worked in the past. Modern Windows 10 uses so much resources, it's not funny. And especially the big half-year-upgrades of Windows 10 break stuff that worked before.

I am experiencing similar issues. Software was working okay until 3 days ago when it stop recording. I'm able to hear the tracks but cannot record or save any files, which makes it absolutely useless. I usually use ableton, mpc's, and studio one for my music production and thought this would add a different flavor to my software library, but my experience the last few days has me quite pissed off. I can't get anyone at MAGIX to reply to emails and I'm just so disappointed. I've tried everything that has been mentioned in these comments, but nothing works. Does anyone have any suggestions?

Did you also try an external audio interface? Like I said, it solved all problems for me but it it's expensive. I use a Focusrite Scarlet 2i4 with the newest beta drivers.

Many people also recommend RME audio interfaces because of their excellent drivers. But something like the Babyface Pro is very expensive.

I tend to agree that it shouldn't be this difficult. Luckily I have an old cheap Edirol external interface and access to the FLStudio ASIO driver so everything works fine. It was frustrating when I started with MM2019 with the midi problems and direct sound. I'd like to compare things to Mixcraft which I recently got the old basic Steam version. If I don't have my audio interface plugged in it works. If I do it works. I don't have to change any settings. I've never had any problems with FLStudio. I don't think people should need to buy even cheap interfaces like Behringer to get it to work. Some of this reminds me of the annoyance of getting things to work years ago.

@browj2

Really thank you for this video...i am trying to do it accroding your tutorial.....but when i am trying to drag this .syn file into Magix (Magix Music Maker 2021 premium version) i get this message

I am not sure if the problem is here but then according this tutorial

i was trying to remove "write-protected" message, but it is not working for me...i have stil mesasge "Diskpart failed to clear disk attributes

Please do you know where is my problem?

Really thank you

@Lubomir-Rabatin SYN-files aren't supported by the newer Music Maker version. They still should work fine in Samplitude or Samplitude Music Studio.

@SP.

but when i copy it to the folder with new MMM then for example the "Lead Synth" from my old MMM is working in my new MMM....i want this cool BeatBox working in my new MMM.....i think it should work according this @brow tutorial.....do i just need to solve my issue that i have my drive "write protected?" thanks....

@Lubomir-Rabatin The old Beatbox uses a SYN-file and these files cannot be read by Music Maker since two or three versions ago. Support was removed. Yes, it works in the video of @browj2 because in the video he uses the older Music Maker 2017 version.

It works fine in Samplitude. You can use the free Samplitude Pro X4 Silver. http://dl04.magix.net/2019/SamplitudeProX4Silver/Program/SamProX4_Silver_INT_200121_07-59.exe

@nuFF3

Hi

. . . . X99A Raider Motherboard (Realtek ALC892 Codec), i7-6800k (6 cores, 12 threads), 16gb of ram, and with the software installed on an SSD. . . . . There is no reason for the program to act like way it is . . . .

The crashing issues may have nothing to do with the audio issues you are seeing.

From your computer specs it would appear that you do not have a graphics card/chipset installed - the Intel i7-6800K has no integrated GPU, therefore you must have a third party graphics card installed and it could be the display drivers that are causing the crashing.

John EB
Forum Moderator

@Lubomir-Rabatin

Hi,

I should probably remove the video from YT. I'll start by putting a note that the trick only works in older versions of MMM and Samplitude. I just tried Samplitude Pro X3 and Beatbox works, Livid loads but nothing play, Loop Designer works.

MMM2022 has a new Beatbox that comes with it. It looks different from the old one.

I suggest that you upgrade to the new Version, 2022 - the program, that is, because it's free. Once you have logged in, the program recognizes previous Editions, like Premium 2021, and unlocks features, presets, etc. that you already had, but does not give you all of the new features that you can see in the version comparison chart. You will have to download and install many items under the Downloads tab.

With the free version, you get the new BeatBox. If you purchase Plus or Premium 2022, you get the Pro version of Beatbox.

Take note that MMM is now a 64bit program, starting with 2021. For 32 bit plugins, you need the 32 bit bridge.

EDIT: I just tested the last 32 bit version of Music Maker (2020 - 28.0.3.51) and the synths works except for Livid which just won't play.

John CB