Hacker News new | ask | show | jobs
by duranduran 821 days ago
I'm working on a very experimental music generator: https://app.bars.ai (I regret my domain choice). It's free to use and you can play around with it pretty easily.

The idea is that you have a "framework" that you can change for what you want the music generator to produce. You can download the MIDI files it produces as well.

1 comments

I honestly loved (!) the created melody, but stumbled across a couple UX issues. Most of those, I think, could be fixed with smarter defaults and some tweaks. Excellent work, though. Would love to see how it develops...

During creation of a new track:

- Why do I need a description?

- Why do I need a name, actually?

- Why is there only Latin and Empty available?

- Edit: Just realised that the Latin track is hardcoded?

During editing:

- I was not sure whether / how my actions affect the tracks / track items. (One remedy could be showing the actual waveform of the created sounds in the editor instead of a placeholder waveform.)

- Creating a new instrument — I found the "Instrument Sound Pack" dropdown menu only by accident after some clicking. It would be great to see what type of instrument I'm dealing with without having to click on the instrument itself. (Maybe map it directly to the displayed name? I'd rather have Acoustic Bass 1 to 4 instead of a bunch of "Unnamed Instrum...")

- Some actions have no effect until you restart the playback (e.g. changing speed of a track item).

- Some actions stop the playback (e.g. changing the instrument type)

Thanks for checking it out!

This is really good feedback, I'll try to address some of these tonight.

I've added name and description because I made a feature where you could create an account to save your work. During development, I got tired of having to constantly recreate test scenarios, so I integrated AWS cognito and started saving compositions.

Latin is hardcoded. To be honest, I wasn't really sure what to do there. The latin template really just bootstraps the UI to save some time and act as a demo. My plan is to make 3-5 premade compositions for each major genre, and have the create flow let you pick between them.

On making changes impacting the UI, this is something that I'm still really struggling to find a balance between. I'll prioritize this higher based on what you've said!