MultiMedia Soft forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

SMF - Just Installed!

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - Administrator

Pages: 1 2 [3] 4 5 ... 21
31
Hello,

although you didn't specified the version in use, there should be no problem at all in using our components in Windows 10.

Kind regards

Severino Delaurenti
MultiMedia Soft

32
Hello,

this is an interesting question but, unfortunately, we cannot give an answer because it's a lot of time that we no more use Pentium-based PC.
Our minimum suggested requirement is Windows XP so, technically speaking, if a PC can run Windows XP efficiently, then there should be no reason for which our components shouldn't work, at least when speaking about audio management: for video management, being based upon DirectShow, there could be a really high load of such old CPUs.

Kind regards

Severino Delaurenti
MultiMedia Soft

33
Hello,

a busy computer is certainly the most relevant candidate for this kind of behavior but we don't know how you are currently scheduling the switch (timer or something else) so it's quite hard to guess the effective cause.

Kind Regards

Severino Delaurenti
MultiMedia Soft

34
Hello,

in this case it's quite likely that Mp3Tags didn't use the "İprf" frame for saving the performer name: we have tried to write this frame into a test file and then read it using our component and it seems to recognize the frame without problems; do you have the possibility to upload the mentioned m4a file into our FTP server for evaluation?

ftp server: ftp.mmsoftlabs.com
username: myguest@multimediasoft.com
password: GwDu{#u)&4z9

Once uploaded, please, send me a note so I will download it.

Kind regards

Severino Delaurenti
MultiMedia Soft

35
Hello,

the installer for your version of the component was created before the release of Visual Studio 2019 so it doesn't have the capability to identify its presence.
You can install the component into the toolbox of VS 2019 following suggestions contained in the second part of the related tutorial:
https://www.multimediasoft.com/adjstudnet/help/visual_studio_2005.htm

Hope this helps

Kind Regards

Severino Delaurenti
MultiMedia Soft

36
Hello,

sometime the issue is caused by an incompatibility between the output format of the LAV decoder and the driver so you may eventually try to play with available output formats as explained in the previous topic you mentioned:
https://mmsoftlabs.com/forum/index.php?topic=256.0

If this shouldn't help, unfortunately we don't know what happens between K-Lite and the underlying video driver because our component's code doesn't go so low-level. You may try to ask this question inside the K-Lite forum:
https://codecs.forumotion.net/

Hope this helps

Kind regards

Severino Delaurenti
MultiMedia Soft

37
Hello,

the PlaySoundFromRecorderEx method was introduced specifically for DirectSound when WASAPI was still not available in Windows.

With WASAPI, listening and playing back the audio flow from a capture device is quite easier and doesn't require using both components (DJ Studio and the Recorder) anymore, indeed you can perform this task using the "Audio Dj Studio API for .NET" only by leveraging the WASAPI.AttachInputDeviceToPlayer method.

You can see how to use this method by looking into the code of the WasapiInputPlayer sample, available in both C# and VB.NET, installed by our setup package within samples of "Audio DJ Studio API for .NET".

Hope this helps.

Kind Regards

Severino Delaurenti
MultiMedia Soft

38
Hello,

video rendering is based upon DirectShow which uses DirectSound for its audio rendering so, also if the component is set to work with WASAPI for audio playback, video playback will continue using DirectSound.

The AUDIO_RENDERER_MODE_CUSTOM_2 mode should give better performances in most cases so it's suggested that you continue using it.

Kind Regards

Severino Delaurenti
MultiMedia Soft


39
Hello,

that should be quite simple: this method allows defining coordinates and size, both expressed in pixels. If for example your usercontrol should have a size of 600 pixels width and 200 pixels height and you should need to cover the whole usercontrol surface, you could specify 0 and 0 for the nLeft and nTop parameters and 600 and 200 for the nWidth and nHeight parameters. In case the usercontrol should be resized at runtime, you could invoke this method within the OnSizeChanged handler (or, depending upon your environment, whatever is called the handler of the WM_SIZE message) of the usercontrol itself.

Hope this helps to clarify.

Kind Regards

Severino Delaurenti
MultiMedia Soft

40
Hello,

the waveform analyzer doesn't have an auto-size feature but can be resized programmatically through the WaveformAnalyzer.Move method: have you already tried with it?

Kind Regards

Severino Delaurenti
MultiMedia Soft

41
Hello,

if you are going to use 2 or more instances of the component, you should provide separate callback functions, one callback function for each instance of the component.

Hope this helps.

Kind Regards

Severino Delaurenti
MultiMedia Soft

42
Hello,

re-configuring video filters installed through K-Lite should not impact DirectShow's general behaviour because the installed "Codec Tweak Tool" comes with a feature which allows to "Reset", "Backup" and "Restore" applied settings.

Kind Regards

Severino Delaurenti
MultiMedia Soft

43
Audio editing components / Re: Audio Editor tool in Visual Studio 2019
« on: February 13, 2020, 09:40:13 AM »
Hello,

if you purchased the component in 2017, indeed that version will not support installation into Visual Studio 2019 during the setup phase: specific support for VS 2019 has been added into the latest version 7 of our audio editor component, released in 2018, and updated when the latest VS 2019 was officially released.

That said, you could still use your version of the audio editor component in Visual Studio 2019 by manually adding the component into the toolbox of the IDE; please, read the second part of the following tutorial for guidelines about this specific issue:
https://www.multimediasoft.com/asoednet/help/visual_studio_2005.htm

Just in case you should be willing to upgrade to the latest major version 7, please, drop us a note for claiming your discounted upgrade price.

Hope this helps.

Kind Regards

Severino Delaurenti
MultiMedia Soft

44
Hello,

encryption is briefly described inside this tutorial:
https://www.multimediasoft.com/asrecnet/help/how_to_protect_your_recording.htm

The concept behind the recorder is quite simple: you can perform a regular recording session by choosing to store recorded audio data inside a memory buffer or inside an output file in a specific audio format. Once the recording session is completed, by invoking the EncryptCurrentSession method recorded audio data will be encrypted and stored inside another file that won't be usable by other multimedia applications: in order to use this encrypted file you will need to use one of our components which are able to decrypt the file.

Hope this could be clear enough.

Kind Regards

Severino Delaurenti
MultiMedia Soft

45
Hello,

the reason could be an incompatibility between one of the transform filters used for managing output on multiple screens (named "InfinitePinTee") and the video driver. This may sometime due to the color space used in output by the LAV video decoder.

Unfortunately our component doesn't have control over the output format of the LAV decoder so there may be the need to make some fine tuning inside the properties page of the LAV decoder itself; we would try the following:
1 - inside the Windows "Start" menu select "K-Lite Codec Pack/Codec Tweak Tool"
2 - inside the "Configuration" section press the "DirectShow filters" button
3 - under the "Video decoders" column select the "LAV video decoder" button
4 - on this page you will find a number of checkboxes inside the "Output formats" groupbox, each indicating a different output format
5 - on our system the "YV12" format seems to be the default so we would try to uncheck the "YV12" checkbox and press the "Apply" button without closing the page
6 - now try to reload the video using our component and see if it works; if it shouldn't, you may try to uncheck other check boxes until the problem disappears: we would live the "YUY2" checkbox checked which, at least here, seems to work correctly: please, don't forget to press the "Apply" button each time you uncheck one or more checkboxes

Hope this helps

Kind Regards

Severino Delaurenti
MultiMedia Soft

Pages: 1 2 [3] 4 5 ... 21