Hey, all. I'm putting together some spotter packs using Mystical's excellent index resource.
I have a few goals. One is a dedicated trucks spotter pack. Another will obviously be a Cup car spotter pack. I do have a proof of concept here. (Excuse any profanity and vulgarity) -- It's taken some trial and error, but I have the audio quality about where I want it (after I merge onto the track in that video); just have to fix the popping P's and the muddy S's a little bit more, hence me stressing those sounds in the test.
My friend and I have actually already made one from the ground up recently using Mystical's guide. It takes about 2 hours or so to record with bloopers and edits on-the-fly, and honestly only about 4 hours or so to chop the recording up into the 500+ individual WAV files. But the audio quality was garbage (see the pit-road speed limit callout at the beginning of the video I linked), so I experimented with Audacity and found a pretty good setup to get crisp, clear callouts. Once I have the workflow down pat, I'm going to put together a YouTube spotter-pack tutorial of some kind, as well.
I guess I'm just asking for any unique ideas you all have for spotter packs. It's just impossible for one person alone to come up with 500+ unique callouts and/or ideas, and I've hit a wall creatively. Any good resources you know of in terms of NASCAR slang, spotter transcripts, anything will be helpful. As it stands, the spotter packs will have some profanity with a piss here and a shit there scattered, but no F-bombs and by no means are they profanity-laden. Also, the one thing I've learned with making even ONE spotter pack from scratch is that jokes/clever one-liners that are funny at first...get old FAST.
And I promise you, this isn't something that "Hey, I'm working on..." and then it just disappears. In a few weeks at most, the community's spotter pack database will practically double overnight with everything I'm putting together, and I just want some input from everyone and possibly anyone interested in really putting the packs through their paces to find any errors/weak spots. Thanks.
I have a few goals. One is a dedicated trucks spotter pack. Another will obviously be a Cup car spotter pack. I do have a proof of concept here. (Excuse any profanity and vulgarity) -- It's taken some trial and error, but I have the audio quality about where I want it (after I merge onto the track in that video); just have to fix the popping P's and the muddy S's a little bit more, hence me stressing those sounds in the test.
My friend and I have actually already made one from the ground up recently using Mystical's guide. It takes about 2 hours or so to record with bloopers and edits on-the-fly, and honestly only about 4 hours or so to chop the recording up into the 500+ individual WAV files. But the audio quality was garbage (see the pit-road speed limit callout at the beginning of the video I linked), so I experimented with Audacity and found a pretty good setup to get crisp, clear callouts. Once I have the workflow down pat, I'm going to put together a YouTube spotter-pack tutorial of some kind, as well.
I guess I'm just asking for any unique ideas you all have for spotter packs. It's just impossible for one person alone to come up with 500+ unique callouts and/or ideas, and I've hit a wall creatively. Any good resources you know of in terms of NASCAR slang, spotter transcripts, anything will be helpful. As it stands, the spotter packs will have some profanity with a piss here and a shit there scattered, but no F-bombs and by no means are they profanity-laden. Also, the one thing I've learned with making even ONE spotter pack from scratch is that jokes/clever one-liners that are funny at first...get old FAST.
And I promise you, this isn't something that "Hey, I'm working on..." and then it just disappears. In a few weeks at most, the community's spotter pack database will practically double overnight with everything I'm putting together, and I just want some input from everyone and possibly anyone interested in really putting the packs through their paces to find any errors/weak spots. Thanks.