Hmmm.. Seems a strange one. I can see nothing wrong with your log. This problem is usually about ARC not finding the correct version of xvid. Or that xvid has somehow got corrupted.
I note that the time for the encode is in excess of 7 hours. This is an abnormally long time. What are the specs of your machine so I can determine whether it has a problem or not.
A new AviReComp V1.4.1 is now available perhaps you would like to update.
To ensure that xvid is correctly installed follow these steps. Their should be no need to reboot your machine but it doesn't hurt if you wish to. Uninstall current ARC. Uninstall current xvid. Use Search to find xvid in C:\WINDOWS\system32 if any instances of xvid components are found then delete them. OK now you have a clean sheet to start with: Install ARC Install xvid - make sure to install xvid to it's default location or you will have file size issues.
Try the recompress again and let us know what happens.
I am a little intrigued as to why you want a file of 702meg as opposed to 700meg. Xvid is rarely that accurate. regards..
jrfer.
Virgin Media are to send all your browsing data through Phorm. Find out why this is wrong at
Thanks for your fast reply. I have uninstalled ARC 1.4.0, Xvid (no leftovers in System32 directory) and AviSynth, then restarted the computer and installed ARC 1.4.1 with all its components to their default location and with their default settings, except for SubVob, for which I have selected all the checkboxes during installation.
The computer is an AMD Athlon XP 2000+ (1.7Ghz) with 512MB of RAM.
I chose 702MB because the original file size was 701.46MB, and I wanted to retain the same video quality. Was this not the right thing to do?
In any case, I'm recompressing again now, and will post the result in about 7 hours.
I have avisynthe and vobsub installed in their own folders so there is no need to uninstall/reinstall them if you update ARC unless they have been updated. Of course there is no harm if you wish to do it your way, just a little extra work.
I see your computer is a little underpowered by todays standards and could maybe benefit from some more RAM but I feel it should be quicker than it is.
I have a 3gig HT machine which is itself getting a little past it but nevertheless manages a similar re-compress in about 90 minutes. So I feel your machine should manage it a lot quicker than it is running it at the moment.
Is your machine free of spyware, malware and/or virus and is it regularly defragged? Are you running many apps that are auto starting and slowing your machine to a crawl. I am wondering if a lack of optimisation is causing your file sizing problems.
If the original file had a bit rate of 800 or above (a rough estimate for a movie to run reasonably well) then a size of 700MB would have been fine. An odd megabyte here or there doesn't make much difference one way or another.
Feel free to ask if you need any assistance to optimise your machine. regards..
jrfer.
Virgin Media are to send all your browsing data through Phorm. Find out why this is wrong at
Heh, thanks for being gentle in your assessment. This is actually my secondary computer, used for testing. It is a clean machine with only the operating system, antivirus and firewall.
Unfortunately, the movie file ended up being too big again (754MB). I'll send you the movie info in private message so you could try it on your computer. It's a free movie available on the Internet. movie_new_avi_recomp.log
The source is just of low quality, grainy stock that doesn't compress well. The movie was probably produced on a very tight budget.
Not a problem with ARC, VDM or xvid but nevertheless interesting.
We did learn that ARC is not detecting the divx codec correctly with regards to the divx version. Not a biggie but something to correct in a future version of ARC. regards..
jrfer.
Virgin Media are to send all your browsing data through Phorm. Find out why this is wrong at
