Video is not converted into specified file-format

[VanillaChief]

Bug Information

Bug Description

When attempting to convert a video file using HandBrake Web, the application fails to convert the file to the specified format. I expect the file to be saved in the chosen video format, but the output remains unchanged, as if the conversion settings were ignored. I am not sure if I set it up wrong or something is actually not working right. Please advise.

Bug Steps

1. Import Preset, which specifies that the file should be converted to mp4
2. Watcher set up with this preset finds a .mkv files
3. After conversion, the output is still mkv
4. When using the preset with Handbrake Desktop, it works like expected

Additional Information

Application Information

HandBrake Web Version

• v0.7.1

Docker Compose

services:
  handbrake-server:
    image: ghcr.io/thenickoftime/handbrake-web-server:latest
    container_name: handbrake-web-server
    user: 1000:1000 # edit to run as user (uuid:guid) with permissions to access your media. 0:0 to run as root (not recommended).
    ports:
      - 8994:9999
    volumes:
      - ./data:/data
      - ./media:/video # ensure this path is the same across all containers
      - ./output:/output

  handbrake-worker:
    image: ghcr.io/thenickoftime/handbrake-web-worker:latest
    container_name: handbrake-web-worker
    user: 1000:1000 # edit to run as user (uuid:guid) with permissions to access your media. 0:0 to run as root (not recommended).
    environment:
      - WORKER_ID=handbrake-worker # give your worker a unique name
      - SERVER_URL=xxx.xxx.xxx.xx # change if setting up a standalone worker, prefix with http(s):// if necessary
      - SERVER_PORT=8994 # change if using a reverse proxy or the port is otherwise different than above
    volumes:
      - ./media:/video # ensure this path is the same across all containers
      - ./output:/output
    depends_on:
      - handbrake-server

Host Machine

• OS: Debian 12
• CPU: i7-8700T

[TheNickOfTime]

Sorry for the late response, I've been slammed with work lately. Could you provide some log output from the worker handling this? It should hopefully reveal what is going on here. You should be able to download the log for the failed job from the queue interface:

If that isn't available for some reason, you can access worker logs from the the data/log directory of your mounted data path

[eltiel]

I have the same problem.

Log attached: worker1-job-5.log

[TheNickOfTime]

Thank you for the log! I'll take a look to see what's going on. I'll prioritize this fix and push it in a v0.7.2 patch version - hopefully by the end of this weekend. Development is attached to issue #248.

[TheNickOfTime]

I had some time today to fix the issue, and have published the fix with release v0.7.2. Just pull the latest docker images and you guys should be good to go!

[KucharczykL]

Hi, I have only started using handbrake-web after 0.7.2 was released (and checked that I am indeed running 0.7.2) but I am also having this issue.

[TheNickOfTime]

Could you drop a log as mentioned above? Probably another edge case where this can occur.

[KucharczykL]

Here's the log:

handbrake-worker-devilfish-job-23.log

[eltiel]

Hi, I have only started using handbrake-web after 0.7.2 was released (and checked that I am indeed running 0.7.2) but I am also having this issue.

Same here. In 0.7.2 didn't fix the issue it seems

[TheNickOfTime]

Thanks for the logs and reports, will look back into this, thank you for your patience!

[TheNickOfTime]

Just to clarify, the issue that you are still experiencing is that the file output is not using the file extension that is specified in your preset?

There is a bit of a conflict in the way that the CLI handles extensions vs the desktop version of handbrake - the CLI uses the extension specified in your output path, whereas the desktop version of HandBrake will use what is stored in the preset. Currently this application ignores what is in the preset, and uses what is manually specified when creating a job.

[eltiel]

Just to clarify, the issue that you are still experiencing is that the file output is not using the file extension that is specified in your preset?

Yes

There is a bit of a conflict in the way that the CLI handles extensions vs the desktop version of handbrake - the CLI uses the extension specified in your output path, whereas the desktop version of HandBrake will use what is stored in the preset. Currently this application ignores what is in the preset, and uses what is manually specified when creating a job.

I use watchers instead of manually creating a job, so I don't get to specify the extension.

[TheNickOfTime]

Cool - must have forgotten to add the extension select to the watcher creation process. I'll push a 0.7.3 release soon that allows you to specify the extension for watchers (#257). Then, for v0.8 I will make it so a preset's extension is respected first, then you can override it if desired (#258).

[KucharczykL]

Ah, that's right, I did forgot to mention I also use a watcher. Makes sense now. Thanks for looking into it!

[TheNickOfTime]

I just published v0.7.3 that should fix this issue well enough for now! Essentially watchers will use whatever extension is defined in their preset for the time being. I will be reworking how output extensions are handled for v0.8.0.

[KucharczykL]

I updated and converted one video and the problem seems to be fixed. Thanks! 👍