Vp13 not reading timestamp in mp4 files

hans-m1736 wrote on 3/22/2018, 8:32 AM

I have VP13. While making a registration of a 4hrs session, I kept one (statically placed ) camera running continuously while making over 100 short 'clips' walking around with a 2nd camera. I thought using the nice feature which inserts clips on the timeline according to their timestamp would allow me to sync just one clip - and all the rest would be in sync as well.
To my dismay, it doesn't work! The program complains it can't find the 'offset' (the start-time, I take it) and indeed: the corresponding  column in the media window is empty. And not just for the clips (shot with a Canon, MP4 format) but also for the MTS files shot with a Sony!  I read on a forum this was a bug in a software module ('Co4' something) but as far as I can see I do not have this module (at least it doesn't figure in the advanced preferences where it should).
Is there a solution for this? For example re-muxing the (mp4-) clips to a format which my Vegas CAN read? But which format to use, then?
It is really a big problem for me; it's not only the work of syncing all those clips one-by-one, but also many are really very hard to sync as they may show something not captured by the 1st camera.
I am even willing to buy the latest upgrade, but I can't find info on whether this 'bug' (i think it is one) has been solved.
Can someone help?

Comments

NickHope wrote on 3/22/2018, 8:35 AM

https://www.vegascreativesoftware.info/us/forum/avc-xavc-s-issues-in-vp15-try-disabling-so4compoundplug-dll--108345/

and

https://www.vegascreativesoftware.info/us/forum/timecode-in-not-being-read-by-so4-compound-reader-in-vegas-pro-15--109306/

hans-m1736 wrote on 3/22/2018, 9:38 AM

Thanks, Nick, and I apologize for not having found these threads myself.
Despite your name, your response does not give me much hope, though. It seems to be a recurring problem which may or may not have to do with the 'So4' module. Contrary to what was said in one of those threads the bug apparently also occurrs in VP13. Apparently VP14 does better but it is still not solved in VP15.
I really feel duped as this bug seems so very easy to fix.

HOWEVER, I find it hard to believe that the programmers installed this feature knowing it would't work for ANY file type. So, I am still hoping for advice on a file type which works so IO can re-mux my clips to a file type which works.
Hans

Musicvid wrote on 3/22/2018, 10:18 AM

One thing that goes all the way back to at least V8 and my multicam shoots is the fact that if the first frame is missing the timestamp, Vegas never finds sync. This happens even with SMPTE nondrop freerun TC in a master/slave chain.

One thing you can try is to trim the first few frames of each take and see if Vegas picks up the index, even if it isn't necessarily 00.00.000.

Let us know if this old trick from DVCAM days affects your outcome.

Since your footage is mp4, you might also check and see if mp4Box or ffmpeg are capable of reindexing your timestamps, at least that would get you closer. Syncing to audio is an alternate means of getting there.

Here's a background discussion of various strategies in Vegas.

https://www.vegascreativesoftware.info/us/forum/multi-cam-sync-flash-rolling-shutter--92837/?page=1

hans-m1736 wrote on 3/22/2018, 11:48 AM

@misicvid: I think there may be, also in the links mentioned above, some confusion between 'timecode'and 'timestamp'. (BTW, Vegas offers both as an option to use). Afaik the 'timecode' is embedded in the frames; taking care of syncing sound with video etc. The 'timestamp' on the other hand is in the meta-data of the file; it simply marks the start of the clip. With modern gear I'd say that is enough to go on and I would expect Vegas to read it and arrange clips accordingly on the timeline.

Hans

 

Musicvid wrote on 3/22/2018, 5:04 PM

If you are saying something has changed since V8, I accept that, and I have no experience auto syncing Vegas multicam footage to anything other than embedded SMPTE TC.

I wouldn't hang my hat on tags as someday has to write them; they are missing or just plain wrong a good part of the time...