Since the vorbis encoder supplied in my builds is quite broken, it’s highly recommended to re-encode with one of the builds off the above site.

But, following this guide, you can build ffmpeg with webm for windows rather easily. But for those without a linux distro to play with, you can simply download them here:

Download:
[OUT DATED! See top of post]
Removed links. Please stop using these versions. They have a broken vorbis encoder. Use the latest above.

Use:

ffmpeg -i [video file to encode] -b [bitrate]k -aq 60 -threads 4 output.webm

On a command line and wait. And wait. It’s slow. Very slow. You can speed it up a bit by using -level 300 if you want, though quality suffers a little bit. Two pass encoding is supported with -pass 1 followed by a second encode with -pass 2, as per usual.

Have fun!

Supported VP8/WebM Flags, all flags require a numeric value after them.

You can also use this nice spreadsheet.

-vb [target bitrate]
-level [Encoder speed/quality and cpu use[?]. 100 = best, 200 = average, 300 = ‘realtime’/fast]
-threads [number of threads to use for encoding, can't be 0 [auto] with VP8/this build]
-token_partitions [number of partitions to split the video into, useful for multi-core decoding]

-lag [number of frames to look ahead for when encoding]
-keyint_min [min distance between keyframes]
-g [max distance between keyframes]

-bt [bitrate tolerance in VBR/2pass mode]
-minrate [Minimal bitrate allowed in vbr/2pass mode]
-maxrate [Maxium bitrate allowed in vbr/2pass mode]

-qmin [min quantizer allowed]
-qmax [max quantizer allowed, set just this for fixed quantizer mode]

-bufsize ["ratecontrol buffer size (in bits)"]
-rc_init_occupancy ["number of bits which should be loaded into the rc buffer before decoding starts"]
-rc_opt_occupancy ["number of bits which should be kept in the rc buffer during decoding"]
-rc_buf_aggressivity ["currently useless", buffer use aggressiveness]

-spatial_rsmpl [spatial resampling]
-spatial_rsmpl_up ["Spatial resampling up watermark, percentage of target data buffer."]
-spatial_rsmpl_down ["Spatial resampling down watermark, percentage of target data buffer."]

-profile [Can't find much data on this, usually set to 0]

-nr [Noise reduction]
-sharpness [Has a value from 0 to 7, assuming it applies a sharpness filter after decoding]

-altref [Allow alternate reference frames, 1]
-ar_max_frames ["Max frames used in creating alt. ref. [0,25]“]
-ar_type ["Filter type used in creating alt. ref."]
-ar_strength ["Filter strength used in creating alt. ref. [0,6]“]

-skip_threshold [threshold to skip a frame instead of encoding it[?]]
-mb_static_threshold [static frame threshold[?]]

First we have a Wrath by Matt Current. Win32 demo. Mostly dark and whatnot.

Next up, some fun little thing by ASD titled Chameleon. Win32, some 2D art and 3D. They made this in a few days for a random compo.

Here, have Lightshaft by Elude, a modern Amiga demo. Yay low res.

Now for something completely different, Frameranger by Fairlight, Orange, and CNCD [whew], once again a Win32 demo, and probably the biggest demo of the year so far. Random more main-stream oriented car/robo scenes, followed by more proper effects known of the scene. This thing runs like crap in real time though even on a high end rig.

Sorry, no oldskool platforms here this time, unless you count the upgraded amiga used for the Elude demo.

Phlix basically will take any non-flash video file [AVI/MOV/WMV/MP4/Etc, as long as it's on a http server], and convert it to flash on the fly, without [too] much wait [5-15 seconds at most if the server containing the video is slow]. No need to download some random codec to watch videos, as long as you can stand [slightly higher quality than normal] flash video.

Randomly got the idea with a chat with my mate, and a few others who seemed to be interested in the idea. Basically it’s to bridge the gap in the online media world, where there’s still non-flash files laying around. [And if you don't like flash video quality, well then don't use this!]

A weekend’s worth of coding; yay ffmpeg having most of the support that I needed already in, only had to hack in a few things. Thanks to TJ for abusing it to death to iron out some odd bugs. Fun times had by all.

Anyway, try it out, tell me what you think, and if something doesn’t work right, let me know.

Todo:
- Idiot proof the url box
- Support FTP
- Properly detect live-streams so it won’t try to cache them
- Provide Embed code
- Impliment h.264 support [mmmm more ffmpeg editing]
- Provide some notice when the source server is being head-achingly slow

So, here’s a small taste of what was released there. The top 3 for each category at the party. Remember, normally these demos are generated in real time, and etc etc, just captured here for those without a powerful PC/don’t feel like downloading the binaries.

4kb – 1st

4kb – 2nd

4kb – 3rd

Demo – 1st

Demo – 2nd

Demo – 3rd

There’s actually two winners for 3rd:

Also, my kiosk software is now on Pouet.net

Capped.TV Kiosk. If you’re headed to NVScene or NVision, stop by the demoscene hall and check it out.

And that’s my work of the month.

Edit: Yes that’s my only bit to NVScene; was unable to get a demo together after working the past few weeks on the kiosk. I’m sure no one wants to see Rob is Jarig encapsulated in a time-delay fake prod anyway… [Hey, will someone release a 4k version of it already? ]

And don’t forget to come to NVision ’08! Demoscene stuff will be happening at the NVScene part of the convention.

Capped.TV will have a presence there, in the form of Capped.TV Authorized Juice Kiosksâ„¢. Which will include HD captures of many of the demos featured in the reel, plus many more.

Don’t forget to register.

You can have fancy urls for wordpress in IIS without any need for a url rewriter. Then again, this is really the only way I know to do fancy urls in IIS..

Anyway, simply take this code:

<?php
//404 hack
//by the mickelphin

?>

And insert it in a file called 404.php in your blog directory.

Then open up IIS’s config and move to your blog directory. Open up properties for that, and go to the Custom Errors tab. Click on the first 404 entry [and only the first], press edit, change it to url, and put in ‘ /[your blog directory, if any]/404.php ‘.

Ok on out. In wordpress, change your permalink style to exclude index.php. ie simply: ‘ /%year%/%postname%/ ‘ or whatever.

And have fun. I’m using it now.

If you have any issues, feel free to leave a comment.

Code updated on August 11, 2009

Here’s a few demos by The Black Lotus, done for Amigas. Of course, the amiga they were using is fairly well modified with extra ram and etc, but meh.

Captured in WinUAE, so both have a fairly high framerate then on the real machine.

This one was ported to Atari Falcon. Here it is running on the machine [once again, fairly well modified]

The really short version: It sucks.
The lesser short version: Project Wonderful is not good for content providers, however, for advertisers it’s a great low-cost way to do ads.

Our site’s average CPD [Cost Per Day] for our adspot [a add on the bottom of T.RScript.org] was 33 cents. 33 freaking cents for 10k ad views. Click ratio was about 0.15%.
For comparison, our Google AdSense click ad ratio has been 0.17%, and it’s average CPD is $2.

Project Wonderful: $0.02 per click, $0.04 per 1k views, $0.33 a day [338 clicks, 252k views, 31 days]
AdSense: $0.13 per click, $0.23 per 1k views, $2.01 a day [448 clicks, 252k views, 31 days]
[Both costs are AFTER the ad services take their cut]

Quite a big different if you ask me. Project wonderful is great for advertisers who want cheap ads, but suckage for content owners, with the low return we’ve been experiencing. Personally, I don’t think Project Wonderful is that well balanced as they say it is.

At least, not for smaller sites like t.rscript.org with only 10k views a day.

But, even on larger sites like PVPonline.com, it doesn’t seem to get the full value out of Project Wonderful. $20/day for 120k+ page views of your ad. Not sure about clicks, but I imagine it’s fairly decent, I’ve found a few things interesting on their adspace anyway.

In Conclusion: Project Wonderful Sucks for Content Providers; But Awesome for Advertisers. With it’s super-low cost per click ratio, the ratio of fairness between Content Providers and Advertisers is leaned heavily toward Advertisers.

————————-

Anyway, the ad place on the bottom will be removed later today once we have finally cleared the cash withdraw point of $10. Google ads, on the other hand, are making us about $60 for t.rscript.org.

Hopefully, the removal of that ad will help lighten the visual load. Also will allow us to add site statistics in it’s place as per the original plan.

That’s all for now. Back to working on Capped. And job-hunting. [Anyone need a PHP Dev? Contact me and I'll send my resume]