| Printable Version of Topic
Click here to view this topic in its original format |
| Unofficial VirtualDub Support Forums > Advanced Video Processing > Change Temp Directory For External Encoders |
| Posted by: -vdub- Aug 18 2011, 11:27 PM |
| Avery do you think can be done for all virtualdub for all processes to use user set dedicated temporary drive/directory/folder on another drive. From a temporary file location set from the options. This would help overnight to speed up all processing to increase the fps throughput. I noticed this long ago the difference fps throughput between other software's and virtualdub. Then again today when using external encoders with ffmpeg where it used the source folder for temporary processed files. Of course ffmpeg may or may not be controlled by virtualdub though would need maybe an external encoder option to change this. Maybe do this while making setting change for virtualdub user set location for temporary files.  |
| Posted by: stephanV Aug 19 2011, 04:45 AM |
| You can already replace the tokens with a real value (like e:\folder\temp.264) I don't think it will help much though since encoding is normally CPU bound. |
| Posted by: -vdub- Aug 19 2011, 09:36 AM | ||
I did think of that after posting, left post as is since. Better would be global for virtualdub and external encoders using virtualdub > preferences > Disk I/O About the cpu comment. The hdd i/o is also an important factor that affects the processing speed. |
| Posted by: phaeron Aug 23 2011, 06:05 AM |
| There is one thing you lose when hardcoding the temp names, which is that VirtualDub can no longer track the output file and delete partial temp files. I can change the logic to avoid prepending the output path if the temp filename template is an absolute path. I'd agree, though, that switching disks is unlikely to make a difference. Only compressed data hits the hard drive, so it should already be low bandwidth. The uncompressed data stays in memory as it is transferred over a pipe device. If you're working with a largish frame size you might try increasing the output buffer size -- this also controls the size of the pipe buffer and may help if you've got a pipe bottleneck. Check the CPU utilization between the processes. Ideally either VirtualDub or the video encoder should be the bottleneck and loading down the CPU by at least one full core. If both processes are underutilizing the CPU then that's a bad sign. |
| Posted by: -vdub- Aug 23 2011, 01:25 PM |
| Yes output would be a static drive used for temp files. If need to delete the temp files it is no problem will then use a folder on the temp drive to delete correct temp files. I was initially asking mainly for the external encoders where it will read from source at same time writing its video/audio temp files. The performance buffers are set at max (far right) except for audio still at 4secs. Cpu is very high but thought that was normal for encoding as it happens with all other softwares while encoding video. Encoding video is 22-40 fps with other softwares with virtualdub doing same encoding using no filters it is 06-20 fps (min-max) video compression encoding, audio copy. Virtualdub has many filters for use where other softwares will have few or none. When no filters are needed will use other softwares instead for encoding video with higher fps. Not working with HD frame sizes. Cpu cores are both up high at the same time, not exactly the same peaks in task manager, and not mirrored meaning are really using both cpu correctly. Turning of one cpu remains the same cpu is high. But then is the same whenever i encode video no matter what software used. Not a cpu issue then really if like this with many softwares for encoding. If encode to uncompressed lossless avi with pcm then cpu for video-audio compression is 50-60 fps and the mux i guess is about 15-45 fps the cpu will raise and fall between these values quickly. |