LMMS • Forums

very happy to find the real library with asio support

http://www.sm5bsz.com/linuxdsp/install/pa/palir-02.zip

after you need to change the name from palir-02.dll to libportaudio-2.dll

bye and support lmms

spread the news

You can also find it here:

http://code.google.com/p/portaudiosharp/downloads/list

IMO, since LMMS can't distribute this DLL, it should ask the user to download that file (perhaps after installation has finished.) This approach places the license compliance issue on the user, so there are no legal issues with the LMMS package itself.

At the very least, it should inform the user about the ASIO-enabled DLL. LMMS without ASIO is not very useful.

i dont understand...

i find on the internet this library and is part of this project
http://www.sm5bsz.com/linuxdsp/install/pa/pa.htm

also if it use portaudio library that is free opensource
why there is some legal problem?

anyway the user can choose to download or not and is not part of lmms setup...

my answer is this...

why other program can use asio support?

why lmms with portaudio has this restriction???

if there is some legal problems that i don't know
please somebody tell me and i delete this post/information on this forum

The legal problem is with distributing the ASIO-enabled DLL because it was created with the ASIO SDK from Steinberg. You as the end user can download it without problem. But LMMS can't distribute it. Other software usually simply ignores this issue. Which is fine; I don't think Steinberg will start sending takedown notices. But I guess LMMS wants to be 100% sure.

If the PortAudio DLL was built using the VeSTige asio.h header file, then I guess there wouldn't be a problem, since the reverse-engineered asio.h has a free license. But for as long as the DLL is built using the official header file from the ASIO SDK, it can't be distributed without complying with Steinberg's license.

At least that's how I understood the issue.

thanks for reply
now is clear

bye

I just wanted to add a little more clarification for those trying to get this to work.

I spent the better part of yesterday trying to get ASIO4ALL to work in LMMS, and it took a lot of doing for me (because I don't know what I'm doing). First, before you dl the file and replace the one in the LMMS folder, make sure you are using the 32-bit version and not the 64-bit. If you try to replace the file on the 64-bit version, you get a binary reading error. After I figured that much out (you stated it in your other post) I could load ASIO but couldn't hear any sound while using it. What I ended up figuring out is that Windows 7 doesn't normally allow ASIO to use your standard playback output because MS Wavetable hogs it. So what you may need to do if you get ASIO to load but can't hear any sound is go into your sound setting on your PC and disable your playback device. This frees up the device for ASIO to use and you should be able to hear your sounds after restarting ASIO once you have disabled the device.

ASIO certainly helps with latency a lot, although I have some VSTis that seem to be real resource hogs that will periodically crash LMMS anyhow.

Hallo Jungs,

Vielen Dank!
Ich habe auch gerade PALIR-02 heruntergeladen, den Namen umgeändert und in den LMMS-Folder kopiert und es funktioniert angeblich alles gut.

LMMS funktioniert somit auch mit KOMPLET AUDIO 6



Upss... Sorry

Thank you very much guys.
I just downloaded PALIR-02 and renamed it to libportaudio-2.dll as told.

Now I got KOMPLETE AUDIO 6 working as a sound interface hardware.

Yey!

Mr Burns says it best: Exelent!

tnx

mark107 wrote:i dont understand...

i find on the internet this library and is part of this project
http://www.sm5bsz.com/linuxdsp/install/pa/pa.htm

also if it use portaudio library that is free opensource
why there is some legal problem?

anyway the user can choose to download or not and is not part of lmms setup...

my answer is this...

why other program can use asio support?

why lmms with portaudio has this restriction???

if there is some legal problems that i don't know
please somebody tell me and i delete this post/information on this forum

If the PortAudio DLL was built using the VeSTige asio.h header file, then I guess there wouldn't be a problem, since the reverse-engineered asio.h has a free license. But for as long as the DLL is built using the official header file from the ASIO SDK.