I had to make a proxy to preview smoothly on my i5, as I have had to do with other 60fps GH5 / GH6 files.

Is there a non long GOP option or other formats with this camera you can try?

@serd

The playback at Best / Half was dismal on my five-year-old system with GPU decode enabled. RX480 doesn't offer much in the way of HEVC decode.

It was equally dismal with my CPU doing all the work.

Converting to Apple ProRes 422HQ was significantly better.

Building proxy played at full frame rate using Display Preview/Half, but took longer to render than ProRes 422HQ.

Building a 1080p Apple ProRes 422HQ file and replacing the HEVC GH6 file while editing played full frame rate smoothly at Best /Half.

@Former user yeah, whatever todd-b, You are a very funny and misguided one, who often also posts rude comments here and don't expect someone to say something about it. Not so it goes.

@Steve_Rhoden He has a legitimate complaint, GPU decoding doesn't work for this file with his system, and it's a Vegas bug. He compares Vegas playback with Premiere to illustrate. Telling him to go back to Premiere doesn't help with this Vegas problem that will affect many others

Sigh!!!

Every time when such topics sprout, struggles spread like wildfire.

I AM right, you ARE wrong, he IS an idiot......

I'll collect some time and write an intro with this title:
Know your HW, know VEGAS & its Way with Media

But don't know when.

@Steve_Rhoden All you've added to this post is aggression & petty personal name calling, if you can't take the backlash of making such an unnecessary initial comment then don't do it, & while you're talking about past comments of Todd & I, You're past comments leave a lot to be desired, i've noted on several occasions you've made similar aggressive, negative, bullying & sometimes personal comments, So don't YOU expect someone not to say something about it, !

Qwik Proxy (Happy Otter Scripts) worked like a gem. 40 seconds flat.

@Steve_Rhoden All you've added to this post is aggression & petty personal name calling, if you can't take the backlash of making such an unnecessary initial comment then don't do it, & while you're talking about past comments of Todd & I, You're past comments leave a lot to be desired, i've noted on several occasions you've made similar aggressive, negative, bullying & sometimes personal comments, So don't YOU expect someone not to say something about it, !

"Never overestimate your power to change others; never underestimate your power to change yourself."

Continuing on with the proxy theme:

Yes, using an external program like Qwik proxy (or Vegasaur, Shutter encoder, Davinci Resolve, any number of ffmpeg front ends) for generating proxies has a number of advantages over Vegas' "internal" proxy system:

1) Works with the trimmer!

2) Can add a "burn in" ( I like to see timecode, orig. resolution, and orig. frame rate)

3) doesn't make a .svp0 mess in your original file folder.

As suggested, Prores works well with Vegas, with the exception that Vegas doesn't read .mov timecode, which is why I prefer Grass valley .avi files.

Good luck!

As suggested, Prores works well with Vegas, with the exception that Vegas doesn't read .mov timecode, which is why I prefer Grass valley .avi files.

Good luck!

A quick question @Kinvermark
Which program are you using to create Grass valley .avi files for editing in Vegas?
Are you using Edius to do this?

p.s. Thanks for suggesting Shutter Encoder!
I've been out of the loop for a while and never heard of this tool before today. I just downloaded it and it works beautifully - it offers all the codecs I like to convert video into and converted very fast. Perfect 😊

@ Dr Zen Shutter Encoder is the Swiss Knife for every video editor and a must have. Beyond encoding to other codecs, it has dozens of other video tools which work fast and accurately. Once used, you wonder how you could do without before.

As suggested, Prores works well with Vegas, with the exception that Vegas doesn't read .mov timecode, which is why I prefer Grass valley .avi files.

Good luck!

A quick question @Kinvermark
Which program are you using to create Grass valley .avi files for editing in Vegas?
Are you using Edius to do this?

@I'd_tag_you_if_I_could Resolve does this with it's Media Manager. I think with free resolve to play/transcode HEVC files the Windows HEVC extension needs to be installed.

@Former user

Grass Valley HQ.avi codecs are a free download from Edius.net. Try Google. They have been available for many years.

This thread contains several hostile comments from some users directed to other members of the community. These have also been reported to admins and mods. Users are reminded of this post from a former Community Manager. Please note that "repeat violations of CR #1 will result in removal from the community".  Please also note CR #6. Thank you for understanding this as the warning CRs #1 and #6 mention.

@diverG Yeah much prefer it to prores but you're right maybe Dr Zen didn't know that, and wasn't interested in an external transcoder to create GrassValley fast.

@Steve_Rhoden He has a legitimate complaint, GPU decoding doesn't work for this file with his system, and it's a Vegas bug. He compares Vegas playback with Premiere to illustrate. Telling him to go back to Premiere doesn't help with this Vegas problem that will affect many others

@Former user If this footage edits better in Premier than Vegas, paying for Premier is the best solution. If I found myself in that same situation, I'd follow that advice too.

But keep in mind that Premier is rental-only. And that once you stop paying, your project work-product no longer works. I avoid that trap by test-driving footage in Vegas, which I own forever, before I buy a camera.

@Howard-Vigorita It's the 'no GPU decode' bug that's been around for years, he doesn't need premiere he needs anything that isn't Vegas to play it smoothly, alternatively Vegas could fix the problem. OP, like many would prefer to use Vegas.

I even tried this in Windows Video Editor, for some reason it also isn't using GPU decode, but does a much better job at Vegas playing without GPU decoding, it's only using 45% CPU. The free video editor that everyone has does a much better, but not quite perfect job. I think it gets stuck at the beginning of the GOP. Using Legacy decode on Vegas

As a comparison using Legacy decoder on Vegas to utilize all of the CPU for decode, vegas will use 100% CPU and play back more poorly. The reply given to the OP was bigoted and rude, it's akin to telling an immigrant of another race to GO BACK HOME if they dare to complain about a problem in their new country. No user should speak to another person that way when reporting an actual bug, because of that bug, the software doesn't play as it should, as he's used to in his other NLE. Howard you're too kind to see the evil in people.

I tried it in Vegas and Premiere. In Vegas, it was crazy choppy but Premiere did pretty well. Ryzen 7 2700X & Radeon RX 6900 XT.

I've had playback issues in Vegas for a few years now so I've been working with proxies because I don't like using Premiere. I have a camera that automatically creates proxies so it's not that big of a deal. Vegas does have issues even working with the proxies but I deal with it just hoping for a fix eventually. For me, messing with the way Vegas deals with the so4 compound .dll is the only thing that improves playback. This seems to be especially important when dealing with 59.94 fps footage for some reason, but I'm not sure if that has anything to do with your issue.

@jimingo-1 It was always my hope that their need to get ProresRaw and BlackMagic Raw to work on Vegas would require they rejuvenate the render engine to such an extent that everything works well, but then I was shown BRAW working really well by one of the beta testers without the need to fix anything else, so I expect they can do the same with ProRes Raw too working along side the much maligned SO4 decoder, which is disappointing.

For me, messing with the way Vegas deals with the so4 compound .dll is the only thing that improves playback.

What are you doing here?

Thanks

@Former user My playback issues started in Vegas 14. In 14, there was just one setting in the internal preferences that needed to be changed - changing a "true" to a "false". But in Vegas 19, there are three internal settings and one in File I/O that deal with the so4 decoder and I have no idea what each should be set to. I'm assuming there's probably a perfect combination but I haven't figured it out. I think someone mentioned that all you have to do now is uncheck the enable legacy avc decoding (in file I/O) but that hasn't worked for me.

PS @serd many on here are aware of Vegas's lack of playback ability & performance but most are loyal & have their head in the sand reg these issues.

You can take that BS somewhere else. Nobody "has their head in the sand" about these issues, everyone acknowledges them and the efforts being made to address them... Except the same few annoying dead horse kickers out there, who insist nothing is being done while ignoring what is being done. When the team fixes one thing, they start complaining about the next as if nothing is being done.

They complained about no nvenc/vce/qsv support, then it was added. Then they complained about no GPU decode, then it was added, then they complained about dynamic ram preview, then it was fixed, then despite being told the team is currently at work on a new render/cache system to speed up playback, they complain as if that was never said and nothing is being done... It gets old really fast.