Need to understand

[triky40]

I'm new in this forum.

Let me state my problem.

I tried to use "RB free version" on my desktop (Celeron 466 mHz) and it gave a problem (drop frames or some thing like that) then I tried "RB free version" on my wife laptop (of course it is newer Del Inspirion 600M) and it works fine.

I order (sorry which verb I should use,"order", "purchase", or "donate") "RB pro version" and install it into my wife laptop but I want to install on my desktop to see whether it works. Wife doesn't like me to use her computer for some thing like this. To her this is a wasted money and time. No argue with her because I will not win anyway.

Question:
If it works then great but what if it does not work like "RB free version" then will I lost 1 out of 5 "unique System ID"? Can I recover it when I uninstall "RB pro version" from my desktop?

Thanks,
Tri

[jikchung]

See if this post by jdobbs answers your question, looks like it won't be an issue for you:

http://forum.doom9.org/showthread.php?p=784789#post784789

[Trahald]

I'm new in this forum.Welcome! :)I order (sorry which verb I should use,"order", "purchase", or "donate") "RB pro version" "Donate" is most applicable.No argue with her because I will not win anyway.you are wise and will have a long and happy marriage.

[jdobbs]

Is your desktop system's processor or memory overclocked? That's almost always the problem with lost frames.

Just a note: a 466MHZ Celeron probably isn't quite fast enough for reasonable processing times. It will work -- but expect it to be slow.

[triky40]

Quote:"Is your desktop system's processor or memory overclocked? That's almost always the problem with lost frames."

No, just a plain Celeron 466 mhz with 252 MB of ram. ( I'm not good enough to mess with internal computer).

The attached is a question that I asked with another forum. Do not mean to ask again but greatly appreciate if you can help with the answer.

Sorry about not asking the question clearly.

First, I used "wizard +DVD Decrypter" to decrypt the movie in DVD Decrypter folder.
Second, using Shrinks on the files in "DVD Decrypter folder" and save the result in "Shrink folder"- works great - can play with Media player classic. The whole process tooks 4 hours and 30 minutes.
Third, to test DVD RB, using DVD RB free edition on the files in "DVD Decrypter folder" and save the result in "DVD Rebuilder folder". The whole process took little more than 30 minutes ??? kind of abnormal based on what I have been reading from this forum. Play VIDEO_TS.IFO with Media player classic. It does play the menu. When I click on "play movie" in the menu. The menu stays there with the sound of the movie.
I uninstall DVD RB and re-install it and go through the setting again but it does not make any different.

My computer is Celeron 466 mhz. I know it is the antique device but it still works for me.

attached is the RB log

[07:56:36] One Click encoding activated...
-----------------
[07:56:37] Phase I, PREPARATION started.
- VTS_01: 2,560,059 sectors.
-- Scanning and writing .D2V file
-- Processed 177,588 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 87.7%
- Overall Bitrate : 4,189Kbs
- Space for Video : 3,787,652KB
- HIGH/LOW/AVERAGE Cell Bitrates: 5,001/600/4,189 Kbs
[08:10:52] Phase I, PREPARATION completed in 14 minutes.
[08:10:52] Phase II ENCODING started
- Creating M2V for VTS_01 segment 0
- Creating M2V for VTS_01 segment 1
- Creating M2V for VTS_01 segment 2
- Creating M2V for VTS_01 segment 3
- Creating M2V for VTS_01 segment 4
- Creating M2V for VTS_01 segment 5
- Creating M2V for VTS_01 segment 6
- Creating M2V for VTS_01 segment 7
- Creating M2V for VTS_01 segment 8
- Creating M2V for VTS_01 segment 9
- Creating M2V for VTS_01 segment 10
- Creating M2V for VTS_01 segment 11
- Creating M2V for VTS_01 segment 12
- Creating M2V for VTS_01 segment 13
- Creating M2V for VTS_01 segment 14
- Creating M2V for VTS_01 segment 15
- Creating M2V for VTS_01 segment 16
- Creating M2V for VTS_01 segment 17
- Creating M2V for VTS_01 segment 18
- Creating M2V for VTS_01 segment 19
- Creating M2V for VTS_01 segment 20
- Creating M2V for VTS_01 segment 21
- Creating M2V for VTS_01 segment 22
- Creating M2V for VTS_01 segment 23
- Creating M2V for VTS_01 segment 24
- Creating M2V for VTS_01 segment 25
- Creating M2V for VTS_01 segment 26
- Creating M2V for VTS_01 segment 27
- Creating M2V for VTS_01 segment 28
- Creating M2V for VTS_01 segment 29
[08:14:10] Phase II ENCODING completed in 4 minutes.
[08:14:10] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Reading/processing TMAP table...
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 2 VOBID: 1 CELLID: 3
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 3 VOBID: 1 CELLID: 4
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 4 VOBID: 1 CELLID: 5
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 5 VOBID: 1 CELLID: 6
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 6 VOBID: 1 CELLID: 7
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 7 VOBID: 1 CELLID: 8
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 8 VOBID: 1 CELLID: 9
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 9 VOBID: 1 CELLID: 10
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 10 VOBID: 1 CELLID: 11
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 11 VOBID: 1 CELLID: 12
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 12 VOBID: 1 CELLID: 13
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 13 VOBID: 1 CELLID: 14
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 14 VOBID: 1 CELLID: 15
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 15 VOBID: 1 CELLID: 16
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 16 VOBID: 1 CELLID: 17
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 17 VOBID: 1 CELLID: 18
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 18 VOBID: 1 CELLID: 19
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 19 VOBID: 1 CELLID: 20
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 20 VOBID: 1 CELLID: 21
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 21 VOBID: 1 CELLID: 22
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 22 VOBID: 1 CELLID: 23
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 23 VOBID: 1 CELLID: 24
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 24 VOBID: 1 CELLID: 25
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 25 VOBID: 1 CELLID: 26
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 26 VOBID: 1 CELLID: 27
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 27 VOBID: 1 CELLID: 28
- Possible dropped frame(s) noted in this segment, continuing...
- Rebuilding segment 28 VOBID: 1 CELLID: 29
- Possible dropped frame(s) noted in this segment, continuing...
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 29 VOBID: 2 CELLID: 1
- Possible dropped frame(s) noted in this segment, continuing...
- Updating NAVPACKS for VOBID_02
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
- Updating TMAP table...
Correcting VTS Sectors...
[08:30:13] Phase III, REBUILD completed in 16 minutes.
Done.
[08:30:13] PREPARE/ENCODE/REBUILD completed in 34 min.Thanks,
Tri

[triky40]

See if this post by jdobbs answers your question, looks like it won't be an issue for you:

http://forum.doom9.org/showthread.php?p=784789#post784789

Thanks for the link.

Tri

[wmansir]

Check the system requirements for your encoder (CCE, QuEnc, HC, etc).

On your system the encode phase should take many hours, not 4 minutes as the log suggests. Whatever encoder you are using probably doesn't support your chip, so it's not encoding the video at all.