duranduran

I've been working on a summit-level wind forecasts for 16 mountaineering objectives (Rainier, Whitney, Denali, Mont Blanc, the Matterhorn, ...).

It's mountaineering safety tool I've been making for my friends and I.

The fun part: if your browser has WebGPU, the page solves that field live as a compute shader (about 35 ms on an Apple GPU) as you scrub the timeline, and draws the flow over a 3D terrain view. Browsers without WebGPU get a precomputed field.

https://mattduran.dev/summitwind/

Ranges and uncertainty only, no go/no-go verdicts. That still requires your best judgement as a mountaineer. Next up is a free-play mode where you set the wind direction and speed yourself and watch the field re-solve.

This kind of exists, but I doubt there are any commercial solutions based on it yet. https://crfm.stanford.edu/2023/06/16/anticipatory-music-tran...

Their paper says that they trained it on the Lakh MIDI dataset, and they have a section on potential copyright issues as a result.

Assuming you don't care for legal issues, theoretically you could do: raw signal -> something like Spotify Basic Pitch (outputs MIDI) -> Anticipatory (outputs composition) -> Logic Pro/Ableton/etc + Native Instruments plugin suite for full song

Thanks for testing it out! You're the third person to give me that feedback on the composition name on launch. I'll delete that step.

On back navigation, that's really bad bug! I'll repro it and fix. Thanks for finding that!

Tonal is great! I use it extensively here: https://app.bars.ai

There are a few small areas where the library hiccups, like with bigger chords. I've been able to work around some of those things by reframing the chord as an inversion of N relative to the root of whatever scale I'm in. I haven't bothered to debug why it does that, but my little work around has been sufficient.

Thanks for checking it out!

This is really good feedback, I'll try to address some of these tonight.

I've added name and description because I made a feature where you could create an account to save your work. During development, I got tired of having to constantly recreate test scenarios, so I integrated AWS cognito and started saving compositions.

Latin is hardcoded. To be honest, I wasn't really sure what to do there. The latin template really just bootstraps the UI to save some time and act as a demo. My plan is to make 3-5 premade compositions for each major genre, and have the create flow let you pick between them.

On making changes impacting the UI, this is something that I'm still really struggling to find a balance between. I'll prioritize this higher based on what you've said!

I'm working on a very experimental music generator: https://app.bars.ai (I regret my domain choice). It's free to use and you can play around with it pretty easily.

The idea is that you have a "framework" that you can change for what you want the music generator to produce. You can download the MIDI files it produces as well.

What helps me is setting goals and clear intentions about what I want out of my side project. I tend to optimize for personal fulfillment+learning, and not money making potential. If you go for the latter, the thinking model changes.

When the pandemy started, I got really serious about learning guitar. I started guitar lessons and eventually hit a wall with trying to grok music theory. I was involuntarily given the opportunity to work on a side project (thanks google), so I picked something that I felt would keep me interested for a while. That kicked off this: https://app.bars.ai

It's very very far from being done, let alone useful. It originally started with little scripts that I had been writing, and it slowly evolved into a website, fancier css, APIs, etc. I've been using it as my little test bed for experimenting with new stuff.