Repository navigation
Pro Wave 0.1.7
Pro Wave 0.1.7 is an early development build of a Logic Pro-style music production app (DAW) written in Rust: tracks, MIDI and audio regions, Piano Roll, Mixer, Library and a built-in synthesizer. Expect missing features and rough edges.
What's new in 0.1.7
All systems (Windows, macOS, Linux)
✅ Tempo track: Track > Show Tempo Track. Double-click to add a tempo change, drag a point to change or move it, double-click or right-click to delete. Saved with the project and undoable; the control bar shows the tempo at the playhead.
✅ Marker track: Track > Show Marker Track. Name sections (Intro, Verse, Chorus...): double-click to add, click to jump there, drag to move, double-click to rename, right-click for colour or delete. Navigate > Create Marker, Delete Marker, Go to Next / Previous Marker.
✅ Audio region edits: Region Inspector Gain, Fade In, Fade Out, Curve (Equal Power, Linear, S-Curve) and Reverse; right-click Normalize Region Gain and Reverse Region. The audio file is never changed. Fades show on the region and the waveform follows gain and reverse. Saved with the project.
✅ Compact menus like Logic: each menu is as wide as its longest entry instead of stretching across the window. The File menu follows Logic, with ▸ submenus (Open Recent, Revert to, Import, Export, Bounce, Share...), also in the macOS menu bar. Entries that aren't built yet are greyed out.
✅ 24 tracks without dropouts: 60 seconds of 24 stereo 48 kHz / 24-bit audio tracks: 0 dropouts, 1.6 % CPU (Windows)
✅ Lighter audio regions: the read-ahead buffer of each audio region follows the size of the song: at most 0.68 s per region and 8 MiB for all regions together (up to 128 regions), then 0.17 s each. Before it was a fixed 0.5 MB per region (about 12 MB for 24 tracks).
✅ More efficient reverse playback: reuses decoded audio between blocks to reduce repeated disk seeks; automated checks cover resampling and jumping within a reversed region
✅ Playback during large imports: the disk worker refills active regions between batches of new-file requests and skips canceled regions before opening their files
✅ Lighter region playback: reuses calculated region timing between edits and skips unnecessary fade-curve calculations outside the fade
✅ Lighter mixer updates: during playback, volume and pan edits recalculate gain targets for the changed channel while still updating mute and solo across channels
✅ Steadier playback: broken values (from a damaged project or a bad setting) can no longer make noise or stop the sound
✅ No freeze when normalizing: Normalize Region Gain reads the file in the background (a long recording used to freeze the window for seconds); the status line shows "Normalizing…".
✅ SMPTE timecode fix: a position exactly on a frame was shown one frame early (up to 8 % of frame-exact positions at 25 fps).
✅ Lighter transport when the song has tempo changes; tempo ramps avoid repeated logarithm calculations between tempo boundaries
✅ 17 languages: Help > Language: English (default), 简体中文, 日本語, Français, Deutsch, Español, Português (Portugal), Português (Brasil), Filipino, Bahasa Indonesia, हिन्दी, Українська, Norsk, Svenska, Suomi, Polski, Lietuvių. Each language is listed in its own name; the choice switches the whole interface at once (menus, panels, dialogs, messages, also the macOS menu bar) and is kept for the next start. Chinese, Japanese and Hindi use the system's fonts.
✅ Still light: about 360 ms to start and 120 MB of memory at rest (Windows), 13 MB program
Engine groundwork (not in the interface yet)
✅ Tempo ramps (gradual tempo changes)
✅ SMPTE timecode at 24, 25, 29.97 (drop / non-drop) and 30 fps
✅ Windows ASIO for low latency, as an optional build feature
Still to do or test
❌ Region gain, fades and reverse heard on real recordings (checked by automated tests only)
❌ Dragging fades directly on a region (Fade tool) and crossfades
❌ Tempo ramps and SMPTE display in the interface
❌ Several time signatures in one song (Signature track)
❌ ASIO in the Windows download, and its latency measured on real hardware
❌ macOS menu bar submenus tried on a real Mac
❌ Translations checked by native speakers (written by the AI, verified by automated tests for completeness, placeholders and fonts)
Downloads
| System | File | How to install |
|---|---|---|
| Windows 10/11 x64 | prowave-windows-x86_64.zip |
Unzip, run prowave.exe |
| macOS (Apple Silicon + Intel) | prowave-macos-universal.zip |
Unzip, move Pro Wave.app to Applications (see below) |
| Debian, Ubuntu, Mint | prowave-studio_0.1.7_amd64.deb |
sudo apt install ./prowave-studio_0.1.7_amd64.deb |
| Fedora, openSUSE, RHEL 9+ | prowave-studio-0.1.7-1.x86_64.rpm |
sudo dnf install ./prowave-studio-0.1.7-1.x86_64.rpm |
| Any Linux | Pro_Wave-0.1.7-x86_64.AppImage |
chmod +x it and run it |
| Any Linux (sandboxed) | prowave-studio-0.1.7-x86_64.flatpak |
flatpak install --user ./prowave-studio-0.1.7-x86_64.flatpak |
| Any Linux | prowave-linux-x86_64.tar.gz |
Unpack, run ./prowave or ./install.sh |
Linux packages need glibc 2.31 or newer (Ubuntu 20.04+, Debian 11+, Fedora 32+) and ALSA for sound. Details, required libraries and troubleshooting are in README.txt inside the tarball and in dist/README-linux.txt.
Not signed yet
None of the files is code signed, so your system will warn before running them:
- Windows: SmartScreen shows "Windows protected your PC". Choose More info, then Run anyway.
- Windows antivirus: Norton, Avast, AVG or McAfee may block the unsigned
prowave.exewith "Windows cannot access the specified device, path or file". Add the Pro Wave folder to the antivirus's exclusions (Norton: Settings > Antivirus > Scans and Risks > Items to Exclude from Auto-Protect, Script Control, SONAR and Download Intelligence Detection). - macOS: the app is ad-hoc signed but not notarized. The first time, right-click
Pro Wave.app, choose Open, then Open again. If macOS says the app is damaged, runxattr -dr com.apple.quarantine "/Applications/Pro Wave.app".
How well tested is it?
Windows is the developer's daily platform. The Linux and macOS packages were built and install-checked on GitHub's build servers (Ubuntu and Fedora installs, and a 15-second launch under a virtual display on Linux), but have not yet been run on real Linux or macOS hardware. Please report what works and what doesn't.
Licensed under the GNU General Public License v3 or later.