stereosteve

Thanks! I made this change.

As a side project I'm working on a multitrack audio play along website. If you are learning bass you can mute the bass track.

I used to play along to Jamey Aebersold CDs back in the day, and now on YouTube there are many Play Along videos... but I thought it would be fun to make one where you have more control.

Here's the demo, feel free to upload a track if you have one handy! https://jamz.stereosteve.com/

The source code is here: https://github.com/stereosteve/playalong

It uses this wave surfer multitrack example, which is a pretty nice vanilla JS project: https://wavesurfer.xyz/examples/?multitrack.js

Now that the basics are working... hopefully I'll actually spend some time actually making some practice tracks!

Why does Picard always have to specify temperature preference for his Earl Gray tea? Shouldn’t the super smart AI have learned his preference by now?

Just a few days ago I started working on a similar project, but one where you can upload via a UI.

After talking to some artists + musician friends, it was clear that a SSG was going to be a non-starter for most of them.

Currently it just supports simple track upload + playback, but plan is to add Artists, Albums + RSS feed.

Code: https://github.com/stereosteve/SHYM Demo: https://tunez.stereosteve.workers.dev/

There is no auth and everything you upload will be deleted in the coming days. But feel free to upload some tracks!

Another good library for this is Graphile Worker.

Uses both listen notify and advisory locks so it is using all the right features. And you can enqueue a job from sql and plpgsql triggers. Nice!

Worker is in Node js.

https://github.com/graphile/worker

I don’t disagree. RSS has most of these features and was pretty popular 15 years ago.

My point is that key pairs and signed posts is a good primitive if things are to be re homed and retransmitted.

I think nostr is better in this regard:

  - The "account" primitive is just a key pair, but you can layer more auth requirements on top of that.
  - All messages are always signed by your key pair end to end.
  - Server admin can't read your DMs or edit your messages.  The worst they can do is see public posts or delete events.
  - You can move your messages between servers with via piped CLI commands.

e.g.:

    echo '["REQ", "my_mirror_request_id", {"pubkey": "mynpubkey"}]' | websocat -n wss://source | jq -c '[.[0,2]]' -M | websocat wss://destination

Anyway I know there are reservations, but ultimately I think it got many of the "account" things right as compared to other fedeverse projects where the "webmaster" is still a big deal. Ideally the server side of things would be unimportant, the clients can offer compelling experiences, and people can create their own internet cul-de-sacs in a more chill way...

Maybe nostr is not "the thing" but it's better than the mastodon paradigm.

Agreed. I am experimenting with using go-jet instead and it’s going real good so far.

https://github.com/go-jet/jet

This is a cool explanation!

I wrote a Euclidean rhythms plugin for Logic Pro X scripter:

code: https://github.com/stereosteve/ScriptDiddy

demo: https://www.youtube.com/watch?v=cInvIxaeYZ4

of course I copy pasted the actual implementation from here: https://github.com/Lokua/euclidean-sequence/blob/master/inde...

It's pretty fun to use with AUs and VSTs

The interleaving of modern day ads really kills the fun here. And everywhere I suppose.

I just started working on a project with this use case in mind.

So far just a "browse" experience somewhat like GitHub, but uglier.

Soon want to add ability to commit, similar to GitHub desktop, but without electron.

Very WIP atm but hoping to work on it some this week.

https://github.com/stereosteve/git-goggles