Luke 42216 Posted Tuesday at 06:03 PM Posted Tuesday at 06:03 PM @seanbuffor @rbjtechdidn't you ask this before? Do you recall where?
Neminem 1607 Posted Tuesday at 06:38 PM Posted Tuesday at 06:38 PM (edited) This has been talked about here + other places but same conclusion. Edited Tuesday at 06:39 PM by Neminem 1
rbjtech 5338 Posted Tuesday at 07:13 PM Posted Tuesday at 07:13 PM 1 hour ago, Luke said: @seanbuffor @rbjtechdidn't you ask this before? Do you recall where? @NeminemTks. In summary, due to the very small image being processed, even with h/w tone mapping being applied, it takes longer to move the data into the GPU to then process it and move it back, than it does to simply process it directly in the CPU. If you want things done quicker, then running multiple instances of the BIF generator with Emby on different parts of the library is the way to go. 1 1
Ansell 5 Posted 17 hours ago Author Posted 17 hours ago 我的I/o不是瓶颈 最大的问题是cpu几乎沾满了 根本无法正常使用 我看的bif被弃用了应该使用更新的技术 emby是否考虑使用呢?
Luke 42216 Posted 1 hour ago Posted 1 hour ago 15 hours ago, Ansell said: My I/O isn't the bottleneck; the biggest problem is that the CPU is almost completely full, making it unusable. I've noticed that BIF is being deprecated and a newer technology should be used. Should we consider using Emby? HI, what makes you think bif is being deprecated?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now