Any file that does not contain a timecode field will start at zero in Vegas. Most MP4 files do not contain a timecode field.
Technically speaking I am not sure the MP4 spec allows for a timecode field. However some encoder/muxers put Quicktime format timecodes in MP4 files and this pretty much always works. The MP4 file format was based on Quicktime and most applications use the same demuxer for both.
For the OP as name: Aiki - 1) Timecode features begin with the camera - your camera has to be of a design that equipped with the proper tech will record timecode. Most consumer cameras DO NOT -although a familiar runtime code feature may be there - PLEASE please dive into the camera!
2) Timecode display will be affected by the format of the recording - hence an mp4 file or a .mov file (and consider re-wrap container options) may or MAY NOT offer access to the embedded timecode.
3) Based largely on point (2) there can be various issues for a software NLE like VegasPro. VegasPro is not able to display .mov container timecode natively - but can access it thru third-party apps. A lot depends on points (1) and (2) and (3) to be met for you to achieve work with timecode.
The XA20 has a timecode menu, check your settings there. I owned a HF G30 which is basically the same camera and looking at those files, they all contain the time code. Use the Vegas build in script "Add timecode to all media" to make the timecode visible.
The XA20 has definite timecode mechanics aboard the camera head. Generally the output should not be MP4 from this camera - so the first question is where did you get the MP4?
Recall that timecode generated from a camera head shows up in first generation encoding - if you later transcode footage - the likely result is that timecode is stripped from the succeeding gens of the original.
@VideoITguy
The XA20 does output MP4 at max. 35Mbps.
General
Complete name : E:\Personal\Raw Footage\HF_G30\Vienna_2013\MVI_0002.MP4
Format : MPEG-4
Format profile : Base Media / Version 2
Codec ID : mp42 (mp42/avc1/CAEP)
File size : 69.0 MiB
Duration : 16s 517ms
Overall bit rate : 35.1 Mbps
Encoded date : UTC 2013-12-23 09:41:24
Tagged date : UTC 2013-12-23 09:41:24
Video
ID : 1
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High@L4.2
Format settings, CABAC : Yes
Format settings, ReFrames : 2 frames
Format settings, GOP : M=3, N=30
Codec ID : avc1
Codec ID/Info : Advanced Video Coding
Duration : 16s 517ms
Bit rate : 34.7 Mbps
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Frame rate mode : Constant
Frame rate : 59.940 (60000/1001) fps
Color space : YUV
Chroma subsampling : 4:2:0
Bit depth : 8 bits
Scan type : Progressive
Bits/(Pixel*Frame) : 0.279
Stream size : 68.4 MiB (99%)
Language : English
Encoded date : UTC 2013-12-23 09:41:24
Tagged date : UTC 2013-12-23 09:41:24
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709
BUT, The question here is ..if an MP4 container of an AVC codec file (that is not transcoded from the original recording) can actually be re-wrapped in a .mov container such that VegasPro or other app will show the original timecode.
The question here is whether an MP4 container can contain timecode that Vegas can read. The answer was a conditional "Yes, sometimes". So the course of action is to first confirm that the timecode is present in the media, and if it's there then confirm whether Vegas sees it. There's no switch I know of to make Vegas see or not see timecode. It either does or doesn't.
<edit>There's also the question of *which* version and build of Vegas can read timecode in an MP4 container. The OP is using Vegas 12. </edit>
If the timecode exists but Vegas can't see it then rewrapping it in a quicktime container might be a fallback proposal.
[I]The question here is whether an MP4 container can contain timecode that Vegas can read.[/I]
Not a question anymore in my opinion. I am very certain the XA20 has identical file and timecode format as my HF G30 had and Vegas can read the timecode in those files.
EDIT: CORRECTION!!
the AVCHD file's timecode will be read correctly in Vegas, the MP4 version will always start from zero. I remembered that I used the HF G30 for an event and enabled it's dual recording capabilities. I also remembered that I sort of synced the timecode with the other cameras too and set it to Free Run. I have put both files on the VP13 timeline and applied the "add timecode to all media" script. The AVCHD (MTS) file starts at 5min something and the MP4 (AVC) file at zero.
can you try and record in AVCHD and see if you get a timecode in VP? I know it is probably not your preferred recording codec but it would at least confirm my findings.
For the OP as name: Aiki - 1) Timecode features begin with the camera - your camera has to be of a design that equipped with the proper tech will record timecode. Most consumer cameras DO NOT -although a familiar runtime code feature may be there - PLEASE please dive into the camera!
2) Timecode display will be affected by the format of the recording - hence an mp4 file or a .mov file (and consider re-wrap container options) may or MAY NOT offer access to the embedded timecode.
3) Based largely on point (2) there can be various issues for a software NLE like VegasPro. VegasPro is not able to display .mov container timecode natively - but can access it thru third-party apps. A lot depends on points (1) and (2) and (3) to be met for you to achieve work with timecode.
This Message last edited on 8/16/2016 1:00:32 PM, by videoITguy in above thread.
All sorts of things could be happening. Maybe Vegas doesn't read timecode in MP4 containers, or maybe it just doesn't read it the way your camera wrote it. For example, it used to be that Vegas could read TC in DV25 files it had captured, but not in DV25 files that were captured via Premiere.
I seem to remember reading here that you could actually just change an MP4 file extension to MOV and it would remain readable. It'd be a stroke of luck if rewrapping your mp4 files were that simple.
<time passes> Well, it IS that simple in as much as Vegas will still read an MP4 file if you change the extension to .mov. But since my own mp4 files definitely do not have timecode in them I can't say more than that.
Vegas may default to it's own decoder for AVC in quicktime wrappers. I'm certainly not seeing any differences in the way Vegas identifies the .mov version of my .mp4 file. Vegas says each of them is "Type: Sony AVC". In comparison, Vegas identifies a different (DVCProHD).mov file as "Type: QuickTime" and vegas sees the timecode in it.
Here is the lower portion of the file info provided by MediaInfo:
Other
ID : 3
Type : Time code
Format : QuickTime TC
Duration : 5s 5ms
Time code of first frame : 00:29:37:36
Time code, striped : Yes
Language : English
Encoded date : UTC 2014-03-08 15:51:53
Tagged date : UTC 2014-03-08 15:51:53
Bit rate mode : CBR
Note the timecode format!
Here is a link to short MP4 file from my HF-G30. Maybe earlier versions can read the TC correctly?
Do you have the latest firmware for your XA20? I understand there was a new firmware release in 2014 that mentioned timecode improvements for MP4 files?
The latest is FW 1.0.4.0 but there where changes already in FW 1.0.3.0 that read:
[I]"When recording in the MP4 format [59.94P/50P (35Mbps)], changes have been made in the metadata details so that the time codes can be properly displayed in Apple Final Cut Pro X Version 10.0.9.
Frame Rate = 59.94P"[/I]
It involves FCP X but maybe it also helps with Vegas?
Former user
wrote on 8/17/2016, 8:06 PM
After finding a timecode reference (beginning of video), I have gone into Vegas and manually entered the timecode in the file properties. That then allowed me to match the original file so an editor using Final Cut could use my EDL and have a valid timecode reference.
FWIW My GoPro 3+ Black outputs a timecode into it's MP4 AVC files and Vegas 13 reads that timecode just fine. MediaInfo lists the TC as a Quicktime timecode field.