RealVideo 10 'Elysian'

[Shinobu]

Just have le little problem with new rc

if i use
<rcEnableCurveCompression type="bool">false</rcEnableCurveCompression>
it's all right and i can customise all a want i'll be alway ok.
but if i use
<rcEnableCurveCompression type="bool">true</rcEnableCurveCompression>
i canencode but the vidéo i get is unseekable , if i seek >1 min it freeze, if i dont seek, there is no bug at all during the play...


any clues ?

++

[karl_lillevold]

No, I am afraid I do not know. Seeking takes just a moment for all the encodes I have done with the new RC, and it is quite a few by now. However, the new rate control introduces enough variability in the bitrate that very old players (or old DLLs/registry settings) may have a problem seeking.

I use RealPlayer 10 Beta, with updated decoder DLLs (HFE + inloop), and I use Media Player Classic.

Which player are you using? If codec pack + RealMediaSplitter, then it is most likely a problem with RealMediaSplitter or the codec pack. You should try r1pclean (http://www.lillevold.com/files/r1pclean.zip) and then install RealPlayer 10. You can still use any alternative player you like, but then you know all the codecs and registry are in order.

EDIT: if after making sure everything is up to date, and you still have a problem seeking, please try to arrange for me to get a copy of the problematic rmvb file.

[phrentec]

I've had several problems and not all of them happened concurrently. I just wondered if anyone else had it or if it is just me because I'm running under a nonadmin account.
1)Sometimes producer(command line with and without elysian dlls) stops at 100% in the first pass and doesn't go on to the 2nd pass
2)producer exceeds the specified bitrate as if it didn't take it into consideration, actual bitrate was like way over a thousand, specified bitrate was 400, and the wierd thing is I had to calculate that bitrate because realone player showed an incorrect bitrate during playback.
3)when I try to stop producer with crtl+c it doesn't stop. I have to sometimes just hit the X to close the commandline. Then I have to use dtdriver and demux the video. It could be because I used "run as" and ran the producer under an admin.
4)I sometimes get this warning when trying to encode an avi. and the avi plays perfectly in windowsmediaplayer. Warning: Neither uncompressed audio or video was available in DirectShow Reader

These are just a few problems I'm running into on this computer. However when testing on a seperate computer it worked perfectly fine.

[karl_lillevold]

phrentec: This sound very much like a DirectShow problem. As you know, Producer uses DirectShow to read its input files. Perhaps it will give you some insight into what goes wrong if you load the source file into graphedit. It will show you the filters that DirectShow loads. Auto-loading filters like VSFilter and Morgan Stream Switcher are known to cause problems for Producer.

[karl_lillevold]

rv10_elysian_022404.zip

Available from the Helix Community Binary Downloads (https://helixcommunity.org/beula/download).


<rcKeyFrameBoost type="uint">0</rcKeyFrameBoost>
<!-- Boost keyframes by rcKeyFrameBoost % -->

<rcHighBitrateReduce type="uint">0</rcHighBitrateReduce>
<!-- Reduce larger than average frames by rcHighBitrateReduce % -->
<!-- Usually good for average PSNR, and/or low/medium bitrate -->
<!-- streams, where the largest frames cost too many bits -->
<!-- compared to the PSNR achieved -->

<rcLowBitrateBoost type="uint">0</rcLowBitrateBoost>
<!-- Boost smaller than average frames by rcLowBitrateBoost % -->


Please do not ask me what the best values are. This depends on many factors. In most cases, leave them alone. Or try to find what works best for you. Here is some initial advice: For constant quality and high bitrates, all zeroes are best. For low/medium bitrate and for best average PSNR, try rcHighBitrateReduce 30-80 or so. I have not really found a good use for rcLowBitrateBoost, it tends to increase mostly tiny B frames, which are best left on their own. Maybe some tuning is still needed here.

This update also hooks up video mode 'sharp' to the following inloop options:

<inloopCutOffQuant type="uint">10</inloopCutOffQuant>
<inloopCutOffCompatible type="bool">false</inloopCutOffCompatible>
<inloopCutOffBUseRefQuant type="bool">true</inloopCutOffBUseRefQuant>


Finally, this option did not change, but if you have not tried the new decoder postfilter HFE, please do. At strength 1 it adds a nice improvement in textures/noise in the spatial domain and their temporal continuity.

[phrentec]

okay I am now trying to encode a vob file(unencrypted). Here is a picture of what graphedit shows
http://www.geocities.com/nvet8/1vob.htm

the error I get in the commandline is here

---edited out---

problem found to be ligos, thanks to Karl
will now try avs script with dvd2avi/ac3

[karl_lillevold]

I don't know how many times this question comes up... It's also in the FAQ section in the main RV info thread, but I really should improve the answer I put there.

The Ligos MPEG-2 decoder filter is probably not working as input to Producer. Few MPEG-2 decoders do, since they only expect to be used as playback filters. The MPEG-2 decoder from Elecard has been known to work, but as always, the safest method to encode MPEG-2 is DVD2AVI-> .d2v/ac3. Then you can create an Avisynth script, or use one of the GUIs that can do the job for you, for instance AutoRV9/10.

[Sagittaire]

@ Karl

rcKeyFrameBoost, rcHighBitrateReduce & rcLowBitrateBoost ... ?

You can describe precisely the influance of these new seeting ... please

[phrentec]

one problem still not solved. the bitrate goes more than two times beyond the average.

[karl_lillevold]

Originally posted by Sagittaire
rcKeyFrameBoost, rcHighBitrateReduce & rcLowBitrateBoost ... ?
You can describe precisely the influance of these new seeting ... please
I am not sure what more there is to say than what I wrote in the previous post:

rcKeyFrameBoost: adds <n> % to the size of keyframes, where <n> is the rcKeyFrameBoost parameter.

rcHighBitrateReduce: reduces <n> % from the size of frames that are larger than the average for a certain frametype, where <n> is the rcHighBitrateReduce parameter. Applies to P and B frames, not I frames.

rcLowBitrateBoost: adds <n> % to the size of frames that are smaller than the average for a certain frametype, where <n> is the rcLowBitrateBoost parameter. Applies to P and B frames, not I frames.

In all cases, please enable rcLogFileName. You will see a number of columns. First is the size from the 1st pass (Size), then the linearly scaled size that would have been the target for constant quality (Scaled). Then is the column for the scaled size after the parameters above have been applied (AdvSc). After that the column for target sizes after it has been adjusted for the current bitrate overflow (Target). (Actual) is the actual framesize achieved. (Error) is the different between Target and Actual. And finally, the current bitrate buffer overflow (OFlow). Please take a look at how these parameters affect the AdvScale column to understand how they work.

Originally posted by phrentec
one problem still not solved. the bitrate goes more than two times beyond the average.

I am not sure what this means. Are you using the new rate control, and the file ends up at more than twice the bitrate requested? This either sounds like the 1st pass reference file, when the encoder runs in two separate passes, or the rcSourceFrameRate parameter is half of what it should be. In either case, the rate control log file (rcLogFileName) is the key to resolving the problem, and will tell you what the rate control is doing. The last frame should have a overflow of just a few thousand bytes (usually less than 100,000) compared to its calculated target, which will be listed in the beginning of the same file.

If what you mean is that the peak bitrate goes to more than twice the average, this is perfectly normal, like Sirber mentions. I would imagine even higher peaks. The average should come out almost exactly as requested though.

[datascab]

@ karl

Hi, nice work with the new R-C.

Is this release ok enough for archiving some dvd's yet?

I'm just hanging on so I dont have to use the old method

Thanks

Data

[karl_lillevold]

datascab: thanks, but credit really goes to the XviD team for showing how it is possible to achieve such constant quality with a completely different method than RealVideo had been using in the past. When I first saw how XviD picked a quantizer (quality level) for the 2nd pass and stuck with with throughout a 2 hour encode, and still reached the target filesize, made me realize it was not possible to continue to hack on the old RealVideo rate control, but that it was time to learn something new :)

Re stability: I do not expect to make any further changes. This should be the method that goes into Producer 10 Gold. All my test encodes and feedback indicate it works well.

[datascab]

@ Karl...

With regards to real producer gold...

Did the the powers that be decide it would be a good idea for people like us doom9'ers to be able to use use a fully functional real producer with GUI?

Surely it would put real P in the forefront? :)

(Attempt to make the real bosses feel good, lol) :D

Data

[phrentec]

the bitrate problem I had is now solved. I was encoding just a short 10sec which made the bitrate look like it was going way beyond but now that I encoded the whole video the bitrate came down to the average.


I still have one problem though.
I was trying to encode a quicktime file with 2-pass and producer always fails to go on to the 2nd pass. It reaches up to and just stays put at 100% in the firts pass.


oh yeah and before it hits to producer gold do you thing there will still be time to have a fps, time left/elapsed counter?

feedback:
one thing I notice about the video I encoded is at the initial change of a scene, the first few frames of the new scene are very blurry, and then it gradually becomes sharp. this happens allmost all the time at the beginning of a scene change. So I was wondering how it would be possible to insert a keyframe at the beginning of each scene change?

[karl_lillevold]

Originally posted by datascab
Did the the powers that be decide it would be a good idea for people like us doom9'ers to be able to use use a fully functional real producer with GUI?
No news on that front, I am afraid. Fortunately there are many really nice 3rd party GUIs.

Originally posted by phrentec
I still have one problem though.
I was trying to encode a quicktime file with 2-pass and producer always fails to go on to the 2nd pass. It reaches up to and just stays put at 100% in the firts pass.

Sorry, I don't know. I almost never encode Quicktime files, and once I needed to, I first converted to AVI. If you can upload the file to me, I can file a bug.


oh yeah and before it hits to producer gold do you thing there will still be time to have a fps, time left/elapsed counter?

No, I am afraid not.

feedback:
one thing I notice about the video I encoded is at the initial change of a scene, the first few frames of the new scene are very blurry, and then it gradually becomes sharp. this happens allmost all the time at the beginning of a scene change. So I was wondering how it would be possible to insert a keyframe at the beginning of each scene change?
This is really an indication something is very wrong. I don't know the bitrate you are using, but this should not happen. The codec already inserts key frames at every scene change. I have seen something like this when someone encoded the 2nd pass with a 1st pass analysis file for another source file. Perhaps if you are encoding directly from .vob (not recommended, and if you do, anything can happen), the MPEG-2 DirectShow filter is in some kind of real-time mode, and skips frames such that the codec does not see the same frames in the 2nd pass and the 1st pass.

[phrentec]

where can I upload my quicktime file to(it is around 1mb).

When I ecoded the video(.vob) I loaded it into dvd2avi and saved the project and then through this avisynth script I encoded the video with producer.


LoadPlugin("C:\producer\soft\decodefix100\MPEG2Dec3dg.dll")
video=mpeg2source("C:\Documents and Settings\All Users\Documents\2\2.d2v")
audio=wavsource("C:\Documents and Settings\All Users\Documents\2\2 AC3 T01 2_0ch 384Kbps 48KHz.wav")
ConvertToYV12(audiodub(video,audio))
Crop(00,94,720,300)

[karl_lillevold]

phrentec: I'll PM you the upload URL.

Your MPEG-2 encoding method appears to be just the way it should be. Could you also upload your encoded file, with the blurry frames, including the 1st pass file (.pass) and the 2nd pass log file (rcLogFile parameter). Thanks.

[SometimesWarrior]

Hi Karl, I have a couple of questions.

1) When making changes to the new bitrate boost and reduction parameters, do I need to re-encode the first pass with every change, or can I simply redo the second pass?

2) By setting inloopCutOffQuant to 0, am I turning the filtering on permanently, or am I allowing the encoder to decide when to activate it (the way it did before Elysian)? Does the encoder then apply the filtering adaptively (per-frame), does it decide on a cutoff quant at the start (lower or higher depending on bitrate), or is it hard-coded (cutoff at 8, for example)?

[phrentec]

a little off topic but how do I merge two elysianProducer encoded rmvb files into just one rmvb file. I have tried one shareware tool for this and it didn't work. I was wondering if there were any freeware alternatives. Thanks.

[Sirber]

what about cmdline rmeditor?

[phrentec]

ok that will work.

another question. How do determine the colorspace that my avs script is outputing to. and if I use the ConvertToYV12, is that converting my dvd to rgb and then to yv12? what is the most effecient way to reach yv12 colorspace without loss of quality. thanks. and also after installing karls' yv12 codecs I still don't see it being used in graphedit. DOes that have to do with the merit? thanks.

[karl_lillevold]

Originally posted by SometimesWarrior
Hi Karl, I have a couple of questions.

1) When making changes to the new bitrate boost and reduction parameters, do I need to re-encode the first pass with every change, or can I simply redo the second pass?

2) By setting inloopCutOffQuant to 0, am I turning the filtering on permanently, or am I allowing the encoder to decide when to activate it (the way it did before Elysian)? Does the encoder then apply the filtering adaptively (per-frame), does it decide on a cutoff quant at the start (lower or higher depending on bitrate), or is it hard-coded (cutoff at 8, for example)?

1) The only parameter that has an effect during the 1st pass is maxConsecutiveBFrames. This has no effect during the 2nd pass, because the frame types will be forced to the same in the 2nd pass.

You can repeat the 2nd pass as many times as you like using the same 1st pass file, and change all the other options, including bitrate boost and reduction, inloop options, target filesize/bitrate etc.

2) setting it to 0 results in the codec operating normally, i.e. adaptively, where the effective threshold is somewhere around 8, at which it starts to do a little filtering, but very limited, and depending on the video content.

Originally posted by phrentec
How do determine the colorspace that my avs script is outputing to. and if I use the ConvertToYV12, is that converting my dvd to rgb and then to yv12? what is the most effecient way to reach yv12 colorspace without loss of quality. thanks. and also after installing karls' yv12 codecs I still don't see it being used in graphedit. DOes that have to do with the merit? thanks.
If you use the right mpeg2dec in Avisynth it will output to YV12 directly. There is no need to ConvertToYV12.

My YV12/I420 codecs are VfW (Video for Windows). In DirectShow they are loaded via AVI Decompressor, and graphedit does not show which VfW codec gets loaded. Media Player Classic does though (Play -> Filters -> AVI Decompressor (YV12).

[SometimesWarrior]

Thanks for the reply, Karl, that will save me some time when testing various parameters. I'll post my results when I've found an easy way to do double-blind comparisons between encodes. Coming from Hydrogenaudio, where listening tests are flamed unless possible sources of bias are throughly eliminated, I'm sometimes surprised by what passes for "testing" on this forum... :rolleyes:

What video lengths are appropriate for testing the rate-control mechanisms? Right now, I'm simply re-encoding the entire 2-hour movie each time I change the bitrate boost or reduction. Would a 30-minute or 10-minute segment be just as effective for testing purposes, or does Elysian really shine only on full-length videos?

[karl_lillevold]

I can not answer which clips will work best for double blind comparisons, but during development and testing of the new rate control, I would never have finished if I were to use 2 hour test videos.

In fact, I was using an 8min test clip I constructed from several segments of one of my favorite sources; first 3 minutes of low motion, then 2 minutes of the most intense action, finally 3 minutes of mixed action. This I resized down and saved as YV12 to speed up encoding even further, down to just about one minute for both passes in low complexity mode.

The new rate contol works really well on anything a few minutes long, that has varying action, with some very complex and lengthy scenes. However, the shorter the total length, the closer the new and old rate control will work. The old rate control started having problems when high activity lasted for relatively long periods.

My most used test video:
mpeg2source("source.d2v")
crop(0,60,718,356)
#BicubicResize(640,272,0,0.5)
LanczosResize(320,136)
a = Trim(106926, 111368)
b = Trim(147000, 152074)
c = Trim(178310, 180905)
v = a+b+c
return v

For the bit distribution illustrated with the stats viewer on the 1st page of this thread, I had another test clip, half almost no motion, half the highest motion you can imagine. This was only 3 minutes total length.

[Griniaris]

I have a problem when using the new elysian rc.

Files are produced ok and look good enough but seeking in them is sometimes very very slow...
This does not happen with all the positions in the file. If I click to seek to time 'x' seeking might only take a few msecs but if I click to seek to time 'y' seeking might take a few secs. Maybe it is because I do not have realplayer installed but I use MPC instead but I never had any problems before... Until now I had MPC and drvc.dll in the same folder and all video files were working fine. I replaced the dll with the new one but seeking is still slow. Will my problem be solved if I install RealPlayer or could it be something else? Does it have anything to do with seeking near keyframes or away from one? I remember reading something similar a few days ago but I do not know if it was somehow solved.

Thanks,
Chris

[Sirber]

It's simply a bug. Sometime producer don't use keyframe, so seeking is slow or impossible :). Redownload the lastest DLL.

[Griniaris]

Which dll do you mean?

I have allready downloaded and used the latest "elysian" 24/02 release. Do I need to update another dll too? Maybe you mean to redownload the full producer command line package?

[Sirber]

nope, the lastest Elysian DLL.

[karl_lillevold]

Based on the problem reported by Shinobu, I found that I had bypassed too much of the old rate control, and the key frame interval was ignored. Thus, for sections where the codec does not auto-insert key frames based on the video content, for instance credits, or certain anime, it will be hard to seek.

I have fixed the problem, and sent Sirber and Shinobu a fixed DLL. Sirber, you are too early. It is not yet available, should be later today. It also has a new CPU scalability level.

[Sirber]

Sorry, my mistake :)

[karl_lillevold]

https://helixcommunity.org/beula/download/

030104:

Fixed bug, where max key frame interval
was ignored.

Added new encoder complexity level, which is almost
the same quality as High, but 30% faster. Made
Medium 30% faster as well. So we now have the following
levels:

100: Very High (95-100)
90 : High (85-94) ** Recommended
80 : Medium-High (78-84) ** 2nd Recommended
70 : Medium (70-77)
60 : Low (60-69)
50 : Very Low (50-59)

The numbers on paranthesis indicate the actual range
which the codec interprets to mean the same. The range
is needed for Live encoding.

The bold lines correspond to the modes available with the command line switch -eco, and the encodingComplexity mode parameter, via 'low', 'medium', or 'high'.

[karl_lillevold]

Thanks especially to Shinobu for noticing the seeking problem in files created with this new rate control, and for him taking the time to carefully reproduce the problem, make log files for me to examine, as well as verify the problem to be fixed.

[Griniaris]

Thanks a lot for this fix!

I just got it and will test tonight...

Chris

[phrentec]

<encoderComplexity type="string">high</encoderComplexity>

<encodingComplexity type="string">high</encodingComplexity>

I tried both of those and producer.log still says


PID696,Informational,Command Line,2004/03/01 16:41:44,10529,Preparing to encode file "C:\1.avs" to file "C:\producer\encode.rmvb"
PID696,Informational,SDK Encoding,2004/03/01 16:41:44,15000,Starting encode
PID696,Informational,SDK Encoding,2004/03/01 16:41:44,15004,Starting analysis pass
PID696,Error,Video Codec,2004/03/01 16:41:44,0,Failed to Set Property: Key encodingComplexity Value high
PID696,Error,Video Codec,2004/03/01 16:41:44,0,Failed to initialize video codec 04VR
PID696,Error,SDK Encoding,2004/03/01 16:41:44,15001,Job failed to start encoding
PID696,Error,Command Line,2004/03/01 16:41:44,10532,Encoding failed!

[karl_lillevold]

encoderComplexity, uint goes inside codecProperties:

<videoStream>
<pluginName type="string">rn-videocodec-realvideo</pluginName>
<codecName type="string">rv10</codecName>
...
<codecProperties type="bag">
<encoderComplexity type="uint">90</encoderComplexity>
</codecProperties>
...
<encodingType type="string">vbrBitrate</encodingType>
</videoStream>

encodingComplexity, string (low, medium, high), goes outside:

<videoStream>
<pluginName type="string">rn-videocodec-realvideo</pluginName>
<codecName type="string">rv10</codecName>
...
<encodingComplexity type="string">high</encodingComplexity>
...
<encodingType type="string">vbrBitrate</encodingType>
</videoStream>

encoderComplexity over-rides encodingComplexity, and allows setting of more levels. Hope this helps.

[ookzDVD]

@karl,

I don't know what is wrong, my machine is getting slower or the RV10.

but I'm experiencing that RV10 is very2 slow on my machine,
for 2.30 minutes clip, res 640x344, i have to wait about 30 minutes. :(

[edit]I'll try the latest update. I hope it will be faster :)

[phrentec]

Thanks for the reply.

So to experience the new 30% faster encoder complexity level, which tags (encodercomplexity or encodingcomplexity) would I use and at what value(ie high, veryhigh, very high, very-high, 80, 90, 100, 85?).

Sorry for any confusion that i've caused myself.

[karl_lillevold]

Sorry for the confusion: the new mode, "medium-high", is available only with encoderComplexity, uint, at 80. The "official" encodingComplexity parameter that also corresponds to the -eco command line switch, supports only low, medium, high.

I edited the post above to indicate which modes are available via this Producer codec agnostic interface.

[Griniaris]

I used the latest dll last night and everything seems to work fine now! The file is seekable to all times and looks great. Thanks for that!

[phrentec]

How do I force producer to use directshow to open up quicktime files, as opposed to the default quicktime opener in producer? Or there there a way to add a switch like that?

[karl_lillevold]

ookzDVD: Hope you figured out the problem. I can not think of any change I made to make encoding slower. There have been some cases, where GUIs or codec interface changes accidentally resulted in the wrong encoding complexity level being chosen though. As always, rv9log.txt will show you the encoding complexity the codec is actually using.

pthrentec: that's easy.. Just go to the tools folder, move qtreader.dll into a backup folder. I just tried it, and it works.

without qtreader.dll (options -lc e,d):
"Input File Properties from rn-avfile-directshow"

with qtreader.dll:
"Input File Properties from rn-avfile-qt"

[Big_Berny]

Hi,
is it possible to activate the old rate-controle? Because I think that it worked better on lowbitrates. Perhaps it would be good, that it uses automaticaly the old rate-controle if you use a low bitrate, what do you mean?

EDIT: Sorry, I only tested with a short clip. I'll try a longer one.

Big_Berny

[Sirber]

If you want to use the old RC, just *NOT* enable the new one :p

[karl_lillevold]

For very low bitrates, constant quality is not the best option, since too many bits are spent for the high complexity scenes, and low motion scenes pay too much in terms of having too low bitrate. At least use the rcHighBitrateReduce parameter, I found that average PSNR increased with this parameter even as high as 80.

Sirber is right though, if you do not specifically enable the new RC, everything will be as before. However, be aware that the old RC for very short clips and VBR would sometimes end up with a much higher bitrate than you asked for, due to its use of the MSL buffer. The new RC should be very accurate down to very short clips, and perhaps you ended up with a lower bitrate than with the old RC...

[Big_Berny]

I'll do a test on a simpsons episode:
I choose a resolution of 384x288 and it's about 22 minutes long.

Do you think that on these conditions the new ratecontrole is better?

Big_Berny

[Caddis]

@Karl or D-C

I seem to be having getting a constant error when using Autorv10.
It allways come up to do with racp.dll. I have all the updates for Real10 and am using the latest Autorv10 exe. I can't figure out what it is. I've read everything I can find on this too.

I'll post the error from the cmd. line window.


Diagnostic: "C:\DivX\AUTORV~1.0_B\Softs\RP9_LI~1\producer.exe -j E:\DivX_VOB\Movie.rpjf -daw -lc e,d" command line being run
Helix DNA(TM) Producer 10.0 Preview Build number: 10.0.0.74
Diagnostic: --------- Input File Properties from rn-avfile-directshow
Diagnostic: Input Filename: E:\DivX_VOB\Movie.avs
Diagnostic: File Size: 1KB
Diagnostic: Total Duration: 01:51:35.821
Diagnostic: Video Track
Diagnostic: Dimensions: 640 x 276
Diagnostic: Frame Rate: 23.976 FPS
Diagnostic: Format: YV12
Diagnostic: Duration: 01:51:35.821
Diagnostic: Audio Track
Diagnostic: Channels: Stereo
Diagnostic: Bit Depth: 16
Diagnostic: SampleRate: 44100 Hz
Diagnostic: Format: Uncompressed Audio
Diagnostic: Duration: 01:51:35.821
Diagnostic: --------- End Input File Properties
Diagnostic: Load Level Headings: Reference Time, Stream Time, Delay, Inte
rval Load, Average Interval Load, Processing Load, Stream Interval, Reference In
terval, Accrued Delay, Average Delay, Load Level
Diagnostic: Using AutoRV9 Audience File Audience
Diagnostic: Using video codec: rv10 (772000 bps)
Diagnostic: Using audio codec: racp (96000 bps)
Diagnostic: Setting video packet size to 15000
Encoding: 4:08.2/1:51:35.9 ( 3%) Errors: 0 Warnings: 0

***************************************************
2004/03/01 16:49:48
Exception code: C0000005
Fault address: 60A57817 01:00056817 C:\DivX\AUTORV~1.0_B\Softs\RP9_LI~1\codecs\racp.dll

Call stack:
Address Frame Logical addr Module
60A57817 00000001 0001:00056817 C:\DivX\AUTORV~1.0_B\Softs\RP9_LI~1\codecs\racp.dll


***************************************************
2004/03/01 16:49:48
Exception code: C0000005
Fault address: 004015F7 01:000005F7 C:\DivX\AUTORV~1.0_B\Softs\RP9_LI~1\producer.exe

Call stack:
Address Frame Logical addr Module
004015F7 053B29AC 0001:000005F7 C:\DivX\AUTORV~1.0_B\Softs\RP9_LI~1\producer.exe
00401952 053B2B24 0001:00000952 C:\DivX\AUTORV~1.0_B\Softs\RP9_LI~1\producer.exe
620090DE 053B305C 0001:000080DE C:\DivX\AUTORV~1.0_B\Softs\RP9_LI~1\PNCRT.dll
77E9D702 053BFFEC 0001:0003C702 C:\WINDOWS\system32\kernel32.dll
***************************************************

[Sirber]

Looks like a nice bug :D

Can you post your AVS and your jobfile?

[karl_lillevold]

Big_Berny: Sorry, I do not know the general answer. It depends... on bitrate, and your own preferences for variation in quality in low and high motion scenes.

Caddis: That does look like a nice bug. Unfortunately I have not worked on the wrapper code for the HE-AAC encoder, but I have asked what kind of information would be most useful, and will let you know. I don't really need job file or avs file, I think, since I know how those generally are generated by AutoRV10.

[Sirber]

Originally posted by karl_lillevold
I don't really need job file or avs file, I think, since I know how those generally are generated by AutoRV10. At least it's some infos to look at :)

[Caddis]

I'll post what I think you want.... .rpij and .avs

<?xml version="1.0" encoding="UTF-8"?>
<job xmlns="http://ns.real.com/tools/job.2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<enableTwoPass type="bool">false</enableTwoPass>
<clipInfo>
<entry>
<name>Created with</name>
<value type="string">AutoRV9 (www.video-tools.com)</value>
</entry>
</clipInfo>
<input xsi:type="avFileInput">
<filename type="string">E:\Movie.avs</filename>
</input>
<parOutputs>
<output>
<destinations>
<destination xsi:type="fileDestination">
<filename type="string">E:\Movie.rmvb</filename>
</destination>
</destinations>
<mediaProfile>
<audioMode type="string">music</audioMode>
<disableAudio type="bool">false</disableAudio>
<disableVideo type="bool">false</disableVideo>
<videoMode type="string">sharp</videoMode>
<audienceRefs>
<audienceRef>AutoRV9 Audience File</audienceRef>
</audienceRefs>
</mediaProfile>
</output>
</parOutputs>
<audiences>
<audience>
<avgBitrate type="uint">1052000</avgBitrate>
<maxBitrate type="uint">5030000</maxBitrate>
<name type="string">AutoRV9 Audience File</name>
<streams>
<stream xsi:type="videoStream">
<pluginName type="string">rn-videocodec-realvideo</pluginName>
<codecName type="string">rv10</codecName>
<codecProperties type="bag">
<encoderComplexity type="uint">85</encoderComplexity>
<noisyEdgeFilter type="bool">false</noisyEdgeFilter>
<calcPSNR type="bool">true</calcPSNR>
<maxConsecutiveBFrames type="uint">3</maxConsecutiveBFrames>
<rcEnableCurveCompression type="bool">true</rcEnableCurveCompression>
<rcAnalysisFileName type="string">C:\realvideo.pass</rcAnalysisFileName>
<rcTargetVideoSize type="uint">1280737</rcTargetVideoSize>
<rcPassNumber type="uint">2</rcPassNumber>
<rcLogFileName type="string">c:\realvideo.log</rcLogFileName>
<rcKeyFrameBoost type="uint">0</rcKeyFrameBoost>
<rcHighBitrateReduce type="uint">0</rcHighBitrateReduce>
<rcLowBitrateBoost type="uint">0</rcLowBitrateBoost>
<rcPFrameRefQuant type="uint">6</rcPFrameRefQuant>
<rcBFrameRefQuant type="uint">10</rcBFrameRefQuant>
<inloopCutOffQuant type="uint">11</inloopCutOffQuant>
<inloopCutOffCompatible type="bool">false</inloopCutOffCompatible>
<inloopCutOffBUseRefQuant type="bool">true</inloopCutOffBUseRefQuant>
<customPacketSize type="uint">16000</customPacketSize>
</codecProperties>
<encodingType type="string">vbrBitrate</encodingType>
<quality type="uint">1</quality>
<maxStartupLatency type="double">60</maxStartupLatency>
<maxFrameRate type="double">25</maxFrameRate>
<maxKeyFrameInterval type="double">10</maxKeyFrameInterval>
<enableLossProtection type="bool">false</enableLossProtection>
</stream>
<stream xsi:type="audioStream">
<pluginName type="string">rn-audiocodec-realaudio</pluginName>
<codecName type="string">racp</codecName>
<codecFlavor type="uint">1</codecFlavor>
<streamContext type="bag">
<presentationType type="string">audio-video</presentationType>
<audioMode type="string">music</audioMode>
</streamContext>
</stream>
</streams>
</audience>
</audiences>
</job>

************************************************************
# PLUGINS
LoadPlugin("C:\DivX\AUTORV~1.0_B\SOFTS\AVSFILE\MPEG2DEC3.DLL")
#
# VIDEO SOURCE
Video=Mpeg2Source("E:\movie.d2v")
#
# AUDIO SOURCE
Audio = WavSource("E:\movie\Stream1.wav")
#
# COMBINE VIDEO + AUDIO
Video=AudioDub(Video,Audio)
#
# TRIM MOVIE
Video=Trim(Video,0,276185)
#
# CROPPING
Video=Crop(Video,12,88, -14, -90)
#
# RESIZING
Video=LanczosResize(Video,640,252)
#
# LIMIT Chroma & Luma Value
Video=Limiter(Video)
#
# FINISH
Return(Video)