Timecode In not being read by So4 Compound Reader in Vegas Pro 15

Dr Zen wrote on 11/7/2017, 12:00 AM

I was trying to sync some video clips using Timecode in Vegas Pro 15 and thought I was going crazy, until I realised something was not working correctly in Vegas Pro 15. Can someone else please confirm that this is a problem, so that it can be reported ?

Steps to reproduce problem in Vegas Pro 15:
1. Import series of videos recorded with Sony A7s using XAVC-S format, into VP15.
2. Go to Project Media tab and set Views = Details
3. Timecode In column = 00.00.00.00 for all clips, instead of different time stamps for each video.
4. I then opened the same video clips with Vegas Pro 14 and this time there is proper data showing for Timecode In.
5. I then went back to Vegas Pro 15 and opened Preferences/Internal using Shift key and disabled So4 Compound Read for AVC/M2TS.
6. Re-import video clips and this time Timecode In shows unique values for each clip - Layout Tracks using Media Date/Time Stamp now spreads out videos correctly on timeline.

Screen shot showing problem:

Screen shot showing Timecode now working, when So4 is disabled:

Regards
Derek

Comments

NickHope wrote on 11/8/2017, 1:56 AM

I tested this in VP15 build 216 with 3 XAVC-S clips that I have saved in the past from various threads on this forum. One called "Sony-Alpha-7RI-ii...", one called "Sony-A7SII...", and one called "Sony-RX10-II-xavc-s...". They show the same "timecode in" with either compoundplug or so4compoundplug, and it's not zero.

AVsupport wrote on 12/18/2017, 1:10 AM

[VP15.261] Using my 50fps XAVC-S clips from my A6300 which recorded freerun timecode, I can confirm that all TC Start times are Zero (using so4..) in Vegas.

I discovered this also when I wanted to burn-in Timecode, and all clips started from Zero.

I'd say this is likely a bug, I would say, needs to be fixed (as this probably also breaks multicam sync & editing..!)

Last changed by AVsupport on 12/18/2017, 1:14 AM, changed a total of 1 times.

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Dr Zen wrote on 12/18/2017, 5:09 AM

Thank you for confirming this AVsupport.

My Sony XAVC videos are coming directly a Sony A7s.
I believe there is definitely a bug in the so4 plugin which is causing this problem, because when I deactivate it in the Internal Preference Settings and default to the original Mainconcept decoder, the Timecode displays as it should. Timecode also works 100% OK in Vegas Pro 13 and 14, but not VP15.

It would be great if we can find a 3rd person who works with XAVC video to confirm this and then get this REPORTED to Magix as a confirmed bug. It is tedious to have to keep switching from so4 to Mainconcept all the time - I would prefer to use the new so4 encoder/decoder for everything.

 

AVsupport wrote on 12/20/2017, 4:27 AM

[[MENTION:undefined]] Nick, maybe since the previous VP versions didn't have that problem, those old files have attached data that VP15 can't create..Maybe rename/re-import those to replicate the fault, just a suggestion; otherwise I shall post some of those culprits

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

AVsupport wrote on 12/20/2017, 4:04 PM

This issue is definitely caused by 'So4..'. when I disable the plug, and re-import the clips, I have TC info back for the clips in VP15. (However, when I use either Vegas TC effect or Ignite TC effect to 'burn in TC', clip TC will displayed 0 at clip start, so no joy really..but I'm not sure if this is a different unrelated issue)

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

NickHope wrote on 12/20/2017, 10:49 PM

I tested again in VP15 build 261 with those 3 files I have. Now I am seeing the same problem as you guys. Perhaps I messed up my previous test. I have added it to the "known issues" post. I'll let one or both of you report it.

AVsupport wrote on 12/20/2017, 11:39 PM

Great. Thanks Nick! Always on the ball! Please go ahead @Dr Zen!

Let's get these bugs smashed!!

Last changed by NickHope on 12/22/2017, 12:21 AM, changed a total of 1 times.

Reason: fix Dr Zen tag

my current Win10/64 system (latest drivers, water cooled) :

Intel Coffee Lake i5 Hexacore (unlocked, but not overclocked) 4.0 GHz on Z370 chipset board,

32GB (4x8GB Corsair Dual Channel DDR4-2133) XMP-3000 RAM,

Intel 600series 512GB M.2 SSD system drive running Win10/64 home automatic driver updates,

Crucial BX500 1TB EDIT 3D NAND SATA 2.5-inch SSD

2x 4TB 7200RPM NAS HGST data drive,

Intel HD630 iGPU - currently disabled in Bios,

nVidia GTX1060 6GB, always on latest [creator] drivers. nVidia HW acceleration enabled.

main screen 4K/50p 1ms scaled @175%, second screen 1920x1080/50p 1ms.

Dr Zen wrote on 12/22/2017, 3:45 PM

I have now reported the problem via support page and provided a link back to this forum thread.