Bug: crashed and didn't transcribe

[FAElite]

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": "C:\\Users\\furqa\\OneDrive - University Of Houston\\Documents\\2024-09-23 15-23-37.wav",
  "lang": "en",
  "verbose": false,
  "n_threads": 6,
  "init_prompt": "",
  "temperature": 0.4,
  "translate": null,
  "max_text_ctx": null,
  "word_timestamps": false,
  "max_sentence_len": 1
}

Caused by:
    no segements found!

Location:
    core\src\transcribe.rs:292:13
App Version: vibe 2.5.2
Commit Hash: 7780d6fa971ef096a21e4ec84dc3330172f8a241
Arch: x86_64
Platform: windows
Kernel Version: 10.0.22621
OS: windows
OS Version: 10.0.22621
Cuda Version: n/a
Models: ggml-medium.bin
Default Model: "C:\\Users\\furqa\\AppData\\Local\\github.com.thewh1teagle.vibe\\ggml-medium.bin"
Cargo features: vulkan


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

[aManWhoIsNobody]

Hi, I had the same bug (first time that I've tried this app) and I managed to resolve it? or bypassed it, idk. Anyway, I noticed some weirdness when I selected the GPU (my laptop has a 2070 super max-q) with number 1 it kept crashing, so I tried with the igpu (hd630 I believe, it's a 10th gen intel) and it worked. I tried to select again the dgpu and it literally started changing numbers, like 7 or even -4. So I thought that maybe it was some kind of software related issue. I disabled nvidia optimus from the bios and it worked, first try, it's also really fast, @thewh1teagle made a fantastic job with this project. Hope that this comment can be helpful

[FAElite]

I only have a igpu (Intel Iris Xe), and it says 0 for me. However, I did remember changing it or something else so it could have crashed because of that. And I selected the high graphics performance cause it sounds better? I'm going to test it out again today with it turned on and off and hopefully it works.

…

On Tue, Sep 24, 2024 at 11:35 AM aManWhoIsNobody ***@***.***> wrote: Hi, I had the same bug (first time that I've tried this app) and I managed to resolve it? or bypassed it, idk. Anyway, I noticed some weirdness when I selected the GPU (my laptop has a 2070 super max-q) with number 1 it kept crashing, so I tried with the igpu (hd630 I believe, it's a 10th gen intel) and it worked. I tried to select again the dgpu and it literally started changing numbers, like 7 or even -4. So I thought that maybe it was some kind of software related issue. I disabled nvidia optimus from the bios and it worked, first try, it's also really fast, @thewh1teagle <https://github.com/thewh1teagle> made a fantastic job with this project. Hope that this comment can be helpful — Reply to this email directly, view it on GitHub <#292 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A33SXYQ6NXFA7HOCT3TVHMLZYGIDRAVCNFSM6AAAAABOW2VJQSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZRG44DGNJQGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[thewh1teagle]

#370