pyVideoTrans

Appearance

Table of Contents

  1. Login
  2. Create an API KEY
  3. Using it in Video Translation Software

0. Login and Get Free Credits ​

If you don't have an account, you need to register first. Email and phone number registration are supported.

Login/Registration address: https://gpt302.saaslink.net/teRK8Y

1. Create an API KEY ​

After logging in, you will see the following interface. Click API Supermarket -> API Management on the left side.

Enter a name in the API Name field on the right, and then click Add API at the bottom. The API KEY creation is complete. It's that simple.

Scroll down, and you will see the created API list. Click the eye icon to display the complete API KEY. Copy it for later use.

Which models can be used?

You can see the API List on the left. Click to view all model series. There are a total of 6 series, with dozens of models in total.

You can use the entire OpenAI model series, including ChatGPT-3, ChatGPT-3.5, ChatGPT-4, ChatGPT-4o, etc.

And OpenAI's main competitor, the claude-3 series of models.

Google's Gemini-1.5 series is also available.

Domestic models such as Wenxin Yiyan, Tongyi Qianwen, iFlytek Xinghuo, Tsinghua ZhiPu, Baichuan Intelligence, Yue Zhi Anmian, ShenDu QiuSuo are also supported.

It almost covers all the mainstream models, eliminating the need to connect to them one by one. Just one API KEY grants access to all.

3. How to Use the API KEY in Video Translation Software ​

  • First, upgrade the video translation software to 2.10+
  • Then click the top-left settings - 302.ai translation integration
  • Fill in the API KEY you just created
  • Select the model you want to use

That's it! Go to the main interface, select 302.ai in the translation channel, and start using it.

Not only the translation channel can use 302.ai, but the dubbing channel can also. Click top-left - settings - 302.ai dubbing integration, fill in the API KEY, select the model you want to use, and select 302.ai in the main interface dubbing channel. Done.

Why are there two separate configuration windows? Why not combine translation and dubbing into one?

Because dubbing models are generally different from translation models and need to be specified separately. Currently, 302.ai dubbing models only support openai's tts-1/tts-1-hd models, but Azure AI TTS dubbing will be supported soon. Separating them into two windows facilitates the addition of Azure TTS later.

Video translation software open-source address: https://github.com/jianchang512/pyvideotrans

302.ai Website

Help Center: https://help.302.ai/