2022-12-23 (F) Weekly Summary

I got back to recording, but I am also taking voice-over classes, so as I learn, I will practice with Gravy Shock and start over when I'm confident in my skills. The first session had a handful of voices, but I used voice-altering hardware to differentiate characters this time.
First recorded session of the new take

It should work better to record one character at a time and embody them rather than blasting through everyone at once. I did this for Ness and finished the chapter, and I'm happier with this session's quality.
Ness 1.1

I kept plugging away at Ness's track, but I didn't make it as far as I had hoped because I ran into a problem where I repeatedly deleted their track. It could have been an error on my part or a bug in Audacity, but I made some progress.
Ness 1.2

I made more progress on Ness than on any other day, and I did better work. My goal is to get through the first pass, then record all their lines in one killer session.
Ness 1.3

I didn't record much, but I focused on improving the sound and made subtle changes. I read an article about choosing a decent microphone and ordered a new one so I don't have to rely on Audacity's Noise-Reduction filter.
Ness 1.4

I recorded another big chuck, but it was challenging. I'm nervous about recording Ness's entire script in a day, but I'm improving.
Ness 1.5

The rest of the summary posts have been arranged by date.
First time here?

Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Completed projects from year 7
Completed projects from year 8

Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com

This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.

All information on this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.

All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.

Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.

This blog, including pictures and text, is copyright to Brian McEvoy.