Dispatch 182
Week ↗

Sunday, shipping music studio v1 and building out the web backend

Sunday the 15th. Sixteen commits across four repos. Not a quiet day. The headline was Majiks Studio Pro hitting v1.0.0 with a Complete edition DMG that ships 15 GB including ACE-Step models and ffmpeg. I wro…

Commits
16
Systems
4
Read
2min
Product capture

Majiks Studio — effects.

Sunday the 15th. Sixteen commits across four repos. Not a quiet day.

The headline was Majiks Studio Pro hitting v1.0.0 with a Complete edition DMG that ships 15 GB including ACE-Step models and ffmpeg. I wrote the build scripts, the download page, the roadmap, and the deployment summary. A big chunk of the day went to fixing critical bugs found in pre-launch code review across fourteen files. Pop-out crash, RPC hanging, license UX, file store paths. The fixes came clean: a hundred lines added, two hundred and forty-seven removed. It was the kind of cleanup you do right before shipping when everything that could be wrong gets shown to you at once. I also pushed a smaller follow-up fix for LibraryStore and SessionStore, then went back one more time for the Codex review issues. The final pass hit pop-out crash, RPC hanging, and license UX again, so clearly I needed to stare at it longer between rounds.

There was a weird detour with ace-step-1.5, a one-line change to cast a bool tensor to int32 before argsort in pack_sequences. You do not invent these bugs. They invent themselves, and they only show up at night. One line added, one removed, and the model stops screaming.

I wrote the build scripts, the download page, the roadmap, and the deployment summary.

The web side told a different story. I committed the initial Majiks Studio website at v1.0.0 with 122 files, then did something heavier in the web app itself: wired every frontend tab to real backend APIs and fixed the queue architecture. That single commit touched seventeen files, added two thousand four hundred and fifty-two lines, removed two hundred and eighty-two. It was the kind of refactor that makes the old code look like a guess.

Behind that, I integrated the real ACE-Step 1.5 API for GPU music generation, flipped the Docker worker to be compatible with PyTorch 2.5.1 on a Tesla P40, and removed the read-only volume mount that was blocking checkpoint downloads. The worker stack finally did what it was supposed to do on the first try, which I immediately suspected was a sign I forgot something. I did not.

Also today: the downloadable website project landed with full docs, Stripe setup notes, and a Docker Compose stack, all in one initial commit.

It was a shipping day wrapped in a cleanup day, which is just how it goes when the code review finds everything before the customer does.

Also in the frame

Real product captures — click any to enlarge.

majiks
majiks
majiks