Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

People have been comparing it to Strudel, so I wanted to clearly explain the difference.

ÆTHRA vs Strudel (in short):

ÆTHRA is output-oriented: you write a script → run it → get a WAV file.

Strudel is performance-oriented: it’s browser-based live coding focused on real-time pattern manipulation.

Key differences:

Export

ÆTHRA has built-in WAV export (one click).

Strudel doesn’t natively export audio files; users usually record output manually.

Execution model

ÆTHRA renders audio offline (deterministic, no glitches).

Strudel runs in real time via the Web Audio API.

Use cases

ÆTHRA: game music, background scores, generative assets, scripting music like code.

Strudel: live coding, experimentation, performance.

Environment

ÆTHRA runs locally (currently Windows).

Strudel runs entirely in the browser.

Both tools are free, and they’re not trying to solve the same problem. ÆTHRA is meant to feel closer to a music compiler, while Strudel feels closer to a live instrument.

ÆTHRA is early (v0.8), but it already supports tempo, ADSR, chords, scales, loops, echo/reverb, live preview, and WAV export. I will update AETHRA soon and make it very powerful to reach v1.0



  >  ÆTHRA is output-oriented: you write a script → run it → get a WAV file.
You are competing with traditional noninteractive usage of CSound. What do you think you can do better than CSound? More generally, what are the peculiar and valuable ÆTHRA features that you want to develop well?

The current language is relatively verbose and readable (more suitable for live coding than for a "music compiler"), but somewhat simplistic and ad hoc on the notation side (e.g. no separate tracks, parts etc.) and not very general on the sound synthesis and processing side (e.g. fixed waveforms and keywords for effects).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: