186859
Level 28 Mixist
argarak
post #186859 ::
2024.03.14 1:17pm :: edit 2024.04.19 7:48am
Xaser, nitrofurano, Blast_Brothers, Hz-Voyager, blower5, Viraxor, Max Chaplin, mirageofher, damifortune, blockblockblock, SRB2er and Kaytse liēkd this
Xaser, nitrofurano, Blast_Brothers, Hz-Voyager, blower5, Viraxor, Max Chaplin, mirageofher, damifortune, blockblockblock, SRB2er and Kaytse liēkd this
hi!
over the last little while i've been writing a small web app for musics composition. inspired by vcv rack, nanoloop, tahti.studio, hardware sequencers and probably more. it's very much in an alpha state but i'm releasing it now so that you can try it out if you like!
you can find it here: https://blipgrid.app
find the source codes here: https://github.com/argarak/blipgrid
the app uses tone.js for all the audio processing and i wrote all the ui components using lit.
how do the sequencing algorithms work?
the algorithms are "bytebeat-esque", you have a step counter `t` that executes the function once for every step. rhythmic algorithms take in the length of the sequence and return true/false if the step is active. melodic algorithms take in the globally set scale and return an index that represents a valid note within the scale. all algorithms have "controls" that allow you to manipulate their behaviour which is set internally using the `mod` parameter list.
the software does kinda lack in terms of the number of algorithms at the moment, maybe that will change in the future. haven't had a ton of time to work on this so far.
why did i write this?
1. i don't really like most of the web apps out there, with the exception of tahti.studio. either that or they're very limited. i still think my app is still quite limited but it's early days.
2. the combination of rhythmic and melodic algorithms is at least somewhat unique... it resembles how you might sequence something on a modular system, but in a more streamlined layout. the end goal is to have a program where people can try out sequencing algorithms without resorting to complicated software like pure data.
3. music program user interfaces are quite interesting to me and i thought it would be a good challenge to build something to be very fast and immediate. i believe that user interface plays a major role in the kind of music that is written.
4. i wanted to do a final university project that i was actually interested in and that i would use. somehow they let me get away with this.
5. limitation breeds creativity?
to reiterate, this is alpha software, not ready for prime time. expect to see bugs, errors, and the loss of your data (there are several known issues).
over the last little while i've been writing a small web app for musics composition. inspired by vcv rack, nanoloop, tahti.studio, hardware sequencers and probably more. it's very much in an alpha state but i'm releasing it now so that you can try it out if you like!
you can find it here: https://blipgrid.app
find the source codes here: https://github.com/argarak/blipgrid
the app uses tone.js for all the audio processing and i wrote all the ui components using lit.
how do the sequencing algorithms work?
the algorithms are "bytebeat-esque", you have a step counter `t` that executes the function once for every step. rhythmic algorithms take in the length of the sequence and return true/false if the step is active. melodic algorithms take in the globally set scale and return an index that represents a valid note within the scale. all algorithms have "controls" that allow you to manipulate their behaviour which is set internally using the `mod` parameter list.
the software does kinda lack in terms of the number of algorithms at the moment, maybe that will change in the future. haven't had a ton of time to work on this so far.
why did i write this?
1. i don't really like most of the web apps out there, with the exception of tahti.studio. either that or they're very limited. i still think my app is still quite limited but it's early days.
2. the combination of rhythmic and melodic algorithms is at least somewhat unique... it resembles how you might sequence something on a modular system, but in a more streamlined layout. the end goal is to have a program where people can try out sequencing algorithms without resorting to complicated software like pure data.
3. music program user interfaces are quite interesting to me and i thought it would be a good challenge to build something to be very fast and immediate. i believe that user interface plays a major role in the kind of music that is written.
4. i wanted to do a final university project that i was actually interested in and that i would use. somehow they let me get away with this.
5. limitation breeds creativity?
to reiterate, this is alpha software, not ready for prime time. expect to see bugs, errors, and the loss of your data (there are several known issues).