thewh1teagle / vibe

Transcribe on your own!

Home Page:https://thewh1teagle.github.io/vibe/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Bug: ffmpeg not found

oboythefirst opened this issue · comments

What happened?

A bug happened!

Steps to reproduce

  1. step one...
  2. step two...

What OS are you seeing the problem on?

No response

Relevant log output

options: {
  "path": "D:\\Downloads\\Ieuan Jones Bible Intro.m4a",
  "model_path": "C:\\Users\\Administrator\\AppData\\Local\\github.com.thewh1teagle.vibe\\ggml-medium.bin",
  "lang": "en",
  "verbose": false,
  "n_threads": 4,
  "init_prompt": "",
  "temperature": 0.4,
  "translate": null,
  "max_text_ctx": null
}

Caused by:
    ffmpeg not found

Location:
    core\src\audio.rs:54:42
App Version: 2.0.3
Commit Hash: 6c5ace63edd36807905fd906c26ec34fab1325ea
Arch: x86_64
Platform: windows
Kernel Version: 10.0.19045
OS: windows
OS Version: 10.0.19045
Models: ggml-medium.bin
Default Model: "C:\\Users\\Administrator\\AppData\\Local\\github.com.thewh1teagle.vibe\\ggml-medium.bin"


{
    "avx": {
        "enabled": true,
        "support": true
    },
    "avx2": {
        "enabled": true,
        "support": true
    },
    "f16c": {
        "enabled": true,
        "support": true
    },
    "fma": {
        "enabled": true,
        "support": true
    }
}

Thank you for reporting this issue!

Could you please check if you installed the NVIDIA version? I think I may have missed bundling ffmpeg in the latest update.

How do I check if it's the NVIDIA version? Bitdefender found and quarantined Gen:Variant.Lazy.540663 from ffmpeg.exe when I installed Vibe, so it looks like the ffmpeg was not installed. Can I add ffmpeg another way? Thanks,Stephen On Tuesday, June 11, 2024 at 01:35:45 PM EDT, thewh1teagle @.> wrote: Thank you for reporting this issue! Could you please check if you installed the NVIDIA version? I think I may have missed bundling ffmpeg in the latest update. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.>

You can open vibe folder in the path %localappdata%\vibe (paste this in explorer.exe in the top bar)
If it contains some DLL files which named like cuda it's nvidia, if not it's regular. also the folder size should be small if it's not nvidia.
Also when you open the folder check if ffmpeg.exe is there.
Try to reinstall vibe, looks like Windows defender deleted the file ffmpeg.exe when you installed it. if you can screenshot when it report it, and also provide here the exact URL you downloaded vibe from, I will be able to report it to Microsoft so they will stop blocking it.

Thanks :)

I downloaded ffmpeg, and copied the exe over to the Vibe folder. Vibe is now working, and even though I've just started, it looks like it's doing a great job. I've got an old tape of a Welsh teacher with his sing-songy voice that's been converted to an m4a file, and it looks like Vibe is getting everything. I've got some Chinese stuff that needs transcribed, so I'll check that out later. Thanks for this. Stephen

If you have macOS or an NVIDIA GPU, you can transcribe audio incredibly quickly, processing up to 2 hours of content in just a few minutes. I'm glad to hear everything is working well for you and that you're enjoying it so far!

Do you have a PayPal account so I don't have to fill out all my info on github? Stephen

I appreciate your willingness to support the project! While I don't have a PayPal account, you can easily support the project on Ko-fi without needing to sign up or fill in details. Just follow this link: Ko-fi.

Thanks a lot for supporting vibe!