Anyone with a decent understanding of music and acoustics can tell it's silly from the title and abstract alone.

Burning out to grind out tons of code - for which you get paid no extra above your salary - is not a net win for coders. It's only a net win for the employers and it's turning coders into serfs. People are going to get wise and realize the electricians have a way better deal right now. This is no longer a nice way to earn money for a 20 to 40 year career.

Take away the attraction to the grifters and you reduce the issue.

Of course this does not eliminate the problem of the streaming platforms tolertating AI generated work so that they do not need to pay as much out for your subscription fee.

Personally, if there were a decent Spotify alternative that had a zero tolerance to gen AI policy, I'd switch without a second thought.

The most annoying part is having to declare everything properly on the tax returns even when its peanuts. sigh.

"Jazz Musician": someone who puts a $10000 horn in a $1000 car to play a $100 gig

There's no way this isn't happening with other skills. No goddamned way. Anyone who tells you otherwise is grifting.

I can do this when in shape, but like most mortal sleight-of-hand practitioners, only with in-hand faros. Actual table faros, what most people are thinking of with a rifle, are the domain of very very few, and even fewer can get that to a point of consistency. In hand faros are not impossible given fresh cards and enough practice.

My lawn == I'm not wasting any of my dwindling old man time on bullshit people vomit out. You want to do that, you fork and leave me out.

Is there a performative and marketing element? sure. But that's the music world, a great deal is performative. We have depended on patrons who want to support the arts and be seen supporting the arts for time immemorial.

If you want to schedule tasks in Max accurately with code, you can either use Max, C extensions, or my extension.

yes, you can do patcher scripting from S4M as well as you can easily send messages to named objects, which is all you need in order to be able to do that. That is how max patching works - whether you do it in the GUI, JS, or messages to the patcher, the whole thing is just objects sending messages to other objects, and the patch is just a connected graph of references of instantiated objects. If you send message to a thispatcher object, you achieve the same thing under the hood as manipulating the GUI or going through JS. You can read about it if interested in the Max SDK documentation and in the Cipriani & Giri books on thispatching.

I'm currently a PhD candidate in it, have previously used Csound, SuperCollider, Max, Pd, Common Music, and others, and have published/presented at conference on this topic. Of everything I've tried, I prefer working in Scheme in Max over other options. It is definitely practical and accurate. (Though in Scheme in Pd has soe nice features too!)

One of the main reasons I wrote Scheme for Max (S4M) was to enable tightly timed scripting. You can pick which thread an S4M instance runs in, and each instance is totally isolated, which is very different model from the Max js objects (including the new V8) one. Those are global and only in the UI thread. S4M works very well for this, I use it in Max for Live and can get it synchronized perfectly underload with other sequencers.

I started scripting max with JS and built Scheme for Max after banging into its limitations. My typical workflow is a mix of Max, Csound in Max, Gen and Scheme, with the fast majority of the work happening in Scheme.

The live object model is MUCH nicer to use in a lisp, as basically you do everything by making dynamic lists to represent what you want to access! There are examples in the Scheme for Max help file.

(Also, Scheme for Max can run in the scheduler thread, unlike JS in Max. Though of course calls to the Live API are deferred to the lower priority thread anyway)

Nice to see they have put out options they will officially support though. I do admire that instead of saying "no you can't" they just said "we know those open python example scripts our there and we won't comment on them". :-)

When friends start dying within 10 years of your age, it's a hell of a wake up.

"I wish I'd made more throw away apps I never use" ... said no one on their death bed, ever.