xberk wrote on 4/27/2017, 4:52 PM

Is this true on a new project?


marc-s wrote on 4/27/2017, 4:57 PM

Yes, I just started the project. Something I've come across in the forums is the possibility of a problem with certain types of footage because of the way it's saved into the metadata? This is XAVC-S 4K from a Sony A7rii.

xberk wrote on 4/27/2017, 5:10 PM

Check View Menu/ Event Media Markers / Show Markers .. or Ctrl+Shift+K

marc-s wrote on 4/27/2017, 5:17 PM

Yes those are checked. I just ran a test creating markers on a wave file in the trimmer. That works and appears when returning to the file. This seems to be an issue with the type of footage I'm using (XAVC-S). Curious if this has been fixed in Vegas 14.

xberk wrote on 4/27/2017, 9:34 PM

Ok Marc. I rendered a short bit to XAVC-S and tried it. I'm seeing the same behavior as you. The marker disappears once the trimmer is closed. This is true in VP13 and in VP14. Same behavior with XAVC-S footage.

This seems to be a bug. I'd file a report on it.

marc-s wrote on 4/28/2017, 12:20 AM

Thank you for checking.

NickHope wrote on 4/28/2017, 1:08 AM

Confirmed. Markers stored internally in XAVC-S files such as those from cameras like the Sony A7Rii or A7Sii, or rendered by VP13 & VP14, do not appear in VP13 or VP14. However they do get saved in the files, and they do appear in VP12.

To confuse matters, if you render XAVC-S in VP12, markers for those files are stored in a sidecar .sfl file, not the MP4 file itself. And that then functions correctly in VP12, 13 & 14.

XAVC-L and XAVC-I use .sfl sidecar files in all versions and behave themselves properly.

Also Sony AVC stores markers in the file itself and those show up in all versions.

For info from the help file:

"If the selected file type cannot save markers internally, Vegas Pro will save the metadata to an external file with an .sfl extension (using the same base name as your media file)."

As a side note, I've always thought that saving markers to the original file's metadata is a rather dangerous practice. I fear it may affect the files' compatibility with other applications. I have no evidence of it causing problems though. I'd prefer if markers got saved to .sfl files for all formats.

NickHope wrote on 4/28/2017, 2:11 AM

I also discovered that markers and regions don't get saved in ProRes or HEVC files in VP14. It does at least warn you: "An error occurred while saving one or more files. The reason for the error could not be determined".

However if you add markers or regions to ProRes files in an earlier version that decodes them with Quicktime instead of the VP14 native codec, then the markers and regions get saved in a sidecar .sfl file. However they won't subsequently show up in VP14 unless you bypass the native Prores/HEVC codec.

And I also discovered that unchecking "Automatically save trimmer markers and regions with media file" does not stop the automatic saving. Separate thread on that here.

NickHope wrote on 4/28/2017, 2:33 AM

XAVC-S issue support request: [Ticket#2017042817005543]

ProRes/HEVC issue support request: [Ticket#2017042817005614]

marc-s wrote on 4/28/2017, 1:25 PM

Thanks Nick. I hope they solve this as the Trimmer is one of the main reasons I still use Vegas. When you have a series of 30 minute interviews it's very useful for logging sections and comments before building the timeline.

xberk wrote on 4/28/2017, 3:44 PM

Nice job Nick, as usual, and Marc for bringing this up ... Personally I don't use trimmer markers except on rare occasions.

Marc .. For intercutting interviews, I use regular timeline markers, a separate veg file and a second instance of Vegas rather than the trimmer.

marc-s wrote on 4/29/2017, 3:00 AM

Thanks, that's what I did on this project. Prefer the trimmer though.

NickHope wrote on 5/1/2017, 10:24 PM

XAVC-S issue support request: [Ticket#2017042817005543]

ProRes/HEVC issue support request: [Ticket#2017042817005614]

Today I received separate replies from Support for each ticket that included this:

"This is now logged in our bug tracker as a known issue for QA/Development to take a look at."

NickHope wrote on 6/26/2017, 11:58 PM

The issue with markers and regions in ProRes or HEVC files is fixed in VP14 build 270. They are now correctly saved.

However the issue with markers and regions in XAVC-S files remains.

NickHope wrote on 9/14/2018, 10:08 PM

This issue also arose in relation to Sony AVC files in this post. A summary as I understand it:

VP13 and VP14 save markers/regions for XAVC-S and Sony AVC into the file itself. Those "internal" markers/regions in XAVC-S files then only show up in VP12 or earlier. Those "internal" markers/regions in Sony AVC files only show up in VP14 or earlier.

VP15 and VP16 by default save markers/regions for XAVC-S and Sony AVC into a "sidecar" sfl file. Those "external" markers/regions only show up in VP13 or later (XAVC-S) or VP15 or later (Sony AVC).

However if so4compoundplug is disabled in VP15 or later, those versions will still markers/regions for Sony AVC (but not XAVC-S) into the file itself, and will also display them.

So the required fix would be to make Vegas display regions/markers stored within XAVC-S and Sony AVC files, as it used to.