Steam installeren
inloggen
|
taal
简体中文 (Chinees, vereenvoudigd)
繁體中文 (Chinees, traditioneel)
日本語 (Japans)
한국어 (Koreaans)
ไทย (Thai)
Български (Bulgaars)
Čeština (Tsjechisch)
Dansk (Deens)
Deutsch (Duits)
English (Engels)
Español-España (Spaans - Spanje)
Español - Latinoamérica (Spaans - Latijns-Amerika)
Ελληνικά (Grieks)
Français (Frans)
Italiano (Italiaans)
Bahasa Indonesia (Indonesisch)
Magyar (Hongaars)
Norsk (Noors)
Polski (Pools)
Português (Portugees - Portugal)
Português - Brasil (Braziliaans-Portugees)
Română (Roemeens)
Русский (Russisch)
Suomi (Fins)
Svenska (Zweeds)
Türkçe (Turks)
Tiếng Việt (Vietnamees)
Українська (Oekraïens)
Een vertaalprobleem melden
As far as I can tell compressing to any compressed file type like .zip wouldn't really compress any further at all. What did you use to create the videos?
I have been experimenting with lower bit rates but it didn't work for me as I would like to keep the original quality as much as possible.
PAQ is a kind of compression similar to ZIP, that is said to have some crazy results. Compressing files to 1/10th of the original size. But it also has long compression and decompression times.
I am using nvidia's recording software to record the files in 1080p at 12 Mbps. It outputs the files in MP4 format and is using the H.264 codec from what I could find online.
NV should have an option to change the codec used to HEVC which will be h265 for better compression... but...
GPU output will be trash in terms of space used. GPU's are quick but not very good at encoding video. Since this is the case instead of tasking the GPU with both capturing and encoding it down to a lower bitrate (which it sucks at) just instead let it capture at a higher bitrate natively with plans to shrink it down after it captured... In this case it wont matter if you go with 264 or 265 to start you can use whichever you think looks better. Though going from 264 to 265 might add some more time to the transcodes.
Then use Handbrake or the likes to deal with the files how you see fit, from changing codec (to h265) to chaning bitrate or framerate (if you dont care about the footage being @ 60fps, but it was recorded at that, you can save a good chunk of space by halving the framerate to 30). If you *really* dont care about the time you can (and should) use the sooftware transcodes (which are the defaults) instead of using the GPU. This will use the CPU for the work in analyzing and outputing the new video file, and will take some time. Potentially lots of time. But this will produce the smallest files with the least loss in quality in terms of what you can do with the video itself.
well, I've never used the Nvidia program for recording videos so not sure how it compares but if you're still recording videos I would try OBS studio. That's what I use. I install after install I go to the video quality configuration and select "small file indistinguishable quality" setting and I don't mess with the bitrate settings. The video looks perfect to me and I do choose to use my GPU to encode. My performance takes less of a hit encoding by GPU than by CPU from what I can tell. And I do really like the encoding job done by my GPU. I actually always use it (especially because it's faster). Even when transcoding videos. To encode with my CPU would take like three times as long than as my GPU. GPU encoding makes it fly and the quality is almost identicle as far as I can tell. So I would start there and see if it helps.
Also you can try changing audio settings. Maybe change it to 128 bps audio which used to the the standard back when Napster was around. It's not that bad but 192/256 is better.