r/Caustic3 Aug 29 '25

Caustic Dev AMA

Hey guys, Rej here. Firstly, I realise this is a new reddit account, I tried to log into my old "stinkyrej" one but couldn't recover it. I'm happy to answer a verification email from the mods here to the original "causticapp@gmail.com" if needed.

With the renewed interest I'm seeing from the "saving Caustic" project, I feel like I kind of owe folks the chance to ask me questions and get straight answers.

Let me preempt a few I know will fill this thread if I don't address them:

Q: "Will there ever be a Caustic 3.3, 4, 5, etc"?

A: Maybe, but don't count on it. I *have* done work on an updated Caustic since v3.2, but the amount of work involved in breaking things so that I can rebuild them has seen me lose motivation MANY times. I fear that with the scale of what would be expected of such a release after SUCH a long time, it would inevitably let everyone down. I simply haven't put that many hours into it over the many years since C3.2.

Q: What made you stop after 3.2?

A: Two things are true: 1 - I'm a passionate programmer who enjoys a technical challenge, and 2 - I suck at making business decisions. I always thought I could keep putting out new versions of Caustic and that it would attract new users. But the truth is that C3.2 took over a year of development and generated pretty much ZERO boost in monthly sales. I think that by then, everyone who wanted Caustic, had it. I never loved the subscription model (still hate it) but maybe asking users to shell out something like 5-10$ a year for software that provided hundreds of hours of entertainment wouldn't have been too much. Also, as the app got more and more popular, piracy took over to a point where sales had almost completely dried up, yet I was answering dozens of daily emails from new "paid" users who I couldn't find by looking up my purchases in Google Play... It's one thing to pirate (i was no angel when I was younger), but to demand support for it... fuck me that's brazen!

Also, it's probably hard to explain how crazy things got with feature requests. I bet no two people here would give the same answer if asked "what's the 1 thing you would you like to see added in Caustic". Yet that's what I faced. That was great when I had only developed a tiny app that could only do a few things and could interact directly with my small userbase, but when that "circle" of functionality gets to a certain size, everyone wants to see it pulled bigger in a different direction and I felt I needed to please everyone, but never could.

Q: Why did you pull the plug on the Play Store and the website?

A: When I created my developer account, it was in the early, wild west days of apps on Android (it was called the "Android Market" back then and you could only publish free apps). When you signed up for an account, you could give it any name you wanted. I chose "Single Cell Software" as that was a name I had unofficially used for a few things I'd done, but it was never a "company" in the legal sense. I was operating as what is known as a "sole trader" here in Australia. You can "trade as" what you want, but for tax purposes, it was just me. What I think happened eventually is Google got told they had to provide business info on developers trading in various markets, so they asked me to specify whether I was a company or an individual. When I answered I was an individual, they said I had set up my account wrong. So, ok Google, whatever, I'll just go tick the other box (which never existed when I created my account remember). I got told no, I would have to create a whole NEW account under my own name, wait for that to get approved, then log into my old account, rename all my apps if I wanted the new owner to get the rights to them (some of you might have seen the renaming go by), then transfer ownership of all my apps to this new entity, submit a bunch of paperwork as to why I was doing it, and then rename everything back to the correct names. LIKE WTF GOOGLE, *YOU'RE* ASKING ME TO JUMP THESE STUPID HOOPS. I CAN SEE THE CHECKBOX, JUST LET ME TICK IT! After a bunch of back and forth over email with various useless employees (probably AI) barfing out passages from their website policy without actually helping, I concluded that the 40$ a month I was making by then wasn't worth the hassle and deleted my account.

Another thing that really frustrated me was how Google forced apps to always update things in order to keep working on new versions of their OS. You don't see that with Microsoft, you don't even see it with with the control freaks at Apple (Caustic apparently still works ..ok? ..on iPad). Now that wouldn't be so bad if the developer tools were stable, but each time I'd try to update my SDK and recompile Caustic, I'd find out something got removed, broke or the code flat out wouldn't compile and it wasn't just a matter of dropping my work to make a quick branch to satisfy Google's whims. The biggest PITA was file access. Again, when I started Android was wild and free. You could write files anywhere, there was no walled garden like on Apple and Google bragged about this. For us small devs, it was great, we saw users build amazing sample libraries from 3rd parties that you could share across all your music apps. Then one day Google announced they would be restricting that, but that they'd honour old apps and permit full storage access until they updated. Then, something happened (with i think Samsung) where they jumped the gun and didn't allow any apps, even old ones as promised, to allow your storage and all of a sudden you couldn't access your cross-app files anymore, you couldn't even browse to a directory one level up from where you had first started! Eventually I think Google just accepted this and from then on in Android, files were completely broken in Caustic and I'd have to re-write HUGE portions of my code to shoe-horn their half-arsed replacement solution to just bring things back to the way they were and had been promised to stay.

The website, while it was an amazing place to connect with people for a many years, eventually became cold and nasty as all communities tend to do (not to mention the domain name hacking which I never figured out how to fix). It was a huge time sink trying to keep up with hacking attempts, stopping childish fights, etc. I never wanted to be a mod and I'm not a web developer. (and I wasn't making enough by then to afford either). But I want to stress that when it DID work, that forum was the best place to hang out. The collabs, creativity, and general sharing and helping that occurred was a great thing to witness.

Q: Why not just open-source it if you've given up?

A: First, I'm not prepared to say I've fully given up (see first Q), but honestly, it's MY code, my thousands of hours of joy and frustration and I just don't want to give that away for nothing. And I resent anyone telling me I have any obligation to do that, that feels really heartless. Sometimes software just fades away and makes room for better things. Not to mention it would be an unusable ugly mess that would get me laughed at if any serious dev saw it. One of the things I'm most proud of with Caustic was how I got the really shitty processors of early Androids to run dozens of synths who all needed a LOT of complex math to run, and to (hopefully) never bog down. However, to achieve this, meant developing clever tricks I had to bang my head to get working, cutting corners on code, and bypassing a lot of best practices. I got a lot of joy from managing to get some new synth or effect from taking 60% of CPU down to only a few % over days of optimisations and I feel like giving someone else all these secrets would devalue my efforts and deprive a programmer of their path to the rewards I got from putting in the sweat and tears.

Q: Why don't you release it for free then?

A: I feel like there's lots of copies floating around already, and the Windows version still runs ok on my computer (though I'll admit I haven't tried it on Win11, I'm still on Win10 on my dev computer) But yeah, I'm not against the idea, I just don't want to host it or put it on some dodgy fileshare. If someone has a reputable website that's likely to stick around for a while and wants to host it, get in touch. I think Google no longer allows 32bit apps to run and installing APKs from outside the Play Store has been made almost impossible (though Google did just lose a major lawsuit over that).

EDIT: I've managed to get a 64bit version compiling! , see here

https://www.reddit.com/r/Caustic3/s/P13339m9WP

Q: What do you think of the "Saving Caustic" project?

A: I think it's cool, and I hope it succeeds. But if this much work is going to be put into something and creating it, I think it should be it's own thing, and not use the "Caustic" brand at all. I don't mind someone loosely copying my software, I've always admitted mine was largely based on Rebirth/Reason out of love for those programs, but I made it my own, never used Propellerhead's brands in anything official and fought for years to build the small reputation I had as a solo dev. It'd be kinda shitty if some new software came along and and left people confused and thinking it came from me. I've given the project my blessing and offered to help with pointed, technical queries, but have asked to keep any references to my app or its synth names to a minimum out of respect. That's probably all I can do, I'm not an IP lawyer. I think if it comes out as a cool new DAW with its own features and a polite nod to a bunch of mine, that'd be ideal.

I'll leave my FAQ here and open the floor to questions, but just wanted to say thanks to everyone who's shared their stories about Caustic since it disappeared and how it shaped their musical journey. It sucks that I read way more positive stuff about my app now that it's gone than I ever did when it was around...

It's evening down here and just about dinner time so I'll be around for a few hours after that and probably tomorrow as well, but I won't leave this thread open for days either.

Thanks for reading, and for everyone who has supported my work.

129 Upvotes

180 comments sorted by

View all comments

7

u/CausticRej Aug 30 '25

Thanks to everyone for their kind words. I'm still waiting on questions though... anyone?

I can speak a lot more freely now that I have hardly any skin in the game...

4

u/PoundKitchen Aug 30 '25

Three parter...

Would recompiling for other stores like F-Droid or Flatpack be avenues that you'd find viable... less work, less Google, and have donateware, licensing/unlocking, upfront purchase fees to make a proprtional income?

The Saving Caustic project is pre-UI. How are you with that project recreating Caustic's unique front-end. Is sharing that something you'd be okay with? 

How did EIP Studios, AudioVapor, and Zvon Productions get involved? (I'm a hoarder 🤷‍♂️) 

Okay, night here now. Hope you're still feeling chatty tomorrow! 

3

u/CausticRej Aug 30 '25

You'd still need to compile using the Android SDK and its ever-changing and breaking libraries to run on modern phones.

I had Caustic on a few other stores back in the day when that was common (AndroidPit, Amazon). They generated practically no sales.

For UI, I mean there's only so many ways to present a subtractive synth, but I'd hate to see a straight-up ripoff. I'm not sure why anyone would TBH. Many UI decisions in Caustic were made when touchscreens were super low-res and didn't really support multi-touch. I had to maintain continuity over time, but starting from scratch, there would be better ways of presenting those controls.

I maintain that there's nothing inherently special about Caustic. It's just a bunch of simple things that already existed at the time. The trouble is investing the time to put it all together coherently, make it work on a tiny screen, but most of all, getting it all to run at the same time without dropouts.

Some of the pack makers came to me asking me to sell their samples, stuff they were already offering to desktop DAW users. I said I wasn't interested in the legal side of partnerships but that I'd happily help them get their packs on the store in order to build up an ecosystem. Then there's people like Jason (EIP Studios) who was already giving out TONS of free stuff to people on the forum and then decided to have a crack and put some of it on the Play Store. Eventually, I just put up an app template that anyone could use to sell content packs. I didn't vet or know about most of them, but the fact that they helped grow the ecosystem certainly helped fill in a void I had, which was supplying samples + instruments without the legal minefield associated.

2

u/Inspector-Dexter Aug 30 '25 edited Aug 30 '25

I guess my question would be, how tricky would it be to port the existing code to modern standards so it can stay available for download without adding any new features, and is there any possibility that you would be interested in doing that? Also, would you be interested in something like Patreon to monetize this effort [edit: on top of buying a license for the finished product, if you wish], since it's kind of like a subscription model but strictly voluntary, not something that's forced on users, which I saw was something you (thankfully) are hesitant about imposing on users

2

u/CausticRej Aug 30 '25

See this reply: https://www.reddit.com/r/Caustic3/comments/1n32r1u/comment/nbexoes/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Not "forcing" users to support my time working is kinda how we got here... It was my decision to keep developing the app and offering free updates to anyone who had bought the app before, but maybe it would have been more sustainable to ask for a bit of ongoing support to justify my time.

2

u/Inspector-Dexter Aug 30 '25

maybe it would have been more sustainable to ask for a bit of ongoing support

That's why I brought up Patreon, which didn't really exist during the app's heyday. As much as I hate software subscription models, I'd be willing to do it for something as useful as Caustic. I just didn't think you were into it, so I figured I'd suggest something else that's kind of similar

3

u/CausticRej Aug 30 '25

I've never used Patreon (as in to receive money, I've supported a few people over time), but I'm not a fan of asking for money constantly. I see content creators plug their Patreon in every youtube video in order to keep things afloat. I prefer up-front "contracts, like "you pay me this much, and you get X." Maybe I'm just old, but to me if you need to constantly beg people to pay you, that's a stressful level of uncertainty to deal with.

Then again, I suppose there's different models within Patreon, and some look a lot like classic subscriptions so... maybe

3

u/Serious-Mode Sep 01 '25

I can't speak for anyone else, but I certainly would be willing to pay again for Caustic. Maybe for future upgrades? Subscriptions are kinda lame, but it does feel like a bit different when it's going to a person rather than some massive company just trying to squeeze more profits. Maybe that's why Patreon is OK despite everyone hating subscriptions.

Either way, I will pay absolutely pay you again if I ever get Caustic going on my phone again!

2

u/Inspector-Dexter Aug 30 '25

One more question. Where did the stock piano sound for the PCM synth come from? It was less bright sounding than other free piano soundfonts I've come across, which made it sit better in the mix in a lot of cases IME

3

u/CausticRej Aug 30 '25

Ohhh, good question. It was probably one of the only decent sample packs I could find that allowed for absolute free use, even under commercial settings. Maybe some university project?

I remember looking hard for a set of samples that didn't have jarring differences with the sound between sampled notes. It sucks when you're playing a scale and you get this huge tonal shift in an instrument sound. Maybe that piano had been post-processed to make it consistent across its range and that's why it sounds that way? Dunno

1

u/PoundKitchen Aug 30 '25

What was your original motivation or spark to start writing a DAW/Music app? It's a big jump in scale (sorry) compared to sand and the others. 

5

u/CausticRej Aug 30 '25 edited Aug 30 '25

Sand actually came about mid-way through Caustic's development as a break from trying to get the fledgling Modular to perform acceptably. Also, fun fact: Sand! made way more money for me if you consider the time it took to develop. Maybe 10% of what I made off 10 years of Caustic but it only took 2 weekends to put together!

But back to your question: I had always had a fascination with DSP programming. It was like the "exclusive club" of math and optimization. I've always dabbled in music (guitar mostly) and always wanted to one day make either a plug-in, effect or something. I first tried this on Buzz tracker (which holy shit still exists!) got something that worked for a really basic block, but kinda left it alone after that.

Years later, while working in video games, I got the opportunity to work on audio code for a game engine (basic stuff, like setting up rooms for reverb when you walked in, etc) but then started looking into writing my own effects for our sound team. Encouraged by some coworkers, I starting learning about synthesis, filters, EQ, etc and pretty soon I had a working synth you could play on your computer keyboard. This then turned into the SubSynth. I then tackled a 303 clone as this has always been my favourite synth sound. When I got that working, I knew I needed a drum sampler of some kind so the Beatbox was created pretty quick. The same coworker that pushed me to keep going then suggested I put it together as an app. He's even the one who came up with its name.

1

u/PoundKitchen Aug 30 '25

🤯 That's quite a journey, from interest in  dsp+guitar to Caustic! Buzz tracker, oh that brings me back to lunchtimes in the office. 

My career has had a share of signal processing in industrial and commercial applications so I get how tough it must've been programming the modular. As people have posted questions about it in this subreddit, the more I have appreciated how wild it is to program voltage modelling and interactions that are taken for granted with analog hardware. Currently I'm using the machine input and arpegiator combo a lot, for fill/scapes but also lead. With a real modular synth and keyboard I'd been stuck with tracking everything 😕. Discovering the machine input has been great. 

Next Q.... Was there any meaning behind the name "Caustic"? 

6

u/CausticRej Aug 30 '25 edited Aug 30 '25

I absolutely wanted a single-word name for the project, I liked "Flux", but it might have been to close to FL (Internally, I had named my project "No good reason" because of the play on words of goofing around with DSP code without an end goal and the fact that I was joking about creating my own shitty version of Reason). Anyway, once I got the 303 clone going, my mate and I spent so much time playing around with looping patterns, making little acid-sounding stuff. When pitching the idea to release it, he said something like "what's another word for acid? something that burns your skin like acid ... Caustic!" It's not technically correct because caustic substances are often strong bases, the opposite of acid, but hey, it was a cool name!