❓ Frequently Asked Questions (FAQ)

Common questions and answers for contributors, developers, and users of Aestra.
📋 Table of Contents
🌍 General Questions
What is Aestra?
Aestra is a modern digital audio workstation built with C++17, featuring:
- Ultra-low latency audio engine with WASAPI support
- GPU-accelerated custom UI framework (AestraUI)
- Pattern-based workflow
- Professional-grade audio processing
- AI integration (Muse) — deferred to post-Beta
Who develops Aestra?
Aestra is developed by Dylan Makori in Kenya, with contributions from the open-source community. While the source code is publicly visible for transparency, Aestra is proprietary commercial software.
Is Aestra free to use?
Yes! Aestra Core is free forever. The hybrid model:
- ✅ Aestra Core: Completely free - full DAW with all essential features
- 💰 Premium Add-ons (future): Muse AI and premium plugins require paid licenses
- 👁️ Source code is publicly visible for transparency
- 🎓 Student discounts will apply to premium add-ons
- 🤝 Contributing to development is free and welcomed
Current support:
- ✅ Windows 10/11 (64-bit) - Primary platform
- 🚧 Linux - In development
- 📋 macOS - Planned for future
Is Aestra open-source?
No. Aestra uses the ASSAL (Aestra Studios Source-Available License) - a source-available license, not open-source. This means:
- ✅ Aestra Core is free to use for all purposes
- 👁️ You can view and study the source code
- 🤝 You can contribute improvements
- ❌ You cannot reuse the code in other projects
- ❌ You cannot distribute modified versions
- 📜 All contributions become property of the project
See License Reference for complete details.
🔨 Building and Setup
How do I build Aestra from source?
Follow our comprehensive Building Guide:
Quick start (Windows):
git clone https://github.com/currentsuspect/Aestra.git
cd Aestra
cmake -S . -B build -DAestra_CORE_MODE=ON -DCMAKE_BUILD_TYPE=Release
cmake --build build --config Release --parallel
What are the build requirements?
All platforms:
- CMake 3.15+
- Git 2.30+
- C++17 compatible compiler
Windows:
- Visual Studio 2022 with C++ workload
- Windows SDK
Linux:
- GCC 9+ or Clang 10+
- ALSA, X11, and OpenGL development libraries
What is Aestra_CORE_MODE?
Aestra_CORE_MODE=ON builds only the public core without premium features. This is required for community contributors since premium modules are in private repositories.
# Public build (community contributors)
cmake -S . -B build -DAestra_CORE_MODE=ON
# Full build (requires private repos - internal only)
cmake -S . -B build
Build fails with “private folder present” error?
This is expected in public CI. Use Aestra_CORE_MODE=ON to skip private folders:
cmake -S . -B build -DAestra_CORE_MODE=ON -DCMAKE_BUILD_TYPE=Release
How do I set up my development environment?
- Install prerequisites - See Building Guide
- Clone the repository - Fork and clone from GitHub
- Install Git hooks -
pwsh -File scripts/install-hooks.ps1
- Build the project - Follow build instructions
- Configure your IDE - Use
.clang-format for code formatting
See Contributing Guide for detailed setup.
🤝 Contributing
How can I contribute to Aestra?
Several ways to contribute:
- Report bugs - Open issues on GitHub
- Suggest features - Share your ideas in discussions
- Submit pull requests - Contribute code improvements
- Improve documentation - Help make docs better
- Test and provide feedback - Try new features and report issues
See Contributing Guide for details.
Do I need to sign a CLA?
Yes. By submitting a pull request, you agree that:
- All contributed code becomes property of Dylan Makori / Aestra
- You grant full rights to use, modify, and distribute your contributions
- You waive ownership claims to your contributions
This is necessary because Aestra is commercial software. See Contributing Guide for details.
What kind of contributions are accepted?
Public contributions (in Aestra-core/):
- ✅ Core audio engine improvements
- ✅ UI framework enhancements
- ✅ Bug fixes and optimizations
- ✅ Documentation improvements
- ✅ Unit tests
- ✅ Build system improvements
- ✅ Cross-platform compatibility
Private modules (not in public repo):
- ❌ Premium plugins and effects
- ❌ AI models (Muse internals)
- ❌ Licensing system
- ❌ Code signing and distribution
How do I report a bug?
- Search existing issues - Check if it’s already reported
- Create a new issue - Use the bug report template
- Provide details:
- Operating system and version
- Steps to reproduce
- Expected vs actual behavior
- Screenshots or error messages
- Aestra version
What code style should I follow?
Follow our Coding Style Guide:
- clang-format for automatic formatting
- PascalCase for classes
- camelCase for functions and variables
- m_ prefix for member variables
- 120 character line limit
How long do PR reviews take?
- Simple fixes: 1-3 days
- Small features: 3-7 days
- Major features: 1-2 weeks
- Large refactors: 2-4 weeks
Reviews depend on maintainer availability and PR complexity.
💻 Technical Questions
What audio drivers does Aestra support?
Windows:
- ✅ WASAPI (Exclusive and Shared modes)
- ✅ DirectSound (fallback)
- 📋 ASIO (planned)
Linux:
- 🚧 ALSA (in development)
- 📋 JACK (planned)
- 📋 PulseAudio (planned)
What’s the typical audio latency?
- WASAPI Exclusive: 5-10ms (best)
- WASAPI Shared: 10-20ms
- DirectSound: 20-50ms (fallback)
Latency depends on buffer size, sample rate, and hardware.
Does Aestra support plugins?
Not yet. Plugin support is planned:
- 📋 VST3 hosting
- 📋 AU hosting (macOS)
- 📋 Native Aestra plugin format
How does the UI rendering work?
AestraUI uses a custom batched rendering system:
- OpenGL-based rendering
- Adaptive FPS (1-120 FPS based on activity)
- GPU-accelerated for smooth 60+ FPS
- Cache-friendly widget tree
See Architecture Overview for details.
What’s the threading model?
Aestra uses multiple threads:
- Main Thread: UI and application logic
- Audio Thread: Real-time audio processing (lock-free)
- Loader Thread: Async file I/O and caching
See Architecture Overview for threading details.
Can I use Aestra in my commercial projects?
Yes! Aestra Core is free for all commercial use. This includes:
- ✅ Commercial music production
- ✅ Client work and studio projects
- ✅ Released tracks and albums
- ✅ Live performances
- ✅ YouTube, streaming, broadcast
Only premium add-ons (Muse AI, premium plugins - future releases) will require paid licenses.
Note: The source code itself is proprietary and cannot be reused in other software projects.
⚖️ Licensing
What license is Aestra under?
Aestra is proprietary commercial software. The source code is visible but not open-source. See License Reference for complete terms.
Can I fork Aestra?
No. You cannot create forks, derivative works, or distribute modified versions. However:
- You can contribute via pull requests
- You can suggest features and improvements
- You can study the code for educational purposes
Can I use Aestra code in my project?
No. The code is proprietary and cannot be used in other projects. Any use requires explicit written permission from Dylan Makori.
Why is Aestra not open-source?
We chose a proprietary model to:
- Fund development - Sustainable business model
- Maintain quality - Professional team and support
- Provide value - Fair compensation for developers
- Competitive edge - Protect innovative features
Source code transparency allows educational use and community contributions while maintaining a viable business.
🔧 Troubleshooting
Audio is cutting out or glitching
Possible causes:
- Buffer size too small - Increase in audio settings
- CPU overload - Close other applications
- Wrong driver mode - Try WASAPI Exclusive mode
- Sample rate mismatch - Check audio settings
Solutions:
- Increase buffer size to 512 or 1024 samples
- Use WASAPI Exclusive mode for lowest latency
- Match sample rates (typically 44100 Hz or 48000 Hz)
Build fails with missing dependencies
Windows:
# Ensure Visual Studio 2022 with C++ workload is installed
# Check CMake version
cmake --version # Should be 3.15+
Linux:
# Install all development libraries
sudo apt install build-essential cmake git \
libasound2-dev libx11-dev libxrandr-dev \
libxinerama-dev libgl1-mesa-dev
Git hooks installation fails
Solution:
# Ensure PowerShell 7+ is installed
$PSVersionTable.PSVersion
# Install hooks manually
Copy-Item -Path .githooks\* -Destination .git\hooks\ -Force
UI is slow or laggy
Possible causes:
- Low-end GPU - Integrated graphics may struggle
- High resolution - 4K displays require more GPU power
- Driver issues - Update graphics drivers
Solutions:
- Update graphics drivers
- Lower resolution or scaling
- Check GPU usage in Task Manager
Cannot find audio device
Solutions:
- Check device manager - Ensure audio device is enabled
- Update drivers - Get latest audio drivers
- Try different driver - Switch between WASAPI modes
- Restart audio service - Windows Audio service
Sample playback position is wrong
This was a known bug (fixed). Ensure you’re using the latest version:
git pull origin main
cmake --build build --config Release
📚 Additional Resources
Still have questions? Check these resources:
💬 Getting Help
Can’t find your answer?
- Search GitHub Issues - Someone may have asked already
- Open a new issue - Describe your problem clearly
- Email support - makoridylan@gmail.com
- Community discussions - GitHub Discussions (coming soon)
← Return to Aestra Docs Index