Giter Club home page Giter Club logo

edgetx-sdcard-sounds's Introduction

EdgeTX - Voice packs

This repository contains the files needed to generate the voice packages used in EdgeTX.

The currently supported languages are:

  • Chinese Mandarin
  • Chinese Taiwan Mandarin
  • Chinese Hongkong Cantonese
  • Chilean Spanish
  • Czech
  • Danish
  • English
  • French
  • German
  • Italian
  • Japanese
  • Portuguese
  • Russian
  • Spanish
  • Swedish
  • Ukrainian

The following languages are not yet supported:

  • Dutch
  • Hungarian
  • Slovak

Directory structure

SOUNDS

This folder has the audio files already processed and separated by language.

To use them, the language folder (for example, en) must be under the SOUNDS folder of your SDCARD. With the folder added, go to the EdgeTX settings menu and select the language of the audio language that will be used (eg English).

To use any audio on your switches, first copy the file you want to use to your language folder, then you can use this file in your Global Functions or Special Functions by selecting a switch for the function and choosing the Play track option.

SCRIPTS

Inside the language folder there is a folder called SCRIPTS, which has audio files for commonly used LUA scripts. These audio files are generated with the same voice as the other audio files of their language pack. Each script has their own folder.

BETAFLIGHT

Audio files for Betaflight TX Lua Scripts. Copy the WAV files from SOUNDS/<lang>/SCRIPTS/BETAFLIGHT/ to SOUNDS/en/ to overwrite the original audio files of the script.

INAV

Audio files for iNav Lua Telemetry Flight Status. Copy the WAV files from SOUNDS/<lang>/SCRIPTS/INAV/ to SCRIPTS/TELEMETRY/iNav/<lang>/ to overwrite the original audio files of the script.

YAAPU

Audio files for Yaapu Telemetry Script and Widget. Copy the WAV files from SOUNDS/<lang>/SCRIPTS/YAAPU/ to SOUNDS/yaapu0/<lang>/ to overwrite the original audio files of the script.

Voices

All of the voices used in the EdgeTX voice packs have been picked from the neural voices offered by Microsoft Azure text to speech service, in order to get as close as possible to human-like voices. If you want to see what voices are available, and try different phrases, check out the online demo generator. Using some recording software, you could even save your own phrases and use them in the voice packs.

Generating custom phrases

If you have a Azure Speech Services subscription (there is a free usage tier), phrases can be generated with curl or a http client like postman. After building a text to speech resource in Azure you can use it by REST calls (http requests).

The request url is: https://<YOUR_RESOURCE_REGION>.tts.speech.microsoft.com/cognitiveservices/v1

You should add the following headers to your request:

Ocp-Apim-Subscription-Key: <YOUR_RESOURCE_KEY>
Content-Type: application/ssml+xml
X-Microsoft-OutputFormat: riff-8khz-16bit-mono-pcm

Note: EdgeTX supports up to 32khz .wav file but in that range 8khz is the highest value supported by the conversion service. However, it is possible to select higher quality like riff-48khz-16bit-mono-pcm and convert to 32khz afterwards with another tool (i.e. ffmpeg -i input.wav -ar 32000 output.wav) if you want the best possible audio quality.

And in the request body (raw) place your ssml (change the voice name according to your preference, the full list is here):

<speak version='1.0' xml:lang='en-US'>
    <voice xml:lang='en-US' xml:gender='Female' name='en-US-MichelleNeural'>YOUR_PHRASE_HERE</voice>
</speak>

How to build yourself

In order to generate the voice packages and do the release processing, you will need a Linux environment to run in. Ubuntu 18.04 is recommended as it is a LTS release. Newer versions and other flavours of Linux will most likely work also, but are not supported.

You will also need to have ffmpeg, spx and ffmpeg-normalize packages installed.

ffmpeg is used to clip any silence from the audio files. ffmpeg-normalise is used to normalise the audio files. spx is the tool that generates the audio files using Microsoft Azure Text to Speech processing.

Installing SPX can be a little tricky, but can be installed as follows:

wget https://packages.microsoft.com/config/ubuntu/20.04/packages-microsoft-prod.deb -O packages-microsoft-prod.deb
sudo dpkg -i packages-microsoft-prod.deb
sudo apt-get update; \
  sudo apt-get install -y apt-transport-https && \
  sudo apt-get update && \
  sudo apt-get install -y dotnet-sdk-6.0

dotnet tool install --global Microsoft.CognitiveServices.Speech.CLI

After you have installed SPX, you will also need to create a Microsoft Azure account if you don't have one already. There are both free and paid options, but the free one is sufficient for this purpose - it is just rate limited. After you have done that, follow the quick start guide to configure the required region and subscription keys.

Alternatives

Contributing

See CONTRIBUTING.md

edgetx-sdcard-sounds's People

Contributors

daleckystepan avatar dosclic98 avatar dr-gandalf avatar edernucci avatar forceu avatar frankiearzu avatar gonzalo-bulnes avatar howels avatar hthuren avatar microraptor avatar pfeerick avatar robertod91 avatar shezinger avatar sumolx avatar theisotopes avatar toshihiromakuuchi avatar ujenmr avatar ulfhedlund avatar zandorsp avatar zyren avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar

edgetx-sdcard-sounds's Issues

Add more words/phrases

  • SAFE on
  • SAFE off
  • timer 1 reset
  • timer 2 reset
  • timer 3 reset
  • expo 1
  • expo 2
  • expo 3

Check for

  • Launch Mode
  • Loiter
  • Return to Launch

de: long silent phase after spoken text

en: about 0.15s silence after spoken text
de: about 0.8s silence after spoken text - this makes german SF play value veeerrrryyy sloooowwww

A played value of 23.7 Volt will take about 2-3 seconds for en, but about 6-7 seconds for de. Please adjust the silent phase accordingly.

Here's a comparison of the en/0023.wav vs de/0023.wav:

image

Include sounds.json as a release asset

The file in the code directory reflects the pre-release build and not necessarily Latest or older releases.
This makes automating the installation of releases more challenging such as when using the sounds.json file for displaying available language packs for older releases. Then if chosen pack does not exist handling the error situation.

request sounds for Camera Control

I have a Runcam Thumb Pro which supports connection to a flight controller to start & stop recording video via Betaflight's support of the Runcam protocol to control cameras. There are flight modes available in Betaflight to start recording, configure the camera, or enable WiFi on a camera (the thumb doesn't have WiFi but I believe others do.)

Request sounds to say things like:
"camera power button" or "camera/video/recording start/begin"

"camera change mode"
image

Catalan Languaje

I'd like to use Catalan languaje in my TX16S. Meanwhile I have saved with my voice some sounds and changed them in 'es' sound folder and system ( not all changed an some else added ).
How can I implement 'ca' languaje in EdgeTX ?
Catalan is one of the 4 oficial languajes in Spain ( Castillian/Spanish, Catalan, Vasque and Galaic ) and has about 10 million of users in the world ( Also ANDORRA ).
Thanks in advance
voices.zip
.

release builder should strip `v` from version tag

Version tags have the v present, but it seems like from past releases this hasn't been included in the filename. Until I've ascertained the collateral damage to Buddy and Companion that would result from leaving this, release.sh should strip it out.

German voice pack not correctly

According to the de-DE.csv file, 205 system and 26 other files are listed.
but in the zip file there are two files too many in the system folder, engon.wav and fm-9.wav, they don't belong there.

can someone please check that.

a couple of sound requests

a sound for Betaflight's Acro Trainer flight mode

Blackbox erase Betaflight mode. I have a 3-state switch that I have do nothing when it's up, then mid it's set to enable blackbox & when it's all the way down it erases the Blackbox.

feat: Adding car phrases for four wheel steering modes

Four wheel steering is a popular option for rock crawlers. With a steering servo on the front and rear of the vehicle, you can have 4 different options for steering modes (sometimes called different names). I cover this setup in a video if you are curious on the application of it:
https://www.youtube.com/watch?v=qEAxVIe_x5I

My request is to add the following phrases/suggested file names:
str-f.wav - "Front Steer"
str-r.wav - "Rear Steer"
str-4w.wav - "Four Wheel Steer"
str-mr.wav - "Mirror Steer"
str-cr.wav - "Crab Steer"

Release action

Github action needs to upload differently for release and latest builds - as they are named differently

Standardization of all the sound packs about String IDs and names

After browsing the sound files, because of implementing the sounds to certain switches, I realised, that we don't have the same sound files in every language directory. Also I noticed, that the String IDs aren't the same for the sounds in every language. For better implementation I think it would be useful to standardise each String ID to one sound / word / phrase.
Then we can start to make the sound files for each language with the same files and not only half of them available in some language packs.
Also the name of each wave file should be standardized. See the example below for that.
The best starting point would be to use the english_GB csv file as the main, checking if other languages maybe have additional sounds and adding the missing there.
Discussing here, how to name the files and then using this for every other csv file.

Two examples about what I mean about different IDs and also different naming of the wav files

The number 100

English
100 = 0100.wav -> ID 101
German
hundert = 0101.wav -> ID 103

The word AND

English
and = 0110.wav -> ID 111
German
und = 0105.wav -> ID 106
French
et = 0120.wav -> ID 121

Also I can understand, that different languages have things which maybe can not translate directly to each other, because of the different gramma and use etc.
So as a suggestion, we could use String ID 0-999 for the general things implemented for every language.
And special things für each languages like this,
1000-1999 Czech
2000-2999 German
...
Every future implemented language can be added after that.

Documentation

Would you mind please mention what is the default EN voice you use, so when we add phrases at the online demo we can use the same one?
Can you provide SSML we can edit to generate a whole new package easily?

Son Belges

Serait-il possible de générer les sons suivants pour la Belgique et la Suisse ? Merci d'avance

.../fr/SYSTEM/
0070.wav --> Septante
0071.wav --> Septante et un
0072.wav --> Septante deux
0073.wav --> Septante trois
0074.wav --> Septante quatre
0075.wav --> Septante cinq
0076.wav --> Septante six
0077.wav --> Septante sept
0078.wav --> Septante huit
0079.wav --> Septante neuf

0090.wav --> Nonante
0091.wav --> Nonante et un
0092.wav --> Nonante deux
0093.wav --> Nonante trois
0094.wav --> Nonante quatre
0095.wav --> Nonante cinq
0096.wav --> Nonante six
0097.wav --> Nonante sept
0098.wav --> Nonante huit
0099.wav --> Nonante neuf

Additional surface phrases.

Hello again!

I’ve been making a phrase wish list while using my radio, and I have some more phrase suggestions.

They are:

“Drift Mode Enabled”
“Drift Mode Disabled” (I know there are ones that sound similar, more on that in a sec)
“Screenshot”
“Cell” (for including in prompts about cell voltage)
“Transmitter Battery Low”
“Left”
“Right”
“Shift”
“Stability Control On”
“Stability Control Off”
“Stability Control Enabled”
“Stability Control Disabled”
“Thermal Warning” (“thermal” and “warning” already exist, so it would be there just to make the trigger sequence for the phrase simpler)

Now, as I’ve been selecting phrases, I’ve noticed something interesting: some phrases have an On/Off end, and some have Enabled/Disabled or even Active instead (see phrases like “course hold…” or “rescue mode…”. So I’ve added some phrases like “drift mode enabled/disabled” to pair well with other lines like “wet mode enabled/disabled”

in the future it’s probably something to look out for, to ensure integrated, smooth phrase transitions.

Malformed sounds.json in release 2.5.3 assets

Qt cannot convert to a json document as it needs to have the comma after the last entry removed (see below)
{
"language": "zh-CN",
"name": "Chinese Female",
"description": "Chinese Female Voice",
"directory": "cn"
}, <<<<<<<------------ THIS ONE
]

Note: Latest Voice Pack and Preliminary 2.7.0 are okay

Documentation enhancement

Please add a paragraph for custom phrases.

For custom phrases there is no need for ubuntu or different installations. Phrases can be generated with curl or http client like postman.
After building a text to speech resource in Azure you can use it by REST calls (http requests).
The request url is:
https://<YOUR_RESOURCE_REGION>.tts.speech.microsoft.com/cognitiveservices/v1
You should add the following headers to your request: (EdgeTX supposed to support up to 32khz .wav file but in that range 8khz is the highest value supported by the conversion service. It's possible to select higher quality like riff-48khz-16bit-mono-pcm and convert to 32khz afterwards with another tool like ffmpeg).

Ocp-Apim-Subscription-Key: <YOUR_RESOURCE_KEY>
Content-Type: application/ssml+xml
X-Microsoft-OutputFormat: riff-8khz-16bit-mono-pcm

And in the request body (raw) place your ssml (Change the voice name according to your preference, the full list is: tts.speech.microsoft.com/cognitiveservices/voices/list):

<speak version='1.0' xml:lang='en-US'>
    <voice xml:lang='en-US' xml:gender='Female' name='en-US-MichelleNeural'>YOUR_PHRASE_HERE</voice>
</speak>

Generally speaking, the implementation in voice-gen.py can be a series of http requests without the proxy objects. I don't see any benefit if they require ton of installations, but I might be wrong here. I'll be happy to hear if they contribute somehow.
It seems that it can be an os independent implementation.

Default Azure Voice for English?

I got the Azure Speech CLI set up on my machine to generate some custom sounds and dink around with the internal sounds. I was generating some GB and US English and non of the female voices seem like the one used in the sound pack. What is the default method and voice used for generating english? Thanks!

Copy the same audio files as OTX to maintain migration compatibility

Should have the following files:

  • acro.wav
  • armed.wav
  • crowof.wav
  • crowon.wav
  • disarm.wav
  • engoff.wav
  • flapdn.wav
  • flapup.wav
  • fm-1.wav
  • fm-2.wav
  • fm-3.wav
  • fm-4.wav
  • fm-5.wav
  • fm-6.wav
  • fm-7.wav
  • fm-8.wav
  • fm-acr.wav
  • fm-ang.wav
  • fm-crs.wav
  • fm-flt.wav
  • fm-fst.wav
  • fm-hor.wav
  • fm-id1.wav
  • fm-id2.wav
  • fm-lch.wav
  • fm-lnd.wav
  • fm-nrm.wav
  • fm-png.wav
  • fm-pwr.wav
  • fm-rce.wav
  • fm-spd.wav
  • fm-stb.wav
  • fm-thl.wav
  • fm-thm.wav
  • fm-thr.wav
  • geardn.wav
  • gearup.wav
  • lnding.wav
  • lowbat.wav
  • lq.wav
  • nrmmod.wav
  • rathi.wav
  • ratlow.wav
  • ratmed.wav
  • rfmode.wav
  • sigcrt.wav
  • siglow.wav
  • spdmod.wav
  • splrdn.wav
  • splrup.wav
  • thmmod.wav
  • thract.wav
  • thrcut.wav
  • tohigh.wav
  • tolow.wav
  • trnoff.wav
  • trnon.wav
  • vrioff.wav
  • vrion.wav

Finish translating additional words/phrases added

The following phrases/words need to be translated into

  • cn / Chinese @//zyren Can you help with this?
  • cz / Czech
  • de / German @//rotorman Can you help with this?
  • es / Spanish
  • fr / French @//raphaelcoeffic Can you help with this?
  • it / Italian
  • pt / Portuguese
  • ru / Russian

I'm trying https://www.deepl.com to see how it goes with the initial translation. And as brainbubblersbest pointed out, context for most of this is iNAV modes, as well as some video transmitter stuff such as OSD and pit mode. https://github.com/iNavFlight/inav/blob/master/docs/INAV_Modes.pdf

    manmod.wav;manual mode
    acrmod.wav;acro mode
    angmod.wav;angle mode
    hznmod.wav;horizon mode
    lncmod.wav;launch mode
    airmod.wav;air mode
    pitmod.wav;pit mode
    navcrs.wav;navigation cruise
    navcsh.wav;navigation course hold
    navalh.wav;navigation altitude hold
    navpos.wav;navigation position hold
    navrth.wav;navigation return to home
    navwp.wav;navigation waypoint
    cruise.wav;cruise
    crshld.wav;course hold
    althld.wav;altitude hold
    poshld.wav;position hold
    rth.wav;return to home
    waypnt.wav;waypoint
    manual.wav;manual
    auto.wav;auto
    osd.wav;O S D
    osdprf.wav;O S D profile

missing phrases

i just realised the edgetx-sdcard-sounds/voices/es-ES.csv is missing many phrases.
And why there are two columns, "source text" and "translation", but both are in spanish?
I can translate to spanish, but i am pretty new to github and this code :P

English voice changed - no longer clear and harder to distinguish

I flashed my radio using the Flasher tool but found that when I switched on the radio it was mumbling to me. The voice sounds like a breathy/soft anime voice and is very hard to make out words as the consonants are very soft. It's almost a whispering style of intonation and really hard to make out words.

Can we please revert to the original EdgeTX style of English voice? Radios don't have good speakers and I need to be able to distinguish the words easily.

Developer docs: a few questions to get started contributing to this repository (engineering, with first-hand localization experience)

Hi @pfeerick (and everybody else who can answers these questions!)

I'm interested in contributing some thinking and tooling to this repository.
I see opportunities to reduce duplication, automate further and make the job easier for people interested in providing or correcting sounds in their own language (including by contributing translation docs). But I'd like to make sure I understand how this repo relates to the other EdgeTX projects before making the wrong assumptions.

Can I check my understanding of the goals with you?

  1. This repository releases include:

    • one archive per language-locale-voice, with the contents of the /SOUNDS/<language code> directory of the EdgeTX SD Card.
    • one sounds.json file
    • some other archives that don't follow a strict naming pattern, but also expand to the /SOUNDS/<some language code> directory of the EdgeTX SD Card.
  2. Who consumes sounds.json? I don't see it used in the SD Card, is it retrieved from the releases page by Companion or Buddy?

  3. Regarding locales and voices: my understanding is that EdgeTX is not currently aware of the locale and voice, only the language.
    By that I mean: I can place the contents of the en_GB-Libby archive in my SD Card's /SOUNDS/en directory and the contents of es_CL-Catalina in /SOUNDS/es. That will allow me to switch the voice language from English to Spanish from the radio settings, but I can't have en_US-Ryan at the same time, unless I hack my way around (e.g. my placing the contents of the archive in /SOUNDS/de and selecting German. Is my understanding correct?

  4. The files in /SOUNDS/SYSTEM are directly referenced by EdgeTX code, and as such are required for a language pack to be complete. But the files directly at the root of /SOUNDS are not, and can be considered optional. Is that true?

  5. Similarly, the files in /SOUNDS/INAV are required for the INAV language pack to be complete, but the script does not rely on any file outside of that directory. Is that also true? (Or SHOULD it be? I understand that depends in part on what the maintainers of the INAV and other scripts do.)

  6. Companion and Buddy rely on the GitHub Releases page directly to retrieve language packs and information about them, so the content of the Assets section of each release can be thought of as the interface of this repository with Companion and Buddy. Is that correct? (I'm half-guessing here.)

  7. There MUST be an archive named edgetx-sdcard-sounds-<language code>-<edgetx version>.zip for each of the supported languages for Companion and Buddy to function as expected. But the archives that follow a different naming pattern (e.g. edgetx-sdcard-sounds-es_cl-catalina-2.9.0.zip) are only meant to be downloaded by individuals who visit the Releases page. Is that correct? (Again, I'm guessing here.)

  8. If you've got pointers to the EdgeTX code that loads or consumes the content of the /SOUNDS directory, I'd welcome them! In particular, I'm interested in understanding if / how the first column (ID) of the CSV files is currently used (or not used - see also #48 (comment)).

Request: new wav file for "level mode"

Hello,
We have wav files for "acro mode", "horizon mode", "normal mode", but there is no wav file for "level mode" which is often used by newbie quad pilots and is one of the flight modes available in BetaFlight (although BetaFlight calls it "angle mode", and there is a wav file for "angle mode").
Please, would it be possible to add a new wav file for "level mode", which is more descriptive than "angle mode" ?
Thank you very much!

Add issue templates

Overview

I'm thinking of adding some issue templates in order to make it as easy as possible for folks to:

  1. report sounds that "say the wrong things" (e.g. pit mode / modo foso in Spanish - is roughly equivalent to saying "moat mode" en English, it just makes no sense unless you know that a pit and a moat are kinda similar in a context that's not remote-controlled aircraft.)
  2. report sounds that "don't sound right" (e.g. es-CL transcribes hertz as jertz for phonetic purposes, even if the word in written hertz in Spanish, that's sometimes necessary depending on what voice is used by the TTS service. More on that below.)
  3. request new locales to be supported (e.g. #62)
  4. request new voices to be supported (why not?)
  5. Other (a default template)

"says the wrong thing"

It seems like providing voice packs in different locales can make EdgeTX more accessible to more people.

Relying on machine translations allows to provide some meaningful level of support to non-English speakers, but good translations require both language and EdgeTX proficiency.

So there will be some mediocre translations in the voice packs that receive less attention (see 👍 in #17 despite "mode fosse" in fr-FR and "modo foso" in es-ES which are wrong.)

Review mistakes will happen, and not all sounds will make sense to all reviewers every time and that should be okay. I think we can make the trade-off relying on unreliable machine translations acceptable by making sure that reporting errors is easy, so they get fixed over time.

"doesn't sound right"

Sometimes terms that we use are jargon that a general-purpose text-to-speech service may not render correctly. The current pipeline allows the text to be adjusted in order to compensate for that, and it's an easy thing to fix, assuming that someone reported it.

I hope that having a template to report those issues will help lowering the amount of effort folks need to put into contributing to making the voice packs better in their own language.

new locale please

That one seems obvious. If there are no voice packs for your locale, and adding them is not too hard / costly, it should be easy to request them. 🙂

new voice please

There are different voices for some of the locales already (e.g. en_US), so I suppose that's something that people request from time to time.

default template

Of course, providing issue templates fro some common requests / problems shouldn't prevent anyone from reporting the other ones.

Couple new phrases and QOL words

Hey EdgeTX team! I have some more sound requests today.

“Servo Overload”
“BEC Overload”
“Stability Control - Standard” (if possible I think a slightly longer pause in between Control and Standard would help show the purpose of the phrase)

“Stability Control”
“Gyro” (which will probably come out as gyroscope…)
“Low”
“Medium”
“High”
“Standard”
(for combining with other words)

Once these are added, (if possible, obviously) I’ll help review them.

Wrong hello.wav phrase in RU voice pack

Russian neuro voice dont prounences EdgeTX word correct. Its sounds like Edjix. For correct prounences by neuro voice need use phrase "Добро пожаловать в Эдж Ти Экс" insted of "Добро пожаловать в EdgeTX".

EN: some strange wav's

English language en: ms0.wav, ms1.wav, ml0.wav and ml1.wav with strange pronunciation

milliseconds is missing an l in milli:
SOUNDS/en/SYSTEM;ms0.wav;milisecond
SOUNDS/en/SYSTEM;ms1.wav;miliseconds

millliters is pronounced wrong

trainer on/off is very unclear

Most voices seem to make contract these words into "traineroff" and "traineron" where you can't tell the difference. Adding a , should solve the issue.

Please change these to "trainer, on" and "trainer, off". This might be useful in other places as well.

French sound pack

Hello,

It is not the highest priority but,
In the french sound pack the hello.wav file says "bienvenu sur OpenTX" (=> "welcome to OpenTX") instead of ""bienvenu sur EdgeTX".

General information

  • EdgeTX version 2.5.0
  • Sound Pack version : 2.5.4 ( fr)
  • Hardware : Radiomaster TX16S

Bad French sounds

Is there an existing issue for this problem?

  • I have searched the existing issues

What part of EdgeTX is the focus of this bug?

Transmitter firmware

Current Behavior

Bad translated sounds, example: 0010.was return two hundred and not one hundred and one.

Expected Behavior

I have found that the from from 00101.wav to 00189.wav have a bad translated sound.

Steps To Reproduce

play sound are bad

Version

2.9.4

Transmitter

RadioMaster TX16S / TX16SMK2

Operating System (OS)

Windows

OS Version

w11

Anything else?

No response

Yaapu "Fly by wire a flight mode" mispronounciation

The Yaapu "Fly by wire a flight mode" message (flybywirea.wav) is pronounced as if the "a" is part of "wire", rather than being pronounced separately as a letter. "Fly by wire b flight mode" is pronounced correctly. Perhaps capitalizing A or some other minor change would get the TTS to produce the correct result.

build_release action - deprecated node12

.github/workflows/build_release.yml

Uses marvinpinto/action-automatic-releases which is dependent on node12, which is now depreciated. Need to swap it out for another upload/release action. It is also responsible the two set-output warnings, which will also stop working soon.

Some new words for surface models.

Hi all! I would like to see some new English sounds for surface models added. Some I can think of right away include:

"drift mode on"
"drift mode off"
"gyro enabled"
"gyro disabled"
"launch control active"
"wet mode enabled"
"normal mode"
"max gyro"
"max assistance"
"overheating"
"boost mode"

If these sounds are released I'll verify the sound quality and pronunciation on my MT12.

Missing phrase

I'm watching RCVR channel on YouTube where he's setting up FM1-FM3 to play two phrases each.
I don't know which voice pack he has, but he has a Sport Mode (sprtmd) phrase which I don't see on my SD (I do have the Sport phrase).
So, I checked GitHub and also don't see the sprtmd phrase under the EN folder.

I know Bardwell, on his channel, was saying there were a lot of phrases he had to record in order to create his voice pack. Is there an official list so I can check for other missing phrases? Might as well find out now so the keeper of phrases can commit them to the repository.

Sound normalization

There is a huge difference in the gain of the OTX voice versus the one generated.

Another VTX sound pack

I am going to make another sound pack related to VTX and LED settings. Just to be clear no spacing for acronym based sounds.

Example:
VTX Frequency R1
VTX Frequency R2
VTX Frequency R3
VTX Frequency R4
VTX Frequency R5
VTX Frequency R6
VTX Frequency R7
VTX Frequency L1
Etc....

LEDS Red
LEDS Green
LEDS Blue
LEDS Cyan
LEDS Yellow
LEDS White
LEDS Orange
LEDS Violet
LEDS Magenta
LEDS Off

I just want to be sure this will be OK before starting this effort. I tested both real quick and sounded good. It's too bad we can't combine multiple sounds together.

Directory for Swedish sound pack should be /se, not /sv

Someone on a social media page was having problems with the error "No data files" when attempting to change their TX16S to the Swedish language. He posted pictures where he was attempting to create a Special Function. I downloaded a couple of language packs to experiment. They all worked except for Swedish. I successfully tried German /de, French /fr and of course, my native language English /en. When I tried the Swedish language pack /sv, I got the same error message. I searched for the correct DISO Country Code for Sweden and it it is SE, not SV. I renamed the directory on my SD card from /sounds/sv to /sounds/se and it worked! I am now able to switch between English, German, French and Swedish on my radio.

I request that you rename the Swedish sound pack in the repository from edgetx-sdcard-sounds-sv-2.8.0.zip to edgetx-sdcard-sounds-se-2.8.0.zip and make the corresponding changes to the file itself so it extracts into a correctly named directory.

Thanks for all your wonderful work on this project! People do appreciate what you are accomplishing!

Add language/locale: En_Ireland

Description

I'd like to be able to CREATE A voice pack in the following language(s) and locale(s): English in an Irish accent.

This is not a request to use AI to generate a new dialect, but to get help on how my wife, who is Irish, can record a voice pack of the correct format. She does some voiceover work and has good clear enunciation in a fairly neutral Dublin accent.

Thanks!

  • en_IRL

Help make EdgeTX better!

  • (optional) I can help reviewing the translations.
  • (optional) I can help reviewing the sounds once they're generated.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.