the project is very much still going through it's maturing stage whilst feedback has been coming in.

it's also great to see people submitting pull requests and bug fixes for the project still; thank you for being here.

hello friends;

nw_wrld v0.6.0-beta just released. a few updates to the software:

—Audio threshold meters now sync with the active track
—Starter modules can be rewritten and replaced from the UI
—New CubeGrowth module added for 3D visualisations
—Expanded tests and CI improvements for reliability

nw_wrld//dpCube[4]

Made in Typescript & Ableton, via nw_wrld software.

#newmediaart #creativecoding #audiovisual

hello friends <3

nw_wrld v0.5.0-beta just dropped; officially as native application for macOS, Windows, and Linux.

you can now use this as a piece of software without running it through a terminal environment.

this is a huge step for the project as the number 1 request this past month.

latency isn't _too_ bad however the software will support an "offset" field for such issues <3

on-device audio as input-type coming soon #opensource #webgl

nw_wrld PRTCL module built with webgl & chart.js #opensource

built using webgl & point-cloud data; this is an MDL planetary visual as part of the recent OSS nw_wrld software. #opensource

nw_wrld v0.4.0-beta

many folks have kindly asked for specific video walkthroughs on modules/features in the app. I'll be putting together some more documentation <3

weekend currently looks like:

- E2E playwright workflows
- more TypeScript, runtime, and unit test migrations
- linux (via WSL) stabilisation
- improved documentation for general use-cases

1-week of open-sourcing "nw_wrld". What an incredible and baffling reception so far.

why thank you, that means a lot. Best place for discussions is on the repo itself; there's a discussions tab where we've all been sharing ideas, plans, roadmap :)

kurokawa is phenomenal at this stuff. had the true pleasure of interviewing with him last year <3

hopefully these two modes balance UX and customisation. beyond MIDI, OSC, and on-device audio, I'm curious if there are other signal types that would benefit from support?

previously, Ableton and Strudel were sending the same value from different octaves, which caused issues. While a note-name-only trigger addresses this, people had kindly raised that octave-specific matching for lighting software or physical hardware would be useful.

nw_wrld MIDI integration improvements:

1. simple note-name trigger: listens for any note name (C, D, E, etc.) regardless of octave

2. advanced mode: supports standard MIDI note numbers (0–127)

Taken from the "nw_wrld" project: This DGSR module queries a Solar Radiation dataset from the Antarctic Zhongshan Station. It cycles though estimated DGSR over a 30-year period to generate mutable Perlin noise. #opensource

It’s a good problem to have because this is the moment that defines the next 12 months of features and potential. The coming weeks will see major stabilisation, UX, and QOL features before considering long-term scope.

tysm for the incredible feedback so far <3

right now "nw_wrld" solves a specific problem for artists and developers trying to get into this space, and because of the sudden traction it would be easy to go overboard with the scope of the project.

* already there have been some amazing discussions raised on the future of the project; at this point the software could branch many ways.

"ENTRP[pcd]" animation created using Ableton, three.js, and nw_wrld software.

yes tysm

you raise a good point. The latest proposed solution would be allowing users to pick from two modes:

- Pitch Class mode: compare (noteNumber % 12) → fixes naming mismatch and ignores octaves.

- Exact Note mode: compare noteNumber exactly → gives octaves back (up to 128 unique triggers).

getting strudel working with my open-source A/V software

and we also officially have Linux support (working example on Ubuntu with GNOME).

working through some stabilisation & bug fixes for “nw_wrld”; there’s been some updates to how MIDI mappings work, specifically to cater for DAW users in Ableton, FL Studio, Reason, etc.

an example of how this SDK references within static files:

the “nw_wrld” project allows users to write visuals using web-libraries as simple JavaScript files; with any complexities being handled by the runtime SDK. you can declare and use a combination of three.js, p5, d3, and many pre-defined methods for animations/camera/sequencing all out of the box.

of course! FOSS all the way. And nice would love to see some more stuff that you're up to!

why thank you! hope you can mess around with it :)