Obviously the command line parameters being fed to the x265/FFmpeg command line via Handbrake aren't optimal. I mean like I stated already about 10 times you're using the same damn encoding back end. I'm calm but when people can't connect a dot that you gave straight up results to connect them...
This is exactly what Handbrake is guy. I like how I can post freely consumable info from the internet, real results mind you, running Windows with this same hardware and those results get ignored. You can't take any examples I've provided and realize it's the program feeding variables to the...
The problem is completely with Handbrake in regards to x265 in Windows. Performance is perfectly fine with other GUIs using the same open source software. Not sure what else plainly obvious I have to articulate to you are real world results not enough?
I already give up posting here not...
It should just be the command line arguments for x265 handbrake is using the dev responsible for that portion of the app should be able to figure it out pretty quickly. Handbrake is open source so expecting some level of performance from a free GUI might not be some expectation you can cash your...
Sure run standardized tests that's fine but don't stop there with some open source GUI that is obviously not optimized for the hardware you are reviewing. In that case the only people are you are connecting with are people that buy a 32 core CPU that aren't properly going to utilize it. Paid...
I have a R820 poweredge 4 socket with older v2 8 core xeons and for x265 I do exactly what I stated above to maximize encoding speeds on it. Depending on 4K source material bitrate, etc. I can encode 4K source/ouput near real time 23fps when combined with my 1950x system. 2990wx used properly in...
Handbrake is just a GUI for ffmpeg, x265, etc. just like many of the other open source GUIs available that serve the same functions. It's pretty obvious other GUIs using the same backend tools don't have this performance issue in Windows running on AMD CPUs including the 2990wx as noted in the...
What is actual CPU utilization during these handbrake encodes? I don't use handbrake admittedly but I thought it was known it scales like crap with over 8 cores (phys or log) I'm not sure.
https://hwbot.org/benchmark/hwbot_x265_benchmark_-_4k/rankings?cores=32#start=0#interval=20
2990wx seems...
I really could care less about projected 4K performance with sli and crossfire based upon low resolution benchmarks...it's then just a matter of making an educated guess. All of the hardware necessary for testing sli and crossfire is available so someone should just test it instead of worrying...
someone please review sli or crossfire with ryzen @1440p @2160p for the love of god. waiting for the first review that actually shows a: multi-gpu works on x370 as it should b: cpu scaling at higher resolutions. who cares about real world 1080p gameplay on a PC? People that game @ 1080p...
True but GPUs are current and future as VR will rely on that rather than CPU architecture. Business applications haven't really required faster CPUs in the past 5 years as you can stick tons of VMs on a single multicore server and not be CPU bound. I understand desktop Ryzen got released but I...
It's bad how much the CPU market has stagnated with performance. I have two x79/3930k rigs overclocked to 4.6Ghz+ that still yield exceptional performance that can be purchased for around $350 total used (cpu/mb/ram). I can live with only two usb 3.0 ports or just buy a hub.
AMD will live and...
Not a single review I see that shows what someone investing money in a Ryzen rig can expect. I think I saw a single review with games tested @ 4K res. I see ZERO reviews currently with high end SLI or Crossfire setups. It would be NICE if instead of reviewers focusing on games running @ 1080p...