Log in

View Full Version : Problems with .ogm and Nero


Micro
20th March 2003, 23:05
Have anyone noticed strange and very annoying problem, that some burnt .ogm movies do have differences with original laying on HDD ?

I recently did a XviD encode of good old Matrix and muxed it into .ogm stream with AC3 and capters using latest VDubMod.
When the CD burning was finished and Nero started to verify the CD it stopped in middle of the verification process with error message that one of the files was different from original, it was .ogm file.
When tried to load this file from CD to VDubMod it gave an error message in the middle of loading "Page error".
The same happened in almost all attemts to write the CD.
Later I used CD-(RW)
I verified the CD surface with CD Speed and everything was OK.
Also, the original file(s) were OK according to VDubMod.
OS:W2K SP3, Asus P4PE, P4 2.4, ASPI4.60, differnt writers: Asus, LiteOn, Plextor, different new versions of Nero, different write settings - TAO, DAO, DAO96.
I haven't tried other burning programs yet.

Anyone ever noticed similar problems ?

Neo Neko
20th March 2003, 23:13
No. But if this is the first time you have noticed it and you were not able to reproduce it. Would it not be safe to say it may have been a general burn error? If you can reproduce it let us know.

Micro
20th March 2003, 23:45
@ Neo Neko,

Yes, it is pretty constant problem with these two .ogm files.
I tried to burn them with different settings/burners several times.
Mostly these were unsuccessful attempts. But sometimes, when Nero gave me verification error, files were still readable by VDubMod.
I noticed verification problem also before on different machine with
WinXP, unfortunately I had no time then.

New: tested couple of times with some old WinOnCD3.8, so far written files were readable by VDubMod.
Will test with Easy CD Creator 6.0 soon .... but I feel it's NERO :-(

Micro

Koepi
21st March 2003, 07:56
that "page error" may indicate a problem with your memory or processor. Do you o/c your system?

Koepi

Micro
21st March 2003, 15:26
I can confirm now, that this problem is not related to .ogm or any other content.
It's some kind of OS - Burner program conflict.
Sorry for creating fuzz.

Micro