Vegas Pro 22 (239 Build) Timecode issue

Trevor-Miller wrote on 1/23/2025, 2:32 AM

After such a long wait we finally got a new update build 239, unfortunately it seems the fix I wanted the most as not been fixed which is the timecode fx reader Vegas pro 22 is still not reading my camera time code. Can you please get this issue sorted out vegas team. I lucky enough to have all version of vegas on my system so my work round is to track back to version 19 sync up my footage with the timecode fx plugin then open the project in verion 22 to continue. I would like to hear if anyone as successfully manage to get the timecode to work in version 22?

Comments

j-v wrote on 1/23/2025, 4:25 AM

I would like to hear if anyone as successfully manage to get the timecode to work in version 22?

No problem for me, look

 

met vriendelijke groet
Marten

Camera : Pan X900, GoPro Hero7 Hero Black, DJI Osmo Pocket, Samsung Galaxy A8
Desktop :MB Gigabyte Z390M, W11 home version 24H2, i7 9700 4.7Ghz,16 DDR4 GB RAM, Gef. GTX 1660 Ti with driver
566.14 Studiodriver and Intel HD graphics 630 with driver 31.0.101.2130
Laptop  :Asus ROG Str G712L, W11 home version 23H2, CPU i7-10875H, 16 GB RAM, NVIDIA GeForce RTX 2070 with Studiodriver 576.02 and Intel UHD Graphics 630 with driver 31.0.101.2130
Vegas software: VP 10 to 22 and VMS(pl) 10,12 to 17.
TV      :LG 4K 55EG960V

My slogan is: BE OR BECOME A STEM CELL DONOR!!! (because it saved my life in 2016)

 

VEGASDerek wrote on 1/23/2025, 9:26 AM

@Trevor-Miller

Could you provide some specifics on the media you are using? I suspect that this may be related to work with the new video engine and the replacement of some of our video decoders. We are aware of some timecode reading issues with a few formats, but without knowing the details on your media, we probably will not be able to help you out.

Trevor-Miller wrote on 1/23/2025, 3:38 PM

j-v is the time code reading the time code from your footage or the timeline in your project?

Trevor-Miller wrote on 1/23/2025, 3:43 PM

the camera use for recording is a Sony AX 53, shooting mode MOV or MP4 format, i've been using this camera for four or five years and never had a issue with vegas not picking up the time code for the camera footage.

VEGASDerek wrote on 1/23/2025, 3:59 PM

MOV and MP4 are containers and tell us virtually nothing about the actual format. Please provide a MediaInfo readout on the media you are using.

Trevor-Miller wrote on 1/23/2025, 4:58 PM

General Complete name : C0003.MP4 Format : XAVC Codec ID : XAVC (XAVC/mp42/iso2) File size : 1.67 GiB Duration : 4 min 8 s Overall bit rate mode : Variable Overall bit rate : 57.8 Mb/s Frame rate : 25.000 FPS Encoded date : 2024-10-18 08:20:13 UTC Tagged date : 2024-10-18 08:20:13 UTC Video ID : 1 Format : AVC Format/Info : Advanced Video Codec Format profile : High@L5.1 Format settings : CABAC / 2 Ref Frames Format settings, CABAC : Yes Format settings, Reference frames : 2 frames Format settings, Slice count : 8 slices per frame Codec ID : avc1 Codec ID/Info : Advanced Video Coding Duration : 4 min 8 s Bit rate mode : Variable Bit rate : 56.1 Mb/s Maximum bit rate : 60.0 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 25.000 FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Scan type : Progressive Bits/(Pixel*Frame) : 0.270 Stream size : 1.62 GiB (97%) Encoded date : 2024-10-18 08:20:13 UTC Tagged date : 2024-10-18 08:20:13 UTC Color range : Limited Color primaries : BT.709 Transfer characteristics : xvYCC Matrix coefficients : BT.709 Metas : 3 Codec configuration box : avcC Audio ID : 2 Format : PCM Format settings : Big / Signed Codec ID : twos Duration : 4 min 8 s Bit rate mode : Constant Bit rate : 1 536 kb/s Channel(s) : 2 channels Sampling rate : 48.0 kHz Bit depth : 16 bits Stream size : 45.4 MiB (3%) Encoded date : 2024-10-18 08:20:13 UTC Tagged date : 2024-10-18 08:20:13 UTC Other ID : 3 Type : meta Format : rtmd Codec ID : rtmd Duration : 4 min 8 s Bit rate mode : Constant Encoded date : 2024-10-18 08:20:13 UTC Tagged date : 2024-10-18 08:20:13 UTC IrisFNumber_FirstFrame : 2.600051 FocusPositionFromImagePlane_FirstFrame : 42900000.000 m AutoExposureMode_FirstFrame : Manual AutoFocusSensingAreaSetting_FirstFrame : Center Sensitive Auto ShutterSpeed_Time_FirstFrame : 1/50 s CameraMasterGainAdjustment_FirstFrame : 24.00 dB ElectricalExtenderMagnification_FirstFra : 100% AutoWhiteBalanceMode_FirstFrame : Automatic

Trevor-Miller wrote on 1/23/2025, 4:58 PM

is this what you need?

VEGASDerek wrote on 1/23/2025, 5:02 PM

Thank you. Yes, XAVC is one of the formats which is now using a new decoder. We are working on reading the metadata for this format with the new decoder so the timecode is handled properly. We do not have a timetable as to when this work will be done, but we are aware of this and it is in our database right now.

john_dennis wrote on 1/23/2025, 8:08 PM
General 
Complete name : C0003.MP4 
Format : XAVC 
Codec ID : XAVC (XAVC/mp42/iso2) 
File size : 1.67 GiB Duration : 4 min 8 s 
Overall bit rate mode : Variable 
Overall bit rate : 57.8 Mb/s 
Frame rate : 25.000 FPS 
Encoded date : 2024-10-18 08:20:13 
UTC Tagged date : 2024-10-18 08:20:13 
UTC Video ID : 1 
Format : AVC Format/Info : Advanced Video Codec 
Format profile : High@L5.1 
Format settings : CABAC / 2 Ref Frames 
Format settings, CABAC : Yes 
Format settings, Reference frames : 2 frames 
Format settings, Slice count : 8 slices per frame 
Codec ID : avc1 
Codec ID/Info : Advanced Video Coding 
Duration : 4 min 8 s 
Bit rate mode : Variable Bit rate : 56.1 Mb/s 
Maximum bit rate : 60.0 Mb/s 
Width : 3 840 pixels 
Height : 2 160 pixels 
Display aspect ratio : 16:9 
Frame rate mode : Constant 
Frame rate : 25.000 FPS 
Color space : YUV 
Chroma subsampling : 4:2:0 
Bit depth : 8 bits 
Scan type : Progressive 
Bits/(Pixel*Frame) : 0.270 
Stream size : 1.62 GiB (97%) 
Encoded date : 2024-10-18 08:20:13 UTC 
Tagged date : 2024-10-18 08:20:13 
UTC Color range : Limited 
Color primaries : BT.709 
Transfer characteristics : xvYCC 
Matrix coefficients : BT.709 
Metas : 3 
Codec configuration box : avcC
 
Audio 
ID : 2 
Format : PCM 
Format settings : Big / Signed 
Codec ID : twos 
Duration : 4 min 8 s 
Bit rate mode : Constant 
Bit rate : 1 536 kb/s 
Channel(s) : 2 channels 
Sampling rate : 48.0 kHz 
Bit depth : 16 bits 
Stream size : 45.4 MiB (3%) 
Encoded date : 2024-10-18 08:20:13 
UTC Tagged date : 2024-10-18 08:20:13 
UTC Other ID : 3 
Type : meta 
Format : rtmd 
Codec ID : rtmd 
Duration : 4 min 8 s 
Bit rate mode : Constant 
Encoded date : 2024-10-18 08:20:13 UTC 
Tagged date : 2024-10-18 08:20:13 UTC 
IrisFNumber_FirstFrame : 2.600051 
FocusPositionFromImagePlane_FirstFrame : 42900000.000 m 
AutoExposureMode_FirstFrame : Manual 
AutoFocusSensingAreaSetting_FirstFrame : Center Sensitive Auto 
ShutterSpeed_Time_FirstFrame : 1/50 s 
CameraMasterGainAdjustment_FirstFrame : 24.00 dB 
ElectricalExtenderMagnification_FirstFra : 100% 
AutoWhiteBalanceMode_FirstFrame : Automatic

Sorry. That S#1t just drives me nuts.

Trevor-Miller wrote on 1/23/2025, 11:40 PM

Thanks for the update and info.

Thomas-Monks wrote on 4/13/2025, 8:09 PM

Although typically, I shoot and edit with my Sony AX-700, I'm going 2 cameras for an upcoming shoot, adding a Sony Z90. I'm running Vegas 22 Build 239 and want to use Sony's built-in TC generator to synch to the two camera recordings in Vegas

I've having a hard time trying to figure out how to get these two cameras to synch in my timeline. All I can find is "Audio Synch info." Since I have good Sony cameras with TC built in, I want to use it :-)

Please help me find educational stuff about how I do this...sorry being a first time virgin using TC in Vegas. BTW, I'm shooting both cameras in 4K, delivering in HD.

Thanks,

Tom Monks

Thomas-Monks wrote on 4/13/2025, 8:27 PM

Update: I was able to try the Lay Out Tracks Using Media Time Code." Strange it puts each segment on a different track... no biggie, I guess as I can manually move them to their C1 or C2 tracks. At least they're synched. Agree, comments, suggestions ?

wjauch wrote on 4/13/2025, 9:03 PM

@Thomas-Monks please check out this thread: https://www.vegascreativesoftware.info/us/forum/timecode-sync-attempt-error-message--145178/?page=2

This was my journey into getting timecode sync to work, several very helpful forum members kindly helped with scripting writing scripts that work and are way beyond my knowledge. User joelsonforte.br very kindly sent me his timecode tools, which I have used in Vegas 21, 22 and 19. Perhaps he'd be willing to share it with you also (or sell it if he has made it a commercial product)?

Thomas-Monks wrote on 4/13/2025, 9:46 PM

Ya, I know nothing about scripts. Ok, I did figure out a work-around...

1) Grab all segments from C1 and C2... IMPORT into a new Vegas .VEG and save as "TC GENERATOR.VEG"

2) Execute "Lay Out Tracks Using Media Time Code." which does line up both camera's segments to matching time code :-) Than SAVE to the same .VEG file.

3) DELETE ALL TRACKS for C2... SAVE AS "TC CAM 1.VEG"

4) CLOSE and REOPEN "TC GENERATOR.VEG" (Has both camera's tracks). DELETE TRACK (All Cam 1 tracks)

5) SAVE AS "TC CAM 2.VEG"

6) OPEN main project and IMPORT "TC CAM 1.VEG" and "TC CAM 2.VEG"

7) That did it with the CAM 1 and CAM 2 tracks all TC SYNCHED :-) Be sure to begin both tracks at the same frame in the main project.

If anyone know of an easier solution, let me know.

Thanks,

Tom

 

Trevor-Miller wrote on 4/14/2025, 7:51 AM

The work round I use is very straight forward, if you are a long time user of Vegas and lucky enough to have a previous going back in time from V.19 just start and sync your project as the TC works fine, save it and then re-open in V.22 lock your tracks and start editing, just remember you cannot open a V.22 project file in a older Version if you need to re sync.

Thomas-Monks wrote on 4/14/2025, 10:21 AM

Thanks for the heads-up Trevor... I will try it. One major issue that I have is that I will need to import the 2 cameras, TC arranged clips into a much more complex pre-produced final show. I will give it a shot. Thanks !

Trevor-Miller wrote on 4/21/2025, 4:26 AM

It's so annoying they just release another update but still have not addressed the problem with reading the media time code why is it such a big issue