View Full Version : Hardware considerations for BD Rebuilder
Groucho2004
4th May 2013, 15:56
Also, note my edit to my last post... the GPU isn't being used by DGDecNV.
That's not entirely true. By default, DGDecodeNV uses CUDA (which uses the GPU) for MPEG-2 decoding.
jdobbs
4th May 2013, 15:59
That's not entirely true. By default, DGDecodeNV uses CUDA (which uses the GPU) for MPEG-2 decoding. I would not pretend to be an expert in how CUDA works, but I think Neuron2 is (he wrote DGDecNV) and I was simply quoting him from this post (http://forum.doom9.org/showthread.php?p=1595435#post1595435).
Groucho2004
4th May 2013, 18:53
I would not pretend to be an expert in how CUDA works, but I think Neuron2 is (he wrote DGDecNV) and I was simply quoting him from this post (http://forum.doom9.org/showthread.php?p=1595435#post1595435).
For reference, here are a couple of screen shots showing how the graphics card is utilized with the 2 different decoding modes (MPEG-2 HD stream):
Cuda:
http://s22.postimg.org/stqmldlap/cuda.gif (http://postimage.org/)
CuVid:
http://s18.postimg.org/dasevyzih/cuvid.gif (http://postimage.org/)
blusky
4th May 2013, 21:49
Her is the Comparison of No Multiprocess and Multiprocess=1 with a reboot after each encode to clear cache.
No Multiprocess
[05/04/13] BD Rebuilder v0.43.06 (beta)
[11:58:04] Source: MEN_IN_BLACK_3_00800
- Input BD size: 26.88 GB
- Approximate total content: [01:45:50.385]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: DGDecNV
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[11:58:04] PHASE ONE, Encoding
- [11:58:04] Processing: VID_00800 (1 of 1)
- [11:58:04] Extracting A/V streams [VID_00800]
- [12:01:16] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 152,257 frames
- Bitrate: 27,186 Kbs
- [12:01:16] Reencoding: VID_00800, Pass 1 of 2
- [12:26:28] Reencoding: VID_00800, Pass 2 of 2
- [14:08:22] Video Encode complete
- [14:08:22] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[14:08:22]PHASE ONE complete
[14:08:22]PHASE TWO - Rebuild Started
- [14:08:22] Rebuilding BD file Structure
[14:08:51] - Encode and Rebuild complete
- WORKFILES folder removed.
[14:08:52] JOB: MEN_IN_BLACK_3 finished.
Here is MULTIPROCESS=1
----------------------
[05/04/13] BD Rebuilder v0.43.06 (beta)
[14:27:38] Source: MEN_IN_BLACK_3_00800
- Input BD size: 26.88 GB
- Approximate total content: [01:45:50.385]
- Target BD size: 22.95 GB
- Windows Version: 6.2 [9200]
- MOVIE-ONLY mode enabled
- Quality: High Quality (Default), Two Pass
- Decoding/Frame serving: DGDecNV [4-way]
- Audio Settings: AC3=0 DTS=0 HD=0 Kbs=640
[14:27:38] PHASE ONE, Encoding
- [14:27:38] Processing: VID_00800 (1 of 1)
- [14:27:38] Extracting A/V streams [VID_00800]
- [14:30:57] Reencoding video [VID_00800]
- Source Video: MPEG-4 (AVC), 1920x1080
- Rate/Length: 23.976fps, 152,257 frames
- Bitrate: 27,186 Kbs
- [14:30:57] Reencoding: VID_00800, Pass 1 of 2
- [14:52:22] Reencoding: VID_00800, Pass 2 of 2
- [16:25:23] Video Encode complete
- [16:25:23] Processing audio tracks
- Track 4352 (eng): Keeping original audio
[16:25:23]PHASE ONE complete
[16:25:23]PHASE TWO - Rebuild Started
- [16:25:23] Rebuilding BD file Structure
[16:25:53] - Encode and Rebuild complete
- WORKFILES folder removed.
[16:25:54] JOB: MEN_IN_BLACK_3 finished.
Here are the results: the No Multiprocess took 2:10 48sec.
The Multiprocess=1 took 1:58:16
The Multiprocess=1 encode was faster by 12: 32 sec.
Looks like clearing the cache did have a measurable effect on the time.
Tomorrow , just for fun I will try Multiprocess=2 and 3 to see how it compares.
Thanks jdobbs for the suggestion.
Darksoul71
7th May 2013, 11:49
That's not entirely true. By default, DGDecodeNV uses CUDA (which uses the GPU) for MPEG-2 decoding.
I think CUDA != PureVideo:
Pure Video (http://www.nvidia.com/page/purevideo.html)
vs.
CUDA (http://www.nvidia.com/object/cuda_home_new.html)
To my limited understanding of GPU architecture PureVideo is an integrated video processing engine while CUDA uses the GPU cores directly.
Groucho2004
7th May 2013, 13:26
I think CUDA != PureVideo
And nobody is disputing that.
I was just pointing out that DGDecodeNV can make use of CUDA (and therefore the GPU) when decoding MPEG-2 streams. However, the CPU load also increases in this scenario.
Darksoul71
7th May 2013, 14:16
And nobody is disputing that.
I was just pointing out that DGDecodeNV can make use of CUDA (and therefore the GPU) when decoding MPEG-2 streams. However, the CPU load also increases in this scenario.
Ah, sorry...this wasn't too obvious to me from the previous postings...
Then simply ignore my previous post ;)
Mark_Venture
12th May 2013, 16:28
Sorry, I'm a little confused as I read the last 20 or so posts of this thread with the talk and tests around DGDecNV.
Did it help speed up BD-Rebuilder in this case?
For DGDecNV, is the video card the limiting factor in how much it improves? or the CPU?
Is blusky's machine now optimized to give the best speed and quality output?
emilio99
4th June 2013, 19:40
How can I activate that the BD Rebuilder use CUDA for acceleration? Actually it uses:
- Decoding/Frame serving: DirectShow
Ch3vr0n
4th June 2013, 19:43
you can't. It doesn't. DGdecNV does that.
jdobbs
4th June 2013, 20:06
How can I activate that the BD Rebuilder use CUDA for acceleration? Actually it uses:
- Decoding/Frame serving: DirectShowYou'd need to install DGDecodeNV/DGIndexNV. If you don't have it, something you might want to try would be the OpenCL capability of X264 and see if you get any speed improvement. You can enable it by adding the following to your Config file under [Options]:
TWEAK_PASS_ONE=--opencl
TWEAK_PASS_TWO=--opencl
I haven't done any speed testing using this. So if you try it, please let me know how it works out.
soneca
5th June 2013, 01:08
You'd need to install DGDecodeNV/DGIndexNV. If you don't have it, something you might want to try would be the OpenCL capability of X264 and see if you get any speed improvement. You can enable it by adding the following to your Config file under [Options]:
TWEAK_PASS_ONE=--opencl
TWEAK_PASS_TWO=--opencl
I haven't done any speed testing using this. So if you try it, please let me know how it works out.
Experienced with the r2309 and no difference in speed here.
There were also conflicts with the nvidia drivers, so I stopped testing.:mad:
jdobbs
5th June 2013, 04:58
Experienced with the r2309 and no difference in speed here.
There were also conflicts with the nvidia drivers, so I stopped testing.:mad:Have you tried it with the latest release of BD-RB which includes r2334?
soneca
5th June 2013, 13:14
I tried now but got this message.:confused:
Later try on another pc.
http://s20.postimg.org/r95eqnvgt/x264_erro.jpg
jdobbs
5th June 2013, 13:31
I tried now but got this message.:confused:
Later try on another pc.
http://s20.postimg.org/r95eqnvgt/x264_erro.jpgOne of two things. Either the video driver doesn't support opencl -- or the opencl.dll stub is still in the folder with X264. If it is you should delete it (opencl should be in the system32 folder if installed with the video card).
soneca
5th June 2013, 13:57
Went to work, after opencl.dll be erased from the tools folder.
Later come back to do some tests.
jdobbs
5th June 2013, 14:08
Went to work, after opencl.dll be erased from the tools folder.
Later come back to do some tests.Yeah. That needed to be there at one time -- it will be removed in the next release.
soneca
6th June 2013, 23:39
There are still problems with this implementation of OpenCL, I have had problems(conflicts) on two machines(with recent nVidia boards and latest drivers installed) using both BD Rebuilder as RipBot264.
Mark_Venture
14th January 2014, 14:07
Sorry to revive an old thread, but with all this talk about optimizing the hardware to help encoding, since my BD-ROM just died, I thought about ripping speed, and since that will likely involve hardware, I thought this the best rather than starting a new thread.
I had an LG BH08LS20 BD-RW/DVD-RW. Using AnyDVD HD, I could rip (bluray) discs to my hard drive in under an hour. I don't recall if I used MediaCodeSpeedEdit to remove the RipLock, or not, it was so long ago. It has now died.
As a replacement, I got an LG BH16NS40 BD-RW/DVD-RW drive. Despite reading some older postings from across the web that it is a fast ripper, some blurays have taken nearly 2 hours to rip. MCSE doesn't appear to support this drive to remove riplock, and I haven't found any other solutions out there.
So, along with beefier processors, SSDs, etc... what do you do to speed up your ripping? What Bluray drive do you use? How long does it take you to rip a bluray to your hard drive?
soneca
14th January 2014, 17:05
I use PIONEER BD-RW BDR-208D(1.10) with AnyDVD HD and DVDFab but I can almost always higher speeds using AnyDVD HD. The time is from 10 to 45 minutes, depending on the content, and extracting BD-25 speeds are always higher. Never got similar speed with both LG have ever used.
http://s20.postimg.org/6lha7y3d9/anydvd.png
Have you tried updating the cable, sata drivers/chipset package?
jdobbs
14th January 2014, 17:27
I use PIONEER BD-RW BDR-208D(1.10) with AnyDVD HD and DVDFab but I can almost always higher speeds using AnyDVD HD. The time is from 10 to 45 minutes, depending on the content, and extracting BD-25 speeds are always higher. Never got similar speed with both LG have ever used.
http://s20.postimg.org/6lha7y3d9/anydvd.png
Have you tried updating the cable, sata drivers/chipset package? I have an LG drive (BH16NS40), and I'm peaking at about 25MB/s. So your numbers look pretty good to me.
gonca
14th January 2014, 22:54
LG WH14NS40 gets 7x to 8x on BD-DL
Mark_Venture
15th January 2014, 19:49
I have an LG drive (BH16NS40), and I'm peaking at about 25MB/s. So your numbers look pretty good to me.Hmm.. reading Cliffhanger, I topped out at 8.5 MB/s per Anydvd HD with my BH16NS40.
What firmware is on your BH16NS40? 1.0 or 1.01?
jdobbs
15th January 2014, 20:36
Hmm.. reading Cliffhanger, I topped out at 8.5 MB/s per Anydvd HD with my BH16NS40.
What firmware is on your BH16NS40? 1.0 or 1.01?I'm using 1.01.
The speed changes quite a bit between discs. 25 MB/s is where I peak. But I don't think I ever get down as low at 8.5 MB/s (maybe for a DVD, but not a BD). It's connected via SATA.
Mark_Venture
17th January 2014, 04:36
I'm using 1.01.
The speed changes quite a bit between discs. 25 MB/s is where I peak. But I don't think I ever get down as low at 8.5 MB/s (maybe for a DVD, but not a BD). It's connected via SATA.
do you have AnyDVD HD set for speed control enabled? or do you leave that unchecked?
jdobbs
17th January 2014, 06:12
do you have AnyDVD HD set for speed control enabled? or do you leave that unchecked? It is unchecked.
Mark_Venture
18th January 2014, 15:22
It is unchecked.
Thank you.
I did another rip yesterday, The Family, and it appears just the smaller files rip way slow. There was one M2TS which is about 30 gig. It did get up over 22MB/S for that file. Rip time was less than one hour.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.