4 ms·
Pulselyre: A touch-screen synthesizer app for live music production - https://www.pulselyre.com https://www.pulselyre.com Spent a few years experimenting with
by tekdude 6y ago
Pulselyre: A touch-screen synthesizer app for live music production - https://www.pulselyre.com https://www.pulselyre.com
Spent a few years experimenting with touchscreen UI and audio synthesis in my free time on and off, and eventually settled on an engine and interface design. The idea is to create 'instruments' in the editor (2nd screenshot) by connecting basic modules to create and transform audio based on user X/Y touch coordinates. Then, stack a bunch of instruments on screen and use your fingers to create and loop sequences of notes live on stage. The demo video ( https://youtu.be/Qk85IrgXRj0 https://youtu.be/Qk85IrgXRj0 ) shows how that part works.
Once COVID hit, I was sent home to do nothing with full pay, so I had free time and decided to power through and create a functional MVP and website. My plan was to get some beta users, polish it up, add missing features, and then start charging. I showed it around on some music production forums and to friends who dabble in it, and got terrible feedback: 1. Too hard to use; 2. not compatible with existing plugin systems; 3. terrible demo video (I'm not a musician nor an expert on creating cool synth sounds); 4. "touch screens are *"; 5. nobody wants to do live production; 6. it sounds terrible
Of those responses, #2 was the killer. Without compatibility with existing synth plugin frameworks, like VST, it was pretty much dead in the water. No producer was going to use a synth app that didn't support their favorite plugins, and no plugin developers were going to switch to an application with no users (I built my own custom plugin framework for it). I looked into adding support, but VST uses such a completely different architecture from the synth engine that I created that they couldn't really work together in any sensible way. One suggestion I got was to remove my synth engine entirely and just make the app a MIDI front-end for other synths, which is something I might do in the future, though the limitations of the MIDI protocol would mean removing a lot of functionality. (I have a new WFH job now, so no more unlimited time.) I'm also thinking of open-sourcing the project entirely, but I need to clean up some things in the codebase first.
I did decide to split out the UI manager that I created for the app into a separate open-source Windows UI framework, which I still work on and use for other small utility apps that I create: https://tinyurl.com/upbeatui https://tinyurl.com/upbeatui
If I were to do it again, I'd have started with support for existing VST plugins or MIDI and worked from there. I also wouldn't have wasted so much time figuring out auth stuff. The only costs were the domain and VPS hosting.
- michae2 6y agoThank you for the detailed comment. During quarantine I started working on a rudimentary sound engine, and this gives me a lot to think about. I really appreciate your analysis of the feedback you received. Your demo video looks really great to me. Maybe it's not something serious music production people would use, but stick this on an iPad and I could see someone having a lot of fun with it, kind of like https://loopyapp.com/ https://loopyapp.com/ or https://audiokitpro.com/synth/ https://audiokitpro.com/synth/