HC or CCE - which is the better companion?

I must have been half asleep earlier, and posted something similar in the DVD-R Advanced section.

Anyway...

I have heard lots to support both HC and CCE, to go along with Rebuilder.

HC is native to it, but I am told that CCE produces comparable results and is faster.

Would the native interaction of HC or the greater speed of CCE, the comparable results in mind, be better?

Are the results comparable?

Money and time aside, which companion do you favour and why?

Thanks.

 

Money and time aside (we are not talking much money here, $49 - $58 for CCE Basic), I opt for CCE. Both produce excellent results, but CCE's edge in speed wins me over. I must admit, however, that since my new build, I haven't used HC with "multiple encoder processes" enabled. Maybe someone has some times to compare with a Core2Duo processor in their rig. I'll try to make a few comparisons in the next few days.

 

Check my sig for encoder/transcoder comparisons...hope it helps some. HC is great, but slow compared to CCE, especially since I have a single core processor. My vote is for CCE, but I suggest downloading the trial and do a couple of test runs for yourself, nobody is going to be a better judge of what you like more than you.

 

Well put, ebega. I was looking for that thread earlier. Excellent info!!! I may do a movie or two with HC and CCE to give him/her an idea of the time differences...

 

Brass tacks: HC took almost an hour longer, using your example, unless I misread something.

Do you feel it is that much better, to justify an hour?

I have a DVD-9 that I want to backup and remove the region coding on (this I have no problem with), crunching it down to a DVD-5. I'd like to do this for a friend who is quite discerning.

We can all be wise when looking at stills, but could you tell there was a difference when the images were moving?

 

Honestly, I couldn't tell a huge difference in moving picture comparisons, but I would have to say that the edge for both quality and speed go to CCE. Like I said before, just download a trial of CCE and give it a go, but IMHO, CCE would probably be the best bet if you are not concerned about spending the $60 (or so) for it.

 

As promised. (Source file is 7.64GB; full disc; menu encoding enabled; multiple encoder processes enabled; HC- best quality; CCE- 2 passes; output to ISO) HC Encoder version is 19.0.1 (I don't know how much faster version 20 is, sorry. Should have upgraded first.) CCE is version SP 2.67. CCE is almost 50% faster. Quality is virtually indinstinguishable between the two.


[16:36:53] Phase I, PREPARATION started.
- DVD-RB v1.23.1
- AVISYNTH 2.5.6.0
- HC encoder selected
- Source: BLOOD DIAMOND
- VTS_01: 3,927,965 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 210,679 frames.
-- Building .AVS and .ECL files
- VTS_02: 78,297 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 8,134 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 59.2%
- Overall Bitrate : 4,184/3,347Kbs
- Space for Video : 3,728,972KB
- HIGH/LOW/TYPICAL Bitrates: 8,808/1,805/3,347 Kbs
[16:39:11] Phase I, PREPARATION completed in 3 minutes.
[16:39:11] 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
- Creating M2V for VTS_01 segment 30
- Creating M2V for VTS_01 segment 31
- Creating M2V for VTS_01 segment 32
- Creating M2V for VTS_01 segment 33
- Creating M2V for VTS_01 segment 34
- Creating M2V for VTS_01 segment 35
- Creating M2V for VTS_01 segment 36
- Creating M2V for VTS_01 segment 37
- Creating M2V for VTS_02 segment 0
- Creating M2V for VTS_02 segment 1
- Creating M2V for VTS_02 segment 2
- Extracting STILLS for VTS_02 segment 3
[17:40:21] Phase II ENCODING completed in 61 minutes.
[17:40:21] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 2 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 3 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 4 VOBID 5 CELLID 1
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 5 VOBID 6 CELLID 1
- Rebuilding seg 6 VOBID 6 CELLID 2
- Rebuilding seg 7 VOBID 6 CELLID 3
- Rebuilding seg 8 VOBID 6 CELLID 4
- Rebuilding seg 9 VOBID 6 CELLID 5
- Rebuilding seg 10 VOBID 6 CELLID 6
- Rebuilding seg 11 VOBID 6 CELLID 7
- Rebuilding seg 12 VOBID 6 CELLID 8
- Rebuilding seg 13 VOBID 6 CELLID 9
- Rebuilding seg 14 VOBID 6 CELLID 10
- Rebuilding seg 15 VOBID 6 CELLID 11
- Rebuilding seg 16 VOBID 6 CELLID 12
- Rebuilding seg 17 VOBID 6 CELLID 13
- Rebuilding seg 18 VOBID 6 CELLID 14
- Rebuilding seg 19 VOBID 6 CELLID 15
- Rebuilding seg 20 VOBID 6 CELLID 16
- Rebuilding seg 21 VOBID 6 CELLID 17
- Updating NAVPACKS for VOBID_06
- Rebuilding seg 22 VOBID 7 CELLID 1
- Rebuilding seg 23 VOBID 7 CELLID 2
- Rebuilding seg 24 VOBID 7 CELLID 3
- Rebuilding seg 25 VOBID 7 CELLID 4
- Rebuilding seg 26 VOBID 7 CELLID 5
- Rebuilding seg 27 VOBID 7 CELLID 6
- Rebuilding seg 28 VOBID 7 CELLID 7
- Rebuilding seg 29 VOBID 7 CELLID 8
- Rebuilding seg 30 VOBID 7 CELLID 9
- Rebuilding seg 31 VOBID 7 CELLID 10
- Rebuilding seg 32 VOBID 7 CELLID 11
- Rebuilding seg 33 VOBID 7 CELLID 12
- Rebuilding seg 34 VOBID 7 CELLID 13
- Rebuilding seg 35 VOBID 7 CELLID 14
- Rebuilding seg 36 VOBID 7 CELLID 15
- Rebuilding seg 37 VOBID 7 CELLID 16
- Updating NAVPACKS for VOBID_07
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Processing VTS_02
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 2 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 3 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_02_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
- Building ISO Image...
- Removing DVD files
- ISO Image successfully created.
[17:52:07] Phase III, REBUILD completed in 12 minutes.

Done.
[17:52:07] PREPARE/ENCODE/REBUILD completed in 76 min.
[17:52:07] One Click encoding activated...
-----------------
[17:52:07] Phase I, PREPARATION started.
- DVD-RB v1.23.1
- AVISYNTH 2.5.6.0
- CCE 2.62+ encoder selected.
- Source: BLOOD DIAMOND
- VTS_01: 3,927,965 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 210,679 frames.
-- Building .AVS and .ECL files
- VTS_02: 78,297 sectors.
-- Scanning and writing .D2V & .AVS files
-- Processed 8,134 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 59.2%
- Overall Bitrate : 4,184/3,347Kbs
- Space for Video : 3,728,972KB
- HIGH/LOW/TYPICAL Bitrates: 8,808/1,805/3,347 Kbs
[17:54:28] Phase I, PREPARATION completed in 2 minutes.
[17:54:28] 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
- Creating M2V for VTS_01 segment 30
- Creating M2V for VTS_01 segment 31
- Creating M2V for VTS_01 segment 32
- Creating M2V for VTS_01 segment 33
- Creating M2V for VTS_01 segment 34
- Creating M2V for VTS_01 segment 35
- Creating M2V for VTS_01 segment 36
- Creating M2V for VTS_01 segment 37
- Creating M2V for VTS_02 segment 0
- Creating M2V for VTS_02 segment 1
- Creating M2V for VTS_02 segment 2
- Extracting STILLS for VTS_02 segment 3
[18:34:01] Phase II ENCODING completed in 40 minutes.
[18:34:01] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 2 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 3 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Rebuilding seg 4 VOBID 5 CELLID 1
- Updating NAVPACKS for VOBID_05
- Rebuilding seg 5 VOBID 6 CELLID 1
- Rebuilding seg 6 VOBID 6 CELLID 2
- Rebuilding seg 7 VOBID 6 CELLID 3
- Rebuilding seg 8 VOBID 6 CELLID 4
- Rebuilding seg 9 VOBID 6 CELLID 5
- Rebuilding seg 10 VOBID 6 CELLID 6
- Rebuilding seg 11 VOBID 6 CELLID 7
- Rebuilding seg 12 VOBID 6 CELLID 8
- Rebuilding seg 13 VOBID 6 CELLID 9
- Rebuilding seg 14 VOBID 6 CELLID 10
- Rebuilding seg 15 VOBID 6 CELLID 11
- Rebuilding seg 16 VOBID 6 CELLID 12
- Rebuilding seg 17 VOBID 6 CELLID 13
- Rebuilding seg 18 VOBID 6 CELLID 14
- Rebuilding seg 19 VOBID 6 CELLID 15
- Rebuilding seg 20 VOBID 6 CELLID 16
- Rebuilding seg 21 VOBID 6 CELLID 17
- Updating NAVPACKS for VOBID_06
- Rebuilding seg 22 VOBID 7 CELLID 1
- Rebuilding seg 23 VOBID 7 CELLID 2
- Rebuilding seg 24 VOBID 7 CELLID 3
- Rebuilding seg 25 VOBID 7 CELLID 4
- Rebuilding seg 26 VOBID 7 CELLID 5
- Rebuilding seg 27 VOBID 7 CELLID 6
- Rebuilding seg 28 VOBID 7 CELLID 7
- Rebuilding seg 29 VOBID 7 CELLID 8
- Rebuilding seg 30 VOBID 7 CELLID 9
- Rebuilding seg 31 VOBID 7 CELLID 10
- Rebuilding seg 32 VOBID 7 CELLID 11
- Rebuilding seg 33 VOBID 7 CELLID 12
- Rebuilding seg 34 VOBID 7 CELLID 13
- Rebuilding seg 35 VOBID 7 CELLID 14
- Rebuilding seg 36 VOBID 7 CELLID 15
- Rebuilding seg 37 VOBID 7 CELLID 16
- Updating NAVPACKS for VOBID_07
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
- Processing VTS_02
- Reading/processing TMAP table...
- Rebuilding seg 0 VOBID 1 CELLID 1
- Updating NAVPACKS for VOBID_01
- Rebuilding seg 1 VOBID 2 CELLID 1
- Updating NAVPACKS for VOBID_02
- Rebuilding seg 2 VOBID 3 CELLID 1
- Updating NAVPACKS for VOBID_03
- Rebuilding seg 3 VOBID 4 CELLID 1
- Updating NAVPACKS for VOBID_04
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_02_0.IFO
- Updating TMAP table...
- Correcting VTS Sectors...
- Building ISO Image...
- Removing DVD files
- ISO Image successfully created.
[18:46:05] Phase III, REBUILD completed in 12 minutes.

Done.
[18:46:05] PREPARE/ENCODE/REBUILD completed in 54 min.

BATCH SUMMARY

 

So CCE is quicker. We knew that, as ebega had already directed readers towards the comparison link in his signature. Speed is not the issue. Quality is (and whether the faster can match the quality of the slower). You had already spoken of quality, albeit briefly, so I am not quite sure what that post was for.

 

The point of that post was to quell my, and other's, curiousity as to whether HC with multiple processes had closed the "time" gap any... I haven't used HC in about a year...

 

Ok. Which are the lines that indicate how many passes each was set to?

You seem to like testing, so it would be interesting to see how older versions of HC have progressed.

 

i have seen the same results time and time again, when speaking of quality output, CCE and HC are iqual, yes CCE is faster but HC is free so take your pick. i hardly use rebuilder because i don't owned a big TV,35' but, the times i have use it, it is been with HC and i can tell you, there is no need to pay for a encoder, HC quality is great.

 

I have seen responses, on another forum, that have preferred HC for quality. I will most probably start with it and see what happens.

This issue has more or less been exhausted, so thanks.

 

Glad to see your going to use your computer time to do some of your own testing. Our opinions on the matter can only go so far, and I still suggest you encode a movie using both encoders and decide for yourself, that will probably be the only way you are going to get a definitive answer.

 

HC produces a better picture for movies that have a low bit rate compared to CCE, but as Ebega suggested doing some comparisons for yourself is the best way to go.

Note: This is IMO only. ;-)

 

Normally I would, but I have heard enough folks - on another forum and whose opinions I trust - go for HC. I just wanted to see the counter-thoughts / stances. Much appreciated.

That's all the info needed, thanks.

 

HC does indeed close the time gap, but as we all know CCE is natively SMP ready (Dual threaded)and has an advantage there and also with quality in my view. HC is a great freeware encoder and in time it might even rise to the top but for now in this debate, CCE is supreme. For those who are really into testing give Canoppus procoder a try as well. On interlaced video you won't be disappoiinted except for speed. It too can be ran using multiple processes.

 

Great, but I will be going with HC for starters. I have heard plenty of worthy support for it.

I have enough info on the differences, thanks. Subject done!

 

jlrm365

I wasn't debating with you, I was merely answering your original question.

Actually HC is not native to Rebuilder, we were all testing RB with CCE for a year or more before HC came along.

That doesn't mean however that I would argue against your interest in using HC instead of CCE. It's both good and free and that should be enough for anyone who supports it. I know that jdobbs does! But as far as I know he does most if not all of his original testing with CCE.

 

The question had been answered, as far as it needed to be. I have more than enough information, which is a good thing.

Thanks, but I have chosen to go with the opinions of another set of users on another forum and chose HC.

As before, all questions have been answered and no more need be added.

Thanks.

 

The question might have been answered in your mind, but perhaps not in the minds of others who are still following this thread. I wish you well on your journey of discovery. I am certain that the unmentioned forum where you've found success has served your needs well, but as long as this source of success remains unnamed you will stand alone in its benefits.

All knowledge us cumulative!