So i tried enabling experimental HEVC and that made the one media file that was the worst work okay. But the other one that ran good before now craps the bed... I can really use some help.

Support tickets are not working. Been trying to open a support ticket for weeks and they seem not to work.

@joshua-noesser

Well, it is a GoPro, which are notorious for their excessive compression schemes. Plus, add the fact that you are also recording at 5.3K, 60p (59.940), this just increases the problem. I have used GoPro's since the Hero 3 Black Plus (3+, 5, 6, 7, 9, 10, 11, and 12 - Skipped 8 because of the lens filter crap). I always shoot during my daily walks, approximately 1 Hour 15 Minutes long, with the Highest Resolution for the particular model (though mostly use the 11 & 12 Black now), at 30p (29.970), recording high bit rate, and flat/log. Once I get back and download the footage, I open Shutter Encoder, and transcode the footage to ProRes 422 LT. Same if I record at 60p. I don't have an Intel processor with an integrated gpu (iGPU), and my computer specs are in my signature.

The ProRes files work fantastic, even back through the original ThreadRipper (1920x & 1950x), as well as the Intel X79 & X59 platforms, and the various iterations of either VEGAS Pro or VEGAS Movie Studio (transcoded them to GrassValley HQX though).

And, as I also have the Canon R6, R7, and R6 MkII, with all recording video at 4k 24/30/60p in CLOG3 - Cinema Gamut - IPB; the files are 4:2:2 10-Bit, so without that Intel iGPU for decoding, transcoding to ProRes 422 is a no-brainer. As an example of how long it takes to transcode CLOG3 files with Shutter Encoder, I returned from a trip to Iowa visiting my Uncle and Cousin, with 82 clips of 121GB - it took about an hour to transcode them all to ProRes 422 - approximately 407GB - so I went and did some shopping while the computer was cruising along.

Just so there is no confusion amongst people on the forum as well, I do have DaVince Resolve (Free - 18.6), and do the same procedure. Heck, the Canon files won't even display the video if I try to use the native files from any of those cameras.

Basic moral of the story: Buy a large capacity Hard Drive or two (or more), and transcode.

Mike "The Chief" O'Sullivan

@joshua-noesser

Well, it is a GoPro, which are notorious for their excessive compression schemes. Plus, add the fact that you are also recording at 5.3K, 60p (59.940), this just increases the problem. I have used GoPro's since the Hero 3 Black Plus (3+, 5, 6, 7, 9, 10, 11, and 12 - Skipped 8 because of the lens filter crap). I always shoot during my daily walks, approximately 1 Hour 15 Minutes long, with the Highest Resolution for the particular model (though mostly use the 11 & 12 Black now), at 30p (29.970), recording high bit rate, and flat/log. Once I get back and download the footage, I open Shutter Encoder, and transcode the footage to ProRes 422 LT. Same if I record at 60p. I don't have an Intel processor with an integrated gpu (iGPU), and my computer specs are in my signature.

The ProRes files work fantastic, even back through the original ThreadRipper (1920x & 1950x), as well as the Intel X79 & X59 platforms, and the various iterations of either VEGAS Pro or VEGAS Movie Studio (transcoded them to GrassValley HQX though).

And, as I also have the Canon R6, R7, and R6 MkII, with all recording video at 4k 24/30/60p in CLOG3 - Cinema Gamut - IPB; the files are 4:2:2 10-Bit, so without that Intel iGPU for decoding, transcoding to ProRes 422 is a no-brainer. As an example of how long it takes to transcode CLOG3 files with Shutter Encoder, I returned from a trip to Iowa visiting my Uncle and Cousin, with 82 clips of 121GB - it took about an hour to transcode them all to ProRes 422 - approximately 407GB - so I went and did some shopping while the computer was cruising along.

Just so there is no confusion amongst people on the forum as well, I do have DaVince Resolve (Free - 18.6), and do the same procedure. Heck, the Canon files won't even display the video if I try to use the native files from any of those cameras.

Basic moral of the story: Buy a large capacity Hard Drive or two (or more), and transcode.

Mike "The Chief" O'Sullivan

Before this update, the files ran fine. I skipped 300 and 314. But with this release, it is also my other cameras, not just the GoPro. The other camera is a GH6 recording 4k 60fps 100 Mbps 4:2:2, which I am also having issues with now. This one has never had a problem with this software. I turned on experimental HEVC and the go pro footage was amazing, the trimming worked great on all cameras, but the software would not play the GH6's video in the preview and the whole thing would just fall apart. I can check out the shutter encoder, never heard of it. But would just like for the software to work like how it used to.

Adding more info, and can't add to the above

But while the software is doing its first start-up, I have noticed that this bug doesn't exist. It only seems to be a problem after everything is loaded and the software is idle.

Here is a video of the issue with trimming lag. The more I play with it, the more I feel like it has something to do with the thumbnails, like the original release has issues with on 21.

What version were you using? You said you skipped 300 and 314- did you also skip 21.315? 22.93 is a refined version of 21.315 in my opinion.

The old versions like 21.208 used so4compound decoder for HEVC (and benefited from Intel QSV decoding). You can renable that with "experimental HEVC decoding" in preferences/ file io.

With NVIDIA in VP 22.93 I recommend keeping preferences, file io on defaults. NVDEC does the decoding using MxCompound. If GoPro is the only format causing issues consider converting it to a less compressed format (ShutterEncoder can give you 10 bit AVC or HEVC with shorter GOPs- set it to your framerate in advanced settings).

The downside of going to all NVDEC is that it's not capable of decoding 10-bit 422 HEVC if that's what your Panasonic is set to. Only Intel QSV can do that. I'd set the Panasonics to shoot 10-bit 420 if that's an option and then all should work well together.

Also, could you add your hardware to your signature for easy reference?

What version were you using? You said you skipped 300 and 314- did you also skip 21.315? 22.93 is a refined version of 21.315 in my opinion.

The old versions like 21.208 used so4compound decoder for HEVC (and benefited from Intel QSV decoding). You can renable that with "experimental HEVC decoding" in preferences/ file io.

With NVIDIA in VP 22.93 I recommend keeping preferences, file io on defaults. NVDEC does the decoding using MxCompound. If GoPro is the only format causing issues consider converting it to a less compressed format (ShutterEncoder can give you 10 bit AVC or HEVC with shorter GOPs- set it to your framerate in advanced settings).

The downside of going to all NVDEC is that it's not capable of decoding 10-bit 422 HEVC if that's what your Panasonic is set to. Only Intel QSV can do that. I'd set the Panasonics to shoot 10-bit 420 if that's an option and then all should work well together.

Also, could you add your hardware to your signature for easy reference?

Thank you Roger for resonding

Currently on 21.315

What are your thoughts on 22? Is it worth upgrading to? I don't really want to upgrade unless it fixes my problems. I just want the video clips to work like they used to. Smooth. Now I have to create a proxy for all footage because randomly, some footage will be all glitchy, then after a restart, it will be fine but something else will be glitchy. Not sure what is going on Plus i have this lag issue that is driving me insane. All these problems were nowhere like this before. I only had a small lag issue on one previous patch. But it was nothing like this.

I tried turning on the experimental HEVC decoding, which did great for the goPro footage, but the other footage from the GH6 was horrible after that. It would be great if the software could determine what was best per camera.

Thanks for the idea

It's your GoPro footage, which is optimized for shooting, and about the worst thing in existence for editing.

At 60p and 120Mbps, editing smoothly is kind of a crapshoot with loaded dice.

The solution for many people is simple: Create a Video Proxy in Vegas for editing, and do your render to AVC, not HEVC.

Due to the nature of your source footage, it may not be any better in Vegas 22: we're still a ways off from having the hardware codecs and speed to handle it seamlessly.

What version were you using? You said you skipped 300 and 314- did you also skip 21.315? 22.93 is a refined version of 21.315 in my opinion.

The old versions like 21.208 used so4compound decoder for HEVC (and benefited from Intel QSV decoding). You can renable that with "experimental HEVC decoding" in preferences/ file io.

With NVIDIA in VP 22.93 I recommend keeping preferences, file io on defaults. NVDEC does the decoding using MxCompound. If GoPro is the only format causing issues consider converting it to a less compressed format (ShutterEncoder can give you 10 bit AVC or HEVC with shorter GOPs- set it to your framerate in advanced settings).

The downside of going to all NVDEC is that it's not capable of decoding 10-bit 422 HEVC if that's what your Panasonic is set to. Only Intel QSV can do that. I'd set the Panasonics to shoot 10-bit 420 if that's an option and then all should work well together.

Also, could you add your hardware to your signature for easy reference?

Thank you Roger for resonding

Currently on 21.315

 

What are your thoughts on 22? Is it worth upgrading to? I don't really want to upgrade unless it fixes my problems. I just want the video clips to work like they used to. Smooth. Now I have to create a proxy for all footage because randomly, some footage will be all glitchy, then after a restart, it will be fine but something else will be glitchy. Not sure what is going on Plus i have this lag issue that is driving me insane. All these problems were nowhere like this before. I only had a small lag issue on one previous patch. But it was nothing like this.

I tried turning on the experimental HEVC decoding, which did great for the goPro footage, but the other footage from the GH6 was horrible after that. It would be great if the software could determine what was best per camera.

 

Thanks for the idea

For my own work I am using VP 21.208 as it doesn't have any decoding glitches. If it can't play back files at full speed I make proxy files in VEGAS.

I think 22 holds a lot of promise (with experimental HEVC off) and would suggest trying the trial of it when the first update patch is released as there are some unfortunate bugs like a memory leak, and still some decoding errors with NVDEC.

The other option is to batch convert the troublesome GoPro files- I use ShutterEncoder for that (free). https://www.shutterencoder.com/

What version were you using? You said you skipped 300 and 314- did you also skip 21.315? 22.93 is a refined version of 21.315 in my opinion.

The old versions like 21.208 used so4compound decoder for HEVC (and benefited from Intel QSV decoding). You can renable that with "experimental HEVC decoding" in preferences/ file io.

With NVIDIA in VP 22.93 I recommend keeping preferences, file io on defaults. NVDEC does the decoding using MxCompound. If GoPro is the only format causing issues consider converting it to a less compressed format (ShutterEncoder can give you 10 bit AVC or HEVC with shorter GOPs- set it to your framerate in advanced settings).

The downside of going to all NVDEC is that it's not capable of decoding 10-bit 422 HEVC if that's what your Panasonic is set to. Only Intel QSV can do that. I'd set the Panasonics to shoot 10-bit 420 if that's an option and then all should work well together.

Also, could you add your hardware to your signature for easy reference?

Thank you Roger for resonding

Currently on 21.315

 

What are your thoughts on 22? Is it worth upgrading to? I don't really want to upgrade unless it fixes my problems. I just want the video clips to work like they used to. Smooth. Now I have to create a proxy for all footage because randomly, some footage will be all glitchy, then after a restart, it will be fine but something else will be glitchy. Not sure what is going on Plus i have this lag issue that is driving me insane. All these problems were nowhere like this before. I only had a small lag issue on one previous patch. But it was nothing like this.

I tried turning on the experimental HEVC decoding, which did great for the goPro footage, but the other footage from the GH6 was horrible after that. It would be great if the software could determine what was best per camera.

 

Thanks for the idea

For my own work I am using VP 21.208 as it doesn't have any decoding glitches. If it can't play back files at full speed I make proxy files in VEGAS.

I think 22 holds a lot of promise (with experimental HEVC off) and would suggest trying the trial of it when the first update patch is released as there are some unfortunate bugs like a memory leak, and still some decoding errors with NVDEC.

The other option is to batch convert the troublesome GoPro files- I use ShutterEncoder for that (free). https://www.shutterencoder.com/

okay, i will try going back to 208. That was the one that seemed to work the best for me too.

@joshua-noesser

Well, it is a GoPro, which are notorious for their excessive compression schemes. Plus, add the fact that you are also recording at 5.3K, 60p (59.940), this just increases the problem. I have used GoPro's since the Hero 3 Black Plus

@Chief24 Vegas Pro 21 and 22 playback GoPro HEVC better than AVC. Your signature says you're on Vegas Pro 20, and that would be your experience with that version but Vegas was notoriously bad at playing back HEVC.

Here are some figures for GoPro from my use with VP21 and VP22 with new GPU decoder.

• 4K AVC 8bit - 2160P project - 210fps - 66watts GPU power
• 4K HEVC 8bit - 2160P project - 258fps - 66watts GPU power
• 5K HEVC 10bit - 2988P project - 252fps - 86watts GPU power

*fps figure is maximum playback without any drop in frames as reported by Vegas in display information.

CPU us is low on all. There are still some bugs with new decoder including very poor concurrent playback of media for both AVC and HEVC versions, but that's merely a bug and will be fixed in time.

@UltraVista

Thanks, you prompted me to update my profile for versions of VEGAS Pro I use.

Addtionally, my comment to @joshua-noesser was more for his issue of "trimming" in the timeline, or my guess is his ability to "edit" the footage (note - GoPro), and not "Playback". So, I do still stand by my previous comment above concerning the use of ProRes 422 LT. Possibility of better performance now with VEGAS Pro 21/22 and the newer encoding/decoding engine, may be happening. But, since I am currently working on projects using VEGAS Pro 20 (411), I am not going to take any chances with corrupted Project Files and/or Media.

The engine in VEGAS Pro 20 was a heck of a lot better than previous versions, but using compressed formats to try and edit was still a pain, so the transcoding. Plus, since I also typically use Canon CLOG3 files in the project as well, not having an Intel CPU with the iGPU for HEVC decoding of 4:2:2 10-Bit, again lends to transcoded media.

But again, thanks for the "kick in the rear" to update my Profile page (Done!)

@Chief24 Here's a demo of HEVC 5.3K 10bit playback in 4K project. It's 24fps media conformed to 60fps, then played back at 2x in Vegas. Because it's 10bit project is set to 32bit FP color

The fade shows the concurrent playback bug, this isn't a result of the combined decode speed being too high, it will also happen at 24fps played back at 1x. When I quickly cut up with clip I didn't have any lag or slowdown like OP but I do know what he's talking about with the redrawing, it can be so bad that the entire section of timeline disappears and there is only a border outline, but I don't recall it correlating to lag, although I do like his conjecture, the resources Vegas is using to rebuild the timeline is taken away his editing.

So you do have VP22 then, and your experience is gopro 4K HEVC 8bit does playback worse compared to AVC 4K 8bit or is your comparison between 10bit HEVC and 8bit AVC. If you haven't given it a try yet I'd be interested in your perspective having so much experience with gopro,

The really big negative working in 32bit color is that although playback and decoding doesn't have the slow down of older Vegas's the full render engine through to the encoder has not been updated, so 250fps playback on timeline doesn't equal a very fast encoding experience it's 6fps or similar.

@UltraVista

I am not concerned with playback speed on the timeline. I am concerned with editing/trimming on the timeline. If I want to playback my files, i just open up the folder where my GoPro footage is (and even the CLOG3 from my Canons'), right click on the media file, and open it with MPC-HC (64-bit) that is installed with Happy Otter Scripts.

As mentioned previously, currently have projects ongoing using VEGAS Pro 20 (411), so anything to do with Versions 21 (315) or 22 (93), will have to wait for any type of testing or project work.

Back when I got my original GoPro Hero 3 Black Plus, that "4K" could only shoot in that weird 14.945 fps crap, was super compressed, but you were better off using the old GoPro Studio and "convert/transcode" to the old Cineform .avi container provided. Heck, as I moved up to the 5 Black, and Studio got butchered by GoPro, than the Cineform was sourced out, I purchased the MagicYUV codec for .avi container, and happily used that transcoding footage within VEGAS Movie Studio at the time, or GrassValley HQX. And when I finally moved up and started using VEGAS Pro more often, originally was using the "Magix Intermediate" VEGAS was implementing at the time until they got licensed for proper ProRes, which I use now, within Shutter Encoder.

When I do transcode the GoPro Hero 9, 10, 11, or 12 Blacks', I leave the resolution at either 5K or 5.3K, and let VEGAS Pro do the resizing to 4K within project settings, or 1080 if I am doing a Blu-Ray. Frame Rate is typically at 29.970 for most projects, including my Canons', but if I know I am doing any discs, I'll shoot in 23.976.

As far as whether it is 8-Bit or 10-Bit, depends on which camera has the most footage, though since the GoPro Hero 9 and 10 Black are getting used less, and the Canons' are 10-Bit, the project gets set for that. For which "codec", all of my cameras use HEVC (H.265). Though, that old Hero 5 is AVC, not used hardly (makes a great camera at camp when sighting in rifles), and the Hero 6 is typically AVC unless you shoot in the few formats it forces you into HEVC. The Hero 7 and up, I have set for HEVC. The Canon R6, R6 MkII, and R7 are all set for using CLOG3/Cinema Gamut/IPB. Since the R6 MkII and R7 have the video Custom settings, they each have one for 24p, 30p, and 60p (23.976, 29.970, and 59.940 respectively). Have to manually set on the original R6.

And for the Hero 12 Black, I also have that using the GoPro Log setting, and I do use the LUT provided by GoPro. I will say this, that sucker needs a lot of "tweaking", more so than using Canon CLOG3 on a timeline!

So, like the "playback" of files, I really am not concerned about how fast it can play. Scrubbing the timeline and moving quickly about for editing, YES! So I do not mind the time it takes to Transcode my files. Just like when it comes to rendering, typically use the Non-VCE (AMD gpu render) setting, increase the AVG/Max Bit Rates, hit render, then go do something like laundry, cook, mow the lawn, go shopping, etc.

@UltraVista

I am not concerned with playback speed on the timeline. I am concerned with editing/trimming on the timeline. If I want to playback my files, i just open up the folder where my GoPro footage is (and even the CLOG3 from my Canons'), right click on the media file, and open it with MPC-HC (64-bit) that is installed with Happy Otter Scripts.

@Chief24 I do know what you mean, it's also a pet hate of mine when people will screencap them playing a video file in Vegas from the beginning and exclaiming, no problems here, must be your hardware. Vegas isn't a player it's an editor, also Vegas pre-caches so such a test may not even be showing actual decoding playback.

What I do is remove sections of test video and playback a different clip before the screencap, the one you see to the right then while playing move playhead to the test file, that means it's decoding in real time, and everytime it meets an edit point it risks lagging, the faster the playback the higher that chance, but it doesn't lag, not even at 120fps (except for the fade transition which is a bug)

What I'm showing is HEVC is very editable in Vegas Pro22, and there's been a huge improvment in playback, and the problems I see with HEVC are the same ones I see with AVC. The GoPro's have a GOP of 24 which is also a factor in why they edit so well, some of the Sony formats use a GOP as high as 60 and won't edit as well.

What version were you using? You said you skipped 300 and 314- did you also skip 21.315? 22.93 is a refined version of 21.315 in my opinion.

The old versions like 21.208 used so4compound decoder for HEVC (and benefited from Intel QSV decoding). You can renable that with "experimental HEVC decoding" in preferences/ file io.

With NVIDIA in VP 22.93 I recommend keeping preferences, file io on defaults. NVDEC does the decoding using MxCompound. If GoPro is the only format causing issues consider converting it to a less compressed format (ShutterEncoder can give you 10 bit AVC or HEVC with shorter GOPs- set it to your framerate in advanced settings).

The downside of going to all NVDEC is that it's not capable of decoding 10-bit 422 HEVC if that's what your Panasonic is set to. Only Intel QSV can do that. I'd set the Panasonics to shoot 10-bit 420 if that's an option and then all should work well together.

Also, could you add your hardware to your signature for easy reference?

Thank you Roger for resonding

Currently on 21.315

 

What are your thoughts on 22? Is it worth upgrading to? I don't really want to upgrade unless it fixes my problems. I just want the video clips to work like they used to. Smooth. Now I have to create a proxy for all footage because randomly, some footage will be all glitchy, then after a restart, it will be fine but something else will be glitchy. Not sure what is going on Plus i have this lag issue that is driving me insane. All these problems were nowhere like this before. I only had a small lag issue on one previous patch. But it was nothing like this.

I tried turning on the experimental HEVC decoding, which did great for the goPro footage, but the other footage from the GH6 was horrible after that. It would be great if the software could determine what was best per camera.

 

Thanks for the idea

For my own work I am using VP 21.208 as it doesn't have any decoding glitches. If it can't play back files at full speed I make proxy files in VEGAS.

I think 22 holds a lot of promise (with experimental HEVC off) and would suggest trying the trial of it when the first update patch is released as there are some unfortunate bugs like a memory leak, and still some decoding errors with NVDEC.

The other option is to batch convert the troublesome GoPro files- I use ShutterEncoder for that (free). https://www.shutterencoder.com/

Hey Roger, do you know of a way to convert a version 315 format video save to version 208 so I can open it? or do I just have to restart? I am hoping you have some magic up your sleeves.

@UltraVista

Thanks, you prompted me to update my profile for versions of VEGAS Pro I use.

Addtionally, my comment to @joshua-noesser was more for his issue of "trimming" in the timeline, or my guess is his ability to "edit" the footage (note - GoPro), and not "Playback". So, I do still stand by my previous comment above concerning the use of ProRes 422 LT. Possibility of better performance now with VEGAS Pro 21/22 and the newer encoding/decoding engine, may be happening. But, since I am currently working on projects using VEGAS Pro 20 (411), I am not going to take any chances with corrupted Project Files and/or Media.

The engine in VEGAS Pro 20 was a heck of a lot better than previous versions, but using compressed formats to try and edit was still a pain, so the transcoding. Plus, since I also typically use Canon CLOG3 files in the project as well, not having an Intel CPU with the iGPU for HEVC decoding of 4:2:2 10-Bit, again lends to transcoded media.

But again, thanks for the "kick in the rear" to update my Profile page (Done!)

Thanks for the input, but what i found is I never had issues in older versions like you all are talking about. I would be able to run no proxy and have no lag when editing. The 315 version of 21 is a mess.

What version were you using? You said you skipped 300 and 314- did you also skip 21.315? 22.93 is a refined version of 21.315 in my opinion.

The old versions like 21.208 used so4compound decoder for HEVC (and benefited from Intel QSV decoding). You can renable that with "experimental HEVC decoding" in preferences/ file io.

With NVIDIA in VP 22.93 I recommend keeping preferences, file io on defaults. NVDEC does the decoding using MxCompound. If GoPro is the only format causing issues consider converting it to a less compressed format (ShutterEncoder can give you 10 bit AVC or HEVC with shorter GOPs- set it to your framerate in advanced settings).

The downside of going to all NVDEC is that it's not capable of decoding 10-bit 422 HEVC if that's what your Panasonic is set to. Only Intel QSV can do that. I'd set the Panasonics to shoot 10-bit 420 if that's an option and then all should work well together.

Also, could you add your hardware to your signature for easy reference?

Thank you Roger for resonding

Currently on 21.315

 

What are your thoughts on 22? Is it worth upgrading to? I don't really want to upgrade unless it fixes my problems. I just want the video clips to work like they used to. Smooth. Now I have to create a proxy for all footage because randomly, some footage will be all glitchy, then after a restart, it will be fine but something else will be glitchy. Not sure what is going on Plus i have this lag issue that is driving me insane. All these problems were nowhere like this before. I only had a small lag issue on one previous patch. But it was nothing like this.

I tried turning on the experimental HEVC decoding, which did great for the goPro footage, but the other footage from the GH6 was horrible after that. It would be great if the software could determine what was best per camera.

 

Thanks for the idea

For my own work I am using VP 21.208 as it doesn't have any decoding glitches. If it can't play back files at full speed I make proxy files in VEGAS.

I think 22 holds a lot of promise (with experimental HEVC off) and would suggest trying the trial of it when the first update patch is released as there are some unfortunate bugs like a memory leak, and still some decoding errors with NVDEC.

The other option is to batch convert the troublesome GoPro files- I use ShutterEncoder for that (free). https://www.shutterencoder.com/

Hey Roger, do you know of a way to convert a version 315 format video save to version 208 so I can open it? or do I just have to restart? I am hoping you have some magic up your sleeves.

@joshua-noesser I don't know a way to do that. If you still have 20 or 19 you can open that and 21.315 at the same tie and copy and paste the entire timeline into the older version. Then uninstall 315 and reinstall 208.

What version were you using? You said you skipped 300 and 314- did you also skip 21.315? 22.93 is a refined version of 21.315 in my opinion.

The old versions like 21.208 used so4compound decoder for HEVC (and benefited from Intel QSV decoding). You can renable that with "experimental HEVC decoding" in preferences/ file io.

With NVIDIA in VP 22.93 I recommend keeping preferences, file io on defaults. NVDEC does the decoding using MxCompound. If GoPro is the only format causing issues consider converting it to a less compressed format (ShutterEncoder can give you 10 bit AVC or HEVC with shorter GOPs- set it to your framerate in advanced settings).

The downside of going to all NVDEC is that it's not capable of decoding 10-bit 422 HEVC if that's what your Panasonic is set to. Only Intel QSV can do that. I'd set the Panasonics to shoot 10-bit 420 if that's an option and then all should work well together.

Also, could you add your hardware to your signature for easy reference?

Thank you Roger for resonding

Currently on 21.315

 

What are your thoughts on 22? Is it worth upgrading to? I don't really want to upgrade unless it fixes my problems. I just want the video clips to work like they used to. Smooth. Now I have to create a proxy for all footage because randomly, some footage will be all glitchy, then after a restart, it will be fine but something else will be glitchy. Not sure what is going on Plus i have this lag issue that is driving me insane. All these problems were nowhere like this before. I only had a small lag issue on one previous patch. But it was nothing like this.

I tried turning on the experimental HEVC decoding, which did great for the goPro footage, but the other footage from the GH6 was horrible after that. It would be great if the software could determine what was best per camera.

 

Thanks for the idea

For my own work I am using VP 21.208 as it doesn't have any decoding glitches. If it can't play back files at full speed I make proxy files in VEGAS.

I think 22 holds a lot of promise (with experimental HEVC off) and would suggest trying the trial of it when the first update patch is released as there are some unfortunate bugs like a memory leak, and still some decoding errors with NVDEC.

The other option is to batch convert the troublesome GoPro files- I use ShutterEncoder for that (free). https://www.shutterencoder.com/

Hey Roger, do you know of a way to convert a version 315 format video save to version 208 so I can open it? or do I just have to restart? I am hoping you have some magic up your sleeves.

@joshua-noesser I don't know a way to do that. If you still have 20 or 19 you can open that and 21.315 at the same tie and copy and paste the entire timeline into the older version. Then uninstall 315 and reinstall 208.

I will reinstall an older version and do that.

What version were you using? You said you skipped 300 and 314- did you also skip 21.315? 22.93 is a refined version of 21.315 in my opinion.

The old versions like 21.208 used so4compound decoder for HEVC (and benefited from Intel QSV decoding). You can renable that with "experimental HEVC decoding" in preferences/ file io.

With NVIDIA in VP 22.93 I recommend keeping preferences, file io on defaults. NVDEC does the decoding using MxCompound. If GoPro is the only format causing issues consider converting it to a less compressed format (ShutterEncoder can give you 10 bit AVC or HEVC with shorter GOPs- set it to your framerate in advanced settings).

The downside of going to all NVDEC is that it's not capable of decoding 10-bit 422 HEVC if that's what your Panasonic is set to. Only Intel QSV can do that. I'd set the Panasonics to shoot 10-bit 420 if that's an option and then all should work well together.

Also, could you add your hardware to your signature for easy reference?

Thank you Roger for resonding

Currently on 21.315

 

What are your thoughts on 22? Is it worth upgrading to? I don't really want to upgrade unless it fixes my problems. I just want the video clips to work like they used to. Smooth. Now I have to create a proxy for all footage because randomly, some footage will be all glitchy, then after a restart, it will be fine but something else will be glitchy. Not sure what is going on Plus i have this lag issue that is driving me insane. All these problems were nowhere like this before. I only had a small lag issue on one previous patch. But it was nothing like this.

I tried turning on the experimental HEVC decoding, which did great for the goPro footage, but the other footage from the GH6 was horrible after that. It would be great if the software could determine what was best per camera.

 

Thanks for the idea

For my own work I am using VP 21.208 as it doesn't have any decoding glitches. If it can't play back files at full speed I make proxy files in VEGAS.

I think 22 holds a lot of promise (with experimental HEVC off) and would suggest trying the trial of it when the first update patch is released as there are some unfortunate bugs like a memory leak, and still some decoding errors with NVDEC.

The other option is to batch convert the troublesome GoPro files- I use ShutterEncoder for that (free). https://www.shutterencoder.com/

Hey Roger,

I went back to 208, but I am getting a lot of crashes. Do you have any idea? Below is my settings.

I looked at my older notes and turned off everything GPU for 208 looked like. Unfortunately, when I did that, my renders were full of artifacts. 300 was more stable, but I was getting some weird lag. However, I seemed to have a workaround for the major issue, just not some small lag in some spots. If you don't have any idea, maybe I will try 300. Do you have the link to the downloads? I am struggling to find them right now.




 

i9-14800k

96GB Ram

4080 Nvidia

z790 aorus master x board
4x 20tb Raid 5 Internal Drives for video storage

2tb m2 990 for C drive.

@joshua-noesser wrote

Do you have the link to the downloads? I am struggling to find them right now.

https://www.vegascreativesoftware.info/us/forum/faq-where-can-i-download-vegas-pro-and-other-vegas-software--104782/

Hey Roger,

I went back to 208, but I am getting a lot of crashes. Do you have any idea? Below is my settings.

I looked at my older notes and turned off everything GPU for 208 looked like. Unfortunately, when I did that, my renders were full of artifacts. 300 was more stable, but I was getting some weird lag. However, I seemed to have a workaround for the major issue, just not some small lag in some spots. If you don't have any idea, maybe I will try 300. Do you have the link to the downloads? I am struggling to find them right now.




 

i9-14800k

96GB Ram

4080 Nvidia

z790 aorus master x board
4x 20tb Raid 5 Internal Drives for video storage

2tb m2 990 for C drive.

 

For VP 21.208 and older I would not use NVDEC. Select Intel QSV as the decoder in preferences file io and uncheck legacy AVC deocder.

I would not recommend build 300 given all the bugs it has compared with 314/315.

Your other settings seem fine.