OLD | NEW |
(Empty) | |
| 1 # The Chrome OS PATTS speech synthesis engine |
| 2 |
| 3 Chrome OS comes with a speech synthesis engine developed internally at Google |
| 4 called PATTS. It's based on the same engine that ships with all Android devices. |
| 5 |
| 6 ## Building from source |
| 7 |
| 8 This is for Googlers only. |
| 9 |
| 10 Visit [http://go/chrome-tts-blaze](http://go/chrome-tts-blaze) |
| 11 for instructions on how to build the engine from source and get the |
| 12 latest voice files. |
| 13 |
| 14 When debugging, start Chrome from the command-line and set the |
| 15 NACL_PLUGIN_DEBUG environment variable to 1 to print log messages to stdout. |
| 16 |
| 17 ## Updating |
| 18 |
| 19 First, follow the public |
| 20 [Chromium OS Developer Guide](http://www.chromium.org/chromium-os/developer-guid
e) to check out the source. |
| 21 At a minimum you'll need to create a chroot. |
| 22 You do not need to build everything from source. |
| 23 You do need to start the devserver. |
| 24 |
| 25 Next, flash your device to a very recent test build. Internally at Google |
| 26 you can do this with the following command when the dev server is running, |
| 27 where CHROMEBOOK_IP_ADDRESS is the IP address of your Chromebook already |
| 28 in developer mode, and $BOARD is your Chromebook's board name. |
| 29 |
| 30 ```cros flash ssh://CHROMEBOOK_IP_ADDRESS xbuddy://remote/$BOARD/latest-dev/test
``` |
| 31 |
| 32 Before you can make changes to PATTS, the first thing you need to run |
| 33 (from the chroot) is call cros_workon with two relevant ebuilds: |
| 34 |
| 35 ``` |
| 36 cros_workon --board=$BOARD start chromeos-assets |
| 37 cros_workon --board=$BOARD start common-assets |
| 38 ``` |
| 39 |
| 40 Next, make sure you're in the platform/assets directory and run |
| 41 ```repo start``` and create a branch. |
| 42 |
| 43 ``` |
| 44 cd platform/assets |
| 45 repo start <branch_name> . |
| 46 ``` |
| 47 |
| 48 |
| 49 The PATTS data files can be found in this directory: |
| 50 |
| 51 ```platform/assets/speech_synthesis/patts``` |
| 52 |
| 53 When updating the files, the native client files (nexe) need to be zipped. |
| 54 |
| 55 Replace all of the files you need to update, commit them using git, |
| 56 then from the chroot, run: |
| 57 |
| 58 ``` |
| 59 emerge-$BOARD common-assets |
| 60 cros deploy CHROMEBOOK_IP_ADDRESS common-assets |
| 61 ``` |
| 62 |
| 63 Note that you need to call cros_workon on both chromeos-assets and |
| 64 common-assets. You will be changing files in chromeos-assets, but |
| 65 to flash it onto your device, you need to emerge and deploy |
| 66 common-assets. |
| 67 |
| 68 After that, reboot your Chromebook and verify that speech works. |
| 69 |
| 70 To upload the change, use repo upload, something like this: |
| 71 |
| 72 ``` |
| 73 git commit -a |
| 74 BUG=chromium:12345 |
| 75 TEST=Write what you tested here |
| 76 repo upload . |
| 77 ``` |
OLD | NEW |