Building a Music Production System Between My Phone and Computer
I rotate hobbies depending on the time of year and music production always seems to come back in winter. I do not know if that says anything about me, but if I look at the last few years, that is the pattern. As soon as the days get shorter, I start wanting to make tracks again.
This year started the same way.
Around December, I got back into production after a two-year break. There was nothing dramatic behind that break. I had been focusing more on my health and giving myself time to build better habits. Then I met a new group of people, saw what they were making, heard how seriously they talked about their craft and that was enough to wake something up again.
Once that happens, I always run into the same question first. Where do I start?
Starting With a Theme
This time I wanted to work around specific concepts instead of opening a music production software and waiting for something to happen. The Vatican was one of those concepts. I liked the idea because it gave me something visual and emotional to react to. Not the literal city in a documentary sense, but the atmosphere I associate with it. Space, ritual, stone, distance, silence, crowds, echo, ceremony. That is the kind of material I can actually work with.
My process is usually a mix of a few things: melodies from a MIDI keyboard, external mp3 sounds, free samples and textures like crowd noise or room ambience.
Then I start layering, cutting, stretching and reshaping existing things until they sit together properly. I never felt guilty about working that way because production is full of reuse (and I'll never call it stealing). You take existing material, change it, combine it with something else and push it far enough that it becomes its own thing. Sometimes you make it better, sometimes you ruin it.
Either way, once you turn it into something personal, it becomes yours, just like I did with this one.
The Actual Problem Was Never the Idea
The problem was not inspiration. The problem was continuity. I do not get ideas on command, most of them show up when I am away from the computer. Usually I record a voice note on my phone, maybe hum a melody, maybe note down a texture or an arrangement idea, then tell myself I will deal with it later.
Later was where the process kept breaking.
My phone and computer were living in separate worlds. Ideas started on the phone and got stranded there. The computer was where the actual work happened, but moving material between the two always felt annoying enough to slow me down. Small amounts of distraction are enough to kill momentum when you are trying to do something creative.
That was the real issue I needed to solve. I needed one place where ideas could survive the jump from mobile capture to actual production.
Working with Soundtrap
I tested a bunch of programs before landing on Soundtrap. At first I did not trust it much. It had that strange feeling some products get when they seem half-alive online. Since Spotify had owned it, I assumed it might be one of those acquisitions that quietly disappears later. Then I saw it had been re-acquired by the original owners and that made me a lot more comfortable using it. At least it looked like something people still cared about instead of an abandoned side product waiting to be buried. More importantly, it actually solved the problem I had.
The free version already did enough for me. I could move between devices, sketch ideas quickly and keep the work in one environment. That alone made it more useful to me than GarageBand. GarageBand was never the issue in terms of quality. The issue was support. I needed something that worked across my actual devices, including Android and the web. If a tool traps me on one machine, it breaks the whole point of how I work.
Soundtrap gives me access across devices, a simple production environment, enough built-in material to experiment quickly, version history so I can move backward and forward without fear and easy export when I’m done. It’s purely practical, and that’s exactly why it works for me.
Getting Source Material Into the Workflow
Once I had the environment, I still needed a clean way to collect and process source audio. That broke down into two tasks: downloading the audio I wanted to study or reshape and splitting it into usable parts.
For downloads, I used yt-dlp. Mostly because I wanted to avoid every shady converter site on the internet. Those tools are always packed with limits, bad quality, or suspicious behavior. yt-dlp is direct and predictable.
For stem separation, I used Demucs. I had heard about Spleeter before, but Demucs ended up fitting what I needed better. I wanted a practical way to separate vocals, drums, and instrumental layers so I could take apart interesting source material and work with pieces instead of full tracks. That kind of control matters. Once a sound is separated, it becomes much easier to borrow an energy, isolate a texture or rebuild the emotional shape of something without just dragging a whole file into a project and hoping it works.
How Google Colab Ended Up in the Middle of This
The funny part is that Google Colab ended up being one of the most useful parts of the whole setup. I had used it before, but only for small throwaway scripts, never as part of a music workflow. Then I realized I could run a script in the browser, process audio there, and send the results straight into Google Drive. That changed everything because it removed another annoying transfer step. A lot of apps can import directly from Drive, especially on Android, so it became the most practical place to store and move the files.
The System as a Whole
Once I had everything connected, the process stopped feeling fragmented. I can now catch ideas on my phone, keep projects accessible across devices, bring in reference or source audio cleanly, split sounds into stems when needed, store outputs somewhere reliable and continue arranging and mixing without losing momentum.
That is what I actually wanted from the beginning. I wanted continuity. I had the theme, the tools and a way to move between devices without breaking the flow. That let me focus my energy on what actually matters to me, shaping the track.
What matters more is that I solved a workflow problem that had been blocking me for a long time. Before this, ideas got stuck between the phone and the computer. I would capture something in one place and fail to carry it into the place where I could actually build it. Now that gap is much smaller.
That makes this post part of a bigger thing I have been working on around the idea of a Mobputer. I am trying to make my devices feel less separate and more like parts of the same working environment. This music setup is one version of that. It is not about turning a phone into a perfect studio. It is about making sure ideas do not die during transfer.
That is enough. A system is only useful if it gets you to the work.