News:

SMF - Just Installed!

Main Menu

Recent posts

#41
Hello,

that's strange, please, zip the file and try to attach it to your reply on this forum: we have raised the max size to 50 MBytes.

Kind regards

Severino Delaurenti
MultiMedia Soft
#42
Hello,

Unfortunately not able to open the site. Getting error message

Your connection is not private

Did everything to resolve but no success.

Why don't you add a format .mp4 in your attachment which is most common today.

What to do?

Thanks and Regards,

Ravindra
#43
Hello,

please, upload the troublesome video inside our ftp site:
ftp.mmsoftlabs.com
username: myguest@multimediasoft.com
password: GwDu{#u)&4z9

Once uploaded, please, send us a note.

Kind regards

Severino Delaurenti
MultiMedia Soft
#44
Hello,

I am playing a video file with the method,
nResult = AudioDjStudio1.DisplayVideoPlayer.LoadForTempoChange(Player_A, lSongFileFullName)

I found a very strange behaviour that when i try to play a particular video file then
it fails to load and my application just closes without returning any nResult.
(Of course My other videos files playing without any problem)
It also failed when i tried in the sample project VideoPlayerAdvanced.
This particular video file played successfully in Windows Media player, VLC, MPC.

What could be the problem ?

I am struggling to attach this video file (.mp4, 10.5 MB) in .zip format but giving Upload Directory Full error. Please advise me what is to be done?

Thanks And Regards,

Ravindra.
#45
Hello,

many device drivers have this behaviour: when the new device added is connected, its driver will set itself as the system default one, causing the current device to stop playing (not in every system but it happens in many).

Unfortunately this happens at low level and, when using the default DirectSound protocol, if something affecting the order of listed output devices should happen, like a new insertion or a change of the system default device, the engine will not be able to recover the situation automatically so a reset of the engine (through the combination of our ResetEngine and ResetControl methods) will be required in order to have an updated list.

Due to the fact that our component is compatible with CoreAudio APIs introduced with Windows Vista, you can be notified when something affecting the list happens by catching the CoreAudioDeviceStateChange event: after catching this event, you may eventually reset the engine and the component by calling the ResetEngine and ResetControl methods.

A solution to avoid having to deal with ResetEngine/ResetControl combination would be adopting the Wasapi protocol in place of DirectSound: this protocol allows the engine to manage connections/disconnections with more flexibility so, after connecting/disconnecting a device, you could get an updated list of devices, allowing to avoid the need to shut-down and restart the engine.
Please, check the tutorial "How to manage audio flow through WASAPI" inside the documentation and the few Wasapi-related sample projects installed inside the system.

Hope this helps

Kind regards

Severino Delaurenti

#46
Hi Severino,

I use InitSoundSystem method to detect output device in my application.

It so happens that my application is running and i connect external sound source other than built in
speakers then my audio sound output goes. I have to restart the application and get back the sound again.

Sometimes we may have multiple playback devices like Bluetooth speaker, audio interface etc. connected then can we detect automatically which of them is currently active and giving audio output so that my application set the output device to active playback device.

It happens may times in musical programs where Laptop is connected to external Mixer/Amplifier system.
If software is already open and external sound system is connected the audio output stops.
After restarting application it comes back.

Thanks and Regards,

Ravindra.




#47
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
#48
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
#49
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

#50
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