Vegas is no Mediaplayer but an editprogram. How a file plays at preview in Vegas depends on - previewsettings - choice of projectproperties - program and buildversion - the use of proxies for too heavey files for your hardware - and thus also the kind of hardware with extra's and driverversions
- the use of proxies for too heavey files for your hardware - and thus also the kind of hardware with extra's and driverversions
I'm not sure what you want me to list...you don't mean all my hardware with driver versions do you?
Does this media info give any clues as to the problem?
General Complete name : Z:\MA2 tests\DJI_0001.MP4 Format : MPEG-4 Format profile : Base Media Codec ID : isom (isom/iso2/mp41) File size : 3.50 GiB Duration : 4 min 6 s Overall bit rate : 122 Mb/s Encoded date : UTC 2020-06-02 16:18:17 Tagged date : UTC 2020-06-02 16:18:17 Writing application : Lavf56.15.102
Video ID : 1 Format : HEVC Format/Info : High Efficiency Video Coding Format profile : Main@L5.1@Main Codec ID : hvc1 Codec ID/Info : High Efficiency Video Coding Duration : 4 min 6 s Bit rate : 122 Mb/s Width : 3 840 pixels Height : 2 160 pixels Display aspect ratio : 16:9 Frame rate mode : Constant Frame rate : 59.940 (60000/1001) FPS Original frame rate : 59.000 FPS Color space : YUV Chroma subsampling : 4:2:0 Bit depth : 8 bits Bits/(Pixel*Frame) : 0.245 Stream size : 3.50 GiB (100%) Encoded date : UTC 2020-06-02 16:18:17 Tagged date : UTC 2020-06-02 16:18:17 Codec configuration box : hvcC
-the use of proxies for too heavey files for your hardware - and thus also the kind of hardware with extra's and driverversions
I'm not sure what you want me to list...you don't mean all my hardware with driver versions do you?
I gave you the 5 reasons that can influence the preview velocity, you gave 3 but did not answer these two. And yess we like to know what kind of computer you use for this program with its components as CPU and GPU (s?) with its used driverversions. The type of files and projectformat you listed play at normal speed (50p) on my desktop from signature in full preview without added FX's
The average Joe's system will not be able to play back hevc 4K 60P in Vegas. You gonna need a bad ass system to coupe with that. This will required the combination of both CPU and GPU working together. If the selected GPU is not working or not supported within Vegas, then you are out of luck. Your option is would be transcode the footage or using proxy.
Proxy maybe making a large files for preview purposes... but at least it helps for smooth previewing. You will spend more time on the preparation (waiting time for the software to render to proxy - but then, you will be able to edit in comfort)
Ok, you still did not tell which drivers are installed, but if you use the latest Studio drivers nr. 442,92 for the NvidiaGPU that should be good enough if you also use Video acceleraton with the Nvidia and file decoding at Opt/Pref./File I/O, If all is set right the playback must be faster at Preview/Full and when you use proxies it goes much faster.
I guess I'll just have to imagine that the ever changing scenes of the footage from my drone will look good and edit away.
I will need to upgrade before long tho because I'll be doing plenty of post pro with it (color correction, cropping, etc) and need to see the actual results.
I believe that i7 assisted with 1660 SUPER sould be capable of better preview speed.
I'd double check that the latest NVidia studio driver installed, GPU acceleration is enabled (Preferences | Video), GPU decoder is enabled (Preferences | File I/O) and so4 reader is not disabled (Preferences | Internal).
Then I'd create simple project with single file (match media settings) on local internal SSD (Z: -- is it local or portable or network drive?), started task manager and started preview. Then check CPU/RAM/Drive/GPU/GPU decoder usage.
If you have iGPU (too lazy to google about the CPU you have), I'd play with GPU acceleration/GPU decoder: iGPU | NVidia.
i7 3rd Gen doesn't get benchmarked much anymore ....
4xxx, however, can be very serviceable chips for the budget minded
Former user
wrote on 6/2/2020, 10:19 PM
Proxy maybe making a large files for preview purposes... but at least it helps for smooth previewing. You will spend more time on the preparation (waiting time for the software to render to proxy - but then, you will be able to edit in comfort)
Can I make my own proxies? my Trancoder app can convert 4k60pHEVC to 1080p60AVC at 240fps. Probably is faster and creates higher resolution then vegas proxy generator. If I can how do I make vegas use my proxy generated files?
ProxyAssist – creates low resolution proxies as takes using internal/external encoders
Former user
wrote on 6/2/2020, 10:37 PM
I can make them fine, I just didn't know how to make vegas use them. apparently adding the files to the same directory as your original, name it the same but use extension .sfvp0, will make vegas use my own generated proxies. Well i'll test that a bit later