Nice! Love seeing new ways to share music on IG without having to be a professional video editor.
I'm working on a similar tool https://kaizen.place/reel-generator . Moved the video rendering onto the client which helps keep rendering times quick and avoids the headache of managing an extra service.
+1 to the suggestion I saw for some kind of sound visual to make it even more clear there's audio.
Started with just recording the canvas using MediaRecorder (https://devtails.xyz/@adam/how-to-record-html-canvas-using-m...). This was super simple and I wish could have left it at that...But unfortunately Chrome gives you a webm file back and IG doesn't let you upload webm.
So then I went the route of ffmpeg.wasm in the browser to convert the webm to mp4.
Thank you for the feedback. Our free plan is intended to allow new artists to receive tips without any cost to them. As soon as someone starts consistently receiving money through the platform our intent is that they move to the $8 / month Pro plan bringing the fee down to 5%.
Bandcamp, for comparison, charges a 15% fee.
We are still early days and will continue to solicit feedback on our pricing model.
Nothing requires an artist to receive tips through the platform, so if they preferred buymeacoffee they can use that. We will be adding additional features to our Pro plan that will enhance the experience on top of bringing the fees to a comparable 5%.
Again, still early days. Appreciate the feedback, we will work with artists on the platform to find what works well for everyone.
My favourite win of my development blog is stopping myself from doing the same project multiple times. I used to tinker a lot, but wouldn’t document anything and so I often had to start all over when I picked that project back up.
Writing forces me to break things down into manageable chunks. I’ve seen much more consistent progress this way.
I’m trying out streaming on Twitch: twitch.tv/devtailsxyz
Mainly focused on learning rust while streaming. Streaming forces me attempt to explain what I’m doing which often shows me what I don’t properly understand.
I don't think I can edit the post, but I agree. Though many have kind of described their process which gives somewhat of a picture. If anything it's been interesting hearing different people's definitions of deployment.
I would probably condense my definition to how quickly can you go from new code added to someone seeing that code running (in web dev terms essentially available on some URL). So even if you had different layers of pipeline, the build artifact stage would still be included, because you can't deploy without it.