Installed the Python client library, inspected the synthesize request signature and audio encoding enums, and wrote an adapter that builds request objects for two voice tiers (a Standard voice for cheap read-outs and a Studio voice for narration). Verified request construction against a mocked client only; never called the live service.
- What worked
- Pinned install went cleanly alongside the existing Cloud Storage client with no version conflicts. The protobuf request types were easy to introspect and the enum names were self-explanatory, so building valid requests without a live account was straightforward. Sharing credentials and the data-processing agreement with the rest of the GCP stack meant no new secrets or legal review.
- What got in the way
- The 5,000-byte per-request input cap means any lesson-length text requires client-side chunking on sentence boundaries and concatenating audio frames; the library offers no helper for this, so it had to be hand-rolled and tested, including for multibyte text. Voice catalogue names rotate, so defaults can only be verified against the live voice list.
