2025-02-23, 10:09 AM
Hi,
last week I installed Jellyfi on a Mini PC Gigabyte GB-BSi5A-6200 running Windows 11 Pro with an USB 8TB SSD. Installation and setup went smooth. For transcoding I am using hardware acceleration with the builtin Intel HD520.
It is not the fastest, but normally there is no problem running transcoding. I have more than 1000 TV recordings in all kind of formats (mp4, ts, ..). They work fine an all tested platforms (Windows, Android, ...), except for the TS recordings. After converting them 1:1 to MKV they play fine on Android.
So thanks to the authors of Jellyfi. You have done a great job!
Now I have started to put some DVD iso files on the Jellyfi server and discovered some problems, especially with Android Jellyfi Client.
I attach an example with DVD "DISCLOSURE", which seems to crash Jellyfi. The playback starts with very poor video quality with non-readable text, and pauses from time to time, and then finally stops. It seems to be that hardware transcoding does not work and high cpu usage cause the poor encoding quality. Even after ending playback the cpu usage was high, and I had to reboot the system.
One reason may also have been that I configured a transcoding buffer of 10 s only, because this worked fine for all the TV recording. After setting back the buffer to 120 s, the crash didn't happen again. But, I report this with the attachments to give some input for a future bug fix. A fix is not urgent.
After the buffer fix the playback quality on Android is still bad and slow, but ffmpeg reports that HW acceleration is in use:
> [AVHWDeviceContext @ 0000020a96610ec0] Using device 8086:1916 (Intel® HD Graphics 520).
On Windows the DVD plays fine, except that the residual video length is reported wrong. It seems to stuck with the "FBI warning" message.
Thanks for your help!
Best
Emil
last week I installed Jellyfi on a Mini PC Gigabyte GB-BSi5A-6200 running Windows 11 Pro with an USB 8TB SSD. Installation and setup went smooth. For transcoding I am using hardware acceleration with the builtin Intel HD520.
It is not the fastest, but normally there is no problem running transcoding. I have more than 1000 TV recordings in all kind of formats (mp4, ts, ..). They work fine an all tested platforms (Windows, Android, ...), except for the TS recordings. After converting them 1:1 to MKV they play fine on Android.
So thanks to the authors of Jellyfi. You have done a great job!
Now I have started to put some DVD iso files on the Jellyfi server and discovered some problems, especially with Android Jellyfi Client.
I attach an example with DVD "DISCLOSURE", which seems to crash Jellyfi. The playback starts with very poor video quality with non-readable text, and pauses from time to time, and then finally stops. It seems to be that hardware transcoding does not work and high cpu usage cause the poor encoding quality. Even after ending playback the cpu usage was high, and I had to reboot the system.
One reason may also have been that I configured a transcoding buffer of 10 s only, because this worked fine for all the TV recording. After setting back the buffer to 120 s, the crash didn't happen again. But, I report this with the attachments to give some input for a future bug fix. A fix is not urgent.
After the buffer fix the playback quality on Android is still bad and slow, but ffmpeg reports that HW acceleration is in use:
> [AVHWDeviceContext @ 0000020a96610ec0] Using device 8086:1916 (Intel® HD Graphics 520).
On Windows the DVD plays fine, except that the residual video length is reported wrong. It seems to stuck with the "FBI warning" message.
Thanks for your help!
Best
Emil
![[Image: GitHub%20Sponsors-grey?logo=github]](https://img.shields.io/badge/GitHub%20Sponsors-grey?logo=github){kind=icon}