The Waves Audio Driver Is Not Supported By Your Current Audio Codec

1 view

Skip to first unread message

Andreas Mbili

unread,

Aug 3, 2024, 11:01:43 AM8/3/24

to smalsayseartho

Brand new PC and updated to Music maker premium 2020. Same issue as I had with the 2016 version...doesn't matter if I have 10 tracks or 1. Program either freezes or the sound becomes crackly and skips until the program finally freezes and I have to force quit through task manager. I had HP help me but all they did was check to see I had updated drivers. I use headphones and I've tried both my mixer interface USB audio codec as well as the Audio jack on the PC which is the Realtec audio. No improvement.

I have tried different drivers. The wave driver 16 bit and 24 bit works fine for playback only but I cant use my music keyboard. The wasapi and asiov2/magix low latency driver all did the same thing. I am on a new PC with a fresh install of MMM2020 and these are the same issues I had with the 2016 version on my old PC which is new from 2017. I only have one music keyboard plugged in. I have tried new cords, two other different keyboards with no improvement. So now this makes me believe it is a driver issue. The Magix Latency has not been updated since 2016, The ASIO has not been updated since May 23 2017 Windows 10 has had some upsetting updates which may have caused these drivers to fail. It feels like the drivers are having a asio surge which needs to be updated.

Cubase has had such an update however the ASIO v2 driver in cubase does the same thing. The ASIO V2 needs to be updated or Magix just needs to update their program to 64 bit. You cant run a "VW engine in a tesla"

I've been waiting to hear back from Magix support but no response so far. It's been two weeks. I tried emailing the guy who made the ASIO v2 driver but no response. I know everyone is under lock down and this would have been the perfect time to sit and write music but it sucks that I paid for a program that doesn't work. If anyone else has an idea or solution...you will be my new best friend if it gets resolved!

At this point in time, to learn a whole new DAW is not an option, I tried Cubase and it was way too much to handle. MMM allows me more creative writing than to mess with all the technological bits and pieces. Besides I can almost work on MMM with my eyes closed. If I did change, I would lose more than 1000 songs over the course of the years since 2006? ?

If you have such a big library of songs I would suggest to never change a running system and always keep a working pc configuration for old versions of Music Maker and your songs. This is veryimportant!

The Behringer XENYX302 USB uses the generic audio Driver I dont believe they have one. I have been using this for a few years now with no issue.Whatever Windows 10 update did, needs to be addressed by Magix. As far as keeping an older system...a person should not have to do this. The only thing that should change in a DAW other than the interface is the driver support for updated Computer systems.

I know what you mean and I have tried different buffer amounts but it does nothing to change the effect. The Behringer XENYX 302USB interface has no dedicated other than the Generic USB audio Codec used by windows.

Oh, I understand that that's why I've always used the Generic Audio codecs and never had an issue, until Windows updated. I'm also using a 64 bit PC with the 32 bit Magix program and outdated ASIO drivers :-0

ALL the downloads for the Behringer unit are listed here. I note they do include the ASIO4All driver. Why did you say earlier that it needs an update? I checked the link on that Downloads page and it directs straight to the actual ASIO4All website! The latest version (2.14) is there. Have you actually downloaded and tested it?

I have always used the ASIO4all driver since the beginning and it was all good. I tried using the 2.14 version and the 2.13. I've tried Rolling back my MMM2020 to the 2016 version doing a clean install, different compatibility settings etc....long story short, I tried many many configurations and it all leads back to the driver. Cubase has recently updated their ASIO driver...if I can remember that it was due to an overflow of the asio driver. It could also be the 64 bit PC im on is too powerful for the Asio driver? If there is anyone who has The MMM premium 2020 and it's works perfectly, I would love to hear how they are set up. If it's a Computer issue such as "HP" then I would be happy to return this new one for the one that works :-) When I switch to the Wave driver 16 bit, the music plays flawlessly but again, Cant record or play anything from the music keyboard. So when I believe it's the asio driver, Im thinking an update might help...

Yes, I have MMM Premium 2020 working without problem using ASIO, albeit the dedicated ASIO driver for my MOTU interface. I also have ASIO4All v2.14 installed, and can use that without problem. That driver/program has not been updated since about 2017 because no update has been needed; it still functions exactly as it always did!

It is possible that a recent Windows update has changed some permission settings for access to your audio but and ASIO driver basically "punches through" standard Windows Audio settings so this should not be an issue, I think.

This suggestion may have come too late for you (if you have already started the process of resetting and reinstalling) but have you tried increasing the buffer size in that ASIO4All control panel, currently 512 samples? Doing so may introduce some latency (delay) which can be a problem if you are overdubbing but could at least show you where exactly the problem is coming from.

I can play HIGH end videos games with full power, Full spectrum sounds and extreme graphic details and My CPU runs at half...If I run Magix with only one track or more the CPU runs at 100% very high.....what am I missing here???? Still no reply back from Magix...

I could finally get the crackling to appear after about 20 mins of swapping in/out and playing various projects, from simple 6 track Soundpool based to 13 track MIDI with various effects on all tracks - buffer settings were set to the defaults.

The fix it for me was to increase the number of buffers - 8 worked for most of the time- with only a small hint of a crackle after on the most complex MIDI project with one instrument - crackled disappeared when it was muted (?), however 16 buffers worked best.

How this would affect latency I do not know as I do not have a MIDI keyboard at the moment to test, however I would not expect the latency to increase as much as it does increasing the buffer. I suspect the buffers run in parallel.

Your laptop has a Realtek ALC295 audio codec connected to the analogue output. You can see this in your device list as Realtek(R) Audio - Realtek is a known audio codec developer / manufacturer and it's device ID DEV_0295 identify it as the ALC295.

Something like "ALC 892/897" is a special audio chip connected to an Intel HDA compatible soundcard. It's called a codec because it codes and decodes the digital data stream coming from the soundcard, and converts it to and from audio signals.

Most modern chipsets have an Intel HDA "soundcard" integrated into the chipset (after all, the point of having an external codec is that you just need a few extra pins to connect it to the standard chipset).

Now, even if it's integrated into the chipset, your motherboard doesn't have to use the Intel SDA soundcard. So if they have a different soundcard (like your Realtek one) which doesn't use external codec chips, then no actual "codec" will appear in the system information.

Finally, don't confuse Intel HDA codec chips with software codecs (the list in your first image) like MP3, MPEG, etc. These also code and decode and digital data stream, but this is compressed audio, and coding and decoding happens purely in the CPU, by software.

Hey all. I've been having a bit of an issue with getting these drivers working on Windows 95. Sound is indeed working (albeit, very jittery and slow), but the system is rendered unusable due to an inevitable crash. The error presented is "Runtime error 202 at 0003:020E", but sometimes the system will just lock up without displaying an error. I am running this on a Dell Latitude e6410 with the RAM limited to 448 MB. I have applied the Vcache, MinTimeSlice, and SMARTDRV stability fixes to no avail. Thanks.

Currently running OSR2.5 C.
Did all of the above recommendations, with no change unfortunately.
DirectX actually wasn't installed, so I installed it, but no change.
Interestingly, it appears that the only sounds that jitter are system sounds and WAV files. Playing video files (for example, from the FUNSTUFF folder) leads to almost flawless playback, hold for the few pauses in playback.

System sounds do not use a player with DirectSound. WAV-files can be associated with another player, Windows Media Player for instance. I do not know if this is possible for System Sounds. I only use them if I want to test if sound is actually working.