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.
i just use index fingers to type my system. which i guess is super slow... why not build a system that uses all fingers? well like ive mentioned.... i have broken fingers on each hand.... and in the past i learned an input system which i never ended up using.... and idk i just found it straining to use all fingers on qwerty/ergodox keyboard...... if you look up speed typers... typically they use mainly index and middle finger to achieve their typing speeds.... but yea i do like the idea of a glove with a key sewn into the end of each finger. dont know.
you can do 'chording'.... the thing stenographers do.... you might need to create your own keyboard hardware for this though.... qwerty keyboard does cap out at some point with the amount of keys being held down its capped at some point. eh i dont really think chording is super great though.... less ergonomic for wrists etc. when you have to hold down certain keys.... i prefer the way ive build my system,,,, which is one press just fires off and the whole layout instantly changes.
theres Talon voice-to-computer technology... you can build input chains for this software.... e.g. you can say to talon 12859345346 and it is trained well enough that it will recognize the correct number you just said.... this way of inputting has no muscle memory requirement because you're using voice.... but you still have to learn whatever input chains you code into it..... but yea no muscle memory learning for this voice-to-computer stuff. not as fast as typing tho, imo
you can ask me questions about this. i expect none of this really makes any sense. i think ultimately an input system with 1 press for each finger would be good. like a pair of gloves with one key on each finger. and make input chains built around that idea
i think with these input systems its ideal if you can test them as soon as possible..... there can be unforseen things that make an input system not pleasant to use...... so also why building them modular is good.... because hopefully if that happens you can re-use some parts of the code if you have to entirely rebuild the input system
i like randomizers.... for example, i have functions for 'choose random snare drum sample', 'choose random BPM.... id probably like to extend and customize these type of randomization options. for example, theres like 10 chord progressions i usually come back to.... so ill probably create randomizers for choosing one of these chord progressions, and then another randomizer for what rhythm to play that chord progression... etc.... i already have randomizer for changing musical key in the code. i think the randomizers will eventually get more and more complex... these input systems are nice because once you know how to code them,,,, you can code macros for anything. for instance maybe you like reverse piano sound... you could create input system just for reverse piano sound.... or something even more specific. one way to make an impact sample is to have a kick drum hit, with heavy reverb, and then some white noise sample with EQ automation..... you could parameterize all this into input chains or whatever.... so these input systems are never really done... good to build them as modular as you can maybe.
also i think its pretty unlikely that i keep the github file updated...... make your own input system if you want.... you really want to be able to code them yourself
also im probably going to rebuild every single function and how it interacts with ableton. ahk has functions like 'pixelgetcolor' which i can use to make the code less-likely to have bugs. by checking the state of ableton using pixelgetcolor. ultimately this system would be better on something like Reaper DAW,,,, reaper daw has Reascript.... but it looks kind of buggy and unused, i looked into this a little bit and people were having to make workarounds for certain things in reascript.... doesnt look that good. or maybe tweaking an open source daw would be a good idea. dunno. sounds like actually hard programming at that point... so im just sending mouse macros and shit to ableton atm. seems relatively bug free so far. you can send so much crap to ableton window and it usually processes it fine every time
yea i cant say id advise getting into building input systems. youll waste a shit tonne of time and have nothing to show for it. stick to the tools you already use to make art is my advice
yea idk that this type of system is worth learning. takes a long time to learn the muscle memory and you better have built it right or thats a lot of time gone
lol why is it 126 options and not 127 options. idk the way i was building the 126 options it just came out that 126 options was a good amount.... i was trying to pick ergonomic presses. so if it goes R L R, the 2nd Right hand press will be an ergonomic press based on whatever the first press was.... just came out as 126 options when i built it. need 127 options for MIDI velocity format
i learned the muscle memory for the 126 options first... takes about 20-40hours training game to learn 126 options into muscle memory. then i think i learned something basic like "input one 16th with velocity",,,, i think thats called '1pixel' input in the code file or something.... rectangle select is an example of a complicated chain.... because you need 2 x values and 2 y values. so its what is it 12 presses long
the code editor i use is called scite4autohotkey... it makes the code look nicer and colors things in... what is it called... IDE...>?
also might go with phase plant instead of serum... phase plant probably most state of the art synth atm....
also i need to build a bunch of shit for this... i want to make serum inputter.... so quickly sound design using all the functions and envelopes and modulating things in serum... also want to make inputter for EQing..... so i need a basic number inputter. probably going to build a basic number inputter using 2by2grid for each hand... 0-9 digits, +- symbol, decimal point, enter, double 00, triple 000.
if i was going to learn all the muscle memory again,,,,, i might want to try a relative coordinate system... the absolute coordinate system i went with here 4 bars, 58 pitches high.... it just takes a shit tonne of muscle memory to learn... a relative system, where you have a little token you move around on the screen, might take something like 4 times less muscle memory training game to learn..... dont know
i have a switcher for whether or not im using ergodox or not... idk how to explain all this code. i guess its just long macro chains stacked up next to each other... so yea
it might also only work on 1920 by 1080 screen resolution. dont know. like i mentioned earlier, it uses some grafix library calld gdip so i think you need 32 bit ahk install, not 64 bit install.
its also not finished and a couple of the functions are unfinished.
it doesnt have training game... training game was on an older version of the code. so youd have to create your own training games to learn the muscle memory.
really i like playing piano... i could play piano all day if my elbows werent so fucked up.... maybe i should focus on making piano music. dunno. not sure yet
yeah this probably doesnt make sense. i dont actually give a shit about making sense so go fuck yourself
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
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 383 days ago
oh i should mention... i dont understand how gdip graphics library works. the documentation for it isnt the friendliest to noobs like me. so the way i interact with gdip is a few custom functions i wrote.... .since i dont understand gdip these functions are probbaly 90% redundant code