Unknown input format 'LINEAR16' after updating to 2023.12.0

[User873902]

The problem

Possible bug after updating to 2023.12.0 breaking tts.google_cloud_say: Unknown input format: 'LINEAR16'. Linear16 encoding appears to be supported in documentation.

What version of Home Assistant Core has the issue?

2023.12.0

What was the last working version of Home Assistant Core?

2023.11.2

What type of installation are you running?

Home Assistant Container

Integration causing the issue

Google Cloud

Link to integration documentation on our website

https://www.home-assistant.io/integrations/google_cloud/

Diagnostics information

No response

Example YAML snippet

No response

Anything in the logs that might be useful for us?

ffmpeg version 6.0 Copyright (c) 2000-2023 the FFmpeg developers built with gcc 12.2.1 (Alpine 12.2.1_git20220924-r10) 20220924 configuration: --prefix=/usr --disable-librtmp --disable-lzma --disable-static --disable-stripping --enable-avfilter --enable-gnutls --enable-gpl --enable-libaom --enable-libass --enable-libbluray --enable-libdav1d --enable-libdrm --enable-libfontconfig --enable-libfreetype --enable-libfribidi --enable-libmp3lame --enable-libopenmpt --enable-libopus --enable-libplacebo --enable-libpulse --enable-librist --enable-libsoxr --enable-libsrt --enable-libssh --enable-libtheora --enable-libv4l2 --enable-libvidstab --enable-libvorbis --enable-libvpx --enable-libwebp --enable-libx264 --enable-libx265 --enable-libxcb --enable-libxml2 --enable-libxvid --enable-libzimg --enable-libzmq --enable-lto --enable-pic --enable-postproc --enable-pthreads --enable-shared --enable-vaapi --enable-vdpau --enable-vulkan --optflags=-O3 --enable-libjxl --enable-libsvtav1 --enable-libvpl libavutil 58. 2.100 / 58. 2.100 libavcodec 60. 3.100 / 60. 3.100 libavformat 60. 3.100 / 60. 3.100 libavdevice 60. 1.100 / 60. 1.100 libavfilter 9. 3.100 / 9. 3.100 libswscale 7. 1.100 / 7. 1.100 libswresample 5. 0.100 / 5. 0.100 libpostproc 57. 1.100 / 57. 1.100 Unknown input format: 'LINEAR16'

Additional information

No response

[home-assistant[bot]]

Hey there @lufton, mind taking a look at this issue as it has been labeled with an integration (google_cloud) you are listed as a code owner for? Thanks!

Code owner commands

Code owners of google_cloud can trigger bot actions by commenting:

• @home-assistant close Closes the issue.
• @home-assistant rename Awesome new title Renames the issue.
• @home-assistant reopen Reopen the issue.
• @home-assistant unassign google_cloud Removes the current integration label and assignees on the issue, add the integration domain after the command.
• @home-assistant add-label needs-more-information Add a label (needs-more-information, problem in dependency, problem in custom component) to the issue.
• @home-assistant remove-label needs-more-information Remove a label (needs-more-information, problem in dependency, problem in custom component) on the issue.

_{^{(message by CodeOwnersMention)}}

---

google_cloud documentation google_cloud source _{^{(message by IssueLinks)}}

[User873902]

This issue was circumvented by removing the encoding configuration 'linear16' from the configuration.yaml file. The default is mp3. Unclear what changed in the FFMPEG migration to 2023.12.0.

[joie96]

I've got the same issue. I doubt that this is a problem with ffmpeg, because the ffmpeg version used in the 2023.11.2 docker image of homeassistant is the same one used in the latest.

[maymaymay]

+1 here

[soundneedle]

Also had this issue and removed linear16 from config. I'm also having lots of TTS w/sonos issues after the upgrade. All my TTS automations are now broken.

[dakahler]

Related? https://github.com/home-assistant/core/pull/102814

[seanmccabe]

Chaning config from:

tts:
  - platform: google_cloud
    key_file: google_service_account.json
    voice: en-GB-Wavenet-F
    encoding: linear16

to:

tts:
  - platform: google_cloud
    key_file: google_service_account.json
    voice: en-GB-Wavenet-F

So removing the encoding line, appears to have resolved the issue.

[DrShivang]

+1 here

[0anton]

+1 I'd rather keep encoding: linear16, because it delivers better sound quality than mp3.

[issue-triage-workflows[bot]]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates. Please make sure to update to the latest Home Assistant version and check if that solves the issue. Let us know if that works for you by adding a comment 👍 This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.