wrapping up the input chains i mentioned ages ago
im back to working on input chains. if anyone was interested in that concept, i have a 1000 line version of the training game im using. its just the old code with me going in for 20 minutes and cutting out a bunch of it and tacking on a training game, but maybe its easier to read than the (4000?) line old version. pretty much im building and learning muscle memory for a simple 4bar drum inputter for ableton. mostly based on 4 presses for each index finger, always swapping left-hand to right hand. i might add a bit more than 4 presses for each hand for lower percantage presses (<5% presses etc.) and then hopefully extending it out from there to do enough in ableton to write full edm tracks. or my elbows explode and i have to switch into writing it for talon voice-to-text input software. anyway im probably not going to talk anymore about these input chains. i might keep using them might not. dont know. theres some post where i talked about them for 30+ comments, about an hour long-read in one of the posts i made if anyone wants to know more.
heres a link to the 1000 line partial training game for simple drum inputter, i just uploaded: https://github.com/carptunnel/simple-drum-inputter-training-v1/blob/main/simple%204by4%20drum%20inputter%201%20v1.ahk
this might be easier to look at than 4000 lines if you wanted to build your own input system in ahk/take the same concepts into another programming language. it has a basic training game hooked in/tacked on, where gdip displays a rectangle on the screen and you have to type in the correct 16th. (4 bars of music = 64 16ths). but i mean you could do it different... you could do 8 bar sections and then theres 64 8ths or 128 16ths....) eh ffs idk how to explain all this. the training game, i run the script then i open up ableton so i have the ableton 4bar grid so i know which rectangle im meant to be inputting. since that gdip garbage stays on top of all windows. then i type whatever 3press combination for the 16th the game has generated. if i get it right, it creates a new random option from the 64 possible options. if i get it wrong, it moves back to main layer automatically, ready to attempt typing in the correct sequence again. spacebar can be used at any time in this build to go back to main layer, e.g. in case any erroneous presses were made, or just if you come back to keyboard and want to make sure youre starting off any press from main layer every time etc
cant figure out how to link to the post where i talked for an hour about them. it was the post on 2023-02-08 where i mostly talked abou the input chains ideas
yea so im not really going to talk about these input chains anymore. theres enough info if you want to build your own input system now i think. i mean personally i think the image with the thing about the dog and the fish and the mammals or whatever was enough information to go off so uploading code is just waste of time really
made a beat and drew a picture
this isnt april fools thing. also why are companies all doing april fools. i propose burning all companies to the ground that participate in april fools. companies are not ppl. company does not make jokes. its not an entity capable of making a joke. if companies start making jokes they also have to start cooking food somehow.... making other types of art maybe. idk why is companies doing april fools. idk why companies doing april fools pisses me off. theres something extremely wack about it almost every time ive seen it. also why does my microsoft login screen talk to me. i dont care what microsoft corporation has to say. i wake up in the morning WELCOME TO THE NEW DAY FROM MICROSOFT CORPORATION, MICROSOFT CORPORATION BELIEVES IT IS A BEAUTIFUL LMORNING LOOK AT THE SUNRISE IT HAS BEAUTIFUL TINGES OF PURPLE REMINISCENT OF ROSE FLOWERS PSYCCCCH APRIL FOOLS DIPSHIT, THE WEATHER IS MISERABLE, YOU JUST GOT APRIL FOOLED BY MICROSFOT CORPORATION DIKHEAD
screen capture of the midi input system im working on. even though ive done ~100/150(?)hours muscle memory into this system, im only just starting to try writing music with it. the metaphor id use is that the muscle-memory-training-games i used to learn this system are like READING... and now i have to actually learn how to WRITE with the system so its a bit different, the difference between reading and writing text maybe is the metaphor. all the pauses in this are me either a) thinking of what note to input next b) making typo c) trying to remember what the macro chain for a specific note/velocity is. the 2nd half of this video has a bit faster inputting of notes. also i just used the same velocity for all these notes, but when im not screencapping im working on getting better at inputting velocities between around 90-120 atm. also theres lots of functions that dont show up in this short video segment. pitching notes up and down octaves... changing velocity of existing notes. selecting a box of notes and deleting. all has similar but different muscle memory to learn for each function with typing on keyboard. still dont know if this makes any sense.
ultimately i want the muscle memory to be 3/4 times faster than this at least. dont know if it will happen but ill do some more inputting with it and see where it goes. i could get rid of the 4 bars and just keep using the first 2 bars, like i was doing here pretty much. thats half the muscle memory requirement gone if i did that, so should be twice as fast to learn. dont know yet. you can build these input systems a million different ways. are they worth it? probably not. you have to already know how to make music in DAW/play instrument. you have to be a programmer pretty much, and you have to sink 100s hours into boring muscle-memory-training game before even attempting to make this slow tedious inputting of actual music. id rate it . 0 out of 10 stars nah whatever but i dont recommend input systems,. like i keep saying. also i built the system just for index fingers... would probably be more ideal to build it for something like index and middle fingers... or use different hardware than qwerty/ergodox keyboard... or use talon voice-to-text software(no muscle-memory-training required for talon voice-to-text i guess looks good). which would be completely different muscle memory/no muscle memory and coding of the system layers in all cases. you can see why i talk about making a pixel-inputter system. since the muscle memory ive learned is basically to-do with inputting boxes onto a grid. its a 64 wide grid, 58 high. all the notes are limited to exact grid-coordinates atm, but i might build in things to move things slightly off grid etc.
you can see the keypresses i make onscreen. thats not normally in the code, just added for the illustrative purpose. its a lot of keypresses, but a lot of them are typos and theyre maybe nowhere near max speed yet............................. dunno. ill know in a month or 6 whether this is worth it. probably... not.. because of all the reasons i listed in the above paragraph.
the input system is doing everything in this. inputting the notes and getting ableton to play audio, mainly. most of the other functions arent shown in this clip. i think i move the pitch of an already-existing note once in this clip somewhere
also its fixed in the key of A minor/ any minor/major scale with no out-of-key notes. you dont have to build it this way.
i couldnt say for certain whether ill keep using this input system. maybe ill know in a month or 6. i think it could be stripped back in complexity and be good. dont know. ive made these input systems before over yrs
and learned them to some level so maybe i think it will work based on that. the goal would be 3/4 times faster than this inputting at least. otherwise i think i wouldnt use this system and chop bits out of it and remake it somehow and see if that works
the code for this is in the github link i posted a couple days ago if you go two posts ago the massive wall of comments i made on the post 2 days ago. its not fully finished code at all... ist just the version im working with atm. needs to be rewritten probably. its not good code. it is pretty well-commented code i think. it just does this 4bar editing of midi pretty much, its not set up for songwriting or made for multiple different computers or anything like that. im not super interested in helping people with these systems other than these text posts and any questions people have. although to be honest i wont be able to answer any questions. like its input chains. it takes a long time to learn the muscle memory.... idk wot 2 telya. write one for talon, then you dont have to learn 100 hours muscle memory. you need to know how to program to make these input systems so you gotta figure it out i guess. idk how much more detail i can go into... its input chains.... you make long chains of macros and write training games to learn the muscle memory. its an enormous waste of time
im going to start doing music posts on a different streak, if you want to listen to emo trap bangers u can find me on daily music dump probably. ive uploaded a source code of the input system im working on for electronic music. if you check my last post the link is in the comments. im not using it yet... it takes say ~200-500(?) hours muscle memory training game to learn an input system like that so idk if you really want to waste your time trying.... but yeah... maybe ill keep working on it and have a video of it working in a month or 6, dont know. maybe if you like the idea of the input system you can build something for your own needs. its just basic autohotkey script. wouldnt take long to learn how it works. maybe. but input systems like that can become enormous time-sinks. maybe in a month or 6 i should have video of it working at speed. and properly explain how it works in video format. dont know. so its just sneak peek for now i guess. input chains like that can be used for visual art as well. pixel art. bezier curves. changing color using CMYK color format. maybe something with blender/houdini scripting and low poly. whatever. i havent built any of that. ill probably do a pixel art inputter eventually. im hesitant to say what kind of 'speed increase' such input systems offer. depends how well you design the input system... and then it depends per artist. one artist might use an input system like this and get no real speed increase... another artist might get 5x faster electronic music input. you kind of have to always be adding your own macros to the system and then learning the muscle memory for what you just added... always changing the system. the input system should never really be 'finished'... youre always going to be adding functions that you find yourself reaching for over and over again. so you have to be a programmer pretty much... and you have to be an artist as well... input system isnt a silver bullet... just allows some things in the computer to be done a lot faster than regular input, maybe. but some things wont be faster than just using the normal tools like mouse and keyboard and midi clips automation etc... might be the same speed for some things. also because im a programming noob and i just built the system for spamming mouse movements and keystrokes into the ableton window... its probably always going to be somewhat a buggy piece of shit... so yea its unlikely that ill move the system into actually solid programming with a DAW that has exposed data parameters etc.
actually what im mostly interested in at the moment with the input system is just using randomizers... so having loads of different randomizer functions with parameters that can be input. i think this is one of the more interesting aspects of input system. so having a few keyboard presses that select a random snare drum sample to use, then a few presses to generate a random pre-selected chord progression midi is inputted on e.g. a melodic instrument track, then you can react to whatever the computer generates and edit that, then add some more random stuff... mostly just adding random instruments from pre-selected banks seems good.... it is kind of a chore to manually select instruments every time and the randomness can allow happy accidents. im not talking about randomly generating entire melodies... that seems kind of boring to me. just small randomizer things to get a track started off. randomize bpm, random key selector... i guess just those things
i wrote an actually good melody the other day (rarely happens). dont know what to do with it. i like the song 'avril 14' by aphex twin. maybe i could try and turn it into something like that. or turn it into a EDM song. i dont rlly know how to write edm almost all my music work is pointless noodling on piano. i fucking hate songwriting so enjoy this melody caus its bout as good as i get.
dont know if audio is in accepted of this streak. 40 second audio, open to roast
loop from remixing around with NSYNC - Bye Bye Bye. muted vocals for copyright.
so many good quality acapellas on youtube. any pop song some dude has stripped the vocal with AI and uploaded the acapella to youtube in the last couple years. looks like pop artists are starting to upload the acapellas themselves now as well. probably because of the AI stripping. and caus ppl upload 5 different versions of a song these days for more content
joined 456 days ago
Post a comment