Encoding time longer ?

[QWERTZ]

I jsut finished encoding A.I. useing DivX 5.01 in VirtualDub for the first time.
It took me about 10 h for each pass. Normally a movie takes about 6 h for both passes on my system. I use a 1 gig athlon with 256 meg ram. Is this something new in DivX 5.01 or is it just this special movie ??

[DJ Bobo]

you may post your AVS-File and your DivX5 encoding settings and the length of the film...

[dragoman]

Hi,

I actually got a speed boost from 5.01.....

I have an Athlon 800, 448MB RAM

1st pass speed around 12-13fps....second pass 15-17fps

dragoman

[theReal]

I use a 1 gig athlon with 256 meg ram.
You might have to buy more memory. Especially avisynth eats up a lot of memory and 256MB might not be enough (I can get a RAM load of 220MB with avisynth and virtualdub even under win98SE).

I actually got a speed boost from 5.01.....
I have an Athlon 800, 448MB RAM
See what I mean?

[ErMonnezZa]

i just have the same problem u got! the first time i used divx50.1 all has been right..the second time i was waiting about 6 hours for the first pass but only after 10 hours i've seen the end of the pass...and is't normal since if i try to move the arrow on the screen during the encoding i see that it moves very slowly, like under windows was execing other weight programs...but they wasn't! i formatted one time for this reason but the problem is still there...after 2 encoding i see only bugs (maybe is it w98 second edition?)..if i reinstall divx5.0 i solve the problem..but i can't (with the old relase) see movies encoded with 5.01 codecs :(

my sistem is a Duron 900 with 256 mb ram...so the time to encoding is nearly your system...

anyone know the reason?? is a Codec Bug?

[Jaeuhl]

I have the problem, too. When I installed 5.01 my encodings suddenly had framerates of around 4fps. I the reinstalled 5.0 and now everything is normal again (which means framerates of around 13fps). My system: Athlon 1 Ghz 256 Ram

[Hardy]

I can confirm this, I had the same problem on a PIII/500/256MB with DivX 5.0.1, VDub, performance went down after some encodings and got worse and worse. ~7 frames/s in the beginning and about 3 frames in the end.
I also noticed that even with thread priority turned down to idle GUI speed slowed down and any other tasks could hardly be done with the computer.
After downgrading to 3.0 everything was OK again!
So I think it should be a bug within DivX?! I have posted the same problem on DivX forum but didn't get an answer yet.

[Mac Sidewinder]

I use 5.01 and constantly get frame rates of 14-22 depending on the encode. I have a 1.4Ghz pentium, 384 meg ram, 80Gb 7200 rpm drive, Nivida gforce 2 64Mb video. It doesn't seem to make much difference what priority I set the thread at. Most of my encodes (from rip to finish) take around 5 hours, using GKnot. An hour of that is ripping and using dvd2avi project to serve, so the actual encoding is around 4 hours.

Mac

[theReal]

From what you are all saying, it seems that everyone with more than 256MB RAM doesn't have any problems, while all who have problems have exactly 256MB RAM.
Check the memory load, maybe you need to buy more RAM for Divx 5.01

[trekminal]

I have using Divx5 some weeks, and 5.01 at this time. I use DVD2AVI and Vdub + VFAPI and no velocity changes for me.

[N_F]

My computer: Athlon 1300, 256 MB RAM, XP.

Encoding method: Smartripper, DVD2AVI, Goardian Knot, VirtualDub.

When I use smart deinterlacing from Goardian Knot my speed in VD is usually 9 fps on the first pass and 10-11 on the second pass (due to the mv-file). According to XP's Task Manager (or whatever the name is) VD uses about 80 MB RAM. I got the impression many of you encodes much faster with computer even slower than mine, but with more memory. But do you really think more memory would make any difference when VD only uses 80 MB?

[Alex_e_Basta]

@theReal
I can confirm the performances improvement increasing RAM.
When I installed divx 5.1 I increased RAM from 256KB to 512KB and I never got speed problems (a 15% improvement indeed).
In my system (AMD K7 1Ghz 512MB Win2K SP2), as Task Manager states, VD use approximately 300MB of RAM.
Encoding method: DVD2AVI, Avisynth, VirtualDub, Divx5.1pro, 2-pass.

Ciao.
Alex

[N_F]

@Alex_e_Basta
What fps do you usually get?

[Alex_e_Basta]

@N_F

This depends on resolution and MPEG4 parameters used . Approximately 10-12 fps in the first step and 12-16 in the second one.
Ciao.

Alex

[theReal]

But do you really think more memory would make any difference when VD only uses 80 MB?I think your problem here is that it only uses these 80MB RAM and not more. When I encode with avisynth frameserving to Vdub in Win98, VDub has a memory usage of ~160-220MB RAM (depending on filters). Never seen it using less than 160MB (it's avisynth which uses so much memory, VDub alone only takes about 20-30MB).

btw. just in case your wondering: I'm using using TaskInfo2000 to monitor processes and memory load in Win98, it's a pretty mighty and concise taskmonitor.

[ErMonnezZa]

I think it not depends by the ram..infact(as i wrote) the first times i encoded with divx 5.01 i haven't had any problem..the encoding speed was the same of using 5.0 ..the memory was the same(256) but only after two rips i sow the decrease of speed...and this strange effect of the mouse -harrow that during the encoding was very slow to translate in other parts of the screen...like as other application was running in background..:(

[theReal]

sounds like one of the encoding processes is set to normal or even higher priority (slow mouse movement).

I found the ditribution of CPU-power amongst the processes is best if you set VDub to idle priority.

Example: If VDub is set to high priority, it will take som 50% CPU power for the encoding process and leave only 50 percent for avisynth. That results in 10% being not used at all because avisynth cannot render fast enough with only 50% left.
With both processes set to idle, the distribution seems to work quite good.

Don't know if this helps, but maybe you changed the priority in Vdub for the last few encodes? Or maybe Divx 5.01 takes a higher priority than divx 5.0? I dunno.

[Hardy]

Originally posted by ErMonnezZa
I think it not depends by the ram..infact(as i wrote) the first times i encoded with divx 5.01 i haven't had any problem..the encoding speed was the same of using 5.0 ..the memory was the same(256) but only after two rips i sow the decrease of speed...and this strange effect of the mouse -harrow that during the encoding was very slow to translate in other parts of the screen...like as other application was running in background..:(

Yes, that's it! Exactly the same problem I have. And it's NOT dependent from the thread priority in VDub! Even when I turn it down to idle GUI gets so slow that I can't do any other things while encoding...:-(

[DivxBr]

I´m having the same trouble, today, when I try to encode in Divx 5.01 I get half of the encoding speed of the Divx 5.00 and a high priority job (that makes the mouse cursor do jumps) in the encoding process (even when Vdub is in IDLE).

May it be some kind of time-bomb in Divx 5.01???? It works for some time, then..... crash.... :( (or, some kind of virus, that only works in a specific day!!)

I tried to uninstall and install again the Divx 5.01, no change...

I installed back the Divx 5.00, so, all is ok now!!! (except from the fact that the Divx 5.01 encoding I made are not playable)....

Anyone already send this bug to the DXN guys???

[ErMonnezZa]

Originally posted by DivxBr


May it be some kind of time-bomb in Divx 5.01???? It works for some time, then..... crash.... :( (or, some kind of virus, that only works in a specific day!!)

I tried to uninstall and install again the Divx 5.01, no change...

I installed back the Divx 5.00, so, all is ok now!!! (except from the fact that the Divx 5.01 encoding I made are not playable)....

Anyone already send this bug to the DXN guys??? [/B]

Exactly the Same on My system, the install back of divx 5.0.. and the reinstall of divx 5.0 that refuse to work properly...i think the expression "kind of time-bomb?" is really appropriate to explain the problems i found.
what tell me about te arrow? (in high priority all application are very slow,and it is right,but the arrow have to be smooth on the screen and in the idle position too! instead i see a sort of interrupped flash..if u understand what i mean)

[Hardy]

Originally posted by DivxBr
Anyone already send this bug to the DXN guys???
Yes, I did it yesterday! No answer until now but a similar thread is running on http://www.divx.com/forums/viewtopic.php?forum=13&topic=32655

[theReal]

I'm really glad I haven't made any 5.01 encodings yet, so I can stick with 5.0

I did so because 5.01 wasn't working for me from the beginning. It gave me "wrong input format" errors. The strange thing about it was it gave me these errors about 2 of three times, with every kind of input video I tried (using VDub 1.4.10).

So... let's keep on waiting for the first stable release of Divx 5... maybe 5.02 will solve the problems...

[Wintermute]

I just hope it isn't some "feature" that kicks in if the spyware can't do its thing (i.e. blocked by firewall)...

[Mac Sidewinder]

Well I've done around 20 encodes now with 5.01 pro and haven't seen any problems with frame rate yet. I still get around 16-20 on the first pass and 18-22 on the second pass.

Mac

[N_F]

Originally posted by theReal
I think your problem here is that it only uses these 80MB RAM and not more. When I encode with avisynth frameserving to Vdub in Win98, VDub has a memory usage of ~160-220MB RAM (depending on filters). Never seen it using less than 160MB (it's avisynth which uses so much memory, VDub alone only takes about 20-30MB).

btw. just in case your wondering: I'm using using TaskInfo2000 to monitor processes and memory load in Win98, it's a pretty mighty and concise taskmonitor.


I should describe my encoding method more precise:

I first use Smartripper to rip the files to the harddrive. Then I use DVD2AVI to create a project and get the ac3-file. The ac3-file is encoded with Besweet. I then open the projectfile in Gordian Knot and fixes the approiate settings. Then I save an avs-file which I then open in VirtualDub for the actual encoding. This is pretty much the way Doom9 describes in his guide.

Exactly what do you mean when you say "avisynth frameserving"?

Are you doing your encodings very differently?

[ErMonnezZa]

..The FuC@@@ problem now is that divx 5.0 doesn't read movies encoded with divX 5.01!!!!:angry: :angry: :angry:
what i ask :why the developers of divx 5 didn't worked oon the performance of divx 3.11 that was really stable?

[Apfelstruhdl]

i think the ram problem is under win98 as it can only use up to 96mb of ram efficently. you will need a REAL operating system as nt or xp to use more than that amount of ram.

i didn't get any probs with 5.01 pro either.

:sly: :scared: :eek:

[N_F]

Originally posted by Apfelstruhdl
i think the ram problem is under win98 as it can only use up to 96mb of ram efficently. you will need a REAL operating system as nt or xp to use more than that amount of ram.

i didn't get any probs with 5.01 pro either.

:sly: :scared: :eek:

Was that directed at me? I'm using XP so I am using a "real" OS. :)

I should also add that this isn't specific to DivX 5.01. I have pretty much the same speed in all DivX versions and XviD.

Any other ideas?

[theReal]

i think the ram problem is under win98 as it can only use up to 96mb of ram efficently. you will need a REAL operating system as nt or xp to use more than that amount of ram. Without question Win2k or XP have better RAM management and performance, but it is not true that Win 98 can only use 96MB. Maybe it can only use 96MB for the OS components itself, but I have seen avisynth in combination with nandub using 230MB IN WIN 98 (I was using Taskinfo 2000 for monitoring which is way better even than the NT-based task-monitors).
I know the RAM performance suffers a bit in benchmarks compared to NT-based OS's, but it's not extreme and on the other hand you can turn off virtual memory which speeds up Win98SE quite a bit!

However, I rather have Win98SE with 512MB than Win2k or XP with only 256MB ;)

[theReal]

Exactly what do you mean when you say "avisynth frameserving"?

Opening your .avs file invokes avisynth which frameserves (or is it "serves frames"?) to the application (that is Virtualdub). The .avs file consists of commands that tell avisynth (a program installed with Gordianknot, but it has no GUI so you can't "see" it) how to resize and filter the vob-mpeg2 and convert it to avi. It does this frame by frame in realtime rather than saving an intermediate avi (which would be almost impossible because uncompressed avi is huge).

[N_F]

Ok... so my encodes are pretty much the same as yours... Damn this is annoying. :(