Scenarist error message

[Corion]

Anyone seen this one before?...

"Warning The modification time of the MPEG file is incorrect. This may lead to delays upon importing. Please correct the file modification time.."

It does indeed slow down importing as well as many other operations...most annoying! The answer would seem to be to re-encode but I get this crop up from time to time, quite randomly (or so it would seem).

Is there anything I can do to avoid this in future?

BTW I'm encoding at 8mbps (CBR), PAL, 12-frame-GOPS, 1 in 3 closed.

[D3s7]

is the timestamp set to 00:00:00:00 in the mpeg?

not sure where you'd check that but it could be the cause

[mpucoder]

Sounds more like the file modification date/time is later than the vif file, so Scenarist makes a new vif file.

[dgoodbourn]

Check the date of the mpeg2. Is it in the future, if so that's your problem. Either change the date of the machine with Scenarist on, or modify the mpeg2 so that the date is reset.

D.

[Corion]

Good suggestions...turns out you're all correct in a way!

The files in question were encoded on Sonic Creator which instead of starting the timestamp from 00:00:00:00, uses the original timecode from the master tape. You can see this in the track editor in Scenarist. Not sure how to fix that but as it turns out that's not the problem.

The Mac on which Creator resides was under the impression that the year is 2036! I changed the modification date of the MPGs and all is working smoothly now - and needless to say sorted the mac out...though at this rate I'll probably still be running OS9 in 2036!

Thanks for your help.

[dgoodbourn]

The timestamp isn't a problem at all. (so long as the audio syncs up to it!!) The video can have any timestamp you want.

D.

[Corion]

The timestamp thing does appear to be causing Scenarist to crash out when previewing but the tracks all mux ok and are fine once on DVD.

[dgoodbourn]

Just to make sure we're all singing from the same hyme sheet, when you say timestanp, you do mean the data start time??? If so, (which I'm sure you are), then the timecode of any video shouldn't make any difference, and certainly shouldn't make Scenarist crash. My videos are never 00:00:00:00 and I've never had any problems at all. Maybe something else is making it crash?

D.

[Corion]

Yes, data start time (the starting number in the track editor right?). It may well be somthing else. We're running Scenarist Studio here and I'm not overly impressed. We've had a few problems with general stability and the guys at Sonic haven't been able to help. oh well, ho hum.

Thanks for your time though.

[dgoodbourn]

Which version of Scenarist are you running? My advice is don't go near v3. It's still fairly buggy.

D.

[Corion]

Unfortunately we only bought it 6 months ago and so came in on V3. Seems like most people here prefer 2.7. From what I read here I'd much prefer to be running 2.7 but I'm not sure how Sonic would feel about that! Now on 3.1 which I'm not even sure is up for general release yet but I had so much difficulty with 3.01 it had to be done.

[dgoodbourn]

Sonic should be able to supply you with a copy of v2.7, especially if you are having problems with v3.1

D.

[Arky]

Resetting your MPEG timestamps is simple - just use the freeware util 'ReStream' (find it on the main software download page, here on Doom9).


HTH.

Arky ;o)