I’m using an ARC A380 and at some point things broke and I didn’t realize why I was suddenly getting huge CPU spikes. Turning off tone mapping for now.
@ChuckPa Now with 1.40.5.8796 it seems it doesn’t even even fallback to software transcoding. The segmentation fault exits out the whole plexmediaserver, not just that one transcoding process. But yeah, I guess I’ll keep tone mapping turned off for now, just to be safe.
Is there any way y’all can revert the transcoder to whatever was working in 1.40.2, instead of keeping the transcoder in this half-working state? If not revert the version itself, but the same compiling process to a new version? Because the “new hardware” was working in 1.40.2, so idk if there’s a need to develop anything new.
If you want 1.40.2 then you’re free to stick with it until we do add ARC GPU support. Arc GPUs working with 1.40.2 is a fluke. We didn’t test or plan for it. Some folks just got lucky because of what’s installed already on their machines.
The transcoder will not be reverted. Doing so would break what was fixed for ApolloLake, GeminiLake, and several other CPUs (QSV transcoding & tonemapping).
I have one very sorely and long-since needed transcoder update here on my machine. It would be forum preview right now except for one machine where it didn’t work correctly. I expect it to be forum preview Monday/Tuesday.
After we complete preview, we’ll then be fully updating the transcoder.
As I understand the upstream FFMPEG release info, ARC GPU support is native to that new FFMPEG.
I would greatly appreciate not being bullied about this Arc GPU thing.
Support for the GPU will not come any sooner. It’s in the queue with 2 tasks ahead of it.
The more time I spend here responding to such posts detracts from completing the work
While I understand the frustration about waiting, please understand mine. I’m not a punching bag and do have limits.
The current default (and only) choice is Mobius tone mapping algorithm. This usually leads to over saturated colors . It almost makes the resultant H264 unwatchable.
What we are adding is where you can select the algorithm you want:
– Mobius
– Hable (much more realistic / life like IMHO)
– Linear
– Gamma
Each algorithm has it’s Pros and Cons as this is a 3D space mapping into a 2D solution. One axis will be lost / projected onto the other two. I find Hable to be the least objectionable and actually quite desirable for a H264 on a 1080p older TV.
I just posted some examples of a few of the different algorithm options in another thread. I only tested hable, mobius and reinhard. I came to similar conclusion as ChuckPa that I prefer hable myself (which is the default).
This support doc has a matrix of which platforms tone mapping is supported but I don’t know how up to date it is with recent changes to the transcoder.
@ ChuckPa
Is tonemapping for Rocket Lake fully fixed with PMS 40.5 and kernel 6.8.12 (Unraid)?
Logs indicate vaapi is active, but performance with tonemapping turned on still seems lackluster to what it used to be? (Let me know if you need logs).
I cannot speak to RocketLake. I have just acquired an AlderLake machine.
I can confirm AlderLake transcodes perfectly.
Even VC-1, progressive scan, works perfectly.
I will need your Debug logs which capture the attempted playback to look further.
I tried downgrading from v1.40.5.8854 to v1.32.8.7639 but after the downgraded completed the server was not available. So eventually had to revert back to 1.40
So the latest server update adresses some transcoder related issues and transcoding on Gemini Lake got something better. Converting 4K HDR stuff is going with transcoder speed 0.5 instead of 0.1. But it seems not to be using hw. I think sth is still fishy.
For me 1.40.5.8897 is still severely broken with Gemini Lake J4125.
Transcoding sessions for higher resolutions don’t start playing at all. Sometimes Dashboard shows the session, but on the client only yellow circle is showing.
While “HW” is shown in the dashboard, the CPU is fully loaded.
Lower resolutions (1080p → 720p) works but also under full load for the CPU.
Can we expect a working version in the nearer futere? To what version could I downgrade, to get it working again?
