If the sound files don't match up exactly, one delivery might be longer or shorter, then the lip files will have to be done again to match the new sound files. Fun times.
Hey guys.
1) It's indeed a very good Clint-Eastwoodish sound, as far as I'm concerned. Good recording, too. (My voice is at its roughest when I'm actually hangover, so maybe you could try that).
2) I'm not specifically looking to "enhance" RP. So far, I have my hands full just figuring out its bugs.
3) Everyone is able and welcome to submit pull requests at https://github.com/BGforgeNet/Fallout2_Restoration_Project.
4) There's plenty of people who are able to convert the voicing into FO2 format and submit a pull request. I trust that if there's demand, there will be supply.
5) Every (already) voiced line has a sound id it it - Cas0103, Cas0104 here:
Not every Cassidy's line has it, but these would be a good start. Anyway, the whole file is not that large.Code:{102}{}{You see an elderly man with deep wrinkles along his face. He nods at you.} {103}{Cas0103}{Well, now. I ain't seen you around before, stranger. Name's Cassidy. I run this place. What can I do for you?} {104}{Cas0104}{Well now, if it ain't the mysterious stranger. What can I do for you today?} {105}{}{Ug Nog?}
If the sound files don't match up exactly, one delivery might be longer or shorter, then the lip files will have to be done again to match the new sound files. Fun times.
Traitor!The voice sounds like a true Texan wastelander, I like this alternative version.
Hey slick.Oh damn @Dravean replied! Hey man – you should TOTALLY record again, but I'd be glad to still offer mine up as an alternative for anyone who wants it
Just had a go at recording a couple Cass lines again as I can't seem to find my original files ().
My problem is that I don't seem able to get the "wav2lip" converter thing that @burn helpfully linked to to workI wonder if @Lexx could weigh in?
Thing is, wav2lip does not open a command line when I try to run it. It's like it's immediately closing.
I'm not familiar with this program but it probably because it expects terminal input. It might spit out some general use info when you run it and then exit. And since the program is finished it will also close the window.
Open a cmd prompt and go to the directory where the executable is and start it from there and it wont close.
cd <path to exe folder>
<name of exe>
If you get no output try add adding /?, -h or --help