1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
|
#+TITLE: Rusty Microphone
[[https://travis-ci.org/JWorthe/rusty_microphone][https://travis-ci.org/JWorthe/rusty_microphone.svg?branch=master]]
* Summary
The goal of this project is to create a dashboard for real-time
feedback to musicians while they are practicing. This is a personal
needs project, and so will at least initially focus only on the
trumpet and working on my intonation.
More information on how the project works can be read [[https://www.worthe-it.co.za/programming/2017/08/14/rusty-microphone.html][here]].
* Getting started
** Environment Setup
This is a Rust project. The latest version of the Rust compiler and
Cargo are available from your system's package manager, or from
https://www.rust-lang.org/.
The project depends on two native libraries: GTK and
Portaudio. These need to be preinstalled.
On OSX, this can be done with Homebrew using
#+BEGIN_SRC sh
brew install pkg-config
brew install gtk+3
brew install portaudio
#+END_SRC
On Ubuntu, you can skip the portaudio install since it can be compiled
as part of the build process. You still need to install GTK though,
like so:
#+BEGIN_SRC sh
apt-get install libgtk-3-bin libgtk-3-dev libpango1.0-0
#+END_SRC
On Fedora
#+BEGIN_SRC sh
yum install gtk3-devel portaudio-devel
#+END_SRC
** Compiling and running
To compile the project:
#+BEGIN_SRC sh
cargo build
#+END_SRC
To compile and run:
#+BEGIN_SRC sh
cargo run
#+END_SRC
To compile and run unit tests. Use this as the CI build command if
setting up a CI server.
#+BEGIN_SRC sh
cargo test
#+END_SRC
* Project structure
** File Structure
- Dependencies are declared in ~Cargo.toml~
- The project main function for the project executable is in
~src/main.rs~. This should only be an entry point. Any actual
functionality should be part of the library build.
- The other files to be included in the build are declared in
~src/lib.rs~.
- Unit tests are kept in the same files as the units they are testing.
- The main function will launch the GUI in ~src/gui.rs~. From here,
the GUI can call out to the other parts of the library as required.
** General Architectural Guidelines
- Try to keep functions pure when possible. If not possible, try to
isolate the impure parts.
- Split functionality into files based on their logical separation of
concerns. Try to keep mathematical processing separate from
presentation logic, so that the processing can be reused
independently.
* System Requirements
I have tested this project and found it to be working on a Linux
system. It should also work under MacOS.
Unfortunately, Windows is not currently supported. If you wish to
contribute to adding Windows support, the most useful approach would
be to take a look at the [[https://github.com/RustAudio/rust-portaudio/issues/71][open issue in rust-portaudio]] for supporting
Windows in their build script.
* Upcoming Features
The main upcoming feature that I have planned is to create a
WebAssembly build of the core logic of the application. With this,
some HTML, and the Web Audio API, I will create an application that I
can embed in my website to allow others to use without needing to
compile or install it themselves.
Progress can be seen by running ~make build-web~ and opening
~target/site/index.html~. This requires Make to be installed, and the
wasm32-unknown-unknown target to be installed in your Rust nightly
toolchain. If you are using Rustup, this can be done by running
~rustup target add --toolchain nightly wasm32-unknown-unknown~
|
