Mick Hardy
2019-07-16T08:04:31Z
A few people have been reporting issues where a few seconds of video loops at the end of events. The Vegas events are set longer than the source media so it loops.

This may also cause black sections of videos if the template events have looping turned off.

It may be less obvious where events are too short and the media is truncated.

After several weeks of heartache and grey hairs, we've discovered this is a Vegas bug.

This affects Vegas 15 and Vegas 16 including the latest builds, Vegas 15 (Build 416) and Vegas 16 (Build 424).

It's caused by the new So4 Compound Reader in Vegas, which incorrectly reports the source media length. TandemVids adjusts the length of the events to match the media duration supplied by Vegas. Vegas gives incorrect data and we set the events too long so the source media loops. It's easily identified by the little indents circled in red in the attached time lines.

To rectify the issue, disable the Vegas So4 Compound Reader.

  1. Close TandemVids
  2. Open Vegas
  3. Options | SHIFT Preferences | Internal
  4. Type So4 in the search box
  5. Set the “Enable So4 Compound Reader” option to FALSE.


Disable So4 Compund Reader.jpg
So4 Compound Reader still broken 01.jpg
So4 Compound Reader still broken 02.jpg
So4 Compound Reader still broken 03.jpg
Mick Hardy
2019-07-21T09:30:01Z
We've finished a fairly major architecture change to work around this Vegas bug. We couldn't see Magix fixing it in a timely fashion.

The issue is caused by Vegas caching old files. When we replace the source media in the working folder for new customers, the file names are the same and Vegas incorrectly retrieves the previous customers file data, which is no longer valid. When TandemVids sets the length of the events to match the source media to be inserted, Vegas gives us the duration from a previous customer. It does this intermittently, which made it extremely hard to analyse.

Rather than building the project in the working folder, we now build the project directly in the customer's folder. This allows all source media files to have unique names due to the unique path for each customer's folder. As an added bonus, the customer's files are copied a single time. Previously the project was archived to the customer's folder after the build.

If you have any custom software, which relies on photos in the instance folder, it will no longer work. You'll need to add an additonal folder to the output using the Folders tab.

For DVD and blu-ray builds, the photos are copied to the folder configured on the Photos tab prior to the burn. They'll still be fine.

The changes are complete but they touch a lot of areas so testing will take several days.
Mick Hardy
2019-07-22T09:40:05Z
This issue has been fully resolved with the release of TandemVids 2018.1.2.0.

If you've disabled the So4 Compound Reader as a workaround, it can be turned back on.

  1. Close TandemVids
  2. Open Vegas
  3. Options | SHIFT Preferences | Internal
  4. Type So4 in the search box
  5. Set the “Enable So4 Compound Reader” option to TRUE.


Enable So4 Compund Reader.jpg