I see the downloads for various systems. I am using Windows 10 and want to verify what I need to download.
The list shows Audacity Windows Installer and Audacity Windows Zip but there doesn’t seem to be any explanation.
I guess I can also use the Audacity Manual.
Are any of these the source code or am I only seeing the download just to run Audacity?
I am already using Audacity for my audio editor.
The source code is available from GitHub: https://github.com/audacity/audacity
Is there a “Getting Started” file?
I found an INSTALL file but di doesn’t seem to be too happy.
I see an Audacity.sln file. Is Audacity a Visual BASIC file or is this just a part of the overall package?
Some suggestions to get started would be nice.
Audacity is mostly written in C++, which is a very large and complex low level, object orientated language.
Unless you have substantial experience programming in C++ you will find it very difficult to understand the Audacity code. Audacity is not a beginners project - Although there have been many contributions from hobbyists and young graduates, most was written by very experienced professional software developers.
The sln file is for Microsoft Visual Studio, which is the development platform used for developing Audacity on Windows. On macOS, Xcode is used instead. On Linux, kdevelop is sometimes used.
Instructions for building on Windows can be found here: https://github.com/audacity/audacity/blob/master/win/compile.txt
There is some information for new Audacity developers in the Audacity wiki: https://wiki.audacityteam.org/wiki/For_Developers
I have experience in several languages over the last 20 years: Assembly, BASIC, Pascal, C, C++,COBOL, SNOBOL, SQL, Novell, Visual BASIC, HTML and lately Python.The last three of which I have taught at the college level. I have a B of S in Computer Science among other degrees.
Still, I do not see this as an easy task but I do have a lot of free time.
I will explore the two URLS suggested.
Compiling Audacity from source can be a bit of a battle, as you have to get libraries compiled first. We’ve also recently changed over to using the newer Microsoft MSVC 2017 Compiler (free Community Edition), having previously used MSVC 2013 for a long time. You would need to have MSVC 2017 on your development machine. Instructions for compiling on Windows, which we are part way through updating, are at https://github.com/audacity/audacity/blob/master/win/compile.txt . There is fortunately an active community of developers on our developer mailing list who are happy to help people new to compiling Audacity. It’s well worth subscribing to audacity-devel, saying ‘hello’ and saying what you would like to achieve with Timer Record. https://sourceforge.net/projects/audacity/lists/audacity-devel.
If you want to drive Audacity from an external script, I have been working on that for Audacity 2.3.0. So on audacity-devel we could also talk about how far along that feature is, and whether it is suitable for what you would like Timer Record to do. As a developer, I am on audacity-devel far more than I am on Audacity forum,
There is some documentation on Label Tracks on our wiki. https://alphamanual.audacityteam.org/man/Label_Tracks. You can set the start and ends of region labels accurately by zooming in at the end points first. The labels can also be set precisely from an external script in Audacity 2.3.0, using the recent improvements to the external scripting feature.
this is the primary thing that Emorogork wants:
basically repetitive (n times) hourly recordings with exports
Also I think he, like me, would like access to the controls white Timer Record is actively recording or waiting to record.