Log in

View Full Version : Bug in 1.07.2 - Status Log


rpboy
16th February 2006, 16:58
Before I went to bed, I set up for DVD-RB to do three batch jobs. I had run the Prepare phase for each and saved each project. Each had a very different number for the High/Low/Typical bitrates reported during the Prepare phase.

When I woke up this morning, the batch was completed and these were the final lines of the Status Log:

BATCH SUMMARY
Batch Job #1 finished in 00213 minutes.
- HIGH/LOW/TYPICAL Bitrates: 3,064/2,096/2,406 Kbs

Batch Job #2 finished in 00182 minutes.
- HIGH/LOW/TYPICAL Bitrates: 3,064/2,096/2,406 Kbs

Batch Job #3 finished in 00153 minutes.
- HIGH/LOW/TYPICAL Bitrates: 3,064/2,096/2,406 Kbs

That's pretty impressive if there were actually all the same. It looks like it took the numbers for the last job and just put them for all three.

This may have happened in previous versions, I don't know. First time I ever did three jobs at once though, so maybe that's why I noticed it.

laserfan
16th February 2006, 17:17
I did two different DVDs last night and can confirm this rpboy:

BATCH SUMMARY
Batch Job #1 finished in 00214 minutes.
- HIGH/LOW/TYPICAL Bitrates: 8,168/400/3,331 Kbs

Batch Job #2 finished in 00184 minutes.
- HIGH/LOW/TYPICAL Bitrates: 8,168/400/3,331 Kbs

Rippraff
16th February 2006, 19:09
This is an old one (http://forum.doom9.org/showthread.php?p=747175). ;)

Cu Rippraff

jdobbs
16th February 2006, 20:12
It's also one that has me scratching my head... because it never happens in my testing... obviously something out there make it happen. I just can't see how. Last time I put my hands on the code and yelled "HEAL!" several times at the top of my lungs, and that also seemed to have no impact.

Rippraff
16th February 2006, 21:21
Last time I put my hands on the code and yelled "HEAL!" several times at the top of my lungs, and that also seemed to have no impact.
Now I know the way you're fixing bugs. :p http://forum.gleitz.info/images/smilies/ani_lol.gif

Cu Rippraff

jdobbs
16th February 2006, 21:26
It's a nice change from the usual chicken bones and tea leaves I use to make bug fixes.

Rippraff
16th February 2006, 21:29
http://www.jonas-im-wal.de/Gifs/rofl.gif

Cu Rippraff

Prowler
16th February 2006, 22:30
There is no such thing as bugs in DVD-RB they are just undocumented features. ;)

rpboy
16th February 2006, 22:47
It's also one that has me scratching my head... because it never happens in my testing... obviously something out there make it happen. I just can't see how. Last time I put my hands on the code and yelled "HEAL!" several times at the top of my lungs, and that also seemed to have no impact.
If it helps, I am running on Windows XP SP2. I have a P4 3.0 GHz processor with HyperThreading enabled. I have 1 GB of RAM.

For this batch job, I was using the HC Encoder 0.17 and I had Multiple Processor Encodes options (or whatever its called) selected. I had selected a custom matrix (Auto-Q2, if I recall).

laserfan
17th February 2006, 00:58
If it helps, I am running on Windows XP SP2. I have a P4 3.0 GHz processor with HyperThreading enabled. I have 1 GB of RAM...Almost the same here, 3.2GHz.

But as the encodings appear to be perfect I guess I don't give a rip (sorry) whether this is fixed or not. :cool:

blutach
17th February 2006, 07:26
No matter what yer log says rpboy, that was the most productive night's sleep anyone's had!

Regards

rpboy
17th February 2006, 08:24
But as the encodings appear to be perfect I guess I don't give a rip (sorry) whether this is fixed or not. :cool:
Thanks, he'll be here all week. :p

Yeah, certainly not a serious bug by any means. Just a strange one.

Cropsy
17th February 2006, 12:33
BATCH SUMMARY
Batch Job #1 finished in 00246 minutes.
- HIGH/LOW/TYPICAL Bitrates: 2768/393/2429 Kbs

Batch Job #2 finished in 00216 minutes.
- HIGH/LOW/TYPICAL Bitrates: 3273/393/2441 Kbs

Batch Job #3 finished in 00219 minutes.
- HIGH/LOW/TYPICAL Bitrates: 3124/393/2393 Kbs

Batch Job #4 finished in 00163 minutes.
- HIGH/LOW/TYPICAL Bitrates: 4977/400/4043 Kbs

Batch Job #5 finished in 00138 minutes.
- HIGH/LOW/TYPICAL Bitrates: 8552/1229/4980 Kbs

Batch Job #6 finished in 00222 minutes.
- HIGH/LOW/TYPICAL Bitrates: 3159/393/2402 Kbs

Batch Job #7 finished in 00222 minutes.
- HIGH/LOW/TYPICAL Bitrates: 2917/393/2460 Kbs

Batch Job #8 finished in 00123 minutes.
- HIGH/LOW/TYPICAL Bitrates: 6067/786/5186 Kbs

Batch Job #9 finished in 00216 minutes.
- HIGH/LOW/TYPICAL Bitrates: 3502/393/2426 Kbs

Batch Job #10 finished in 00217 minutes.
- HIGH/LOW/TYPICAL Bitrates: 3235/393/2457 Kbs

Batch Job #11 finished in 00216 minutes.
- HIGH/LOW/TYPICAL Bitrates: 2756/393/2413 Kbs

Batch Job #12 finished in 00217 minutes.
- HIGH/LOW/TYPICAL Bitrates: 3407/393/2404 Kbs

Batch Job #13 finished in 00230 minutes.
- HIGH/LOW/TYPICAL Bitrates: 2673/393/2407 Kbs


Totally perfect ;-))))))))))))))))))

jdobbs
17th February 2006, 12:35
I did a four DVD jobs last night, and mine came out right too. I know there's something in there.... but why can't I find it? The code for this reporting is incredibly simple...

Rockas
17th February 2006, 13:51
@Cropsy
13 jobs!?!?!
That's what I call "being productive" http://www.thestylemachine.com/smileys/palmas.gif http://www.thestylemachine.com/smileys/uy.gif

rpboy
18th February 2006, 02:29
I did a four DVD jobs last night, and mine came out right too. I know there's something in there.... but why can't I find it? The code for this reporting is incredibly simple...
Would it help if I sent you my INI file?

jdobbs
18th February 2006, 03:14
No... not really. I looked at the code earlier today. It's incredible that it could do this. The "minutes" in the output comes from the same text variable as the following outut... how one could be right and the other wrong is beyond me.