Old AutoRV10 discussion (closed)

[Dark-Cracker]

edit : i think i have found the bug.

[Doom9]

I guess I just don't know how AutoRV10 checks that but it is throwing a major fit on my machine:

When I install AutoRV with AviSynth, upon startup I get a "You need to install AviSynth 2.5.x" error message. And.. in fact I can no longer play may AviSynth files. So then I installed AviSynth 2.5.5 after AutoRV10 and now I get a "You need to install a YV12 decompressor". Needless to say that this is complete BS, my PC is perfectly capable of handling YV12 content and just in case I've installed the latest XviD build (and I know with certainty that XviD can handle YV12 decoding, and not only for XviD playback).

[Valky]

For the first time ever, I had this error too "You need to install a YV12 decompressor" when I was trying to start the app.
I know I dont need to install anything and I have not had any problems with earlier builds.

[Razorblade2000]

there is some helix community yv12 decompressor thingy bundeled with realanime... maybe that's what you need :D

[Doom9]

instead of having to install yet another real rip package, is there any chance you could post that decompressor for us to try? I'd much appreciate it and I'm sure valky would, too.

[Razorblade2000]

Kein Problem :D
I attached it, hope it's ok :D

edit: hmm... he DOES display something when I edit the post (Keep current attachment ( yuvcodecs.zip ))...
but it isn't visible for others 0_o
Does it have to be accepted by an admin/mod first?

[Doom9]

Does it have to be accepted by an admin/mod first?Yes it does. Thanks for posting. Too bad I can't try it right now as I'm encoding and I'm a bit afraid installing filters might have an adverse effect on that.

[hellfred]

I can help great mr doom9 himslef?
Great!
The Helix codec is available <drums rolling> in your very own forum (http://forum.doom9.org/showthread.php?s=&threadid=56972). It is a vfw codec, so maybe that is the problem with letting xvid do the colour scace transformation from th YV12 to the I420 colourspace.
I think I once tried to enable ffdshows raw decoding support in the vfw configuration, but i have forgotten weather that worked, too, or not. So you can check that one before installing any Helix binaries.

By the way, do you know some basic german?
Here (http://www.heise.de/newsticker/meldung/54377) is a link anouncing that Cyberlink (http://gocyberlink.com/english/index.jsp) has a
MPEG4 AVC encoder application (http://www.gocyberlink.com/english/cyberstore/product_order.jsp?ProdId=89) for sale.

Hellfred

[hellfred]

Damit, i was too slow :(
EDIT: No fame for me for helping doom9 himself :( :(
EDIT: Not even recieving any sign of attention by his Higness
*hellfred wanders off sobbing*
:D

[karl_lillevold]

I think D-C used to include the YV12 codec in his installer. Now it is simply listed as one of the three downloads on the first page in this thread. This probably indicates it would be a good idea to again include it in his installer. :)

[Dark-Cracker]

hi,

in fact the yv12 error msg is just a check on the registry key :

HKEY_LOCAL_MACHINE, "Software\Microsoft\Windows NT\CurrentVersion\Drivers32", "VIDC.YV12

i don't know exactely how avisynth react if it doesn't found an yv12 decompressor (i think i will try with YUV and if it fail it will try with RGB).
so to avoid problem of multiple colorspace conversion i have add a check on this registry key (installed when you install xvid or helixyv12 codec who will be included in the final installer). if someone know a better check to know if the yv12 colorspace will be correctely decompressed, let me know the tip.

for the avisynth error it's because my nsis script is bugged this will be solved with the next install script.

PS : a new build will be released soon, i will try to made it quickly if you need a binary soon.

++

[Doom9]

installed when you install xvid or helixyv12 codec who will be included in the final installerActually, I tried installing XviD. I already had Koepi's 1.1 build installed, then I tried Nic's and finally Koepi's 1.0.2 and I kept getting the same error. It'll be another 1.5 hours then I can try installing the real codec and see where that gets me.

[Dark-Cracker]

hi,

a quick build to fix the bugs reported from the beta 7.

link :
------
http://dark.pluridis.org/AutoRV10_v1.0_b7.1_update.zip

changelog :
-----------
- fix one little bug if the .pass is really huge
- fix bug with the maxbitrate when you use endcredits
- disbable the yv12 error msg (be sure you have an yv12 decompressor)
- add the new erv4.dll (latest RV10 codec dll)
- i have finaly add some code in my "exit buttons" :) :) :)

@doom9
plz use this build , i have also disable the yv12 error msg. else if you install the helixyv12 codec you will not have this error msg.

Bye.

Bye.

[Valky]

Things are working again, so thanks for this quick-fix.
I didn't have to intall any additional codecs (I know I had them anyway).




Hmm.. managed to get an error. Error number '13' 'type incompatible' or something like that.

edit: I found the problem. I was testing with very short video and I used the same script first with file limit 1mb (0.151bits) and next testing I didn't want to use 2mb cause this would have gave me too big 0.302 bits. Program accepted filelimit setting 1.5mb and it would have gave me 0.227 bits, but it always gave me that error when it should have started encoding.

This isn't a big issue cause people don't usually use that kind of filelimits but cause it accepted that value I thought it should work.

[Dark-Cracker]

hi,

i think you have got this error because you have try to enter a float number file size but with the wrong separator.

perhaps you have used the character "," instead of "." ?

i will add some check error in the textbox later :)

EDIT : in fact if you use the separator "." for the float it will not work you should use the comma "," so i think "1,5" should work.
i will try to fix this when i found a few minute :)

++

[Doom9]

@Dark-Cracker: thanks for the new build, though I'm already well into encoding.. I installed the codec to be done with it.

[Valky]

Originally posted by Dark-Cracker




EDIT : in fact if you use the separator "." for the float it will not work you should use the comma "," so i think "1,5" should work.
i will try to fix this when i found a few minute :)

++

Actually I tried with both separators, but when trying to use comma the value in bit-box didn't change like it did when using dot. That's why I thought I chose the right separator.

[Doom9]

I do have a feature suggestion: check the available space.. I just wasted the last 14 hours because I didn't check if there was enough HD space (serves me to use a notebook as encoding machine).. and not even realproducer aborted.. it simply wrote a 500mb file instead of a 1400mb one.

[Dark-Cracker]

@valky
it's perhaps because it search in the local setting the separator ( dot for english country and coma for european country), i will solve this bug for the next build :)

@doom9
yes you are right i think this option could be usefull , i have add it to my todolist.

EDIT : by curiosity do you use the Standard Curve compression or the AltCC option ?

Bye.

[Doom9]

EDIT : by curiosity do you use the Standard Curve compression or the AltCC option ?standard as suggested by karl

[Valky]

I was little bit surprised to see my final result was 6 mb oversized when target was 350 mb (dvd, ac3 audio). I have never had any problems before with this tool, but it was the first time I used this setting '100 insane'.

[Dark-Cracker]

hi,

yes it's strange, it's perhaps because you source is hard to compress, if you want you can try to re-do only the second pass (when you click on add job you can select the first .pass file and when it will ask if you want to keep the scaled value you answer NO) keep the same params but with a size lower else you can also disable the AltCC and use the Linear Scaling it will perhaps work more accurate.

Bye.

[ookzDVD]

@DC

To be honest, the AutoRV10 is the most complete & easy solution for DVD into RV at least for me. Two thumbs up for your program!

I wonder someday your program will be more similar like AutoGK which
does automatic field detection, automatic resize, etc.

No more manual work to do except ripping the DVD use the DVD Decrypter in IFO mode.

Thank you.

[Dark-Cracker]

hi,

@ookzDVD

thank u for you nice words :) i am always glad when i see my work is apreciated and usefull for other peoples :)

about the *auto* feature there is still a lot of room to improve them, for the moment i have add a "basic" frame analyser who detect the percent of FILM, Interlaced or telecined frame i think however hybrid material are not really well detected, for the resolution there is an auto-crop (who select the black bars / it analyse 5 frame to detect the correct values instead of using the autocrop avisynth filter), i have also work on a way to suggest the best resize resolution (once you have made a compressibility test it analyse the avg quatizer).
of course these functions are not perfect because it requiere a lot of time to made some tests and to find the correct threshold to use for an accurate result. i think len0x have spend a lot of time to made some tests, and in my case i don't have really much time to develop my softwares so for the moment i will try to improve other features (like a better subtitle support, DTS support, or improve ripping functions) and after i will try to improve this :)


Bye.

[#2]

Hi DC. Thanks also from me for this tool it has made my encoding life so much easyer. : )

Right now, with the latest beta, I'm getting my Favourite error again.

Settings: For LOTR-ROTK extended edition (2 DVDs).

-AMD optimisations
-PAL 16:9
-Anamorphic resise with keep croped resolution
-No Field filter (progressive source)
-removegrain
-Normal motion
-First pass higher complexity
-E.H.Q. 100
-Idle Process Priority

Heeps of space every where, NTFS, win XP SP1 and SP2. This has happened on 2 machines one with an output file size of 4680MB useing a single .d2v
and the other with 2 .d2v/jobs (finalsizes of around 2250MB)

Blade Runner went ok with very simmilar settings;

-Decomb Field filter
-finnalsize=1850MB

I'm going to try it now with the b7 /softs;/avs and the b6 exe;ini;cfg;dll

[Dark-Cracker]

hi,

i suggest you to test with the following :

- install the full version
http://dark.pluridis.org/downloads/Autorv10_v1.0.zip
- install the update beta 7.1
http://dark.pluridis.org/AutoRV10_v1.0_b7.1_update.zip
- install the fix (overwrite the old .exe with this new one)
http://dark.pluridis.org/AutoRV10_tmp.zip

the beta 7.1 have fix the overflow error msg when you have a big .pass file (=> when you have a long movie).

the third fixed .exe is to avoid overflow error when you use and ouput desired size bigger than 3072 mb.

some people who encode some hdtv movie for an output size of dvd (4489 mb) have report me this error and i think the third .exe have fixed this matter.

remember you can re-use the first stat .pass file this will avoid you to re-do the first pass.

in any case thank you for the bug report :)

PS : just in case : when you encode with an output size bigger than 2GB don't use endcredits else rmeditor will failed to open such bigger file.

PS2 : let me know if this solve you problem :)

PS3 : it's perhaps time for me to made a full working installer :)

Bye.

[ookzDVD]

@DC,

Thank you for your reply.

Glad to know you still have "energy" to improve your program :)

I know the "auto" feature is need more time to try and test
than time to program itself. :) But I believe someday you have
some time to make that happen! :)

I'm agree with you (like a better subtitle support, DTS support, or improve ripping functions) is in your priority.

Thank You.

[#2]

Wow. I really appreciate the speed of your work.

I thought you might like an up date.
The b6 attempts failed with the same error while your latest build worked flawlessly for the 2x 2250MB encode.The 'all in 1' 4680MB encode just finnished now and is split at 3.9G even though it was in a NTFS partition, a fail safe for fat32 I guess? Now all I have to do is figure out how to join a 3.9G file to a 690MB one. : )

BTW I'm really likeing the high quality encodes that you can get with 'Anamorphic resize' and 'keep cropped resolution'

Are there any other tweeks to my settings that I could be doing for these type of back ups? Any thing to the advanced codec settings? And correct me if I'm wrong but with 'keep cropped resolution' there is no resizeing done so Lancoz vs Bicubic would make no difference?

And thanks once again for your great tool.

[Dark-Cracker]

hi,

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 don't know how to made a such join (even if you move the file on a ntfs disk , rmeditor can't open file bigger than 2gb :( ) i think the best solution is to re-do the second pass with an output size of 3990 mb .

in anamorphic keep cropped res mode the filter resize is ignored.

i think some good time for such high encode could be :

AltCC with auto calc at light, and agressivity at Slow.
and i think a litte Xsharpen could improve slighthy the details.

i think there is no other *general* tweak to improve such HD encode :)

thank you for the bug report these fixes will be added in the next releases :)

Bye.

[#2]

Cheers DC I'll try those settings.

Another couple of Qs;

-With Xsharpen. If I'm useing 'removegrain' might I also use 'Reduce Noise Amplification' with a light Xsharpen? Or would that be more for lower bit rates?

-If I change my 'Curve Agression' from Medium to Slow can I still reuse my first pass file?

Thank you.

[calinb]

Originally posted by Dark-Cracker
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 don't know why there would be this limitation for Linux running any of the popular and modern filesystems.

I too am having much better results with your latest test build. One job, that previously had the error 6, completed. My 4489MB jobs are not yet finished, though. Great work, darkcracker :)

@ #2 - you might try to re-mux to matroska, or even ogm. Then try to read/append the files into vdubmod 1.5.10. I've had some luck using directstream copy to join mp4 ASP files this way. I'll let you know if a figure out a method.

[Dark-Cracker]

hi,

@#2
it's not needed to use "reduce noise amplification" with xsharpen for such hight bitrate :)

yes even if you change some tweak in the altCC you can still reuse you first pass (autorv10 write the *new* scaled frame size value in the .pass file without overwritting the original frame size, and when you re-use a first stat .pass file if autorv10 detect such a file was already scaled it will ask you if you want to keep these value or not, if you select not it will overwrite the .pass file without the scaled value and when it will start the second pass it will scaled the file with the AltCC settings, hum i hope it's enough clear even with my poor english :) ).

and i think the better solution to join the two file is to use mkvmerge and get an output matroska file (attention it will strip some rmvb information like chapters or tag, so if you have use them think to add them again in mkvmerge GUI).

PS : apparently realproducer have split you file in two part can you plz post the name of the 2 file ? (i think it have generate a name like xxx_20041220 by adding the date and perhaps time in the filename).

@calinb
happy to heard it work also for you :)
i am not sure if the previous realproducer were running under linux so perhaps if it's a start they have add a limitation and wait to fix it later. i will let you know if i found more information on this :)

PS : i think you have made some bigger backup so i am interested to know if you have encountered some filesize limitation/problems ?

Bye.

[#2]

Thanks Cal. I remuxed to .mkv with mkvmerge then used avimux to join and then mkvmerge to mux the audio. (Could possibly use AVIMux for the whole lot if your not useing an AAC audio stream)

During the encode I trimed the 2 black frames of the end of the first disc and the audio is in sync for the whole film. I must say I am pritty happy with the results. : )

For DC. My file names.
LOTR-ROTKallin1_Movie.rmvb
LOTR-ROTKallin1_Movie1.rmvb
Sorry no dates in them.

Re. the first pass file. I guess I should have asked which settings I should NOT change if I want the first pass file to still be worth useing to save time.

I'm guessing I can change any filters on the filters page but not resolution/cropping or frame count?

If I change the final file size then the first pass file will still save time? Just the output size will be over writen?

I'm not sure about changing the codec settings either; EHQ complexity, first pass complexity, advanced codec settings, dupe filter, black filter etc.

Cheers
#2

[Dark-Cracker]

>which settings I should NOT change if I want the first pass file to still be worth useing to save time.

when you open the first stat .pass file autorv10 check if the following params are correct :

- detect if the realvideo stat version file is correct.
- check if the number of frames is equal.
- check if the FPS is equal.
- check if the resolution is equal.

as soon as the following values stored in the .pass are equal at the input video you can re-use the .pass file. there is no check on the crop or the filter used, so you can change them (slightly) from the first pass to the second pass without *problem* (attention : filters change the compressibility so this can *potentially* disturb the bits redistribution for the second pass).

you can change final size, EHQ level, and AltCC params without problems.

"first pass EHQ" will be ignored because the first pass will be skipped because you re-use the .pass file :)

for the realvideo filters (like DropDupe and black filter) i think there is no problem too.

but in any case if you re-use a .pass file it's always better to reuse the same filters, and only change EHQ, final size and AltCC params.

Bye.

[IgorC]

i have a version 1.0.6 (downloading update right now) Does it use a last updated codec RV10?
i put in properties ¨Delete temporal files¨ but it didn´t delete them.

can anybody suggest me how enchased RV10 for high bitrate? 3-3.5 Mbits

Source: NTSC 29.9 fps 740x480 no noisy, most scences are high-motion.

[Dark-Cracker]

hi,

yes latest beta come with the new erv4.dll file (latest rv10 codec).
"delete tempory file" is not actually completely finished so it will work better in the futur releases :)

my personnal (i can't take responsability :) ) settings for HD encoding :

RV10 HD => use anamorphic resize (keep cropped resolution) be sure you crop values are not ODD.

perhaps a ligh xsharpen filter to improve sharpness.

removegrain filter genraly doesn't harm.

use kerneldeint for IVTC if needed.

EHQ = 100 / highter EHQ for first pass.

if you encode a short movie ( around 1H30 or below) use AltCC with autocalc at full and agressivity at slow.
if the movie is >1H30 i suggest AltCC with autocalc medium and agressivity at fast.

hope these few suggestions can help you :)

++

[calinb]

Originally posted by #2
Thanks Cal. I remuxed to .mkv with mkvmerge then used avimux to join and then mkvmerge to mux the audio. (Could possibly use AVIMux for the whole lot if your not useing an AAC audio stream)

Hey, thank you #2. I hadn't found time to try it myself but, after your success, I did. :) I even used the GUIs for mkvmerge and avimux and they worked great. I thought maybe avimux would have trouble with the AAC, but it seems to mux it okay, after doing the initial mux of the files with mkvmerge. I now have my first 4489MB file created with AutoRV10--actually, it's about 4MB oversize in both mkv and rvmb files but now we know how to do it :)...and thanks to dark-cracker for supporting large files. Now, if we can just get RN to do something about the silly 3.9G limiation we can reduce the steps.

[#2]

This is great. So many Questions that I've wanted to know are now being answered.

Just to clarify this DC;

Originally posted by Dark-Cracker
if you encode a short movie ( around 1H30 or below) use AltCC with autocalc at full and agressivity at slow.
if the movie is >1H30 i suggest AltCC with autocalc medium and agressivity at fast.


Do you mean;

if you encode at a 'high quality (bits/frm*pxl)' use AltCC with autocalc at strong (full?) and agressivity at slow.
if the movie is encoded at lower quality (bits/frm*pxl) i suggest AltCC with autocalc medium and agressivity at fast?

By "if you encode a short movie" I'm asuming you mean that for a given file size, say 2 CDs, a short movie would then have a higher bits/frm*pxl. And you then adjust the 'Auto. Calc.' and 'Curve Agression' settings based on the encodes 'Quality' (bits/frm*pxl)

Or were you saying that the running time of a film has an influence on the 'Auto. Calc.' and 'Curve Agression' settings.

I assume that you mean the first. And if so the sugestion you gave me for high my high 'quality' (0.235 bits/frm*pxl) encodes was;
Auto. Calc.=Light
Curve Agression=Slow

But above you sugest
Auto. Calc=full (I guess you mean Strong?)
Curve Agression=Slow


So I guess I'm a bit confused.

-Did you mean Strong not full
-Did you mean bits/frm*pxl or actual running time.
-Would you still sugest;
Auto. Calc.=Light
Curve Agression=Slow
For my 0.235 bits/frm*pxl encode of a 4hr+ film.

Thanks again this has been very informative

P.S. I'm glad to hear it worked for you Cal esp. with AAC. Ditto on the 3.9 GB Real splitting.

[Dark-Cracker]

hi,

in fact i have speak about lenght of movie just to separate the 2 cases :
- an easy compressibility.
- a movie hard to compress.

i think you can speak about Quality (bits/frm*pxl) even if in this case the resolution doesn't matter.

i will explain a bit better the AltCC params :)

Auto Calculation => calculate the high and low % from average frame size.
the params (Light / Medium / Strong) are some threshold to compute these %
- Light => count all the frames.
- Medium => exclude some frames (ignore some "unnaturally high" framesizes)
- Strong => exclude more frames.

for example with a short sample you have these values :
- Light => 600% / 250%
- Medium => 300% / 200%
- Strong => 250% / 190%

these high/low distance % are used in the bitrate redistribution, Lowering the low distance will move the preference towards low bitrate frames. Raising the high distance will move the preference towards high bitrate frames.

Curve aggression defines how quickly the codec adapts bitrate to frames.
the params (Slow / Medium / Fast) are the speed of bitrate redistribution.

A fast aggression will help the codec aid low bitrate frames while hurting high bitrate frames and is better for very dynamic scenes (i.e. a slow motion scene, then up to a lot of motion very quickly). Slow aggression adapts slower and won't improve low bitrate frames as much, but will not harm high bitrate frames much either.
Medium aggression is a compromise of the two.
-----------

1)
in you case i think >=0.23 bits/frm*pxl
Auto. Calc.=Light
Curve Agression=Slow

it will result in a no agressive redistribution.

2)
and below :
Auto. Calc.=Strong
Curve Agression=Fast

this will result in a redistribution of hight bitrate toward the low bitrate frame size.

the case 1) is what i call a short movie , case 2) is what i call a long movie. :)

PS : feel free to post another question , i am actually working on a FAQ :)

Bye.

[tiki4]

Hi D-C,

I just saw your FAQ. Very nice work!

Best wishes,

tiki4

[Dark-Cracker]

thank you :)

the faq is here : http://forum.doom9.org/showthread.php?s=&threadid=87270

and it's still under construction but if you find some usefull question/answer to add feel free.

++

[calinb]

Originally posted by #2
During the encode I trimed the 2 black frames of the end of the first disc and the audio is in sync for the whole film. I must say I am pritty happy with the results. : )#2: How did you trim the 2 frames? I'm happy with the results and our file joining method usually works for me, but I have one encode where the 2nd part has audio 1000ms ahead of the video. Other encodes are perfect. Weird! I'm unfamilar with RV10 tools and directstream copy in Vdubmod leaves me with a corrupted file. Thanks!

[#2]

For Cal.

Originally posted by calinb
I have one encode where the 2nd part has audio 1000ms ahead of the video.

This sounds like there's 1 second of video missing at the change over (or 1 sec of audio padded). So it doesn't sound to me like trimming more video will help you. : ]

3 ways to trim; (especially for 2+DVD encodes)

1- Untick the last chapter while useing DVD Decrypter on all but the last DVD. (Not the most reliable method)

2- Use rmeditor.exe to trim post compression. (Reliable but not frame accurate and only for sub 2GB files : (

3- Add a trim line below the source line of your AVS ('Edit Script AVS' button in AutoRV10 'Add Job' dialoge)

Video=Trim(Video,Start Frame,End Frame)
For Example;

# VIDEO SOURCE
Video=Mpeg2Source("F:\RIPS\LOTR-ROTK\D2\LOTR-ROTKallin1.d2v", idct=2 )
Video=Trim(Video,0,183534)

Or you can cheat and set your end credits to your desired 'end frame' and then use the Film_Movie.rmvb
(Frame accurate but obviously slow)

Originally posted by calinb
I'm unfamilar with RV10 tools

Methods for useing rmeditor

- Add the attached file (Open Cmd Prompt Here for NT/2000/XP/2003) to you registry. Unless you already have this.

-Copy the file you want to split/trim to your ...\Autorv10\Softs\Rp9_Light directory.

-OR Add ;"Drive:\Path\To\Autorv10\Softs\Rp9_Light" to your PATH. Right click My Computor -> Properties -> Advanced tab -> Enviorment variables -> Select Path -> Edit -> scroll to end -> add your path to rmeditors folder including the ";" separator(Useing this method you can use rmeditor from any directory with out haveing to copy a potentialy large file to your System partition)

-Right click on the directory with your file in it and select cmdhere.

-Type "rmeditor" in the cmd prompt for useage help. It's easy really.

For example.
rmeditor -i LOTR.rmvb -o LOTRTrimmed.rmvb -s 00:00:00:000 -e 02:12:14.855

(You can get the start and end time from Ctrl+G in MPC when paused at the right frame)


Don't worry it took me 3 months to get my encode of the Starship Troopers flipper right. ;)
Hope that helps.

P.S Fantastic start to your FAQ DC that really helps a lot.

[calinb]

#2, Thanks for the tutorial. Your post gave me some ideas. I'm encoding HD transport streams so there's no DVDDecrypter step. I'm trying to avoid re-encoding so I'll try trimming about 1 sec of video with rmediator or adding 1 sec of sound with BeSweet. Re-encdoding the AC3 sound won't take long. Luckily, the break is in a place in the movie where it won't be noticed :) Even though it's not frame accurate, I might get lucky with rmediator.

Update:

The sync problem was associated with using avi-muxGUI to join and mux the producer split files containing real audio sound. Actually, I was surprised when avimuxGUI almost worked.

So I encoded the original AC3 to AAC with Nero to try it again. I remuxed the fully joined video file using mkvmerge and no sync problems :). I didn't need to edit the video stream at all. If dark-cracker can convince Real to remove this 3.9G limitation we'd have a pretty sweet point and shoot ap for making full DVD-R/+R HD videos.

To summarize what works for me for an output filesize > 3.9GB:

1. Use AutoRV10 to encode video only (no audio).

2. Use an audio encoding ap of choice to encode audio (or just keep AC3/DTS or whatever.

3. Use mkvmerge mmg/GUI to remux the 2 rmvb files to 2 mkv files.

4. Use avimuxGUI to join the 2 mkv files and remux with audio, if the audio is compatible with avimuxGUI.

5. Use mkvmerge mmg/GUI to mux audio to the mkv file produced by avimuxGUI (joined file), if not done in step 4 (AAC, for instance).

[karl_lillevold]

calinb: Thanks for doing all these experiments!

In Step 1) above, did you encode the video in two parts to end up with two files, both < 3.9 GB in size?

I have to refresh my memory (by talking to the right person) how hard it is to fix the 4GB file size limit, but I worry that it is quite problematic. It might be field in the RM file format that is 32 bit, and RMFF itself must be changed. The 2GB limit in Rmeditor is a programming problem, but the Producer team is extremely limited in resources and will not update the old rmeditor code.

I wonder if it is possible for AutoRV10 to use the mkvwriter output plugin to output directly to Matroska, thus having no filesize problems at all, and significantly simplifying the process outlined above..

I think using Matroska is the best solution for now. The 4GB filesize limit will not be fixed soon.

[calinb]

Originally posted by karl_lillevold
calinb: Thanks for doing all these experiments!

In Step 1) above, did you encode the video in two parts to end up with two files, both < 3.9 GB in size? Yes. My target filesize is 4.38 GB (single DVD-R) and I always end up with one file of 3.9 GB and the "overflow" in a 2nd file.

Another method for ease of use and close to full DVD-R bit utilization would be to not encode the audio and keep the AC3 as a separate file on the DVD-R. Encode the video right up to the 3.9 GB limit. MPC can load external audio files automatically. No remux hassle :) A matroska plugin solution would be much better though, obviously.

[Dark-Cracker]

hi,

hum if i right remember the matroska plugin have still some problems :(
i will try to see later if there is a better way but i think for the moment huge encode will still need the previous trick.

++

[#2]

To further the High Definition encode discussion.

What I have been doing to date is setting the bits/frm*pxl to 0.235 for all sources. However due to the continuium of sources' compressibility based on the ammount of detail and motion in it. This will generate a different visual 'quality' for each encode??

I gather from what I've read on your compressibility test in earlyer posts if you get a 'compressibility' result of 100% from a test useing 100% of 'movie percent used' then you can be sure that the source will be encoded to 'max' quality with producer in quality=75 mode (used to be quality=83). Is this correct?

If this is correct then for the sources I've tested. I end up with large file sizes at 'max' Quality (100% Comp. test result) :

Blade Runner;
2843MB
0.362 bits/frm*pxl

A Time For Dancing;
2701MB
0.285 bits/frm*pxl

ROTK (Ext. ed.);
8697MB
0.336

Dead Man;
2981MB
0.443 bits/frm*pxl

Also I've noticed that the greater the percentage of a source I use the higher the 'Compressibility' results tend to be.

eg. Dead Man: 5%=57.9 15%=57.9 50%=60.1 80%=61.8 100%=63.9
I got similar results (4% - 8% increase in 'Compressibility' from 5% 'movie percent used' to 100% 'movie percent used') for other sources as well.

So I'm guessing I could be better to set my finnal file size for a 60% - 70% 'Comp. test' result than to just religiously sick to a 0.235 bits/frm*pxl setting.

Also what might be a min. 'Comp.test' result that would still be compatable with the type of HD encodes we've been talking about here. ('light' / 'slow', Anamorphic, Keep Cropped, kerneldeint, EHQ = 100 / higher EHQ for first pass, Xsharpen)

P.S. Is 'Use chroma mode decision' good for HD?

P.P.S Are there any more strings that I can use in the Settings.cfg file to change the defaults to say 'removegrain', AltCC settings, Anamorphic, Keep Cropped, EHQ = 100 / higher EHQ for first pass, etc.

Thanks : )

#2

[karl_lillevold]

#2: Sorry I can not be of much help.. I generally do not use the comp. test. I have found that for SD anamorphic encodes when viewed on my Samsung DLP via DVI, 0.235 bits/pixel looks very nice. Lower motion content, even 0.2 or a little lower is OK. I always use HFE2 for playback, no sharpening for anamorphic.

I have not yet played around with encoding HD for viewing on that TV though.

The reason compressibility increases when you use more of the source for the the comp test, is that the scene changes then become less frequent. This makes the source easier to compress.

I would also suggest you use EHQ 85 and 50 for 1st pass for HD. This will save you a bunch of time, without any noticable loss in quality. Chroma mode decision should improve the quality for strong chroma videos, both SD and HD, and never hurt for any videos.

I would be curious which bits/pixel number you end up with, if you target 60-70% comp test final file size ....

[#2]

Thanks Karl.

You've just inspired me to use HFE2 for the first time. (I take it is not included in RealPlayer 10-5?)

Nice explanaton on the Comp. test discrepency. I'm thinking with a bit of experience one might be able to fairly well guess the result of a "Select movie percent used=100%" test from the results of a "Select movie percent used=10%" test. (eg. +3-6% for high motion source +6-9% for a low motion source)

So you think EHQ=85 and the default 50 for the first pass? I'll run some speed tests and see if I can spot the difference visually.

While on the subject... please excuse a potentially silly question but 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 bits/pxl figures for a 70% Quailty target are.... Just 70% of the 100% Quality figure.. : ) All those Comp. tests were useing 100% of the source and calculated for 100% Quality.

Blade Runner
0.253 bits/pxl

A Time for Dancing
0.2 bits/pxl

ROTK (Ext. ed.)
0.235 bits/pxl

Dead Man
0.31 bits/pxl

Dead Man is a bit of a suprise as it is B/W and very low motion. (although high grain)

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

[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

[snowcrash]

So where can I download the latest version? I looked in your forum where I've downloaded it before but I can't find it. When are you going to make a final version and update your website with proper download links for AutoRV10? Thanks.

[Dark-Cracker]

hi,

i am working on a new version (nothing really new but some few bugs and a few improve) i will try to made a full nsis script (it's a task who really dislake me :) but i will make some efforts).

same for the website i have lost my webmaster who is too busy so i must also update it and moderate the forum :( and i not have a lot of time (i will start my training period in an entreprise monday and i am really busy) but i will made my best and try to at last offer a direct link with a full package of a stable release soom :)

++

[Capirossi]

you can try to add others filter in the program ? :cool:

[Dark-Cracker]

which filter do you want to see ? list them and explain their effect i will try to see if they are really useefull to be added.

++

[Capirossi]

mfToon :cool:
very nice in anime encoding :cool:
http://forum.doom9.org/showthread.php?s=&threadid=53364&perpage=20&pagenumber=1 :D

[wata]

suddenly autorv10 can't startup, got this message everytime i run it

Run-time error '6'.
Overflow

i delete everything and reinstall autorv10 v1.0 and replace files with AutoRV10_v1.0_b7.1_update and then AutoRV10_tmp.zip, as instruct in the previous pages
still the same it crash immediately

i have to go back to previous version (AutoRV10_v1.0_b5_update.zip)
then the program run fine?

running windows 2000 here

what are the possible cause, thanks

[calinb]

Originally posted by wata
suddenly autorv10 can't startup, got this message everytime i run it

Run-time error '6'.
Overflow I can't quite remember, but I think this is the error that requires you to eject the DVD that's sitting in your DVD drive. Yes! :)

Update: nope, it was this one:

http://www.video-tools.com/modules.php?name=Forums&file=viewtopic&t=657&highlight=

(You may have to join the AutoRV9/10 forum.)

[wata]

thanks it work now :D
i try everything like reintalling the program and update all the VB components to the latest version, didn't know a simple eject solve the problem
is this a bug which is not fix?

[wata]

using beta 7.1 now, i notice that maximum bitrate doesn't calculate as average bitrate multiply by 5 anymore like beta 5, just +1kbps higher
is this normal?

eg.
now
<avgBitrate type="uint">668000</avgBitrate>
<maxBitrate type="uint">669000</maxBitrate>
before
<avgBitrate type="uint">668000</avgBitrate>
<maxBitrate type="uint">3340000</maxBitrate>

[wata]

batch encode doesn't work

eg.
i have six short movie to encode
all stream demux to m2v with ac3

after adding all the job to the queue and press start encoding
the program will start to decode the ac3 of the LAST task to wave,
when finish decoding, it will start to process the FIRST task which the ac3 is not decode yet

but if i decode all ac3 to wave using besweet beforehand, it work fine

[Dark-Cracker]

hi,

the dvd bug have been fixed thx to calinb. but just in case send me all the ifo file who are on your dvdrom at :
darkcracker(a)caramail.com
i will try again to see if it work correctly.
i am actually re-coding the queue job function i think the futur build will solve this bug.

EDIT :
for the max bitrate it normal because in the 2 pass mode, autorv10 use the new RateControl who ignore the maxbitrate.(i add +1 because maxBitrate should be above avgBitrate else producer will return an error).

stay tuned :)

Bye.

[Rumbah]

Hi!

I tried Autorv10 and noticed the analyze bug, too, but I found the error for me. I encoded an avs file, not a d2v file and in the preview and end avs the file is loaded correctly via import(). But in the analyze avs file it is loaded with
v = mpeg2source("E:\Temp\SOMMER~1\SOMMER~1.AVS")
and results in an error message.
In addition to that I noticed that the MaxMemory in the avs file leads to a producer which uses about 400 MB and without it uses about 50 MB.

[Dark-Cracker]

i will see for this import bug , for the maxmemory can i know the number who is set in the MaxMemory(xxx) function in you .avs script ? i don't know exactly how many mb are allowed at avisynth if this version is not found.

++

[Rumbah]

In the origianl avs file from AutoRV10 it is
SetMemoryMax(384)
and results in about 430MB for the producer process.
I simply set it to
#SetMemoryMax(384)
and the result is 50MB for the producer process so that World of Warcraft runs great with producer in background ;) .

[Dark-Cracker]

i think that when there is no setmaxmemory param avisynth use around 32Mb the fact that producer use a but more memory is surely because it store a few frames in buffer. i will perhaps think of an option to limit the maxmemory value.

thank u for the bug report.

++

[Capirossi]

producer 11 is out
nobody update for autorv10 ? :cool:

[buzzqw]

or autodub...
BHH

[Dark-Cracker]

i will check this update i still have some few function to finish for autorv10 (i have rewrite a part of the code) and try to provide u an update.

for autodub i will not stop this project i still have some idears to improve it i will try to work on it when autorv10 will be at a stable stage. but it's hard to keep motivation with the AutoGk tool who is used in mass i will perhaps try to oriente my software toward a network or matroska functionnality.

damn my english suck :)

++

[calinb]

Originally posted by Dark-Cracker
i will perhaps try to oriente my software toward a network or matroska functionnality.++ Both very cool goals, Dark-Cracker! :D

The only encoding ap I've ever used that has network features is Vidomi. Even though Vidomi networking is difficult to successfully configure and is, essentially, just a batch job splitter/server, it was really convenient to queue up about a 10 or 20 jobs on the server and keep several client machines busy for a few days. No machine ever went idle because the faster ones just got served more jobs.

[Capirossi]

and add http://forum.doom9.org/showthread.php?s=&threadid=56051&perpage=20&highlight=conditional%20filter%20qmf&pagenumber=1
please :cool:

[Dark-Cracker]

@Capirossi

QMF is already included when you select denoise click on "dynamic" and the cleanning will be adjusted following the movie motion :)

++

[Capirossi]

thanks, I have not seen it
regards :)

[Sirber]

AutoRV10 b7.1 crash if I terminate producer. "Dépassement de capacité"

[Dark-Cracker]

i have fix this bug, the correction will be available in the next build.

thx for the bug report.

++

[Sirber]

no problem.

Also, GUI told me it was to be 695kbps, but producer started at 350kbps. :confused:

[Dark-Cracker]

could you post the .rpjf file plz.
which settings have u used ?

++

[Sirber]

2h06, 700MB
Checked end credit, but did not conf it (no popup)
Anamorphic

http://www.detritus.qc.ca/files/steam_Movie.rpjf
http://www.detritus.qc.ca/files/steam_Credit.rpjf

[neo_anderson]

hi, i have avisynth 2.5,dgindex, and real player plus 10.5 installed on my pc, what all other things do i need to install to encode dvd movies to real video? i know this has been answrered, but i'm little confused, so pls pls can anyone give me links or just tell me what all to download?

[Dark-Cracker]

you need to have the vb6 runtime (cf in the download section of my site web).
after this you need to extract the autorv10 full package in a folder, overwrite the old file by decompressing the update archive in the same folder.
if you use the latest dgmpeg version think to overwrite the ..\Softs\avsfile\dgdecode.dll with the one provided in the dgmpeg archive.

if you have some problem after this feel free to ask and i will try to give u an answer :)

++

[tarantism]

autorv10 and the last producer beta? it works?

[Dark-Cracker]

yes it work.

[karl_lillevold]

Backflip: not sure which answer you found, but since your question was in the e-mail notification, I just wanted to make sure you found the right answer:

RV10 (and older RV) requires the input to be modulo 4, both width and height. If the input is modulo 16, compression is slightly more efficient, but nothing to worry about. It is better to get the cropping and aspect ratio correct. Narrow (1-2 lines) black edges would reduce compression efficiency more.

[Backflip]

Thank you for your answer :)

[raj2569]

Hi,

I am using latest AutoRV10 for encoding DVDs. I had two problems. One was that when I am using two pass vbr, my client used to freeze with in about 10 minutes of play. karl_lillevold suggested in Producer list to try with one pass vbr and that fixed this.

Another problem I am having is when I encode from a DVD, and play in real player (from server or from file), the voice is bit messed up. The symptoms are that, human voice, like speech has lower volume but action voice like gun fire has higher volume. But when I tried Lord of the Rings, in the introduction, the female narration is louder than DVD, but the strange creature's voice (the one who has the ring, just before Hobbit gets it) when it says "My Precious" is fainter.

I have read the " GUIDE: How To Properly Encode Dolby Digital Audio (AC3)" and it seems the problem is with Dialog Normalization or Dynamic Range Compression, but these settings are not possible in AutoRV10. If any files from my jobs are required, I will post them.

with warm regards,

raj

[Dark-Cracker]

hi,

i don't know why you have problem playing you video file encoded in 2 pass, i can only suggest you to be sure to clean all the previous RV codec you have install (like the Real Alternative codecpack) be sure to install the latest realplayer version and perhaps update your video card drivers, i really don't know why you have a fix and i can only come with these generic advices :)

for the audio problem.

I have read the " GUIDE: How To Properly Encode Dolby Digital Audio (AC3)" and it seems the problem is with Dialog Normalization or Dynamic Range Compression, but these settings are not possible in AutoRV10

when you open a .ac3 file you will have the button "advanced dolby digital settings" who will be un-greyed , it allow you to have access at the settings like "use dialog normalization" and "dynamic compression" i hope this will help u to adjust the setting for audio and help u to have better audio quality :)

++

[karl_lillevold]

raj2569: which audio codec and bitrate did you choose for encoding the audio?

[raj2569]

Karl:

According to the realproducer output:

Diagnostic: Using AutoRV10 Audience File Audience
Diagnostic: Using video codec: rv10 (1212710 bps)
Diagnostic: Using audio codec: cook (183290 bps)

I am using realvideo10 and cook for video and audio. I am also attaching my BeSweet logs, Audience File and real producer logs.

Dark-Cracker: I had already checked the options inside "advanced dolby digital settings", and "use dialog normalization" and "dynamic compression" are already set. The BeSweet logs will have details. But no success so far :(

with warm regards,

raj

[raj2569]

I tried to change from "MultiChannel" mode to "Surround" to see if that fixes the volume problem, and I get a dialouge box with an error. I have attached the error message box I get along with this post. The settings are the same for this and my previous encodings, except for "Channel Mode" and BitRate in "Audio Codec" section of audio.

regards,

raj

[karl_lillevold]

Yes, I think the problem might be you are encoding in RA 5.1 channels, and playing back on a two speaker system, hearing only the left and right channel. I thought DirectSound was supposed to downmix, it does that on my system, maybe that is not working in your player. Try the following, in RealPlayer, Tools->Preferences->Hardware->Sound Card Compatibility (Settings...), check the box for "Disable Direct Sound".

Regarding the error message from Producer, I would recommend to setup AutoRV10 to use the Producer that comes with it. It looks like you have set the paths to another version of Producer.

[raj2569]

Hi,

Thanks a lot, it worked perfectly when i disabled the Direct Sound. I have been struggling for 2 weeks to encoding this.

You saved my day!!

:thanks:

raj

[Dark-Cracker]

happy to see karl have solve your problem :)
i have add the solution in the FAQ.

++

[HASH ULTRA]

Seems you have a bug in your software v1.0b7.1 - if you have a cd/dvd in the drive when starting the program it may give you an 'Erreur 9'.

[Dark-Cracker]

yes this bug have been reported when you have a DVD in the DVDROM with more than 10 .ifo file on the disc.

could you plz confirm it was a dvd ?

++

[Xeno86]

Unfortunately I can't test your software because it gives me this error 'You need to have the administrator privelege !'. I'm using Windows 98 SE so I always have administrator priveleges. You should correct your software to first check Windows version and then if it is NT os check priveleges.
So far I'm disappointed :(

[Dark-Cracker]

normaly it already check the OS version, perhaps win98 SE is bad detected. i am disapointed myself :)

[Dark-Cracker]

hi,

long time no see :) i have released a new version of AutoRV10 (only a few change i have not really a lot of time with new job :) but i am still working on the project).

Here is the link (http://dark.pluridis.org/AutoRV10_v1.0_b8_update.zip)


and here the changelog :

- use an accurate overhead calculation (accurate at 99.99 %).
- rewrite a big part of the audio process.
- improve compressibility test. (now give you the *best* suggested resolution)
- handle correctly the HDTV file with a weird resolution (1920x1088 instead of 1080)
- add ELA (Edge Line Average) when using upper-resize in the anamorphic mode
- improve ColorMatrix() use (detect the need to apply a colorimetric filter)
- improve the anamorphic formula
- possibility to save image as .JPG from the preview window
- auto detect insert/eject media CD.
- add an fps limiter during the avs preview (crop window)
- Improve chapter grabbing (encode text using ISO88-59)
- possibility to use COOK instead of RACP for bitrate range 32kbps-96kbps (content patent for the HE-AAC codec use)
- select beetween STEREO or SURROUND Matrix if the codec COOK is used for the bitrate 64kbps or 96kbps.

- fix few bugs.
- clean,speedup of the code and memory optimisation.


Enjoy :)

feel free to report bug (surely some new bug in the audio part).

[#2]

Thankyou DC!!!
It's great to see you still chipping away at this :)
RV10 is still my favorite codec.

[Dark-Cracker]

happy to heard this :)

next version will have a few friendly user options and an OCR engine for the subtitle.
until the next release feel free to report bugs :)

++

[karl_lillevold]

This thread has been closed. Please discuss AutoRV10 in the new and clean thread here:
http://forum.doom9.org/showthread.php?t=29077