From b7a790461b1fed3adad4c9fbb76a414bd11bf194 Mon Sep 17 00:00:00 2001 From: dreat Date: Thu, 12 Feb 2026 13:27:42 +0100 Subject: [PATCH] trying to migrate away from jeckyl --- index.html | 239 ++++ notes/Hidden Mineral World.md | 148 +++ ...Jaurim - Damn Ive Been Living Like This.md | 16 + notes/Korean grammar.md | 1107 +++++++++++++++++ notes/Korean phrases.md | 499 ++++++++ notes/Korean translations.md | 8 + notes/Korean.md | 9 + notes/Making a game with C++ and Raylib.md | 9 + notes/Music composition.md | 159 +++ notes/Signals.md | 24 + notes/Spectral Forge.md | 42 + notes/Stellar Chant.md | 51 + notes/categories.md | 12 + notes/codex vitae.md | 25 + notes/excuse hydra.md | 18 + notes/just do it.md | 14 + notes/learning.md | 11 + notes/make setup.md | 102 ++ notes/music.md | 11 + notes/random.md | 10 + notes/software engineering.md | 8 + notes/solid for fp.md | 16 + 22 files changed, 2538 insertions(+) create mode 100644 index.html create mode 100644 notes/Hidden Mineral World.md create mode 100644 notes/Jaurim - Damn Ive Been Living Like This.md create mode 100644 notes/Korean grammar.md create mode 100644 notes/Korean phrases.md create mode 100644 notes/Korean translations.md create mode 100644 notes/Korean.md create mode 100644 notes/Making a game with C++ and Raylib.md create mode 100644 notes/Music composition.md create mode 100644 notes/Signals.md create mode 100644 notes/Spectral Forge.md create mode 100644 notes/Stellar Chant.md create mode 100644 notes/categories.md create mode 100644 notes/codex vitae.md create mode 100644 notes/excuse hydra.md create mode 100644 notes/just do it.md create mode 100644 notes/learning.md create mode 100644 notes/make setup.md create mode 100644 notes/music.md create mode 100755 notes/random.md create mode 100644 notes/software engineering.md create mode 100644 notes/solid for fp.md diff --git a/index.html b/index.html new file mode 100644 index 0000000..fe38bb1 --- /dev/null +++ b/index.html @@ -0,0 +1,239 @@ + + + + + MDwiki + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+
+ + diff --git a/notes/Hidden Mineral World.md b/notes/Hidden Mineral World.md new file mode 100644 index 0000000..2771b40 --- /dev/null +++ b/notes/Hidden Mineral World.md @@ -0,0 +1,148 @@ +--- +title: Hidden Mineral World +tags: music +--- + +_written in the middle of making this_ + +Spotify Link + +### Intro + +Hidden Mineral World EP (or HMW for short) started out as a challenge from my friend. He generated this: + +using StableDiffusion and I jokingly said I will do a dark techno/glitch EP for that. + +==and the game was on== + +### First try + +I started dabbling in Ableton Live but with no real progress. After some short loops I kinda forgot about this. + +### Second try + +As I saw the cover again, I decided to give it another go. This time I used ChatGPT4 to write the song structure, bpm and track titles. It came up with +1. Subterranean Frequency +2. Crystal Resonance +3. Geode Rift +4. Iron Vein + +I also got BPMs and tracks structures, but, having more draw into Ambient stuff it, again, got forgotten + +### Third try + +Third time's the charm, right? + +I may have neglected this, but this EP kept coming back to my mind, so I decided to give it a final try, this time with extra challenge - I will work on it for 15min daily. No more, no less. I open up Ableton Live, start the timer and save&quit when timer gets off. + +And, surprisingly, this works. Works so well, that I have force myself to stop. + +As of the time of writing this I have a premix versions of tracks 1 & 2 and track 3 is in progress. + +#### Subterranean Frequency + +This is what I got from ChatGPT4 + +``` +BPM: 125 + +- 0:00-1:15: Opening with a pulsating sub-bass drone, the sound of distant drilling emerges to introduce the thematic elements of the track. +- 1:15-2:30: The sub-bass transforms into a steady, dark techno beat as the percussion intensifies. Metallic glitches layer over the rhythm. +- 2:30-4:00: A breakdown in the middle introduces distorted synth elements, building tension. +- 4:00-5:00: The track closes by revisiting the initial rhythm, while the drilling and glitches fade, leaving only the deep echoes of the bass. +``` + +I started with marking the timestamps (which I had to move a bit to align with bars) and named locators after the defined structure. This helped me a lot, as I exactly saw how long each section is, what it is and what comes after another. I also added "end" locator to have a clear indication where the track ends. + +It was a nice challenge, I used some CC0 industrial samples (drills, pickaxes, stones etc), learned a lot about wavetable. Used some more samples for glitchy beats above kicks, needed to use parallel compression to make it work properly. + +This was the first one, I think the quickest one. +Going on for 15 minutes and with set structure was a bit of a challenge, but did help greatly move forward. If you have only 15 min to do work, you make every second count. + + +#### Crystal Resonance + +This is what I got from ChatGPT4 + +``` +BPM: 132 + +- 0:00-1:00: Introduction with ethereal pads, a soft, minimalistic drum beat enters to set the tempo. +- 1:00-2:15: Glitchy beats are layered over the pads, the tempo increases. Synths mimic the sound of crystals resonating. +- 2:15-3:30: The final section features a crescendo of resonant sounds, ending with a series of glitchy echoes that fade out to silence. +``` + +Again, I started with location markers, and, again, I had to adjust them to align with the beat. Here I added extra one for "echoes" before "end" - to show the time of the echoes to decay. + +Another dive into wavetable. A lot of youtube diving into understanding this tool more definitely helped. + +I tried to make "glass needles" sound for `crystal resonance` here and I actually decided to use a MIDI drum clips from Ableton's packs. I did eventually change them a bit, partially to maintain `techno` feel. +Here I had a huge clash of frequencies and had to use a lot of parallel compression to make it sound good. It's actually even better than I've wanted and had an extreme case study of clashing instruments. + + +#### Geode Rift + +This is what I got from ChatGPT4 +``` +BPM: 128 + +- 0:00-1:00: A heavy bassline starts the track, suggesting the outer shell of the geode. +- 1:00-2:15: The track 'cracks open' with sparkling arpeggios and expansive synths, replicating the awe of discovering the geode's interior. +- 2:15-3:45: Techno beats enter, increasing in intensity to represent the geode's harsh formation environment. +- 3:45-4:30: The music reduces to a soft, twinkling outro, mirroring the closing of the geode and leaving the listener with a sense of intrigue. +``` + +This one is still in progress, so this entry may actually start being interesting. + +As usual, I started with location markers. + +Then I used operator -> noise with some processing (EQ, filters, erosions etc) to create cracking noise to simulate "cracking open". LFO helped give it some rhythm. + +Quick heavy bassline in wavetable, quick synth arpeggios and some beats. + +Challenge here was that it was the most melodic track yet. I started with some scale to help me - continued to use that for other stuff, but I knew it was not working. + +Actually after initial bass I went into designing fading outro, with automated autofilter and freeze from reverb. + +I actually broke from the scale suggestions and went with what sounds cool to me (and arpeggiated). Grouping wavetable with second, more plucky one, did help to get more pleasing sound as well. + +I changed previous midi clips to new melody and added new synth for a bass line for the "cracking open" part, that will stay with the song till the end. +Initial bass is automated to get to `-inf dB` slowly over the course of the second part. + +I though that I need some pads, so I whipped out wavetable to create something lush. I duplicated the track, froze two chords (first one from pattern and very last one), reversed audio clips and used them as smooth transition. It works especially well if you have reverse audio going into the synth when there's a transition between parts. It makes it all glue together, and sounds really well. + +After rendering and listening to it, I may go back to it and add something in first part, as, right now, it's a bit boring. + +#### Iron Vein + +This is what I got from ChatGPT4 +``` +BPM: 130 + +- 0:00-0:45: A steady, driving beat starts, metallic synths layer over to build tension. +- 0:45-2:00: The intensity increases, bringing the raw energy of iron extraction to life. +- 2:00-3:30: The track breaks down into a quieter passage, with softer sounds representing the depleting vein. +- 3:30-4:15: A somber, atmospheric outro, symbolizing the aftermath of extraction. +``` + +I spent first session, trying to make synths that are `metallic enough`. I decided to switch things a bit, and went with Ashlight from NI for some dark pad paired with quiet `metallic` operator with some echo. +Turns out that first part is divisible by 6, not 4 (given the length of patterns I created), so this makes things a bit more interesting. +Afterwards I added a standard 808 kick that slowly appears. Synth has parallel compression to make that kick stand out, but this time I did 50% wet (instead of 100%), and, I must say, it sounds great. + +I managed to create simple hihat pattern and got `time outed` when trying to find next percussive sounds. + +While playing around with `bongo` sound I managed to create great accents using sparse two hits at a same time (with some reverb on some of the hits) and found great rhythmic pattern with second preset. I actually made it quicker to test some effects and realised that it sounds great as a background sound, so I kept it there. + +I stole the idea of "arpeggiating" 5 notes to create rhythmic variety - put a long 5 note MIDI with arpeggio on operator bell sounds. To enforce the melody, in third section of a song I used the same notes, just slower, going up with first note as a pedal note. I just found a nice Vital preset that fit the mood. Moving it around a bit made "progression" that was supported with sustained bass. + +As LLM suggested track slowly fading away I started getting more sparse with bongos (to the point it was removed), slowly removing layers. Track ends with reverb tail from bass and Vital. + +#### Final touches + +I went around the tracks and did some small fixes here and there. Also I mixed it quickly (limiter on master maybe is not advanced technique but did the job) and added a little, barely audible, heavy processed sample in Geode Rift. Afterwards I uploaded it to streaming services. And now only thing left is to wait for it to be processed. + +### Random thoughts + +- As said many times, both image and text generative AIs give "raw material" rather than finished product. Cover was worked on in PhotoShop after it was generated. I did interpret the song structure in my own way. +- OTOH, not having a blank page to start with is a great help. While here it's way more constraining that I would use for something else, LLMs can be great for ideation and getting some concrete starting points. +- I still deviated from some of the suggestions after banging my head against the wall, but, many of those were helpful, or made me try out and learn new things diff --git a/notes/Jaurim - Damn Ive Been Living Like This.md b/notes/Jaurim - Damn Ive Been Living Like This.md new file mode 100644 index 0000000..ed65442 --- /dev/null +++ b/notes/Jaurim - Damn Ive Been Living Like This.md @@ -0,0 +1,16 @@ +--- +title: Jaurim - Damn! I've Been Living Like This +--- + +Status: 🌱 + + +| section | Korean | English | +| -------- | -------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| title | 자우림 "**그래 제길** 나 이렇게 살았어" | Jaurim - "**(ok? eh?) damn!** I lived/been living like this" | +| verse 1 | 그래 제길 나 이렇게 살았어
*보다시피* **볼 것** 없이 살았어
해놓은 것 없이, 가진 것 하나 없이
그럭저럭 되는대로, 그런 하루, 하루 | eh, damn, I've been living like this
*as you see* I lived without **seeing**
without doing anything, without having one thing / anything
somehow anyhow(?), like that, day by day(?) | +| chorus 1 | 나도 간절하게 바랬던 게 있어
나도 맘을 다해 했던 일이 있어
내 뜻대로 되준 일은 없어
결국 아무것도 나에게는 쉽지 않아 | I too desperately faded there
I too used up my feelings on things that happen
My own way does not exist(?)
In the end nothing is easy for me
| +| verse 2 | 그래 제길 나 이렇게 살았어
보다시피 볼 것 없이 살았어
믿는 사람 없이, 진짜 사랑 한 번 없이
그럭저럭 되는대로, 그런 하루, 하루 | | +| bridge | 그래 제길 나 이렇게 살았어
보다시피 볼 것 없이 살았어 | | +| chorus 2 | 간절하게 바랬던 게 있어
맘을 다해 했던 일이 있어
내 뜻대로 되준 일은 없어
결국 아무것도 나에게는 쉽지 않아
간절하게 바랬던 게 있어
맘을 다해 했던 일이 있어 | | + diff --git a/notes/Korean grammar.md b/notes/Korean grammar.md new file mode 100644 index 0000000..df6d596 --- /dev/null +++ b/notes/Korean grammar.md @@ -0,0 +1,1107 @@ +--- +title: Korean grammar +--- + +Status: 🌿 +
+Table of contents + +
+ +### Formal vs Casual {#formal} + +There are two ways of communicating in Korean + +존댓말 - formal one. More polite, good `default` mode. +반말 - informal one - to be used with friends + +Usually the difference is adding -요 to the end. Also, if there are many ways of saying/writing something, the longer one is more polite one. + +| 존댓말 | 반말 | +| ------------------------ | ----------------- | +| 안녕하세요 | 안녕 | +| 안녕히 가세요/잘 가요 | 안녕 / 잘 가! | +| 안녕히 계세요 / 잘 지내요! / 잘 있어요 | 안녕 / 잘 지내 / 잘 있어! | +| 저 | 나 | +| -씨, -님 | 너, -야/-아 | +| 네 / 예 | 응 / 어 >> 웅 / 엉 | +| 아니요 / 아니에요 | 아니 / 아니야 | +| 이거 뭐예요? | 이거 뭐야? | +| 이거 뭐였어요? | 이거 뭐였어? | +| 내일 일 할 거예요 | 내일 일 할 거야 | + +Politeness levels are determined by the verb ending. There are three basic verb endings used to express different politeness levels +1. -ㅂ니다 = the most polite and most formal ending +2. -(아/어/여)요 = the polite, natural and slightly formal ending +3. 아/어/여 = the casual, informal and intimate ending + +반말 can be only used: +1. with someone who is younger +2. someone of the same age +3. someone with whom you agreed to mutually use 반말 +If other person's age or social status is not known, do not use 반말. Once you know other's person's age and find out they are younger than you, you can use 반말, however it's safer, as well as a nice gesture, to ask the person whether you can use 반말. + +Common cases for using 반말 +1. You are much older +2. You are older than the other person and you got their permission to use 반말 +3. You are the same age and you got their permission to use 반말 +4. Students in same age group +5. Talking to yourself or writing in a diary/journal + +Common cases to **NOT** use 반말 +1. You know the other person only through work and not personally +2. You are older than the other person, but they are your business client or customer +3. You are older than the other person, but you are talking in an official environment (like business meeting, seminars, lessons) +4. You just met the other person. +5. You are younger and never got permission from the other person to use 반말 with them +6. You are the same age, but you are both adults and you do not know each other that well +7. You are older, but the other person is your boss +8. You are older than the other person, but they are the spouse of your sibling +9. You are talking to a large group of people or filming a video blog + +How to ask for 반말? + +If you are the older one +``` +말 놔도 돼요? = May I speak 반말 with you? +말 = language, word +놓다 = put down +말을 놓다 literally means "put down the language" or "lower the language" + +말 편하게 해도 돼요? = May I speak comfortably with you? +편하다 comfortable +편하게 comfortably +``` + +If you are the younger one +``` +말 놓으셔도 돼요 = You can speak casually with me +놓다 >> 놓으시다 + +말 편하게 하셔도 돼요 = You can speak comfortably with me +하다 >> 하시다 +``` + +If you are of the same age +``` +우리 말 놓을까요? = Shall we speak 반말 to each other? +말 편하게 해도 되죠? (-지요=--죠) = I can talk in 반말 with you, right? +``` + + +### What {#what} + +###### What + verb -> 뭐 + verb +example: 뭐 했어요? -> What did you do? + +###### What + noun = what kind of -> 무슨 + noun +example: 무슨 책 좋아해요? - what kind of books do you like? + +### Time {#time} + +AM = 오전 +PM = 오후 +hour = 시 +minutes = 분 + +time format: 오전/오후 + NK number + 시 + SK number + 분 + +year = 년 +month = 월 +day = 일 + +date format: SK + 년 + SK + 월 + SK + 일 + +### Counting {#counting} + +what + NK number + counting word + +example: 책 다섯 권 = five books + +|word|what it counts|comments| +|---|---|---| +|살|age (years old)|can't use 개| +|명|people|can't use 개| +|마리|animal|can't use 개| +|병|bottle|| +|벌|clothes|| +|개|"thing"|can be used for other words unless specified otherwise| +|그루|tree|| +|켤레|a pair|| +|장|paper, page, ticket|also works for e-tickets| +|권|book|| +|대|car, phone, tv|from what I understand "expensive" things| +|조각|piece|| +|송이|flower|| +|컵|cup|for cheap/take-away coffee etc| +|잔|glass|for expensive/proper coffee cup etc| + +### Subject markers {#subject} + +**-은/-는** + +"unlike other things" + +"different from other things" + +**example** + +이거는 사과예요. + +(The other things are not apples, but) this is an apple. + +-이/-가 + +**example** + +이 책이 좋아요. + +This book is good + +(there are no other books as good as this one) + +1. Once mentioned, a subject is given `은/는`. The subject is turned into a topic. + - 그 강아지는 예뻐요 = The dog is pretty + - 공원에 강아지가 있어요 = There is a dog at the park +2. `은/는` can be also used for things that are not subjects. Use `은/는` when it means _this topic is a little_ **different** _from other topics_ + - 여기에 한국인이 많아요. 근데 저는 미국인이에요. = There are a lot of Koreans here. But I am American + - 저는 강아지를 좋아하는데 고양이는 안 좋아해요 = I like dogs, but I don't like cats +3. If **the subject** is important, use `이/가`. If anything other than the subject is more imporant, use the `은/는`. + - 누가 드랫이에요? 제가 드랫이에요. (Who is Dreat? I am Dreat => **I(저)** is more important than the name) + - 이름이 뭐예요? 제 이름은 드랫이에요 (저**는** **드랫**이에요 / 드랫이 제 이름이에요) = What is your name? My name is Dreat (I am Dreat) (name is more important than `I(저)`) + +### Object markers {#object} + +-을/-를 + +### Present tense {#present} + +1. Ends with ㅏ or ㅗ = add 아요 +2. Doesn't end with ㅏ or ㅗ = add 어요 +3. Ends with 하 = add 여요 + +### Past tense {#past} + +1. Ends with ㅏ or ㅗ = add 았어요 +2. Doesn't end with ㅏ or ㅗ = add 었어요 +3. Ends with 하 = add 였어요 + +### Future tense {#future} + +Add -(으)ㄹ 거예요. + +or + +Add -(으)ㄹ 게요 to focus more on actions or decisions as a reaction/result of what the other person says or thinks + + +### Present progressive (-ing) {#ing} + +Add -고 있어요 + +### Want {#want} + +Add -고 싶어요 + +#### Do you want to...? -(으)ㄹ래요? +It is built based on the future tense. It is used when expressing the intent of the will to do something. With question mark it changes to "do you want to...?". When used as a statement it can mean "I want to..." or "I am going to...". + +1. 집에 가고 싶어요 = I want to go home (most general and vague way) +2. 집에 갈게요 = (if so) I will go home (looking for feedback / reacting to the situation) +3. 집에 갈 거예요 = I am going to go home (most direct) +4. 집에 갈래요 = something between "I want to go home" and "I am going to go home" + +혼자 할래요 vs 혼자 할게요 -> second sounds much nicer, but both mean "I will do it alone" + +저는 안 가래요 (I do not want to go/I am not going to go) vs 저는 안 가고 싶어요 (If you really insist, I might go) + +### Negation {#negation} + +1. 안 before verb +2. negative verb ending -지 않다 + +### Verb into noun {#verbintonoun} + +1. Drop 다 +2. Add 기 + +**example** + +보다 - to see + +부기 - seeing + +or add `-(으)ㄴ/는/(으)ㄹ 것 ` + +**for action verbs** +1. present tense: verb stem + -는 것 +2. past tense: verb stem + -(으)ㄴ 것 +3. future tense: verb stem + -(으)ㄹ 것 + +**for descriptive verbs** +1. present tense: verb stem + -(으)ㄴ 것 +2. future tense: verb stem + -(으)ㄹ 것 +### Can/cannot do {#cancannot} + +1. Drop 다 +2. Add (으)ㄹ 수 있다/없다 + +### It can't be -(으)ㄹ 리가 없어요 {#itcantbe} + +`리` means "reason" or "logic" and can be found in `이유(reason)` and `논리(logic)` + +given that, the structure -(으)ㄹ 리가 없어요 literally means "there is no reason that..." -> it's used as "it cannot be..." or "it is impossible...". + +`그렇다` is a very common expression thatmeans "to be so". (ㅎ is usually dropped with verb endings) + +그러 + ㄹ리가 없어요 = 그럴 리가 없어요! = It cannot be/That is impossible! + +을 리가 없어요 can be places after tense suffix -았/었/였. In that case, it always starts with -을. (ex: 갔을 리가 없어요 -> There is no way that he/she went) + +For future tense use present verb form + add words that indicate future (ex: 내일 -> 내일 일요일일 리가 없어요 -> there is no way that tomorrow is Sunday) + +### Descriptive verbs {#descriptiveverbs} + +verb stem + 아/어/여 + 하다 + +**example** +슬퍼요 - I am sad + +슬퍼해요 - "to feel sad"/"express such emotions" + +(for feelings only descriptive form can be used for other people) + +### Place {#place} + +-에 = at, to, in + +**example** + +학교에 갔어요 - I went to school + +-에서 = at, in, from + +used to + +1. Describe where action is taking place (도서관에서 궁부했어요 = I studied in the library) +2. Describe "from place" (서울에서 왔어요 = I came from Seoul) + +### From/to {#fromto} + +##### From +1. -에서 -> for location +2. -부터 -> for time + +##### To + +까지 (for both location and time) + +##### From/to someone + +1. -한테 = to/from someone +2. -한테서 = from someone + +### And/But/Therefore/So {#andbut} + +##### And + +1. 그리고 = and, and then. +2. -하고 = and (used for nouns) +3. -(이)랑 = and (for nouns), also "with" + +2 and 3 can be combined with "같이", which means "together" + +##### But + +1. 그렇지만 - gives "disappointment" vibes +2. 그런데 - can be used as "and" +3. 근데 - shorter form, used in speaking + +##### Therefore/so + +그래서 + +### Also/too {#also} + +-도 + +저도 좋아해요 - I like it too + +*도 can emphasise different things in a sentence* + +-기도 하다 + +먹기도 해요 - I also eat + +### Only {#only} + +-만 + +아침에는 커피만 마셔요 (I only drink coffee in the morning) + +아침에만 커피 마셔요 (I drink coffee only in the morning) + +Only + verb +1. verb in noun form +2. add -만 하다 + +- 밖에 = literally outside something, _other than something_, out of range of something + +`Noun + -밖에 + negative conjugations` + +아침에는 커피밖에 안 마셔요 (I drink nothing but coffee in the morning) + +in general -만 and -밖에 are interchangeable, but +1. You need negative form with -밖에 +2. -밖에 is used more +3. -밖에 cannot be used with imperative sentences +4. When verb has a negative meaning, -만 is more commonly used (저는 닭고기만 싫어해요 = I only hate chicken) + +### Irregulars {#irregulars} + +| ends with | change | +| -------------------------------------- | ---------------- | +| ㅅ | remove ㅅ | +| ㄷ | ㄷ => ㄹ | +| last vowel ㅗ + ㅂ | remove ㅂ, add 오아 | +| last vowel not ㅗ + ㅂ | remove ㅂ, add 우어 | +| vowel in 2nd last syllable ㅏ/ㅗ + ㅡ | ㅡ => ㅏ | +| vowel in 2nd last syllable not ㅏ/ㅗ + ㅡ | ㅡ => ㅓ | +| last vowel ㅏ/ㅗ + 르 | 르 => ㄹ + 라 | +| last vowel not ㅏ/ㅗ + 르 | 르 => ㄹ + 러 | + +but! +- 입다 -> 입어요 -> 임을 거예요 (to wear) +- 잡다 -> 잡아요 -> 잡을 거예요 (to catch) +- 씹다 -> 씹어요 -> 씹을 거예요 (to chew) +- 좁다 -> 좁아요 -> 좁을 거예요 (to be narrow) +- 넓다 -> 넓어요 -> 넓을 거예요 (to be wide) + +### More than {#morethan} + +A보다 더 = more than A + +수박은 사과보다 더 커요 = A watermelon is bigger than an apple + +### If/in case {#if} + +- 만약 - (optional) in case/if +- -(으)면 = verb ending for "if" + - ends with no 받침 or ㄹ -> add -면 + - ends with 받침 other than ㄹ -> add -으면 + +_examples_: +1. 만약 지금 자면, 일찍 일어 날 수 있어요 - If I sleep now, I can wake up early +2. 지금 자면, 일찍 일어 날 수 있어요 - I can wake up early, if I sleep now + + +### Still/already {#stillalready} + +- 아직 - still, not yet +- 아직도 - still + even/also -> "still (not) happening". Sound critical/being a little mad or angry +- 이미 - already, when you know about something +- 벌써 - when you are just finding out about somthing + +### Someone/Something/Somewhere/Someday {#somex} + +1. 누구 (who) + -ㄴ가 = 누군가 (someone) +2. 뭐 (what) + -ㄴ가 = 뭔가/무언가 (something) +3. 어디 (where) + -ㄴ가 = 어딘가 (somewhere) +4. 언제 (when) + -ㄴ가 = 언젠가 (someday) + +Even when intended meaning is "someday", 언제 can be used instead of 언젠가. Same goes for 뭐/어디/누구. + +*examples:* +1. 누구 만날 거예요? - whom will you meet? +2. 누군가 만날 거예요? - will you meet somebody? +3. 뭐 찾았어요? - what did you find? +4. 뭔가 찾았어요? - did you find something? + + +### Imperative {#imperative} + +Fixed expressions using '-세요' +- 어서오세요 - Welcome +- 안녕히 가세요 - goodbye +- 안녕히 계세요 - goodbye +- 안녕히 주무세요 - goodnight + +1. If you want to tell somebody to do something + - Verb ending with vowel or ㄹ - add -세요 + - Verb ending with consonant other than ㄹ - add -으세요 +2. Please do it for me. + - It has much *nicer tone* + - Has nuance of asking someone for a favour or asking someone to do sth "for you" + - 아/어/여 주세요 + +*examples*: +1. 아이스크림 사세요 - please buy yourself some icecream +2. 아이스크림 사 주세요 - please buy **me** some ice cream + +줘요 is less formal 주세요, but more polite than just -세요. + +### Have to/Should/Must {#haveshouldmust} + +-아야/어야/여야 + 되다/하다 + +### Method/way {#methodway} + +-(으)로 + +1. Made with x - 뭐로 이거 만들었어요? - what did you make this with? +2. Come by x - 오늘 택시로 왔어요? - did you come by taxi today? +3. Do x using y - 카드로 낼 거예요 - I will pay by card +4. Get hurt/sick - 사구로 다치다 - to get hurt in an accident +5. To be famous for x - 프랑스는 치즈로 유명해요 - France is famous for its cheese +6. Path - 이 길로 가다 - to go this path + +### All/more/less {#allmore} + +- 다 - all +- 더 - more +- 덜 - less, not completely (opposite of 다) + +1. 다 먹었어요 (we ate all/we finished eating) +2. 덜 먹었어요 (we ate not completely everything/we didn't finish eating)[^14] + +### Don't do it {#dontdoit} + +add -지 마세요 + + +### Verbs that require nouns {#vnounsreq} + +Some verbs require nouns to make sense. "To sing"/"To dance"/"To draw" makes no sense if it's not specified **what** + +examples with most *generic* nouns: + +1. To eat - (밥을) 먹다 + - 밥(을) 먹어요 - I eat + - 뭔가 먹어요 - I eat something +2. To draw - (그림을) 그리다 + - 그림 그려료 - I draw + - 강아지 그려요 - I draw a dog +3. To dance - (춤을) 추다 + - 춤을 춰요 - I dance + - 힙합을 춰요 - I dance hip-hop +4. To sing - (노래를) 부르다/하다 + - 노래 불러요 - I sing + - 케이팝 불러요 - I sing K-pop + +### Too much/very {#toomuchvery} + +너무 - too much, excessively; Can be also used as very/quite/really. + +In past it was used only in negative sentences, but nowadays it's possible to use in positive contexts as well. Most people use it both ways. + +example: +너무 더워요: +1. It is too hot +2. It is very hot + +### Linking verbs {#linkingverbs} + +#### -고 +-고 can be used to link verbs. Only last one needs to specify tense, others - just replace `다` with `고` +It's used to connect **independent** clauses or actions together to form once sentence. + +example: 공원에 가고 책을 읽었어요 -> I went to the park and I read a book. (listing things done in a day) + +#### -아/어/여 서 +-아/어/여 서 is translated as "therefore/so" and is used to connect two or more verbs in a sentence to show logical relationship between the verbs. + +1. Reason + 아/어/여 서 + result (비가 와서 못 갔어요 -> It rained, so I cannot go) +2. An action + 아/어/여 서 + another action that takes place after first action (공원에 가서 책을 읽었어요 -> I went to the park and read a book. Reading a book was after park) +3. An action + 아/어/여 서 + the purpose of or the plan after the action (케이크를 사서 친구한테 줄 거예요. -> I'm going to buy a cake and give it to a friend) +4. fixed expressions + 1. according to -> -에 따라(서) (뉴스에 따라서 오늘 비가 올 거예요 -> According to the news, it will rain today.) + 2. for example -> 예를 들어서 (예를 들어서 이렇게 할 수 있어요 -> For example, you can do like this) + +#### -아/어/여도 +same meaning as "그래도" (but still, nevertheless) + +#### -는/은/ㄴ데 +1. -는데 is used after action verbs (ㄹ is dropped), after 있다/없다, and after -았 or -겠 +2. -은데 is used after descriptive verbs with have a final consonant in the verb stem, exepct for the consonant ㄹ +3. -ㄴ데 is used after descriptive verbs with end in a vowel or ㄹ (ㄹ is dropped) and after 이다 and 아니다 + +This ending has a diverse meaning +1. Explaining the background or the situation before making a suggestions/request/question -> 내일 일요일인데, 뭐 할 거예요? (It is Sunday tomorrow, what are you going to do?) +2. Explaining the situation first before explaining what has happened -> 어제 자고 있었는데, 한국에서 전화가 왔어요 (I was sleeping + 는데 + I got phone call from Korea) +3. Showing a result or situation which is contrasting to the previous action or situation -> 아직 9시인데 벌써 졸려요 (it is still 9 o'clock, but I am already sleepy) +4. As 3, but second part can be omitted for implied meaning (bit sassy) -> 준비 많이 했는데(요)... +5. Showing surprise or exclamation -> 멋있는데(요)! (Oh, that is cool!) +6. Asking a question (expecting some explanation about a situation or behaviour) -> 지금 어디에 있는데(요)? (So where are you now?) +7. Expecting an answer or a response -> 지금(요)? 지금 바쁜데(요)... (Now? I am busy now, so...) + +### Shall we?/I wonder... {#shallweiwonder} + +-(으)ㄹ 까요? + +It is used to: +1. Asking oneself a question of showing doubt about something +2. Raising a question and attracting attention of others +3. Suggesting doing something together + +### Approximately, About {#approxabout} + +1. -쯤 (no space) +2. 정도 (after word, with space) +3. 약 (before word, with space) + +`약` can be used as `ummm` to buy time when answering a question. 1+3 and 2+3 are valid options. + +### Before noun {#beforenoun} +(noun +) 전에 = before (+ noun) +- before class = 수업 전에 +- before Sunday = 일요일 전에 +- before 1o'clock = 1시 전에 +- an hour ago = 한 시간 전에 + +with verb = change a verb into a noun (-기) +- 가기 전에 = before going +- 사기 전에 = before buying +- 먹기 전에 = before eating + +**examples** +- Finish your work before you go home = 집에 가기 전에 일 끝내세요 +- Eat before you study = 공부 하기 전에 밥 먹으세요 +- Don't use it before you pay. = 돈을 내기 전에 쓰지 마세요. + +### Before verb {#beforeing} +change verb into noun (-기 form) + 전에 +가다 -> 가기 -> 가기 전에 (before going) +사다 -> 사기 -> 사기 전에 (before buying) +먹다 -> 먹기 -> 먹기 전에 (before eating) + +집에 가기 전에 (before going home) +집에 가기 전에 일 끝내세요 - finish your work before going home + +공부 하기 전에 먹으세요 - eat before you study + +### After {#after} + +다음에, 후에, 뒤에 + +after -ing +- -(으)ㄴ + 다음에 +- -(으)ㄴ + 후에 +- -(으)ㄴ + 뒤에 + +to go home = 집에 가다 + +after going home: +1. 집에 간 다음에 +2. 집에 간 후에 +3. 집에 간 뒤에 + +### Plural marker {#pluralmarker} + +noun + 들 + +커피들이 있어요 (more than 1) + +커피가 있어요 (1 or more than 1) + +_do not use with counting verbs_ +incorrect: '커피 4잔'들 (sounds like 1 or more sets of 4 coffee cups) + +### But still, nevertheless {#butstillnevertheless} + +#### 그래도 +it means "but still"/"however"/"nonetheless"/"nevertheless" + +example: It is raining! Are you still going? = 비가 와요! 그래도 갈 거예요? + +그래 + 도 = "even if you do that"/"even if that happens"/"if you do that, too" + the meaning of "still" + +### To look like/to seem like {#looklikeseemlike} + +**비슷하다** = to be similar +A is similar to B +A은/는 B(이)랑/B하고 (use with) 비슷하다 +Lemon is similar to kiwi +키위랑 레몬은 비슷해요 / 레몬은 키위랑 비슷해요. + +**같다** = to be the same +A is the same as B +A은/는 B(이)랑/B하고 (use with) 같다 + +A**랑** 같아요 - it is the same as A +B는 A**랑** 같아요 - B is the same as A +A**하고** B는 같아요 - A and B are the same + +##### with verbs +-(으)ㄴ/는/(으)ㄹ 것 같다 + +- present tense: verb stem + 는 것 + - present tense for action verbs +- past tense: verb stem + -(으)ㄴ 것 + - present tense for descriptive verbs + - past tense for action verbs +- future tense: verb stem + -(으)ㄹ 것 + - future tense for action and descriptive + + +### Making Adjectives {#adjectives} + `+ -(으)ㄴ + 명사 (noun)` + +In English "pretty" is an adjective and can be found in a dictionary. +In Korean "pretty" is "예쁜", but it cannot be found dictionaries. The "descriptive verb" or "the adjective in infinite form" is "예쁘다" and can be found in the dictionary. + +- 싸다 is not "cheap". It means "to be cheap" +- 바쁘다 is not "busy". It mean "to be busy" +- 맛있다 is not "delicious". It mean "to be delicious" + +In Korean adjectives can be conjugated to different tenses, for example + +- 재미있다 (to be fun) +- 재미있어요 (present tense) +- 재미있었어요 (past tense) +- 재미있을 거예요 (future tense) +(vs English It is fun/ It was fun/ It will be fun; `fun` is always the same) + +**Exceptions:** +- 하얗다 -> 하얀 (white; 하얀 가방 - white bag) +- 그렇다 -> 그런 (such; 그런 가방 - that kind of bag) +- 달다 -> 단 (sweet) +- 있다 -> 있는 +- 없다 -> 없는 + +**Common mistake** +- 예쁜 + 이에요 𐄂 -> 예뻐요 ✓ +- 비싼 + 이에요 𐄂 -> 비싸요 ✓ +- 라떼 한 잔 주세요. 따뜻한 - 𐄂 (can't be without noun) +- 라떼 한 잔 주세요. 따뜻한 라떼. ✓ + +**Action verbs can be also used as adjectives** + +action verb -는 + noun (for verbs ending with ㄹ, drop ㄹ) + +- This is **a bag I like** +- 이 가방은 제가 **좋아하는 가방**이에요. +- This bag is **a bag I liked** +- 이 가방은 제가 **좋아한 가방**이에요. +- This bag is **a bag I will like** +- 이 가방은 제가 **좋아할 가방**이에요. + +- Someone who Yeji likes -> 예지씨가 좋아하는 사람 +- Someone who likes Yeji -> 예지씨를 좋아하는 사람 + +- Is there a Korean food that you eat often? -> 자주 먹는 한국 음식 있어요? +- Is there a cafe that you go to often? -> 자주 가는 카페 있어요? + + +### Well then, In that case, If so {#wellthenifso} + +그러면, 그럼 + +``` +if, in case = 만약 -(으)면, or -(으)면 +to be so = 그렇다 +``` + + +그러면 is `그렇다 + (으)면` and literaly means ("then" or "in that case") + +if you say **그럼!/그럼요** it mean "of course!" or "naturally!" + +### Let's {#lets} + +A few different ways to say `let's` in Korean + +1. - 아/어/여요 (polite/plain) +2. -(으)시죠 (honorific) +3. -자 (informal) +4. -(으)ㄹ래요? (polite/casual) +5. -(으)실래요? (polite/formal) + + +### In order to, For the sake of {#inorderto} + +위해, 위해서 = in order, for + +위하다 => 위해 (위하여) / 위해서 (위하여서) + +noun + -을/를 위해서 +- 건강을 위해(서) = for health/for the sake of health/in order to be healthy +- 회사를 위해(서) = for the company/for the good of the company + +"위해(서)" in a sentence sounds very formal. In casual, spoken conversation -(으)려고 or 위한 is used + +### Maybe I might {#maybeimight} + +-(으)ㄹ 수도 있어요 = +- it could... +- it is possible that... +- it might + +1. -(으)ㄹ 수 있다 -> can, to be able to +2. -도 -> also, too + +The word 수 is a noun which means "way", "method" or "idea". Therefore -(으)ㄹ 수 있다 means "there is a way to do...", "there is an idea for doing..." or "there is a possibility for doing..." + +Adding -도 (too/also) changes the meaning to "to also be able to do something". + +It usually means "it might", "it could" or "perhaps". + +- to meet = 만나다 +- might meet = 만날 수도 있다 +- we might meet again tomorrow = 내일 다시 만날 수도 있어요 + +**important**: +1. I might not come here tomorrow => 저는 내일 다시 안 올 수도 있어요 +2. I might not be able to come here tomorrow + - 저는 내일 다시 올 수 없을 수도 있어요 + - 저는 내일 다시 몾 올 수도 있어요 + + +### -네요 verb ending {#neyo} +It is used in case of being impressed, surprised, or one's own personal thought. This is used quite frequently + +Verb stem + -네요 + +- 크네요! = (I see that) it is big! / (I did not know it was but, but) is it big. (expressing surprise) +- 잘 어울리네요! = Oh, I think that it looks good on you (expressing impression) +- 맞네요 = I see that it is correct! (Finding out a fact for the first time) +- 여기 있네요! = oh, here it is! +- 벌써 11원이네요 = wow, it is already November + +### The more ..., the more... {#themorethemore} + +-(으)면 -(으)ㄹ수록 + +the more A(verb), the more B(verb) = A-(으)ㄹ수록 B + +examples: +- The more delicious it is, the better is sells = 맛있을수록 잘 팔려요 +- The more busy you are, the more important your health is = 바쁠수록 건강 더 중요해요 +- The more people, the better = 사람이 많을수록 더 좋아요 + +-(으)ㄹ수록 can also mean (depending on context of conversation) +- "Even more so, especially when..." - 학생일수록 책을 많이 읽어야 돼요 = You need to read a lot of books, even more so if you are a student +- "Especially if..." or "Even more..." +- "Particularly when..." - 바쁠수록 더 자야 돼요 = You need to sleep more, particularly when you are busy + +If you want to emphasise a bit more, you can use -(으)면 before -(으)ㄹ수록 + +- The busier you are... = 바쁠수록 = 바쁘면 바쁠수록 +- The better is it... = 좋을수록 = 좋으면 좋을수록 + +**갈수록** comes from 가다 + -(으)ㄹ수록. It literally means "the more you go", but it's used as "more and more so in time" or "as time goes by" +- It keeps getting colder = 갈수록 추워요 +- Dreat keeps getting better at Korean - 드랫은 갈수록 한국어를 잘해요 + + +### -지(요) {#ji} + +it's a verb ending that subtly changes meaning. Use it when + +1. talking about something, supposing that** the other person also already knows** about it +2. both you and the other person know about something or have a common opinion about something, and you are **just mentioning the fact again** +3. (as interrogative/question ending) both you and the other person know about something, but you are just **reassuring yourself** by asking a question +4. (as interrogative/question ending) you know about something, and you are **asking yourself to confirm** the fact. In this case, do not use 존댓말 +5. (as interrogative/question ending) you do not know something, so you are asking yourself a question. **Usually you are thinking out loud and asking the other people around you at the same time**. 반말 is used in this case as well. + +When speaking in 존댓말, the verb ending -지요 often changes to -죠 for simplicity and ease of pronunciation. + + +### It's okay to / You don't have to {#itsokay} + +`-아/어/여도 되다` + +`되다` means "to function", "to be possible" or "can do" + +1. to turn on, to switch on -> 켜다 +2. it is okay to turn... on, it is okay even if you switch...on -> 켜도 되다 +3. it is okay. you can turn it on -> 켜도 돼요 +4. you can turn the light on -> 불을 켜도 돼요 +5. you can turn the computer on -> 컴퓨터를 켜도 돼요 + + +1. to do -> 하다 +2. it is okay to do / it is okay even if you do -> 해도 되다 +3. it is okay if you do it tomorrow / you can just do it tomorrow -> 내일 해도 돼요 +4. is it okay if I do it tomorrow? -> 내일 해도 돼요? + +To say "do not have to" or "it is not necessary to" add `안` before whole verb[^1] + +### You shouldn't / You're not supposed to {#shouldnot} + +`-(으)면 안 돼요` + +되다 means "to function", "to be possible" or "can do", so `-(으)면 안 되요` literally means "it is not okay if"/"it is not acceptable if"; it is used as "you should not..."/"you are not supposed to..." + +examples: + +1. 열면 안 돼요 - You should not open it / You are not supposed to open it +2. 열면 안 돼요? - Should I not open it? / Am I not supposed to open it? +3. 열면 안 돼! - (to a child) You should not open it +4. 열어도 돼요 - Is it okay to open it / You can go ahead and open it +5. 열어도 돼요? - Can I open it? + + +### Among, between {#amongbetween} + +**중에서, 사이에서, 사이에** + +#### 중에서 + +it means "among" or "between", but it can only be used when listing **a few options** to choose from. + +It **cannot** be used to describe location (ex: "the house is located between the bank and the park"). + +examples: + +1. A하고 B 중에서 = between A and B +2. 이 책하고 저 책 중에서 = between this book and that book +3. 이 세 개 중에서 = among these three things +4. 열 명 중에서 = among ten people +5. 이 중에서 걸라 주세요 = please choose among these +6. 이 세 개 중에서 하나 사져가세요 = please take one of these three + +#### 사이에서 + +It is used to explain relationship or the theoretical space between certain objects or people + +examples: + +1. 친구들 사이에서 인기가 많아요 = he is popular among friends +2. 이 가수는 한국사람들 사이에서 인기가 많아요 = this singer is popular among Koreans + +#### 사이에 + +It is used to refer to the physical space between object or people + +examples: + +1. 은행하고 공원 사이에 있어요 = I am between the bank and the park +2. 약국은 학교하고 경찰서 사이에 있어요 = the pharmacy is between the school and the police station + + +### Any (#any) + +`아무` + +It is used to say "anyone", "anything", or "anywhere". It basically means "any" _in a positive context_ and it **HAS TO** be used along with other nouns - no exceptions. When used in a negative context it means "no + \" + +For positive sentences, add -나 at the end of the word + +- 아무나 = anybody, anyone + - 아무나 올 수 있어요 = anyone can come +- 아무거나 = anything[^2] + - 아무거나 주세요 = just give me anything +- 아무 데나 = anywhere, any place[^3] + - 아무 데나 좋아요 = any place is good + +For negative sentences, add -도 at the end of the word + +- 아무도 = nobody + - 아무도 안 왔어요? / 아무도 없어요? = Nobody is here? +- 아무것도 = nothing + - 아무것도 만지지 마세요 = do not touch anything + - 아무것도 몰라요 = I don't know anything +- 아무 데도 = nowhere + - 아무 데도 안 갈 거예요 = I am not going anywhere + +If you want someone to be careful making a choice, you can use positive sentence in negative context + +examples: + +- 아무나 올 수 없어요 = not everyone can come +- 아무도 올 수 없어요 = nobody can come +- 아무거나 먹으면 안 돼요 = you should not eat just anything +- 아무것도 먹으면 안 돼요 = you should not eat anything at all +- 아무 데나 가고 싶지 않아요 = I do not want to go just anywhere +- 아무 데도 가고 싶지 않아요 = I do not want to go anywhere + +More 아무 phrases + +- 아무 때나 = anytime +- 아무 말도[^4] / 아무 이야기도 = no word, no mention +- 아무렇지도 않다[^5] = to be okay, to be alright, to be unaffected by +- 아무한테도 = to nobody[^6] +- 아무렇게나[^7] = just in any way, however you like it +- 아무(런) + noun + -도 + (없어요) = there is no + noun (of any kind) + - 아무(런) 소식도 없어요 = there is no news[^8] + + + +### Try {#try} + +`-아/어/여 보다` + +literal translation is "to do something and see (what happens)". It is used: + +1. Tell someone to try or attempt something +2. Ask if someone has ever done or tried something +3. make a command sound less demanding + +##### Fixed expressions and verbs containing -아/어/여 보다 + +_important_ in those expressions space is not necessary + +1. 물어보다 vs 물어 보다 (묻다 = to ask) + 1. 물어보다 = to ask, to try asking + 2. 물어 보다 (x) - makes no sense in writing, do not use +2. 알아보다 vs 알아 보다 (알다 = to know) + 1. 알아보다 = to look into something, to recognize + 2. 알아 보다 = (x) - makes no sense in writing, do not use +3. 지켜보다 vs 지켜 보다 (지키다 = keep) + 1. 지켜보다 = to keep a watchful eye on something/someone + 2. 지켜 보다 = (x) - makes no sense in writing, do not use + +##### examples +1. 김치찌개를 먹어 봤어요? = Have you tried kimchi stew? +2. 이 옷을 입어 봐도 돼요? = May I try these clothes? +3. 날씨 많이 더워졌는데[^9], 이번 주말에 제주도에 가 불까요? = It's gotten a lot hotter, so would you like to go to Jeju this weekend? +4. 일 너무 많아서 고향에 갈 수 없는데, 전화해 봐도 돼요? / 불 수 일을 까요? = I can't go to my hometown, because I have too much work to do, can I try calling? + + + +[^1]: 해도 돼요 <-> 안 해도 돼요 + +[^2]: it comes from 아무 + 것이나; 것 means thing + +[^3]: 데 means "place" or "spot". While 곳 also means place, it cannot be used here + +[^4]: 아무 말이나 = any word + +[^5]: 아무 + 그렇다 (to be so) + 지 않다 (to be not); it works only in a negative format + +[^6]: <=> 아무한테나 = to anybody + +[^7]: 아무렇게 works only here in this case, cannot be used independently + +[^8]: 뉴스 is used for TV/newspaper news, for gossip/news from friends/family 소식 is used + +[^9]: 더워지다 = to get hot + + +### Spacing in Korean {#spacing} + +`띄어쓰기` + +When writing in Korean, in order to avoid unclear and confusing sentences, spacing is important. + +#### Space between words + +1. an adjective and a noun + 1. a pretty puppy = 예쁜 강아지 + 2. an early bird[^10] = 부지런한 사람 +2. an adverb and a verb + 1. to walk quietly = 조용히 걷다 + 2. to speak fast = 빨리 말하다 / 말 빨리 하다 +3. noun (+marker) and a verb + 1. I bought this = 이거(를) 샀어요 + 2. I made the one = 그거(를) 만들었어요 +4. a noun and another noun + 1. trip to Korea = 한국 여헹 + 2. the cost of a wallet = 지갑 가격 + +#### No space between words + +1. a noun/pronoun and a marker + 1. I + subject marker = 저 + 는 = 저는 + 2. I + object marker = 저 + 를 = 저를 +2. noun in a proper name + 1. Korea Tourism Organisation = 한국-관광-공사 + 2. Seoul Metropolitan Rapid Transit Corporation = 서울-도시-철도-공사 + 3. Samsung card = 삼성-카드 +3. words which form fixed expression can be written together without space[^11] + 1. Family photo - 가족 + 사진 = 가족사진 + 2. this thing - 이것 +4. noun + 하다[^12][^13] + 1. 공부(를) 하다 = 공부 하다 = 공부하다 + 2. 운동(을) 하다 = 운동 하다 = 운동하다 + 3. 청소(를) 하다 = 청소 하다 = 청소하다 + + +### The most {#most} +`제일, 가장` + +제일 and 가장 are almost the same thing and can be used interchangeably. + +- 제일 = Sino-Korean word +- 가장 = native Korean word + +examples: + +- to be pretty = 예쁘다 +- the most beautiful = 제일 예쁘다 +- the prettiest girl = 제일 예쁜 여자 + +- to be good = 좋다 +- (x) is the best = 제일 좋아요 +- the best thing = 제일 좋은 것 + + +[^10]: in Korean - a hardworking person + +[^11]: commonly found in sino-Korean words + +[^12]: does not work for descriptive verbs, for example 이상 하다 + +[^13]: also works work noun + 있다 (맛있다); when split, marker is needed (맛**이** 있다 / 재미**가** 있다) + +[^14]: `덜` is basically the same as `다 안` diff --git a/notes/Korean phrases.md b/notes/Korean phrases.md new file mode 100644 index 0000000..522cd95 --- /dev/null +++ b/notes/Korean phrases.md @@ -0,0 +1,499 @@ +--- +title: Korean phrases +--- + +Status: 🌿 + +### Thank you + +from most to least formal + +- 감사합니다 +- 고맙습니다 +- 감사해요 +- 고마워요 +- _casual territory_ +- 고마워 +- 감사 (texting) +- ㄱㅅ (= thx) + +### Please give me + +주세요 + +### Here you go + +여기요 + +### Goodbye + +안녕히 계세요 - literally "stay in peace". Used when person you're saying "bye" to is staying and you're leaving + +안녕히 가세요 - literally "go in peace". Used when other person is leaving (regardless if you're staying or going as well). + +### Sorry (apology) + +those are used as an apology, not "I'm sorry to hear that" + +Phrases below mean "I am sorry I did X". + +from most to least formal +- 죄송합니다 +- 미안합니다 +- 죄송해요 +- 미안해요 +- _casual territory_ +- 미안해 +- 미안 +- ㅁㅇ (for textchat, but can be used as "sorry not sorry") + +### Sorry (I'm sorry to hear that) + +괜찮아질 거에요 = it's gonna be okay + +너무 걱정 말아요 = don't worry too much + +건강 관리 잘 해요 = take care of your health + +### It's okay/I'm okay + +괜찮아요 + +### Excuse me +죄송합니다 - "excuse me"/"I'm sorry" - often used when passing through the crows of people or when bumping into someone + +실례합니다 - excuse me + +### Here you go + +여기요 + +### To like + +좋아하다 = to like + +### See you next time + +- 다음에 봐요 +- 봐요 - see you +- 다음 - next time +- 에 - time marker + +### Time + +- 몆시 = what time +- 지금 = now +- 내일 = tomorrow +- 오늘 = today +- 어제 = yesterday +- 정오 = midday +- 자정 = midnight +- 아까 = earlier +- 이따가 / 나중에 = later + - 이따가 집에 가고 싶어요 = I want to go home soon + - 나중에 집에 가고 싶어요 = I don't want to go home/go as late as possible +- 오래 전에 = long time ago +- -번 = -times (몇 번 = how many times) +- 자주 = often +- 얼마나 자주 = how often +- 얼마나 오래 = how long +- 항상 = always + +### Days of the week + +1. 월요일 +2. 화요일 +3. 수요일 +4. 목요일 +5. 금요일 +6. 토요일 +7. 일요일 + +### 계절 Season + +- 봄 - spring +- 여름 - summer +- 가을 - fall, autumn +- 겨울 - winter + +### This/that + +#### 이 (this) +- 이 - this +- 이 물 - this water +- 이거 - this/this thing + +#### 저 (that) +- 저 - that +- 저 커피 - that coffee +- 커거 - that/that thing + +#### 그 (the) +- 그 - the +- 그 가방 - the bag +- 그거 - it/the one + +### 날씨 Weather + +- 날씨 어때요? - how is the weather? +- 하늘 - sky +- 기상예보 - weather forecast +- 첫눈 - first snow +- 화창하다 - sunny +- 흐리다 - cloudy +- 이슬비(가) 내리다/오다 - drizzle +- 바람(이) 불다 - wind/windy +- 덥다 - hot +- 따뜻하다 - warm +- 춥다 - cold +- 시원하다 - cool +- 비(가) 오다/내리다 - to rain +- 번개(가) 치다 - lightning +- 일출 - sunrise +- 일몰 - sunset +- 도 - degrees +- 13.9도 = 십삼 쩜 구 도 = 13.9C +- 저온 - low temperature +- 고온 - high temperature +- 영하 - below zero (for C) +- 습도 - humidity +- 건조하다 - dry +- 습하다 - humid +- 쌀쌀하다 - chilly +- 비가 그치다 - to stop raining + +### Questions +- X + -은/는 요? - How about X? +- 누구 - who +- 누가 - which person +- 누구 예요? - who is it? +- 누가 했어요? - who did it? +- 언제 - when +- 알다 -to know +- 모르다 - to not know +- 어디 - where +- 어디 예요? - where is it? +- 네? - what? +- 뭐 - what +- 왜? - why? +- 어떻게 + verb = how + verb +- 얼마 = how much +- 얼마나 + adj = how + adj + +### Really + +- 조금 - a little, a bit +- 정말 - really, truly +- 진짜 - real(ly) +- 아주 - very, truly +- 별로 - (not) really (only with neg sentences) +- 전혀 - (not) at all (only with neg sentences) + +### In front of/Behind/etc + +- 앞 = front +- 뒤 = back +- 옆 = side +- 위 = top +- 밑, 아래 = bottom + +### to be alike/the same + +같다 = to be like + +noun + (이)랑 = to be the same + +_(with verbs)_ +-(으)ㄴ/는/(으)ㄹ 것 같다 + +### 색, 색깔 - Colour + +| colour | option1 | option2 | +| ------------ | ----------- | ------------------ | +| black | **검정**색 | 블랙 | +| blue | 파란색, 파랑 | 블루 | +| navy blue | 남색 | 네이비 | +| sky blue | 하늘색 | 연(light) 블루 | +| brown | 갈색 | 브라운 | +| dark brown | 진 갈색, 밤색 | 진 (deep, dark) 브라운 | +| gold | 금색 | 골드 | +| silver | 은색 | 실버 | +| gray | 회색 | 그레이 | +| purple | 보라색 | 퍼플 | +| green | 초록색 | 그린 | +| light green | 연두색 | | +| blue-green | 청록색, 민트색 | | +| orange | 주황색 | 오렌지 | +| pink | 분홍색 | 핑크 | +| red | 빨간색, 빨강 | 레드 | +| white | 하얀색, 흰색, 백색 | 화이트 | +| yellow | 노란색, 노랑 | 옐로우 | +| light yellow | 연노란색 | | + +### Korean words similar to English + + (word - 단어) + +| Korean | English | +| ----------- | ------------------------------ | +| 크로와상 | croissant | +| 카페 | cafe | +| 카페 라떼 | cafe latte | +| 바닐라 라떼 | vanilla latte | +| 카라멜 라떼 | caramel latte | +| 스트로베리 프라프치노 | strawberry frappuccino | +| 카푸치노 | cappuccino | +| 아메리카노 | americano | +| 에스프레소 | espresso | +| 시나몬 롤 | cinammon roll | +| 콩글리쉬 | Konglish (Korean + English) | +| 아이쇼핑 | window shopping (eye shopping) | +| 아르바이트 | part-time job (Arbeit) | +| 모닝콜 | wake-up call (morning call) | +| 서비스 | one the house (service) | +| 린스 | har conditioner (rinse) | + +### Exchanging Numbers + +번호교환 + +- to be glad (to meet) = 반갑다 +- to let (someone) know = 알려 주다 (알리다 + -아/어/여 주다) +- to let (someone) know (honorific) = 알려 드리다 +- business card = 명함 +- number = 번호 (specific number ex. phone, house, bus number), 숫자 (any number, ex. number 4) +- mobile phone = 핸드폰, 휴대폰, 스마트폰 +- contact information = 연락처 +- to save = 저장하다 +- to see, to meet (honorific) = 뷥다 + + +### 당신 (you) + +Use with caution in real life conversations - "you" is rarely used, especially when speaking 존댓말 or more format language. + +Uses of `당신` + +1. you are **angry at someone** and do not mind fighting or arguing with that person + 1. 당신 뭐야? / 너 뭐야? = who do you think you are? what are you? + 2. 당신 뭐가 문제야? / 너 뭐가 문제야? = what is your problem? +2. you are **translating a foreign language** and you absolutely must have *a word for "you"* +3. you are **writing or singing a song**, or using indirect language in general + 1. (both 2 and 3) + 2. 당신의 눈은 참 아름다워요 = your eyes are so beautiful + 3. 당신에게 이 노래를 바칩니다 = I dedicate this song to you +4. you are addressing your spouse (commonly used among middle-aged or older people)[^1] + 1. 당신 지금 어디예요? = honey, where are you? + 2. 당신 지금 어디야? = honey, where are you? +5. (rare case) you are talking about someone (**who is not present**) in an honorific way and *want to say "he" or "she"* + +### 괜찮아요 + +1. Present tense = 괜찮아요 +2. Past tense = 괜찮았어요 +3. Future tense = 괜찮을 거예요 + +uses: + +1. I am okay / I am alright / Everything is fine [^4] +2. Do not worry [^5] +3. It is good [^6] +4. I'm good / I'm cool/ No, thanks [^7] + +### Slang + +- 맞을래? - do you want to be hit? [^8] +- 죽을래? - do you want to die? [^8] + +### Sometimes, Often, Always, Seldom, Never, Almost + +Usually they go right before the verb, but their position is very flexible. As long as the meaning of the sentence is clear, it does not matter where they are placed, **but** certain part of a sentence can be emphasized. + +- 가끔 - sometimes +- 자주 - often + +- 항상 - always +- 맨날 - (lit. every day) all the time, always[^13] +- 매일 - every day + +- 별로 - seldom, rarely, not much +- 전혀 = not at all +- 거의 = almost (but) not at all[^14] + +### Word contractions + +Used to make speech faster. If used in text - very informal + +#### -은/-는 + +- 저는 -> 전[^15] +- 나는 -> 난 +- 우리는 -> 우린 +- 이것은 (v formal) -> 이거는 (casual) -> 이건 (casual) +- 서울에는 -> 서울엔 +- 어제는 -> 어젠 + +#### 것이 + +- 이것이 -> 이게 +- 저것이 -> 저게 +- 그것ㅣ -> 그게 + +### Word builder + +#### 학 + +**학** is related to "learning", "studying", "school" + +- 학 + 생 (person, member, participant) = 학생 = student +- 학 + 교 (school) = 학교 = school +- 학 + 원 (house, garden) = 학원 = private academy +- 수 (number) + 학 = 수학 = mathematics +- 과 (subject, class, species) + 학 = 과학 = science +- 어 (word) + 학 = 어학 = language learning +- 언어 (word + word) + 학 = 언어학 = linguistics +- 경제 (economy) + 학 = 경제학 = economics +- 학 + 년 (year) = 학년 = school year (grade) +- 학 + 기 (period) = 학기 = semester +- 방 (to release, let go) + 학 = 방학 = school vacation +- 장학금 = scholarship +- 장학생 = student on a scholarship +- 복학생 = student who has returned to school (usually) after a long break, returning student +- 독학 = self-study, studying by oneself + +#### 실 + +**실** is related to "room" + +- 교 (school, teach) + 실 = 교실 = classroom +- 연습 (practice) + 실 = 연습실 = practice room +- 사무 (office work, desk job) + 실 = 사무실 = office +- 병 (disease) + 실 = 병실 = hospital room, patient's room +- 대기 (wait) + 실 = 대기실 = waiting room +- 화장 (makeup) + 실 = 화장실 = toilet, bathroom +- 분장 ((stage/theatre)makeup) + 실 = 분장실 = dressing room, backstage room (specific to stage/theatre makeup) +- 회의 (meet) + 실 = 회의실 = meeting room, conference room +- 실 + 장 (head, leader) = 실장 = head of the office +- 실 + 내 (inside) = 실내 = indoors +- 실 + 외 (outside) = 실외 = outdoors, outside + +[^1]: other words that can replace 당신 in this usage are 여보 (most common) and 자기 (more common among young couples) + +#### 동 + +동 is related to movement, move, to move + +- 운 (to tranport) + 동 = 운동 = exercise, workout +- 작 (to make) + 동 = 작동 = operation (of a device) +- 활 (to flow, to be alive) + 동 = 활동 = activity[^2] +- 연 (to connect) + 동 = 연동 = linkage, interlocking[^3] +- 동 + 영(to project) + 상(image) = 동영상 = video + +#### 중 + +중 means "center" or "middle" + +- 중 + 학교 (school) = 중학교 (middle school) +- 중 + 식 (eat) = 중식 (format name for "lunch") +- 회의 (meeting, conference) + 중 = 회의중 (meeting in progress) +- 공사 (construction) + 중 = 공사중 (under construction) + +[^2]: 온라인 활동 = online activities + +[^3]: ex: 페이스복 연동 + +[^4]: ex You slip and fall and someone asks you if you are alright + +[^5]: ex: your friend is worrying about something and you want to tell them to not worry + +[^6]: you refer to something as "cool", "good" or "recommendable" + +[^7]: your friend offers you a drink and you want to politely refuse it + +[^8]: not literally, used to express annoyance or "don't" in informal way + + +#### 불 + +`부/불` means "not" + +- 불 (not) + 안 (comfortable) = 불안 = anxiety, anxious[^12] + - 불안하다 >> action >> 불안하 + 아/어/여하다 = 불안해하다 + - 불안해하지 마세요 = Don't be anxious +- 불 (not) + 편 (comfortable, convenient) = 불편 = inconvenient, uncomfortable +- 불 (not) + 완전 (complete) = 불완전 = incomplete +- 불 (not) + 균형 (balance) = 불균형 = imbalance +- 불 (not) + 만 (full) = 불만 = complaint[^9][^10] +- 부 (not) + 정확 (correct) = 부정확[^11] = incorrect/inaccurate +- 부 (not) + 주의 (attention) = 부주의[^11] = carelessness + - 제 부주의로 사고가 났어요 = I was careless, so it caused an accident +- 부 (not) + 당 (correct, right) = 부당[^11] = wrong, unfair, unjust +- 부 (not) + 적절 (proper) = 부적걸 = inappropriate, improper + +#### 가 + +`가` means "family" + +- 가족 = family +- 가구 = furniture +- 외가 = one's mother's paretns' home +- 가전제품 = hosehold electrical appliance + +#### 장 + +`장` means "first" or "head" + +- 부장 = department head +- 사장 = president +- 장녀 = the oldest daughter +- 회장 = chairman + +#### 인 + +`인` means "person" + +- 부인 - wife +- 연예인 - celebrity +- 인형 - doll +- 애인 - lover + +#### 심 + +`심` means "heart" + +- 관심 = interest +- 조심 = caution +- 의심 = doubt +- 자전심 = self-esteem + +#### 외 + +`외` means "outside" + +- 시외 = countryside +- 외국 = foreign country +- 외출 = go out +- 해외 = foreign country + +#### 력 + +`력` means "power" + +- 능력 = ability +- 경력 = career +- 노력 = effort +- 실력 = skill + +[^9]: 저한테 불만 있어요? = Do you have any complaints against me?/Do you have a problem with me? + +[^10]: 만죽 = satisfaction/be pleased + +[^11]: 불 is pronounced and written as 부 when the consonant that follis is ㄷ or ㅈ + +[^12]: can also mean `unstable` for example 불안해요 = It doesn't look stable + +[^13]: more common in spoken + +[^14]: can join other words for different meanings, e.g.: 거의 맨날 = almost every day + +[^15]: warning! also a pancake diff --git a/notes/Korean translations.md b/notes/Korean translations.md new file mode 100644 index 0000000..8a5b4ae --- /dev/null +++ b/notes/Korean translations.md @@ -0,0 +1,8 @@ +--- +title: Korean translations +--- +Status: 🌱 + +As an attempt to boost my learning, my plan is to do some translations of media I enjoy or have gotten access to. + +- [[Jaurim - Damn Ive Been Living Like This]] \ No newline at end of file diff --git a/notes/Korean.md b/notes/Korean.md new file mode 100644 index 0000000..09a67f8 --- /dev/null +++ b/notes/Korean.md @@ -0,0 +1,9 @@ +--- +title: Korean +--- + +Status: 🌱 + +- [[Korean phrases]] +- [[Korean grammar]] +- [[Korean translations]] diff --git a/notes/Making a game with C++ and Raylib.md b/notes/Making a game with C++ and Raylib.md new file mode 100644 index 0000000..5ca207b --- /dev/null +++ b/notes/Making a game with C++ and Raylib.md @@ -0,0 +1,9 @@ +Status: 🌱 + +A bit of context: + +I gotten my hands on a course that was intro to writing games with C++. While it wasn't perfect, I got some starting point and inspiration - Raylib seems low level enough to get me with "all the fun", but high enough so I don't need to manually manage all OpenGL, which felt a bit too much at a time. + +I'm documenting my journey, all with wins, fails and lessons I got along the way. + +1. [[make setup]] \ No newline at end of file diff --git a/notes/Music composition.md b/notes/Music composition.md new file mode 100644 index 0000000..5643139 --- /dev/null +++ b/notes/Music composition.md @@ -0,0 +1,159 @@ +--- +title: Music Composition +--- + +Status: 🌱 + +
+Table of contents + +
+ + +### Motives and Phrases {#motivesphrases} + +##### Motives + +- "smallest musical idea" +- usually 2-7 notes[^1] +- motive is a seed/DNA of things to come +- motives are developed + +2 parts of a good motive: + +1. distinct interval/shape[^2] +2. distinct rhythm + +[^1]: rule of thumb - can be more, but difficult to pull off. Same with 1 note, very exceptional cases. + +[^2]: distinct doesn't necessarily mean never heard before - just something that is recognisable in a piece + + +#### Phrases + +- "complete expression of that idea[^3]" +- consists of motives +- standard phrase is 2 bars long + +3 parts of a good phrase: + +1. motive - no more than 3 motives +2. peak - the most something; can be lowest/highest, loudest, most disonant, etc[^4] +3. punctuation - as in writing, simplest is rest or hold a note[^5]. Important to give listener a pause + +[^3]: idea = motive + +[^4]: it needs to stand out and it's best to hit it only once + +[^5]: good idea is to visualise someone singing and needing to take a breath + + +### Harmonic Function {#harmonicfunction} + +Each chord in a key has a function. + +For major key + +| Tonic | Subdominant | Dominant | +| ----- | ----------- | -------- | +| I | ii | V | +| iii | IV | vii[^6] | +| vi | | | + +C Dm Em F G Am Bdim can change to +Cmaj7 Dm7 Em7 Fmaj7 G7 Am7 Bm7(b5) + +in minor key +Am Bdim C Dm Em F G +Am7 Bm7(b5)[^7] Cmaj7 Dm Em7[^8] Fmaj7 G7[^8] + +[^6]: very spicy in major, beginner should avoid + +[^7]: dimished here is more useful in minor, as it can be seen as "spicy subdominant chord to v" + +[^8]: can be changed to E/E7 and G#dim/G#dim7 to give more pull into tonic + +### Period and sentence forms {#sentenceperiod} + +#### Period + +- 8 bar phrase +- **basic idea**[^9] - 2 bars +- **antecedent** = basic idea + 2bars that end with half cadence[^10] - 4 bars +- **consequent** - basic idea[^11] + 2 bars that end with authentic cadence - 4 bars +- period = antecedent + consequent. It's bit like question and answer, or saying basic idea, "not sure where to go", repeat basic idea and lead somewhere satisfying. + +Period is a very balanced form. ABAC is good representation of it. + +#### Sentence + +- also 8 bar form +- more forward directed than period +- 4 first bars -> basic idea x2[^11] +- bars 5&6 -> **continuation** -> there's "more something"[^12] +- bars 7&8 -> any cadence + +because of open end it is easy to move on, but more difficult to use repetition to extend beyond 8 bars due to repetitive nature of beginning. AABC is good representation of it + +[^9]: pretty harmonically stable + +[^10]: contrasting idea + +[^11]: can be copypaste, can introduce variation, but familiar melody **needs** to be repeated + +[^12]: no matter what more, but more. Bit like with peak. Can be more chords in a bar. Can be idea expressed in 1 bar instead of 2. Can be more notes. + + +### Harmonic Rhythm and Sequence {#harmonicrhythmseq} + +#### Harmonic rhythm + +`how many chords per bar` [^13] + +#### Sequence (in melody) + +Take a small pattern and shift in N steps, for example + +`def efg fga`[^14] + +#### Harmonic Sequence + +`tl;dr the same but for chords` + +Examples: + +- chords going down by 3rds: `C Am F Dm` +- ii V I that goes forever: `Dm7 G7 Cmaj7 Cm7 F7 Bbmaj7 Bbm7 Eb7 Abmaj7...` + +very useful in continuation of sentence form + + +[^13]: use similar chord functions to increate chord count + +[^14]: even if we shift diatonically, not exactly by the same amount, so it fits the scale, if overall shape is the same - it still counts as a sequence + + +### Secondary Dominants {#secondarydominants} + +`tl;dr borrowing V chords from other keys that tonics are present in our key` + +example: + +1. in key of C we have Dm chord +2. in key of D we have A(A7) as dominant chord +3. we can "borrow" that A7 and lead into Dm even in a context of C + +Basically, we can create a "pull" into any chord[^15] and add some extra color (C# in A in example above) + +[^15]: except vii° diff --git a/notes/Signals.md b/notes/Signals.md new file mode 100644 index 0000000..87127ea --- /dev/null +++ b/notes/Signals.md @@ -0,0 +1,24 @@ +--- +title: Signals +tags: se +--- + +Status: 🌿 + +Signals, as Sandi Metz calls them (not sure if she came up with the name or just passed along) is obvious in hindsight but brilliant programming tool. + +Here examples will describe best what they are, so: + +1. Prime/large numbers - pick arbitrary prime/large number, so it signals insignificance of a number. For example, in tests, you can write 5000 where any other number is not bigger than 10; this is a **signal** for others to not search for a meaning behind a number. Personally, I prefer `0` or large numbers instead of primes, as they are more clear on intent. +2. Strings. Same as with numbers, but there's more flexibility. For example, if I need to pass a user ETH wallet address, but it's irrelevant for testing I will go with `"0xfakeaddress"` - so it's clear that it's there just as it's needed and there's no special meaning. If it was a legit address it could make someone believe it's important. + +Signals can also imply meaning. While I'm yet to find this usecase, Sandi shown this example + +In Ruby code blocks can be in `{ }` or `do end` + +1. code in `do end` has side effects +2. code in `{ }` has no side effects + +*(note that it's not any official standard and it's not enforced by anyone or any tool)* + +This is example of syntax based signal that gives clear understanding of a code (outside tests) to show what's happening even before reading the code in the code block. \ No newline at end of file diff --git a/notes/Spectral Forge.md b/notes/Spectral Forge.md new file mode 100644 index 0000000..f01db18 --- /dev/null +++ b/notes/Spectral Forge.md @@ -0,0 +1,42 @@ +--- +title: Spectral Forge +tags: music +--- + +_postmortem_ + +Second solo ambient live I ever did. +May 2023 at Festiwal Światła + +I took some lessons from [[Stellar Chant]] and had some more time. Biggest change was that I decided to make my own visuals (and it kinda worked, more on that later). + +This time I went with 4 tracks and setup with PC (mainly due to visuals). I still had one point of failure, but had everything backed to iCloud/Dropbox so I could recover if I had at least some time. + +Setup for this year: +1. Laptop with Ableton Live 11 Suite. I had samples and instruments there. I `bounced` (aka "make this an audio") almost everything I decided not to play and had MIDI clips just in case if anything goes wrong with MIDI keyboard +2. Arturia Keystep connected to laptop and Ableton to control MIDI. First concept was to change MIDI tracks for different instruments, but was scrapped. +3. SOMA Lyra-8 connected to Ableton with huge convolution reverb for basically whole 2nd track. I did a photo of Lyra setup so I could replicate it if any knob would be changed. +4. Focusright Scarlett Solo as an audio interface and output. +5. MIDI over (50m 🤯) ethernet cable to send MIDI data to change visuals. + +### What went right +- I managed to learn Blender enough to do 1/4 of the visuals and they were cool +- My friend helped me with amazing AI-gen visuals for the rest of the show +- Everything worked perfectly, including MIDI over ethernet +- I had killer outfit to "transform" into MonoChromancer. This seems silly, but helped me a lot to "play character". +- Had a proper soundcheck +- Have better photo/video than last year +- Actually released Spectral Forge as debut album! (even if it's not mixed as well as I would like, it's still a huge lock out of my head) +- A lot of my stickers found new home +- Discovered I can manipulate volume "kinda as an extra instrument" - small changes in volume for some parts really did enhance the show + +### What went wrong +- Still, even with soundcheck with folks I was too quiet. Not as bad as last time, but turns out that a lot of people do dampen the sound a lot. +- I tried rehearsing playing on Arturia before show and it turns out that by far my best take was at home composing. So I decided to ditch whole live playing for 3 tracks out of 4 - so for most part I stayed there trying to look like I'm doing something +- Out of stress I did turn wrong know on Lyra for a while and had to recover quickly during stress. It made the track bit worse + +Lastly, I think I focused too much on "let's make something that will be playable live" and lost track somewhere along the lines. I kinda got lost in a quest to "make live for a festival" that I made a bit compromised version of music. At least it was eye-opening afterwards to change direction and go back to the "proper path" (aka path that actually is fun for me). + +Also, it made me rethink my "all live" approach. I may come from local rock bands background, which may not necessarily translate 1:1 to ambient music. + +Overall a huge net positive, especially with release out and a "wake-up call". \ No newline at end of file diff --git a/notes/Stellar Chant.md b/notes/Stellar Chant.md new file mode 100644 index 0000000..933a56b --- /dev/null +++ b/notes/Stellar Chant.md @@ -0,0 +1,51 @@ +--- +title: Stellar Chant +tags: music +--- + +_postmortem_ + +This was my first ever solo live and first ever ambient live. +May 2022 at Festiwal Światła + +### How I prepared +- I talked a lot with folks and gathered informations and inspirations +- I was thinking about using Number Stations sample and got nice SkyKing recording link from my friend - decided to go with it, as it was great even without processing +- Decided to go PC-less, so I took Deluge, Korg NTS-1, looper, singing bowl and drums +- I decided to split whole thing into 3 parts: + - first, most `dark ambient` like with the sample + - second, more energy focused, with live drums + - third, more `casual generative ambient` to calm down and finish off +- I still prepared a lot of sounds in my DAW and exported WAV files to Deluge, where I would set them up in a song +- I got idea for underlying beat for part 2 from listening to clipping. +- I bounced demos with friends to get early feedback +- Got in touch with friend to create visuals and control lights +- Got in touch with other friends to do a fireshow during the second part +- Printed (in multiple copies) a "cheat sheet" to know when and what to do + +### The setup +Deluge was the main "brain" of the operation. It had the whole song arranged, so I had to do there is to press play. I had one track with noisy synth to play at the end of part 2. It was connected directly to the mixer. +I had a contact mic on snare drum, that I played using brushes. This mic went to a looper (so I could do other things) that went into Korg NTS-1. Korg NTS-1 had `ensemble` effect on (to make mono signal stereo again) and heavy reverb with riser delay. I played with delay time and amount to create texture. It went to mixer as well. +I had a single mic for singing bowl, went straight into the mixer. +Lastly, there was a floor tom with cymbals (and mic to gather the sound) to play during the second part. + +### What went right +- I survived +- Visuals and fireshow added a lot to the live perfomance +- I did learn a lot during all this time (more on that later) +- I managed to do it all in under a month +- I created a set that I actually really liked +- PC-less setup was actually working great. Deluge may be a small cheat thou, as it's basically a hardware DAW + +### What went wrong +- I was too quiet. Definitely don't soundcheck without external help. +- I didn't test how singing bowl sounds on larger scale. Hitting it was really meh and I was to stressed to do proper sound in any other way. Quickly ditched it +- I heard myself not good enough - to the point where I lost programmed beat and was playing unevenly on drums to it. +- Fireshow was great, but when it ended and quiet, simple music slowly started to appear, many people thought it was already over. +- Visuals were on a laptop that died day before the show, so I had quickly made up ones. Lesson - always back up those. And have them with you, so you don't have to rely on external folks +- I let the momentum go away and didn't finish up live version to release as studio album. And, at this point, I will probably never will - unless I revisit it + + +That's it as my memory is bit fuzzy. + +It was great experience, great first barrier broken and I've learned a lot to make [[Spectral Forge]] better. diff --git a/notes/categories.md b/notes/categories.md new file mode 100644 index 0000000..4350695 --- /dev/null +++ b/notes/categories.md @@ -0,0 +1,12 @@ +--- +title: Categories +--- + +Status: 🌱 + +This is a starting point of a `graph`, I list all categories I write about here + +- [[software engineering]] +- [[music]] +- [[random]] +- [[learning]] diff --git a/notes/codex vitae.md b/notes/codex vitae.md new file mode 100644 index 0000000..aed207d --- /dev/null +++ b/notes/codex vitae.md @@ -0,0 +1,25 @@ +--- +title: Codex Vitae +tag: personal +--- + +Status: 🌱 + +This is my Codex Vitae, a list of things I believe/follow in life. Feel free to take anything that resonates, but please remember those are things that work for me and may not necessarily work for you. + +## people +- Don't be a dick +- Give everyone a chance, but if they turn out to be not worth the time - remove from life +- Remember about [[excuse hydra]] and avoid it. +- If you can give some value to someone with low/zero cost - do it. +- Unsolicited help/advice is worse than lack of it + +## philosophy +- Stoicism seems to work really well +- Don't suffer imagined troubles - if something bad has not happened yet, it's not terrible. +- You can prepare for the bad thing thou - just don't get stressed about something +- Happiness comes from things you have control over - from the inside +- You don't have control over other people's reactions +- You do have control over your own reaction - anger is easily managed by stopping for a second before reacting +- Treat every situation like a hand in a card game - you try to play best what you're given, not complain about what you got. +- There's no "inherent fairness" to the world, some people will have better/worse start than you had - don't waste time and energy complaining about it diff --git a/notes/excuse hydra.md b/notes/excuse hydra.md new file mode 100644 index 0000000..d189cee --- /dev/null +++ b/notes/excuse hydra.md @@ -0,0 +1,18 @@ +--- +title: Excuse Hydra +tag: opinions +--- + +Status: 🌱 + +Sometimes people will have an excuse for not doing **the thing**. + +The natural instinct here is to help them dissolve the excuse, to help them. If that happens and they say "thanks!" and go their way, then good job, you did something good. + +But sometimes other thing will happen - they will have another excuse ready. You cut it down too, and there's another one. That's something I call "excuse hydra" -> no matter how many excuses you defeat, there's always a new one. + +My hunch here is that folks who do that don't actually want/need help - just attention. By being there and fighting with hydra, you give them that while wasting your energy and time. + +While I'm not sure if that's the (only) reason for hydra to appear, what I'm sure that one should not engage with excuse hydra. As soon as you notice it - just stop fighting with it. Change topic, or end conversation. It's a waste of time and energy. + +Note: there may be a lot of excuses and it will not be excuse hydra - what I've encourtered the most is excuses being "provided" very quickly, right after you get one down. If you talk with someone for 3 hrs and during that time you get 5 excuses, with some timespan in between, chances are that it's not excuse hydra. diff --git a/notes/just do it.md b/notes/just do it.md new file mode 100644 index 0000000..3bf3a2b --- /dev/null +++ b/notes/just do it.md @@ -0,0 +1,14 @@ +--- +title: Just do it +tags: + - opinions +--- +Status: 🌱 + +I have noticed interesting pattern. While two examples are not entirely enough, I decided to try to test this hypothesis when opportunity arises. + +Long time ago, I decided to start writing in mirror mode. Because it's way easier for a left-handed person to write that way. I approached the challenge very `logically`. I started practicing letters, but kinda got nowhere after a while. Then I just started writing. It went way better than "dry exercise" and I've been writing like this ever since. + +Second case: Korean keyboard. Same thing, I started with typing exercises etc, but then just started writing, even without Korean layout visible. I still make mistakes, but I've seen huge improvement once I started writing and not just doing rewrites. + +My hypothesis here is there are skills (maybe even all?) that benefit greatly from "real world" and not "isolated exercises". Don't write letters. Write text. \ No newline at end of file diff --git a/notes/learning.md b/notes/learning.md new file mode 100644 index 0000000..fca2fe8 --- /dev/null +++ b/notes/learning.md @@ -0,0 +1,11 @@ +--- +title: Learning +--- + +Status: 🌱 + +Here is a list of my notes done during learning various things + +[[Korean]] +[[Making a game with C++ and Raylib]] +[[Music composition]] \ No newline at end of file diff --git a/notes/make setup.md b/notes/make setup.md new file mode 100644 index 0000000..ca417eb --- /dev/null +++ b/notes/make setup.md @@ -0,0 +1,102 @@ +Status: 🌿 + +Because I'm a weirdo, I decided to go with terminal only development. That means no `easy mode` of going with VSCode and pressing `build` to make it work. + +But it turns out (at least for start) it's not as difficult to do: + +### Step one - Install Raylib + +I'm on MacOS, so I just typed `brew install raylib`. You can easily get it on official website as well - https://www.raylib.com + +### Step two - Prepare build + +I went with a very simple Makefile, that I prepared during the course and was using for all projects there + +```bash +.Phony: format + +files := main.cpp + +build: $(files) + clang++ -o game $(files) -Wall -std=c++14 -g -O0 -I. -I/opt/homebrew/include -L. -L/opt/homebrew/lib -lraylib -framework OpenGL + +format: + clang-format -i *.cpp + clang-format -i *.h + +``` + +(You will need clang-format to use `format` target). + +Now, when I type `make`, my code is compiled and I can type `./game` to mess around. +When I type `make format` my code get's formatted. + +For a brief explanation what's happening here: + +- This is a Makefile, which `tldr` "helps building software" +- `.Phony:` is used to say "hey, run it always" +- `files := main.cpp` is where you define files for your c++ project +- `clang++ ...` is the compiling step + - output `game` executable, so it's possible to run `./game` and mess around + - show warnings, use c++14, all that jazz + - include all files from current directory as well as `/opt/homebrew/include` + - link all libs from current directory as well as `opt/homebrew/lib` + - (if brew was not used to install raylib, obviously the paths will change) + - `I want raylib` + - `use OpenGl` +- and `format` -> with `make format` I get formatted code, `clang-format` is needed, obviously + + +### Step three - render something + +With following `main.cpp` + +```cpp +#include "raylib.h" + +int main() { + const int windowWidth = 300; + const int windowHeight = 300; + InitWindow(windowWidth, windowHeight, "Hello Raylib"); + + unsigned char red = 0; + unsigned char green = 117; + unsigned char blue = 44; + Color color = {}; + + SetTargetFPS(60); + while (!WindowShouldClose()) { + red = (red + 1) % 128; + green = (green + 2) % 128 + 128; + blue = (blue + 3) % 128; + color = {red, green, blue, 255}; + BeginDrawing(); + ClearBackground(WHITE); + DrawCircle(windowWidth / 2, windowWidth / 2, 50, color); + + EndDrawing(); + } + CloseWindow(); + return 0; +} + +``` + +Code is not pretty, but will get the job done. +So; what's happening here? + +1. Creating window. Width, height and title. +2. Then, I decided to be a bit fancy and (had to look into Raylib cheatsheet) created manually a color that I will manipulate. + - Yes, those are unsigned chars, probably not most convenient way of doing that + - `Color color = {};` seems like pretty recent addition - simple, but default initialisation is something I really enjoy +4. `SetTargetFPS(60)` set's the maximum FPS the game will run. +5. `while` loop with check if `esc` was pressed or `close window` button was pressed. Pretty handy, thou for game I would have not just kill everything on simple `esc` press. +6. Do wonky color manipulation. +7. `BeginDrawing()` and `EndDrawing()` are required, to easily show what goes into a frame. +8. `ClearBackground(WHITE);` + - `WHITE` is Raylib's built in `Color` that we can use. + - this method is used to prevent screen flickering +9. Draw our circle in the middle of the screen. Left right edge is {0,0} and it increases down and right. We give it `color`, so it is `animated`. +10. Once we're out of the loop, close window and be on own's merry way. + +That should give a solid headstart for some simple experimentation with Raylib - if you know how to code it should be fun exploring how this can be extended. \ No newline at end of file diff --git a/notes/music.md b/notes/music.md new file mode 100644 index 0000000..4003631 --- /dev/null +++ b/notes/music.md @@ -0,0 +1,11 @@ +--- +title: Music +--- + +Status: 🌱 + +While there may be some things I will have to share about music making, this category starts as a "journaling" of my music making I may add some more stuff in the future. + +- [[Stellar Chant]] +- [[Spectral Forge]] +- [[Hidden Mineral World]] \ No newline at end of file diff --git a/notes/random.md b/notes/random.md new file mode 100755 index 0000000..ff905d8 --- /dev/null +++ b/notes/random.md @@ -0,0 +1,10 @@ +--- +title: random +--- + +Status: 🌱 + +(At least for now) a bag for all thoughts that do not fit other categories + +- [[excuse hydra]] +- [[just do it]] diff --git a/notes/software engineering.md b/notes/software engineering.md new file mode 100644 index 0000000..7c1e7b9 --- /dev/null +++ b/notes/software engineering.md @@ -0,0 +1,8 @@ +--- +title: Software Engineering +--- + +During my years working with code I stumbled upon stories to share and some thoughts to explore. All of those will be put here + +[[SOLID for FP]] +[[Signals]] diff --git a/notes/solid for fp.md b/notes/solid for fp.md new file mode 100644 index 0000000..d738f3c --- /dev/null +++ b/notes/solid for fp.md @@ -0,0 +1,16 @@ +--- +title: SOLID for FP +tags: se, fp +--- + +Status: 🌱 + +I have OOP brackground and used SOLID and other OOP techniques to make my code better. + +Since then I switched to FP and feel like there's not enough `guidelines` for writing FP code. At the same time I have a hunch that some of the OOP wisdom can be applied here. + +- **S**ingle Responsibility Principle - this one is easy and free to take. Just make sure that your methods have "one reason to change" - a single responsobility. Make them small and specialized. Anything with `and` in name can be a sign that there's too much going on +- **O**pen Close Principle - this one is trickier, but if we say that refactoring is flow of making code open to extension - this makes things easier to adapt. Basically you want to be able to add new functionalities withtout altering existing code - and this can be achieved in FP. +- **L**iskov Substitution Principle - +- **I**nterface Segregation Principle - +- **D**ependency Inversion Principle - can be argued to go with "top level module" as main dependency, instead of more specialized ones.