solution for hardware transcode issue in synology with emby 4.8.8.0

[pdbear 0]

hi admin,

I found emby 4.8.8.0 hardware transcoding failed with this key words:
```bash

Could not write header for output file #0 (incorrect codec parameters ?): No such file or directory
Error initializing output stream 0:0 --

```

when i create the dest directory on my hands, the transcoding works fine.

pls check the tanscode procedure，ffmpeg need create des path first。

 

like:

```bash

/var/packages/EmbyServer/target/bin/ffmpeg -loglevel +timing -y -print_graphs_file "/var/packages/EmbyServer/var/logs/ffmpeg-transcode-20054eb9-0f59-4360-a8b0-a23543f915df_1graph.txt" -copyts -start_at_zero -init_hw_device "cuda=cuda:0" -f matroska,webm -c:v:0 h264 -threads:v:0 1 -hwaccel:v:0 cuda -hwaccel_output_format:v:0 cuda -noautorotate -c:v:1 mjpeg -i "/volume2/PT/电影/[大话西游之月光宝盒.星光联盟].A.Chinese.Odyssey.Part.One.Pandora's.Box.1995.SUBBED.WEB-DL.4K.H264.50FPS.AAC.Cantonese-OPS.mkv" -filter_complex "[0:0]scale_cuda@f1=w=640:h=360,setsar@f2=sar=sar[f2_out0]" -map [f2_out0] -map 0:1 -sn -c:v:0 h264_nvenc -b:v:0 808001 -g:v:0 150 -maxrate:v:0 808001 -bufsize:v:0 1616002 -keyint_min:v:0 150 -r:v:0 50 -profile:v:0 high -c:a:0 copy -metadata:s:a:0 language=chs -disposition:a:0 default -max_delay 5000000 -avoid_negative_ts disabled -f segment -map_metadata -1 -map_chapters -1 -segment_format mpegts -segment_list "/volume2/docker/emby_server/transcoding-temp/731266/731266.m3u8" -segment_list_type m3u8 -segment_time 00:00:03.000 -segment_start_number 0 -individual_header_trailer 0 -write_header_trailer 0 -segment_write_temp 1 "/volume2/docker/emby_server/transcoding-temp/731266/731266_%d.ts"

```

the dest dir `/volume2/docker/emby_server/transcoding-temp/731266/` must created by emby but emby not do, especial this 731266 tmp directory.so ffmpeg report error. pls create the dest dir before start ffmpeg.

[pdbear 0]

@Luke

[pdbear 0]

sorry，i install a wrong source spk，officail package not have this issue。 @Luke

[Luke 42077]

What spk did you install?

[MarkBear 3]

@LukeI have a suspicion the cause of this (and similar issues i’ve seen on the forums) may be the linuxserver.io docker image.

Until moments ago, we were using this image on our linux homelab and were facing this issue. pdbear’s comment (no relation; ha) led me to wonder if it was the image, and swapping to the official image fixed the problem for us - we got 5 episodes of a show to play faultlessly first time.

Something perhaps permissions related happening in the linuxserver.io base image perhaps.

[Luke 42077]

1 hour ago, MarkBear said:

@LukeI have a suspicion the cause of this (and similar issues i’ve seen on the forums) may be the linuxserver.io docker image.

Until moments ago, we were using this image on our linux homelab and were facing this issue. pdbear’s comment (no relation; ha) led me to wonder if it was the image, and swapping to the official image fixed the problem for us - we got 5 episodes of a show to play faultlessly first time.

Something perhaps permissions related happening in the linuxserver.io base image perhaps.

Hi, that's interesting. Thanks for the feedback.