AMD Ryzen
- Thread starter mayorville
- Start date
x264 stand alone will eat as many cores/threads as you can throw at it. CPU utilisation will be close to 100% most of the time but it does depend on encode settings, some can reduce utilisation however you can usually bump it back up to 100% by increasing the threads and lookahead-threads. If those options are set to auto they should increase as needed but they don't always go far enough so sometimes it's necessary to set them manually. In my experience the occasions where x264 CPU utilisation is less than 100% are rare when adjusting the thread settings where necessary, only some of the encodes using the most demanding encode settings at high resolutions run at less than 100%.
Congratulations ! That is beaut news.
jmc
Active member
I'm ready...
Hmm, may have to buy both Pro and non Pro,
I prefer the less complex non Pro except for special needs.
Heh, any bundle discount?
jmc
jmc
Active member
From what I've been reading the problem with Ryzen is not the cpu but
the chipsets...
Low PCie lane numbers. So far you won't find 40 plus lanes in a Ryzen board.
So may have problem fitting in all the GBs per second M.2
storage systems you want. And the number of fast Sata connections
may also be lacking.
I've got a stack of old SSDs I want to raid into one fast 1.2 TBs of storage.
Hopefully better motherboards with all the goodies will come out in the future.
EDIT....
Only the X300 / B300 / A300 chipsets have PCie3.0 !
These are Small Form Factor chipsets.
The main chipsets ONLY have PCie2.0 which is what my 6 year old
SandyBridge X79 has and THAT cuts my storage transfer speed in half
vs PCie3.0.
Hope the motherboard makers add their own PCie 3.0 lanes!
jmc
the chipsets...
Low PCie lane numbers. So far you won't find 40 plus lanes in a Ryzen board.
So may have problem fitting in all the GBs per second M.2
storage systems you want. And the number of fast Sata connections
may also be lacking.
I've got a stack of old SSDs I want to raid into one fast 1.2 TBs of storage.
Hopefully better motherboards with all the goodies will come out in the future.
EDIT....
Only the X300 / B300 / A300 chipsets have PCie3.0 !
These are Small Form Factor chipsets.
The main chipsets ONLY have PCie2.0 which is what my 6 year old
SandyBridge X79 has and THAT cuts my storage transfer speed in half
vs PCie3.0.
Hope the motherboard makers add their own PCie 3.0 lanes!
jmc
Last edited:
You know you can use the simple profile dialog in Pro right? There is a check box at the bottom of the profile list that swaps the two. And t any time you can use the other dialog by holding shift when clicking the button. This works on all the buttons in the profile dialog and the options button in the Save dialog.
jmc
Active member
I'll have to try that out and see how it goes.
Sometimes I forget simple little options and how to get back there!
Thanks,
jmc
Will the upcoming v6 be using x265 encoder that supports max CPU? Also will this be available in consumer TV Suite v6 as well or will TVSuite v6 continue to use MainConcept's and use its implementation of H.265 HVEC?
jmc
Active member
I've never been able to get my AMD 290 video card to encode. So no idea of quality.
I did see the following article, it showed (almost 3x what I use) 3.5Mbps NVEnc encoding vs (cpu) X264 images
and I was stunned on how bad the NVEnc image was.
I mean, that may be acceptable on Utube but can't see any video person keeping it.
Would love to see an image quality comparison on what you are coming up with.
https://uk.hardware.info/reviews/7206/2/streaming-devices-review-10-capture-cards-tested-advantages
I wouldn't put much stock in that review. 3.5Mbps is pretty low for a 720p transcode. Netflix uses 7Mbps for 1080p/24fps, a 720p/59.94 has MORE pixels per second then 1080p/24. So you'd need to use closer to 8Mpbs to get maximum quality. Heck BluRay uses ~20Mbps for 1080p/24 content.
My point is that if your goal is quality, and not size, then you can get fine encodes from NVEnc by setting the bitrate to a decent level. If your goal is to compress the video as small as possible then using x264 in double pass mode is probably your best bet.
My point is that if your goal is quality, and not size, then you can get fine encodes from NVEnc by setting the bitrate to a decent level. If your goal is to compress the video as small as possible then using x264 in double pass mode is probably your best bet.
I find NVEnc very close in quality to software encoders on the faster settings. If you want significantly better quality you need a software encoder set to go very slowly, like under 10 frames per second even on a desktop Core i7. Waiting for that is too tedious for me in most cases.
Finally got my Ryzen 1800x/x370 MB up and running Win7-64. Had no trouble installing or finding latest drivers for all the MB devices.
Still waiting for my "free" cooler bracket update. Gave up and put on an old clip-on cooler for now - no overclocking, but it will handle encoding loads at stock 3600 GHZ.
Encoding a 1080i recording down to 720x400, VRD/h264 does use all 16 threads with a fairly uniform 50%-60% load on each. Had encoded the same file on the old FX-8370/AMD 970 system. The new Ryzen finished the same encode in half the time and twice the fps.
Temps stayed under 65C, but I didn't want to try encoding 2 at once until I can get a better cooler setup installed.
Still waiting for my "free" cooler bracket update. Gave up and put on an old clip-on cooler for now - no overclocking, but it will handle encoding loads at stock 3600 GHZ.
Encoding a 1080i recording down to 720x400, VRD/h264 does use all 16 threads with a fairly uniform 50%-60% load on each. Had encoded the same file on the old FX-8370/AMD 970 system. The new Ryzen finished the same encode in half the time and twice the fps.
Temps stayed under 65C, but I didn't want to try encoding 2 at once until I can get a better cooler setup installed.