sag to Memes@lemmy.ml • 1 year agoChad VLClemm.eeimagemessage-square101fedilinkarrow-up10arrow-down10
minus-square@AVincentInSpace@pawb.sociallinkfedilinkEnglish0•edit-21 year agoForget playback. How was that video file recorded? How do you even store data that fast, let alone encode it?
minus-square@ulterno@lemmy.kde.sociallinkfedilinkEnglish0•1 year ago1 Terrabyte RAM with a 64GB RAM Drive perhaps?
minus-square@lud@lemm.eelinkfedilink0•1 year agoYou can read more about why and how it was made here: https://www.svt.se/open/en/content/ The only place I could find where I could kinda play the video is inside Davinci resolve, it doesn’t look how I would like it to.
minus-square@AVincentInSpace@pawb.sociallinkfedilinkEnglish0•1 year agoOhhhhhh. It’s a video decoder torture test. “If your app can play this it can play anything” sort of deal. That makes sense. Also makes sense that VLC puked.
minus-square@lud@lemm.eelinkfedilink0•1 year agoI think it’s more of a test for encoding, not sure if you are really supposed to try and play it in an app.
Forget playback. How was that video file recorded? How do you even store data that fast, let alone encode it?
1 Terrabyte RAM with a 64GB RAM Drive perhaps?
You can read more about why and how it was made here: https://www.svt.se/open/en/content/
The only place I could find where I could kinda play the video is inside Davinci resolve, it doesn’t look how I would like it to.
Ohhhhhh. It’s a video decoder torture test. “If your app can play this it can play anything” sort of deal. That makes sense.
Also makes sense that VLC puked.
I think it’s more of a test for encoding, not sure if you are really supposed to try and play it in an app.