[Aaron Star]

To me that sounds like a hacked version of Vegas you are running.

There used to be problems with help files that were infected with code that tried to do numerous things on the machine. Someone could have infected common tasks in vegas, in an attempt to install code, or force you to a page that installs code.

Contemporary browsers like Chrome are most likely blocking this code execution, and its only getting so far as the task switch.

There are a lot of ways to get around Anti virus, and URL or code that calls somewhere else is a good way.

[Aaron Star]

So you think it’s the editing system creating a poor encode?

Maybe post a link to the video, so people can see what you are talking about.

If your system is caching the video, the playback will be the same everytime. Are you sure your getting a new uncached version each time? That would be for a short video, a long video is another thing. You really do no offer much info as to length or time in the video the problem happens.

Is there an extream amount of movement of screen change at the time the picture is having a problem?

Have your tried re-rendering the video, and re-uploading the video again? So you can replicate the problem? Maybe clipping the video out where the issue is, so you determine if the source material is causing the problem?

The full res vs 360p could be the way Facebook has thier page code written. I can see them wanting the business material running a better quality, and the timeline footage defaulting to low qaulity. Mainly the low quality is for speed to first frame playback, so you can see the video play instantly when scroll past it. Also having timeline playback set low end reduces your overall bandwidth across hundreds of thousands of users.

I looked into my crystal ball and its not telling me much more than this.

[Aaron Star]

Processing the Canon DPX files through FFMPEG:

ffmpeg -i A001C007_171001QB_CANON_000000%2d.DPX -vcodec dpx A001C007_171001QB_CANON_%d.dpx

Vegas will read the output dpx format just fine. There is something up with the way canon is writing their dpx format. It could be more updated, or there is an error in the header that the other NLE have just done a work around.

When you import the dpx image sequence into Vegas, set your project to 32-bit FP FULL (View transform ACES RRT sRGB). Then on the import screen/media properties choose frame rate, and color space Sony S-log or s-log2 f65.

From here you can create proxy format for the main image sequence, or render to a new intermediate like Cineform or XAVC-intra.

Rendering to XAVC-intra gives a file 10-bit 422 image:

General
Complete name : C:\Users\Aaron\Desktop\avc-intra-test.MXF
Format : MXF
Format version : 1.3
Format profile : OP-1a
Format settings : Closed / Complete
File size : 3.27 MiB
Duration : 83 ms
Overall bit rate : 330 Mb/s
Encoded date : 2017-10-20 12:06:18.000
Writing application : SONY Vegas 13.0.0.453
Writing library : Sony MXF Development Kit (Win32) 4.8.0.113.1

Video
ID : 2
Format : AVC
Format/Info : Advanced Video Codec
Format profile : High 4:2:2 Intra@L5.1
Format settings, CABAC : No
Format settings, GOP : N=1
Format settings, wrapping mode : Frame
Codec ID : 0D01030102106001-0401020201323001
Duration : 83 ms
Maximum bit rate : 240 Mb/s
Width : 4 096 pixels
Height : 2 160 pixels
Display aspect ratio : 1.896
Frame rate : 23.976 (24000/1001) FPS
Standard : Component
Color space : YUV
Chroma subsampling : 4:2:2
Bit depth : 10 bits
Scan type : Progressive
Color range : Limited
Color primaries : BT.709
Transfer characteristics : BT.709
Matrix coefficients : BT.709

[Aaron Star]

It is not uncommon for 2-4k display formats to separate audio and video

MPEG-DASH uses a standalone audio track and varies the video bandwidth.

HEVC 4K DVD more than likely uses a file format that allows for multiple tracks for 5.1 and alternate sound tracks.

You may have to figure out what your playback source can handle, then render audio tracks to the correct channels in a multi channel capable container.

[Aaron Star]

I would post a few files in a gdrive or dropbox share and see if others in the forum can help you figure this out.

Is there an option to convert from RAW to EXR, or 16-bit BMP?

I only have VP13 and am able to process .dpx files as an imported image sequence from an F35.

Here is the media info on the 2 different formats of my files.

Format : DPX
Format version : Version 2.0
File size : 11.9 MiB

Image
Format : DPX
Format version : Version 2.0
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Color space : RGB
Bit depth : 16 bits
Compression mode : Lossless
Stream size : 11.9 MiB (100%)
Color primaries : BT.709
Transfer characteristics : BT.709
Frame rate : 24.000

And these from a film scan.

Format : DPX
Format version : Version 1.0
File size : 190 MiB
Writing library : TCS Scan V1.0

Video
Format : DPX
Format version : Version 1.0
Width : 1 920 pixels
Height : 1 080 pixels
Display aspect ratio : 16:9
Color space : RGB
Bit depth : 10 bits
Scan type : Progressive
Compression mode : Lossless
Stream size : 190 MiB (100%)
Writing library : TCS Scan V1.0
Transfer characteristics : Printing density

[Aaron Star]

You hardware specs are really low for so much decompression overhead on your source footage. There are reasons why the i5 is not branded an i7 or i9.

Like the CPUs, there are different versions of the NVENC that you are looking at Vegas to take advantage of. The 680 was a mid tier gaming purchase in the 1st place. https://en.wikipedia.org/wiki/Nvidia_NVENC

I understand your argument if VP13 can edit those formats, why is VP15 struggling. With VP15 it sounds like vegas is attempting to use NVENC hardware for both encode(render) and decode(timeline.) This is a dramatic shift in from the way VP13 handled timeline footage. more than likely the 680 is over loaded with tasks, or the software is just not optimized for that generation of hardware and drivers. VP15 was most likely tested with the latest gear and not that heavily tested with legacy gear.

I would read some of the many posts on optimizing your pc for vegas. Also look up the VP15 minimum hardware for 4K and then improve on that by double if you can.

[Aaron Star]

maybe list details of your new hardware and media workflow?

[Aaron Star]

Which Blackmagic devices and software driver version are you using?

Have you tried capturing with the Blackmagic capture application that installs with the driver? Does that application drop frames as well?

What are your system specs?

I would not use the Vegas Capture tool. I would use the Blackmagic utility for capture, then edit the captured footage with vegas.

[Aaron Star]

Bluetooth headsets should work just any other listening device in Windows. You PC/laptop obviously needs to have bluetooth abilities at the same level your headset supports (for example Boothtooth v2.0-5 for audio streaming. If your headset works in windows apps like media player, your head set should work listening to Vegas playback.

What the others are saying about sound quality is another issue, as BT audio does not use your sound cards SN qualities. The media is compressed and sent to your headphones and played back. Granted the compression is good, but still limited compared to a good set of hardwired cans.

If you use your sound card, make sure you are using the correct audio port with the head phone amp.

[Aaron Star]

The technology sounds good.

The problem I have had is the LG drives that work it fail to last more than 100 burned discs. I used to burn 100 discs at a time across different DVD drive manufacturers, and the LGs would always fail. So good luck with that drive being operational in 20 years. If the media plays in any device, then you only have to have to worry about the truth in the claim, and there being a drive around that will read it in 20 years.

Optical has been around as long as HDD, but there are optical formats that can no longer be read by a modern system. But a 10 MB IBM AT HDD could still be read today with the right connecting cables (if it still worked.)

I think a mirrored external HDD would be better and cheaper. Even if the USB standard goes away, you can alway disassemble the enclosure and get an adapter to directly interface the HDD. There are newer file systems like REFS that continually check for bad blocks and help with bit rot. But you do need to leave REFS online in order for it work. So a pair of 10GB RED drives in REFS mirror for near term archive storage, and mirrored 10TB shelf copy or NAS separate from the main system would be best. Then migrate every 5 years to the latest tech via network.