Introductory Post

[deathisyourart]

The Multifandom VID Commentary Challenge!

The objective of this challenge is for you to write or record your own commentary for a vid (or many vids) that is/are not of your making. This is not a review, a critique, or a recommendation, and we don't want a rehash of what the vidder says they did, we want to know what you believe the vid is doing;

Comments

[0mindthegap0]

Just to clear things up for certain - since you didn't have any audio commentary examples from our corner of fandom, do you mean basically like these, but from an outsider perspective?

[deathisyourart]

Yes, but from a viewers perspective and with an accompanying transcript. :)

[deej]

I just wanted to ask if it wouldn't be a bad idea for vid_commentary to use the default comments page? I'm laying out my screencaps and in the journal's current size, if I want to sit images 2-across (which I'd prefer to do compare/contrast caps), they'd only be able to be 225px wide to fit the layout.

The default page would give us plenty more room to play with :)

[deathisyourart]

This layout was not what I wanted, but the custom one I had kind of broke just a few days ago. Do the screencaps in the commentary I already posted appear side by side or as a single line? They are 320px across and they appear 2 side by side in my browser, I'm on a 15" screen running 1280x800.

I'll attempt to adjust the layout to make things easier on everyone.

[deej]

Thanks for making that adjustment :) Yours weren't before, but they're sitting side by side now, yay! Sorry to hear about your custom one breaking (was that the white one? I really liked it!) it happens at the worst possible times hey *eye roll*

[deathisyourart]

I loved that white layout! *sigh* It was created by thefulcrum (she makes a lot of amazing layouts) but LJ decided that it would no longer accept the URL that I had the script hosted on, and it won't accept the code being copied straight into the override box, so.... I can't use it anymore.

Thank you for letting me know that there was an issue!