Missing m2v files FIXED with new CCE...NOT!

[DD51]

CCE SP Version 2.70.02.01 Thursday, May 12, 2005

Bug Fixes
- Fixed the problem of 2.70.02.00 in which batch encoding was
not functioned.
- The previous version of 2.70 did not work on Athlon processor
that does not support 3DNow! Professional.


For me it totally fixed m2v missing error!
I overclock my PC and I backed up a dvd (Australian Pink floyd Show) which I could NOT backup without getting the error.
I just did a backup without a single error...wooooohooooo!
I can't beleive how much time jdobbs spent on the previous 2.70 versions:mad:
jdobbs, hats of to you. You're an incredible man for trying so much and so hard to get CCE SP 2.70 to work. I really beleive this version is fixed! I could never get the previous versions to work without a failure.

I hope this fixes the missing .m2v files for everyone else. Please let jdobbs know if this fixes it for you.


UPDATE - UPDATE - UPDATE
I just did 2 more movies
Blade Trinity Extended
Assault on precinct 13
Both have droped frames :( :mad: :angry:
I guess this new version fixed NOTHING:sly:
Back to 2.67 for me :(

Regards,

[Fishman0919]

There was a few fixes that were not mention, one was the bug with high bitrate demand scenes... causing CCE to crach on the infamous HBO Logo.

[Fishman0919]

Both of those movies I have done with the new CCE Basic 2.70.01.04..with no problem....maybe I'm one of the lucky one and never had any problem with cce sp 2.70 or cce basic 2.70.... including the HBO Logo.:confused:

[DD51]

Originally posted by Fishman0919
Both of those movies I have done with the new CCE Basic 2.70.01.04..with no problem....maybe I'm one of the lucky one and never had any problem with cce sp 2.70 or cce basic 2.70.... including the HBO Logo.:confused:

Do you overclock your PC? Just curious that's all.
FYI
If I DO NOT OC my PC...It runs fine.

[RaistlinMajere]

Its CCe 2.70, nothing to do with your system overclocked or not. It happened on both my systems which are not overclocked in anyway and are perfectly stable.

A better way of finding out what causes it is to list hardware to see if theres a common link.

Happened to me on 2 systems

athlon xp's
win 2000 pro sp4
a nvidia mb and a via mb

I think these are the only componants that should possibly effect the program, there might be a common link. I'll stick with 2.67 thanks

if it aint broke don't fix it

[Carpo]

i have only ever had this issue once with cce 2.70 - you would think that they would be ontop of this now - i mean if you were a comp and paid $2000 wouldnt you be a bit miffed

mind u if you paid for the basic version wouldnt you be a bif miffed also and email support demanding they puled their finger out ?

[jdobbs]

How many frames were dropped?

[jdobbs]

I've never experienced a single lost frame nor have I ever seen a missing .M2V, I've been using v2.70 almost exclusively for quite a while now (mainly because I want to try and catch errors). But if it helps I'll provide my system specs:

Athlon XP3200+ processor
512MB PC3200 memory
ASUS A7N8X-E MB
nVIdea nForce2 video
Windows 2000
250GB, 7200rpm 8MB cache Maxtor HD


I also sometimes run on this config -- still never had the error:

Athlon XP2400+ processor
512MB PC2700 memory
ASUS A7S8X-MX MB
SiS 741 Video
Windows XP Professional (SP2)
80GB, 7200rpm 8MB cache Western Digital HD

[Carpo]

it was on (ye you guessed it) final fantasy ;) - but as i say that is the only film that has ever given me issues all the other films i have done with it have been fine

my config

P4 3.4Ghz CPU
2GB DDR 4400 RAM
ASUS P4C800-E Deluexe MB
GeForce 6800 ultra
WinXP SP2 PRO
2 x 200GB 7200rpm 8MB cache SATA Western Digital

[Fishman0919]

Originally posted by DD51
Do you overclock your PC? Just curious that's all.
FYI
If I DO NOT OC my PC...It runs fine.

Yes, I have two AMD 64 3800+ OC'ed to about a 4000+ and on both CCE SP 2.70.02 and CCE Basic 2.70.01.04 work fine.

[Fishman0919]

Originally posted by RaistlinMajere
Its CCe 2.70, nothing to do with your system overclocked or not. It happened on both my systems which are not overclocked in anyway and are perfectly stable.

I emailed Cinema Craft about the problem with CCE basic 2.70 and CCE SP 2.70.02 trial and they told me it was a known issue and a solution was being worked on. A friend was having the HBO Logo problem with CCE Basic 2.70.01.02 and with 2.70.01.04 it went away... he tried CCE SP 2.70.02.01 and it worked fine also.

It seems to be a hit or miss problem..I have never had a problem with either, my brother also no problems... my best friend nothing but problems... all three of us doing the same movie. But all three of us have no problems with the new CCE Basic 2.70.01.04.... then again everyone else could have nothing but problems.

[DD51]

Originally posted by jdobbs
How many frames were dropped?

jdobbs,
I had erased the result so I reran it yesterday.
This is MOVIE ONLY MODE.
This time it only put 1 line of droped frames vs. 2 originally.
I personally wouldn't bother...I'm sure you're busy with other more
important projects.
I can't beleive that a $2,000 program is buggy like that :confused:


[01:11:18] One Click encoding activated...
-----------------
[01:11:18] Phase I, PREPARATION started.
- CCE SP 2.70.2.1 encoder selected.
- "Movie Only" mode is enabled.
- VTS_01: 2,575,278 sectors.
-- Scanning and writing .D2V file
-- Processed 156,711 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 85.8%
- Overall Bitrate : 5,107Kbs
- Space for Video : 4,074,614KB
- HIGH/LOW/TYPICAL Bitrates: 5,643/500/5,107 Kbs
[01:13:23] Phase I, PREPARATION completed in 2 minutes.
[01:13:23] 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
- Extracting STILLS for VTS_01 segment 21
[02:12:42] Phase II ENCODING completed in 59 minutes.
[02:12:42] Phase III, REBUILD started.
- Processing VTS_01
- Reading/processing TMAP table...
- 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
- Possible dropped frame(s) [ 5438 ] noted in this segment, continuing...
- 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
- Rebuilding segment 15 VOBID: 1 CELLID: 16
- Rebuilding segment 16 VOBID: 1 CELLID: 17
- Rebuilding segment 17 VOBID: 1 CELLID: 18
- Rebuilding segment 18 VOBID: 1 CELLID: 19
- Rebuilding segment 19 VOBID: 1 CELLID: 20
- Rebuilding segment 20 VOBID: 1 CELLID: 21
- Updating NAVPACKS for VOBID_01
- Rebuilding segment 21 VOBID: 2 CELLID: 1
- Updating NAVPACKS for VOBID_02
- WARNING: VOB Count Old: 0 New: 2
- Updated VTS_C_ADT.
- Updated VTS_VOBU_ADMAP.
- Updated IFO: VTS_01_0.IFO
Correcting VTS Sectors...
[02:26:13] Phase III, REBUILD completed in 14 minutes.

Done.
[02:26:13] PREPARE/ENCODE/REBUILD completed in 75 min.

My PC specs:
OS: WindowsXP Pro SP2
CPU: P4 3.0C OC'd to 3.554GHZ
Mother Board: ASUS P4C800-E Deluxe
Memory: Geil Ultra-X PC4400 550MHz CL 2.5-4-4-7 DDR (2x512)
Video Card: Nvidia GeForce 6800GT
Sound Card: Audigy 2 ZS
DVD-RW: NEC 3520a
DVD-ROM: Lite-on JLMS XJ-HD166S
Hard Disk: C: Sata 36Gig WD 10RPM
Hard Disk: D: Sata 120Gig
Hard Disk: E: Sata 120Gig
Power Supply: Antec True Power 550

Regards,

[DD51]

Originally posted by Fishman0919
Yes, I have two AMD 64 3800+ OC'ed to about a 4000+ and on both CCE SP 2.70.02 and CCE Basic 2.70.01.04 work fine.

Thanks for letting me know. I'm glad it works for you.
You're lucky!
Maybe one-day CCE will eventually fix this "BUG"!:angry:

Regards,

[jdobbs]

@DD51

Hmmm... I'd say losing 5438 frames is not a good thing. It looks like CCE died early in that segment. Interesting, though, is the fact that it had to have gotten through the entire first pass, or it would have died with the "missing M2V" message in PREPARE.

[DD51]

Originally posted by jdobbs
@DD51

It looks like CCE died early in that segment. Interesting, though, is the fact that it had to have gotten through the entire first pass

If this helps.
It most often dies early. The problem is I usually stop the encoding when that happens cause I know it will fail. In other words it's rare I let it continue through the whole process...again cause I know it will fail:(

If you want me to do more tests I'll be glad too.
I'm probably a good canditate cause it always fails for me:confused:

Regards,

[Jeffster]

Originally posted by Fishman0919
....maybe I'm one of the lucky one and never had any problem with cce sp 2.70 or cce basic 2.70.... including the HBO Logo.:confused:

Nope, your not the only one... I've never experienced any problems with 2.70 Basic either.

I made an effort to got hold of the infamous SATC disc with the HBO screen because of comments here, but had no problems encoding it... even lowering the max_bitrate to 7500, which was said to be a possible trigger, did not cause a problem with that disc.

[Fishman0919]

Originally posted by Jeffster
Nope, your not the only one... I've never experienced any problems with 2.70 Basic either.

I made an effort to got hold of the infamous SATC disc with the HBO screen because of comments here, but had no problems encoding it... even lowering the max_bitrate to 7500, which was said to be a possible trigger, did not cause a problem with that disc.

Just a question Jeffster, do you have a Pentium or AMD??

[Rockas]

This may be a shot in the dark but can you people post the Anti-virus you're running? and if you shut it down when encoding or not?

[Jeffster]

Originally posted by Fishman0919
Just a question Jeffster, do you have a Pentium or AMD??

Sorry, I should have mentioned that.

Very modest specs compared to everyone else...

Intel Celeron 1.0GHz (Tualatin)
512 MB SDRAM
Asus TUSL2-C MB
ATI Radeon 9200 SE
XP Pro SP2

[bolke]

The same problem happens with every CCE version I have tried, at the end of the "prepare" option.

That's why I tried to use the HC encoder instead, but the same problem occured. Only now later.




[14:10:58] One Click encoding activated...
-----------------
[14:10:58] Phase I, PREPARATION started.
- "Steal Space from Extras" mode is enabled.
- VTS_01: 2.772.047 sectors.
-- Scanning and writing .D2V file
-- Processed 155.014 frames.
-- Building .AVS and .ECL files
- Reduction Level for DVD-5: 79,1%
- Overall Bitrate : 5.606Kbs
- Space for Video : 4.243.536KB
- Movie improvement from extra reduction = ,0%
- HIGH/LOW/AVERAGE Cell Bitrates: 6.605/1.229/5.606 Kbs
[14:16:50] Phase I, PREPARATION completed in 6 minutes.
[14:16:50] 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
-- Encoding resulted in no .M2V, retrying.
- Creating M2V for VTS_01 segment 3
-- Encoding resulted in no .M2V, retrying.
- Creating M2V for VTS_01 segment 3


Any ideas what could be wrong?

[jdobbs]

CCE failing isn't the only possible cause of this... if you accidentally hit a key during encoding and the "Cancel" button is highlighted -- it can stop the job and cause this error.

In fact that is the only way it has ever happened to me -- but since it was attributable to my own stupidity it doesn't count... :)

[bolke]

Originally posted by jdobbs
CCE failing isn't the only possible cause of this... if you accidentally hit a key during encoding and the "Cancel" button is highlighted -- it can stop the job and cause this error.

In fact that is the only way it has ever happened to me -- but since it was attributable to my own stupidity it doesn't count... :)

No, it doesn't. ;)
Of course this may have happened, but probably not.
I closed all running programs before starting the encoding process.
Checked after about 40 minutes, it was still running. The next time I checked all programs were running again. For some reason the computer had rebooted (perhaps after a crash??). By the way, the encoding was not finished. :)
That probably wouldn't have happened when clicking "cancel".

I've spent a few hours yesterday and again today trying to compress a dvd for the first time. CCE doesn't work, HC Encoder failed. Which encoder should I try now? Which is nearest to these two quality-wise?

[jdobbs]

You wouldn't be running on a machine that is overclocked, by chance, would you? It sure sounds like a system instability issue... and video encoding is the most demanding task your computer will ever run.

I've seen something similar reported several times in the past week -- and backing down to spec has fixed it every time.

[bolke]

No, it isn't overclocked, but I do have this: http://www.upgradeware.com/english/product/370gu/370gu.htm

It causes big stability problems with Windows 2000, but not with XP. At least, not until now....

To test it I would have to go back to a PIII 667MHz CPU (now a 1.3GHz). That has a big disadvantage. It will be just about impossible to do any compressing at all with that thing. I'll try one more time tomorrow, probably with Quenc. See what that does.


If the strain of compressing caused a crash, why would this be at the end of the log:
- 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
-- Encoding resulted in no .M2V, retrying.
- Creating M2V for VTS_01 segment 3
-- Encoding resulted in no .M2V, retrying.
- Creating M2V for VTS_01 segment 3

That doesn't seem to make sense in case of a "random" crash.