i know that the lmms community is under a dev crunch but i'm posting this anyway for future reference of devs.
first of all, i would suggest forking audacity (yeah im serious) and repurposing it to be a backend/audio engine. if you need more idea, i think lmms can use some of audacity's sampling capabilities and also the audio engine. lmms can run on top of audacity. this move can also help with improving mixing and mastering. alongside, the ability to bounce out stems can be made easier. maybe some of these features or the new ui can trickle down to the main audacity. it's a win-win for both the teams.
second change, the ui.
i saw a random image on google.
https://images.app.goo.gl/5qNmumPs9AM53nWg8
here is the issue on github
https://github.com/LMMS/lmms/issues/1911
this is a good idea but with some changes (maybe a slightly darker theme)
these are the major ideas i have rn, will update soon if i get new ideas.
unfortunately, i have no knowledge of c++ or i could have worked on this myself. the only language i know is python and that too on a beginner level.
first of all, i would suggest forking audacity (yeah im serious) and repurposing it to be a backend/audio engine. if you need more idea, i think lmms can use some of audacity's sampling capabilities and also the audio engine. lmms can run on top of audacity. this move can also help with improving mixing and mastering. alongside, the ability to bounce out stems can be made easier. maybe some of these features or the new ui can trickle down to the main audacity. it's a win-win for both the teams.
second change, the ui.
i saw a random image on google.
https://images.app.goo.gl/5qNmumPs9AM53nWg8
here is the issue on github
https://github.com/LMMS/lmms/issues/1911
this is a good idea but with some changes (maybe a slightly darker theme)
these are the major ideas i have rn, will update soon if i get new ideas.
unfortunately, i have no knowledge of c++ or i could have worked on this myself. the only language i know is python and that too on a beginner level.