@ karl :
i registered the new keys but these keys override any further settings in audience, true ? (in fact, if i register complexity at 80 and ask for 70 in audience , producer will still encode at 80 ? )that's what i realized.
so i might guess i have to delete keys in registry ?

@ nah :
<UseThread> markup will also be deleted from rmfactory in next release. About avi ( now avs too ) input , give me please some ideas on how to improve it : i can't read in users mind , neither can they in mine ( i 'really' should write some docs )

psnr :\ and compare/subtract scripts in avisynth.
Also people always ask on amv.org how to convert RM to something else and I think I remember karl saying that EO uses a crappy renderer or something to decode, but that's what I've always used and recommended because it's like the only thing that works.

PSNR calculations can sometimes be very inaccurate. For instance, we have a built-in filter that removes potential capture noise along the edge of the video. Even though the resulting compressed video looks better than the original for those areas, it will significantly degrade a PSNR number, which just looks at pixel for pixel differences. I have no idea how a program like EO video will affect PSNR when it saves RM files as AVI files. By using the proper audience settings it is possible to disable this noisyEdgeFilter though, and there are also some other settings which can be used, but I will leave it as an exercise for the reader to check the producer documentation for these options. Even then there could be problems with rate control and dropped frames. So it is possible to get accurate numbers, but a little complex.

Originally posted by zedude @ karl :
i registered the new keys but these keys override any further settings in audience, true ? (in fact, if i register complexity at 80 and ask for 70 in audience , producer will still encode at 80 ? )that's what i realized.
so i might guess i have to delete keys in registry ?

Actually, since you are using an audience file, it would be best to not touch the registry. You should place these options in the audience (or job) file.

The registry settings are meant to enable this mode in the old GUI Helix Producer and other tools which have not (yet) included the ability to set this mode in the audience file

Or it is nice for those that always want to use encoderComplexity=80, and not have to worry about remembering to enable this in whichever tool they use. And then it would be bad if your tool decided to delete these keys. They are meant to always over-ride whichever setting would otherwise have been chosen.

vbrQuality instead of vbrBitrate. Note that the <maxBitrate type="uint">99999999</maxBitrate> has an effect when vbrQuality is used, so if you want a very high quality, make sure to set maxBitrate high enough.

Also note that RV9's quality levels are very different from other codecs, so for instance RV9 at 85 is not the same as 85 for any other codec.

@BigPapaSmurf: hilsen til Norge fra Seattle! Those bitrate reductions are similar to what I have seen.

Right now I am looking into speeding up 1st pass to faster than default (complexity 50), while 2nd pass runs at normal complexity 80 speed. I am not sure it will be complete for Producer 9.2 - we shall see, but in any case a temporary build can always be made available from helixcommunity.