Old AutoRV10 discussion (closed)

[calinb]

Originally posted by #2

Also I've noticed that the greater the percentage of a source I use the higher the 'Compressibility' results tend to be. Karl addressed this perfectly, but I'd like to submit my observations on the subject of bitrate and compressibility--I'm sure you'll find many opinions here in the forums, though :)

Whatever metric you choose to determine your bitrate, it will be imperfect. Compressibility tests merely enable you to compare a proposed bitrate against the maximum bitrate realized with a fixed or "standard" set of quantizer values. The perceived quality realized when encoding different sources at identical compressibility percentages, (identical fractions of the "standard" bitrate) varies tremendously. The Q used for the 1st pass is arbitrary too. Take a look at all the discussions of first pass quantizer selection against XVID encoder frame size when using high bitrate CQMs here in the doom9 forums. You'll get a feel for how inexact and arbitary any comp test can be. Bottom line: some videos look great at low percentages of the comp test and others look like crap.

Other metrics are probably no better or worse than a comp test. Because bitrate demands do not vary linearly with pixel count or framerate, no single metric or resulting value is perfect. (At least not the simple ones I've come across.) For example, some people use bits/pixel*frame, but this metric fails to account for the fact that bitrate requirements don't vary linearly with increasing framerate. A video inverse-telecined from 30 fps down to 24 fps needs more than 80% of the former bitrate, even though the framerate is only 80% of the original. A 30fps video that's frame doubled up to 60fps doesn't require twice the bitrate but, rather, only a somewhat higher bitrate is required. As a thought experiement, consider a framerate approaching infinity. Just because the framerate is huge, is more information present? No. But if you're encoding a bunch of noise or film grain, bitrate requirements just might nearly scale with framerate.

Other people use bits/pixel*sec as a metric to account for the fact that the "information" contained in a given video stream does not increase linerarly with framerate. (0.200 bits/pixel*frame is equivalent to 6.0 bits/pixel*sec at 30fps.) However, this metric probably errs in the other direction. Similarly, the bitrate requirements for different resolutions (more pixels) doesn't scale linearly with pixels. A 1280x720 video might look great at 0.200 bits/pixel*frame, but, if resized to 688x382 before encoding, it might require something closer to 0.250 or 0.300 bits/pixel*frame to look okay.

Rather than doing a comp test, I like to do a two-pass test encode, at my bitrate of choice, using 5% or 10% of the video I figure that the final video will look better, due to less frequent scene changes, as Karl described. If the test video looks good, I encode the entire video. If the quality compares unfavorably to the source, I either guess at a higher bitrate or run another test at a higher bitrate.

I'm interested in other thoughts or even technical discussions supporting my observations. Guess maybe I'm off-topic, given the general nature of my discusssion so we could move any additional discussion elsewhere too.

[#2]

Thanks calnib.

I think that although your thoughts can apply accross the board. I think they are very relevent here. As trying to find a metric ... to determine your bitrate Is essence of what I was asking.

So, at the moment, what you are saying is that we don't have clever enough automated process that will align its self consistantly with the 'continuium of human perceived visual quality'

That assumed what is best tool, combination of tools or procedure that we have available to us in the current video encodeing world, specifically applied to encoding RV streams with AutoRV10.

My reasoning for useing a Compression test is based on an assumption that producer seems pritty good psyco-visually at desciding where bits should go so why not ask it how many bits it would like. Please excuse my lay terms. ;)

I liked your own procudure of looking at a percentage of the source. For a trained eye this sounds great for desciding bit-rate and filter settings.

For my self one of the things I need is to be able to teach an automated metric to people with, initially, untrained eyes.

So in search of the best currently available automated metric or combo of such we can use to determine our bit-rate for RV streams in AutoRV10....

Under what conditions would you use a;

- Compression test.
- bits/pixel*frame metric.
- bits/pixel*sec metric.
- Is there another process or combo that hasn't been touched on yet?

Also from my previous post;

- If we are not too worried about exact final file size, just a Quality setting of around 70%. Could we not run a "One Pass VBR" or "One Pass Quality" encode? Or will it just not be as clever with its bit-rate redistribution and also end up with larger than nesessary files?

- Is "Max" quality still calculated with producer in quality=75 mode?

Cheers all. :)
#2

[Dark-Cracker]

hi,

sorry for my late answer but i don't have internet the week.

i will try to answer at all the questions :

@ #2

>Are there any more strings that I can use in the Settings.cfg file to change the defaults ...

for the moment the function who store the previous settings (setting.cfg) doesn't work , i will try to re-enable it for the next build :)


> Is "Max" quality still calculated with producer in quality=75 mode?

max quality is around quantizer 6 & 7 the first pass is made with a max quantizer restriction of 6 for i and p frame and 9 for b frame.
i don't know the quantizer mapping table but it should be around 75% & 80% of quality mode.

> - If we are not too worried about exact final file size, just a Quality setting of around 70%. Could we not run a "One Pass VBR" or "One Pass Quality" encode? Or will it just not be as clever with its bit-rate redistribution and also end up with larger than nesessary files?

* the 1pass quality mode is to encode you video with a fixed quantizer. (max and avg bitrate are ignored)
* the 1 pass VBR is when the codec try to have at the end of the encode the whishes average bitrate.
* the 1 pass CBR is when the codec is forced to encode a frame at a given bitrate. (max bitrate is ignored)

Bye.

[#2]

Cheers DC

So would a 1 pass VBR encode just potentially end up with a slightly over sized file or do we lose a lot in Quality with guessed bit rate distribution from the start to the end of the film?

A few other bugs(?) to report.

- Can't delete selected job in job list. It only deletes the first one in the list.
- Overflows after multipul Comp. tests. It seems to ignore max memmory usage. Particularly on a machine with no page file.
- Seems to get the decimal wrong ie. creates files that are about 10 x too small when the Quality settings is over 0.245 with Eternal Sunshine and over 0.567 with Dead Man. This happens on 2 machines and with many different filter and codec settings. And only with Video=SelectRangeEvery(Video,1400,14) AVS settings not with a full encode. (I am setting the file size 100 x smaller than a full encode for this 1% test encode)

I found these trying calinbs visual Comp. tests process. Thanks cal.

Hope that helps

#2

[Dark-Cracker]

Hi,

thank u for the bug report :)

can you explain me the overflow error ? is it an avisynth crash or do you have an VB error msg ? (try to post me the complete error msg , i think it should be somethink like error n°6).

i have a poor english and i am not sure to understand what is the 3th bug. could you plz explain me again and how to reproduce it.

thank you again to take the time to help me to debug this software :)

Bye.

[#2]

No problem DC.

- Run-time error "6": Overflow

- Run a two-pass test encode, with all your fliter and codec setting just like you were going to do a normal HD encode, but with Video=SelectRangeEvery(Video,1400,14) or Video=SelectRangeEvery(Video,140,14) added to the AVS in the 'Add job' dialogue.

Set the 'Quality' setting to something quite high eg. > 0.245 with Eternal Sunshine or > 0.567 with Dead Man.

Then reduce the final file size by a factor of 10 for Video=SelectRangeEvery(Video,140,14) or a factor of 100 for Video=SelectRangeEvery(Video,1400,14)

Be sure not to use end credit option.

So now if the 'Quality setting is > a certain point (different for each source, see above egs.) then the final file size ends up being about 10 x smaller than what you asked for. eg 2.6MB when you asked for a 26MB file size for say a Video=SelectRangeEvery(Video,1400,14) test encode.

Hope thats clearer

#2

[calinb]

Originally posted by #2
- Run-time error "6": Overflow#2 I was getting these errors until I installed the 12/23/2004 AutoRV10.exe. Now it only occurs if I prematurely terminate the producer command window, and that's not a problem.

What version are you using, #2? Also, sorry I haven't had time to give more thought to our compressiblity discussion.

[#2]

Hi Cal.

I'm useing the latest version and it only happens for after multipull Comp. tests. esp. on the machine I've got running no swap.

PS. If I 'end process' from the Task Manager rather than closeing the cmd. window I don't get overflows and loose all my settings.

And yes I would be interested in your thoughts on devloping a clever and clear process to help people new to the progy get in the ball park and on to the plate. ;) It seems to me you have a lot to offer there. I hear you're very busy.. so if the moment grabs you... :)


Cheers
#2

[Dark-Cracker]

hi,

thank you for the bug report :)

the bad news is that i can't reproduce the overflow error even when i terminate prematurely the application producer.exe , but i will continue to test to eraducate this error.

i will solve the "remove job" bug :)

for the bug with selectrangeevery i think it's not a bug.
when you add the line SelectRangeEvery(Video,140,14) it will only keep 10% of the movie, so if you encode the video with an ouput size of 700 MB , with the selectrangeevery line it will only keep 10% of the frames so at the end you will have a final filesize 10x lower.


Bye.

[#2]

Thats great DC.

Originaly posted by Dark-Cracker
the bad news is that i can't reproduce the overflow error even when i terminate prematurely the application producer.exe

Have you tried starting a Comp test and then closeing producers CMD window? Works for me on Win XP sp1 and sp2.

Originally posted by #2
(I am setting the file size 100 x smaller than a full encode for this 1% test encode)

Sorry I wish my French was better. ;)

eg.

DEAD MAN encode with SelectRangeEvery(video,1400,14) ie 1% of source;

Quality=0.153, Final File Size=9,993KB
Quality=0.245, Final File Size=16,167KB
Quality=0.337, Final File Size=22,345KB
Quality=0.490, Final File Size=32,659KB
Quality=0.536, Final File Size=35,765KB
Quality=0.567, Final File Size=37,830KB
Quality=0.597, Final File Size=1,627KB ???
Quality=0.613, Final File Size=1,627KB ???
Quality=0.766, Final File Size=1,627KB ???

This happens on every source I've tryed. When ever I use SelectRangeEvery. But not with full encodes.

What I do is set the Quality to say 0.150 and then for a SelectRangeEvery(video,1400,14) 1% encode I set the file size 100 x smaller than a full encode. ie delete the last 2 decimals. So my guess is it is some kind of out of range bug(?)

Cheers
#2

[Dark-Cracker]

hi,

thank you for the detailled post but could you plz add the "Desired FileSize" and the "Bitrate" in you previous post ?

ex : Quality=X.XXX, Final File Size=X,XXX KB, Desired File Size=XX MB, Bitrate=XXXX KBPS

if you could add the desired file size you have enter for each of your tests and the bitrate calculated by Autorv10 this will help me to know which setting put in the codec panel to reproduce this error and debug it.

For the comptest error it's perhaps because i use a personnal version of autorv10 and i have perhaps already solve this bug.

Bye.

[#2]

Sure DC. My Pleasure.

DEAD MAN encode with SelectRangeEvery(video,1400,14) ie 1% of source;

Quality=0.153, Bitrate=1193Kbps, Desired FileSize=1000MB, Final FileSize= 9,993KB
Quality=0.245, Bitrate=1908Kbps, Desired FileSize=1600MB, Final FileSize=16,167KB
Quality=0.337, Bitrate=2624Kbps, Desired FileSize=2200MB, Final FileSize=22,345KB
Quality=0.490, Bitrate=3816Kbps, Desired FileSize=3200MB, Final FileSize=32,659KB
Quality=0.536, Bitrate=4174Kbps, Desired FileSize=3500MB, Final FileSize=35,765KB
Quality=0.567, Bitrate=4413Kbps, Desired FileSize=3700MB, Final FileSize=37,830KB
Quality=0.597, Bitrate=4651Kbps, Desired FileSize=3900MB, Final FileSize= 1,627KB ???
Quality=0.613, Bitrate=4770Kbps, Desired FileSize=4000MB, Final FileSize= 1,627KB ???
Quality=0.766, Bitrate=5963Kbps, Desired FileSize=5000MB, Final FileSize= 1,627KB ???


NOTE:

-Remember to reduce your file size by 2 decilmals (1%) before starting the SelectRangeEvery(video,1400,14) encode. eg.
Quality=0.153, Bitrate=1193Kbps, Desired FileSize=1000MB, Final FileSize= 9,993KB
Would look like...
Quality=0.002, Bitrate=12Kbps, Desired FileSize=10MB, Final FileSize= 9,993KB
Before you start the encode.

-The bugging point is different for each source I've tested. eg.
Quality=>0.567 for Dead Man = Undersize Final FileSize.
Quality=>0.245 for Eternal Sunshine = Undersize Final FileSize.

Hope that helps.

[#2]

I find that for some sources certian crop settings make both a Comp. test and the encode fail. This only happens when 'Keep Cropped Resolution ' is ticked. (Yes the resoultions are both even numbers)

Eg. with a music video reacently if the left and right crop figures added up to 52 or over (eg. L=12,R=40) the producer windows would pop up and then immediatly close resulting in rmvb flies of arround 15-20Kb. I've attached one for you to have a look at.

I've tryed this with Avisynth 255 and the 2 latest alphas.

Hope that helps.

#2

[Dark-Cracker]

hi,

just a quick msg :) i am still in my courses at school (ADA is too boring :( ).

i have solve your previous bug , in fact i will give you a quick explination :

my altCC function doesn't scale the .pass file when the desiredsize file is above the maxfilesize it doesn't scale the file, i was thinking the rv10 will encode the file with the maxfilesize but instead it will lock the quantizer on max and you will have a little finalfilesize. but apparently when you scale above the maxfilesize the rv10 can still adjust the quantizer above the quantizer given during the first pass (by default : 9 for bf and 6 for pf).

the new bug seems to look like a bad modulo 4 when you crop the video. i will look during the weekend, for this problem.

feel free to post another bugs i will solve them as soon as possible.

Bye.

[Ultra_Immortal]

Damnit.

Every time I run the program and load up my .d2v file, it keeps on exiting so I can't do anything at all. I downloaded AutoRV10 straight. Is their anything I have to do to fix this problem.

Thanks.

[Dark-Cracker]

first be sure you are using the last beta (because i have some a bug similar to this previously).

if you are using an old version it surely the avisyntherror.dll who made this problem, rename it and i think it should stop to crash.

let me know if this solve your problem and if you have the latest autorv10 beta.

Bye.

[iradic]

HI

first sorry if this was answered before, i wasnt using your program since new 1.0 version...

so i wanted to try it now... and now i have some problems :)... after installing 1.0 version it errors me with no yv12 decompressor (although i have helix yv12 codec installed)... after updating with b7 it errors me that i dont have admin rights (i dont understand all this user things but im the only user on my winme ... so is autorv for winme or is this a bug or my fault)...

thans for help bye...

[Dark-Cracker]

what are your OS (win9X ?) ?

[tiki4]

winme = Windows Millennium edition, last in the Win9x series.

Cheers,

tiki4

[Dark-Cracker]

oups i have misread the previous msg :) i think the yv12 error msg and admin error msg are because the API are not the same on win9X and win2k/xp i will made some tests on a win98 and solve this problem.
i will let you know :)

thank u for the bug report.

++

[Ultra_Immortal]

When I 1st tried the program I used a .d2v file I made a while back for manual Xvid encoding. I am going to decrypt the DVD again how I am supposed to and give it another go and let you know what happens. ^_^


EDIT: Great it works. Thanks Dark-Cracker for trying to help me. ^_^

[mlmll]

Hi there,

I was looking for a way to rip easily into RV10 (within MKV would be a plus) and decided to give AutoRV10 a try.

Installed it, with the "Avisynth" install option checked. Then unzipped the v1.0 b7.1 update. Well, whenever I start AutoRV10, I get this message box :

You need avisynth v2.5.X !

on which I can only click OK, then AutoRV10 exits.

Couldn't find anything on it in the forums ; can sbd help please ?

TIA :)

[hellfred]

Originally posted by mlmll
Hi there,

I was looking for a way to rip easily into RV10 (within MKV would be a plus) and decided to give AutoRV10 a try.

Installed it, with the "Avisynth" install option checked. Then unzipped the v1.0 b7.1 update. Well, whenever I start AutoRV10, I get this message box :



on which I can only click OK, then AutoRV10 exits.

Couldn't find anything on it in the forums ; can sbd help please ?

TIA :)
Did you install avisynth on your computer, and a version that is at least 2.5.x?
AviSynth is a tool for filtering and frame serving, used by AutoRV10.
Homepage (http://www.avisynth.org/)

Hellfred

[mlmll]

Originally posted by hellfred
Did you install avisynth on your computer, and a version that is at least 2.5.x?
AviSynth is a tool for filtering and frame serving, used by AutoRV10.
Homepage (http://www.avisynth.org/)

Hellfred

Sure I did.
1. I had it with Gordiank Knot already
2. As I said, I check the option to install it wile installing AutoRV10
3. Afterwards, I also tried to install the standalone AviSynth, from their site.

MLL

[hellfred]

Originally posted by mlmll

2. As I said, I check the option to install it wile installing AutoRV10

Sorry, looks like i have missed that one. It's been a time since i last used AutoRV. Does one still have to run a batch-file to register the producer Activx? But i do not know who this could be related to the error message your have provided.
/me clueless noob

Hellfred

[Dark-Cracker]

hi,

the nsis installer is bugged and not always install correctly avisynth , even after install the standalone version v2.5.6(www.avisynth.org) you have this error ?

i will check this problem this weekend.

Bye.

[mlmll]

Originally posted by Dark-Cracker
hi,

the nsis installer is bugged and not always install correctly avisynth , even after install the standalone version v2.5.6(www.avisynth.org) you have this error ?

i will check this problem this weekend.

Bye.

OK, I'm sooo sorry. I said 3. Afterwards, I also tried to install the standalone AviSynth, from their site., but I was mistaken by the way the stuff is sorted on the SF download page (2.0 shows up first, you have to scroll to reach 2.5).

I now really downloaded AviSynth 2.5.5, and everything's OK.

In short, the problem was due to my stupidity and is now fixed. :)

[hubereevez]

I have the satsuki decoder pack

when trying to annalyse the movie :

"no suitable decompressor found"

why ?

thanks

hubert

[Dark-Cracker]

do you have the same error when you try to open the "manual crop" window ? can you made a preview of the .avs ?

it look like your OS doesn't have an RGB32 codec , what OS do u use ?

[hubereevez]

nope : all settings are fine.

I can crop, resize.

I can preview the .avs. Cannot open the .d2v with mpc either.

Just this strange error "with analyse it"

xp pr0 sp2

i send the avs file, but nothing strange in their, i gess.

# PLUGINS
LoadPlugin("J:\PROGRA~1\encodage\Autorv10\SOFTS\AVSFILE\DGDECODE.DLL")
LoadPlugin("J:\PROGRA~1\encodage\Autorv10\SOFTS\AVSFILE\COLORMATRIX.DLL")
LoadPlugin("J:\PROGRA~1\encodage\Autorv10\SOFTS\AVSFILE\UNDOT.DLL")
#
# VIDEO SOURCE
Video=Mpeg2Source("F:\encodage\ow\ow.d2v", idct=5 )
#
# CROPPING
Video=Crop(Video,0,12, -0, -8, align=true)
#
# RESIZING
Video=Hybridfupp(Video,720,384,preset="high")
#
# UNDOT FILTER
Video=UnDot(Video)
#
# KEEP MPEG2 Color Conversion
Video=ColorMatrix(Video)
#
# FINISH
Return(Video)

[Dark-Cracker]

ok i will speak with you later on msn :) but can u try this :

when you have the error msg (don't click on the ok button) go in the folder "x:\..\Autorv10\Softs\Analyse" and made a copy of the file temp.avs (or a name like this) and try to read it with MPC.

PS : do you open a .avs file or a .d2v file ?

if it's an .d2v input file, do you made an analyse before or after adding the job/editing the .avs ?

Bye.

[hubereevez]

tmps.avs :
LoadPlugin("xxxxxxxxxxx\Autorv10\SOFTS\AVSFILE\DGDECODE.DLL")
LoadPlugin("xxxxxxx\Autorv10\SOFTS\AVSFILE\DECOMB.DLL")

percentmovie=10

global sep="."
global combedthreshold=25

#---
function IsMoving(){global b = (diff < 1.0) ? false : true}
#---
function GetPercent(clip x, float percent) {return SelectRangeEvery(x, floor(16./(percent/100.)), 16)}
#---
function AnalyzeFile(clip c)
{
file="xxxxxxxxxxx\interlace.log"

global clip = c

c = WriteFile(c, file, "a", "sep", "b")
c = FrameEvaluate(c, "global a = IsCombed(clip,combedthreshold)")
c = FrameEvaluate(c, "IsMoving")
c = FrameEvaluate(c,"global diff = 0.50*YDifferenceFromPrevious(clip) + 0.25*UDifferenceFromPrevious(clip) + 0.25*VDifferenceFromPrevious(clip)")

return c
}
#---

v = mpeg2source("xxxxxxxxx.d2v")
v = GetPercent(v,percentmovie)
r = AnalyzeFile(v)
return r.Crop(0,0,8,8)

I open a .d2v file.
I made an analyse before adding the job/editing the avs; same error when analysing after

Ciya ++

hubert

[Dark-Cracker]

can you open this file tmp.avs with MPC or Vdub without problem ?

[hubereevez]

nope

[Dark-Cracker]

nope = no probleme ?

[hubereevez]

lol

no, I can't

I wonder why, I have all the dll

sorry

hubert

[Dark-Cracker]

if vdub or mpc can't open the script autorv10 should encounter the same problem.

it's strange the preview work but not the analyse. try to change the "percentmovie" at 100% to test and try to update your avisynth version, and the plugin.

i really don't know why it doesn't work.

++

[hubereevez]

100 % :same pb
avisynth 2.5.6 beta 1 : same pb
decomb521 : same pb
dgindex 1.2.0 rc2 + dgdecode.dll : not recognize by autorv10

when opening with vdubmod : "could'nt locate decompressor for format 'yv12' (unknown)

I did dl these yv1.2 either

:confused:

thks

hubert

EDIT : WORKs with latest binary from xvid installed!
:) lol
i need xvid to encode in rv10 mouhahahahahahha
yv12 $^*ù*ù$^*ù

[Wilbert]

i need xvid to encode in rv10 mouhahahahahahha
yv12 $^*ù*ù$^*ù
I don't know much about AutoRV10, but perhaps it needs a YV12 decoder (like VDub/VdubMod does) for previewing?

edit:
it's strange the preview work but not the analyse.
Hmm, ok, i didn't say anthing :)

[Dark-Cracker]

hi,

@hub
do you have the "Helix yv12" codec installed ? (normaly at start autorv10 made a check to see if the forCC yv12 is registered with a codec.)

++

[karl_lillevold]

Originally posted by Dark-Cracker
yes i think the 3.9 Gb problem come from the producer (limited at 4gb it's perhaps a safe limitation for fat32, it seems to me i have speak about this problem with karl and it seems to me it was a limitation for linux ??? but i will ask him again later).
I was encoding some HD content, and ran into the 4 GB problem myself. If you want to control the split size at a finer granularity than 4 GB, there is an option in Producer to start a new output file when the filesize reaches a certain size:


Destination File Roll Size (-drs)
Use the -drs option to set an file size limit in Megabytes that causes RealProducer to create a new output file. The section "File Rolling" explains how file rolling works. The following example sets a roll size of 20 Megabytes:

-drs 20


More details from Producer documentation:

File Rolling
File rolling allows you to create multiple RealMedia files for a single output clip. Each new file is appended with a number. The output clip movie.rm might be saved as movie.rm, movie1.rm, movie2.rm, and so on. Rolling happens automatically when the clip reaches the RealMedia file format limit (4 GB), or the maximum size allowed by the operating system:

2 or 4 Gigabytes on Windows
2 Gigabytes on Linux

You can also specify limits to the file size using the destinationRollSize property. A value of 30, for example, creates a new output clip from the file or live input when the current clip reaches 30 Megabytes in size.

====

I guess the main problem with multiple files is the delay when changing from file to file in a playlist, and it is always preferable to contain everything within one file. I should test the Producer -drs option more carefully to check for a/v sync and playlist changing delay...

[Yama4050242]

Erreur d'execution '9':
indice en dehors de la plage
what did this error message tell me?

[Dark-Cracker]

@Yama4050242
the message mean : "index out of range".

explain me when you have this error, all the steps to allow me to reproduce this bug and solve it.

++

[Yama4050242]

i am confused, it occured just now, and now, i can launch the program.
another problem on start the program is Erreur d' Execution '6' - Depassement de Capacite

they occured when i want to launch the pragram(i currently installed both autorv9 v1.3 and the latest autorv10 with updates for a smooth transition, and i also have the dvd2avi and the latest dgindex as well), i am using windows with sp2, amd64 3500+ 1g ram(dual channel), fx5900xt, and i found that the preview in the manual crop (when i dragged and view if it is clearly cropped) is too slow compared to autorv9 v1.3. it never happend when i use autorv9 v1.3 i drag for a small distance and no image is displayed, hope that colud be speedup

an unusual phenomenon is that after i installed autorv10, on the next startup, the computer config my Acrobat.exe automatically.

when using autorv9 v1.3, sometimes it asked me to insert my windows office cd and install something automatically as well.

[Dark-Cracker]

do you have install the autorv10 and autorv9 in the same folder ? (you should install them in separate folder and autorv9 use avisynth 2.0 whyle autorv10 use avisynth 2.5 who can't be installed simultany)

yes the preview will be speedup.

i don't know why it launch acrobat or office installation , autorv9/10 doesn't deal with such application or COM library.

i will release a build with some bug fixes this weekend.

++

[Yama4050242]

sure i installed autorv9 and autorv10 in differnt folders, and i onli use the manual crop from both, so i installed avs 2.55 myself, hope your next rlz will be more stable

[Valky]

Have anyone been able to encode dv-source with this tool?
Program crashes and gives some strange error for me.

[Dark-Cracker]

@valky
try to provide me a link with a dv sample and explain me when you have a crash ? is it producer or besweet or autorv10 who crash ?

if i can't reproduce bug i can't exterminate it :)

[Valky]

Actually I can't reproduce that error :)

But next time I will try to take screenshot.

[cypher_soundz]

To open d2v files made with the latest DGIndex i had to copy the latest version of dgdecode.dll to the autoRV10 directory and replace the file.
Regards
cyph