Does VidCoder.exe 64-bit is using all cores in CPU or HDD is slow?

[WuxiIxuw]

Thanks for your help.
Please I've recorded a video for the whole process and what system monitoring says as well in the attached video.

http://www.youtube.com/watch?v=dmXu06nC2Jw&hd=1
Choose HD quality.
I think that HDD maybe the reason for this slow performance if I am not mistaken.
So please tell me your opinion regarding this issue and shall I go for the SSD option 1st before go to xeon.
So what kind of a Motherboard I should stick to in case I will buy a SSD drive and does the brand vary or all are the same?
I will buy the biggest size of course which is 256 GB as far as I know.
Or I am still need a higher level CPU like faster CPU or a xeon?
Thanks a lot and too much appreciated

[Slipster]

I'd be inclined to run the CrystalDiskMark HDD benchmark on your hard drive before assuming it's the bottleneck.

[jman98]

The "my encodes are too slow" problem can almost never be solved by a faster disk drive. Almost always this is a CPU issue.

[WuxiIxuw]

here it is:
attached.

[Slipster]

Those figures are pretty much what I'd expect to see from a typical healthy drive. I don't know what's causing your problem, but it's definitely not your hard drive unless it's incredibly badly fragmented.

You could try running MyDefrag on all partitions to see if it helps. It certainly won't do any harm and will give you something to try until other suggestions arrive.

[WuxiIxuw]

Those figures are pretty much what I'd expect to see from a typical healthy drive. I don't know what's causing your problem, but it's definitely not your hard drive unless it's incredibly badly fragmented.

You could try running MyDefrag on all partitions to see if it helps. It certainly won't do any harm and will give you something to try until other suggestions arrive.

So you mean that the current HDD is good enough and nothing wrong with it?
But the question still why the CPU is only using a few part of the cpu power?
While the application is using all cpu cores and all cpu threads?

[jagabo]

As jman98 said, the hard drive speed is almost never a problem. Only when you work with uncompressed, or losslessly compressed video does the drive speed really become an issue.

What codec are you encoding with? x264 (used by handbrake) is well multithreaded but most MPEG 2 and MPEG 4 encoders are not. I've never used ffmpeg's MPEG 2 and MPEG 4 encoders but I would guess they are not well multithreaded and won't be able to take full advantage of an 8 thread PC.

[poisondeathray]

There might be other processing bottlenecks. eg.. are you deinterlacing, resizing? any filters are potential bottlenecks

[WuxiIxuw]

As jman98 said, the hard drive speed is almost never a problem. Only when you work with uncompressed, or losslessly compressed video does the drive speed really become an issue.

What codec are you encoding with? x264 (used by handbrake) is well multithreaded but most MPEG 2 and MPEG 4 encoders are not. I've never used ffmpeg's MPEG 2 and MPEG 4 encoders but I would guess they are not well multithreaded and won't be able to take full advantage of an 8 thread PC.

The source file is .TS or .MPEG-2
Both types are resulted from PCI sattalete capturing using DVB-S2 Tevii-420

There might be other processing bottlenecks. eg.. are you deinterlacing, resizing? any filters are potential bottlenecks

• 
• 
• 
• 
• 

[wulf109]

Try HWiNH032 to check your CPU useage is. It should be 95-100% during encode.

[WuxiIxuw]

x264 FHD Benchmark

Intel Core i7-2600K @ 3.39GHz ( 4C / 8T )

x264 0.119.2106kMod 07efeb4
(libswscale 2.1.0)
(libavformat 53.17.0)
(ffmpegsource 2.16.2.1)
built by Komisar on Oct 23 2011, gcc: 4.4.7 20110720 (prerelease) (x86_64.generic.Komisar)
configuration: --bit-depth=8 --chroma-format=all
x264 license: GPL version 2 or later
libswscale/libavformat/ffmpegsource license: GPL version 2 or later

&
ffms [info]: 1920x1080p 1:1 @ 50/1 fps (vfr)
x264 [info]: using SAR=1/1
x264 [info]: using cpu capabilities: MMX2 SSE2Fast SSSE3 FastShuffle SSE4.2 AVX
x264 [info]: profile High, level 4.2
x264 [info]: cabac=1 ref=3 deblock=1:0:0 analyse=0x3:0x113 me=hex subme=7 psy=1 fade_compensate=0.00 psy_rd=1.00:0.00 mixed_ref=1 me_range=16 chroma_me=1 trellis=1 8x8dct=1 cqm=0 deadzone=21,11 fast_pskip=1 chroma_qp_offset=-2 threads=12 sliced_threads=0 nr=0 decimate=1 interlaced=0 bluray_compat=0 constrained_intra=0 bframes=3 b_pyramid=2 b_adapt=1 b_bias=0 direct=1 weightb=1 open_gop=0 weightp=2 keyint=250 keyint_min=25 scenecut=40 intra_refresh=0 rc_lookahead=40 rc=crf mbtree=1 crf=23.0000 qcomp=0.60 qpmin=0 qpmax=69 qpstep=4 ip_ratio=1.40 aq=1:1.00
x264 [info]: started at Sat Aug 25 21:52:09 2012

x264 [info]: frame I:10 Avg QP:25.24 size:293382
x264 [info]: frame P:1242 Avg QP:28.43 size: 90351
x264 [info]: frame B:1248 Avg QP:31.32 size: 19907
x264 [info]: consecutive B-frames: 8.7% 66.6% 23.2% 1.6%
x264 [info]: mb I I16..4: 3.6% 76.6% 19.8%
x264 [info]: mb P I16..4: 0.1% 4.7% 0.8% P16..4: 38.2% 25.5% 16.0% 0.0% 0.0% skip:14.7%
x264 [info]: mb B I16..4: 0.0% 0.4% 0.0% B16..8: 48.1% 6.2% 1.9% direct: 4.2% skip:39.1% L0:36.0% L1:49.9% BI:14.1%
x264 [info]: 8x8 transform intra:83.2% inter:58.4%
x264 [info]: coded y,uvDC,uvAC intra: 90.8% 82.8% 56.9% inter: 30.4% 19.6% 4.0%
x264 [info]: i16 v,h,dc,p: 17% 37% 10% 36%
x264 [info]: i8 v,h,dc,ddl,ddr,vr,hd,vl,hu: 11% 25% 16% 5% 7% 6% 12% 6% 12%
x264 [info]: i4 v,h,dc,ddl,ddr,vr,hd,vl,hu: 15% 21% 13% 7% 8% 7% 11% 7% 11%
x264 [info]: i8c dc,h,v,p: 52% 26% 15% 7%
x264 [info]: Weighted P-Frames: Y:1.0% UV:0.1%
x264 [info]: ref P L0: 70.4% 21.8% 5.9% 2.0% 0.0%
x264 [info]: ref B L0: 90.8% 7.8% 1.4%
x264 [info]: ref B L1: 95.6% 4.4%
x264 [info]: kb/s:22399.00

encoded 2500 frames, 23.99 fps, 22399.00 kb/s

x264 [info]: ended at Sat Aug 25 21:53:54 2012
x264 [info]: encoding duration 0:01:45

Verification Code: 22A6113A5F65565D1134606356115A281E232721213C113111 241F242A38396B11191125341120112945111A113E3E492311 4444362337526465114444443624113752646544596657575D 5611444436251F23113247492C6923272511211F22222A1F23 2221275C3E605511212856575653252CFB565F546055565511 23262121115763525E56641D1123241F2A2A115761641D1123 23242A2A1F2121115C532064

[WuxiIxuw]

Try HWiNH032 to check your CPU useage is. It should be 95-100% during encode.

Why google shows no result for it?
Please link.

[wulf109]

http://www.hwinfo.com/download32.html

[WuxiIxuw]

http://www.hwinfo.com/download32.html

You mean

[wulf109]

No,program opens with a small box,select sensor only.

[WuxiIxuw]

http://www.hwinfo.com/download32.html

this is in idle

[wulf109]

When you open the program there's a small box,check sensor only and click on run, ver 3.96. I'm running Vidcoder now and getting 99-100% utilization at 52fps converting a BR 1920x1080 to 1600x900. Running an I7-960 at 4.0ghz.

[WuxiIxuw]

here it is

[wulf109]

Can't open csv file.

[WuxiIxuw]

Can't open csv file.

please advise what shall I do?

[wulf109]

Have you opened the sensor only window?
I was running W7 and getting 50% utilization,I switched to XP and got 100%
Switch to AHCI mode on your SATA controller.
If your motherboard has a secondary SATA controller switch to it.

[WuxiIxuw]

Have you opened the sensor only window?.

Yes.

I was running W7 and getting 50% utilization,I switched to XP and got 100%.

You mean windows XP will be better? what about my extra 16 gb ddr3 memory?

Switch to AHCI mode on your SATA controller..

Where can I find it in the bios?

If your motherboard has a secondary SATA controller switch to it.

You mean the sata controller in the motherboard may be corrupted?

[WuxiIxuw]

I do not know what happened or what I did or what I installed, but all of the sudden I've found the CPU usage is 94-100% and what was suppose to consume 49 minutes now supposr to consume 14 minutes.
After I closed VidCoder and restart it I found everything get back to the old status with only 25-30% of CPU usage.
I am driving nuts and really this is driving me crazy and about to screw the whole machine, dame it!!!

[wulf109]

In my expierence W7 is slower than XP for video encoding. If your running W7 it should have AHCI drivers,but you have to enable it in BIOS. You enter BIOS during boot press delete. Your in BIOS,goto Integrated Peripherals and under SATA mode there should be an option to change to AHCI mode. If windows starts than the AHCI drivers are on your system. RAM increase won't help,if your running 4Ghz of RAM that's more than adequate. Video encoding is CPU dependant. Your running a 2600K at 3.4Ghz that's more than adequate. Hard drive speed will make no difference, SATA2,SATA3,SSD no difference. Although encoding to a separate physical HD might help a little.

[WuxiIxuw]

In my expierence W7 is slower than XP for video encoding. If your running W7 it should have AHCI drivers,but you have to enable it in BIOS. You enter BIOS during boot press delete. Your in BIOS,goto Integrated Peripherals and under SATA mode there should be an option to change to AHCI mode. If windows starts than the AHCI drivers are on your system. RAM increase won't help,if your running 4Ghz of RAM that's more than adequate. Video encoding is CPU dependant. Your running a 2600K at 3.4Ghz that's more than adequate. Hard drive speed will make no difference, SATA2,SATA3,SSD no difference. Although encoding to a separate physical HD might help a little.

Ok, I will try to use different HDD and this drivers issue as well and feed you back.

[WuxiIxuw]

Hello,
Just to update you with my latest info and after trying many things I've found that VidCoder is really using all cores of the CPU.

Also, what make it slow os fast will depend on exactly what kind of editing you will do like cropping and audio settings, ...etc.

But For almost all tried attemps I've found that using the same audio sample rate is the best option, and when I try to make it 44100 I've found it jump to take more time.

So Any one would like to use VidCoder (which is brilliant by the way) to decrease encoding time must not change the audio sample rate and even cropping or any other thing will not consume a lot of time.

Just in case any one may get use of these experience I passed by which really drive me nuts.

Also this will lead to almose use all CPU power.