2023-01-20 (F) Weekly Summary

I started editing but did not get as far as I wanted. I spent a lot of effort timing the pauses and overlap between people speaking. I figured out how to move all the tracks simultaneously, which helped immensely.
Editing: round 1

I hit a snag on the back-and-forth dialog because a station crewman was supposed to be speaking in the background while everyone else spoke over him, but he had too much to say, so I had to shorten his part, which means I will have to re-record him.
Script revision

The station crewman's lines will wait until I set up the recording desk again, so I kept editing. I applied a low-pass filter to a clip to make it sound like a cat was behind a cupboard cover, and I began documenting times in the script when I came to chapter breaks.
Editing: round 3

I got to the halfway point of editing, as far as the total time goes. I figured out a faster way to edit, so that progress may move faster. The trick was to break up the chores and do them in batches.
Editing: round 4

I could not cover much material during this session because every track had at least one clip, so I had to mind them all. I took extra care to make the gaps between speakers sound natural, but it took a lot of time and was messy with six tracks.
Editing: round 5

I edited ~20% of the play as I improved my proficiency with the software and learned some of the quirks. I am now much faster at selecting all clips after a marker to move them at once.
Editing: round 6

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.

Comments