Possible dropped frames

[blutach]

An encode turned out with a size of 4.18Gb so I thought something might be wrong.

The log shows possible dropped frames. And this is confirmed by an 8 min segment having just 27Mb of m2v.

Why might have this occurred?

Enclosed are the log, ECL and ini files. Note: Even tho' I deselected the 18th subtitle (2nd English Stream), it still shows as a 1 - wonder why?

Is there any way to just re-encode the offending VCID? Is it as simple as adding Encode_Progress=15 (this is the segment which crapped out) to a newly prepared INF file in a separate folder and, when finished, abort and copy the resultant m2v to the original D2VAVS folder and then do a rebuild?

Or perhaps is it safer to edit the existing INF file?

Regards

[Rippraff]

Hi blutach,

I'm wondering why people attach their files instead of posting it with the CODE function. ;)
In your case I can't see which encoder was used.
If it's CCE open Rebuilder.ecl copy the header in a new text file and the parts which contain your corresponding title part (example title=V03000000001001).
Keep both [item] and [file].
Save it under Reencode.ecl.
Feed it directly to CCE with file => open => project function.
Run Rebuild phase again afterwards.
Done. :)

Edit: If it's HC take a look at this thread (http://forum.doom9.org/showthread.php?t=103265) but there might be easier ways... ;)

Cu Rippraff

[blutach]

My apologies rippraff - I guess I like economy in the thread.

Anyways, thanks for the answer.

Procoder 2, mastering.

I did what I thought in post 1 and it seemed to work.

But it got me thinking of a feature suggestion. When these things happen, it would be great to encode a segment through the DVDRB GUI. But maybe that's what RME is for?

Regards

[Rippraff]

My apologies rippraff - I guess I like economy in the thread.
To each his own economy. :D
I like to have all informations at one place, have it immediately (thinking of even moderators have a real life ;)) and with CODE clarity is also given.
But hey this is my personal thing so no apologieses needed. :)

But it got me thinking of a feature suggestion. When these things happen, it would be great to encode a segment through the DVDRB GUI.
I've asked for this a few times in the past. There's already a check implemented if the analyze file (talking about CCE) exists. I would love to see a frame count comparison during encode instead of rebuild phase before RB moves on to the next segment. If it fails reencode the segment, maybe three times in a row like with .vaf. If it fails again stop encoding as there must be something wrong with the system or source.

Could be useful specially in cases like yours where the encoder swallowed and you can't see any reason. Thanks for the files :)

Cu Rippraff

[blutach]

I'd agree on its usefulness. Another thing would be some sort of error message telling me things weren't well with the rebuild. Had I not looked in the log, I would have not known of the encoder error and might have merrily burned. I wonder if some error reporting is warranted here outside the normal log?

Regards

[lastangel]

i have the same problem.

the solution?