Version 1.2.0
This commit is contained in:
parent
1526ee69ef
commit
6a16a706c9
|
@ -5,7 +5,7 @@ set(CMAKE_OSX_DEPLOYMENT_TARGET "10.7" CACHE STRING "Minimum OS X deployment ver
|
|||
|
||||
set(appName "Rhubarb Lip Sync")
|
||||
set(appVersionMajor 1)
|
||||
set(appVersionMinor 1)
|
||||
set(appVersionMinor 2)
|
||||
set(appVersionPatch 0)
|
||||
set(appVersionSuffix "")
|
||||
set(appVersion "${appVersionMajor}.${appVersionMinor}.${appVersionPatch}${appVersionSuffix}")
|
||||
|
|
|
@ -1,5 +1,13 @@
|
|||
# Version history
|
||||
|
||||
## Version 1.2.0
|
||||
|
||||
* **Dialog file needn't be exact**
|
||||
|
||||
Since version 1.0.0, Rhubarb Lip-Sync can handle situations where the dialog text is specified (using the `-dialogFile` option), but the actual recording omits some words. For instance, the specified dialog text can be "That's all gobbledygook to me," but the recording only says "That's gobbledygook to me," dropping the word "all."
|
||||
|
||||
Until now, however, Rhubarb Lip-Sync couldn't handle *changed* or *inserted* words, such as a recording saying "That's *just* gobbledygook to me." This restriction has been removed. As of version 1.2.0, the actual recording may freely deviate from the specified dialog text. Rhubarb Lip-Sync will ignore the dialog file where it audibly differs from the recording, and benefit from it where it matches.
|
||||
|
||||
## Version 1.1.0
|
||||
|
||||
* **More reliable speech recognition**
|
||||
|
|
Loading…
Reference in New Issue