# Stuck with playing a file - TTS, MP3, omxplayer, vlc

**URL:** <https://discourse.nodered.org/t/stuck-with-playing-a-file-tts-mp3-omxplayer-vlc/89366>\
**Category:** General\
**Created:** [9 July 2024 09:07 UTC](https://discourse.nodered.org/t/stuck-with-playing-a-file-tts-mp3-omxplayer-vlc/89366 "2024-07-09T09:07:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 July 2024 09:07 UTC](https://discourse.nodered.org/t/stuck-with-playing-a-file-tts-mp3-omxplayer-vlc/89366/1 "2024-07-09T09:07:21Z")

</div>

Folks,

I'm stuck - yet again.

Scenario:  
Headless RPI  
I use google TTS but only recently discovered a _problem_ with this.  
If there is no uplink, the _message_ won't be translated, so won't be able to be played.

Solution:  
Make a message which says what I want to hear (no uplink available) and find the `.mp3 file` and play it instead.

Found. renamed to something user friendly and moved.

Let's say it says: _Uplink not available_

ssh into machine and I use `omxplayer` to play `.mp3 files`.  
`omxplayer uplinkDown.mp3` and it plays fine.  
~~I hear **ALL** the message.~~  
No, sorry, I hear _uplkink not avail_

Likewise with the exec node  
_uplink not avail_

I have VLC but it has its own set of problems with the the `exec` node.  
NOTHING is played.

Suggestions?

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [9 July 2024 09:52 UTC](https://discourse.nodered.org/t/stuck-with-playing-a-file-tts-mp3-omxplayer-vlc/89366/2 "2024-07-09T09:52:48Z")

</div>

Sorry Andrew, not quite clear what the ask is here. Sounds like you've managed to work around the issue with a local file to play? So what else is needed? Is it that you want that played in the connected users browser?

---

<div class="post-metadata">

**Author:** ![Trying\_to\_learn](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/trying_to_learn/32/28400_2.png) [@Trying\_to\_learn](https://discourse.nodered.org/u/Trying_to_learn)\
**Post date:** [9 July 2024 09:56 UTC](https://discourse.nodered.org/t/stuck-with-playing-a-file-tts-mp3-omxplayer-vlc/89366/3 "2024-07-09T09:56:24Z")

</div>

Well,

the `mp3` file is the full message.

If I use VLC to play it, I hear it clearly/completely.  
Using VLC it works/plays back 100%.

But _weirdly_ if I use `omxplayer` I hear only 90% of it.

So the messages is _uplink not available_  
(Drats, I can't share the file)

I have since found a _better_ one which says _uplink off line_ and it plays completely.

I'm just confused what is going on with `omxplayer` (yeah, sorry, off topic) but it plays all other _sound files_ ok.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [9 July 2024 10:11 UTC](https://discourse.nodered.org/t/stuck-with-playing-a-file-tts-mp3-omxplayer-vlc/89366/4 "2024-07-09T10:11:20Z")

</div>

> [@Trying\_to\_learn](#):
>
> I'm just confused what is going on with `omxplayer` (yeah, sorry, off topic) but it plays all other _sound files_ ok.

No worries. Sound output on Linux has always been a dark art to me. 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex026/uploads/nodered/original/1X/d073cd938eafa2e558d7c2cd59003b3ef4963033.png) [@system](https://discourse.nodered.org/u/system)\
**Post date:** [23 July 2024 10:11 UTC](https://discourse.nodered.org/t/stuck-with-playing-a-file-tts-mp3-omxplayer-vlc/89366/5 "2024-07-23T10:11:47Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.