[EN] FAQ
What should I do if I installed the extension, but it says "Failed to request video translation"? Or why do I need the cloudflare version of the extension?
Tip
This answer is relevant if you are a user of Violetmonkey, FireMonkey, GreaseMonkey, AdGuard, OrangeMonkey, UserScripts and some specific browsers. It will also be relevant for users with blocked Yandex servers.
A Cloudflare version of the extension was created for this case. Thanks to her, all requests go through a special vot-worker.
- Check that the loader (Tampermonkey, etc.) and the extension itself are enabled
- Check that Tampermonkey does not ask you to enable Developer mode
- Check the console for errors
- Still not working? Create an Issue and describe in detail all the steps for playback, as well as do not forget to add console logs
When activating the translation, it says "The audio format is not supported" ("Формат аудио не поддерживается")
There may be several possible solutions to solve this problem:
-
Enable the addition of extensions to the CSP policy via Tampermonkey
1.1. Enable the "Advanced" configuration mode in Tampermonkey
1.2. In the "Add TM to CSP" list, set the value to "Yes"
1.3. Click on the "Save" button
1.4. Reload the video page
-
If your Yandex servers are blocked, then install Cloudflare version of the extension and enable audio proxying in the settings.
-
Check, that the site where you are translating does not require additional actions in the form of a complete shutdown of CSP.
No. Due to the fact that Yandex needs access to the video for translation, you cannot translate a local video unless you upload it to some video hosting service.
No. Voice acting takes place on Yandex servers and cannot be influenced in any way.
Warning
Don't forget to check that there hasn't been such an offer yet.
You can write all your ideas about the extension in Issues.
A special console utility VOT-CLI has been created for this purpose
How to use the extension with FireMonkey?
- Install the FireMonkey extension
Installation
- Copy all the code from vot.user.js
Correct code copying
- Go to the FireMonkey settings (click on the extension icon -> Options)
- Go to the "Scripts and Styles" tab and add a new script
Adding a script
4.1. Go to the "Scripts and Styles" tab
4.2. Click on the button to create a new script
4.3. Insert the script code
- Add the rule
// @inject-into pagebefore the line starting with// @grant ...
Adding a rule
5.1. Find the line starting with // @grant ..., in our example it is // @grant GM_addStyle
5.2. Add the rule // @inject-into page before the found line
- Save the script using the combination "Ctrl + S" or using the "Save" button
How to use the extension with User JS and CSS?
- Install the User JS and CSS extension
Installation
- Copy all the code from vot-cloudflare.user.js
Correct code copying
- Create a new rule and paste the copied code
Creating a new rule
3.1. Click create a new rule
3.2. We write the name of the rule - VOT Cloudflare
3.3. We set the URL pattern according to which the rule will work. The screenshot uses the https://*/* pattern to work on all sites, if this does not suit you, you can manually specify all the necessary sites separated by commas from lines starting with // @match, for example: *://*.youtube.com /*, *://*.youtube-nocookie.com /*
Example of a string starting with "// @match"
3.4. Paste the copied code
3.5. Click "Save" on the top right
- Create external modules for all scripts starting with `// @require'. Don't forget to add a polyfile for GM_info.
Creating external modules
Example of a string starting with "// @require"
Here,
The highlighted fragment is a link to the library.
The name of the library is Protobuf min.
4.1. Click on the "External modules" tab on the left
4.2. Click on the "Add new" button
4.3. Enter the name of the library (usually it is clear by the name of the file at the end of the link) and the link to the library itself
4.4. Click on the "Add" button
- Note: Sometimes adding works crookedly and duplicates an existing script. Reloading the page will help fix this.
This must be done with all libraries from lines starting with //@require
4.5. Do not forget to add the "GM_info Polyfill" library, otherwise the extension will not work:
https://gist.githubusercontent.com/ilyhalight/94313e32c9e5efa791de82306c390d5f/raw/5d6b12792fdac55260afcaa393772b3103c4a500/gm-info-polyfill.js
An example of all the necessary libraries for the extension version 1.5.3.1
| No. | Name | Link |
|---|---|---|
| 1 | Protobuf Min | https://cdn.jsdelivr.net/npm/protobufjs/dist/light/protobuf.min.js |
| 2 | HLS Light | https://cdn.jsdelivr.net/npm/hls.js/dist/hls.light.min.js |
| 3 | GM_addStyle polyfill | https://gist.githubusercontent.com/ilyhalight/6eb5bb4dffc7ca9e3c57d6933e2452f3/raw/7ab38af2228d0bed13912e503bc8a9ee4b11828d/gm-addstyle-polyfill.js |
| 4 | GM_info polyfill | https://gist.githubusercontent.com/ilyhalight/94313e32c9e5efa791de82306c390d5f/raw/5d6b12792fdac55260afcaa393772b3103c4a500/gm-info-polyfill.js |
- Enable the added modules for the VOT rule
Enabling modules
- It's done. When updating the script, you will only need to update the rule code and download external modules (the "Download again" button appears when you click edit on the desired module).
Tip
You may only need your vot-worker for the Cloudflare version of the extension
To deploy your vot-worker, we recommend that you familiarize yourself with the vot-worker repository. Detailed instructions are described in the corresponding folder inside the worker repository.
To change the worker's domain, open the extension menu on any site and enter the vot-worker address at the very bottom.