Jump to content

Version 1.3.0 Professional Released!


Recommended Posts

Hi All,

Version 1.3.0 is packed with fixes + very cool new features. 

Fixes

- TTS (Text to Speech) files that are no longer playable can now be played using the old mechanism. All you have to do is to rename the files by adding _t at the end of the file name. e.g.

hello_world.mp3 -> hello_world_t.mp3

In the majority of cases, this should work for both speaker + bluetooth.

Enhancements

- Direct TTS and translations using Google tts and Google Translate. This means that you can simply put the text in your plugin and leave the rest to the system: creating mp3 files, translating, and applying the correct logic for playback. 

To add your own TTS, simply add as many Custom Parameters as you wish. Please note that the format is pretty important:

The Key is of the format:

tts_<source language>_<destination language>_the name for your creation (it can include spaces). 

eg.

tts_en_en_hello world (source and destination languages are the same = English)
tts_en_fr_hello world in french (source language is English, destination language is French)

For a list of language codes, please see here.

The Value:

Any arbitrary text 

Future:

Yes, I know some of you don't like Google and cloud based solutions. Neither do we! So, we'll experiment with local TTS. 

With kind regards,
Michel

 

  • Like 2
Link to comment
Share on other sites

 

I did a package update and installed version 1..3.0. All is good until I try to play the file with _t added. Nothing happens.

My files are on /storage/sounds but I think it my be looking in another directory.

 

2024-03-15 19:17:00,714 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command

2024-03-15 19:17:00,715 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command

2024-03-15 19:17:00,715 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': '0', 'cmd': 'PLAY', 'query': {'PLAYLIST.uom25': '20'}} from Polyglot

2024-03-15 19:17:00,715 Command udi_interface INFO audio-player:processCommand: Got command: {'address': '0', 'cmd': 'PLAY', 'query': {'PLAYLIST.uom25': '20'}}

2024-03-15 19:17:00,715 Command udi_interface INFO audio-player:processCommand: Playing #20:/storage/sounds/HighWinds_t.mp3

2024-03-15 19:17:00,715 Command udi_interface.node DEBUG node:getDriver: 0:AudioPlayer ST - 0 :: getting dv ST

2024-03-15 19:17:00,817 Command udi_interface ERROR audio-player:processCommand: [Errno 2] No such file or directory: 'tmp_sounds/iox48.HighWinds_t.mp3'

Link to comment
Share on other sites

@garybixler,

The issue is this: we moved the temp directory to where the sound files are located. In your case, this is your /storage directory. Upon startup, the plugin tries to make a temp directory there. The plugin is running as its own user. So, I am 99.9% that your directory does not have write permissions for the node server user. 

For now, you can do:

sudo chmod -R 666 path_to_your_sounds_directory

This makes this directory accessible for everyone which is not safe. But for now, this is going to work. Once done, restart the plugin.

With kind regards,
Michel

Link to comment
Share on other sites

Log for version 1.3.0

2024-03-15 20:28:37,253 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command

2024-03-15 20:28:37,253 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command

2024-03-15 20:28:37,253 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': '0', 'cmd': 'PLAY', 'query': {'PLAYLIST.uom25': '2'}} from Polyglot

2024-03-15 20:28:37,254 Command udi_interface INFO audio-player:processCommand: Got command: {'address': '0', 'cmd': 'PLAY', 'query': {'PLAYLIST.uom25': '2'}}

2024-03-15 20:28:37,254 Command udi_interface INFO audio-player:processCommand: Playing #2:/storage/sounds/Medication.mp3

2024-03-15 20:28:37,254 Command udi_interface.node DEBUG node:getDriver: 0:AudioPlayer ST - 0 :: getting dv ST

2024-03-15 20:28:37,255 Thread-21 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV3 to 100 to Polyglot

2024-03-15 20:28:37,255 Thread-21 udi_interface.node DEBUG node:reportDriver: Updating value to 100

2024-03-15 20:28:37,255 Thread-21 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set ST to 1 to Polyglot

2024-03-15 20:28:37,255 Thread-21 udi_interface.node DEBUG node:reportDriver: Updating value to 1

2024-03-15 20:28:37,256 Thread-21 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV0 to 2 to Polyglot

2024-03-15 20:28:37,256 Thread-21 udi_interface.node DEBUG node:reportDriver: Updating value to 2

2024-03-15 20:28:37,256 Dummy-22 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set ST to 0 to Polyglot

2024-03-15 20:28:37,256 Dummy-22 udi_interface.node DEBUG node:reportDriver: Updating value to 0

2024-03-15 20:28:37,257 Dummy-22 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV0 to 0 to Polyglot

2024-03-15 20:28:37,257 Dummy-22 udi_interface.node DEBUG node:reportDriver: Updating value to 0

2024-03-15 20:28:37,259 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV3', 'value': '100', 'uom': 51, 'text': None}]}

2024-03-15 20:28:37,259 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'ST', 'value': '1', 'uom': 25, 'text': None}]}

2024-03-15 20:28:37,260 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV0', 'value': '2', 'uom': 25, 'text': None}]}

2024-03-15 20:28:37,260 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'ST', 'value': '0', 'uom': 25, 'text': None}]}

2024-03-15 20:28:37,260 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV0', 'value': '0', 'uom': 25, 'text': None}]}

2024-03-15 20:28:37,291 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV3 to 100 UOM 51

2024-03-15 20:28:37,378 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: ST to 1 UOM 25

2024-03-15 20:28:37,421 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV0 to 2 UOM 25

2024-03-15 20:28:37,478 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: ST to 0 UOM 25

2024-03-15 20:28:37,520 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV0 to 0 UOM 25

 

Link to comment
Share on other sites

Log for 1.0.5. 

 
2024-03-15 20:31:24,121 MQTT udi_interface.interface DEBUG interface:_message: QUEUING incoming message command
2024-03-15 20:31:24,121 Command udi_interface.interface DEBUG interface:_parseInput: DEQUEING command
2024-03-15 20:31:24,122 Command udi_interface.interface DEBUG interface:_handleInput: PROCESS command message {'address': '0', 'cmd': 'PLAY', 'query': {'PLAYLIST.uom25': '2'}} from Polyglot
2024-03-15 20:31:24,122 Command udi_interface INFO audio-player:processCommand: Got command: {'address': '0', 'cmd': 'PLAY', 'query': {'PLAYLIST.uom25': '2'}}
2024-03-15 20:31:24,122 Command udi_interface INFO audio-player:processCommand: Playing #2:/storage/sounds//Medication.mp3
2024-03-15 20:31:24,122 Thread-4 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set ST to 1 to Polyglot
2024-03-15 20:31:24,122 Thread-4 udi_interface.node DEBUG node:reportDriver: Updating value to 1
2024-03-15 20:31:24,123 Thread-4 udi_interface.node DEBUG node:setDriver: 0:AudioPlayer Reporting set GV0 to 2 to Polyglot
2024-03-15 20:31:24,123 Thread-4 udi_interface.node DEBUG node:reportDriver: Updating value to 2
2024-03-15 20:31:24,123 Thread-4 udi_interface ERROR udi_interface:write: Exception in thread
2024-03-15 20:31:24,123 Thread-4 udi_interface ERROR udi_interface:write: Thread-4
2024-03-15 20:31:24,123 Thread-4 udi_interface ERROR udi_interface:write: :
2024-03-15 20:31:24,123 Thread-4 udi_interface ERROR udi_interface:write: Traceback (most recent call last):
2024-03-15 20:31:24,124 Thread-4 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 980, in _bootstrap_inner
2024-03-15 20:31:24,124 Thread-4 udi_interface ERROR udi_interface:write: self.run()
2024-03-15 20:31:24,124 Thread-4 udi_interface ERROR udi_interface:write: File "/usr/local/lib/python3.9/threading.py", line 917, in run
2024-03-15 20:31:24,125 Thread-4 udi_interface ERROR udi_interface:write: self._target(*self._args, **self._kwargs)
2024-03-15 20:31:24,125 Thread-4 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_18/audio-player.py", line 43, in audio_player_thread
2024-03-15 20:31:24,125 Thread-4 udi_interface ERROR udi_interface:write: pd = AudioSegment.from_file(AudioPlayerParams.mediaPath)
2024-03-15 20:31:24,125 Thread-4 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_18/.local/lib/python3.9/site-packages/pydub/audio_segment.py", line 651, in from_file
2024-03-15 20:31:24,126 Thread-4 udi_interface ERROR udi_interface:write: file, close_file = _fd_or_path_or_tempfile(file, 'rb', tempfile=False)
2024-03-15 20:31:24,126 Thread-4 udi_interface ERROR udi_interface:write: File "/var/polyglot/pg3/ns/0021b9026038_18/.local/lib/python3.9/site-packages/pydub/utils.py", line 60, in _fd_or_path_or_tempfile
2024-03-15 20:31:24,126 Thread-4 udi_interface ERROR udi_interface:write: fd = open(fd, mode=mode)
2024-03-15 20:31:24,126 Thread-4 udi_interface ERROR udi_interface:write: PermissionError
2024-03-15 20:31:24,126 Thread-4 udi_interface ERROR udi_interface:write: :
2024-03-15 20:31:24,127 Thread-4 udi_interface ERROR udi_interface:write: [Errno 13] Permission denied: '/storage/sounds//Medication.mp3'
2024-03-15 20:31:24,131 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'ST', 'value': '1', 'uom': 25, 'text': None}]}
2024-03-15 20:31:24,131 Thread-1 udi_interface.interface DEBUG interface:_send: PUBLISHING {'set': [{'address': '0', 'driver': 'GV0', 'value': '2', 'uom': 25, 'text': None}]}
2024-03-15 20:31:24,162 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: ST to 1 UOM 25
2024-03-15 20:31:24,252 MQTT udi_interface.interface INFO interface:_message: Successfully set 0 :: GV0 to 2 UOM 25
Link to comment
Share on other sites

Mine was working with 1.2 fine.  And upgraded to 1.3 and went into continuous nodeserver restart looking for GTTS.

I upgraded packages and it got the latest UDX (was udx-3.5.5 and now udx-3.5.6)

after that things worked again. 

Just posting this in case anyone else runs into this.

  • Like 1
Link to comment
Share on other sites

My Radio streams are appearing in the "Play" Dropdown within Admin Console multiple times.  They have only been added once to the Stations key in PG3x.   Is there a way to clean up the Admin Console list.

Link to comment
Share on other sites

1 hour ago, Michel Kohanim said:

Please restart the plugin + the Admin Console.

With kind regards,
Michel

Thanks

I think restarting the Plugin did the trick, I had already restarted the console multiple times.

  • Like 1
Link to comment
Share on other sites

After installing (and re-installing) the plugin's Pro version, Current Status continues to display "Disconnected". My eisy is updated to 5.8.0 (PG3x Version 3.2.20). I have rebooted from the Admin Console, and the multi-function button with no affect. Have I missed something?

Thanks all!

Link to comment
Share on other sites

I upgraded to version 1.3.1 after doing a package update but am still having a problem with using BT. BT device is paired and when I select BT and try to stream an mp3 file it shows playing but just hangs. A restart is needed to restore functionally. No problem using speaker jacks. Also update BT plugin. I think BT had initially worked under version 1.1.0.

Log included. Thanks

Temp Log File.txt

Link to comment
Share on other sites

Hi Gary, 

I suspect you have an older BT speaker that is not actually paired. Try unpair and pair again and make sure your BT speaker gives you an indication that it's paired. Some of these devices may hold on to the socket. If that fails, it may be holding on to the socket.

With kind regards,

MIchel

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing

    • No registered users viewing this page.
  • Forum Statistics

    • Total Topics
      36.5k
    • Total Posts
      367.4k
×
×
  • Create New...