![]() ![]() The bottleneck in many editing operations is getting a video encoded in a particular codec/res/bit-rate decoded into showable frames on the fly. It's important to understand what a proxy file does for you. Thank you all for contributing to my education. I guess that's is the best of both world solution. When that occurs, I am going to quickly transcode that one particular footage and do my scrubbing. My current setup can handle most tasks without transcoding with the exception of some isolated clips with fast action that I wanted to pin down the exact moment. Workflow: I built my PC because I wanted to avoid transcoding my 4K videos for editing. Well, if there is a good deal on the RTX 3060ti I might still jump for it. Hardware: When the hype is cooled off, my current PC setup is really not that bad. Software: I have dabbled into Resolve (free version), but I am still a lot more comfortable with PPCC. Ĭodec: Since most of the consumer grade camera are all recording in H.264 or H.265, it is not something I can change. The editing experience is a combination of. But the exercise brings me to realize that I can forever chase for the perfection which may or may not be that much better than what I have. It's not easy to get a full pictures of the situation and the potential scenario. But I was annoyed that it stuttered when I fast forward/backward and scrub the source in search of the exact moment. I built my PC a couple of years ago to make my video/editing hobby fun. In a lot of way, I was fooled by some of the Youtube tutorials where the OP scrub their clips back and forth at high speed and yet the playback was creamy smooth (now I am convinced that most of them were transcoded footages). ![]() It started out as my search for perfection in my editing experience. ![]()
0 Comments
Leave a Reply. |