Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #4910] [BUG]: Meeting Assistant Transcription Fails #3087

New Issue
Closed
opened 2026-02-22 18:32:33 -05:00 by yindo · 8 comments
yindo commented 2026-02-22 18:32:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @dlmonroe on GitHub (Jan 27, 2026).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4910

Originally assigned to: @timothycarambat on GitHub.

How are you running AnythingLLM?

AnythingLLM desktop app

What happened?

Environment:

  • OS: Windows 10/11
  • Version: AnythingLLM Desktop (January 2026 build)
  • Engine: Meeting Assistant (Tinyscribe / parakeet-tdt-0.6b-v3.nemo)

The Problem: The Meeting Assistant fails during the transcription phase of an existing master-recording.wav. Although tinyscribe.exe initializes and the server starts on port 9090, the worker sub-process crashes when attempting to analyze the audio file.

Technical Traceback Summary:

  1. Core Error: FileNotFoundError: [WinError 2] The system cannot find the file specified
  2. Trigger Point: Occurs at audio_info = ffmpeg.get_audio_info(audio_file) within transcriber.py.
  3. Critical Packaging Errors:
    • ImportError: attempted relative import with no known parent package in cli.py.
    • ImportError: attempted relative import beyond top-level package in aio_handler.py.

Troubleshooting Already Performed:

  • Verified ffmpeg.exe and ffprobe.exe exist in the path provided in arguments: ...\storage\engines\ffmpeg\windows-x64.
  • Verified tinyscribe.exe exists and is running.
  • Added FFmpeg paths to System Environment Variables (no change).
  • Manually placed FFmpeg/FFprobe binaries inside the Tinyscribe windows-x64 and _internal folders to rule out pathing issues (no change).
  • Confirmed the master recording file exists and is accessible.

Developer Note: The logs indicate that while the main Tinyscribe server receives the --ffmpeg path correctly, the worker process spawned with sanitize_env=True is failing to find the binaries or is failing due to the relative import errors mentioned above. This suggests a potential regression in how the Windows binary is packaged or how it handles sub-process environment inheritance.

Are there known steps to reproduce?

I have not successfully completed any transcription using the Meeting Assistant. I have attempted to do it with a recorded zoom call, and I have also attempted to do it with multiple existing mp4 files.

backend-2026-01-27.log
collector-2026-01-27.log
ffmpeg-2026-01-27.log
meeting-assistant-2026-01-27.log

Originally created by @dlmonroe on GitHub (Jan 27, 2026). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/4910 Originally assigned to: @timothycarambat on GitHub. ### How are you running AnythingLLM? AnythingLLM desktop app ### What happened? Environment: - OS: Windows 10/11 - Version: AnythingLLM Desktop (January 2026 build) - Engine: Meeting Assistant (Tinyscribe / parakeet-tdt-0.6b-v3.nemo) The Problem: The Meeting Assistant fails during the transcription phase of an existing master-recording.wav. Although tinyscribe.exe initializes and the server starts on port 9090, the worker sub-process crashes when attempting to analyze the audio file. Technical Traceback Summary: 1. Core Error: FileNotFoundError: [WinError 2] The system cannot find the file specified 2. Trigger Point: Occurs at audio_info = ffmpeg.get_audio_info(audio_file) within transcriber.py. 3. Critical Packaging Errors: - ImportError: attempted relative import with no known parent package in cli.py. - ImportError: attempted relative import beyond top-level package in aio_handler.py. Troubleshooting Already Performed: - Verified ffmpeg.exe and ffprobe.exe exist in the path provided in arguments: ...\storage\engines\ffmpeg\windows-x64. - Verified tinyscribe.exe exists and is running. - Added FFmpeg paths to System Environment Variables (no change). - Manually placed FFmpeg/FFprobe binaries inside the Tinyscribe windows-x64 and _internal folders to rule out pathing issues (no change). - Confirmed the master recording file exists and is accessible. Developer Note: The logs indicate that while the main Tinyscribe server receives the --ffmpeg path correctly, the worker process spawned with sanitize_env=True is failing to find the binaries or is failing due to the relative import errors mentioned above. This suggests a potential regression in how the Windows binary is packaged or how it handles sub-process environment inheritance. ### Are there known steps to reproduce? I have not successfully completed any transcription using the Meeting Assistant. I have attempted to do it with a recorded zoom call, and I have also attempted to do it with multiple existing mp4 files. [backend-2026-01-27.log](https://github.com/user-attachments/files/24892716/backend-2026-01-27.log) [collector-2026-01-27.log](https://github.com/user-attachments/files/24892713/collector-2026-01-27.log) [ffmpeg-2026-01-27.log](https://github.com/user-attachments/files/24892714/ffmpeg-2026-01-27.log) [meeting-assistant-2026-01-27.log](https://github.com/user-attachments/files/24892715/meeting-assistant-2026-01-27.log)
yindo added the possible bugneeds info / can't replicateDesktopinvestigating labels 2026-02-22 18:32:33 -05:00
yindo closed this issue 2026-02-22 18:32:33 -05:00
yindo commented 2026-02-22 18:32:33 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 27, 2026):

Can you confirm if a file here exists?

C:\Users\david\AppData\Roaming\anythingllm-desktop\storage\engines\ffmpeg\windows-x64\ffmpeg.exe

That should be where FFMPEG is installed - if it does not exist, that is where they should be ffmpeg and ffprobe. Can you confirm if those files exist there? Moving them into the _internal will not resolve this issue.

Additionally, if you open the Program folder (right click on icon -> Open location) there should be a ffmpeg logfile

@timothycarambat commented on GitHub (Jan 27, 2026): Can you confirm if a file here exists? ``` C:\Users\david\AppData\Roaming\anythingllm-desktop\storage\engines\ffmpeg\windows-x64\ffmpeg.exe ``` That should be where FFMPEG is installed - if it does not exist, that is where they should be `ffmpeg` and `ffprobe`. Can you confirm if those files exist there? Moving them into the `_internal` will not resolve this issue. Additionally, if you open the Program folder (right click on icon -> Open location) there should be a `ffmpeg` logfile
yindo commented 2026-02-22 18:32:33 -05:00
Author
Owner
Copy Link
Copy Source

@dlmonroe commented on GitHub (Jan 27, 2026):

That is the location where ffmpeg.exe and ffprobe.exe currently are (see attached screenshot).

For the logfile, are you referring to the installation logfile? Attached here are the only two ffmpeg logfiles currently on my system (installation logfile and execution logfile).

A couple additional notes in case it helps for some context.

  1. I re-installed AnythingLLM after it initially failed, thinking that something may have broken during the installation. After re-installing, the same problem persisted.
  2. There is more than one version of ffmpeg.exe installed on my system (one installed by AnythingLLM and one installed by Faster Whisper XXL). These should not impact each other since I noticed that AnythingLLM references the exact path of the correct ffmpeg.exe, and even the system path (which is probably being ignored) points to the correct version of ffmpeg.exe.

ffmpeg_install.log

ffmpeg-2026-01-27.log

Image
@dlmonroe commented on GitHub (Jan 27, 2026): That is the location where ffmpeg.exe and ffprobe.exe currently are (see attached screenshot). For the logfile, are you referring to the installation logfile? Attached here are the only two ffmpeg logfiles currently on my system (installation logfile and execution logfile). A couple additional notes in case it helps for some context. 1. I re-installed AnythingLLM after it initially failed, thinking that something may have broken during the installation. After re-installing, the same problem persisted. 2. There is more than one version of ffmpeg.exe installed on my system (one installed by AnythingLLM and one installed by Faster Whisper XXL). These should not impact each other since I noticed that AnythingLLM references the exact path of the correct ffmpeg.exe, and even the system path (which is probably being ignored) points to the correct version of ffmpeg.exe. [ffmpeg_install.log](https://github.com/user-attachments/files/24897026/ffmpeg_install.log) [ffmpeg-2026-01-27.log](https://github.com/user-attachments/files/24897036/ffmpeg-2026-01-27.log) <img width="897" height="309" alt="Image" src="https://github.com/user-attachments/assets/3b318a76-d70a-4784-b246-befdee196005" />
yindo commented 2026-02-22 18:32:34 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 27, 2026):

Very odd, going to try on a clean Windows PC and see if I can repro this - others have yet to report it but they could be uploading files not requiring file conversion. Will return with results

@timothycarambat commented on GitHub (Jan 27, 2026): Very odd, going to try on a clean Windows PC and see if I can repro this - others have yet to report it but they could be uploading files not requiring file conversion. Will return with results
yindo commented 2026-02-22 18:32:34 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 28, 2026):

@dlmonroe I am not getting this issue on a brand new PC, nothing on it at all.

While it may take some time, do you get this issue with the CPU runtime selected as well as speaker diarization turned off?

Testing a few more combinations but i notice speaker id is on and the GPU runtime was selected (but fell back to CPU)

@timothycarambat commented on GitHub (Jan 28, 2026): @dlmonroe I am not getting this issue on a brand new PC, nothing on it at all. While it may take some time, do you get this issue with the CPU runtime selected as well as speaker diarization turned _off?_ Testing a few more combinations but i notice speaker id is on and the GPU runtime was selected (but fell back to CPU)
yindo commented 2026-02-22 18:32:34 -05:00
Author
Owner
Copy Link
Copy Source

@dlmonroe commented on GitHub (Jan 28, 2026):

I switched to CPU and turned off speaker diarization, and it failed again. I tried it with a 45-minute Zoom recording that it did, then I uploaded a 2-minute MP4 file, and both failed. I also tried it with a WAV file, and after a couple minutes it just returned to the Transcript tab as if I had never uploaded a file (same behavior as selecting the New Meeting button).

There does appear to be an issue with the GPU configuration on my installation. I have an NVIDIA A1000 GPU, and when I flipped back to GPU for the selection, it downloaded something and then had an exclamation mark on the GPU when I returned to that screen. I'll continue testing with the CPU setting and deal with the GPU situation later.

Updated logs are attached in case those help.

ffmpeg-2026-01-27.log

meeting-assistant-2026-01-27.log

backend-2026-01-27.log

@dlmonroe commented on GitHub (Jan 28, 2026): I switched to CPU and turned off speaker diarization, and it failed again. I tried it with a 45-minute Zoom recording that it did, then I uploaded a 2-minute MP4 file, and both failed. I also tried it with a WAV file, and after a couple minutes it just returned to the Transcript tab as if I had never uploaded a file (same behavior as selecting the New Meeting button). There does appear to be an issue with the GPU configuration on my installation. I have an NVIDIA A1000 GPU, and when I flipped back to GPU for the selection, it downloaded something and then had an exclamation mark on the GPU when I returned to that screen. I'll continue testing with the CPU setting and deal with the GPU situation later. Updated logs are attached in case those help. [ffmpeg-2026-01-27.log](https://github.com/user-attachments/files/24901920/ffmpeg-2026-01-27.log) [meeting-assistant-2026-01-27.log](https://github.com/user-attachments/files/24901912/meeting-assistant-2026-01-27.log) [backend-2026-01-27.log](https://github.com/user-attachments/files/24901923/backend-2026-01-27.log)
yindo commented 2026-02-22 18:32:34 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 29, 2026):

After diving into this, i think I know the issue. it is the ffmpeg resolving in the path. I think it is colliding with the one the app relies one. This is a bug and needs to be patched.

If you open the environment variable manager and temporarily remove ffmpeg from resolving in powershell and then startup anythingllm and upload a file I am willing to bet it works.

If it does I know exactly how to resolve this and can make the patch.

@timothycarambat commented on GitHub (Jan 29, 2026): After diving into this, i think I know the issue. it **is** the ffmpeg resolving in the path. I think it is colliding with the one the app relies one. This is a bug and needs to be patched. If you open the environment variable manager and temporarily remove `ffmpeg` from resolving in powershell and then startup anythingllm and upload a file I am willing to bet it works. If it does I know exactly how to resolve this and can make the patch.
yindo commented 2026-02-22 18:32:34 -05:00
Author
Owner
Copy Link
Copy Source

@dlmonroe commented on GitHub (Jan 29, 2026):

Your assumption was correct.

I removed two entries from the system path that pointed to ffmpeg installed by other apps. Once I removed those two directories from the path, AnythingLLM ran fine and was able to complete the transcriptions (including diarization).

@dlmonroe commented on GitHub (Jan 29, 2026): Your assumption was correct. I removed two entries from the system path that pointed to ffmpeg installed by other apps. Once I removed those two directories from the path, AnythingLLM ran fine and was able to complete the transcriptions (including diarization).
yindo commented 2026-02-22 18:32:34 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jan 29, 2026):

Okay, bug confirmed then! Will patch for next release (should auto-update on install).

Thanks for the help and your patience

@timothycarambat commented on GitHub (Jan 29, 2026): Okay, bug confirmed then! Will patch for next release (should auto-update on install). Thanks for the help and your patience
yindo changed title from [BUG]: Meeting Assistant Transcription Fails to [GH-ISSUE #4910] [BUG]: Meeting Assistant Transcription Fails 2026-06-05 14:50:14 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label Desktop investigating needs info / can't replicate possible bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#3087
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?