Internal Error, cannot load engine Number 12 due to error 126

[PatrickVossen]

Hi Severino,

Today, creating a new build for one of our applications using MMS (AudioDjStudioF4.dll).
Always ran a rather old version (control 10.1.0.0 / engine 13.1.1.6) but updated to latest version (control 11.3.0.0 / engine 14.3.0.4)

But now I get a lot of "*** Internal Error, cannot load engine Number 12 due to error 126" errors.
A lot is, one in 5 application starts.

Also noticed that when I got this error, the content of one of the bass-dll's was written into my application logfile.
See attached image..


Tried writing text data using different way (FilePointer / StreamWriter) but that did not help.
Also checked windows antivirus software, but no mentioning for blocked files...

Do you know at what point the bass dll's are written?
Maybe I can disable all my read/write actions until the dll files are written..

Best regards
Patrick Vossen

[Administrator]

Hello,

engine number 12 is indeed the one reported in your log file so there is the possibility that your logging procedure is currently interfering in some way with the loading of the file: I don't know how this could happen but it seems to be strictly related.

Each engine manages a different audio format and, in order to reduce the main engine loading time, they are not created all at the same time: this specific engine is added and loaded on demand when main audio formats like WAV, MP3, Ogg, WMA, MIDI and FLAC are not enough to allow the loading of a specific file of a different audio format so this could happen at any time.

Hope this help

Kind regards

Severino Delaurenti
MultiMedia Soft

[PatrickVossen]

Hi Severino,

Just downgraded to control 10.1.0.0 / engine 13.6.0.2.
Issue seems to be gone...
Has there been a change in writing the dll's between those versions?

Best regards
Patrick Vossen

[Administrator]

Hello,

the way to store and load dlls at runtime has not been changed, other dlls have been added to the existing ones and the one that is giving problems on your machine has been updated in order to support new features but this should not impact the general behavior otherwise we would have been overwhelmed of support requests.
Have you verified the reason why the dll's binary is being written into your log file?

Kind regards

Severino Delaurenti
MultiMedia Soft