What changed in builds 226 to 231

Six builds in three days, which is what the end of a release looks like. Most of it was paperwork. Three things were not.

Describe a tone asks before it sends anything

Build 227.

Describe a tone works by sending what you type to a server, and from there to Anthropic, whose model builds the rig. That is the one feature in RigShed that leaves your device, and until this build it did so the first time you used it without saying so.

Now there is a panel before anything is sent. It says what goes — the words you type, the pickup type if you choose one, and a random number that counts your monthly allowance — and what does not: no name, no account, no audio. There is a link to the privacy policy and a Not now that closes it.

The check on how many tones you have left waits too, because that request carries the same identifier. Agreeing is the first thing that happens, not the thing that happens after the first request.

Stage got a button, and then got bigger

Builds 227 and 228.

Stage mode is the screen for playing rather than editing: big targets, the preset name in type you can read across a room, and a footswitch for every block in your rig that can be switched.

On iPad and Mac it had no way in. The wide layout hides the menu that opens it, so a feature built for the exact screens most likely to be on a stand at a gig was reachable only on a phone. It now sits in the board header, beside Describe a tone.

Then the footswitches themselves were made to fill a wide screen, rather than sitting in a phone-shaped column in the middle of an iPad.

A2 captures: confirmed, and it was never a version number

Build 229, and a question that had been open since August.

The short answer: captures load, whatever architecture they were trained with. That includes the one every modern capture uses, which is what people are asking about when they ask about A2.

The longer answer is more interesting than a tick in a box. The engine links five model architectures. An early version of that list left one out, and every modern capture in a nine-pack test library failed to load with “no config parser registered”. It was found against real files rather than reasoned about, which is why it is now a claim worth making.

What Neural Amp Modeler is, and whether you need it →

Manage subscription goes to Apple

Builds 229 and 230.

It used to open the paywall — the screen that sells you the thing you have already bought. It now opens Apple’s own subscription manager, which is where you actually cancel, change tier, or see what you are paying.

On the Mac that means opening the App Store rather than a sheet.

An app that makes cancelling hard is telling you something about itself. This one should not.

A Mac TestFlight copy knows what it is

Build 231.

On iPhone and iPad a TestFlight build is handed a receipt with a different name from a bought one, so the app can tell them apart. On the Mac both are called the same thing — so Mac testers were being treated as customers, and getting the locks instead of the preview.

Now the answer comes from StoreKit, which says which environment the copy was issued in on every platform. Signed by Apple, so neither signal can be faked by someone who bought the app.

And then it went to Apple

Build 231 is the one submitted for review.

Pricing and availability are set — the app is free, in every territory Apple offers. The four subscriptions exist. The privacy answers are published, and they match what this site says, which took three passes to get right and turned up four things the policy had wrong.

Nothing is purchasable yet, and will not be until the listing is live. The prices are what RigShed will launch at, not what you can buy today.