Missing .m2v when encoding

[Joe_smish]

I've been trying to get DVD-RB to work for me for the past month. I keep hitting error after error and I dont know why. I just wish someone was actually here to show me how to do this. Anyways, I just installed the newest version. And I got this new error at the encode stage. Apparently people have gotten it before but I tried the stuff to fix it and I cant. Its the one about the missing .m2v file. I'm trying to back up "Fight Club" that I used the newest version of Decryptor to rip, vobblanker to blank the extras that I dont want. Before I installed this new version I was able to get to the rebuild phase before I got the error about the single frame stuff. I installed this new version and was going to encode again with the MIN_BITRATE= 500 added into the options to see if this solved the single frame problem. But I didnt get that far. I got this new error that I never got before. I checked to make sure that the dgdecod.dll file was in the right spot and stuff and it was. The settings are all the same as I used with the previous versions. I'm not sure whats going on. I havent had a successful back up with this software yet and I'm kind of getting discouraged. I hear such great things about it and am very excited to see what it can do. Thats why I'm being so persistent. If anyone goes to Uconn and uses this program please let me know so maybe you can give me a run through of how it works and try to help me figure this out. Thanks.

[Rockas]

First:
Have you tried one DVD without any kind of preprocess?

Second:
How did you installed? Have you tried to use my Installer?

[JohnG]

Ironically, I just backed that DVD up last week. Once using CCE and the other with HC. I didn't preprocess except to remove the PUOP's. I don't remember it having any extra material anyway, just commentaries (maybe a different version than yours). If you use Rockas' installer, you will save yourself a lot of headaches. Just remove/uninstall/delete the stuff you've already done (aside from the encoders of course) and download his installer from the link at the bottom of his post. Don't give up, Rebuilder produces superb results.

[Joe_smish]

yeah i used your installer. And no I didnt try one without preprocessing. The reason: I already have a back up of Fight Club that I made with DVD shrink. But it was compressed all the way to 60%. So I want to make the same exact back up but with DVD-RB to compare. Thats why I was trying so hard to get this preprocessed one to work, sort of as a control to have the same files. No what I mean? I just cant figure out why I have this new error now when I didnt have it before. It wasnt so bad before I got this version because every time I ran into a problem I fixed it and made progress, I was in the rebuild stage. Now I cant even get through the encode stage. And I'm using the same exact movie files and same settings. So maybe the older version skipped something that the new version picked up on or something.

[JohnG]

Originally posted by Joe_smish
yeah i used your installer. And no I didnt try one without preprocessing. The reason: I already have a back up of Fight Club that I made with DVD shrink. But it was compressed all the way to 60%.

Yikes! That's a tough movie. Is it even watchable with Shrink? I redid the CCE basic version with HC in order to use the new QLB matrix because I wasn't happy with the cce copy.

[Joe_smish]

Its watchable, and that 60% is even after I blanked with vobblanker. But I'm really curious to see how the quality compares b/c I heard great things about DVD-RB. So I really want to get this back up to work with the same files for a true comparisson. DVD-RB is trying to compress to a 60.5% ratio.

[Joe_smish]

I just started the encode with the non-preprocessed version of Fight Club (the one I didnt use vobblanker on) and it got past the error part. However, had I let it finish the encode it would have been to a ratio of 56%. Do you guys think that 4.5% will make that much of a difference? If I can figure out how to make the preprocessed one work do you think that 4% gain will increase the quality enough to make it worth it? I have never seen rebuilder in action so I dont know.

[JohnG]

My guess is that the results will still surpass Shrink by a wide margin. What encoder are you using?

edit: Did you try to run the blanked version through Shrink with no compression and then run it through rebuilder? Somehow the files may have become corrupt and Shrink might resolve that for you.

[lark]

how about making a oversized DVD with RB and then running vobblanker to get rid of the unneeded material? hopefully you have a fast rig...

regards
t :)

[pg55555]

Joe_smish
If you are new to RB, ALWAYS start with an unprocessed source. Only after you have been able to make a working backup with RB you should start trying with pre-processed sources.

In this way you'll know is not a installation problem neither a RB problem.

Most people DO preprocessing and most of the times there are not problems. But sometimes, some preprocessed source runs into problem. In that case you can post your problem, but PLEASE indicate that your source is pre-processed.

Regarding how to improve the quality of your RB output by increasing the bitrate available to the main movie, you have different options, without preprocessing:
- Half D1 and Half Space for extras
- Steal Space from extras
- The new (RB PRO only) options to blank cells (similar to VOBBlanker) in RB directly

[Joe_smish]

Originally posted by JohnG
My guess is that the results will still surpass Shrink by a wide margin. What encoder are you using?

edit: Did you try to run the blanked version through Shrink with no compression and then run it through rebuilder? Somehow the files may have become corrupt and Shrink might resolve that for you.

I tried that before too. Didnt work. I guess I will just keep the extras and settle for the 56% compression rate. Thats the only thing I can think of to do. The main thing I'm trying to figure out is why I'm getting this error now and not before. I'm using the same material, just a different version of DVD-RB. I'm using CCE Trial version 2.67. I do think it has to do with the fact that I blanked stuff using VobBlanker b/c I have no problem when I left it as is. Only after I used vobblanker. I heard that you can use DVD-RB to blank stuff out. Is that possible with the freeware v0.82? If not, is there another way to donate to the cause b/c I dont have paypal or a credit card.

As for pg55555, I did indicate that it was preprocessed in my original post
I'm trying to back up "Fight Club" that I used the newest version of Decryptor to rip, vobblanker to blank the extras that I dont want.

[pg55555]

I knew you have posted about the pre-processing. And the first suggestion, from Rockas, was "Try without pre-processing"

My point was directed to all the people that do not clarify the point from the beginning.

And from the title of the thread "Im getting frustrated" and the first phrase of your post :"I've been trying to get DVD-RB to work for me for the past month".

And in all that month you never try without preprocessing!!

[Rockas]

it would have been to a ratio of 56%. Do you guys think that 4.5% will make that much of a difference? If I can figure out how to make the preprocessed one work do you think that 4% gain will increase the quality enough to make it worth it?

That depends of the source...
...lets say your original has a medium bitrate of 8000kbps (this is just an example) now if you get a message of 56% of compression from rebuilder your backup would have a medium bitrate of 4480kbps and with that bitrate I would say that you (almost- it depends of the size of your TV) couldn't see the difference between the original and the backup.

On the other way... if your source has a medium bitrate of 3000kbps then the result would require theuse of a good Matrix on the Encoding step :D

[Joe_smish]

Originally posted by pg55555
And in all that month you never try without preprocessing!!

I did try without preprocessing after I ran into errors in the past to see if it worked. Sometimes it did and sometimes it didnt. Thats why I still have the original decrypted files still on my comp. I use them as a test to see if it is DVD-RB or something that I altered that is causing the error. Im confused as to why I didnt get this error with 0.80 w/ the preprocessed stuff but now I am with 0.82. It has something to do with vobblanker b/c after testing with the unaltered files, it worked fine. I tried processing with vobblanker again, but ran into the error. Any suggestions as to what might be going on with vobblanker to cause this new error with DVD-RB v0.82? I'm using the newest version of blanker.

[pg55555]

As mentioned before, pre-processing can work MOST of the times, but sometimes it dont.

Depends on the source, depends in what you blank / strip, depends on the program you use, depends on WHO does it, maybe depends on your PC configuration. Depends on so many thinks that is very difficult to control. Thats the reason RB developer is not commited to support RB working on pre-processed sources.

But it works most of the time.

And if not, you can always do a POST-PROCESSING: Tweak the output size with the "TargetSize=" setting and do the blanking afterwards.

[Joe_smish]

How do you do that?? I bet that would work well. I would be willing to try it. EDIT: specifically, how do you change the target size?

[pg55555]

Look at the Sticky post "Settings" at the top of the Forum, look for Hidden Settings

[Joe_smish]

It says for "Advanced Users". I dont think I'd call myself that ;) but I will try it tonight and let you know how it worked tommorow.

[lark]

that's just what i was proposing a bit earlier with oversized DVD ;-)

1 thing just did pop into my mind: when you say that .80 works with vobblanked dvd and .82 doesn't, are you using the SAME vobblanked source or did you blank with different ver of vobblanker (or perhaps in a different way)?

regards
t :)

[Joe_smish]

Same source.

I just tried it with the unedited source file (the original that I ripped) However, When I got to the very last segment or .avs file, I got the same error that the .m2v didnt exist. This segment is a single frame. What should I do about that? Its the last file everything else was successful. It wont let me rebuild until I get past this file so any suggestions?

EDIT: Also, after encoding everything, should I blank the stuff that I dont want prior to rebuilding or after rebuilding?

[lark]

do blanking after rebuilding
t :)

[Joe_smish]

thanks.:) Any Idea on how to solve the problem? I'm basically back where I started with the preprocessed material, just at the very end of the line rather than the beginning.;) :(

[lark]

sorry, i don't think that i can help.
that the last segment is only 1 single frame sounds scary to me.
somehow i had the impression that it should be at least 12 frames (PAL), but i might be wrong. can you verify that from the rebuilder.ecl & AVS file?

what id you try to encode that AVS file manually?

regards
t :)

[Joe_smish]

#------------------
# AVS File Created by DVD Rebuilder
# VOBID:25, CELLID:01
#------------------
LoadPlugin("C:\Program Files\DVD Burning\AviSynth 2.5\plugins\DGDecode.dll")
mpeg2source("D:\Movies (compressed)\DVDRebuilder Work\D2VAVS\V02.D2V")
trim(200208,200208)
ConvertToYUY2(interlaced=true)
AudioDub(BlankClip())


Yeah its a one frame segment. I tried encoding it with TMPGEnc but I still get the error with DVD-RB and the rebuild button isnt accessable, so even though its encoded with TMPGEnc, I cant rebuild the files.

[pg55555]

Working in a unpreprocessed source, you can complete the backup using RB 0.80 but you get that missing m2v file errror with RB0.83. Right?

Same settings, same encoder, the only think you change is the RB version, Right?

[Joe_smish]

The source file is a file that I ripped using DVDDecryptor. I didnt do anything to it. I have version 0.82 of DVD-RB. I got to the very last segment during the encode phase and got the error that .m2v was missing. I looked at the AVS file and this segment is only one frame long, if that has anything to do with the error. I'm not sure if this would happen with version 0.80, b/c I never fully encoded the non processed version. However, I was able to fully encode the preprocessed version with 0.80 and I ran into an error during the rebuild phase. Jobbs said I could solve the error if I added the min_bitrate=500 line to the [Options] file thing. By the time I was able to try this solution, a new version was out. I downloaded the new version and tried it again. I had to reencode it with the new bitrate thing. But this time with the preprocessed material I couldnt even get past the first segment withough getting the .m2v missing file error, never mind make it to the rebuild stage. After that I thought maybe it was because I added the new bitrate thing so I tried it without that and still got the error. Thats when I started this thread and you guys told me to try it with out the preprocessing. So I did. It encoded everything up to the last segment and I got that same m2v missing error. And here we are. I hope I explained it well enough.:)

[jptheripper]

after you preprocessed, you re-prepared from scratch right? not just reencoded? if you change anything you have to start over

[lark]

if you are adventurous, you can try to change the Progress=2 in the rebuilder.inf. make sure that you have the manually encoded m2v in the directory with correct name (same as the AVS, but with M2V extension). perhaps you can then hit the rebuild button.

you might need to update the Encode_progress as well (set it to the number of AVS files: most probably just increment by 1).

obviously this is not a cure to the initial problem, but might get you a bit further...

regards
t :)

[Joe_smish]

Originally posted by jptheripper
after you preprocessed, you re-prepared from scratch right? not just reencoded? if you change anything you have to start over

Yup I reprepared, every time I was going to try to re encode I reprepared.

[jptheripper]

recmmendation at this point

delete everything

reinstall latest (0.82.1) with rockas installer only.

rerip movie for clean source

rb with 0 preprocessing.

see if that works.

if so, then recreate preprocessing

[Joe_smish]

still noone has addressed the direct issue that the .m2v is missing. Is this b/c there is no direct solution to that so we are trying to come up with possible solutions? Does anyone have at least an idea of what caused this error? I want to know how to solve the problems I run into but also would like to know what caused them as well.

[lark]

that's what i was saying ;-)

at least i've no idea, why it's not encoded automagically, especially if manual encoding works. i personally don't use tmpgenc and thus have no idea, how rb commands it. if it was cce, the problem might be in the ecl file.

perhaps you need jdobbs' help again.

regards
t :)

[Joe_smish]

Originally posted by lark
perhaps you need jdobbs' help again.


He hasnt visited this post yet with his input :(

[JohnG]

Originally posted by Joe_smish
He hasnt visited this post yet with his input :(

Perhaps it's the dodgy title of the thread? ;)

[Joe_smish]

Originally posted by JohnG
Perhaps it's the dodgy title of the thread? ;)
Like the new title??

Anyways, I just uninstalled and reinstalled EVERYTHING that DVD-RB uses including RB itself. Tonight I will rip Fight Club once again and Encode again. Progress report in the morning.

[eriksen76]

I'm also starting to get the "missing m2v file" errors. This has started since 0.82

The source is preprocessed in the same way as I always do (Dvdremake) and I have never run into problems until now.

Very strange I think....

/Eriksen76

[Joe_smish]

I just noticed that when I open the movie in DVD-RB (the movie I just ripped) it shows only the VTS_2 files and not all the other ones. This is the file that is the actual movie. Will this affect anything and maybe the fact that it isnt showing any other ones have to do with the missing .m2v?

[pg55555]

No, by default RB only encodes the VTS that are larger than 50 MB. And it shows in its windows only them.

What encoder are you using? YOu mentioned that tryied TMPGEnc for your manual encoding, but TMPGEnc is not supported by RB. If you are using CCE, what version? Did you try to encode manually the problematic segment with CCE? If you succeded I think you have to tell RB that the encoding process was completed. I think it can be done by changing the Progress setting in Rebuilder.inf (or in Rebuilder.ecl, I do not remember now). If you succeed, the Rebuild button should appear lighted.

Regardin WHY the problem, here a couple of references:

From 0.80 changelog:
- Added code to do a check for existing .M2V file after a segment encode is completed, and to reencode the segment if it does not (up to 3 tries). There have been reports of missing .M2V files causing errors during rebuild. Most often this is caused by an errant keystroke stopping the encode accidentally -- but it appears that sometimes an encoder can abnormally exit leaving DVD-RB without an M2V to process. This code should reduce that likelihood.

Fom 0.81 Changelog
- Changed the actions taken for segments of less than 60 frames. Instead of setting to CBR, VBR is used but with a minimum bitrate. This more accurately correct the reason for adding this fix originally.

Maybe your problem with this problematic one frame segment was introduced by this change in 0.81. I use to have problems with VBR and CCE in small segments, which were resolved by encoding in CBR.

From 0.81 PRO Changelog:
- Updated STILLFRAME code so frames are no longer reencoded but instead are kept intact and are reintegrated into the output stream.

This gives me the idea of using the "No compression (100% video)" Mode to get the m2v segment you need: Run the prepare en encode steps in other directoy, and copy the generated m2v for your missing segment. Also look at the Rebuilder.inf (or was Rebuilder.ecl?) for the right number for the progress setting

Good luck

[TK8472]

I'm also getting this error on my latest encode with Pro 0.84 and 0.83. I'm pre-processing with DVDRemake Pro, but I've done a lot of successful encodes previous to these versions. No other changes to my system or setup have been made. I can't say it started with 0.83 though, as I've not done any encodes for several versions.

'ERROR: File V01001400001015 shows completed, but no .M2V file exists. Aborted.'

Here's the status:

-----------------
[22:38:04] Phase I, PREPARATION started.
- CCE SP 2.67.0.27 encoder selected.
- VTS_01: 2,327,692 sectors.
-- Scanning and writing .D2V file
-- Processed 141,517 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 94.7%
- Overall Bitrate : 5,281Kbs
- Space for Video : 3,805,330KB
- HIGH/LOW/TYPICAL Bitrates: 6,079/500/5,281 Kbs
[22:42:24] Phase I, PREPARATION completed in 4 minutes.
[22:46:40] 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
-- Encoding resulted in no .M2V, retrying.
- Creating M2V for VTS_01 segment 14
-- Encoding resulted in no .M2V, retrying.
- Creating M2V for VTS_01 segment 14

----------------------

Both Pro 0.83 and 0.84 stopped on the same file. If it matters, the movie is 'Dagon', with the trailers removed and the menu buttons hidden.

Tools:
AviSynth 2.5
dgdecode.dll (AviSynth plugins)
CCE SP v2.67.00.27
DVDDecrypter 3.5.4.0
DvDReMake Pro 2.6.7

I haven't tried without any pre-processing, but can if it'll help. I just wanted to post that I was seeing this error as well.

[pg55555]

TK8472
Try without preprocessing to verify the error is not related. Select just 2 passes, so you'll get the answer faster.

Try also OPV, and check if it happens in this mode.

Check your rebuilder.ecl file for the problematic segment (or the corresponding avs file) and look at the size of the segment: is an small segment (less than 60 frames?, one frame?. AS Joe_smish is getting this error in an one frame segment...

[Joe_smish]

Originally posted by pg55555
What encoder are you using? YOu mentioned that tryied TMPGEnc for your manual encoding, but TMPGEnc is not supported by RB. If you are using CCE, what version? Did you try to encode manually the problematic segment with CCE? If you succeded I think you have to tell RB that the encoding process was completed. I think it can be done by changing the Progress setting in Rebuilder.inf (or in Rebuilder.ecl, I do not remember now). If you succeed, the Rebuild button should appear lighted.

Maybe your problem with this problematic one frame segment was introduced by this change in 0.81. I use to have problems with VBR and CCE in small segments, which were resolved by encoding in CBR.


Im running the 2.67 SP trial version. How should I manualy encode the segment in CCE? What settings and such? As said before I re-ripped the DVD after uninstalling and reinstalling EVERYTHING related to this process. Ran into the same error on the unprocessed stuff at the very last segment. Didnt bother with the preprocessing untill I solve this error with the non processed stuff. I've never really used CCE before so I'm not sure what settings to use and such.

[TK8472]

Originally posted by pg55555
TK8472
Try without preprocessing to verify the error is not related. Select just 2 passes, so you'll get the answer faster.

Try also OPV, and check if it happens in this mode.

Check your rebuilder.ecl file for the problematic segment (or the corresponding avs file) and look at the size of the segment: is an small segment (less than 60 frames?, one frame?. AS Joe_smish is getting this error in an one frame segment...

OK, here's what happened using OPV direct from the unprocessed ISO. It made it through the Encode, but failed on the same file during Rebuild.

Fatal Error
ERROR: The input file "V01001400001015.M2V" is missing frames. Rebuild aborting.

Status:
-----------------
[19:48:14] Phase I, PREPARATION started.
- CCE SP 2.67.0.27 encoder selected.
- "One Pass VBR (w/analysis)" mode is enabled.
- VTS_01: 2,327,692 sectors.
-- Scanning and writing .D2V file
-- Processed 141,517 frames.
-- Building .AVS and .ECL files
- VTS_02: 59,015 sectors.
-- Scanning and writing .D2V file
-- Processed 4,661 frames.
-- Building .AVS and .ECL files
- VTS_03: 40,635 sectors.
-- Scanning and writing .D2V file
-- Processed 2,980 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 90.9%
- Overall Bitrate : 5,037Kbs
- Space for Video : 3,825,334KB
- Analyzing VTS_01 for optimal Q factor.
-- TargetSize (sectors):1,853,241
-- Sampling 1416 of 141517 frames.
-- Predicted size (sectors) at Q=20: 1,817,762
-- Predicted size (sectors) at Q=19: 1,869,286
- Q Value selected: 20
- Analyzing VTS_02 for optimal Q factor.
-- TargetSize (sectors):52,236
-- Sampling 48 of 4661 frames.
-- Predicted size (sectors) at Q=23: 38,620
-- Predicted size (sectors) at Q=14: 49,635
-- Predicted size (sectors) at Q=13: 50,681
-- Predicted size (sectors) at Q=12: 51,662
-- Predicted size (sectors) at Q=11: 52,880
- Q Value selected: 12
- Analyzing VTS_03 for optimal Q factor.
-- TargetSize (sectors):35,880
-- Sampling 36 of 2980 frames.
-- Predicted size (sectors) at Q=21: 18,882
-- Predicted size (sectors) at Q=7: 21,718
-- Predicted size (sectors) at Q=3: 22,229
-- Predicted size (sectors) at Q=1: 22,616
- Q Value selected: 1
- HIGH/LOW/TYPICAL Bitrates: 6,000/500/5,037 Kbs
[19:55:20] Phase I, PREPARATION completed in 7 minutes.
[19:56:38] 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
- Extracting STILLS for VTS_01 segment 24
- Extracting STILLS for VTS_01 segment 25
- Creating M2V for VTS_02 segment 0
- Extracting STILLS for VTS_02 segment 1
- Extracting STILLS for VTS_02 segment 2
- Extracting STILLS for VTS_02 segment 3
- Extracting STILLS for VTS_02 segment 4
- Extracting STILLS for VTS_02 segment 5
- Extracting STILLS for VTS_02 segment 6
- Extracting STILLS for VTS_02 segment 7
- Extracting STILLS for VTS_02 segment 8
- Extracting STILLS for VTS_02 segment 9
- Extracting STILLS for VTS_02 segment 10
- Extracting STILLS for VTS_02 segment 11
- Extracting STILLS for VTS_02 segment 12
- Extracting STILLS for VTS_02 segment 13
- Extracting STILLS for VTS_02 segment 14
- Extracting STILLS for VTS_02 segment 15
- Extracting STILLS for VTS_02 segment 16
- Extracting STILLS for VTS_02 segment 17
- Extracting STILLS for VTS_02 segment 18
- Extracting STILLS for VTS_02 segment 19
- Extracting STILLS for VTS_02 segment 20
- Extracting STILLS for VTS_02 segment 21
- Extracting STILLS for VTS_02 segment 22
- Extracting STILLS for VTS_02 segment 23
- Extracting STILLS for VTS_02 segment 24
- Extracting STILLS for VTS_02 segment 25
- Extracting STILLS for VTS_02 segment 26
- Extracting STILLS for VTS_02 segment 27
- Extracting STILLS for VTS_02 segment 28
- Extracting STILLS for VTS_02 segment 29
- Extracting STILLS for VTS_02 segment 30
- Extracting STILLS for VTS_02 segment 31
- Extracting STILLS for VTS_02 segment 32
- Extracting STILLS for VTS_02 segment 33
- Extracting STILLS for VTS_02 segment 34
- Extracting STILLS for VTS_02 segment 35
- Extracting STILLS for VTS_02 segment 36
- Extracting STILLS for VTS_02 segment 37
- Extracting STILLS for VTS_02 segment 38
- Extracting STILLS for VTS_02 segment 39
- Extracting STILLS for VTS_02 segment 40
- Extracting STILLS for VTS_02 segment 41
- Extracting STILLS for VTS_02 segment 42
- Extracting STILLS for VTS_02 segment 43
- Extracting STILLS for VTS_02 segment 44
- Extracting STILLS for VTS_02 segment 45
- Extracting STILLS for VTS_02 segment 46
- Extracting STILLS for VTS_02 segment 47
- Extracting STILLS for VTS_02 segment 48
- Extracting STILLS for VTS_02 segment 49
- Extracting STILLS for VTS_02 segment 50
- Extracting STILLS for VTS_02 segment 51
- Extracting STILLS for VTS_02 segment 52
- Extracting STILLS for VTS_02 segment 53
- Extracting STILLS for VTS_02 segment 54
- Extracting STILLS for VTS_02 segment 55
- Extracting STILLS for VTS_02 segment 56
- Extracting STILLS for VTS_02 segment 57
- Extracting STILLS for VTS_02 segment 58
- Extracting STILLS for VTS_02 segment 59
- Extracting STILLS for VTS_02 segment 60
- Extracting STILLS for VTS_02 segment 61
- Extracting STILLS for VTS_02 segment 62
- Extracting STILLS for VTS_02 segment 63
- Extracting STILLS for VTS_02 segment 64
- Extracting STILLS for VTS_02 segment 65
- Extracting STILLS for VTS_02 segment 66
- Extracting STILLS for VTS_02 segment 67
- Extracting STILLS for VTS_02 segment 68
- Extracting STILLS for VTS_02 segment 69
- Extracting STILLS for VTS_02 segment 70
- Extracting STILLS for VTS_02 segment 71
- Extracting STILLS for VTS_02 segment 72
- Extracting STILLS for VTS_02 segment 73
- Extracting STILLS for VTS_02 segment 74
- Extracting STILLS for VTS_02 segment 75
- Extracting STILLS for VTS_02 segment 76
- Extracting STILLS for VTS_02 segment 77
- Extracting STILLS for VTS_02 segment 78
- Extracting STILLS for VTS_02 segment 79
- Extracting STILLS for VTS_02 segment 80
- Extracting STILLS for VTS_02 segment 81
- Extracting STILLS for VTS_02 segment 82
- Extracting STILLS for VTS_02 segment 83
- Extracting STILLS for VTS_02 segment 84
- Extracting STILLS for VTS_02 segment 85
- Extracting STILLS for VTS_02 segment 86
- Extracting STILLS for VTS_02 segment 87
- Extracting STILLS for VTS_02 segment 88
- Extracting STILLS for VTS_02 segment 89
- Extracting STILLS for VTS_02 segment 90
- Extracting STILLS for VTS_02 segment 91
- Extracting STILLS for VTS_02 segment 92
- Extracting STILLS for VTS_02 segment 93
- Extracting STILLS for VTS_02 segment 94
- Extracting STILLS for VTS_02 segment 95
- Extracting STILLS for VTS_02 segment 96
- Extracting STILLS for VTS_02 segment 97
- Extracting STILLS for VTS_02 segment 98
- Extracting STILLS for VTS_02 segment 99
- Extracting STILLS for VTS_02 segment 100
- Extracting STILLS for VTS_02 segment 101
- Extracting STILLS for VTS_02 segment 102
- Extracting STILLS for VTS_02 segment 103
- Extracting STILLS for VTS_02 segment 104
- Extracting STILLS for VTS_02 segment 105
- Extracting STILLS for VTS_02 segment 106
- Extracting STILLS for VTS_02 segment 107
- Extracting STILLS for VTS_02 segment 108
- Extracting STILLS for VTS_02 segment 109
- Extracting STILLS for VTS_02 segment 110
- Extracting STILLS for VTS_02 segment 111
- Extracting STILLS for VTS_02 segment 112
- Extracting STILLS for VTS_02 segment 113
- Extracting STILLS for VTS_02 segment 114
- Extracting STILLS for VTS_02 segment 115
- Extracting STILLS for VTS_02 segment 116
- Extracting STILLS for VTS_02 segment 117
- Extracting STILLS for VTS_02 segment 118
- Extracting STILLS for VTS_02 segment 119
- Extracting STILLS for VTS_02 segment 120
- Extracting STILLS for VTS_02 segment 121
- Extracting STILLS for VTS_02 segment 122
- Extracting STILLS for VTS_02 segment 123
- Extracting STILLS for VTS_02 segment 124
- Extracting STILLS for VTS_02 segment 125
- Extracting STILLS for VTS_02 segment 126
- Extracting STILLS for VTS_02 segment 127
- Extracting STILLS for VTS_02 segment 128
- Extracting STILLS for VTS_02 segment 129
- Extracting STILLS for VTS_02 segment 130
- Extracting STILLS for VTS_02 segment 131
- Extracting STILLS for VTS_02 segment 132
- Extracting STILLS for VTS_02 segment 133
- Extracting STILLS for VTS_02 segment 134
- Extracting STILLS for VTS_02 segment 135
- Extracting STILLS for VTS_02 segment 136
- Extracting STILLS for VTS_02 segment 137
- Extracting STILLS for VTS_02 segment 138
- Extracting STILLS for VTS_02 segment 139
- Extracting STILLS for VTS_02 segment 140
- Extracting STILLS for VTS_02 segment 141
- Extracting STILLS for VTS_02 segment 142
- Extracting STILLS for VTS_02 segment 143
- Extracting STILLS for VTS_02 segment 144
- Extracting STILLS for VTS_02 segment 145
- Extracting STILLS for VTS_02 segment 146
- Extracting STILLS for VTS_02 segment 147
- Extracting STILLS for VTS_02 segment 148
- Extracting STILLS for VTS_02 segment 149
- Extracting STILLS for VTS_02 segment 150
- Creating M2V for VTS_02 segment 151
- Creating M2V for VTS_02 segment 152
- Creating M2V for VTS_03 segment 0
- Extracting STILLS for VTS_03 segment 1
[20:48:21] Phase II ENCODING completed in 52 minutes.
[20:48:51] Phase III, REBUILD started.
- Copying IFO, BUP, and unaltered files...
- Processing VTS_01
- Rebuilding segment 0 VOBID: 1 CELLID: 1
- Rebuilding segment 1 VOBID: 1 CELLID: 2
- Rebuilding segment 2 VOBID: 1 CELLID: 3
- Rebuilding segment 3 VOBID: 1 CELLID: 4
- Rebuilding segment 4 VOBID: 1 CELLID: 5
- Rebuilding segment 5 VOBID: 1 CELLID: 6
- Rebuilding segment 6 VOBID: 1 CELLID: 7
- Rebuilding segment 7 VOBID: 1 CELLID: 8
- Rebuilding segment 8 VOBID: 1 CELLID: 9
- Rebuilding segment 9 VOBID: 1 CELLID: 10
- Rebuilding segment 10 VOBID: 1 CELLID: 11
- Rebuilding segment 11 VOBID: 1 CELLID: 12
- Rebuilding segment 12 VOBID: 1 CELLID: 13
- Rebuilding segment 13 VOBID: 1 CELLID: 14
- Rebuilding segment 14 VOBID: 1 CELLID: 15
Aborted.

---------------------

Here's the AVS File:

[file]
name=C:\DOWNLOADS\DVD_PROJECT\OPV\D2VAVS\V01001400001015.avs
frame_first=0
frame_last=5312
encode_first=0
encode_last=5312

[Joe_smish]

thats a different error then the one I was getting, mine was in the encode stage.

[TK8472]

Originally posted by pg55555
TK8472
Try without preprocessing to verify the error is not related. Select just 2 passes, so you'll get the answer faster.

Try also OPV, and check if it happens in this mode.

Check your rebuilder.ecl file for the problematic segment (or the corresponding avs file) and look at the size of the segment: is an small segment (less than 60 frames?, one frame?. AS Joe_smish is getting this error in an one frame segment...

I tried a 2-pass on the untouched ISO and the 'Encoder error' resurfaced. So it's not the pre-processing.

'ERROR: File V01001400001015 shows completed, but no .M2V file exists. Aborted.'

[eriksen76]

I have also had this error recently

/Eriksen76

[Joe_smish]

Originally posted by TK8472
I tried a 2-pass on the untouched ISO and the 'Encoder error' resurfaced. So it's not the pre-processing.

'ERROR: File V01001400001015 shows completed, but no .M2V file exists. Aborted.'

You're right. My fault. That is the same error I got.

[eriksen76]

I just did a a movie from sractch!! - NO pre-processing (Latest RB)

"ERROR: The input file V05000100002001.avs is missing frames. Rebuild aborting

[file]
name=C:\\NOTTING HILL\D2VAVS\V05000100002001.avs
frame_first=0
frame_last=3175
encode_first=0
encode_last=3175

Something strange has happend with the latest versons of DVDRB. I never before have had any of the explained errors when using this program. Something has got to be fixed ;)

/Eriksen76

[Joe_smish]

I've never had a sucessful back up with this software yet. Preprocessing or not. I think its time to give up.:(

[pg55555]

eriksen76
From the RB PRO 0.84.1 Changelog:
"Implemented new procedures to prevent unreported overflow errors that are occurring in CCE version 2.70 (both SP and Basic) from causing undersized builds (with frames missing). Tweaked several parameters that make the overflow less likely to happen, and also inplemented a segment frame count verification in the REBUILD phase to flag it should it somehow again happen "
So maybe the error was there but it was not reported before.

The same with the missed m2v file error, the m2v checked was added in the 0.80 version (see my previous post)

Or the new checking routines have problems in itself.

So welcome back to debugging.

My recommendation to you and TK8472 is to go back some versions (0.78?) and try with that version if the same unprocessed source can be backed up without problem. Check specially the reported segment / vob in the backup, can it ve watched in the standalone and no error ocurred?
If successful, you can report to jdobbs it is a new bug reported in the last versions.

[eriksen76]

Thanx for your reply

I get the errors with v0.84

Haven't tried the v0.84.1 version yet, due to server maintenance.

Could you give me the link for version 0.78. Sorry to say that I have deleted it.

Thanx

/Eriksen76

[pg55555]

Joe_smish
Sorry to hear this. I have done more than 200 successful backups with RB, since version 0.46

I would recomend try other DVD before giving-up. Maybe your problem is DVD specific.
If not, it should be your setup.

[pg55555]

eriksen76

Look at Rockas site (www.dvd-rb.com), he has all the old public versions available for download

[eriksen76]

Thanx alot, didn't know I could get the old versions there

I will try with version 0.79 whick seems to be the version before the m2v file check introduced in 0.80

Will let you know how it went

By the way a small question. I have always placed the dgdecode file in the plugin directory of avisynth. Does it make any diffrences to place it in dvdrebulder directory? Just a thought...

By the way I use the right version

/Eriksen76

[lark]

should not make any difference as long as the path is correct (i.e. the loadplugin statement in the AVS files points to the correct dll).

edit: and if its in the avisynth plugin directory, you don't even need the loadplugin statement.

regards
t :)

[SpazzHH]

Originally posted by eriksen76
I have always placed the dgdecode file in the plugin directory of avisynth. Does it make any diffrences to place it in dvdrebulder directory? Just a thought...

By the way I use the right version

/Eriksen76


jdobbs suggests a seperate copy of the DGDecode be kept in the DVD-RB directory to keep some other program from accidently upgrading the .dll to a version that would not be compatable with RB. If the .dll is in the avisynth directory they could easily do that without someone realizing it. Safety precaution with a VERY important file.

[eriksen76]

So what you're saying is only of copy of Dgdecode, which is to be placed in the DVDRB directory.

None in avisynth directory?

By the way right now I'm doing a 2 pass test on the same movie, but this time with Dvdrb 0.79

Will let you know how it went

/Eriksen76

[SpazzHH]

From what I understand by reading other posts on this board, that is his preference. That is why the installer puts it there instead of the Avisynth directory.

[jdobbs]

I'd like to make this perfectly clear. The "missing .M2V file" bug is NOT RELATED TO DVD-RB. It is caused by Version 2.70 of CCE which I believe to be too buggy to use. In every test I performed on it the files were created properly in earlier versions of CCE (both SP and Basic) using the exact same .ECL files. Others have done the same.

I implemented a workaround in DVD-RB Freeware v0.82.1 and Pro v0.84.1 in order to make it work -- but that doesn't mean I am willing to accept the blame for an error that is clearly with Cinemacraft encoder.

If you want your .M2V files to show up use one of these versions of DVD-RB, or better yet, use a stable version of CCE or one of the other encoders (ProCoder/QuEnc/HC) for encoding.

[jdobbs]

Originally posted by eriksen76
I just did a a movie from sractch!! - NO pre-processing (Latest RB)

"ERROR: The input file V05000100002001.avs is missing frames. Rebuild aborting

[file]
name=C:\\NOTTING HILL\D2VAVS\V05000100002001.avs
frame_first=0
frame_last=3175
encode_first=0
encode_last=3175

Something strange has happend with the latest versons of DVDRB. I never before have had any of the explained errors when using this program. Something has got to be fixed ;)

/Eriksen76 That is exactly the problem I have mentioned. Use a stable version of CCE. Go post this on their forum!!!

[eriksen76]

Sorry Jdobbs I have not read this anywhere

Will try with a more stable version.

Thanx for pointing me this out, will let you know how further testing went.

Which CCE is the most stable according to you?

EDITED: Just for the fun of it I tried rebuilding the above mentioned project in "3 click mode" with DVDRB 0.79 and so far it has not given me any errors during rebuild??? It has successfully run through the problematic VTS mentioned above.

/Eriksen76

[jdobbs]

Originally posted by Joe_smish
I've never had a sucessful back up with this software yet. Preprocessing or not. I think its time to give up.:( The reason I've waited so long to respond to this thread is exactly this abrasive attitude...

If you install DVD-RB properly, don't preprocess, don't play with the sources, and let it do its job -- it works.

[pg55555]

DGDecode to be used by RB can be anywhere in your PC as long as the path point to it correctly.

The problem is that DGDecode is also used by other programs, which during installation can overwrite the one in the plugins folder, generating problems in RB working.

So the recomendation is to put the righ DGDecode version in a place to be used exclusivelly by RB, such as the RB folder, and point the Path to it in RB setup. So, you are free to have in the Avisynth plugins folder any other version those other programs require.

[jdobbs]

@eriksen76,

What DVD-RB version are you using? If you continue to have problems, we can work together to fix them. The only variable I can think of that has happened recently is the introduction of CCE v2.70 into the mix and I think that's the source of your headaches. If not, I'll get it fixed. But in the instances where I could repeat the missing M2V problem consistently, it was caused by overflow errors in CCE v2.70. I then simply pointed to an older version of CCE and ran the same job without error.

[jdobbs]

Originally posted by eriksen76
Sorry Jdobbs I have not read this anywhere

Will try with a more stable version.

Thanx for pointing me this out, will let you know how further testing went.

Which CCE is the most stable according to you?

EDITED: Just for the fun of it I tried rebuilding the above mentioned project in "3 click mode" with DVDRB 0.79 and so far it has not given me any errors during rebuild??? It has successfully run through the problematic VTS mentioned above.

/Eriksen76 CCE SP v2.50 or v2.67, CCE Basic v2.69. I'll go back to v0.79 and see if anything has changed that might affect this. Did you try redoing the entire job or just the rebuild? The problem with earlier versions of DVD-RB and CCE 2.70 is that they didn't have the "catch" in -- and an .M2V that was short would just be integrated as-is into the output stream and you might have had a "blank" or "frozen" section that only had sound. That's why I added that framecount check... it's better to not create a VTS than to have one that is in error but it is unknown.

[jdobbs]

Just as an example -- in doing Sex and the City, Season 5, Disc 2 (or was it 1?) -- several thousand frames were missing following the HBO "whitenoise" screen on the last episode.

In earlier versions I made the assumption that if the .M2V was created by CCE it was good. In doing that section the encoder bombed at the beginning of the segment during the first M2V pass, only created a few frames, and didn't display any error messages or pass them back in the process termination code.

It worked fine with any other version of CCE.

[eriksen76]

Originally posted by jdobbs
CCE SP v2.50 or v2.67, CCE Basic v2.69. I'll go back to v0.79 and see if anything has changed that might affect this. Did you try redoing the entire job or just the rebuild? The problem with earlier versions of DVD-RB and CCE 2.70 is that they didn't have the "catch" in -- and an .M2V that was short would just be integrated as-is into the output stream and you might have had a "blank" or "frozen" section that only had sound. That's why I added that framecount check... it's better to not create a VTS than to have one that is in error but it is unknown.

As VIP member I always use the latest version (0.84.1)

Right now I'm doing a full encode with DVDRB 0.84.1 & CCE 2.67 to see if that has solved the problem with the missing frames.

I was just a bit confused because when I suddenly had 2 movies in a row with 2 different errors. Never happend before.

First error was Notting Hill with the missing frames during rebuild (No errors during encode).

The other one is Seven Years In Tibet which I'm also doing some testing on now with the new setup. In order not to confuse too much I will await futher explanations about this problem until this test is done. But this one has problems during encode. It might be due to v2.70.02.00 so I wait a bit with details

B back

/Eriksen76

[jdobbs]

I really want to put an end to this missing .M2V and missing frames thing. If DVD-RB somehow contributes to it or causes it -- I need to know that. Otherwise I need to find a way to somehow prevent CCE from bombing during the encode...

If someone has a DVD that consistently has a missing .M2V -- could you try it with an earlier version of CCE and see if it repeats? Please report it here in this thread -- as this is my highest priority right now.

DVD-RB really shines when it uses CCE, and I want to make it work -- buggy version or not.

[TK8472]

Originally posted by jdobbs
I'd like to make this perfectly clear. The "missing .M2V file" bug is NOT RELATED TO DVD-RB. It is caused by Version 2.70 of CCE which I believe to be too buggy to use. In every test I performed on it the files were created properly in earlier versions of CCE (both SP and Basic) using the exact same .ECL files. Others have done the same.

I implemented a workaround in DVD-RB Freeware v0.82.1 and Pro v0.84.1 in order to make it work -- but that doesn't mean I am willing to accept the blame for an error that is clearly with Cinemacraft encoder.

If you want your .M2V files to show up use one of these versions of DVD-RB, or better yet, use a stable version of CCE or one of the other encoders (ProCoder/QuEnc/HC) for encoding.

In case it was overlooked in my posts, all my .M2V errors have been with CCE SP v2.67.00.27. I've never installed 2.70.

[jdobbs]

I'm making my assumption based upon my own experience.

Give me more details. The problem is that the check for missing .M2V files didn't go in until version .79 and .80. If they were missing before then you would have gotten some other cryptic error message during rebuild.

[jdobbs]

Does anyone think custom matrices might somehow have an influence on this? That's the only thing I can think of that was added recently that might change CCE processing...

[jdobbs]

Originally posted by eriksen76
As VIP member I always use the latest version (0.84.1)

Right now I'm doing a full encode with DVDRB 0.84.1 & CCE 2.67 to see if that has solved the problem with the missing frames.

I was just a bit confused because when I suddenly had 2 movies in a row with 2 different errors. Never happend before.

First error was Notting Hill with the missing frames during rebuild (No errors during encode).

The other one is Seven Years In Tibet which I'm also doing some testing on now with the new setup. In order not to confuse too much I will await futher explanations about this problem until this test is done. But this one has problems during encode. It might be due to v2.70.02.00 so I wait a bit with details

B back

/Eriksen76 Thanks. I'm eager to here your results.

[Fishman0919]

Does anyone think custom matrices might somehow have an influence on this? That's the only thing I can think of that was added recently that might change CCE processing

and turning off CCE's adaptive quantizer matrices feature by default

CCE 2.70 might be abit more pick with that turned off...then again adaptive quantizer matrices haves been in CCE 2.67 and up and is on by default

[eriksen76]

Originally posted by jdobbs
Thanks. I'm eager to here your results.

So far no problems with Seven Years In Tibet. Actually it has gone through the encode of the problematic .m2v file.

Seems to be working :) . Final Conclusion to come later though

/Eriksen76

[jdobbs]

Originally posted by Fishman0919
and turning off CCE's adaptive quantizer matrices feature by default

CCE 2.70 might be abit more pick with that turned off...then again adaptive quantizer matrices haves been in CCE 2.67 and up and is on by default That's true too. I wish I could repeat this problem in some way other than on one single disc. That way I could be sure I'm not chasing the wrong error.

[jdobbs]

Originally posted by eriksen76
So far no problems with Seven Years In Tibet. Actually it has gone through the encode of the problematic .m2v file.

Seems to be working :) . Final Conclusion to come later though

/Eriksen76 Well, that confirms my suspicions of v2.70 so far. I'll wait for the final result.

[jdobbs]

@TK8472,

Do you use custom matrices? Also, was the offending segment using a custom matrix?

[jdobbs]

@eriksen76

Can you tell me what the vbr_brate_avg, vbr_brate_min, and vbr_brate_max are on the offending segment?

[TK8472]

Originally posted by jdobbs
@TK8472,

Do you use custom matrices? Also, was the offending segment using a custom matrix?

No on both.

[Joe_smish]

Originally posted by jdobbs
The reason I've waited so long to respond to this thread is exactly this abrasive attitude...

If you install DVD-RB properly, don't preprocess, don't play with the sources, and let it do its job -- it works.

I'm pretty sure I did install it properly, and I didnt do any preprocessing....didnt work.:(
I'm sorry for an abrasive attitude, that wasnt my intentions. I was actually trying to have an optimistic outlook on this program. I've heard such great things about it and I really want to get it to work with me. Thats why I've been trying so hard to get it to work. But I'm not sure why it isnt working, b/c I installed it properly, I use the trial version of CCE 2.67, I rip the DVD and dont do anything to it. and I got the error of an .m2v missing. I'm not sure what I am doing wrong. I'm sure its me not the program. I really wish someone who used this went to Uconn and could give me a run through. That would be very helpful.

[Joe_smish]

Originally posted by jdobbs
I'd like to make this perfectly clear. The "missing .M2V file" bug is NOT RELATED TO DVD-RB. It is caused by Version 2.70 of CCE which I believe to be too buggy to use. In every test I performed on it the files were created properly in earlier versions of CCE (both SP and Basic) using the exact same .ECL files. Others have done the same.

I implemented a workaround in DVD-RB Freeware v0.82.1 and Pro v0.84.1 in order to make it work -- but that doesn't mean I am willing to accept the blame for an error that is clearly with Cinemacraft encoder.

If you want your .M2V files to show up use one of these versions of DVD-RB, or better yet, use a stable version of CCE or one of the other encoders (ProCoder/QuEnc/HC) for encoding.

I'm sorry but I wasnt blaming DVD-RB, I was just looking for a solution to the problem. I dont know anything about RB so I figured I'd ask and see IF it was a problem with RB, I wasnt blaming it. I dont know anything about CCE either, so for all I konw it could be a problem with that. I have no idea. Whats this matrices stuff people are talking about??

[jdobbs]

I just want this error to stop. If I can manipulate the input to CCE somehow (as I did in the last two versions for the error I'd received) I can get around it...

[jdobbs]

Originally posted by TK8472
No on both. Could you post your REBUILDER.INI file?

[Joe_smish]

Do you think if I had the pro version this would help with my problem? Or do you think it is a source problem, or a setup problem? I dont even know where to start trouble shooting, I feel like I've tried every thing.

[eriksen76]

Originally posted by jdobbs
@eriksen76

Can you tell me what the vbr_brate_avg, vbr_brate_min, and vbr_brate_max are on the offending segment?

Encoding not done yet. Will have a look at it when done.

It might be tomorrow, as its kinda late here in Europe

/Eriksen76

[jdobbs]

I just did some more testing on CCE V2.70. It is EXTREMELY sensitive to high demand scenes -- and using the HBO "whitenoise" intro screen as my baseline I've found that it is crashing with a buffer overflow any time the VBR maximum bitrate gets below about 8500Kbs -- which is a very high point to be crashing... for comparison, on CCE SP V2.67 you can get pretty far down into the low 7000s (on the same scene) before it has any problems.

As I pointed out in another post somewhere here, what the encoder should do when it runs out of headroom is adjust the quantizer scale to get under its maximum. It doesn't look like V2.70 is doing that (or at least not well).

Also, when V2.70 is called as a shell process or from the command line with the -batch switch on -- it doesn't display or make any indication of an error. V2.67 will kick up an error screen when it hits a problem.

[Joe_smish]

Do you have any suggestions that I can try in an attempt to solve the problem?

[jdobbs]

How many different DVDs have you tried? It's always best to do your first encode with an easy one just to make sure your configuration is right. After it's properly set up it will pretty much run on its own from then on.

[jdobbs]

Originally posted by eriksen76
Encoding not done yet. Will have a look at it when done.

It might be tomorrow, as its kinda late here in Europe

/Eriksen76 You can open the .ECL file while it is running... and look at the values. :D Sorry. You probably want to go to bed.

[eriksen76]

Well, "Seven Years In Tibet" is completed now with absolutely no problems at all.

The error with CCE 2.70 and this movie was:

"ERROR: File VXXXXXXX shows completed, but no .M2V file exists. Aborted."

That happend about 40% during the encode before when using CCE 2.7

Now I managed to get it working with latest DVDRB 0.84.1 PRO and CCE 2.67 (Trial)

So I guess the conclusion to the above mentioned error is that it's also related to CCE 2.7

Still, I will report how things went with the "missing m2v file" issue. But I think it will work. (Still encoding..)

Still I find ot very strange that when doing the rebuild of the movie with 0.79 it managed to make it work.

So something must have been changed from 0.79 - 0.84.1 PRO that makes a difference.

To sum up. I did a "one click" on this movie with CCE 2.70 and DVDRB 0.84.1 pro. In the very beginning of the rebuild it gave me the error that m2v file was missing.

But when doing the rebuild only, with the older version of DVDRB then it worked for me.

/Eriksen76

[jdobbs]

That's because all you did was the rebuild. The missing or shortened file was just ignored... v0.79 trusted CCE a lot more than v0.84 does (that's why I added the changes I did). You would be very disappointed when you played it back and had a segment that was audio-only.

I'm liking HC and QuEnc more-and-more. They both can kick through the troublesome disc I'm testing without a hitch.

[eriksen76]

Ok, thanx for the explanation - Glad there was one :)

/Eriksen76

[jptheripper]

Im curious jdobbs, and have thought this awhile

either you can make the program hcenc only (i think i might get stoned forthat comment)

or is there the option to , if the m2v fails the errorcheck twice, to encode that single segment with hcenc or quenc? its better than failing to me. I realize the prepare stages are different, i wonder how long it would take to prepare 2x the avs's/ecls

-jp

[archaeo]

either you can make the program hcenc only (i think i might get stoned forthat comment)

no, no stoning necessary but..

I like HC a lot, but until the encode speed picks up (ie multithread) I just have to go with CCE for times sake.

[jdobbs]

Well... I'm currently testing a beta of HC that HANK315 sent me on my video computer right now -- and from what I've seen so far I may be moving into your mindset as far as recommendations go. It is faster. As for multithreading... I can make DVD-RB run more than one segment at a time, you know!!!

QuEnc is getting better too.

But why would someone want to pay for a commercial encoder that needs a freeware one to rescue it when it crashes? At least from my point of view the problem is with Cinema Craft and they need to fix it.

[archaeo]

and from what I've seen so far I may be moving into your mindset as far as recommendations go. It is faster. As for multithreading... I can make DVD-RB run more than one segment at a time, you know!!!

Hey that would be great on both counts...:D
So you can optimize RB even more for us dualies?
When could this occur??

[jdobbs]

We're getting pretty OT (I'm probably more guilty than anyone). I'll let you know when I look at it a little.

[archaeo]

sounds good ;)

[JohnG]

Originally posted by jdobbs
That's because all you did was the rebuild. The missing or shortened file was just ignored... v0.79 trusted CCE a lot more than v0.84 does (that's why I added the changes I did). You would be very disappointed when you played it back and had a segment that was audio-only.

So to clarify, if I do decide to use CCE 2.7 and the process completes, I am not in danger of finding out later during playback that there are missing frames? To echo your opinion, I would much rather have the process fail than find out as I am viewing the film.
Do you suggest that I (we) just stick with 2.5sp or HC/QuEnc until Cinema Craft decides to fix this problem?

[jptheripper]

Originally posted by jdobbs
Well... I'm currently testing a beta of HC that HANK315 sent me on my video computer right now -- and from what I've seen so far I may be moving into your mindset as far as recommendations go. It is faster. As for multithreading... I can make DVD-RB run more than one segment at a time, you know!!!

QuEnc is getting better too.

But why would someone want to pay for a commercial encoder that needs a freeware one to rescue it when it crashes? At least from my point of view the problem is with Cinema Craft and they need to fix it.


Is hc really that good? i may have to check it out, i have a super bad source dvd with low bitrate ~1800 after encoding that is driving me nuts

[TK8472]

Originally posted by jdobbs
Could you post your REBUILDER.INI file?

I'm at work, but will post it as soon as I get home.

[jdobbs]

HC is an incredible encoder. It may even be better than CCE at low bitrates. It's weakness has been its speed. I'll see how long it takes to encode a DVD with this new version... But it's probably more appropriate to let Hank315 talk about its new capabilities when he releases it.

[Fishman0919]

HC is really that good... it free and about if not the same quality as cce...the new betatest ver is much faster then the old one... it's on par with QuEnc and a tad bit slower then cce for speed for me (quenc about 2.7x, hc .13bt about 2.5x, cce sp 2.70 3.5-4x)

[jdobbs]

HC can be a little difficult to calculate because its second pass is about 1.7x faster than it's first pass so you have to average the two passes... while CCE takes the same amount of time for each of its passes. On my computer (an AMD 3200+) QuEnc is pretty close to CCE in terms of speed.

[eriksen76]

Originally posted by jdobbs
You can open the .ECL file while it is running... and look at the values. :D Sorry. You probably want to go to bed.

Still not done encoding, so I can't tell you how it went, but it looks promising.

This the data when using DVDRB 0.84.1 and CCE 2.7 (Trial)
--------------------------------------------------------------------
"ERROR: The input file V05000100002001.avs is missing frames. Rebuild aborting

(It happend during the rebuild phase)

[file]
name=C:\\NOTTING HILL\D2VAVS\V05000100002001.avs
frame_first=0
frame_last=3175
encode_first=0
encode_last=3175

Here is the log when using DVDRB 0.84.1 and CCE 2.67 (Trial)

[item]
title=V05000100002001
aud_out=0
vaf_file=C:\NOTTING HILL\D2VAVS\V05000100002001.vaf
aud_file=C:\\NOTTING HILL\D2VAVS\V05000100002001.mpa
file_focused=0
packet_size=2048
width=720
height=576
frame_rate_idx=3
cbr_brate=6000
vbr_brate_avg=5382
vbr_brate_min=500
vbr_brate_max=9000
seq_endcode=0
dvd=0
half_width=0
half_height=0
lum_level=0
adjust_q_matrix=0
aspect_ratio=2
gop_m=3
gop_nm=4
gop_hdr=12
seq_hdr=1
all_closed_gop=0
fix_gop_length=0
samples_per_sec=44100
stereo=2
brate_idx=7
crc=1
progressive=0
alternate_scan=1
intra_dc_prec=2
intra_dc_precision_9_max=113
intra_dc_precision_10_max=113
aud_mode=0
tc_ref_frm=0
drop_frame=0
fix_vbv_delay=0
letter_box=0
pulldown_detect=0
offset_line=0
create_new_vaf=1
credits_tweak=0
credits_start=0x00000
credits_brate=1000
h_filter=0
h_filter_idx=8
dither=0

/Eriksen76

[Joe_smish]

http://forum.doom9.org/showthread.php?s=&threadid=91282&perpage=20&highlight=settings%20for%20different%20encoder&pagenumber=1

I would like to try this encoder and see if I can make a successful back up with this since I'm having so much trouble with CCE. I tried downloading the file that you talk about in that post. After doing that I renamed it and put it In the DVD-RB directory right next to the DVD-RB application. I still cant find it in the setup anywhere though. How do I use this program with DVD-RB? I'm sorry to be such a pain. Im no good at this sort of thing and I always feel bad when I ask such stupid questions.

[jdobbs]

Hmmm... that is a very high average and max bitrate for CCE to be choking...

[jdobbs]

Originally posted by Joe_smish
http://forum.doom9.org/showthread.php?s=&threadid=91282&perpage=20&highlight=settings%20for%20different%20encoder&pagenumber=1

I would like to try this encoder and see if I can make a successful back up with this since I'm having so much trouble with CCE. I tried downloading the file that you talk about in that post. After doing that I renamed it and put it In the DVD-RB directory right next to the DVD-RB application. I still cant find it in the setup anywhere though. How do I use this program with DVD-RB? I'm sorry to be such a pain. Im no good at this sort of thing and I always feel bad when I ask such stupid questions. If you're using the Freeware version you have to use the QuEnc path. HC will accept the QuEnc command line options.

[Joe_smish]

Originally posted by jdobbs
If you're using the Freeware version you have to use the QuEnc path. HC will accept the QuEnc command line options.
In the setup do I switch the QuEnc path to whereever the hc.exe file is and then in mode I choose QuEnc. Is this correct? Any other settings I will have to change or is this all?

[jdobbs]

Yes. But make sure you use the "HCBatch..." file -- it is the only one that will take the command line arguments.

You can also create an HC.INI file in the HC (DVD-RB) directory that can set some of the other default values, but it should work without it too.

Do a search of Doom9 -- there are instructions somewhere...

[Joe_smish]

is it allowed to rename the HCBATCH file??
I named it HC.exe like it said in the post. As long as I click the right one that shouldnt matter correct?

[pg55555]

Joe_smish
jdobbs gave a very good advice. Try CCE with other sources. Likely the problem you experienced will not repeat with them.

Get first a working backup, to be sure your setup is OK before start trying more exotic ones

[TK8472]

Originally posted by jdobbs
Could you post your REBUILDER.INI file?

Here you go...

[Options]
CCE=1
RemoveDTS=0
idct7Opt=1
Completed=5
Skin=Windows Standard
AdditionalOutput=0
Backcolor=13484047
Mode=1
HalfD1=0000
Convert_16_9=0000
DisableInterlace=0000
HC_Quality=1
HC_Matrix=1
SkinVersion=5
[CCEOptions]
VBR_bias=25
Quality_prec=16
eclPasses=2
OPV=0
[Paths]
CCENEW=C:\Program Files\Cinema Craft Encoder SP v2.67.00.27\cctsp.exe
MPEG2DEC=C:\Program Files\DVD-RB\dgdecode.dll
DECOMB=C:\Program Files\AviSynth 2.5\plugins\Decomb511.dll
Source=F:\VIDEO_TS\
Working=C:\DOWNLOADS\DVD_PROJECT\2-PASS\
Output=C:\DOWNLOADS\DVD_PROJECT\2-PASS\
[Audio]
Selected=11111

[jdobbs]

Originally posted by Joe_smish
is it allowed to rename the HCBATCH file??
I named it HC.exe like it said in the post. As long as I click the right one that shouldnt matter correct? You can name it whatever you want as long as it ends in .exe and it is pointed to in the path.

[Joe_smish]

I backed up the troublesome movie with no problem at all with the HC endoder. Whats the best method of comparison so I can compare this to the back up I did with Shrink?? That was the whole purpose of this exercise.

[Joe_smish]

I just burned the DVD-RB copy and didnt get a chance to watch the entire movie yet, however, so far everything seems fine. I actually backed up the preprocessed movie. It was no problem at all with HC. I think it may have been somewhere with CCE, but just to let you guys know it wasnt the v2.70 that everyone is saying has bugs, I was having trouble with the Trial version 2.67. I'm not sure what the problem may have been. But I know that as far as I can tell it worked just fine with HC.

[eriksen76]

Originally posted by jdobbs
Hmmm... that is a very high average and max bitrate for CCE to be choking...

I'm sorry to report that this movie failed once again with the new setup!!

The same missing .m2v file error at the same place of the rebuilding stage.

Damn it (sorry)

/Eriksen76

[jdobbs]

Is the M2V missing, or did it fail in the rebuild due to missing frames? Look at my comment in this thread. (http://forum.doom9.org/showthread.php?threadid=92985&goto=newpost)

[eriksen76]

Originally posted by jdobbs
Is the M2V missing, or did it fail in the rebuild due to missing frames? Look at my comment in this thread. (http://forum.doom9.org/showthread.php?threadid=92985&goto=newpost)

It was the .m2v file missing in the rebuild stage

Will your modification solve this problem as well, and with CCE 2.70?

I am trying to encode the movie with HcBatch012 now

/Eriksen76

[jdobbs]

I'm confused. There is no "M2V file missing" error notification in the rebuild stage. There is only a "missing frames" error in the rebuild stage. If the M2V were missing it would flag it in the ENCODE stage.

[jdobbs]

Just an update to all. As I've explained, I think the CCE crashes are due to the way CCE (especially the newer versions) is handling the maximum bitrates. In order to attempt to circumvent that problem, I have added code to DVD-RB that will, after two failures to create an M2V file, increase the VBR maximum bitrate to that of the highest that is compliant with DVD. This is something you only want to do as a last resort, as it ignores the portion of the bitrate used by audio and subpicture streams -- the player's frame buffer should be able to hold the short offending burst that causes this. In the meantime I hope CCE works on their engine.

The new code will be in freeware v0.83 and Pro version 0.85.

[eriksen76]

Originally posted by jdobbs
I'm confused. There is no "M2V file missing" error notification in the rebuild stage. There is only a "missing frames" error in the rebuild stage. If the M2V were missing it would flag it in the ENCODE stage.

Sorry, typing error

Offcourse it was the "missing frames" error

Looking forward to the updated DVDRB version - When can we expect it?

I'm eager to try it

/Eriksen76

[eriksen76]

The missing frames issue was solved when encoding with "HC"

Movie works like a charm now

/Eriksen76

[Whitespliff]

Originally posted by jdobbs
Is the M2V missing, or did it fail in the rebuild due to missing frames? Look at my comment in this thread. (http://forum.doom9.org/showthread.php?threadid=92985&goto=newpost) I think had both problems:
1. First RB said (during rebuild phase) that a .m2v file was missing, this was correct... I encoded it manually with CCE.
2. Second time I tried I got the missing frame error.
I'm using RB 0.84.1 & CCE 2.66.01.07 (trial)

I tried a third time with RB 0.81, no problems.

PS: it wasn't a 1 or 2 frame cell, cell was about 90MB after encoding

[pg55555]

Whitespliff

I think you didnt got it right: the "1 or 2 frames" referenced in the other thread is not related to the lenght of the segment, is that sometimes the "last 1 or 2 frames" are not encoded, and so are missing from the ouput.

As the newest versions include a framecount routine, checking the encoded frames vs the source, you get the error.

With RB 0.81 you do not get the problem because the framecount routine is not there: So the missing frames problem could be there but RB does not know.

If they are just 1 or 2 frames, as jdobbs says, it is not an issue, in the next release of RB he is changing the framecount routine to ignore such small missing number of missing frames.

But the error routine will try to catch larger number of misssing frames that a bug in CCE 2.70 (not RB) generates, and that when the playing the backup shows as a segment with audio but no video.

As you are using CCE 2.66, likely your case falls in the first group

[jdobbs]

Exactly.

[Joe_smish]

Originally posted by pg55555
As you are using CCE 2.66, likely your case falls in the first group

Does this mean that it should work for me with CCE next version of RB?? Barring I do everything correctly, which I probably wont;)

[jdobbs]

Let's hope so.

[Whitespliff]

Oeps, you're right, I didn't got that :rolleyes:
Tnx for the info & jdobbs, tnx (again) for this great proggie :D