Just dropped the new dlls in right now and still getting crashes. Gonna try
looking through my Windows install now.

On Tue, Dec 14, 2010 at 6:05 AM, Cory de La Torre <gear....@gmail.com>wrote:

> Thanks tom, really appreciate it. I'll go looking for those files, though
> might you have any idea which folder they would be located in within the cd
> directory? I'm assuming it would be in the root directory of windows though.
>
>
> On Tue, Dec 14, 2010 at 4:44 AM, Tom Edwards <cont...@steamreview.org>wrote:
>
>> Someone once said they fixed the problem by copying some SAPI-related DLLs
>> off their Windows install CD. They disappeared without telling anyone what
>> those files were, unfortunately.
>>
>> The SAPI extractor is crumbling away because Valve don't use it. They have
>> a different extractor built with phoneme middleware that they don't - I
>> assume - have a distribution license for.
>>
>> I went back to the extractor just now to make sure it still works and
>> found a bug in the error message that appears when extraction totally fails.
>> Somehow I'd cocked up the process of launching the control panel app. Fix
>> here: http://steamreview.org/external/vdc/phonemeextractor_sapi5.4.zip
>>
>>
>> On 14/12/2010 11:50, Cory de La Torre wrote:
>>
>>> Not really sure if this falls under mapping or not, so I threw it in the
>>> coders list. My current problem is extracting phenom extraction. I'm
>>> currently using Tom Edwards "fixed" phonemeextractor.dll. For reasons I
>>> can't seem to understand is during the extraction (after putting in the
>>> sentence for the audio file and clicking ok) faceposer just plain
>>> crashes.
>>> I've found it works for other people and sometimes it doesn't, though I
>>> seem
>>> to be the in the rare group of people that faceposer just plain crashes
>>> on
>>> during the extraction.
>>>
>>> I was following a tutorial earlier that dates back to around 2008.The
>>> tutorial has directed me to go and download the SpeechSDK and install
>>> that.
>>> Upon further investigation I've found that under Windows 7 you don't even
>>> need that, and just the fixed dll. After reading some more I've come to
>>> another fork in the road. It seems the only way to get this shit all
>>> fixed
>>> up again is to reinstall windows, something I am totally not going to do
>>> if
>>> this still doesn't end working. Honestly I shouldn't have to reinstall my
>>> operating system anyways. Thats a severe punishment for this going south.
>>> My
>>> question is whether or not installing the SpeechSDk is the reason
>>> Faceposer
>>> is crashing at extraction.
>>>
>>> To clarify I've went and uninstalled the SpeechSDK before putting in the
>>> fixed phonemeextractor.dll.
>>>
>>>
>>> Aside all of this madness; whats going on anyways!? I wouldn't have
>>> expected
>>> getting faceposer to work would be all this trouble under 2009 on future
>>> operating systems that almost everyone has entirely migrated too. I'm
>>> assuming Valve is at least using some Windows 7 and Vista machines up
>>> there,
>>> unless they are seriously using XP to use a "working" faceposer. The fact
>>> we
>>> need to use a custom modified dll to get all this working again is pretty
>>> bad. Faceposer should "just work" out of the box, and not require any
>>> users
>>> to go searching around for things. Yeah, yeah I know, not in valves
>>> current
>>> needs to do (too busy, yadda yadda) but that shit is starting to get real
>>> tiring. I'd like for once to actually be able to use a single Source
>>> Engine
>>> tool that isn't made by someone outside of Valve and works/does not
>>> require
>>> workarounds.
>>>
>>>
>> _______________________________________________
>> To unsubscribe, edit your list preferences, or view the list archives,
>> please visit:
>> http://list.valvesoftware.com/mailman/listinfo/hlcoders
>>
>>
>
>
> --
> Gear Dev
>



-- 
Gear Dev
_______________________________________________
To unsubscribe, edit your list preferences, or view the list archives, please 
visit:
http://list.valvesoftware.com/mailman/listinfo/hlcoders

Reply via email to