LinuxMusicians

"Scriptable audio" is in the name of this project, so maybe it's about time to include this. Old examples don't use these features yet. I decided to add them when I got tired of varying seed in a randomized script by editing its text. (Maybe default seed deserves another cli option, thoug...

I've released v0.4.4 with new cli and variable features which got done quickly. The saugns program now handles variable = value strings on the command line. As mentioned in the changelog, there's also a syntax change for variable assignments, which a one-line search-and-replace can update scripts fo...

@Basslint, new version, for when you're around on this forum next time. (I see you've been away so I figure you'll miss this thread otherwise.)

I didn't post about the smaller v0.4.2d earlier, maybe I should have. Anyway, now this is here with a CHANGELOG.md.

(Title before v0.4.4: saugns v0.4.3 -- better for test signals, added 'N' noise generator) v0.4.3 of saugns -- program for a simple audio scripting language -- is now out. Like v0.4.0, the first version I announced here , it adds another audio generator -- but this time it's a simpler one. With N , ...

Btw, to help packagers do their part well I recommend you create a CHANGELOG.md file and put in it the highlights for each tag. I've earlier put summaries in the tag messages (e.g. git show v0.4.2c ), though that's only available using git in the repo. It's not a bad suggestion, and fairly quick, t...

New changes: Quartertones are now supported for named pitches ( "frequency values as notes" ), 12-EDO became 24-EDO, and several just intonation variations are now available with the tuning system toggle S f.s (adding both Pythagorean and plain classic Ptolemy's 5-limit tuning, apart from ...

I released a v0.4.2b today, which adds a small feature: when setting a parameter, modulation & sweep parameter lists can now be written several in a row in direct succession, the result being joining them up as if one had been written. (This allows placing sweep subparams after modulators, by us...

I've now put out saugns v0.4.2. (I didn't post about v0.4.1, released early July.) Earlier this year I wrote about v0.4.0 , with my then-new value noise oscillator R : My "SAU language" and saugns program (wiki page here ) is becoming more interesting for making soundscapes lately, with v0...

I've found and fixed a curious bug which kept a few features and scripts using the R generator from working, when saugns was built using clang rather than gcc on x86-64 in particular (no problem on x86). Though when I say fixed, I don't really understand it -- the new code should give an equivalent ...

I've put out v0.4.0c, adding some more to the randomness features ( R violet noise modes, and a uwh line type with noise). There's now an examples page which shows some short scripts and accompanying rendered audio which can be played. To grow over time... I thought of making and submitting packages...

So cool, thanks! Made an openSUSE package for it. Only two things, from the perspective of a packager. In the Makefile it would be better for us packagers if instead of PREFIX = /usr/local you wrote: PREFIX ?= /usr/local /usr/share/examples is not owned by any system package by default and this cre...

My "SAU language" and saugns program (wiki page here ) is becoming more interesting for making soundscapes lately, with v0.4.0, though I think it's still too unexpressive for music in general. It's far, far more minimalist than all the popular languages for writing sounds or music in (whic...

If I understood it correctly we could not edit the wiki or anything else, there was some problem with the wiki. Is the problem now solved by (*1)? I just came back, read this, and decided to try. Everything seems to work, and I just made this entry for my program. Earlier, the password emails for t...

I didn't try sending a PM until a while ago, but it seems I don't have the user permission. Meanwhile, I've written a usage page, and made some minor changes to the program and expanded the syntax page. (It seems writing pages meant to be read by others helps clarify basic ideas. I've twice adjusted...

I've now written a page describing how to use the syntax of my program , hopefully user-friendly. That's hopefully a better introduction to it than the technical plans of the previous post. If people try it out, I'd like feedback on basic things, like details of the syntax. While partly a matter of ...