dean.winter
Member
Hey, thought I'd share an interesting AI use with FSP. While I generally believe the production of art should be left to humans, AI does offer some interesting uses for manual organizational work. Here's a couple use cases.
I ran a session the other day for a jazz quartet. It was 7 songs, and involved 18 channels (2 upright bass, 2 guitar, 1 sax, 11 drums, and 2 rooms). Each song was 7-10 minutes long (cause, you know, jazz), and I did a new FSP session for each song. Normally, this would mean that when I mix I'd set a static mix for one song, and then copy that mix manually to each of the other songs. This works fine, but is tedious. So I thought I'd try an experiment - since Claude can read most of the files that FSP uses, I pointed it at the directory with the songs and said (paraphrasing) - "Can you apply all the mix settings from song A to songs B, C, D, and so on? Make a copy of each of the target songs so you don't overwrite the originals". And holy crap, it worked like a charm. Took about 30 seconds and copied all the mix settings (levels, pan, fx, etc) to each of the target songs. Probably saved me an hour or so of work.
Since then I've used it for a couple other purposes. One more that was very helpful - Claude can read I/O maps. In my studio I run by default at 48khz, but I sometimes have clients who want higher sample rates. Since I heavily use ADAT, MADI, and Dante, changing sample rates also changes the number and mapping of my available channels. In my case that means I drop from 128 channels of A/D and D/A to 64 when going from 48khz to 96khz. It also re-indexes the numbering, so (e.g.) channels 65/66 become 33/34 and so on. As you might expect this makes my 48khz FSP I/O maps completely useless. Normally re-mapping requires hours of setup, but Claude can read the files (including RME TotalMix workspaces) and just do it for you.
Just a couple of thoughts I thought I'd share with the folks here. I know that AI use is potentially controversial, and god knows I share the dislike in a whole bunch of cases, but for these kinds of organizational uses it really is a pretty significant time saver.
Dean
I ran a session the other day for a jazz quartet. It was 7 songs, and involved 18 channels (2 upright bass, 2 guitar, 1 sax, 11 drums, and 2 rooms). Each song was 7-10 minutes long (cause, you know, jazz), and I did a new FSP session for each song. Normally, this would mean that when I mix I'd set a static mix for one song, and then copy that mix manually to each of the other songs. This works fine, but is tedious. So I thought I'd try an experiment - since Claude can read most of the files that FSP uses, I pointed it at the directory with the songs and said (paraphrasing) - "Can you apply all the mix settings from song A to songs B, C, D, and so on? Make a copy of each of the target songs so you don't overwrite the originals". And holy crap, it worked like a charm. Took about 30 seconds and copied all the mix settings (levels, pan, fx, etc) to each of the target songs. Probably saved me an hour or so of work.
Since then I've used it for a couple other purposes. One more that was very helpful - Claude can read I/O maps. In my studio I run by default at 48khz, but I sometimes have clients who want higher sample rates. Since I heavily use ADAT, MADI, and Dante, changing sample rates also changes the number and mapping of my available channels. In my case that means I drop from 128 channels of A/D and D/A to 64 when going from 48khz to 96khz. It also re-indexes the numbering, so (e.g.) channels 65/66 become 33/34 and so on. As you might expect this makes my 48khz FSP I/O maps completely useless. Normally re-mapping requires hours of setup, but Claude can read the files (including RME TotalMix workspaces) and just do it for you.
Just a couple of thoughts I thought I'd share with the folks here. I know that AI use is potentially controversial, and god knows I share the dislike in a whole bunch of cases, but for these kinds of organizational uses it really is a pretty significant time saver.
Dean
