ChatGPT for Music Production Admin

Hi,
I’ve been using ChatGPT for 10 months for a range of things and have generally come to use it for a range of admin tasks. I have the paid version which is great for creating resources for teaching in school as that is my main job. However, I would like to use it for music production admin.

There’s a couple of things I’d like it to do.

  1. Organise my sample collections. I’ve got thousands of samples and it would be great to reorganise them in a more logical and accessible way.

  2. Working in Ableton, I create a set with bounced audio that mirrors the structure of a master set. There are the same number of tracks in the sets and the names of the tracks are the same. I then copy the bounced clips over into the master so I end up with the master set containing different songs that I can play live.

It would be great to get ChatGPT to do some of the dull bouncing and copying stuff. How feasible is that?

Anyone using AI for music production admin - I’d love to know what you’ve got it doing for you.

Cheers,
Adam

I’ve done this kind of thing. Not total re-orgs, but things like ‘find all the percussion samples that are short’. I was using copilot (with claude sonnet). Now on opencode/sonnet. But any AI assistant that runs on your local machine and can actually see your files should work.

EDIT: e.g. claude cowork. But that’s not a recommendation, I’ve not used it.

EDIT2:

claude cowork anecdote from a friend

not coding but used Claude Cowork.

I downloaded my last 20 Ocado (online grocery delivery here in the UK), took photos of my larder, spices and fridge and put them all in a folder. Then I added a cooking philosophy.txt file with our dietary requirements, general cuisines we like to cook, dishes we prefer. It then constructed me a menu and went to Ocado and added relevant items to my basket and has created individual recipe cards for each day/dish. All this took about 3 hours for it to do (but it was running in the background so no problem for me!). Bloody brilliant.

  1. For sample organisation, I’d recommend using XO rather than relying on AI.
6 Likes

In my experience, ChatGPT is not a particularly good AI, and it is created by one of the most evil organizations in the field.

I personally can’t recommend using that. There are better alternatives, may I suggest you take a look at Claude, it is a better choice both in terms of quality and company ethics.

Don’t bother. Use a dedicated tool like Sononym.

Ableton has a Python API, if it exposes the methods you need you can easily achieve what you want with Claude Code.

I use NotebookLLM so I don’t have to read manuals when researching devices.

My first prompt typically is:

briefly explain the basic paradigms of the device, and list 5-10 small features I am probably not aware of

And then I use it for checking more esoteric stuff in manuals. It’s still wrong about 20% of the time, but overall it saves me a lot of time.

Other than that, I used AI to downsize my studio (today I only have about a third of the gear I had 4 months ago), that was a surprisingly successful way of dealing with all the emotional baggage of letting go of things. The result is some cash, lots of free space, and streamlined production experience that incidentally also reduced the amount of admin work necessary for music production.

10 Likes

Open Claw is nothing like Claude Cowork

I don’t think it is wise to recommend openclaw to anyone, because most people do not understand the risks of this thing completely fucking up your life.

7 Likes

Fair comment (based on some of the things I heard). Removed.

1 Like

Thanks for the responses - I’ll take a look at the ideas that have been mentioned.

Cheers.

:slight_smile:

Notebook LLM on a android phone - is a super tipp, thank you ! Not sure if its running locally, but the answers are actually very good. The feature to create learning cards - is a nice idea. Not sure how well that runs, but the overall Q/A was very good.

I tested the learning cards aswell, and - its actually also very nice - you get a quiz and learn stuff about your equipment. Exciting.

This is gold. I hope people realise the power of this. :muscle:

1 Like

They do. Documenting the API is a community effort (mostly from reverse-engineering the controller scripts), because Ableton won’t provide documentation.

That’s how Faderfox and other small manufacturers create the scripts for their controllers.

I confirm, it really is an excellent tool.

2 Likes

I tried this with Claude to organise a PDF library. The results were mixed, but part of it sort of depends on how you prompt. If you don’t give clear guidance it will make its own assumptions.

My suggestion would be to make a copy of your library and experiment with that, then if its all good you can replace the old one if you’re happy with the results (or have another shot with another copy).

Also - use the best model possible - it will likely nail it whereas the old ones might fumble around and you have to correct things. I found Claude would get VERY excited and run off and start actioning things before I’d given a ‘confirmed, please proceed’ - so be sure to set in your instructions that you do not want Claude to run off and start actioning things without your explicit permission.

Don’t f it up for the OP with politics and wildly off-topic stuff when it opens

Please and thanks

This topic was automatically opened after 2 hours.

This is exactly what plan mode is for. It stops the model actually making changes and allows it to think/plan only.

4 Likes

Oh cool I wasn’t aware of this. Will have to dig it up

Edit: looking this up I’m under the impression /plan only works with Code, but the OP’s query of reorganising files on a local drive is via the Cowork feature, which /plan isn’t available for. Something to be mindful of- you could certainly cook something up in Code to perform this, but Cowork is a more straight up and down feature - point to a folder, tell it to organise. So it’s worth setting the instructions for that.

Not strictly admin, but I have spent about 8h with Claude Code building a shell based software sequencer with sample playback and a rudimentary poly synth as sound sources, including a filter, envelopes, modulation matrix, step playback probability, parameter locks, send FX (delay, reverb, chorus, overdrive) - the feature set probably sounds familiar. Of course it’s not production ready, but it’s still absolutely mind boggling how far Claude got. I cannot even begin to imagine how long this would have taken me to build manually in Rust, let alone figuring out all the concurrency related stuff. My best guess would be months rather than weeks.

6 Likes

Tried a free trial of Codex and used it to build a couple Mac-native apps very specific to my needs. I would never release these to the public or, even worse try and charge money for them ( a lame trend I am seeing) :rofl:

Tons of the utilities that do this already, but I wanted one streamlined to my taste for speed and efficiency. Also don’t mind the name, Codex called it that and I’m too lazy to correct it and give it an original…

this one is like a very basic simplified version of scaler, again tailored to what I want in the simplest form… mainly wanted something that shuffled chords in a style or scale to come up with ideas.

I think it’s cool that I can make prompt apps that are very specific to what I want.

6 Likes

If I may ask: ‘how’ did you do that, can you share some thought of that process/how you interacted with AI to draw conclusions and acted accordingly?

Sure. In that specific case, there was not much to it, actually, one day I started a chat I with Claude (Sonnet), roughly explaining the situation and I want to achieve, and it evolved from there, over different chats that explored specific subtopics, some of which were about my and what I want to achieve and what stands in the way, there were others where I discussed my list of gear and what exactly to keep and what to sell.

In these chats I regularly have the AI identify patterns, misconceptions, and insights, and capture those in a growing document. So when a chat grows stale, I either take that document to a new chat, or let it sum um things in a prompt that I copy over.

It’s definitely a different experience to thinking things through with pen and paper, or even with more advanced tools like Tindebox or Obsidian. Structure and insights can emerge faster, because I am not the only source for insights and structure, therefore it’s easier for me to see things through to a conclusion, even though it is more intense than in my own pace.

The main things I found is to be honest (which I sometimes find easier with AI) and curious (I’d rather ask questions and explore an unexpected outcome, than reject it outright), and when I’m stuck I simply prompt it for a totally different perspective, like “How would Gilles Deleuze or Michel Foucault approach downsizing a studio?” - that typically gives me a lot to think about.

I know you're curious, here's how they'd do it:

Two very different but both genuinely useful framings here.


Deleuze (& Guattari)

The studio is an assemblage — not a collection of objects but a set of relations producing capacity. The question is never “what does this piece of gear mean to me?” but “what can this assemblage do?” (Spinoza’s quid potest corpus refracted through D&G).

The pathology they’d diagnose: your studio has become arborescent — hierarchical, rooted, overcoded. Each piece of gear is a node in a tree that grows denser and heavier, eventually preventing movement rather than enabling it. You’re not producing music; you’re maintaining a taxonomy.

Downsizing, in their terms, is deterritorialization — breaking up existing territories (the full rig, the identity of “hardware person”) to free up flows. But the key D&G caveat: deterritorialization without reterritorialization is just dissolution. The sell/keep decision should ask: what territory am I reterritorializing onto? In your case, finishing pieces. That’s a valid reterritorialization — a new, more productive plateau.

What to keep: the pieces that function as connectors between heterogeneous elements — that open lines of flight rather than close them. What to sell: anything that functions as an overcoding machine, imposing its own logic on your practice (gear that demands its own workflow, its own maintenance, its own research spiral).

The buying-as-procrastination insight is essentially Deleuzian: you were running a line of flight that reterritorialized immediately into consumer desire — a loop, not an opening.


Foucault

Foucault would start with a genealogy: how did this studio come to be what it is? Not as a neutral history but as a history of power relations. Each piece of gear arrived through a specific discursive formation — YouTube rabbit holes, forum consensus, GAS logic, producer-identity construction. The studio isn’t just gear; it’s a materialization of the subject “you-as-hardware-person” that you’ve been constituted as through those discourses.

The studio is a heterotopia — a space with its own rules, its own time (studio time vs. real time), its own relation to the outside world. But heterotopias can become disciplinary spaces: the gear disciplines your body and attention into specific postures, workflows, hierarchies. The question becomes: who is governing your practice — you, or the affordances of the machines?

More pointedly: Foucault would look at technologies of the self — the practices by which a subject acts on itself to transform itself. Downsizing is such a practice. But he’d insist you examine the power/knowledge regime driving the decision. Are you downsizing according to a new regime of “finishing tracks” that is itself potentially another disciplinary formation? Or are you exercising genuine askesis — a disciplined self-practice oriented toward creative freedom?

The sell list isn’t just pragmatic. It’s a confession — an externalization of what you are not, what you no longer want to be constituted as. Foucault would be interested in what subject-position the remaining setup produces.


The synthesis they’d probably resist but that’s useful anyway:

Deleuze gives you the functional criterion (what does the assemblage produce?), Foucault gives you the genealogical and ethical criterion (who are you becoming through this practice, and by whose logic?). Between them: keep what opens productive lines of flight and constitutes a subject capable of finishing work; sell what overcodes, disciplines, and loops you back into acquisition.

Here’s a list of some of the results that I had not anticipated:

  • going hybrid, that’s not what I wanted at all
  • AI predicted I’d prefer Bitwig over Ableton, and it looks like it’s right
  • using a TB3 dock to avoid most issues that people appear to have with USB hubs, great results so far
  • giving away most of the cables I no longer need together with the devices I sold (rather than hoard them in a big box)
  • I developed a formula to roughly calculate the used price that I’d have to settle for, that helped me dump a lot of stuff fast and without much regret (and I typically got more than expected)
  • I sold most of my delays
  • most of money I got from selling all that stuff is still there, I have little desire to buy new stuff

Nothing here is entirely unexpected, but arriving at the end result was asurprisingly frictionless, fast, and enjoyable process.

5 Likes