Bug Report: Videos longer than 24 hours loop sound back

Koplopermau wrote on 8/26/2019, 4:54 PM

Hello there!

We are YouTubers that makes gaming video's for my YouTube channel. We place gameplay videos ranging from minute long videos up to videos that can last several hours to even a day long! An example can be found here:


We are currently working on a project that will be almost a week long (you read that right, one video file of a week long) and as ridiculous as it sounds, we found some interesting bugs along the way.

If you create a video in Vegas Pro that lasts for longer than 24 hours (using several long movie files) and you play the video back in the program, at the 24 hours mark, the image will show correctly, but the sound will loop back to the first 24 hours that are in the project. However, if you put your cursor past the 24 hours mark and start playing the project, it will work correctly.

In terms of rendering video's, if you start rendering after 24 hours (so you render starts from a point past 24 hours in the project), the sound will be the sound from the first 24 hours of the project. However, if you start the render all the way from the start and let it render out past 24 hours, it will be just right.

I hope this can be fixed in a new release or update from Vegas 17, since it was just released.

- Koplopermau

Hardware configuration used: i9 9900k, 32GB RAM, MSI GTX1070 TI (8GB vRAM), separate HDD's for reading and rendering video files. Vegas itself is on a separate SSD.

Comments

Musicvid wrote on 8/26/2019, 8:02 PM

That's odd. In which format are you recording your audio?

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

FayFen wrote on 8/26/2019, 9:53 PM

I have two trivia Q for you

1- How big was that 1day video file?

2- How many of your 547K watched it from start to end?

3- what's the purpose?

Koplopermau wrote on 8/27/2019, 8:51 AM

That's odd. In which format are you recording your audio?

https://www.vegascreativesoftware.info/us/forum/faq-how-to-post-mediainfo-and-vegas-pro-file-properties--104561/

The audio format is Stereo ACC, 48.000Hz. I use nVidia Shadowplay for much of my footage.

I have two trivia Q for you

1- How big was that 1day video file?

2- How many of your 547K watched it from start to end?

3- what's the purpose?

1. The file was 101GB big and rendered using the .wmv container. Why not mp4 you ask? In Vegas 15 or lower the Sony AVC/MP4 would crash at videos longer than roughly 13 hours or more. WMV rarely crashes. The bitrate was 12mbit (to stay under the 128GB limit of YouTube). The render took about 7 non-stop days. Mind you that was on another PC that was slower that the one I have now, which should do it quite a bit faster.

2. We cannot see that in YouTube Analytics. However, looking at all viewers, they spend about 15 minutes on average on the video. Germany on average watches the longest with almost 30 minutes on average.

3. No particular purpose, it is just something we do and that our channel by now is known for. We want to make the longest actual content video for YouTube that someone has ever made and we would like it to stay at the top for quite some time, so we decided to put the bar pretty high. Oh and before you ask, yes, we took the 128GB limit into consideration and are talking to YouTube right now how to get the thing onto the platform.

- Koplopermau

Musicvid wrote on 8/27/2019, 4:43 PM

Missed your complete file properties, and those are needed to troubleshoot; however,

Shadowplay is historically incompatible with Vegas, but may work better in 17 with VFR support. Search the forum. I know it has some good features.

Working settings for OBS in Vegas are here :

https://www.vegascreativesoftware.info/us/forum/faq-what-obs-studio-settings-work-well-with-vegas-pro--109925/

With compatible source, an mp4 render shouldn't crash. WMV is kind of bellyup.

Koplopermau wrote on 8/28/2019, 7:30 PM

I intentionally did not post the entire thing because I thought it would be a wall of text and you were asking for the audio. Here's the entire thing.

General
  Name: Dolphin 2019.08.26 - 00.59.27.02.mp4
  Folder: G:\Fraps Filmpjes\Dolphin
  Type: AVC
  Size: 6,45 GB (6.608.630.551 bytes)
  Created: maandag 26 augustus 2019, 00:59:27
  Modified: maandag 26 augustus 2019, 01:18:08
  Accessed: maandag 26 augustus 2019, 01:18:08
  Attributes: Archive

Streams
  Video: 00:18:40,770, 60,000 (VFR) fps progressive, 1920x1080x32, AVC
  Audio: 00:18:40,575, 48.000 Hz; Stereo, AAC

Summary
  [TCFM]: 8

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: so4compoundplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 16.0\FileIO Plug-Ins\so4compoundplug
  Format: AVC
  Version: Version 1.0 (Build 8532)
  Company: MAGIX Computer Products Intl. Co.

OBS is a possibility, however, Shadowplay will do much better for us because it uses better hardware decoding than OBS, which will also use CPU encoding and eats our CPU (slowing down gameplay). Oh, don't mind the directory name 'Fraps', I no longer use that, I'm just used to that being my raw folder.

You are certainly right that sometimes (not always, though) Vegas doesn't cope well with nVidia mp4 files. The main reason for this, I believe, is that Vegas doesn't like the variable frame rate the program uses. We've had cases where the sound slowly unsynced further down the video. Never did we have trouble importing the video or did we have bad video quality. Only sound problems.

Above problem is easily fixable though by renaming the video files to .dif manually. Sound will then import correctly and bugs that exist in the mp4 file will no longer be there. I'm not sure if you guys knew about this particular quickfix, but it works. If I import the file with a .dif filename, I get this:

General
  Name: Dolphin 2019.08.26 - 00.59.27.02.dif
  Folder: G:\Fraps Filmpjes\Dolphin
  Type: AVC
  Size: 6,45 GB (6.608.630.551 bytes)
  Created: maandag 26 augustus 2019, 00:59:27
  Modified: maandag 26 augustus 2019, 01:18:08
  Accessed: maandag 26 augustus 2019, 01:18:08
  Attributes: Archive

Streams
  Video: 00:18:40,734, 60,001 fps progressive, 1920x1080x12, AVC
  Audio: 00:18:40,618, 48.000 Hz; Stereo, AAC

ACID information
  ACID chunk: no
  Stretch chunk: no
  Stretch list: no
  Stretch info2: no
  Beat markers: no
  Detected beats: no

Other metadata
  Regions/markers: no
  Command markers: no

Media manager
  Media tags: no

Plug-In
  Name: compoundplug.dll
  Folder: C:\Program Files\VEGAS\VEGAS Pro 16.0\FileIO Plug-Ins\compoundplug
  Format: AVC
  Version: Version 16.0 (Build 424)
  Company: MAGIX Computer Products Intl. Co.

Different decoder, different results. Who knows this is the solution?

Before we continue to start a war about compatibility though, I've used one of my own video files to recreate the actual issue. I also have a 10 hour video, rendered by Magix Vegas Pro 15, which shows the same issues. After 24 hours, the video plays the wrong sound and defaults to the first 24 hours instead of continuing to count past 24 hours. If you start playing the video on your timeline after 24 hours, you MIGHT hear the wrong sound. It is kind of random. The fix is pretty easy in my honest opinion, let Vegas continue to count past 24 hours on the timeline.

- Koplopermau

Musicvid wrote on 8/28/2019, 8:18 PM

The 24 hour reset may be a legacy issue, like 'way back to IBM.

No, I did not know about .dif files. What more can you share? Does it work with non-mp4 files? Any details greatly appreciated because this is a recurring problem for some.