
Sign up to save your podcasts
Or
Hi and welcome to the GYSO Game Dev Podcast! Follow Thor and Tim as they develop a public domain video game and feel bad about the entire process.
These shownotes are shortened to fit character limits with our distributor. Please view all of it at our main page.
26:57 Thor realizes he has forgotten to take shownotes, and that it's one of his apparent obligations in editing this crap. What's been talked about? I don't really care, complaining about software, crippling perfectionism, how no one cares about the podcast, and probably some other trite nagging.
27:20 Editing this podcast, I've started listening back at 1 2.5x speed, and I'm really only doing it because I need to figure out where the transitions are. We're in What Went Right, by the way.
29:15 Godot as a name is confusing because there are two ways to say the name
30:00 Anyways, it's pretty convenient to listen through that fast, and I'm imagining any listener doing the same thing, because it's really hard
31:15 Object Oriented Programming is bad because it just is
31:45 ... because it's really hard to go back to listening to normal human speaking voices if you've gotten used to speaking at speeds of like 1.25 or 1.5 or 1.6. It really doesn't take that long, it's efficient, and normal speech sounds annoyingly slow when you are forced to go back.
34:20 Going forward, I'm going to try to add markers on my machine as we're recording, so that I can just tab through the markers wherever we place our transitions, because I stopped editing out our long pauses and trying to mute out when one is speaking over the other in, like, part 2.
38:30 I just don't care enough to edit through that stuff. Actually, if I could set up a system of automation, I might
41:08 Our old project, Not Rogelands
41:50 I might use that automatic system, but the problem is *going back in time* when you notice that something should be edited. How far do you need to go, what do you want to do then?
43:03 Even if you reduce your edit actions to a very limited set, maybe.
48:00 What Went Wrong?
48:40 okay I lost my train of though.
49:30 Yeah, so even if you have mute/unmute as binary states, that's not going to sound the best. You're going to want to add crossfades to mute.
50:56 We talk about Anki, the SRS program for a long while here
51:35 It's just not an option, you're going to get unnatural clicks and pops and stops. Believe it or not, but you're going to notice a hard mute on one of our channels.
54:52 This is the first episode where I've applied actual noise reduction to my (Thor) voice, the electrical noise was a bit too much. In other episodes, I have thought it added that slight background noise that tells the listener that the audio file is working, without being overbearing. But something about my compression in this new setup, as I've been discussing the past parts, seems to bring that forth a bit too much.
58:00 Oh and Reaper is super unintuitive for editing long-form content like this. I have to stop using the spacebar for play/pause to using the enter key, because Reaper doesn't actually use play/pause stock. It's more "start from marked position on the timeline" and "stop playing audio and reset the position of the playhead to the marked position on the timeline". Good for editing, and listening back to repeated sections.
1:01:30 Computer specs
1:33:36 I skipped like 8 minutes because these endings are always a drag. We don't get better at this in the coming episode.
1:35:00 Goodbye
Link to the git repo: https://gitlab.com/goopy/get-your-g4me-on
Hi and welcome to the GYSO Game Dev Podcast! Follow Thor and Tim as they develop a public domain video game and feel bad about the entire process.
These shownotes are shortened to fit character limits with our distributor. Please view all of it at our main page.
26:57 Thor realizes he has forgotten to take shownotes, and that it's one of his apparent obligations in editing this crap. What's been talked about? I don't really care, complaining about software, crippling perfectionism, how no one cares about the podcast, and probably some other trite nagging.
27:20 Editing this podcast, I've started listening back at 1 2.5x speed, and I'm really only doing it because I need to figure out where the transitions are. We're in What Went Right, by the way.
29:15 Godot as a name is confusing because there are two ways to say the name
30:00 Anyways, it's pretty convenient to listen through that fast, and I'm imagining any listener doing the same thing, because it's really hard
31:15 Object Oriented Programming is bad because it just is
31:45 ... because it's really hard to go back to listening to normal human speaking voices if you've gotten used to speaking at speeds of like 1.25 or 1.5 or 1.6. It really doesn't take that long, it's efficient, and normal speech sounds annoyingly slow when you are forced to go back.
34:20 Going forward, I'm going to try to add markers on my machine as we're recording, so that I can just tab through the markers wherever we place our transitions, because I stopped editing out our long pauses and trying to mute out when one is speaking over the other in, like, part 2.
38:30 I just don't care enough to edit through that stuff. Actually, if I could set up a system of automation, I might
41:08 Our old project, Not Rogelands
41:50 I might use that automatic system, but the problem is *going back in time* when you notice that something should be edited. How far do you need to go, what do you want to do then?
43:03 Even if you reduce your edit actions to a very limited set, maybe.
48:00 What Went Wrong?
48:40 okay I lost my train of though.
49:30 Yeah, so even if you have mute/unmute as binary states, that's not going to sound the best. You're going to want to add crossfades to mute.
50:56 We talk about Anki, the SRS program for a long while here
51:35 It's just not an option, you're going to get unnatural clicks and pops and stops. Believe it or not, but you're going to notice a hard mute on one of our channels.
54:52 This is the first episode where I've applied actual noise reduction to my (Thor) voice, the electrical noise was a bit too much. In other episodes, I have thought it added that slight background noise that tells the listener that the audio file is working, without being overbearing. But something about my compression in this new setup, as I've been discussing the past parts, seems to bring that forth a bit too much.
58:00 Oh and Reaper is super unintuitive for editing long-form content like this. I have to stop using the spacebar for play/pause to using the enter key, because Reaper doesn't actually use play/pause stock. It's more "start from marked position on the timeline" and "stop playing audio and reset the position of the playhead to the marked position on the timeline". Good for editing, and listening back to repeated sections.
1:01:30 Computer specs
1:33:36 I skipped like 8 minutes because these endings are always a drag. We don't get better at this in the coming episode.
1:35:00 Goodbye
Link to the git repo: https://gitlab.com/goopy/get-your-g4me-on