@marcinzm

Your calculation is correct.

"Can this value be larger than 2?"

I have no idea. Just do the calculation internally and you should be OK. Having said that, there is no guarantee that this will always work. I've had instances where it still wouldn't register properly.

My recommendation is to just stay away from Vegas style proxies completely if you create your own. Swapping is fairly foolproof.

@wwaag

I would like to use nvencc64 encoder to convert the video files using GPU because it is much faster. I did one test today by call:

nvencc64 -i "c:\!!!_YouTube_upload\_media_file_extractor_ffmpeg_input\05_zakonczenie_Sony_FX3_003.MP4" --codec h264  --vbr 31000 --preset quality --colorrange full  --gop-len 30  --output-res 1920x1080 --format mp4 -o "c:\!!!_YouTube_upload\_media_file_extractor_ffmpeg_input\05_zakonczenie_Sony FX3 003_h264_klienci.mp4" > "C:\!!!_YouTube_upload\_media_file_extractor_ffmpeg_skrypt\skrypt_output.txt" 2>&1 

but the output file contains some artefacts. How can I avoid them? Do I need to add some extra parameter to get the output video without bad pixels/artefacts?

I don't mean proxy goal for it, but conversion to h264 or conversion to full hd video.

Can you help me?

You can have speed or quality, but usually not both. Although, GPU renders are fast, they are usually not very high in image quality as measured by most Image Quality metrics. For final renders, I always use x264 with a CRF set to 18. You can use HOS or the free Voukoder app or you could write your own app using FFmpeg. Under the hood, they are the same.

@wwaag

I wrote a plugin in C# to create proxy files, but I noticed that I need to close the project/Vegas and then reopen it to make the proxy files being recognized by Vegas.

Do you know how to refresh the status of raw video files without reopening the project/Vegas to make the create proxy file option disabled? This "Create proxy file" option is only disabled when I reopen the project.

@wwaag I have a weird issue with creating a proxy for one file using nvenc64

Frame rate for input file is 29.970p.

Vegas returns 612 frame count.

Media info returns 734 frame count.

The substraction of these two values gives 112 frames to drop. I think it is not ok, doesn't I?

I have such code:

nvencc64 -i "D:\Filmiki\2022-08-02 - lot dronem na szczycie wawozu Homole niedaleko granicy polsko-slowackiej\!_DJI_Mavic3\2022-08-02 - lot dronem na szczycie wawozu Homole niedaleko granicy polsko-slowackiej 007.MP4" --codec h264  --vbr 12000 --preset performance --colorrange full  --ref 2 --gop-len 30  --fps 29.970 --trim 122:734  --output-res 1280x720 --format mp4 -o "D:\Filmiki\2022-08-02 - lot dronem na szczycie wawozu Homole niedaleko granicy polsko-slowackiej\!_DJI_Mavic3\2022-08-02 - lot dronem na szczycie wawozu Homole niedaleko granicy polsko-slowackiej 007.MP4.sfvp0" > "D:\Filmiki\2022-08-02 - lot dronem na szczycie wawozu Homole niedaleko granicy polsko-slowackiej\skrypt_output_1.txt" 2>&1 

What is wrong with the above call?
Vegas doesn't see this proxy file created from above script.

Proxy file is created by is not compatible with Vegas Pro 20.

I upload this "problematic" video file into wetransfer.com web page: here is a link: https://we.tl/t-kQsqDwuNUI

Are you able to help with it?

@marcinzm

No problem here using HOS. Your Vegas framecount is wrong. HOS returns the same framecount for Vegas and MediInfo--734 frames. Just get rid of the trim option and it should be fine. The only other difference is that I usually use "-fps 30000/1001" rather than "-fps 29.970", although it shouldn't make any difference.

@wwaag So the problem is inside ScriptingVegas.dll library file, isn't it? Just because Vegas returns wrong framecount. How did you receive valid value from Vegas in HOS? I know how to fix the issue in my code, but it would be not as good as it should be, because I thought that when the substraction result is more than 100 than it should be left and doesn't take part in the trim calculation, but I know it is not so good solution and not so perfect behaviour. Thank you for your answer

PS Maybe I uploaded to Visual Studio older version of ScriptingVegas.dll?

@marcinzm

For max compatability, I add the following reference, ScriptPortal.Vegas.dll, from V14. I've never used (or even seen) "ScriptingVegas.dll".

"So the problem is inside ScriptingVegas.dll library file, isn't it?"

No. In this instance, the problem lies with your code--not Vegas returning the wrong framecount. Vegas does have a problem decoding certain HEVC formats and sometimes drops the first two frames, but never 100.

The code I use is very simple in which "inFile" is the media file and "vegFrames" is the Vegas framecount.

Media media = new Media(inFile);
var vegFrames = media.Length.FrameCount;

@wwaag Yes, you are right, I had "ScriptPortal.Vegas.dll" in my mind, but I wrote "ScriptingVegas", because I was typing without a check.

When I was writing my code I was shocked, because I couldn`t have gotten the Frame Count value just from ScirptPortal.Vegas.dll. The only way I found was to get the Frame Count from event, but event has some limits, because when you cut the event, then the Frame Count of cut event is different than from raw/source event. That's why before proxy creaton I always pasted the fresh events on timeline to be sure that the frame count from event is always valid and equal to frame count from raw/source video file. That's why it was not good solution, because in the sample video it doesn't get the right frame count value. In most cases it was working perfectly.

Thank you for your help.