An update to post the "answers" to the test. Your guesses:
The "key" needed to decode the block above (after base64 decoding it) is:
MGFHsrI1S~ywp9UONTPFCib<IN[l4\2v
You can do it yourself using a tool like
http://www.tools4noobs.com/online_tools/decrypt/
-----
So based on our very small sample, we had an unexpected result.
You "guessed wrong" every time, however, the fact that you were consistently wrong means its very likely you can spot a difference between 30 and 60 FPS, you just interpreted the difference you detected 'incorrectly'. Presumably you saw the 30 FPS video as somehow better (more detailed, less choppy, less noise) and concluded it was the 60 FPS video, or alternatively you spotted some flaw introduced by frame-dropping and concluded those must be the lower frame-rate captures.
I didn't think we'd see any pattern, you thought you'd prefer 60 FPS and could identify it. There's a small chance you'd just luck out like that, but we should probably take a moment and consider that maybe 30 FPS captures really do look better if you send them to YouTube. Maybe dropping frames causes YouTube video to look worse. It might be worth some further investigation just to see if you were lucky (or unlucky, depending on how you want to call it) or if there really is something going on here.
I checked and double-checked the files before uploading, and I can see the original file names on youtube in the video manager. For example:
So I'm reasonably sure I recorded all the titles/file-names right.
Possible explanations:
- You're used to seeing video captured and uploaded at 30 FPS. It doesn't actually look better, but it's more consistent with what you expect. While you can detect a difference, you prefer video that looks like the stuff you see most often, not what actually looks smoothest (the same sort of complaints made about 48 FPS films)
- You were lucky. Not insanely lucky, but a <10% chance of getting it by sheer luck is still within the realm of possibility.
- I screwed up the captures/encoding/etc. some how. I'm not sure how that could be, and I'd be willing to document my procedure if you think you could spot something - but I can't think of any shortcuts I took that could introduce error.
- Maybe the way frame-dropping happens actually introduces some sort of weird temporal artifact. Maybe they've optimized their system for high-speed cameras and those cause strange issues with computer graphics. I suppose we could correct for that by doing the frame dropping on my end with premiere.
- The frame dropping method introduces a bit of jitter, or perhaps capturing gams running at very high frame rates (>200 FPS in some cases) at 60 FPS causes artifacts when you drop frames. I can kind of imagine a way that could happen but I can't think of a good way to test it on youtube without doing a lot of work.
In any case, I'm reasonably convinced you can detect the difference between a 30 and 60 FPS file sent to youtube. The problem we have to sort out is that you cited the 30 FPS versions as though they were the 60 FPS versions; you noticed the difference and thought lower frame-rate captures looked smoother. That's surprising to say the least.