Which Windows SDK?

[polksaladannie]

Ok, here's one part that I didn't understand the first time and still don't:


Now would be a good time to open the text file: C:wxWidgets-2.8.12BuildCVS.txt because you need to do step c): (Copy c:wxWidgetsincludewxmswsetup0.h to c:wxWidgetsincludewxmswsetup.h), note that setup.h is staying in the same directory as setup0.h, in effect you are just changing the name of setup0.h while keeping a backup. You will need to change two of the #defines later as the default features are not appropriate for Audacity.

I look in the folder wince and found the setup.h but not setup0.h.

[Edgar]

Don't give up--most (including myself) have problems at first; it is not a trivial task but if you get it right once it will go smoothly thereafter.

[polksaladannie]

Thanks. I haven't quit yet!

Can you clarify what I should do in this step?

Now would be a good time to open the text file: C:wxWidgets-2.8.12BuildCVS.txt because you need to do step c): (Copy c:wxWidgetsincludewxmswsetup0.h to c:wxWidgetsincludewxmswsetup.h), note that setup.h is staying in the same directory as setup0.h, in effect you are just changing the name of setup0.h while keeping a backup. You will need to change two of the #defines later as the default features are not appropriate for Audacity.

[Edgar]

Can you clarify what I should do in this step?

It is really straight forward. Using Windows Explorer open the folder c:wxWidgetsincludewxmsw and find the file setup0.h; this insures you are in the right folder! Now, before compiling wxWidgets (or after doing a complete "clean" on wxWidgets) you need to edit the contents of setup.h so they are in line with those your situation requires. In this case you will actually just copy the setup.h that Audacity supplies into the folder which contains setup0.h as discovered above.

Skip ahead to step 6a of the instructions to find out all the details. Keep pressing on, you will get there!

[polksaladannie]

I'm going to switch over to some different audio editing software for now. Perhaps I'll come back to Audacity in the future. Thanks again for your help.

[Edgar]

Good luck! If you ever want to try compiling Audacity again just jump in and ask away--we're always happy to help. Just remember that there is no need to compile Audacity to use it as-is--just install it from the download, it is only the ASIO stuff that requires compiling. I do not understand why Steinberg gives ASIO away for free but will not let open source apps (like Audacity) include it out-of-the-box.

[Gale Andrews]

Thanks for helping, Edgar.

FWIW, using the Audacity-modified setup.h is completely optional. It just turns on extra accessibility features.

I do not understand why Steinberg gives ASIO away for free but will not let open source apps (like Audacity) include it out-of-the-box.

The answer is simple - the Steinberg licensing agreement prevents us disclosing the Steinberg code. Audacity is free and open source, ASIO is only free.



Gale

[afarina]

I did read this answer already, several times, but I don't buy it.
On Sourceforge, there are dozens of audio programs, with full ASIO support. They are open-source, licensed under GNU, exactly as Audacity. And indeed the support for Asio drivers is included!
I list here just a number of them, but there are several others:
http://llcon.sourceforge.net/
http://asiowmpplg.sourceforge.net/
http://sourceforge.net/apps/mediawiki/j ... _extension
http://sourceforge.net/projects/psycle/

Here another open-source software with full ASIO drivers support (not hosted on Sourceforge, but still GNU):
http://www.experimentalscene.com/softwa ... ve-studio/

In conclusion: if all these open-source programs offer full ASIO support and provide pre-compiled executables containing it, why this is not possible also for Audacity?
I think that the Audacity developer's team did interpret the limitations posed by Steinberg around their SDK too strictly. All these other developers did read them with more elasticity, and apparently Steinberg did not complain with them...
I think that, if Audacity really claims to become a program to be used professionally, embedded support for ASIO drivers must be present without requiring recompiling!

[Gale Andrews]

I did read this answer already, several times, but I don't buy it.

Are those projects using reverse-engineered headers, like Audacity does for VST?

And in any case you are a developer, so you can compile Audacity, no?


Gale

[afarina]

of course, I managed to recompile Auadacity with Asio support.
It was not really as easy as claimed, indeed.
It is perfectly clear that the source code released on Sorceforge cannot include the proprietary code included in the Steinberg SDK.
This is the same for the other programs which I cited.
I was refering to the fact that it is "forbidden" to release a precompiled version of Audacity with Asio support.
First of all, such "prohibition" is probably lacking any legal value here in Italy, and generally in Europe.
Second, I really do not see what is the problem with the GNU license.
If releasing precompiled code containing portions of not-open-sorce code was forbidden, no Windows or Osx executable could ever be released..
Said that, what I am asking is to be allowed ro redistribute to my students the precompiled version of Audacity with Asio support. Nowadays, most of them do not have enough knowledge for being able to recompile themself...
Which is ecactly the same case as for the other programs cited:
The sorce code does not contain the Steinberg SDK, whilst the precompiled executable does contain it...