MJPEG 60p at 530Mbps isn't gonna work. Not if you want to preview it in realtime.

Set aside the time to make a 30p Proxy Render first. You can do this in Vegas.

--or--

My preference is to make an intermediate ProRes 422 file in Shutter Encoder, for a couple of pretty good reasons.

Those are the go-to options for your footage.

For more specific peer assistance, post the MediaInfo and Vegas File Properties.

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

Welcome to the discussion, and please drop back in and share your solution with us.

I think you didn't understand.... Every movie files in 1080p are working TILL meets movie with 4K, after that next 1080p movie files stopped working. Why? This is not normal. Another try.... See on a screen below. I will try to explain this anomaly agian.

 

MJPEG 60p at 530Mbps isn't gonna work. Not if you want to preview it in realtime.
 

But why? It works ewerywhere beyond Vegas. If 1080p clips meets 4K clip, the rest of 1080p clips will glitch.

Do you have QT installed and activated in Preferences/Deprecated Features?

Yes, I have all the time enabled a QuickTime PlugIn

Yes, we understand. @EricLNZ and I have about 40 years of combined technical experience with the Vegas product.

I can't answer your 'but why' question here because their is a 50 year evolution of video technology and licensing agreements behind it. But, to use Quicktime in Windows you are like a very big cat trying to jump through a very small hoop, called 32-bit architecture, going back to 1996 or so . . .

Every movie files in 1080p are working TILL meets movie with 4K, after that next 1080p movie files stopped working. 

Yes, of course. By that time, your computer's memory buffers are completely full of decoded interframe-compressed files, and have spilled over into virtual memory, called your hard disk scratch drive, which is fully 10x slower to seek and access than your system RAM, and the whole works is gummed up from that point forward, until you clear the system cache.

Another old-school option, if you are reluctant to do a proxy or prerender, is to break your project into shorter chunks, and combine them in a "nested" project later. That is an advanced skill that should be learnt after you have tried the options suggested to you, and your immediate production needs are satisfied.

And once you have a product, a good place to start your next level of learning is in these areas: https://www.vegascreativesoftware.info/us/forum/got-questions-consult-the-tutorials-first-please--120282/

https://www.vegascreativesoftware.info/us/forum/speaking-good-video-a-beginner-s-guide--104463/

Again, welcome to the discussions. Let's get your immediate problem fixed by one of the methods being offered, and tackle the learning curve questions later. We're not going anywhere ;?)

Could you share a sample file for testing?

Which build of 21 are you using?

Which build of 21 are you using?

Build 300 according to @Vegas21_user's signature. If that's still correct an update to Build 315 is recommended plus a "factory reset" https://www.vegascreativesoftware.info/us/forum/faq-how-can-i-reset-vegas-pro-to-default-settings--104646/

I'd personally go back to 208 but feel free to test 315 and see if it works for this purpose.

@Vegas21_user I use 4k cameras in my shoots but usually also deploy one or more remote controlled hd ptz cameras. I always set the project to 4k in that case. And have never had any issues in any version of Vegas. Only issue I encountered was with hd cameras that only shoot interlace. Need to activate the filter to reduce deinterlace flicker in clip properties.

I can't change the build because in newer builds the program stops working even more. You have already solved the problem with non-working files on this forum. If I change to a different build, these problems START AGAIN: https://www.vegascreativesoftware.info/us/forum/vegas-pro-21-build-300-mov-avc-pcm-files-black-preview--145365/

I will not engage in any nesting of designs. This is not a solution. The software must run smoothly. I won't use any tricks. The program should work.

I don't go back to 1996, I have a popular camera and I use it. Canon 5D Mark IV.
I would like to remind you that only Vegas always has problems, other programs do not have errors.

So what should I do to make everything work?

 

Could you share a sample file for testing?

There is nothing wrong with files.
1080p: https://we.tl/t-X0CEMPrCOP
4K: https://mab.to/t/TWBJpEvexsb/eu1

@Vegas21_user Hi, why put the two files on different sharing sites?, 'We' wants me to log in, that's not too much of a problem, I've done it before & I've never heard of MyAirBridge. Can you put both files on Google Drive?

What? Are you sure? You don't have to have account to be able to download files from WeTransfer and MyAirBridge too.

I don’t wish to malign your camera, but I see strobing and flashing in the file you provided in various applications including my iPad.

This is true even after conversion to other formats in Shutter Encoder.
I refuse to load Quicktime on my Windows systems.

This might be interesting: https://www.vegascreativesoftware.info/us/forum/media-defects-effects-on-players-and-vegas-pro--123986/

Both files give no problems with my VP21 Build 315. Interestingly on my pc both are decoded with "mxcompoundplug.dll" so my earlier suggestion that Quicktime was needed for the 4K was incorrect.

I will not engage in any nesting of designs. This is not a solution. The software must run smoothly. I won't use any tricks. The program should work.

 

There is nothing wrong with files.
1080p: https://we.tl/t-X0CEMPrCOP
4K: https://mab.to/t/TWBJpEvexsb/eu1

I have VP21b315 and VP22b122 but don't see the glitches with only putting your 1080p file before and after the 4K, not multiple different 1080P files or the single 1080P file repeated. That sort of distortion was more characteristic of build 300 but build 315 still is buggy as you mention.

The more disappointing thing I notice is how poorly the motion jpg plays back in VP22, starts at 14fps goes down to 4.5fps using about 30% CPU, on Resolve it plays smoothly using 16% CPU, no frame drops even at up to 16X playback speed (480fps) and uses 30% CPU. The problem is Vegas is using the new decoder for this, but unlike other formats that saw performance improvements that match Resolve playback this remains poor.

I have a popular camera and I use it. Canon 5D Mark IV.

That is by far one of the hardest acquisition codecs in existence to decode in Windows. The files are very complex, and the Quicktime architecture in Windows is a lot older than your camera model.

My impression is that users of Apple iMac machines may have fewer problems with your files than we on Windows, because they use up-to-date 32 bit application architecture, which can handle  4,294,967,296 calculations per second, rather than 1024 in Windows. I "think" I have that math right.

I encourage you to file a problem report at

https://www.vegascreativesoftware.info/us/support/options/

Vegas system engineers often have a way of addressing issues that your peers cannot, even with our 150 years of combined experience.

Have you updated your Ryzen Video Drivers by clicking the link in your Vegas Help Menu?

Vegas Creative Software comes with a learning curve, I hope you will accept the challenge to grow along with it.

Best regards,

I have a popular camera and I use it. Canon 5D Mark IV.

That is by far one of the hardest acquisition codecs in existence to decode in Windows. The files are very complex, and the Quicktime architecture in Windows is a lot older than your camera model.

The 4k file provided comes from this camera (according to its Media Info) and as mentioned in my earlier post it opens, for me, with "mxcompoundplug.dll". VP21 does not involve Quicktime. I don't know about the Quicktime architecture in Windows.

I have a popular camera and I use it. Canon 5D Mark IV.

That is by far one of the hardest acquisition codecs in existence to decode in Windows. The files are very complex, and the Quicktime architecture in Windows is a lot older than your camera model.

@mark-y Vegas is using the new decoder that makes other formats very fast, but not for motion jpeg.

I put his clip on timeline and duplicate it, so it's almost 30seconds and GPU encode to HEVC

Vegas 4K project/encode 52seconds, 1080P project/encode 44seconds

Resolve 4K project/encode 8 seconds, 1080P project/encode 4 seconds

It looks like a Vegas decoding problem.

I have never felt the need to do video edits or screen captures on my iPad, but I did it this time out of curiosity.

@john_dennis The native Windows 10 editor plays it back fine too but I found even playing back at 2x speed caused playback to pause/start so wouldn't be able to playback 60fps version of this media.

Looks like Motion Jpeg is one of 4 choices listed in the Canon 5D Mark IV manual and the worst of all worlds...

@Vegas21_user: suggest you change your camera settings and transcode anything you already shot with Shutter Encoder. I would go with the All-I Mov camera setting for the easiest editing if it yields sufficient recording time. Mov clips often allow pcm audio on my Canons. It says that Mp4 gives the most recording time with the greatest compatibility but the audio format is typically compressed.

All 1080p clips work for me until a 4K clip shows up. Since the 4K format appeared, subsequent files stopped working (the next files are already in 1080p format). 


Look what happen in Vegas:

OF COURSE IN VEGAS NUMBER 13 THIS PROBLEM DOES NOT OCCUR. ONLY THE CREATORS OF VEGAS 21 can't do it.. Still the same, it's a comedy. I can't have ANY project finally made without bug, errors, problems etc... It's amazing how much this software is WASTING my time while working on it.

There seems to be a lot of decoding errors. Testing that with VP22 b194 as it will be launched today, I do not see any decoding errors.

And - that has nothing to do with the fact that you mix HD with DCI-4K. An upgrde could help.

Just tried the 4K: https://mab.to/t/TWBJpEvexsb/eu1 mjpeg clip and it does play without apparent errors on vp22b194. But not very well... between 6 and 12 fps on my laptop. In contrast, a 4k avc mp4 59.94p clip from an xf605 plays at full frame rate.