Not recognizing SMPTE/EBU timecode

Red Prince wrote on 6/10/2018, 8:37 PM

Well, I thought 🔮 Vegas Pro sported multicamera capabilities, which would automatically align a number of audio and video clips based on the SMPTE timecode, which has been around for about 50 out of my 68 years. 👴 Was I wrong? 😞

I created two test audio (.wav) files, both having the good ole LTC (linear time code, SMPTE) in the left channel and my voice in the right. I asked Vegas to Tools / Multicamera / Synchronize Media Timecode to Align Events, just to be smitten by Vegas, which claimed that, Some media did not have valid offset information and were skipped. 👀 And by some it meant all, even though both had perfectly valid LTC in the audio itself. 😱

Well, I ran it through Tentacle Timecode Tool, which removed the audio LTC and replaced it by the more modern bext chunk, as specified by the EBU Broadcast Wave Format. And here you can see Vegas smiting me again (at the end, the video shows both files do, indeed, have the bext chunk, which is quite empty, except for the timecode information!):

(This is in 4k because it is just a recording of my 4k monitor, but if it seems smudgy on smaller size screens, it just acts exactly the same as I described above for when I tried it with the timecode recorded in the left channel of each audio.)

And this shows Vegas media properties show the option to use the timecode grayed out in the first test file (the second one had it grayed out as well):

This was in the current version of Vegas Pro 15, as can also be seen in the video.

So, is this a bug or am I missing something?

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Comments

Former user wrote on 6/10/2018, 8:40 PM

Don't they have to be on the timeline first to sync them? and I also thought that this only worked with Broadcast Wave Formats. It won't read timecode on an audio track.

From internet: 1. A Broadcast Wave File is a WAVE file with added information (timestamps etc) contained in the header .2. A standard WAVE file only contains sample rate, bit depth track count and file length in the header.

Red Prince wrote on 6/10/2018, 8:46 PM

Don't they have to be on the timeline first to sync them?

This was the only way I could find to try to sync them. And the error message suggests Vegas thinks something is wrong with the media files. As does the fact the media property sees no timecode in the media.

At any rate, if there is another way, I need exact directions because the help file is very vague.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Red Prince wrote on 6/10/2018, 8:48 PM

I also thought that this only worked with Broadcast Wave Formats.

It is in the BWF. That is what the bext chunk is for.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Former user wrote on 6/10/2018, 8:48 PM

If the timecode is on one of the stereo tracks, then Vegas will not read it. It does not know analog timecode.

and with any multicamera, you have to have them on the timeline on separate tracks first I believe.

Former user wrote on 6/10/2018, 8:53 PM

I am not sure it would sync audio with timecode, I know it will do it with Video that has timecode.

Former user wrote on 6/10/2018, 9:16 PM

I realize now I gave you some bogus information and I apologize. It has been a long time since I worked with timecode. You are correct in you apply the sync with the files in the media pool and it is supposed to lay them out on the timeline based on timecode. Again, sorry for being confused and questioning your steps. If you have a wav file you can upload somewherre I can try it on my version 12 of Vegas to see if it works correctly here.

Former user wrote on 6/10/2018, 9:31 PM

I created a BWF file with my Sonar software and vegas does not see the timecode. I also recorded within vegas as a BWF and it does not see timecode. I am thinking this option might only work with video, but still not convinced. It seems like I did this a long time ago but I haven't worried about timecode since I joined the NLE world.

Red Prince wrote on 6/10/2018, 10:08 PM

Yes, here are the files I used. This is the version with the timecode in the BWF format, the same files used in the above video.

I am thinking this option might only work with video, but still not convinced.

That would make no sense. The whole point of timecode is to record the video with a camera and the audio with a separate audio recorder, while using the same timecode with both devices, then syncing the separate video with the separate audio in the editing software. Yes, it can also be used to sync multiple cameras shooting the same scene from different angles, but that is just a nice byproduct of what timecode was designed for.

Essentially, timecode was invented to be for video what a slate is for film. It has been around continuously since the analog days of 1967 or so, so it is not some new idea that the Vegas team could not have heard of yet. And considering Vegas started off as an audio editor, I am very surprised it does not know how to deal with the traditional time code being recorded as an audio signal, but would be even more surprised if it cannot interpret the BWF metadata.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

ryclark wrote on 6/11/2018, 4:19 AM

Yes your files contain the correct BWF timecode info since they position themselves correctly within an Audition Multitrack session. However, as you have found, Vegas 15 doesn't seem to be able to correctly find and use that metadata for some reason.

Red Prince wrote on 6/11/2018, 11:52 AM

Thanks, ryclark. So, at this point I have to hope that someone from Magix will notice this thread, and that Nick includes it in his list of known bugs.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Marco. wrote on 6/11/2018, 2:18 PM

Vegas Pro can read the BWF timecode but only while you import the BWF files via the file menu BWF import option, not for that context menu layout option.

If I use the BWF import option for the two files you offered for download, Vegas Pro places "test1.wav" at timeline position 00:17:01 and "test2.wav" at 00:17:08 (take care of the import settings on the bottom of the import window).

Former user wrote on 6/11/2018, 2:23 PM

I never even noticed the BWF import. My eyes just passed over it. Thanks Marco.

Marco. wrote on 6/11/2018, 2:50 PM

Just a side note …

If a BWF file is used in Vegas Pro, take a look at its file properties. There is a "time reference" number for the "BWF Information". This is the sample count which represents the timecode start of the file.

For "test2.wav" the time reference is  49375589 (samples).
It's 48 kHz – so  49375589 divided by 48000 is 1028 (seconds) which equals the timeline layout after BWF import in Vegas Pro.
 

Former user wrote on 6/11/2018, 3:12 PM

I imported the files I created in Sonar and they worked perfectly. Thanks

Red Prince wrote on 6/11/2018, 3:32 PM

Thanks, Marco! I never noticed the BWF import either. Now, I guess I’ll have to create a YouTube tutorial. Though I shall wait till my two Tentacles, that I ordered yesterday, arrive. These two test waves I made in Audacity by hand.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

max8 wrote on 6/11/2018, 3:40 PM

Would it be possible that support for audio timecode could be added to Vegas?

Tools like the Tentacle and other "SMPTE workflows" are ubiquitous. While Avid Media Composer can handle this type of timecode for a long time, Adobe added support to Premiere a while ago.

ryclark wrote on 6/12/2018, 10:16 AM

Yes, it seems very odd that you would have to Import BWF audio files separately in order to use the embedded time reference. 😞 However even if it eventually happens automagically you sometimes need the option to ignore the time stamp.

Red Prince wrote on 6/13/2018, 2:21 PM

Well, Marco . . . Today my Tentacles have arrived. I promptly hooked one up as an audio input (using an XLR adapter that I bought with the Tentacles) to my Blackmagic Design Video Assist 4k and just recorded the video out of the HDMI output of my computer.

I then used the Tentacle utility to convert the LTC audio to video metadata. I am not familiar with the structure of .mov files, but this is the ending of the converted file, including to what to me looks like a mention of the timecode:

But when I check its properties under Vegas (Pro 15, current), it does not know about that metadata:

So, what am I still missing?

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Red Prince wrote on 6/15/2018, 12:19 PM

On a related issue, when the timecode in the .wav file starts at several hours, the method Marco described places the wave that far in the project timeline. When that happens using several waves and aligning the corresponding videos with them, and grouping it all together so it stays aligned, how do I drag it all to the start of the timeline (and keeping the whole group all synced, of course)? I mean, yes, I can drag it with a mouse, but when there are hours of empty space before it all, is there some simple keypress or mouseclick that would remove all the empty space from the event that is the earliest in the group, while moving everything else in the group with it still synced?

I thought I was able to remove all empty slack in front of an event in the past, but for the life of me I cannot remember how.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

rraud wrote on 6/15/2018, 1:31 PM

In the 'Time Format', (right-click time display) just change the "Set time at Cursor" prior to importing. So the head of the timeline starts at, or just prior to the files' TC.

Red Prince wrote on 6/15/2018, 1:50 PM

In the 'Time Format', (right-click time display) just change the "Set time at Cursor" prior to importing. So the head of the timeline starts at, or just prior to the files' TC.

Wow, I didn’t know you could do that. Alas, it still leaves all the leading empty space in the project, it just assigns negative time to it. What I’d like to do is remove the leading empty space from the project.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

Red Prince wrote on 6/15/2018, 1:55 PM

Oh, wait, you said before importing... OK, sounds good, but that assumes I know the starting time code before I import. Let me try to figure that out, but it sure complicates everything. I would just like to import it and then delete all the leading empty space. I thought there was a way to do that (I seem to vaguely recall that from one of those Gary Rebholtz [I think that is his name] tutorials).

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)

max8 wrote on 6/15/2018, 5:12 PM

Hi,

if you manage to know the timecode before import, you can set the ruler start time in the project properties (Properties --> Ruler). That avoids the negative timecode in the timeline (and empty space). And you preserve the original timecode in the timeline if you need that for your workflow.

To delete the empty space you can select a region of the timeline and enable auto-ripple (Ctrl+L) and press delete. Don't forget to disable this option afterwards.

Red Prince wrote on 6/15/2018, 6:25 PM

Well, so I tried to set the time at cursor to just a few frames before the first timecode. Then I imported the files, and Vegas still placed them far out there. Namely, the first file had the timecode of 00:02:57:12, so I set the time at cursor (which was at the start of the time line) to 00:02:57:00 and then imported the files. Vegas placed the first one at 00:05:54:13, which is 00:02:57:00 + 00:02:57:12 + 1 (not sure why the final + 1).

So, unfortunately, setting time at cursor before importing does not help.

He who knows does not speak; he who speaks does not know.
                    — Lao Tze in Tao Te Ching

Can you imagine the silence if everyone only said what he knows?
                    — Karel Čapek (The guy who gave us the word “robot” in R.U.R.)