Since I last posted, I essentially just reshared my libraries with all users on the ‘new server’.
I’m assuming by doing the above method, I will need to reshare again, so is there any benefit to doing so now? (for instance, at the moment, all users will have to re-pin the libraries for the new server, so if that can be avoided, that would be great).
On a side note, that J4xxx Intel IHD driver issue seems to still be around. My new NAS couldn’t play H265 files on H264 devices, but I managed to since apply the Vaapi driver fix to preferences.xml successfully and now the same H265 files are playing perfectly on the H264 devices…
Per sharing again: Yes you need to share again because the server’s ID numbers were lost during the Preferences.xml corruption.
(they don’t let me in the database to get them… nor do i want that level access)
As for paying me more — — I’m retired.
Helping others keeps my mind active.
What I do here at home keeps my technology level moving forward / quasi-current.
Thanks @ChuckPa , yes, server is back. Any thoughts on the IHD driver issue? Will I have to add the Vaapi line in Preferences every time I update? I thought the issue was fixed with an update but definitely not for me…
Thanks @ChuckPa, I assume if I let it default to iHD, then I can’t do any H265 to H264 transcoding? Or is there a workaround for this (unfortunately I have both high and low bitrate content, so maybe Vaapi is the best compromise, since I can still play H265 on H264)?
Side point, regarding recovery of my server earlier using claim token, I’m assuming that despite sharing libraries again with users, users will see these libraries as a new server with the same name, or should they still be able to access the previously pinned libraries once shared again?
Where I’ve found the i965 driver to be of the most benefit is with lower-bitrate video.
The driver is how we talk to the QSV chip inside the CPU.
We still use that chip to perform the transcoding whether be HEVC H264 or MPEG2 it’s all still the same – except for the communications method.
I’ve noticed that , if you have multiple servers, you only need re-assign their shared folders.
If you have only one server, and their invitation isn’t still in your account, yes you’ll need to re-invite them.
They should still see the same pinned library sections if the server name is the same and library names the same — BUT — I’ve not checked that in a while so I hope it’s still the same.
Thanks @ChuckPa, just to confirm, in terms of reclaiming, they had to pin the libraries again, the old ones didn’t work, despite same server name and same library…
Regarding the drivers, when letting the NAS default to the iHD driver, I cannot transcode H265 to H264 at all, it literally buffers every other second. As I have few H264 only users, and 95% of my library is H265, I don’t really have a choice, so will have to stick to the i965. Thanks for all the info.
Sorry @ChuckPa, as per my post above, I have switched to a TS-453D, as the TS-453B random rebooting issue wasn’t going away. The issues I’m having with H265 to H264 transcoding is with the TS-453D (even with no subtitles).
No problem @ChuckPa. So I tested again (H265 to H264 transcode) with the default iHD driver - plays fine with no VOBSUB subtitles, but stutters every few seconds with them (as noted by yourself above).
I then tried the i965 driver and it transcodes H265 to H264, even with VOBSUB subtitles fine. I think this is what you are expecting, but have attached the log files in case…
So given I have H265 files with PGS/VOBSUB, and remote users who can only play H264, and want to use subtitles, I guess the i965 driver is the only option. (I read previously that the "VaapiDriver=“i965” line in preferences.xml isn’t needed anymore as a recent update sorted the issue - but I guess it still is needed if you are using image based subtitles on H265 files and transcoding to H264…)
— I’m retired.