FFMetrics icon indicating copy to clipboard operation
FFMetrics copied to clipboard

Failing to find ffmpeg

Open thirteenwings opened this issue 2 years ago • 22 comments

On Windows 10. Ffmpeg version 6.0 stable. Tried using 1.3.1 -- after the initial scan no ffmpeg version is shown. Program still tries to scan media files, no metadata shows. Buttons are inactive. Tried using 1,4.8 beta, it's spent 5 mins on getting ffmpeg version and is still going. In a command prompt, ffmpeg -version shows: ffmpeg version 6.0-full_build-www.gyan.dev Copyright (c) 2000-2023 the FFmpeg developers built with gcc 12.2.0 (Rev10, Built by MSYS2 project)

thirteenwings avatar Sep 07 '23 09:09 thirteenwings

Could you follow troubleshooting steps please?

fifonik avatar Sep 07 '23 09:09 fifonik

CrashDumps.zip

Program crashes when I start with -log-level=debug. First 2 dumps are 1.4.8, last 2 are 1.3.1.

thirteenwings avatar Sep 07 '23 11:09 thirteenwings

As I see, the program does not have permissions to write FFMetrics.log that should be aside of executable. Could you move the whole FFMetrics folder to a location with read/write permissions please?

fifonik avatar Sep 07 '23 12:09 fifonik

Okay, so here's what I've tried:

  1. Moved FFMetrics to a different folder with r/w permissions. This fixed the crashing and I got a logfile. However, the logfile said: 2023-09-07 22:52:18 DEBUG: Started 2023-09-07 22:52:18 DEBUG: Initialize finished 2023-09-07 22:52:18 DEBUG: .NET version detected: 480 2023-09-07 22:52:18 DEBUG: InitializeProgramConfig started 2023-09-07 22:52:18 DEBUG: InitializeProgramConfig finished 2023-09-07 22:52:18 DEBUG: InitializeWorkers started 2023-09-07 22:52:18 DEBUG: InitializeWorkers finished 2023-09-07 22:52:18 DEBUG: InitializeCommands started 2023-09-07 22:52:18 DEBUG: InitializeCommands finished 2023-09-07 22:52:18 DEBUG: FF.VersionInfoGet.Started 2023-09-07 22:52:18 ffmpeg.exe -nostdin -filters 2023-09-07 22:52:18 DEBUG: FF.ExecStatus.Started, -nostdin -filters 2023-09-07 22:52:28 DEBUG: FF.ExecStatus.Finished. stdout: , stderr: The system cannot find the file specified(-1) 2023-09-07 22:52:28 DEBUG: FF.VersionInfoGet.Finished: OK 2023-09-07 22:53:48 DEBUG: Finished

  2. I also tried moving the ffmpeg folder. Same result.

  3. When I run "ffmpeg -nostdin -filters" in a command prompt, I get an output as in attachment ffmpeg-output.txt

FFMetrics is still failing to load the ffmpeg version, the tooltip says "The system cannot find the file specified" FFMetrics.log ffmpeg-output.txt

thirteenwings avatar Sep 07 '23 17:09 thirteenwings

"The system cannot find the file specified" means exactly what it says. FFMetrics is trying to execute ffmpeg.exe without providing any path. This must work if ffmpeg.exe (and accompanied dlls if you use shared build) is located in program directory (aside of ffmetrics.exe) or in system %path%.

So:

  1. What type of ffmpeg you use -- shared (exe + dlls) or static (single exe)?
  2. Where ffmpeg.exe located -- directly in ...\FFMetrics\ dir aside of ffmetrics.exe or somewhere else?
  3. If it is located not in ...\FFMetrics\ dir, then does the ffmpeg's dir is in the %PATH%? Have you double checked it?
  4. When you moved ffmpeg folder as you mentioned, have you adjusted system %PATH%?

For simplicity I'd recommend to download static ffmpeg build and put it inside ...\FFMetrics\ dir, just aside of ffmetrics.exe

fifonik avatar Sep 07 '23 21:09 fifonik

Hi. I just woke up and had a thought while having coffee. I tried running it with admin privileges, and it's working now. I'm not sure if that's in the instructions somewhere and I missed it, but it's here now in case anyone else runs into the same issue.

thirteenwings avatar Sep 08 '23 02:09 thirteenwings

Hm. Everything should work without admin privileges and it works in my case.

fifonik avatar Sep 08 '23 08:09 fifonik