HEVC uses x265 and if your client does not support native playback then it will fall back to transcoding which will be crappy on the Pi for sure.So i got my raspberry pi yesterday and since morning I have been playing with it. I was able to install jellyfin (i set gpu_mem to 512) and enabled hardware acceleration, sonarr, qbittorent and in terms of setup, everything works.
Problem I have is jellyfin is working terribly. In the sense, on the Pi, i have my all setup under jellyfin done and scanning of library and all is complete. But when using the jellyfin app on my iPad, the video takes lots of time to start and then too things lag and buffer. If I increase playback speed to 1.25x it keeps stopping even more. Or even if I double tap right side of screen to go ahead by 10 seconds or so, it sort os freezes.
To see if the issue is with iPad app, i even tried on my fire hd 10 and samsung Tab A7 and still same result. I am suspecting it is due to transcoding as the video files are HEVC (is that x265?).
I unchecked the option under my user profile to NOT Transcode and that prevented the videos from completely playing now on my client devices.
So I installed kodi on my android tablet and installed the jellyfin addon and there, everything plays super smooth. I believe that is due to kodi's support for most formats which is always using direct play. But I don't want to use kodi since it does not have playback speed control function. (If there is one, please suggest how to use it).
Can anyone tell me what am i doing wrong and what is the fix?
HEVC uses x265 and if your client does not support native playback then it will fall back to transcoding which will be crappy on the Pi for sure.
Try this though. Keep in mind that x265 will eat CPUs for breakfast if its an older device.
Not used jellyfin, but seems it does have DLNA - https://jellyfin.org/docs/general/networking/dlna.htmlBtw does jellyfin server do DLNA or something so at least I can use my nplayer to do direct streaming?
As already suggested, Jellyfin does serve over DLNA. Second the MiniDLNA recommendation too.... Btw does jellyfin server do DLNA or something so at least I can use my nplayer to do direct streaming? ...
This is the one I have.As people like [mention]Marcus Fenix [/mention] told me before, the heat sinks do nothing in regulating temperature on Rpi4. I have kept the top part of my case open for now. With torrenting and a single 720p direct play stream using jellyfin server, Temps are 75 degree Celsius.
So now I am hunting for a solution to this. Will a passive cooling case actually help or a case with fan will? Links appreciated. I don't want to do trial and error so will buy something that actually works.
Well right now its sitting at 10% CPU usage so don't get your hopes up to that extent but yeah its pretty good.[mention]Marcus Fenix [/mention] wow your pi temps are great. I have never seen anything below 60 Celsius in mine. Is this passive metal case so effective?
My governer too is same as yours right from day 1.
But in my situation, I have applied those 3 heat sinks so can I remove them easily or it needs some special skill? I don't want to screw up the Pi.
Apologies I missed that the link I posted was mentioned earlier in this thread.
Throttling starts at 80s but 75 does seem high for that kind of workload. Is the chip transcoding that video ?
yes you could try this - a shell script to check status of qBittorrent, if not running restart it.Anyway to restart it automatically if it crashes? Any shell script which can be scheduled using cron to check status every 30 min and If crashed then restart.
#!/bin/bash if ! ps x | grep qbittorrent | grep -v grep &>/dev/null ; then ~/usr/bin/qbittorrent sleep 5 echo "qBittorrent successfully restarted : Time $(TZ=":Asia/Kolkata" date)" >> ~/status_check/qBittorrent_Status.log fi
*/5 * * * * /bin/bash ~/status_check/check_torrent
sudo systemctl status qbittorrent
root@DietPi:~# sudo systemctl status qbittorrent
● qbittorrent.service - qBittorrent (DietPi)
Loaded: loaded (/etc/systemd/system/qbittorrent.service; disabled; vendor preset: enabled)
Active: active (running) since Wed 2021-06-09 12:52:02 BST; 3min 50s ago
Main PID: 13150 (qbittorrent-nox)
Tasks: 14 (limit: 4915)
sudo systemctl start qbittorrent
sudo systemctl enable qbittorrent
systemd will automatically restart when a service crashes. no need to script.
seems in your case it is disabled.
sudo systemctl enable qbittorrent