Hacker News new | past | comments | ask | show | jobs | submit login

I don't know how that could be possible, I find tearing to be incredibly noticeable when doing video editing. If you're getting it when trying to do transfers between frame rates it will potentially screw things up, because you're not able to see the actual frame rate. Occasionally I still see a youtube video where someone recorded a screencast and was getting tearing, and I find it really jarring.



Dunno, maybe it's just not something I'm noticing at all. Some people seem incredibly bothered by it, but I just barely notice it if I'm not actively looking for it.

I'm far more annoyed by the added input delay and sluggishness from vsync. I want frames on the screen as fast as possible.


I don't know how you can't notice it when doing video editing, you have to actively notice the frame rate to do it right. Any choppiness will be evident. Also I really don't understand your second paragraph. You can't get rid of input delay or make frames appear faster by disabling vsync. When you mux the video you target a specific frame rate, the common formats are almost always 24, 25, 30, 60, or multiples of those. The frames are appearing the same, it's whatever is in the video file.




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: