Transferring to a new server

[TheDreadPirate]

You can't do that. Upgrading is a one way street. Lots and lots of database changes.

You'd either have to start over or restore from a 10.8.11 backup.

For transcoding, whether this is the official image or a 3rd party image, you need to configure Docker to pass the GPU into the container.

https://jellyfin.org/docs/general/admini...ualization

[Celvin238]

Ok!

I wanted to install the current version of JellyFin (10.10.1) manually (Container Manager, create project...) and integrated the commands to map the iGPU.
(renderD128...)

The installation went smoothly and I was able to transfer all metadata by copying the “cache” and “config” folders from the original container. :-)

However, when I start JellyFin and activate hardware acceleration in the menue "Transcoding", the following error message appears when playing videos:
"Playback has failed due to a fatal player error."

My settings for hardware acceleration are:
- Intel QuickSync
- Enable hardware decoding for all codecs except AV1
- Hardware encoding options: Enable hardware encoding: yes, Enable Intel low-power hardware encoder for H.264: no, Enable Intel low-power hardware encoder for HEVC: yes
- Encoding format options: Allow encoding in HEVC format: yes, Allow encoding in AV1 format: no
- Enable VPP tone mapping: no
- Enable tone mapping: no
All of the following options: no, except “Allow parallel extraction of subtitles”

When I install and configure version 10.8.11 in exactly the same way, no error message appears and the hardware acceleration works fine (I can see this in the log files).

Maybe you know what the problem could be?

[Efficient_Good_5784]

Could you share the ffmpeg logs of the failed stream?
Maybe it will help point to your issue.

Please use a site like pastebin.com

[TheDreadPirate]

Disable both low power encoding options. That requires additional firmware that, AFAIK, can't be installed on DSM. It is optional anyway. Regardless, IIRC Gemini Lake only supports H264 low power encoding anyway.

[Celvin238]

Hi TheDreadPirate,

I really can't understand but at the moment it works just fine...

But the error message shows up, wenn I enable Intel low-power hardware encoder for H.264 (beside: there is no problem, when I enable Intel low-power hardware encoder for HEVC, maybe because the CPU does not support that option).

Thank you so much for your steady support!!!

[Efficient_Good_5784]

Hi TheDreadPirate,

I really can't understand but at the moment it works just fine...

But the error message shows up, wenn I enable Intel low-power hardware encoder for H.264 (beside: there is no problem, when I enable Intel low-power hardware encoder for HEVC, maybe because the CPU does not support that option).

Thank you so much for your steady support!!!

Most likely the issue will happen when you face a transcode.
If the video you play doesn't need to (direct play), having that option enabled will not matter.

It's best to disable both low-power options unless you go through the trouble of installing the data it needs to actually run on your system.

[Celvin238]

I was too hasty: The error is back... :-(

It has reappeared since I took over the “config” and “cache” folders from my original system (without mapping for iGPU).

When I restore the folders it works fine again.

Could it be that by replacing the “config” folder, the setting for mapping the iGPU is lost?

[TheDreadPirate]

We'd need to see full jellyfin and ffmpeg logs.

[Celvin238]

Thanks for your help, but I'll stop here.

Now I have a system that runs flawlessly but doesn't have my metadata and a system that has no hardware acceleration but has my metadata... ;-)

I'll use the second one as best I can because I've invested two days editing the metadata.

Maybe 10.11.0 brings a practical backup function!