View Full Version : Missing .m2v when encoding
Joe_smish
12th April 2005, 05:37
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
12th April 2005, 12:57
First:
Have you tried one DVD without any kind of preprocess?
Second:
How did you installed? Have you tried to use my Installer?
JohnG
12th April 2005, 14:08
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
12th April 2005, 14:57
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
12th April 2005, 15:18
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
12th April 2005, 15:25
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
12th April 2005, 15:48
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
12th April 2005, 16:23
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
12th April 2005, 17:12
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
12th April 2005, 17:19
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
12th April 2005, 19:17
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
12th April 2005, 22:24
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
12th April 2005, 23:08
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
12th April 2005, 23:18
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
12th April 2005, 23:57
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
13th April 2005, 00:05
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
13th April 2005, 01:22
Look at the Sticky post "Settings" at the top of the Forum, look for Hidden Settings
Joe_smish
13th April 2005, 02:52
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
13th April 2005, 07:53
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
13th April 2005, 13:47
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
13th April 2005, 13:57
do blanking after rebuilding
t :)
Joe_smish
13th April 2005, 14:01
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
13th April 2005, 14:08
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
13th April 2005, 16:45
#------------------
# 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
13th April 2005, 17:14
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
13th April 2005, 17:24
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
13th April 2005, 18:35
after you preprocessed, you re-prepared from scratch right? not just reencoded? if you change anything you have to start over
lark
13th April 2005, 18:36
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
13th April 2005, 19:14
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
13th April 2005, 19:24
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
13th April 2005, 19:51
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
13th April 2005, 20:01
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
13th April 2005, 20:03
Originally posted by lark
perhaps you need jdobbs' help again.
He hasnt visited this post yet with his input :(
JohnG
13th April 2005, 20:24
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
13th April 2005, 21:07
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
13th April 2005, 21:50
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
13th April 2005, 22:11
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
14th April 2005, 00:11
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
14th April 2005, 00:31
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
14th April 2005, 00:50
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
14th April 2005, 02:13
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
14th April 2005, 03:28
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
14th April 2005, 03:37
thats a different error then the one I was getting, mine was in the encode stage.
TK8472
14th April 2005, 05:00
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
14th April 2005, 05:33
I have also had this error recently
/Eriksen76
Joe_smish
14th April 2005, 05:37
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
14th April 2005, 05:57
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
14th April 2005, 07:46
I've never had a sucessful back up with this software yet. Preprocessing or not. I think its time to give up.:(
pg55555
14th April 2005, 15:04
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
14th April 2005, 15:16
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
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.