hardware acceleration actually slower? why?

[1jhill]

Oh my quotes comment I misspoke I meant with hardware decoding enabled it makes it slower, sorry. With encoding enabled it seems to do nothing.

And as you can see in the pinnacle images the encoder is absolutely getting used as it should which explains the massive speed increase.

[tletter]

With encoding enabled it seems to do nothing.

'Hardware Encoder acceleration' does significantly speed up rendering. Perhaps not as much as Pinnacle, but it's still significant.

tletter
https://www.youtube.com/user/tletter

[1jhill]

Hmm I’ll have to test again on an actual export. Should the encoder showing activity when making a proxy because mine seems to be inactive and not used at all.

What’s the deal with the decoder and why’s is getting used to render when it shouldn’t? Should it just be left off full time then because as you point out it massively slows down proxy creation, I’d wait a whole day sometimes just to get proxies done. It made the program unbearable to use in any meaningful timeframe.

[Davidk]

Somewhere in this discourse, I recall a comment about large projects. The larger a clip is, the longer it will take to a) create a proxy, and b) render. And a common "practice" among users is to make their projects 'all-in-one' (large): which
- makes editing prolonged
- increases time required for edits proxy creation and rendering etc.
- increases opportunities for any errors to destroy the whole work.
rather than make a project in small batches or segments, each of say 20-25 minutes long.
A better practice is to make a project in segments: instead of one vsp for 1 hour, make 3 short ones each of 20 minutes, the 2nd and 3rd sequentially following from the prior one. Once each segment is done, render it. Proceed then to make the next segment, slight name change, eg project-2, and repeat. When the project segments are complete, a 4th vsp, which just has the rendered parts in it, no other edits: render to make a final project movie.

[1jhill]

My projects are only about 20 minutes long and maybe 40 at most. Usually a bunch of quick clips from riding and even then you create proxies for about no more then 40min of footage can take up to 4-5 hours if hardware decode is enabled. Like I side I had basically stopped doing them because by the time proxies were even done after loading footage from riding my entire day was done and then no time to edit during the week. Now discovering pinnacle and how fast I can make a video made me realize something must be wrong, bugged or setup improperly in video studio to have to run that much slower. So first discovery is absolutely do not enable hardware decode as it will triple your proxy creation.

[tletter]

... even then you create proxies for about no more then 40min of footage can take up to 4-5 hours if hardware decode is enabled.

Many of my projects are an hour long, so I don't understand what is happening as proxies are created in the background when a clip is added to the timeline. It doesn't take anywhere near the time that you report, unless your clips are huge or you're dropping a large number of clips onto the timeline at a single go.

So first discovery is absolutely do not enable hardware decode as it will triple your proxy creation.

Yes, as previously discussed, 'Hardware Decoder acceleration' should be used with caution. The following are the preference setting that work for me:

P.S. Although I have VS2019, I've never used it, rather I use VS2021 to render.

tletter
https://www.youtube.com/user/tletter

[1jhill]

ok so tested and with just the encoder enabled the cpu is more stable and about 20-30% used so less that only software yet the GPU is also at about 20% and the encoder shows its being used and decoder is idle (as id think it should be). So looks like decoder off encoder on is the best its gonna do but already way faster than with decoder enabled. that has to be a bug, no way should enabling a hardware feature cause your system to stall to a crawl. definitely not pinnacle speed but this i can use and the proxies do make editing faster once they're built, that's the one thing I wish pinnacle had.

[1jhill]

well damn just when I thought I had it all figured out on settings I've discovered with hardware decode disabled it then causes editing to be really slow even splitting a clip in two basically freezes the program for a little while. with decode enabled its super fast. So I guess I have to disable to make the proxies and export but enable when editing. too bad there isn't an advanced settings where I can just have it disabled for proxy and export.

[Luna Esterhuizen]

I don't know if my problem is exactly the same but I experience severe issues with play back in VS2023. I am busy with a 4K project. I used the same settings as my resource video files and created proxies. I tried both options regarding hardware acceleration, no difference. When I play back to do my final touches by changing clip durations etc I can hardly see what's going on as the play back is so choppy it skips whole clips totally in the preview. The audio plays on without problems but the images and videos is not showing if it fits. This is a very important process in order to make sure that that all fits at the exact right moments.
I now have to render the video, play it from that file and then do changes again and render it once again. This is not good. Previous versions never did that.
I just want to add that with the new VS 2023 I also have a new laptop that is supposed to be far better than my previous one, so I don't know what is to blame. The hardware or software.
Any suggestions would help me a lot as I am losing so much time.

[Luna Esterhuizen]

Just an update, I went through the settings again and switched of hardware acceleration and in fact play back was less choppy but still not fluently. Then I discovered for some reason my proxy files I created was no where to be found and I created it again, this seems to work perfectly now as it should. So I guess this problem is solved for now.