While the 1070 is fully supported, if its not being found that is a problem. Uncheck "legacy AVC decoding" if it is selected. Can you share a screenshot of file i/o?

I also suggest sharing MediaInfo as the media is the key variable.

It will be supported as I am using the 1080TI which is very similar but with more memory 11GB vs 8GB and a bit faster. As Roger says the issue is likely it is not being found so not being used.

Performance comparison: https://www.gpucheck.com/compare-multi/nvidia-geforce-gtx-1070-ti-vs-nvidia-geforce-gtx-1080-vs-nvidia-geforce-gtx-1080-ti-vs-nvidia-geforce-rtx-2060-vs-nvidia-geforce-rtx-2070

>the age of your video card ... Nvidia 1650 or higher is suggested

Just because it is older does not mean it is slower or has lower performance. The 1070Ti is actually generally considered to be higher performance than the 1650 (but it is definitely more expensive, consumes more power, and runs hotter), a claim supported by numerous 3rd party benchtests and comparisons

Hello,

Here is the I/O.

Here is also the info media of this test video.
Even without loading media, I should find the graphics card in I/O, except it does not appear.

-----------------------------------------------------------------------------------------
Général
CompleteName                     : S:\Téléchargements\GX010274[1].MP4
Format/String                    : MPEG-4
Format_Profile                   : Base Media / Version 1
CodecID/String                   : mp41 (mp41)
FileSize/String                  : 356 Mio
Duration/String                  : 29s 880 ms
OverallBitRate/String            : 99,8 Mb/s
Encoded_Date                     : UTC 2022-04-10 06:49:18
Tagged_Date                      : UTC 2022-04-10 06:49:18

Vidéo
ID/String                        : 1
Format/String                    : HEVC
Format/Info                      : High Efficiency Video Coding
Format_Profile                   : Main@L6@Main
CodecID                          : hvc1
CodecID/Info                     : High Efficiency Video Coding
Duration/String                  : 29s 880 ms
BitRate/String                   : 99,6 Mb/s
Width/String                     : 3 840 pixels
Height/String                    : 2 160 pixels
DisplayAspectRatio/String        : 16/9
FrameRate_Mode/String            : Constant
FrameRate/String                 : 59,940 (60000/1001) Im/s
ColorSpace                       : YUV
ChromaSubsampling/String         : 4:2:0
BitDepth/String                  : 8 bits
Bits-(Pixel*Frame)               : 0.200
StreamSize/String                : 355 Mio (100%)
Title                            : GoPro H.265
Language/String                  : Anglais
Encoded_Date                     : UTC 2022-04-10 06:49:18
Tagged_Date                      : UTC 2022-04-10 06:49:18
colour_range                     : Full
colour_primaries                 : BT.709
transfer_characteristics         : BT.709
matrix_coefficients              : BT.709
Codec configuration box          : hvcC

Audio
ID/String                        : 2
Format/String                    : AAC LC
Format/Info                      : Advanced Audio Codec Low Complexity
CodecID                          : mp4a-40-2
Duration/String                  : 29s 867 ms
BitRate_Mode/String              : Constant
BitRate/String                   : 192 kb/s
BitRate_Nominal/String           : 48,0 kb/s
Channel(s)/String                : 2 canaux
ChannelLayout                    : L R
SamplingRate/String              : 48,0 kHz
FrameRate/String                 : 46,875 Im/s (1024 SPF)
Compression_Mode/String          : Avec perte
StreamSize/String                : 690 Kio (0%)
Title                            : GoPro AAC  
Language/String                  : Anglais
Encoded_Date                     : UTC 2022-04-10 06:49:18
Tagged_Date                      : UTC 2022-04-10 06:49:18

Autre #1
ID/String                        : 3
Type                             : Time code
Format/String                    : QuickTime TC
Duration/String                  : 29s 880 ms
BitRate_Mode/String              : Constant
FrameRate/String                 : 59,940 (60000/1001) Im/s
TimeCode_FirstFrame              : 06:55:50:13
TimeCode_LastFrame               : 06:56:20:05
TimeCode_Striped/String          : Oui
Title                            : GoPro TCD  
Language/String                  : Anglais
Date d'encodage                  : UTC 2022-04-10 06:49:18
Date de marquage                 : UTC 2022-04-10 06:49:18

Autre #2
Type                             : meta
Duration/String                  : 29s 879 ms
BitRate_Mode/String              : Variable
Duration_LastFrame               : -151
-----------------------------------------------------------------------------------------

Thank you.

That you get good timeline performance with HD but not UHD might be related to the amount of RAM thar you have installed on your computer (16 GB). 16 GB is the minimum recommended RAM for HD for Vegas Pro 19 but 32 GB is the minimum recommended for UHD. Please see the minimum recommended specifications for Vegas Pro 19: https://www.vegascreativesoftware.com/us/specifications/#productMenu

When editing, barely 6GB of RAM is used.
The problem is that I don't see my graphics card in "I/O File".

After disabling "legacy AVC decoding" it seems to work better, playback is smooth, just jerky transitions (which I can understand). I see the GPU is used and the CPU less solicited (really weird).

On the other hand, is it possible to lower the number of frames per second in the preview? Because regardless of the setting, it leaves me the same number of images as in the project, i.e. 59 images.

Thank you.

I'm not sure that the exact GPU appears in the I/O File. I've got an NVIDIA GeForce RTX 2080 SUPER 8GB GPU installed and this is what I get in I/O:

jerky transitions

... a possible indicator of a lack of RAM. Does the same jerkiness with transitions occur with an HD project as against a 4K project?

Pls set the I/O exactly this way and preview in Good/Quarter, and tell us how it goes.

your source clip is a hard nut for VEGAS to crack, even with high level hardware.

The nut: high resolution, high fps and mainly H(igh)EVC!

I have the best results with this configuration in PJ.
If I disable the NVIDIA NVDEC, only the processor works, while it's OK.
I find the same performances as in HD. The fade between two videos jerks but it is not very annoying and necessarily requires more resources.
 
Thanks a lot for your help.

When editing, barely 6GB of RAM is used.
The problem is that I don't see my graphics card in "I/O File".

After disabling "legacy AVC decoding" it seems to work better, playback is smooth, just jerky transitions (which I can understand). I see the GPU is used and the CPU less solicited (really weird).

On the other hand, is it possible to lower the number of frames per second in the preview? Because regardless of the setting, it leaves me the same number of images as in the project, i.e. 59 images.

Thank you.

Actually you do see your GPU in file i/o. It's NVDEC (NVIDIA decoder).

This is an HEVC file, so legacy AVC won't affect it, but legacy HEVC will. You can try both ways of decoding HEVC and see if one is better. I'd recommend non-legacy HEVC.

To be realistic, 60p UHD HEVC is hard to decode and edit. I would right-click on media and "create proxy file" for this type of media. Or shoot a more normal framerate like 24, 25 or 30p if your GoPro supports that.

For most filmmakers, 60 fps is about slow motion, so you can add a 60 fps file to a 30fps timeline and get 2x slow motion when you want to emphasize some action and otherwise just play it back at 60fps (it will throw out every other frame). A 30p timeline will perform better than a 60 one.

@KiKoMaSo In the file I/O NVIDIA is all you'll see as @Dexcon showed 👍

I just filmed a short HEVC clip, the info is slightly different to yours in some areas, maybe someone can explain, mp41 vs mp42 is what i'm curious about, i guess i could Google it 😂

This is how it plays back, RAM & GPU,

I have a different pc setup but just thought i'd share 👍

BTW can you go to your icon at the top, click it - My Profile, & fill in your Signature with your Vegas version, Windows version & system specs, CPU, GPU, RAM etc. this will then show at the bottom of the comments 👍 (see mine & others at the bottom of the comments)

Thanks for the tips 👍

@KiKoMaSo Don't know if this makes any difference to your playback issues but

This post is at the top of the forum - VEGAS Pro 19 "does not officially support Windows 11 yet".

https://www.vegascreativesoftware.info/us/forum/vegas-pro-19-and-support-for-windows-11--132810/

I have the best results with this configuration in PJ.
If I disable the NVIDIA NVDEC, only the processor works, while it's OK.
I find the same performances as in HD. The fade between two videos jerks but it is not very annoying and necessarily requires more resources.
 
Thanks a lot for your help.

The problem does not lay with you, it's with the software.

I tried a gopro HEVC 4K60 file. If you have decoder on, Vegas leans heavily on the primary CPU thread(single core performance), if you choose to use LEGACY HEVC DECODING, Vegas can then heavily utilize modern CPU's spreading the workload across many cores, but it also turns off GPU DECODING.

What will happen is with 8 CPU cores you will run out of CPU , and you will be better off using GPU decoder even though Vegas can't use most of your CPU. Of the bugs in Vegas this the most bizarre.

To be realistic, 60p UHD HEVC is hard to decode and edit. I would right-click on media and "create proxy file" for this type of media. Or shoot a more normal framerate like 24, 25 or 30p if your GoPro supports that.

Now that we know about your source, I agree with @RogerS' statement. regardless of which side one chooses on the GPU performance debate.

@Musicvid This is premiere playing GoPRO4K60 HEVC, it has no problem, I doubt any other NLE that supports GPU decoding has a problem with it. The green dot indicates no dropped frames, the yellow line means no proxy or caches built.

I explained the problem. For Vegas to playback such a file it needs 2 things, GPU decoding, plus multi-threaded CPU playback. For Vegas and HEVC you can only choose 1, not both.

Here is picture of CPU use with GPU decoding OFF

Resolve is spoken about as the miracle playback NLE device not Premiere, Premiere is what you should expect from any editor, so Vegas is failing at HEVC playback, and should be improved

I had to change my GPU a year and a half or two years ago, but given the price and the low availability, I had given up.
I'll start looking again, but in game there isn't much difference between my GPU and a 3060 or even a 3060Ti, current prices aren't profitable given how little difference. Video editing comes second to me.
nVidia is due to release its 4000 series this year, as well as Intel which is due to release its cards mid/late 2022. I'll probably wait a little longer to see how this all plays out.
Thank you.

Your GPU is very good, close to gtx1080 performance, the user who tried to convince you that your GPU is the problem, not Vegas does this all the time. It's either through ignorance or malice. Imagine you were convinced to buy a $1000 GPU and nothing at all changed with performance except that you're $1000 poorer.

Having said that though with VFX, not simply playing back the file, you can exceed the power of your GPU with Vegas. People here have suggested the best cards for Vegas are rtx3060 - 3060ti based on MSRP, with 3060ti best value for money ($ to power at MSRP)

As said, the problem you are facing with HEVC is not a problem that can be fixed with a GPU, the software needs to be fixed

Your GPU is very good, close to gtx1080 performance, the user who tried to convince you that your GPU is the problem, not Vegas does this all the time. It's either through ignorance or malice. Imagine you were convinced to buy a $1000 GPU and nothing at all changed with performance except that you're $1000 poorer.

Having said that though with VFX, not simply playing back the file, you can exceed the power of your GPU with Vegas. People here have suggested the best cards for Vegas are rtx3060 - 3060ti based on MSRP, with 3060ti best value for money ($ to power at MSRP)

As said, the problem you are facing with HEVC is not a problem that can be fixed with a GPU, the software needs to be fixed

You reassure 😄
Thanks for your feedback 😉

Hello,

I installed the trial version of Vegas 19 to test the software before purchase.
I have a problem with the preview. With videos in 1080p, it goes without too much problem but once in 2.7K or 4K, the preview is very slow, impossible to work with.

In the Windows task manager, we see that only the CPU is used and not the GPU.
I have the latest nVidia driver installed, the 512.15 in studio version.
In Vegas I don't have the option in I/O to enable decoding but GPU nVidia is selected in Vidéo options.

How do I use my nVidia card for decading in the preview please?

Config:
I7-9700K
16Go RAM DDR4 3600MHz
SSD nvme
nVidia GTX 1070Ti

Thank you.

Helli, i had the same issues with my new RTX306

Ryzen z

32gug ram

ssd

and my plaback is very laggy after 10 seconds. works fine for 1o seconds then i get like 1fps

i have now also the vegas 19 test version but it wasnt any better as with vegas 17 pro.

i hope i can manage to work with the rtx 3060 card. but i assume vegas 17 will not support it properly -.-

I believe, but not certain it wasn't until build 527 of VP18 that they fixed the slow NVENC problem to do with 3000 series cards.

What you're seeing with playback fine for 10 seconds then slideshow is 1 of 2 situations, either vegas started autocaching your timeline when you loaded it, you started playback and after 10 seconds the cache had expired and vegas had to play your camera file in real time which it couldn't do. Other possibility is to do with GPU decoder overload problem Vegas has. You'll see that at edit points but also randomly during playback Have task manger open looking at the GPU decoder graph to determine that. @Paul-Jonack