H.265 Encode Speeds

[Acerjen]

I'm curious if anyone here has a 6-core or 8-core processor and are encoding using H.265. Is it AMD or Intel. I am wondering if the extra cores would make a difference over the 4 core I have now. Thanks for any help.

Later,
Acerjen

[HWK]

I'm curious if anyone here has a 6-core or 8-core processor and are encoding using H.265. Is it AMD or Intel. I am wondering if the extra cores would make a difference over the 4 core I have now. Thanks for any help.

Later,
Acerjen

I do have six core intel processor, however it still slow. If you tell me which preset you use in BD-RB I can run test and let you know difference between 4 and 6 core processors with HT turned on.

[Acerjen]

I do have six core intel processor, however it still slow. If you tell me which preset you use in BD-RB I can run test and let you know difference between 4 and 6 core processors with HT turned on.

I have been using the following settings

caption=MKV Container, HEVC 1920x1080, Intact Audio
vEncoder=1
vBitrate=4000
vKeyint=Auto
aBitrate=*
aType=2
vFormat=5
cType=1

I am currently using an Intel Core i5 Quad core and a 2 hour movie takes about 6.5 hours to encode. Any help you can provide is greatly appreciated.

You don't happen to know if AMD's 8-Core chips would work well for this, do you? I assume the more cores available, the faster it would be, but I have read in several places that AMD's multi-core CPUs don't have actual distinct cores like Intel, but share a lot of the pipeline and therefore don't perform well. But I don't think those reviewers were doing the heavy encoding required for H.265. Again, any help or advice you can give me is greatly appreciated.

Thanks. Later.
Acerjen

[HWK]

I have been using the following settings

caption=MKV Container, HEVC 1920x1080, Intact Audio
vEncoder=1
vBitrate=4000
vKeyint=Auto
aBitrate=*
aType=2
vFormat=5
cType=1

I am currently using an Intel Core i5 Quad core and a 2 hour movie takes about 6.5 hours to encode. Any help you can provide is greatly appreciated.

You don't happen to know if AMD's 8-Core chips would work well for this, do you? I assume the more cores available, the faster it would be, but I have read in several places that AMD's multi-core CPUs don't have actual distinct cores like Intel, but share a lot of the pipeline and therefore don't perform well. But I don't think those reviewers were doing the heavy encoding required for H.265. Again, any help or advice you can give me is greatly appreciated.

Thanks. Later.
Acerjen

Can you post contents of BDRebuider.ini file

[Acerjen]

Can you post contents of BDRebuider.ini file


BDREBUILDER.INI

[Options]
VERSION=0.50.0.2
MODE=3
ENCODE_QUALITY=0
ONEPASS_ENCODING=2
AUTO_QUALITY=1
TARGET_SIZE=23500
AUDIO_TO_KEEP=eng
SUBS_TO_KEEP=all
SD_CONVERT=0
OPEN_GOP=0
RESIZE_1080=0
RESIZE_1440=0
RESIZE_720=0
DEINTERLACE=1
SD_TO_1080=0
IGNORE_3D=0
CONVERT_WIDE=0
DTS_REENCODE=0
AC3_REENCODE=0
AC3_640=1
AC3_192=0
KEEP_HD_AUDIO=1
AVCHD=1
REMOVE_WORKFILES=1
MOVIE_ONLY_LOOP=1
REMOVE_OUTPUT=0
USE_FILTERS=0
BDMV_CERT_ONLY=0
USE_LAVF=0
IVTC_PULLDOWN=0
ASSUME_DVD_PAL=0
UNMASK_CHAPTER=1
COMPLETION_BEEP=0
DGDECNV=1
OUTPUT_SBS=0
NEROAAC=0
SUPTITLE=0
AUDIO_TRACK_LIMIT=0
SUBTITLE_TRACK_LIMIT=1
CUSTOM_TARGET_SIZE=8300
ENCODER=0
DGDECIM=0
FRIMSOURCE=0
MENU_BACKGROUND=C:\BD-Rebuilder\Misc\menuback.jpg
MENU_ACTIVE_COLOR=YELLOW
IMPORT_THRESHOLD=15
QUICK_PLAY_THRESHOLD=10
MENU_AUTO_BACKGROUND=1
MENU_PLAY_SEQUENTIAL=1
MENU_START_WITH_MENU=1
WIDE_PERCENT=40
WIDE_OFFSET=.85
DECODER=0
MOVIEONLY_TYPE=7
ALTCRF=23
ALT_TARGET=4750
ALTMETHOD=2
ALTAUTOCROP=0
QUICK_EXTRAS=0
[Paths]
DGIndexNV=C:\Program Files (x86)\dgdecnv2041\DGIndexNV.exe
DGDecNV=C:\Program Files (x86)\dgdecnv2041\DGDecodeNV.dll
WORKING_PATH=E:\
SOURCE_PATH=V:\


Thanks. Later.
Acerjen

[jdobbs]

I'm curious if anyone here has a 6-core or 8-core processor and are encoding using H.265. Is it AMD or Intel. I am wondering if the extra cores would make a difference over the 4 core I have now. Thanks for any help.

Later,
AcerjenI have both an 8 core AMD processor and a 4 core AMD processor. The 8 core is much faster with X265.

[Acerjen]

I have both an 8 core AMD processor and a 4 core AMD processor. The 8 core is much faster with X265.

How long does it take you to encode a 2 hour Bluray movie to H.265 MKV using your 8-core?

[jdobbs]

I moved this discussion to a thread of its own -- as it was off-topic for the bug thread.

It's been a while and several X264 versions since I tested its speed. So I just started a test disc (Legend of Hercules). It's a 1920x1080 source, that I'm encoding single-pass using a CRF of 23 and quality set to "good", and is currently about 9% complete. It is encoding at 17.5 fps.

So if it keeps up at this pace it would take about 2 hrs and 45min to complete a 2 hour movie.

[HWK]

I moved this discussion to a thread of its own -- as it was off-topic for the bug thread.

It's been a while and several X264 versions since I tested its speed. So I just started a test disc (Legend of Hercules). It's a 1920x1080 source, that I'm encoding single-pass using a CRF of 23 and quality set to "good", and is currently about 9% complete. It is encoding at 17.5 fps.

So if it keeps up at this pace it would take about 2 hrs and 45min to complete a 2 hour movie.


Jdobbs, original poster was looking for comparison of X265

[mparade]

Does anyone know if using the same x265 command line with the same source and all the other settings in BD-RB how can one get drastically different process speeds? I have tested it with my Hobbit 3D BD part 1-2. FrimSource was used as the frameserver which resulted in very distinct fps values (for part1 2.3fps for part2 0.8 fps)during encoding part 1 and 2 which were AVC coded.
Interestingly, my first 4 encodes were made getting around 2.5 fps, but during the next one I got 0.8 fps.

I have a relatively new CPU E5-1650 v3 3.5Ghz with 6 cores.

Maybe the reason is outside BD-RB?

I would like to know if someone has an idea. It would be greatly appreciated.

[jdobbs]

Jdobbs, original poster was looking for comparison of X265The problem is that it couldn't be an "apples to apples" comparison if I ran it on a computer with 4 cores, since the capability of any two processors differs vastly. So, I'm not sure there is really an answer to that comparison.

I guess I could run it on the 8 core processor and only let it allocate 4 cores to the process. But I'm not sure how accurate that would be either.

[jdobbs]

Does anyone know if using the same x265 command line with the same source and all the other settings in BD-RB how can one get drastically different process speeds? I have tested it with my Hobbit 3D BD part 1-2. FrimSource was used as the frameserver which resulted in very distinct fps values (for part1 2.3fps for part2 0.8 fps)during encoding part 1 and 2 which were AVC coded.
Interestingly, my first 4 encodes were made getting around 2.5 fps, but during the next one I got 0.8 fps.

I have a relatively new CPU E5-1650 v3 3.5Ghz with 6 cores.

Maybe the reason is outside BD-RB?

I would like to know if someone has an idea. It would be greatly appreciated.Since you're using X265, I assume your output is to side-by-side. Are the target SBS sizes the same (full or half SBS)? Are you sure the quality setting is the same in each case?

I would expect the speed to change based upon complexity of the source -- but I wouldn't expect it to change that much.

[mparade]

Since you're using X265, I assume your output is to side-by-side. Are the target SBS sizes the same (full or half SBS)? Are you sure the quality setting is the same in each case?

I would expect the speed to change based upon complexity of the source -- but I wouldn't expect it to change that much.

Output is Full SBS format (3840x1080) using an mkv profile with no resize. I left everything on the same values I am 100% sure of that.
I have similar amount of difference in speed after having compared two 2D BD VC-1 coded sources (300 and Lord of the Rings: The Two Tower Extended Cut). I could reach 2.3 fps with 300 but only 0.9 with Lord of the Rings, even though, 300 with much more grain.

I used the same quality settings, the same frameserver, everything was the same except the source. Maybe, x265 itself switches on/off hyper-threading on my computer randomly, or recalculate the thread number every time I start a new encode, I really have no idea.

I will try different frame servers to see if they would equalize the "jumps" in speed, although I was very happy with the result of FrimSource. (x265 Full SBS output with 1.5 fps speed and slow preset).