Welcome to the Poser - OFFICIAL Forum

Forum Moderators:  Digitell, CHMedia    Forum Coordinators:  RedPhantom

Poser - OFFICIAL F.A.Q (Updated: 2020 May 06 10:25 am)


 Subject: Problem with wav and mp3 files in Talk Designer

WiltonJohn opened this issue on Sep 16, 2020 · 6 posts

Top of Forum Print

  WiltonJohn    ( ) ( posted at 3:49PM Wed, 16 September 2020 

Newish Poser user here Poser Ver. 11.3.818 on Win 10, all Microsoft updates in place. Powerful i9-9900K Coffee Lake 3.6 Gig liquid cooled RTX-2080Ti video editing machine with 64 Gigs of DDR4 RAM. SSDs for main and data. I'm trying to get a character to be animated with Talk Designer. I've used Audacity to process the audio I need and output the file. I've tried both wav file and mp3 files in Poser. Some files I've done (VERY short... like three words) the exact same way with this character work for me. But a slightly longer file... like 10 words,........... says "this audio format is not supported for lipsync". But the exact same format files (but VERY short ones) just worked! Processed the same way in Audacity. I've researched this and tried the "plug and unplug a headphone/microphone" "solution... and also the "filename can't have a - character" one. No joy. Anyone have a suggestion for me? Driving me nuts. Thanks.


  Richard60    ( ) ( posted at 9:18PM Wed, 16 September 2020  · @4399667

From the manual Sounds used in the Talk Designer must be uncompressed, single channel (mono) audio files in WAV (Windows) or AIFF (Mac) format. 22050 and 44100 kHz files are supported.

Very important the file meets these requirements.

Poser 5, 6, 7, 8, Poser Pro 9 (2012), 10 (2014), 11

  WiltonJohn    ( ) ( posted at 9:50PM Wed, 16 September 2020  · @4399668

Thanks.... but I actually know it works for BOTH WAV's and MP3's ... because I've done it and it worked just fine with the mp3's as well. But I still have the issue with SOME WAV's (and the same copies of the files saved as mp3's). Even though the files have been processed "thru" Audacity and saved in the same file output conditions (bit rate, codec, etc.) .....they started out from different device outputs. I'm thinking THAT is somehow the source of the issue. Even though they are "washed" in Audacity, there is some "trace" of the formatting that gets passed thru in the final output. I'm thinking that shouldn't be..... but it is looking like that situation can be replicated.


  WDBeaver    ( ) ( posted at 1:48PM Thu, 17 September 2020 · edited on 1:49PM Thu, 17 September 2020 · @4399730

From my experience, one of the wave issues is just what .wav format is involved. There is metadata attached to the raw audio that is meant to be read by one specific editor, and that can sometimes cause issues. Audacity (and many other NLA's) ignore metadata that it doesn't recognize, but that doesn't mean they strip it out.

Another issue is the memory pool. I haven't used talk designer in ages, but the last I recall, its a 32 bit program, so you have a 2 gig memory pool limit per session, including the .wav file being played. Bit dense .wav's will have issues running in TD, as the executable stalls if the memory ceiling it so much as bumped. Check the actual file size, then add it to what is running in task manager's processes.

Audacity rules in the freeware NLA's doesn't it?

One solution is to downscale the animation .wav. Drop the bit rate so enough of the waveform is there to drive the morphs and no more, then in post add in the higher density sound instead. You should get quicker results, less stalls, and still have the higher quality voice. It adds a couple of steps, but the time you save instead of trying to run multiple failed loops in more than compensated for.


  WiltonJohn    ( ) ( posted at 6:24PM Thu, 17 September 2020  · @4399744

Thanks for the detailed info, WDBeaver. I was already using a slightly "downscaled" file for the animator part of things (figured it would help with picking up the voice sounds to drive the morphs) and then will sync the quality audio file in my post work. I didn't know that Audacity just left in stuff that it "ignores"...... and passes it thru to the output. Thought it'd strip such stuff out. Assumptions get ya' every time. Good info.

best,

................john


  WDBeaver    ( ) ( posted at 4:32PM Fri, 18 September 2020  · @4399795

WiltonJohn posted at 4:30PM Fri, 18 September 2020 - #4399744

Thanks for the detailed info, WDBeaver. I was already using a slightly "downscaled" file for the animator part of things (figured it would help with picking up the voice sounds to drive the morphs) and then will sync the quality audio file in my post work. I didn't know that Audacity just left in stuff that it "ignores"...... and passes it thru to the output. Thought it'd strip such stuff out. Assumptions get ya' every time. Good info.

best,

................john

You're welcome!

We really need a dedicated wiki or archive for all the stuff we learn through beating our heads against the walls, one with a good index.


 To create a post you must first sign in or register an account.

Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.