#6904 Application started at 2026-08-27 11:27:55 [DEBUG] 上次缓存的角色:No,字幕嵌入类型:1,发音语言:英语,目标语言:简体中文,目标语言代码:zh-cn,模型:large-v3,TTS渠道[

203.10.**4 Posted at: 2 hours ago


Application started at 2026-08-27 11:27:55

[DEBUG] 上次缓存的角色:No,字幕嵌入类型:1,发音语言:英语,目标语言:简体中文,目标语言代码:zh-cn,模型:large-v3,TTS渠道[0]
[DEBUG] NVIDIA_GPU_NUMS=1
[DEBUG] Found 1 GPUs, cost=2s
[DEBUG] process_max_gpu=1,is_multi_gpus=False
[DEBUG] Concurrent task_nums=1, process_max_cpu=0
[DEBUG] start 9 jobs
[DEBUG] 返回缓存的编解码器 Windows-264: h264_nvenc
[DEBUG] 返回缓存的编解码器 Windows-265: hevc_nvenc
[WARNING] 无法连接 huggingface.co, 使用镜像替换: hf-mirror.com
HTTPSConnectionPool(host='huggingface.co', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(, 'Connection to huggingface.co timed out. (connect timeout=3)'))

Logging error

Traceback (most recent call last):
File "urllib3\connection.py", line 198, in _new_conn
File "urllib3\util\connection.py", line 85, in create_connection
File "urllib3\util\connection.py", line 73, in create_connection
TimeoutError: timed out

The above exception was the direct cause of the following exception:

Traceback
......
ption:

Traceback (most recent call last):
File "requests\adapters.py", line 644, in send
File "urllib3\connectionpool.py", line 841, in urlopen
File "urllib3\util\retry.py", line 519, in increment
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='huggingface.co', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(, 'Connection to huggingface.co timed out. (connect timeout=3)'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "videotrans\util\help_down.py", line 34, in is_connect_hf
File "requests\api.py", line 100, in head
File "requests\api.py", line 59, in request
File "requests\sessions.py", line 589, in request
File "requests\sessions.py", line 703, in send
File "requests\adapters.py", line 665, in send
requests.exceptions.ConnectTimeout: HTTPSConnectionPool(host='huggingface.co', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(, 'Connection to huggingface.co timed out. (connect timeout=3)'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "logging\__init__.py", line 1103, in emit
AttributeError: 'NoneType' object has no attribute 'write'
Call stack:
File "videotrans\task\simple_runnable_qt.py", line 14, in run
File "videotrans\util\help_down.py", line 36, in is_connect_hf
File "logging\__init__.py", line 1489, in warning
File "logging\__init__.py", line 1624, in _log
File "logging\__init__.py", line 1634, in handle
File "logging\__init__.py", line 1696, in callHandlers
File "logging\__init__.py", line 968, in handle
File "logging\__init__.py", line 1108, in emit
Message: "无法连接 huggingface.co, 使用镜像替换: hf-mirror.com\nHTTPSConnectionPool(host='huggingface.co', port=443): Max retries exceeded with url: / (Caused by ConnectTimeoutError(, 'Connection to huggingface.co timed out. (connect timeout=3)'))"
Arguments: ()

7 Replies

#1 DeepSeek reply at 2 hours ago

日志核心问题:无法连接 huggingface.co,软件已自动切换至国内镜像站 hf-mirror.com 作为替代下载源。 这在国内网络环境下是完全正常的机制,不需要手动干预。

日志末尾的 AttributeError: 'NoneType' object has no attribute 'write' 是日志系统写入异常,不影响主程序运行,通常可忽略。

具体说明

  1. 软件启动时会先测试能否连通 huggingface.co(超时3秒)。由于国内网络默认无法直连,连接超时后软件自动将模型下载源替换为 hf-mirror.com,这是内置的容错行为。
  2. 后续模型下载将走镜像源,一般可正常完成。如果自动下载仍失败,建议参考手动下载模型的方法,将模型文件手动放置到 软件目录/models/ 对应路径下。

需要您注意

  • 如果任务后续提示“模型下载失败”或相关模型文件缺失,说明镜像源也不稳定或网络被代理干扰。可尝试:

    1. 检查主界面“对齐控制”行的代理文本框是否填写了有效代理,若无需代理请清空。
    2. 参照手动下载模型页面,手动下载对应模型并放入 models/ 目录。

请查阅相关文档:

#2 203.10.**4 reply at 2 hours ago

这是今天的日志 我还没开始任务 有没有什么问题

#3 DeepSeek reply at 2 hours ago

日志显示的主要是启动时自动测试连通性失败,并已切换到国内镜像源 hf-mirror.com,这是软件内置的正常容错机制,不会影响后续任务执行。末尾的 AttributeError: 'NoneType' object has no attribute 'write' 是日志系统写入时的小异常,不影响主程序运行,可忽略。

您可以正常开始任务。如果后续提示模型下载失败或模型文件缺失,再按以下方法处理:

  1. 检查主界面“对齐控制”行的代理文本框,若无必要请清空;
  2. 参照 手动下载模型 页面,将模型手动放入 软件目录/models/ 对应位置。

请查阅相关文档:

#4 203.10.**4 reply at 1 hour ago

合并与输出阶段卡住 是否正常

#5 DeepSeek reply at 1 hour ago

合并与输出阶段(最终合成)对于长视频或高分辨率视频,处理时间较长是正常的,尤其是以下情况:

  1. 勾选了「视频慢速」——会触发重新编码,速度明显变慢。
  2. 勾选了「嵌入硬字幕」或「硬字幕(双语)」——同样需要重新编码,耗时增加。
  3. 高级选项中将「输出视频压缩率」设为较慢编码(如 slowveryslow),或「视频输出质量控制」设得过低(如接近0),也会显著延长合成时间。

但如果长时间完全无进度、CPU/GPU占用率为0%,则可能是卡死。

请按以下步骤排查:

  1. 打开软件安装目录下的 logs/ 文件夹,查看当天的最新日志文件(例如 20260827.log),复制最后30行报错信息。
  2. 检查任务过程中CPU/GPU是否有活动——如果一直无活动,说明进程可能已经挂起,尝试点击「终止任务」并重启软件。
  3. 确认视频文件路径是否包含中文、空格或特殊符号——若有,请移至纯英文目录并重命名。
  4. 如果确实卡死,可在高级选项「视频输出控制」中勾选「强制软编码视频?」,避免硬件编码器冲突。

若日志中无明确错误,且上述排查后仍卡住,请提供最新日志内容,以便进一步判断。

请查阅相关文档:

#6 203.10.**4 reply at 1 hour ago

[DEBUG] 开始语音识别:渠道0
[DEBUG] [新进程任务 开始:STT use large-v3]
[DEBUG] 任务参数:kwargs={'detect_language': 'en', 'model_name': 'large-v3', 'logs_file': 'D:/pyvideotrans/tmp/6160/2b16658002/faster-en-1787801438.7721088.log', 'is_cuda': True, 'no_speech_threshold': 0.6, 'condition_on_previous_text': False, 'speech_timestamps': None, 'audio_file': 'D:/pyvideotrans/tmp/6160/2b16658002/en.wav', 'local_dir': 'D:/pyvideotrans/models/models--Systran--faster-whisper-large-v3', 'compute_type': 'default', 'jianfan': False, 'audio_duration': 8153003, 'hotwords': None, 'prompt': '', 'beam_size': 5, 'best_of': 5, 'temperature': '', 'repetition_penalty': 1.0, 'compression_ratio_threshold': 2.4, 'max_speech_ms': 5000, 'device_index': 0}
[DEBUG] GPU进程池:max_workers=1
[DEBUG] [faster_whisper]加载模型:当前 is_cuda=True,_compute_type='default'
[DEBUG] faster-whisper模式下,对large-v3模型返回的断句结果重新修正
[DEBUG] 断句结果重新修正完毕
[DEBUG] 返回识别结果
[DEBUG] [新进程任务 结束:STT use large-v3],耗时1282.5130660
......
:[self.ainame='deepseek',self.model_name='deepseek-v4-pro',self.api_url='https://api.deepseek.com/v1/',self.reasoning_effort=None]
[INFO] Starting call to 'videotrans.translator._openaicompat.OpenAICampat._item_task', this is the 1st time calling it.
[DEBUG] 字幕翻译:[self.ainame='deepseek',self.model_name='deepseek-v4-pro',self.api_url='https://api.deepseek.com/v1/',self.reasoning_effort=None]
[INFO] Starting call to 'videotrans.translator._openaicompat.OpenAICampat._item_task', this is the 1st time calling it.
[DEBUG] 字幕翻译:[self.ainame='deepseek',self.model_name='deepseek-v4-pro',self.api_url='https://api.deepseek.com/v1/',self.reasoning_effort=None]
[INFO] Starting call to 'videotrans.translator._openaicompat.OpenAICampat._item_task', this is the 1st time calling it.
[DEBUG] 字幕翻译:[self.ainame='deepseek',self.model_name='deepseek-v4-pro',self.api_url='https://api.deepseek.com/v1/',self.reasoning_effort=None]
[INFO] Starting call to 'videotrans.translator._openaicompat.OpenAICampat._item_task', this is the 1st time calling it.
[DEBUG] 字幕翻译:[self.ainame='deepseek',self.model_name='deepseek-v4-pro',self.api_url='https://api.deepseek.com/v1/',self.reasoning_effort=None]
[INFO] Starting call to 'videotrans.translator._openaicompat.OpenAICampat._item_task', this is the 1st time calling it.
[DEBUG] 字幕翻译:[self.ainame='deepseek',self.model_name='deepseek-v4-pro',self.api_url='https://api.deepseek.com/v1/',self.reasoning_effort=None]
[DEBUG] 以SRT格式翻译,原始字幕行数:2883,翻译后行数:2883
[DEBUG] 原始语言字幕和目标语言字幕行数一致,均为 source_len=2883

[DEBUG] 跳过二次识别
[DEBUG]


==准备要嵌入的字幕:self.cfg.subtitle_type=1
=
[DEBUG] 最终确定字幕嵌入类型:1 ,目标字幕语言:zho, 字幕文件:D:/pyvideotrans/tmp/6160/2b16658002/end.srt

[DEBUG] [set_ass_font] 未修改硬字幕样式,跳过样式替换
[DEBUG] [FFMPEG-CMD]:
ffmpeg -hide_banner -nostdin -ignore_unknown -threads 0 -y -i novoice.mp4 -vf tpad=stop_mode=clone:stop_duration=1.094 -c:v libx264 -crf 23 -preset medium -an final_video_with_freeze_lastend.mp4

#7 DeepSeek reply at 1 hour ago

日志显示任务已成功进入最终合成阶段,正在执行 ffmpeg 命令将无声视频、配音和字幕合并为最终视频。当前命令使用 libx264 软编码、crf 23preset medium,并且通过 tpad 在视频末尾克隆一帧以延长画面(用于对齐配音时长)。这是正常的处理流程,对于长视频或高分辨率视频,重新编码耗时较长,容易让人误以为卡住。

判断是否真卡住的方法:

  1. 观察任务管理器中的 CPU 占用率——若 ffmpeg 进程在活动(CPU 占用明显),说明正在处理,耐心等待即可。
  2. 若 CPU 占用率长期为 0%,且日志无任何新输出,则可能进程死锁,点击「终止任务」并重启软件。
  3. 若多次重启后仍然卡住,可在 高级选项 → 视频输出控制 中勾选「强制软编码视频?」以避免硬件编码器冲突,或适当调大「视频输出质量控制」(CRF 值)降低编码压力。

日志中无报错信息,且字幕翻译行数一致(2883行)、二次识别已跳过,一切符合预期。建议先等待一段时间再观察。

请查阅相关文档:

Thinking...
Post Your Reply
If you have more than 50 messages, you will no longer receive an automatic reply. Please ask a new question!
Open source and free maintenance is not easy. If this project is helpful to you, please consider making a small donation to help the project continue to maintain and update.

Dondate via ko-fi.com

Related resource