View Full Version : Encoding times
shrink0
23rd January 2007, 22:36
Hey jdobbs or any other experts, What settings do you recommend to improve encode time. I'm using DVDRB pro, HCencoder ,Quality=best, mainmovie only. I'm getting approx. 5-6 hrs process times ,i know the free HCenc. has alot to do with it ,but other than buying new HW, what can I do?
Did ask this same ? over at Ddigest's forum , someone mentioned changing the rebuilder ini file Encode_processes=1 to ? so hope I'm making sense!! TIA
therat
24th January 2007, 03:09
A lot will depend on your system. What aree your system specs?
I can use DVD-RB Pro with HC set to best and do a full backup of The Godfather in a touch over 2 hours (did it yesterday).
Bear in mind I am using multiple instances of HC on my E6600 system.
A lower spec system with a single instance of HC will take much longer.
cheers
wmansir
24th January 2007, 04:07
You don't have to edit rebuilder.ini, you can enable Multiple Encoder Processes from the Settings menu within DVD-RB. But this only works if you have multiple processors. To check, hit Ctr-Shift-Esc to bring up the Task Manager, click on the Performance tab. If you have 2 CPU History graphs then you have 2 processors/2 cores/or a Pentium 4 with Hyperthreading enabled to emulate 2 cores. Using multiple instances of HC with the first two situations will give you a significant boost in encode time. I think a P4 w/HT enabled could see minor improvement (10%).
shrink0
24th January 2007, 06:19
That explains it of course! my specs are rather slow on my work pc for encoding. 2600+ athy 64 ,768 Ram . I let the process do it's thing at night so no prob. However I 've just installed DVDRB pro on my Media pc 3700 Athy64, Epox 939 mobo 1 gig Ram, 200g hdd,80 gig hdd,hauppauge 150. Just did my Saving private Ryan main movie only ,HCencoder, quality= best in 281 min. prepare/encode/ rebuild. I'm happy and the results are great. :thanks:
techreactor
24th January 2007, 08:02
Or try with HCenc "Quality=Normal", the quality still remains good and you will not notice the difference on a CRT but the encoding time is reduced considerably.
linx05
24th January 2007, 12:39
http://img207.imageshack.us/img207/5481/cpuz0ap.th.png (http://img207.imageshack.us/my.php?image=cpuz0ap.png)http://img260.imageshack.us/img260/10/task3ia.th.png (http://img260.imageshack.us/my.php?image=task3ia.png)
@wmansir
I heard mine doesn't have *true* multiple processors. For example in picture one, it has for the 'cores' section, 1. When I use multiple processors (with HCenc) I get well under real time (PAL), about 10-15fps. Even using one HCenc I get around real time. Takes me about 6 hours to do a movie, no filters, single HCenc.
Does this sound right?
therat
24th January 2007, 13:01
Yours is a P4 with hyperthreading so it doesn't have 2 separate cores but instead emulates 2 cores. As wmansir said, using 2 instances of HC will only see ~10% decrease in time taken.
6 hours sounds about right for your system especially if you take shrink0's times as a guide.
cheers
wmansir
24th January 2007, 13:32
You have a P4 with Hyperthreading. HT isn't always predictable, this thread (http://forum.doom9.org/showthread.php?t=107248) indicates multiple instances of HCenc with a CPU much like yours is about 10% faster overall.
However, depending on the system it is possible that running multiple instances causes a bottleneck somewhere else and so the total speed is actually slower than one instance. See the thread linked above for more info.
shrink0
24th January 2007, 16:01
Or try with HCenc "Quality=Normal", the quality still remains good and you will not notice the difference on a CRT but the encoding time is reduced considerably.
Thanks tech! I was going to try the Normal setting ,except I was concerned about quality loss. I have a plasma hdtv. I Will give it a shot though and see how it looks.
Also side note to linx05 post, I did King Kong last night,same settings Hcencode,quality>best ,main movie only, total time 6hrs.52min. As i said processed at night so thats ok!!!!!
BTW I ran King Kong on my 2600+ Athy 64 754 skt not the 3700+ skt 939 sys. I should see better results on the 3700....
gizzin
25th January 2007, 06:45
therat
What is your system specs, thats sounds unrealistic to me, whats your setting, best in HC?
I have am2 4200 dual core, with 1 gig ram, it took 281min, one click from start to finish with multiple encoder instances.
the video was 4 hrs 30min however so maybe thats why, it was also interlaced.
therat
25th January 2007, 10:36
therat
What is your system specs, thats sounds unrealistic to me, whats your setting, best in HC?
I have am2 4200 dual core, with 1 gig ram, it took 281min, one click from start to finish with multiple encoder instances.
the video was 4 hrs 30min however so maybe thats why, it was also interlaced.
My system specs are as follows:
Gigabyte GA-965P-DS3 F6 Bios
Core 2 Duo E6600
2x1gig Geil PC-6400 DDR2-800 5-5-5-15
GeCube Radeon X1900GT PCI-x
1x 250g WD SATA11 + 320gb WD SATA1
I was using multiple instances of HC set to Best Quality. My copy of The Godfather is Region 4 PAL and I only backed up the first Disc which doesn't have any extras.
My log is below.
cheers
[13:19:57] Phase I, PREPARATION started.
- DVD-RB v1.21.0
- AVISYNTH 2.5.6.0
- HC encoder selected
- Source: 3
- VTS_02: 3,806,629 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 252,100 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 52.2%
- Overall Bitrate : 2,852Kbs
- Space for Video : 3,511,046KB
- HIGH/LOW/TYPICAL Bitrates: 3,747/2,319/2,852 Kbs
[13:22:52] Phase I, PREPARATION completed in 3 minutes.
[13:23:29] Phase II ENCODING started
- Creating M2V for VTS_02 segment 0
- Creating M2V for VTS_02 segment 1
- Creating M2V for VTS_02 segment 2
- Creating M2V for VTS_02 segment 3
- Creating M2V for VTS_02 segment 4
- Creating M2V for VTS_02 segment 5
- Creating M2V for VTS_02 segment 6
- Creating M2V for VTS_02 segment 7
- Creating M2V for VTS_02 segment 8
- Creating M2V for VTS_02 segment 9
- Creating M2V for VTS_02 segment 10
- Creating M2V for VTS_02 segment 11
- Creating M2V for VTS_02 segment 12
- Creating M2V for VTS_02 segment 13
- Creating M2V for VTS_02 segment 14
- Creating M2V for VTS_02 segment 15
- Creating M2V for VTS_02 segment 16
- Creating M2V for VTS_02 segment 17
- Creating M2V for VTS_02 segment 18
- Creating M2V for VTS_02 segment 19
- Creating M2V for VTS_02 segment 20
- Creating M2V for VTS_02 segment 21
- Creating M2V for VTS_02 segment 22
[15:16:51] Phase II ENCODING completed in 113 minutes.
[15:27:10] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_02
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Rebuilding seg 5 VOBID 1 CELLID 6
- Rebuilding seg 6 VOBID 1 CELLID 7
- Rebuilding seg 7 VOBID 1 CELLID 8
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_02_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
[15:40:36] Phase III, REBUILD completed in 13 minutes.
Done.
techreactor
25th January 2007, 10:44
I did King Kong last night,same settings Hcencode,quality>best ,main movie only,
OT, King kong gives a compression of appx 50% which is too low, you should also try AQMenc with QmatOp for this movie for better results.
therat
28th January 2007, 02:39
OT, King kong gives a compression of appx 50% which is too low, you should also try AQMenc with QmatOp for this movie for better results.
I've never tried AQM before so I have it a go on The Godfather. Compression of 52%. Not sure what I'm doing wrong but I thought both copies done by HC and CCE were better. HC and CCE were very similar quality
BTW with CCE I use the AutoQ2 matrix for low bitrate movies like The Godfather etc
techreactor
29th January 2007, 07:03
did you enable QmatOp, it will determine the optimum matrix to be used and then use it , for each segment.
therat
29th January 2007, 10:57
did you enable QmatOp, it will determine the optimum matrix to be used and then use it , for each segment.
Yes I did
shrink0
30th January 2007, 06:19
Or try with HCenc "Quality=Normal", the quality still remains good and you will not notice the difference on a CRT but the encoding time is reduced considerably.
Thanks TR! I just did Lord of War using HCenc "Quality=Normal, however I slightly OC'ed my 3700 A64 to 2.5 GHZ. The quality looks pretty darn good on the Normal setting. Going back to stock MHZ since I was just trying the Normal quality as fast as possible to compare times. Thanks again!!!!!!:D
[17:05:26] One Click encoding activated...
-----------------
[17:05:27] Phase I, PREPARATION started.
- DVD-RB v1.21.0
- AVISYNTH 2.5.6.0
- HC encoder selected
- "Movie Only" mode is enabled.
- Source: LORD_OF_WAR
- VTS_01: 3,832,956 sectors.
-- Scanning and writing .D2V & .AVS files
[17:56:03] One Click encoding activated...
-----------------
[17:56:03] Phase I, PREPARATION started.
- DVD-RB v1.21.0
- AVISYNTH 2.5.6.0
- HC encoder selected
- "Movie Only" mode is enabled.
- Source: LORD_OF_WAR
- VTS_01: 3,832,956 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 175,302 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 60.7%
- Overall Bitrate : 5,403/4,322Kbs
- Space for Video : 3,857,792KB
- HIGH/LOW/TYPICAL Bitrates: 4,626/400/4,322 Kbs
[18:01:08] Phase I, PREPARATION completed in 5 minutes.
[18:01:08] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Creating M2V for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Creating M2V for VTS_01 segment 7
- Creating M2V for VTS_01 segment 8
- Creating M2V for VTS_01 segment 9
- Creating M2V for VTS_01 segment 10
- Creating M2V for VTS_01 segment 11
- Creating M2V for VTS_01 segment 12
- Creating M2V for VTS_01 segment 13
- Creating M2V for VTS_01 segment 14
- Creating M2V for VTS_01 segment 15
- Creating M2V for VTS_01 segment 16
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_01 segment 18
- Creating M2V for VTS_01 segment 19
- Creating M2V for VTS_01 segment 20
- Creating M2V for VTS_01 segment 21
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
- Creating M2V for VTS_01 segment 26
- Creating M2V for VTS_01 segment 27
- Creating M2V for VTS_01 segment 28
- Creating M2V for VTS_01 segment 29
[19:58:05] Phase II ENCODING completed in 117 minutes.
[19:58:05] Phase III, REBUILD started.
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Rebuilding seg 1 VOBID 1 CELLID 2
- Rebuilding seg 2 VOBID 1 CELLID 3
- Rebuilding seg 3 VOBID 1 CELLID 4
- Rebuilding seg 4 VOBID 1 CELLID 5
- Rebuilding seg 5 VOBID 1 CELLID 6
- Rebuilding seg 6 VOBID 1 CELLID 7
- Rebuilding seg 7 VOBID 1 CELLID 8
- Rebuilding seg 8 VOBID 1 CELLID 9
- Rebuilding seg 9 VOBID 1 CELLID 10
- Rebuilding seg 10 VOBID 1 CELLID 11
- Rebuilding seg 11 VOBID 1 CELLID 12
- Rebuilding seg 12 VOBID 1 CELLID 13
- Rebuilding seg 13 VOBID 1 CELLID 14
- Rebuilding seg 14 VOBID 1 CELLID 15
- Rebuilding seg 15 VOBID 1 CELLID 16
- Rebuilding seg 16 VOBID 1 CELLID 17
- Rebuilding seg 17 VOBID 1 CELLID 18
- Rebuilding seg 18 VOBID 1 CELLID 19
- Rebuilding seg 19 VOBID 1 CELLID 20
- Rebuilding seg 20 VOBID 1 CELLID 21
- Rebuilding seg 21 VOBID 1 CELLID 22
- Rebuilding seg 22 VOBID 1 CELLID 23
- Rebuilding seg 23 VOBID 1 CELLID 24
- Rebuilding seg 24 VOBID 1 CELLID 25
- Rebuilding seg 25 VOBID 1 CELLID 26
- Rebuilding seg 26 VOBID 1 CELLID 27
- Rebuilding seg 27 VOBID 1 CELLID 28
- Rebuilding seg 28 VOBID 1 CELLID 29
- Rebuilding seg 29 VOBID 1 CELLID 30
- Updating NAVPACKS for VOBID_01
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Correcting VTS Sectors...
[20:13:36] Phase III, REBUILD completed in 15 minutes.
Done.
[20:13:36] PREPARE/ENCODE/REBUILD completed in 137 min.
techreactor
30th January 2007, 08:25
Yes I did
Can you post you max/min/avg bitrate from the RB logs and did you use any AVS filters ??
I got good results with KK.
therat
30th January 2007, 10:30
Can you post you max/min/avg bitrate from the RB logs and did you use any AVS filters ??
I got good results with KK.
from the RB logs
[16:56:40] Phase I, PREPARATION started.
- DVD-RB v1.21.0
- AVISYNTH 2.5.6.0
- AutoQMatEnc 0.33.0.7 selected.
- Source: 1
- VTS_02: 3,806,629 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 252,100 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 52.2%
- Overall Bitrate : 2,852Kbs
- Space for Video : 3,511,046KB
- HIGH/LOW/TYPICAL Bitrates: 3,747/2,319/2,852 Kbs
No I didn't use any filters.
What's KK?
BTW AutoQMatEnc takes longer than CCE & HC. 158 mins -v- 113 mins.
techreactor
30th January 2007, 10:39
Well the BR are decent enough, no need to use QmatOp with these. HC would be faster than AQM under these BR's since the crux of using AQM is with low BR's and yes, QmatOp does add a considerable time to the encode.
KK is king kong, it was nearing 51% compression but with lower avg bitrates than 2k.
therat
30th January 2007, 10:50
Fair enough. The Godfather is a much older movie without the special effects and action sequences of modern day movies, so that would explain the bitrates.
gizzin
31st January 2007, 04:07
I didn't realize how good your processor was therat. But it makes sense now. I really wish I never bought a asus board they are really sh*tty.
vBulletin® v3.8.5, Copyright ©2000-2012, Jelsoft Enterprises Ltd.